Follow-up Comment #2, sr #720 (project savane):
> Well, there's no problem putting en_CA, it's just that this
> localization currently does not exists. And so it will get the
> fallback C locale, as expected.
Right. To make my idea clearer, it was that there should be a note, either
in the savannah.conf.pl, or in savane-doc, that the user needs to look in the
i18n directory to see what localizations are available (otherwise many might
not even know that directory exists, or where) before adjusting that
localization variable. Why? Let's say I put "sp_MX" in there because I'm a
Spanish speaker from Mexico. There is no "sp_MX" localization. I might
expect it to fall back to "sp", but I don't know that it will do this. Maybe
it will just default to English or French. The documentation issue is that a)
what the default is if the localization I specify is not available isn't
explained, and b) where the localizations are so I can just go and look isn't
mentioned at that part of the config file.
Again, I'm not asking for any assistance here, just trying to help make the
documentation clearer.
_______________________________________________________
Reply to this item at:
<http://gna.org/support/?func=detailitem&item_id=720>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
