Hi Oliver,
Olivier Hallot wrote:
Hi Sophie
In the past (2003) we built a glossary based on the recomendations of
the l10n project at that time. It had 11K strings aproximately.
That glossary was mandatory as first translation memory for the bulk job
of OO 1.0.3 localization here, although it lead us to errors as some
strings had different translation depending on the application (e.g.
outline for texts, spreadheets or graphics). But since then it became
less important as the memory translation was getting better and better,
and the team got used to the software features.
ok, I understand. That was why I talk about handling also comments or
tags. I rely more on glossary than on translation memory for
consistency, even if it's a great help and save a lot of time.
Today, we don't use a formal glossary. Instead our knowledge on the
software is enough for addressing the improvements. Also, the pace of OO
releases together with pootle ease of use and access allow us to keep
our translation sharp and very often, as side benefit, a reference for
other softwares.
Great :) Do you have documentation translators working with your
previous glossary or searching on Pootle?
Thank you very much for your feedback.
Kind regards
Sophie
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]