mirror of
https://sourceware.org/git/glibc.git
synced 2024-12-23 11:20:07 +00:00
f16491eb8e
The error and warning handling in localedef, locale, and iconv is a bit of a mess. We use ugly constructs like this: WITH_CUR_LOCALE (error (1, errno, gettext ("\ cannot read character map directory `%s'"), directory)); to issue errors, and read error_message_count directly from the error API to detect errors. The problem with that is that the code also uses error to print warnings, and informative messages. All of this leads to problems where just having warnings will produce an exit status as-if errors had been seen. To fix this situation I have adopted the following high-level changes: * All errors are counted distinctly. * All warnings are counted distinctly. * All informative messages are not counted. * Increasing verbosity cannot generate *more* errors, and it previously did for errors conditional on verbose, this is now fixed. * Increasing verbosity *can* generate *more* warnings. * Making the output quiet cannot generate *fewer* errors, and it previously did for errors conditional on be_quiet, this is now fixed. * Each of error, warning, and informative message has it's own function to call defined in record-status.h, and they are: record_error, record_warning, and record_verbose. * The record_error function always records an error, but conditional on be_quiet may not print it. * The record_warning function always records a warning, but conditional on be_quiet may not print it. * The record_verbose function only prints the verbose message if verbose is true and be_quiet is false. This has allowed the following fix: * Previously any warnings were being treated as errors because they incremented error_message_count, but now we properly return an exit status of 1 if there are warnings but output was generated. All of this allows localedef to correctly decide if errors, or warnings were present, and produce the correct exit code. The locale and iconv programs now also use record-status.h and we have removed the WITH_CUR_LOCALE hack, and instead have internal push_locale/pop_locale functions centralized in the record routines. Signed-off-by: Carlos O'Donell <carlos@redhat.com> |
||
---|---|---|
.. | ||
charmaps | ||
locales | ||
tests | ||
tests-mbwc | ||
tst-fmon-locales | ||
unicode-gen | ||
bug-iconv-trans.c | ||
bug-setlocale1-static.c | ||
bug-setlocale1.c | ||
bug-usesetlocale.c | ||
collate-test.c | ||
cs_CZ.in | ||
da_DK.in | ||
de_DE.in | ||
Depend | ||
dump-ctype.c | ||
en_US.in | ||
fr_FR.in | ||
gen-locale.sh | ||
hr_HR.in | ||
hu_HU.in | ||
Makefile | ||
README | ||
show-ucs-data.c | ||
si_LK.in | ||
sort-test.sh | ||
SUPPORTED | ||
sv_SE.in | ||
th_TH.in | ||
tr_TR.in | ||
tst-ctype-de_DE.ISO-8859-1.in | ||
tst-ctype.c | ||
tst-ctype.sh | ||
tst-digits.c | ||
tst-fmon.c | ||
tst-fmon.data | ||
tst-fmon.sh | ||
tst-langinfo-static.c | ||
tst-langinfo.c | ||
tst-langinfo.sh | ||
tst-leaks.c | ||
tst-locale.sh | ||
tst-mbswcs1.c | ||
tst-mbswcs2.c | ||
tst-mbswcs3.c | ||
tst-mbswcs4.c | ||
tst-mbswcs5.c | ||
tst-mbswcs6.c | ||
tst-numeric.c | ||
tst-numeric.data | ||
tst-numeric.sh | ||
tst-rpmatch.c | ||
tst-rpmatch.sh | ||
tst-setlocale2.c | ||
tst-setlocale3.c | ||
tst-setlocale.c | ||
tst-sscanf.c | ||
tst-strfmon1.c | ||
tst-trans.c | ||
tst-trans.sh | ||
tst-wctype.c | ||
tst-wctype.input | ||
tst-xlocale1.c | ||
tst-xlocale2.c | ||
uk_UA.in | ||
xfrm-test.c |
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 http://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: