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.
Heinrich Pesch Finlandia Local time: 04:35 Membro (2003) Da Finlandese a Tedesco + ...
Feb 1, 2008
My current work is a word-file with lots of index fields: {XE"something"}.
Perhaps these are called something else, but they are for indexing the document after translation.
I wonder which tool handles these fields properly. I now use Wordfast, which has a function for this. But it does not work consistently.
When I press Alt+Ins in order to copy the source into the target, a window opens titled "Translatable Field Translation". Most of the time the suggest... See more
My current work is a word-file with lots of index fields: {XE"something"}.
Perhaps these are called something else, but they are for indexing the document after translation.
I wonder which tool handles these fields properly. I now use Wordfast, which has a function for this. But it does not work consistently.
When I press Alt+Ins in order to copy the source into the target, a window opens titled "Translatable Field Translation". Most of the time the suggested translation is right, but always in between things get messed up and I have to wright the translation myself, though Wf has translated the same term hundreds of times right.
What are your experience with translation of these fields in various tools.
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Claudia Alvis Perú Local time: 20:35 Membro Spagnolo + ...
Transit did it for me
Feb 1, 2008
Hello Heinrich,
Remember my thread about embedded text? I tried several tools and the only one that worked perfectly was Transit. But I was dealing with several kinds of field marks, including XE fields, which were very problematic also.
Since the XE code seems to somehow disrupt the way CAT tools handle segments or TUs, I ended up using Transit's own dictionary tool to replace the text between the XE codes. It was easy with Transit*. I don't remember how WF handles te... See more
Hello Heinrich,
Remember my thread about embedded text? I tried several tools and the only one that worked perfectly was Transit. But I was dealing with several kinds of field marks, including XE fields, which were very problematic also.
Since the XE code seems to somehow disrupt the way CAT tools handle segments or TUs, I ended up using Transit's own dictionary tool to replace the text between the XE codes. It was easy with Transit*. I don't remember how WF handles terminology but in theory it should work with other tools too.
Claudia
For the record and maybe this'll help others, Transit tags show up in this format: text. I had to add a space between the tags in order to automatically add the terms in the dictionary. So if you're using a different CAT tool and you can't replace the terms using using the terminology feature, try adding a space to separate the text from the tags.
Translate faster & easier, using a sophisticated CAT tool built by a translator / developer.
Accept jobs from clients who use Trados, MemoQ, Wordfast & major CAT tools.
Download and start using CafeTran Espresso -- for free
Create your account in minutes, and start working! 3-month trial for agencies, and free for freelancers!
The system lets you keep client/vendor database, with contacts and rates, manage projects and assign jobs to vendors, issue invoices, track payments, store and manage project files, generate business reports on turnover profit per client/manager etc.