On Thu, Nov 15, 2012 at 3:24 PM, Fabiano Fidêncio <fabiano@xxxxxxxxxxxx> wrote: > On Thu, Nov 15, 2012 at 7:25 AM, Christophe Fergeau <cfergeau@xxxxxxxxxx> wrote: >> Hey, >> >> On Thu, Nov 15, 2012 at 02:06:55AM -0200, Fabiano Fidêncio wrote: >>> Add this translation in the fedora template file because kickstarter >>> script must set the language using the glib-way (eg: en_US) meanwhile >>> the application must set the language using l10n standard (eg: en-US) >> >> Sorry, haven't paid close attention to these installation series, but what >> is 'l10n standard' ? > > Don't know if "l10n standard" was a good expression. > I spent some time taking a look in the internet, trying to find what > kind of localization is more common. For instance, for Brazilian > Portuguese we can find: pt_BR and pt-BR. > The first one is the way used in linux/glib. The second one is used by > Windows, Java, Mozilla, etc. > >> Does libosinfo have an API expecting the language in >> that format? > > There is no explicit restriction on libosinfo, only in the functions > name as: get/set_l10n_language. > > What do you suggest? The format expected for Windows and Linuxes are > different and we should treat it in the lib, avoiding nagging > application about that. In this case it seems the standard is what windows is complying too (surprising, isn't it?): http://www.ietf.org/rfc/rfc4646.txt . However, since libosinfo is more often/likely to be used on Linux, asking app to translate lang code from linux to standard format and then translating it back again in XSL for all linux scripts seems pretty sub optimal. So perhaps we should do the opposite of what this patch is doing and specify whats expected in osinfo_install_config_set_l10n_language() docs. -- Regards, Zeeshan Ali (Khattak) FSF member#5124
