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.
Drew MacFadyen United States Local time: 07:35 Spanish to English + ...
Feb 4, 2009
I am pleased to announce that ProZ.com will be hosting a series of FREE webinars the week of February 16th, 2009. A listing of all webinars can be found at - http://www.proz.com/online_trainings
SDL TRADOS will be participating and will discuss the top 10 support issues as provided by ProZ.com users.
I am pleased to announce that ProZ.com will be hosting a series of FREE webinars the week of February 16th, 2009. A listing of all webinars can be found at - http://www.proz.com/online_trainings
SDL TRADOS will be participating and will discuss the top 10 support issues as provided by ProZ.com users.
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
kimjasper Denmark Local time: 13:35 Member (2006) English to Danish + ...
SDLX/Workbench transparency or increased exchangeability
Feb 5, 2009
With Workbench as my preferred environment and customers sending work as .itd files and sdlx TMs I often convert the files to the Workbench environment to do the actual work. Working on SDLX material from the Workbench side not a glitch-free process, e.g.:
* When using TagEditor on .itd files you cannot translate to fuzzy because the target part of the segments in the .itd files is typically pre-filled with either the source or a fuzzy match from the TM
With Workbench as my preferred environment and customers sending work as .itd files and sdlx TMs I often convert the files to the Workbench environment to do the actual work. Working on SDLX material from the Workbench side not a glitch-free process, e.g.:
* When using TagEditor on .itd files you cannot translate to fuzzy because the target part of the segments in the .itd files is typically pre-filled with either the source or a fuzzy match from the TM
* .itd files rarely survive a round trip to .ttx and back. If the segment contains tags and other markers (shown as coloring in the sdlx editor), these are typically replaces by a set of tags in the ttx file which do not match with the TM ported from SDLX through TMX. That makes it impossible to leverage the TM or perform batch translation of files. Usually I find myself doctoring the tmx files or or the Workbench source files to circumvent this and then still have to port the TM back to SDLX, open the individual .itd files and tick through the segments and accept the matches
With .ttx as well as .itd being so predominant (and SDL having invented .itd and aquired .ttx) is there any plans to make this process easier for the users by bringing the formats and architectures closer together or to increase the capabilities of the exchange tools?
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.