This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
Simon Willmott United Kingdom Local time: 08:14 Member (2010) German to English + ...
Sep 29, 2011
I encountered an issue with a recent project, where the target XML files I delivered to my client had extra tags that were not present in the source, rendering them invalid.
I originally received XML source files, and had to deliver target XML and TTX files. As I prefer to work in Studio, my workflow consisted of:
1. Open XML files in TagEditor, save as TTX 2. Create new project in Studio, add TTX files as source files 3. Translate 4. Finalize project... See more
I encountered an issue with a recent project, where the target XML files I delivered to my client had extra tags that were not present in the source, rendering them invalid.
I originally received XML source files, and had to deliver target XML and TTX files. As I prefer to work in Studio, my workflow consisted of:
1. Open XML files in TagEditor, save as TTX 2. Create new project in Studio, add TTX files as source files 3. Translate 4. Finalize project in Studio to create translated TTX files 5. Clean these TTX files up in Workbench to get target XML files.
This process resulted in some XML files that were not valid, as the tag structure had been altered. When trying to work out what had happened, I discovered that a workflow without the Studio 2009 stage (i.e. translate in TagEditor) resulted in perfectly valid XML files.
To illustrate what I mean, here are a few screenshots. I've altered the text to remove any sensitive client details.
TTX file translated in the Studio 2009 workflow. Note the tags at the end of the line. These occur outside the TU and are what cause the target XML files created from this file to not work:
TTX file processed solely in TagEditor. Target XML files created from this file work fine:
Comparison of the two target XML files (using BeyondCompare software). The top line is from the file created with the Studio 2009 workflow and this file does not work. The bottom one works fine and was processed exclusively in TagEditor:
There are going to be further batches in this project, so I need to know how to ensure the error does not occur again. Can anyone shed any light on why this happened?
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
RWS Community United Kingdom Local time: 09:14 English
Smart tag pairing
Oct 1, 2011
Hi,
It looks as though you have processed the TTX files in Studio without disabling smart tag pairing. A TTX often produces placeholders that Studio can try to turn into proper tag pairs. This is done to provide for working with a better wysiwyg effect in the editor.
Now, if you are taking the TTX and saving the proper target file rather than a TTX to return to 2007 then this is usually ok. But if you are returning a TTX file instead then you should disable smart tag... See more
Hi,
It looks as though you have processed the TTX files in Studio without disabling smart tag pairing. A TTX often produces placeholders that Studio can try to turn into proper tag pairs. This is done to provide for working with a better wysiwyg effect in the editor.
Now, if you are taking the TTX and saving the proper target file rather than a TTX to return to 2007 then this is usually ok. But if you are returning a TTX file instead then you should disable smart tag pairing to be on the safe side.
The option can be found in Tools - Options - TRADOSTag - Compatibility. Try aain with smart tag pairing disabled and see if this is better (I hope this is the reason..!).
This is covered in the Studio migration guide in the start menu if you want more info on it.... there is also a whitepaper on this here:
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.
The leading translation software used by over 270,000 translators.
Designed with your feedback in mind, Trados Studio 2022 delivers an unrivalled, powerful desktop
and cloud solution, empowering you to work in the most efficient and cost-effective way.