This commit updates month and weekday names (full and abbreviated)
from CLDR 35.1 with the following exceptions.
It was not clear why the full name of February in aa_DJ and aa_ER was
"Kudo" while the abbreviated version is "Nah" but some additional
sources [1] [2] as well as the content of aa_ER and aa_ER@saaho
suggest it should be "Naharsi Kudo". This commit consequently sets
the translation of February to "Naharsi Kudo" in aa_DJ and aa_ET.
aa_ER@saaho is not supported by CLDR but since the month names were
identical to aa_ER before this commit, the same values have been copied
from aa_ER.
Links:
[1] https://fr.wiktionary.org/wiki/naharsi_kudo
[2] http://www.mcit.gov.et/web/guest/-/localization-standard-for-afaraf
[BZ #21897]
* localedata/locales/aa_DJ (abday): Update from CLDR, all words
begin with an uppercase letter now.
(abmon): Likewise.
(mon): Update from CLDR, reword February from "Kudo" to
"Naharsi Kudo", April from "Agda Baxisso" to "Agda Baxis",
and August from "Liiqen" to "Leqeeni".
* localedata/locales/aa_ER (mon): Update from CLDR, reword
April from "Agda Baxisso" to "Agda Baxis" and August from
"Leqeeni" to "Liiqen".
* localedata/locales/aa_ER@saaho (mon): Likewise.
* localedata/locales/aa_ET (abmon): Update from CLDR, reword
abbreviated February from "Kud" to "Nah".
(mon): Update from CLDR, reword February from "Kudo" to
"Naharsi Kudo" and April from "Agda Baxisso" to "Agda Baxis".
POSIX locale descriptions
and
POSIX character set descriptions
Ulrich Drepper Time-stamp: <2004/11/27 13:06:54 drepper>
drepper@redhat.com
This directory contains the data needed to build the locale data files
to use the internationalization features of the GNU libc.
POSIX.2 describes the `localedef' utility which is part of the GNU libc.
You need this program to "compile" the locale description in a form
suitable for fast access by the GNU libc functions. Any compilation is
based on a given character set.
Once you run `make install' for the GNU libc the data files are
automatically installed in the right place, ready for use by the
`localedef' program.
To compile the locale data files you simply have to decide which locale
(based on the location and the language) and which character set you
use. E.g., French speaking Canadians would use the locale `fr_CA' and
the character set `ISO_8859-1,1987'. Calling `localedef' to get the
desired data should happen like this:
localedef -i fr_CA -f ISO-8859-1 fr_CA
This will place the 6 output files in the appropriate directory where
the GNU libc functions can find them. Please note that you need
permission to write to this directory ($(prefix)/share/locale, where
$(prefix) is the value you specified while configuring GNU libc). If
you do not have the necessary permissions, you can write the files into an
arbitrary directory by giving a path including a '/' character instead
of `fr_CA'. E.g., to put the new files in a subdirectory of the
current directory simply use
localedef -i fr_CA -f ISO-8859-1 ./fr_CA
How to use these data files is described in the GNU libc manual,
especially in the section describing the `setlocale' function.
All problems should be reported using
https://sourceware.org/bugzilla/
One more note: the `POSIX' locale definition is not meant to be used
as an input file for `localedef'. It is rather there to show the
values with are built in the libc binaries as default values when no
legal locale is found or the "C" or "POSIX" locale is selected.
The collation test suite
########################
This package also contains a (beginning of a) test suite for the
collation functions in the GNU libc. The files are provided sorted.
The test program shuffles the lines and sort them afterwards.
Some of the files are provided in 8bit form, i.e., not only ASCII
characters. So the tools you use to process the files should be 8bit
clean.
To run the test program the appropriate locale information must be
installed. Therefore the localedef program is used to generate this
data used the locale and charmap description files contained here.
Since we cannot run the localedef program in case of cross-compilation
no tests at all are performed.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Local Variables:
mode:text
eval:(load-library "time-stamp")
eval:(make-local-variable 'write-file-hooks)
eval:(add-hook 'write-file-hooks 'time-stamp)
eval:(setq time-stamp-format '(time-stamp-yyyy/mm/dd time-stamp-hh:mm:ss user-login-name))
End: