[Aptitude-devel] Bug#537858: aptitude: comments on i18n
Manuel A. Fernandez Montecelo
manuel.montezelo at gmail.com
Sat Feb 8 15:29:28 UTC 2014
Control: tags -1 + pending
Thanks for raising this up and the recommendations.
Some of these things are obsolete already, but I addressed most of the
rest of the things, will be present in the new releases:
- About "no-summary", "first-package" and so on, both the original
messages in english and the translated ones are accepted by the
program, so yes, they should be translated
Maybe it would be better to not allow translation of keywords at all,
it's not allowed in other places --e.g., the why command itself--, so
the way in which is done is inconsistent and generates more work for
both devels and translators without much benefit for the user, I
think. Suggestions/comments about this?
- Then, in the error message, since both the english and the
translated are accepted, I think that the translators should put both,
but I don't know what's the common practice.
- I marked as not translatable the ones in GTK GUI and fixed the one
which was not using ngettext, but GTK is disabled since long ago and
never was in good shape. Same for Qt GUI.
Is there a common/easy way to disable source code directories for
gettext when generating the .pot files, so at least new translators
don't waste time to translate things that will possibly not be enabled
- I didn't change the ForTranslators thing yet. Is TRANSLATORS used
(virtually) everywhere? Or different projects use different
conversions and it's all right?
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>
More information about the Aptitude-devel