Forum: CAT Tools Technical Help
Topic: How your CAT tool handle entity references?
Poster: tz7
Post title: RE: XTM
[quote]Stepan Konev wrote:
Why “except XTM”?
Both XTM and Smartling insert a special tag for nbsp, unlike Memsource, memoQ and Trados that use regular character (“invisible” degree sign). [/quote]
Yes, as default, XTM represent non-breaking space as an inline tag in red. If you want, like me in Japanese, you can remove them from your translation. The issue was XTM changes non-breaking space (＆#160;) in XML to ＆nbsp; automatically and this broke our build process, because ＆nbsp; is illegal for XML. The solution provided from XTM was representing all the entities as-is. So translators see "＆#160;＆#160;＆#160;＆#160;＆lt;RecipientStatuses＆gt;", instead of "{sp}{sp}{sp}{sp}＜RecipientStatuses＞", when translating. Well... at least we could get the valid target XML files. But, as expected, translators complained. Another solution provided was representing all entities, including ＆nbsp;, as inline tags, which you can't remove from your translation. We couldn't accept the 2nd solution. So currently, translators are seeing "＆#160;＆#160;＆#160;＆#160;＆lt;RecipientStatuses＆gt;".
I am working as a translator for Japanese and a PM for other languages. I have access to both source files and target. We don't translate any Word files in XTM.
Thank you everyone for your comments!
Topic: How your CAT tool handle entity references?
Poster: tz7
Post title: RE: XTM
[quote]Stepan Konev wrote:
Why “except XTM”?
Both XTM and Smartling insert a special tag for nbsp, unlike Memsource, memoQ and Trados that use regular character (“invisible” degree sign). [/quote]
Yes, as default, XTM represent non-breaking space as an inline tag in red. If you want, like me in Japanese, you can remove them from your translation. The issue was XTM changes non-breaking space (＆#160;) in XML to ＆nbsp; automatically and this broke our build process, because ＆nbsp; is illegal for XML. The solution provided from XTM was representing all the entities as-is. So translators see "＆#160;＆#160;＆#160;＆#160;＆lt;RecipientStatuses＆gt;", instead of "{sp}{sp}{sp}{sp}＜RecipientStatuses＞", when translating. Well... at least we could get the valid target XML files. But, as expected, translators complained. Another solution provided was representing all entities, including ＆nbsp;, as inline tags, which you can't remove from your translation. We couldn't accept the 2nd solution. So currently, translators are seeing "＆#160;＆#160;＆#160;＆#160;＆lt;RecipientStatuses＆gt;".
I am working as a translator for Japanese and a PM for other languages. I have access to both source files and target. We don't translate any Word files in XTM.
Thank you everyone for your comments!