Category Archives: glossary

This is a little article on how to semi-automatically insert context-dependent custom strings in OmegaT. To illustrate what I mean, I give a little example from the kind of work I get to do pretty often. Continue reading →

Situation

So, you downloaded and installed the Tokenizers to make OmegaT’s search for matches and glossary terms more effective. In the Readme file it says that one can create several scripts for the languages they translate from (and for which there are tokenizers), and there are even some examples. So, that’s what you did, and now everything works, but you long for a deeper life harmony and lesser hassle.

Problem

What you need is a possibility to choose which language you are going to translate from and which tokenizer you are going to use, having only one single script, and thus only one launcher on your Desktop/Panel/Start Menu or one command somewhere on the $PATH. Continue reading →