Start a new topic

Using Tagging Glossaries to save time/avoid dull tag insertion work

I define Tagging Glossaries as bilingual word lists that can be used to match the tagging of target terms to that of the corresponding source terms.



An American cowboy rides a 1horse2 and not a 3bike4.


Een boerenzoon uit Holland rijdt vaker op een 3fiets4 dan op een 1paard2.

Content of the tagging glossary




Since this will be a major automation project, good planning is inevitable.

I see two different approaches, both with their pros and cons:

  1. Read all words of the source segment and match these with the source terms of the tagging glossary.
  2. Read all source terms of the tagging glossary and match them with the source segment.
For 1: In average, there will be less words in the source segment than there are source terms in the glossary. So this approach will be faster. However, is this relevant, in the context of the immense speed that modern computers have?
For 2: Multi-word source terms can be handled.

For 1: Multi-word source terms cannot be handled straight away.
For 2: For a larger glossary, a lot of comparing has to be done. However, is this relevant, in the context of the immense speed that modern computers have? And, how many terms will be present in an average Tagging Glossary? I think that it is save to assume that this kind of glossaries will be used for specific types of projects: documents with a lot of indexed terms, software translations with a lot of UI components that have to be set in italics, bold etc.

Once you know how to do it, it's quite simple:


Very happy with this :). This is going te save me a lot of boring tag insertion work and lets me focus on the nice part: the actual translating.

There’s now support for Transit tags too. And I’m planning to add handling of tagged terms with trailing punctuation marks.
Login to post a comment