This is the mail archive of the
libc-locales@sourceware.org
mailing list for the GNU libc locales project.
[Bug localedata/2135] Please add esperanto locale (eo_UY)
- From: "egmont at uhulinux dot hu" <sourceware-bugzilla at sourceware dot org>
- To: libc-locales at sources dot redhat dot com
- Date: 13 Mar 2007 14:20:13 -0000
- Subject: [Bug localedata/2135] Please add esperanto locale (eo_UY)
- References: <20060110140534.2135.eduardo@esperanto.org.uy>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From egmont at uhulinux dot hu 2007-03-13 14:20 -------
It seems to me that while LANG and LC_* may only contain valid locale names
(since these variables are involved in the setlocale() call that handles
structures representing existing locales), the variable LANGUAGE which I guess
is only involved in gettext may take arbitrary value. So for example even if
there's no esperanto locale on your system, this setup seems to be perfectly
valid and working for me:
LANG=en_US.UTF-8
LANGUAGE=eo
and then translations are primary taken from the "<localedir>/eo" directory.
LANGUAGE can even take more language codes separated by ':', e.g.
LANGUAGE=eo:de to fall back to German for each string where esperanto
translation is not available.
This means that you can translate your application to Esperanto even if there's
no such locale. What is still missing is the stuff coming from the locale
database: month and weekday names, first day of week in calendar, localized
date format, decimal separator and grouping character, yes/no regexp, collation
etc...
--
http://sourceware.org/bugzilla/show_bug.cgi?id=2135
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.