The tokenizers are used for stemming, stop words and tokenization of CJK languages, and they make a dramatic improvement for fuzzy matching and glossaries. Tokenizers, the LanguageTool linguistic checker and the scripting engine have been available for quite some time as separate plugins, but they are now an integral part of OmegaT. Which are its newer and more experimental developments? In addition, although it’s not really a feature, I would add that OmegaT works on any platform (Windows, Mac, Linux, FreeBSD, Solaris, etc.) where Java is available. Public plugin API for third party development.Machine translation (Google Translate v2, Microsoft Translator, Apertium…).Spell checking Dictionaries (StarDict and Lingvo DSL formats).Right to left and bidirectional writing management.Projects with an unlimited number of folders and files, in all accepted formats (31 formats available, can be extended to 38 with the Okapi plugin).So, although OmegaT was created by Keith Godfrey, and was later extended by Maxym Mykhalchuk, the key person in the project was Marc, which makes the project very original, because Marc is a translator, and not by any means a developer. Marc was very interested, because he wanted to switch to Linux, and no CAT tool was available for that platform at that time. Keith wanted to abandon the project, when Marc Prior (OmegaT’s Project Coordinator) convinced him to continue. As far as I know, it was a tool intended for his wife, who is a translator. OmegaT was created by Keith Godfrey in 2000. When I became a bit surer I could handle that role, it was changed to “Release Manager”, and later on to “Development Manager”, to better reflect what I do in the OmegaT project. I accepted to become “Acting Release Manager”. When Henry Pijffers resigned as Release Manager in 2007, I was the only active developer with commit rights. I did it first privately, integrating my changes each time a new version was released.Īfter a while, it became tiresome, so I offered my first contribution to the project (revision 712: Added HTML Help Compiler (HHC) filter), which was kindly accepted. I persevered a bit more with OmegaT, and after a few hours everything became obvious.Īlthough I had never really developed in Java before, the fact that the source code was available allowed me to improve the software for my own use, for instance by creating a new filter to translate table of contents of online helps. One day I translated 14,000 words, even if OmegaT was only segmenting by paragraphs at that time). (There were many repetitions in this project. It’s only when I started to work on my first big project in HTML that I quickly realised I needed a CAT tool. Out of curiosity, I had tried Wordfast (Classic, at that time) and OmegaT, but didn’t really see the point initially. What path led you to OmegaT?Īfter a first career in computing, I started to work as a translator (initially mainly in localisation) in 2004.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |