some locale's message.mo file is not generated

[Genie]

Hi~

after r11293,

some locale's message.mo file is not generated.

• hy, ko, pl and tr locale

and message is displayed in english only.

[Christian Boos]

Yes, it's normal, the catalogs haven't been updated by their respective translators and they contain fuzzy translations so they were skipped while compiling.

Full list:

$ make compile | grep fuzzy
catalog 'trac/locale\\el\\LC_MESSAGES\\messages.po' is marked as fuzzy, skipping
catalog 'trac/locale\\fa\\LC_MESSAGES\\messages.po' is marked as fuzzy, skipping
catalog 'trac/locale\\hy\\LC_MESSAGES\\messages.po' is marked as fuzzy, skipping
catalog 'trac/locale\\ko\\LC_MESSAGES\\messages.po' is marked as fuzzy, skipping
catalog 'trac/locale\\pl\\LC_MESSAGES\\messages.po' is marked as fuzzy, skipping
catalog 'trac/locale\\tr\\LC_MESSAGES\\messages.po' is marked as fuzzy, skipping
catalog 'trac/locale\\vi\\LC_MESSAGES\\messages.po' is marked as fuzzy, skipping

See TracL10N#Translationcoordination for contact information if you need to get in touch with some of the current translators.

At some point during 1.0.x, we should do something about "abandoned" translations, targeting in particular those who are below 50%:

$ make summary locale="el fa hy ko pl tr vi"
l10n/el: translations updated (45%)
l10n/fa: translations updated (41%)
l10n/hy: translations updated (75%)
l10n/ko: translations updated (53%)
l10n/pl: translations updated (65%)
l10n/tr: translations updated (76%)
l10n/vi: translations updated (46%)

[Genie]

Thanks for your answer, but it is not normal.

This changes was applied suddenly after Trac 1.0 rc1.

Currently, All messages are displayed in english only for Korean user on Trac 1.0 release.

I'm very shocked because suddenly changed.

[Christian Boos]

Well, the risk of using the Korean translation (or any other translation which fails make check) is not just to miss a translation or two, but to trigger internal errors (like #9197 or #10066). So better not. If this is really a problem for you, then by all means contribute (or find someone to contribute) the fixes.

If no one takes action or shows interest for these translations after a while, then we're simply going to drop the translation to not have the misleading choice.

Maybe we could even have a way to remove them from the list now? (trac.util.translation.get_available_locales() could look for messages.mo files instead of just the directories).

[Christian Boos]

Maybe we could even have a way to remove them from the list now? (trac.util.translation.get_available_locales() could look for messages.mo files instead of just the directories).

trac/util/translation.py

@@ -337 +337 @@
 
         try:
             return [dirname for dirname
                     in pkg_resources.resource_listdir('trac', 'locale')
-                    if '.' not in dirname]
+                    if '.' not in dirname
+                    and pkg_resources.resource_exists(
+                    'trac', 'locale/%s/LC_MESSAGES/messages.mo' % dirname)]
         except Exception:
             return []

[Genie]

Thanks, I think this issue was resolved with releasing Trac 1.0.1.

Replying to cboos:

Maybe we could even have a way to remove them from the list now? (trac.util.translation.get_available_locales() could look for messages.mo files instead of just the directories).

trac/util/translation.py

@@ -337 +337 @@
 
         try:
             return [dirname for dirname
                     in pkg_resources.resource_listdir('trac', 'locale')
-                    if '.' not in dirname]
+                    if '.' not in dirname
+                    and pkg_resources.resource_exists(
+                    'trac', 'locale/%s/LC_MESSAGES/messages.mo' % dirname)]
         except Exception:
             return []

[Genie]

Oops, I misunderstood.

Replying to Genie:

Thanks, I think this issue was resolved with releasing Trac 1.0.1.

Replying to cboos:

…

[Christian Boos]

No problem ;-)

Patch from comment:5 committed in r11684.

[Christian Boos]

Somehow I knew that this innocent looking change from comment:5 would be trouble if committed right before 1.0.1 ;-)

Hopefully it's now all sorted out with r11691.