If your CAT tool can translate XLIFF, then you can also try the Translate Toolkit's program po2xliff (and xliff2po), which may or may not work yet - test it first. You can also use the Translate Toolkit's po2csv program to convert the PO files to CSV, which you can open in Excel and then translate in any program you want, and then save from Excel as CSV again and use csv2po to convert it back to PO.īefore you use po2csv and csv2po extensively, experiment with small files to see if your version of Excel handles CSV files correctly - although if not, you can set certain extra functions in po2csv and csv2po to make provision for it (eg codepage). You can then try to translate those formatted PO files in your CAT tool. It is a commandline tool but it produces compliant PO files quickly. You can try to use find/replace, but that is dangerous, so I suggest you get msgen.exe from the Gnu Gettext suite. To use them in Wordfast, Trados or OmegaT, you need to convert them to source=source format. I assume the client sent you compliant PO files to begin with. although they are displayed in PoEdit in columns, so perhaps the client simply means that he wants compliant PO files that open correctly in PoEdit. I have no idea what "the two columns" mean because PO files don't have columns. ".however, the client imposes to receive the Po files with the two columns. At 50.000 words workload I honestly feel it pays to go this way. Essentially it's a preprocessor for the Word global search
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |