Harklas wrote:
Now I've got a bunch of xml:s and one "ini file" which "it's important to use".
If the customer expects you to use Trados, then I confirm the .ini file is useless.
Forget about the .ini file, you cannot do anything with it.
Open the XML file with a text editor (VI, Notepad, etc.)
If the text to translate is between tags:
Rename a copy of the file to .html
Rename a copy of the file to .xlf
Open in OmegaT, see how it looks, both as HTML and XLIFF.
Generate the target documents. Do a diff between the source and the target
documents. Possibly, there are small things that you'll have to repair
manually after translations. (Like a > converted to >, etc.)
Once you have determined the best compromise, use either the HTML or XLIFF
filter.
If the text to translate is (at least partly) in attributes, you will have
to modify an existing filter.
That sounds like a hell lot of trouble, with no guarantee of good results.
It mostly sounds like it might not be adapted to your case at all.
Circumstances might be different, and that discussion you quote is from 2009. A lot of things have changed since.
I'm not starving or anything, so I'm very tempted to tell the customer to "give me an excel file and a tmx and let your software people sort out the rest or we're not doing this". But the customer is nice so I'd like to at least make an effort first ... I just don't know where to start.
If the customer expects you to use Trados, then they could send TTX files, which would be much more simpler.
Anyway, the best advice was given by Susan:
Susan Welsh wrote:
you might want to post to the OmegaT yahoo group instead, as it gets more attention than this forum, from the people who know all the answers!
Didier
Login to reply/comment 
