Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have some experience in i18n for other project (GNOME), so I have
some answers to your questions.

On 02/26/2015 02:18 PM, Sean Dague wrote:
> This morning in the nova channel we were trying to get to the
> bottom of the unit tests failing lxsi and gillard in en_GB on some
> string comparisons. Something is breaking down in our i18n null
> fixture for the tests.
> 
> However, in trying to track down the route of their messages I ran
> into things like this:
> 
> https://github.com/openstack/nova/blob/master/nova/locale/en_US/LC_MESSAGES/nova.po#L1410-L1411
>
> 
> 
> https://github.com/openstack/nova/blob/master/nova/locale/en_US/LC_MESSAGES/nova.po#L3481-L3485
>
>  
> https://github.com/openstack/nova/blob/master/nova/locale/en_US/LC_MESSAGES/nova.po#L5790-L5793
>
> 
> 
> https://github.com/openstack/nova/blob/master/nova/locale/en_US/LC_MESSAGES/nova.po#L3278-L3282
>
> 
> 
> 
> So, correct me if I'm wrong, but I think that means that when
> running in en_US those log messages are going to get overridden.
> And in many of these cases they are getting overridden to
> completely unrelated messages.

No, those messages are marked as 'fuzzy'. They were filled in by
gettext heuristics, but without a translator to go thru them and
unmark them as 'fuzzy', the translations are not applied.

https://www.gnu.org/software/gettext/manual/html_node/Fuzzy-Entries.html

> 
> That seems quite dangerous. Is there a reason that en_US locale
> tree exists at all (given that we've treated it as base locale
> historically). It seems like it's existence can only cause issues.

In theory, en_US locale may be used to fix typos without touching the
translatable message (to avoid getting the existing messages in other
languages untranslated). This approach is usually applied when in
message freeze mode, when developers are forbidden to touch the
messages, but translators still want to remove typos for en_US users.

I don't know how this applies to openstack though, since I'm not sure
whether we enforce string freeze here, and whether translators care
about occasional typos in en_US UX.

> 
> What's the right way to test / checkpoint on this on a regular
> basis?
> 
> -Sean
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJU7x9kAAoJEC5aWaUY1u577mIH/07l7SaoyQ05+e+grS5XM4Pw
PDAdtEqPFLGJtdyV+9QpvPWbJ2xF1HVC2mTPYmJIStGB9ZOEaFGU9JlCQrmFCM+Q
iS9m60H/ifRlm+pIK5y+o67D4J/Zj8PmuBRfmHO6wYahUYC0FUcKOQj4Zk5RKLZI
sh2MKrtXpYGqQSg+KcpubEtKO0MFYx2V3OfqdtrECiufuQjC+dxiViNUvE6C6rmr
CE6A0yFGa2kxlF62Zy8l05FjGrE2mO/sKMPjbmkrzqzt8b90M7ltK4wKidXRK3qZ
8KXTUtTGDCjicbxxnaRZDLCeK2ZlNpIIx2DncTw73oxY5pv3dEJZJIYhAp82lQA=
=2PSa
-----END PGP SIGNATURE-----