The extra kick of course comes when learning how to parse the whole darn thing: the "source" It can be really HAIRY.I used Tortoise tagger by Alexander Okunev. But once you clean it, it should revert to a bilingual (source > target) PO file, you can check out with POedit. Of course if you then look at the bilingual contents before cleaning, it does look crazy.
Trados will then only see the second source as something to translate. The trick: make everything but the second string in the pair external or nontranslatable (!). essentially make a bilingual Source > Source PO file)Ģ. The latest method - and I tried a few - was close to what Harry suggests - but different.
I have translated what must be about 80.000 words of OpenOffice help ith TRADOS. My poEdit version was downloaded from You may want to have a look at pootle on sourceforge - one of the few projects dealing with PO format. My poEdit version was downloaded from I would greatly appreciate any help in this. While there seems to be no problem with processing the according HTML file with Tageditor, the question is how will I be able to convert the TTX file into the PO format once I have finished the translation? If you find a solution you can work with the software you want but we need Sure if we can transform the html files into po format. I know we can export an html version and work with tageditor but I am not Imposes to receive the Po files with the two columns. ”It doesn't matter to the client if you use Tageditor or poEdit, however, the client Here is what the PM told me upon my proposal to use Tageditor: I started using poEdit, but it looks very time-consuming to me with at least 3 key strokes needed to advance from one TU to the next, so I would be much more comfortable using Tageditor instead of poEdit. This is needed for a website translation of some 50,000 words. Does anyone know of a way to convert a bilingual TTX file into a PO file (poedit file).
0 kommentar(er)
