The formats that particularly come to mind are the GNU gettext. Many open-source projects are not based on the commercially-used file formats that yours and mine are based on, but on ones that many of us have rarely if ever heard of. There is one other reason as well, though, and that is different file formats. (It's too bad that this won't be read by many open-source translators since this will appear only in the paid Premium edition. This points, thirdly, to the cultural rift between the two groups, one that in my opinion is unfortunate. It was a smart move for both their publicity and their influence among those folks.) Second, most commercial TEnTs used to run only on Windows, which was not particularly popular among many connoisseurs/translators of open-source software products. #Xliff editor mac 2016 for free(A few years ago I convinced the developers of Heartsome to give away their tool for free to Firefox translators, who had no tool whatsoever. One is that the commercial translation environment tools are, well, commercial, cost a lot, and are therefore not accessible for the mostly volunteer open-source translators. But the crossover is the exception rather than the rule. The open-source translation environment tool OmegaT, built mostly for and by professional commercial translators, is used by some open-source translators, and there are a handful of commercial translators using tools like Virtaal, Pootle, and Poedit. Virtually none of the tools used by open-source translators are used by commercial translators, and vice versa. I've written before about the strange phenomenon surrounding translators of open-source materials, who, though by most accounts often very technical, have no technology intersection with their commercial counterparts. Actually, both DVX2 and MQ can process po files, too.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |