1

Currently we are using web 8.5 and sending components in bundle for translation and checking its status in translation manager. We have encountered an issue and I am fairly new to translation module and need help in understanding the root cause.

     <p>This is a sample by [[authorName]].<br/>Contact me at [[authorEmail]]</p>

Above is a sample text in rtf when inspected in world server source view, authorEmail is enclosed in embed tag whereas authorName isn’t enclosed in embed tag and getting translated. We did not find this embed tag in cms side and aren’t sure where it is being added in or before sending to world server. We think, due to embed tag not being added to authorName the text in double quotes is being translated which shouldn’t be.

    <p>This is a sample by [[authorName]].</p><br/><p>Contact me at [[authorEmail]]</p>

For testing we sent text in rtf as above closing the p tag before br tag and opening p tag after br tag then we could see authorName also enclosed in embed tag.

Improve this question
5
  • By default, Tridion Sites wouldn't add the wrapping double brackets to content as its stored in the CMS. Do the brackets appear if you check the version history in Tridion Sites before, during, or after sending items to translation?
    – Alvin Reyes
    Commented Aug 7, 2023 at 22:42
  • And do you happen to know if the Translation Manager setup was customized (e.g., with custom ITS rules)? I'll try to ask around but I suspect the brackets and/or those words are being handled on the WorldServer side.
    – Alvin Reyes
    Commented Aug 7, 2023 at 22:44
  • Double brackets are intentional specified by cms author in Tridion to specify the text which would later be replaced by web code with actual value. Sorry for not mentioning it.
    – TridionUser
    Commented Aug 8, 2023 at 6:34
  • Okay, does the mention of "double quotes" above really refer to double brackets?
    – Alvin Reyes
    Commented Aug 8, 2023 at 15:39
  • I added an answer based on what I know for Tridion Sites and WorldServer. I think by default the double-bracketed text would appear as translatable in WS or Computer-aided translation (CAT) client/tool like Trados Studio. So there's likely a specific segmentation rule or configuration to put things like authorName in embed tags.
    – Alvin Reyes
    Commented Aug 8, 2023 at 17:09

1 Answer 1

Reset to default
1

Welcome to Tridion Stack Exchange.

By default, the double-bracketed text would be translatable, as seen by translators in Trados Studio, for example, as segments to translate with the rest of the text. I'll describe the translation process from Tridion Sites to WorldServer from what I know to hopefully highlight a few places for you to check.

From Tridion Sites

As part of the translation process, Translation Manager gathers the requested items to translate and converts them to the .ITS format, which is a format governed by W3C and recognized by various translation systems, such as WorldServer, TMS, or Trados Enterprise.

In general, Tridion Sites marks entire fields as translatable or not, based on the Schema settings. However, the ITS Rules can be modified in the TranslationManager.XHTML.ITS.Rules.xml file (see the documentation). These rules adjust how the XML translates, so it might be worth checking if these might have been customized.

To WorldServer

On the translation side, World Server's filters handle the .ITS file format sent by Tridion Sites through Translation Manager. The format is configured as a "custom component" in WorldServer.

From what I understand from colleagues quite familiar with WorldServer, that double-bracket syntax and contained words would appear as translatable segments by default, at least to the system.

For example, my colleague shared this from a screenshot in Trados Studio of a similar setup, without customization.

source and target translation segments

Note that the <p> tag has been explicitly recognized as a tag, however, the double-bracketed text just appears as source text in the segments on the left, with the text on the right ready to be translated to some expected target language.

Perhaps the segmentation process and filter has been customized for the ITS format (e.g., for .cmp files)? It would be worth following up with your project management office (PMO) or project manager on the localization side (or your localization team if internal). Otherwise submit an RWS Gateway ticket to further investigate the setup.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.