I would like to report a bug (IMHO) in the Trados Studio 2014 (SP1 & SP2) import filter for Rich Text Format.
We have a source RTF document containing the string "shown in Table\~3\_2"
Inside Trados this becomes "shown in Table 32" [with a protected space after Table, but that's not relevant]. The problem is that character 1E is not valid in XML 1.0 (neither as a character nor as an entity).
Therefore both exporting for review (which writes to XML inside docx) and manually building an XML via System.Xml in a plugin raise exceptions with the message "hexadecimal value 0x1E, is an invalid character".
I was able to make our plugin more robust; for being able to export, I had to manually edit the sdlxliff file and search & replace the offending entities.
I would argue that, apart from being invalid XML (at least 1.0), an ASCII "Record separator" 1E is an unlucky choice for what obviously is meant to be a non-breaking hyphen in RTF, and I'd suggest the Unicode non-breaking hyphen ߛ [that's char 2011, in case the entity gets mangled] as a more fitting and compatible replacement – or for that matter, a Trados "non-breaking hyphen" TAG as is done when importing from DOCX.
[Edited at 2014-12-09 19:34 GMT]
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
To report site rules violations or get help, contact a site moderator:
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.
Manage your TMs and Terms ... and boost your translation business
Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.