Re: [musl] gettext LC_MESSAGES differences from other libc

[Thorsten Glaser <tg@mirbsd.de>]

(you’ll most likely not get my eMail since you use Googlemail,
which actively works against community development)

Gavin Smith dixit:

>> Back to the LANGUAGE environment variable. The problem is that here we
>> have the layers (A) and (C), but (B) is missing. The solution ought to
>> be to introduce a layer (B) for LANGUAGE.

But isn’t $LANGUAGE a mostly annoying (I know I have to unset it
in my scripts to make them work on GNU systems all the time) GNU
extension?

>musl supports setting LC_MESSAGES to an arbitrary value that is not
>a locale, so can access arbitrary translation files in a different way.
>However, we didn't think it was worth having a special case in the code
>just for musl:

I’d reconsider that decision instead.

(Not a musl developer, just lurking.)

bye,
//mirabilos
-- 
Yay for having to rewrite other people's Bash scripts because bash
suddenly stopped supporting the bash extensions they make use of
	-- Tonnerre Lombard in #nosec