Re: [PATCH 1/2] localedef: Update LC_MONETARY handling (Bug 28845)

[Andreas Schwab <schwab@linux-m68k.org>]

On Feb 04 2022, Carlos O'Donell via Libc-alpha wrote:

> ISO C17, POSIX Issue 7, and ISO 30112 all allow the char*
> types to be empty strings i.e. "", integer or char values to
> be -1 or CHAR_MAX respectively, with the exception of
> decimal_point which must be non-empty in ISO C.
>
> We include a broad comment talking about harmonizing ISO C,
> POSIX, ISO 30112, and the default C/POSIX locale for glibc.
>
> We reorder all setting based on locale/categories.def order.
>
> We soften all missing definitions from errors to warnings when
> defaults exist.
>
> Given that ISO C, POSIX and ISO 30112 allow the empty string
> we change LC_MONETARY handling of mon_decimal_point to allow
> the empty string.  If mon_decimal_point is not defined at all
> then we pick the existing legacy glibc default value of
> <U002E> i.e. ".".
>
> We also set the default for mon_thousands_sep_wc at the
> same time as mon_thousands_sep, but this is not a change in
> behaviour, it is always either a matching value or L'\0',
> but if in the future we change the default to a non-empty
> string we would need to update both at the same time.
>
> Tested on x86_64 and i686 without regressions.
> Tested with install-locale-archive target.
> Tested with install-locale-files target.

Ok.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."