Re: Translation design patterns or approaches

[Adam Sampson]

Bento Borges Schirmer <bbschirmer@inf.ufsm.br> writes:

> I want to translate my CV to english. [...] Do you know any design
> pattern, macro set or preprocessor that could handle this task in a
> manageable way?

po4a (https://po4a.org/, packaged in most distributions already) is one
approach to this -- you write the document in your preferred source
language, then use gettext translations to specify how it's translated
into other languages.

This makes it reasonably easy to keep the translation up to date when
changes are made, because you can see what new phrases have been added
to the list of translations. (It's also convenient if you're already
using gettext in a project to translate strings in code.)

However, it needs to have an understanding of the document structure to
pull out phrases for translation, and while it supports man/mdoc already
it might not understand enough general groff for your purposes...

-- 
Adam Sampson <ats@offog.org>                         <http://offog.org/>