This content has been marked as final. Show 3 replies
Hi John. TBH I don't believe there is a real cast iron solution to your problem. All the methods you quote work and are used by others but each represents its own problems. I'm not familiar with EditLet. Are there other tools the translation company could host? The problem here is the still the propriety code of RH. Whatever app you use it likely to generate different code to RH which can cause problems when imported. Using Word to review (Ugg!) also works but you can tell from my exclamation what I think of that . Is it possible to get the users to add comments to the HTML code itself using comment tags? If may not be user friendly but they could add their comments without upsetting the delicate RH HTML. Just a thought.
I didn't think there would be a real easy way to do this, either...
Using comment tags is an idea, but I don't know how savvy the reviewers are with HTML.
Thanks for the feedback. I will send it along to the translation agency I work with.
Long time this topic was posted, but I add an answer anyway.
This is for when your translators use Trados. Trados can save translations in a bilingual (*.bif) file. It is an html-like file that contains for each translation unit (or sentence if you like) a tag with the original and a tag with the localized text.
It is not easy to read without Trados Tageditor (which is used by the translator) as it is similar of looking at the source of a html file. But, you could locate the faulty translation in that file and 'fix' it. If you then send these files back to the engine, they can run the 'cleanup' feature from trados. That generates the normal translated files, and while doing so, it also updates the translation memory with the fixes you made in the bilingual file.