Usually it is solved in a way that leadership of translation team translates glossary for project (for example, GNOME, OpenOffice.org both has special po files to for this, don't know about KDE). It contains all terms found in msgid. After careful checking and reviewing put it into use as translation memory in translation applications (Lokalize for example supports this).
Additionally, in my team we now carefully check any previous and new translations and when we sure that file is clearly ok, we add it to translation memory. It not only gives consistency of terminology, but it also provides fast way to translate strings already used in old translations. And even if there is no 100% match, it can at least give you hint how it should look like. For websites, open-tran.eu is quite ok for quick checking how others use terms. Also I suggest to check eurotermbank.com too (which has official terminology in lot of languages). Anyway, translate terminology is hard thing to do and it's a subject what we as a team spend most of our time on. Cheers, Peteris. 2009/12/27 Eleanor Chen <cheny...@gmail.com>: > Hi, all! > > During the translation process, I find that tranlation of terms vaies from > person to person. > So I am wondering if we can write a glossary for each language. > > Cheers, > Eleanor > -- > The world never lacks miracles. > > > -- > ubuntu-translators mailing list > ubuntu-translators@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators > > -- mortigi tempo Pēteris Krišjānis -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
