On Mon, 23 May 2011 16:04:47 +0200 Dr. Werner Fink wrote:
> it should be noted that I've correct locale setup to avoid false
> error reports from locale.sh (as with glibc there is no such
> C_EU.UTF-8 nor C.UTF-8 locale beside C is an alias for POSIX)
the libast locale intercept provides two test locales
C.UTF-8
C_EU.UTF-8
this enables utf-8 multibyte code but does not pull in any other localization
cruft
it allows us to write regression tests with deterministic results across all
platforms
(some target platforms have limited locale support)
the difference between the two test locales is in the LC_NUMERIC category
C.UTF-8 decimal_point='.' thousands_sep=','
C_EU.UTF-8 decimal_point=',' thousands_sep='.'
so the locale settings in the ksh test scripts should not be changed
of course this means all tests using the test locales assume that the
test locales and the ast intercepts actually work
if you find evidence that the test locales are the root of a regression then
we need to know that
can you rerun the tests without changing the locale seetings as distributed
thanks
background: this all came about from the difficulty of writing a portable
script that works on all targets that
(1) determines a UTF-8 locale with decimal_point='.' thousands_sep=','
(2) determines a UTF-8 locale with decimal_point=',' thousands_sep='.'
it was much easier to write the locale intercept and provide at least
C/POSIX locale UTF-8 support on all target platforms
_______________________________________________
ast-developers mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-developers
