Hi Kenneth, folks, > [: Kenneth Nielsen :] > [...] I recently proofread a KDE po-file and discovered something > disconcerting. In this file it _seemed_ that these contexts had been > automatically generated and the context provided was simply the name of > the kind of widget or GUI-element they were in, (they could off course > also have been made by hand in this way, which makes it even more > strange). [...] Obviously we want to make sure that none of our developers > get this kind of idea. [...] Those "context markers" were indeed added by hand, and there are ideas to do it automatically where possible (e.g. in Qt's Designer XML, a counterpart to Glade). As an original perpetrator of this crud :) I'll add a few pointers for completness. The guide for KDE programmers on this topic is here: http://techbase.kde.org/Development/Tutorials/Localization/i18n_Semantics and the discussions which forged its current form: http://lists.kde.org/?t=117770563000002&r=1&w=2 http://lists.kde.org/?t=118209067600004&r=1&w=2 An example of a POT almost fully equipped with context markers: http://websvn.kde.org/*checkout*/trunk/l10n-kde4/templates/messages/kdebase/dolphin.pot?revision=HEAD For the ~2,500 messages retrofitted with context markers in the meantime, the duplication is as follows: due to context marker only: +7% due to context at all (i.e. non-empty when marker removed): +17% Exploiting the --previous option of msgmerge, there is a script to unfuzzy messages fuzzied only due to change/addition of msgctxt, or just of the context marker within it, at translators leisure (possibly adding "unreviewed-context" manual comment). -- Chusslove Illich (Часлав Илић)
Attachment:
pgpFPEjovVvJB.pgp
Description: PGP signature