Languages, translations, locales, timezones, keyboard layouts and the lang-table
On 12/06/2011 02:42 PM, Bill Nottingham wrote:
David Cantrell (firstname.lastname@example.org) said:
The second column provides the value used to find the .po file for
the chosen language. Check out loadLanguage() in lang.c. And look
at the loader.tr target in loader/Makefile.am. The loader.tr file
is a cpio archive containing all of the supported translations for
loader, but we store the po files as LANGKEY.po where LANGKEY is the
value of that second column.
If you can modify it to use any other field to store those files, we
should be fine.
If we're getting out of the loader business and just using standard
set-the-locale-and-use-gettext, can we drop this requirement?
Sure. I would like to see the remaining pre-anaconda interactive bits
become console-only. That works on all architectures we are required to
care about and will encourage us to keep things minimal because who
wants to drop the user to the console? And gettext is fine for that, so
that works for me.
David Cantrell <email@example.com>
Supervisor, Installer Engineering Team
Red Hat, Inc. | Westford, MA | EST5EDT
Anaconda-devel-list mailing list