Probability score: 0.6  

Question improvement suggestion: Provide specific details about the steps you took to troubleshoot the issue, including any error messages received and the exact version of Trados Studio you are using.  

In the meantime, based on the information you have provided, here is a suggested answer to your question:  

Hello,  

It seems you are encountering an issue with tag recognition in Trados Studio 2022, specifically with the links in the generated DE PDF from the translated XML file. Here are some steps you can take to troubleshoot and potentially resolve the issue:  

**Step 1:** Verify the XML Structure  

Check the source XML file to ensure that the tags are correctly structured. Look for any missing or improperly formatted tags that could be causing the issue.  

**Step 2:** Use the Correct Embedded Content Processor  

Make sure you are using the appropriate embedded content processor for your XML files. If you are using the HTML Embedded Content processor, ensure that all special characters are properly escaped as entities (e.g., use < for < and > for >).  

**Step 3:** Adjust Parser Settings  

Since you mentioned that setting "ri:page/@ri:content-title" to "Always Translatable" did not yield any changes, consider reviewing other parser settings in your File Type configuration. Ensure that the tag definitions are correctly set up to recognize the tags in your XML.  

**Step 4:** Check for Unrecognized Characters  

Open the file in the Online Editor and enable "Show Tag Details" to identify any unrecognized characters in the tag segments. If you find any, correct them accordingly.  

**Step 5:** Test with Different File Types  

If the issue persists, try using a different file type configuration or embedded content processor to see if that resolves the problem.  

**Step 6:** Review Translation Memory  

Sometimes, issues can arise from the Translation Memory. Check if the unrecognized characters are coming from the TM and correct them if necessary.  

If these steps do not resolve the issue, please provide additional details about any error messages you are encountering and the specific version of Trados Studio you are using. This information will help in diagnosing the problem more effectively.  

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

RWS Community AI

Nanako Sang 

Is this a PDF or an XML?  What was the actual source file you translated? I think a small sample file with this problematic part would be really helpful here.

Hello Paul:

Thank you for your attention and sorry for my late response.

The actual source file I translated is XML.

Regarding the PDF, it is generated from the translated XML after we submitted it to the client.

I'm enclosing the sample XML with the problematic part but I'm not sure if I enclosed it correctly.

Let me know if you need more details.

Thanks in advance.

/cfs-file/__key/communityserver-discussions-components-files/90/Sample_5F00_XML_5F00_250902.xml

Nanako Sang 

Perfect... that helps.  So I guess this is what you're after?

Your problem, I think, is that the text you're trying to get at is in an attribute and not an element.  So it's not extracted by default.  I created a parser rule for this and you can see from the document structure column on the right the initials ATT which show you the content is the value of the attribute.  These were the rules I used:

The one in question that you could not get at was this:

//ri:page/@ri:content-title

Hope that helps?

Thank you for your kind reply, Paul.

You are right. The one in question is "//ri:page/@ri:content-title".

However,it is not necessary to extract the text to translate. We are intended to put "//ri:page/@ri:content-title" tag in translatable segments instead of being hided in Content.

Here is current status:

Below is what we expected:

Is it possible to get this result by setting "//ri:page/@ri:content-title" in parser?

Also, I enclosed the setting file we used for your reference.

Thanks again for your help~

Nanako Sang 

You mean like this?

Achieved with this rule on the element... not the attribute:

Alternatively you could use a stylesheet just to keep the translation environment clean?  Then it's still visible, and the full content is less cluttered for review as well.

I put a version here in case it's helpful:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0"
  xmlns:xsl="www.w3.org/.../Transform"
  xmlns:ac="atlassian.com/content"
  xmlns:ri="atlassian.com/.../identifier"
  exclude-result-prefixes="ac ri">

  <xsl:output method="html" encoding="UTF-8" indent="yes"/>

  <!-- HTML shell -->
  <xsl:template match="/">
    <html>
      <head>
        <meta charset="UTF-8"/>
        <style>
          body{font-family:Segoe UI,Arial,sans-serif;margin:1rem}
          h1{font-size:1.4rem;margin:.25rem 0 .75rem}
        </style>
      </head>
      <body>
        <!-- render page title then content -->
        <xsl:apply-templates select="//title"/>
        <xsl:apply-templates select="//content"/>
      </body>
    </html>
  </xsl:template>

  <!-- Identity -->
  <xsl:template match="@*|node()">
    <xsl:copy>
      <xsl:apply-templates select="@*|node()"/>
    </xsl:copy>
  </xsl:template>

  <!-- Render <title> as a heading -->
  <xsl:template match="title">
    <h1><xsl:value-of select="normalize-space(.)"/></h1>
  </xsl:template>

  <!-- Key: prepend the referenced page title BEFORE the visible link text,
       but keep all original nodes so Studio segment mapping stays intact. -->
  <xsl:template match="ac:plain-text-link-body[../ri:page/@ri:content-title]">
    <!-- insert the attribute value on its own line -->
    <xsl:text>[</xsl:text>
    <xsl:value-of select="../ri:page/@ri:content-title"/>
    <xsl:text>]</xsl:text><br/>
    <!-- now output the original link body exactly as-is -->
    <xsl:copy>
      <xsl:apply-templates select="@*|node()"/>
    </xsl:copy>
  </xsl:template>

</xsl:stylesheet>