A client asks you to translate a PHP file, or a non-standard XML file, or a proprietary format developed for & by the client. You open the file in Trados (or similar) and it tells you that "This file format is not supported" or "the file is not valid".
Fair enough, but now what? Turn down the project? Yes. Or you could use PrepTags and convert the files in a format which you can easily translate.
The typical translation job goes like this: the customer sends files. Translator opens the files in Word or with a translation tool, translates and delivers.
Simple. But what if your customer's files are not Word documents? There is an increasing demand for XML, (X)HTML, ASP, PHP, JS, SQL, PO and other technical-sounding file formats.
And you could translate these quite easily, if it wasn't for those pesky untranslatable codes. That and the fact everything would explode if you changed so much as a semi-colon.
Comments