[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170129155507.GK1533@brightrain.aerifal.cx>
Date: Sun, 29 Jan 2017 10:55:07 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Re: a bug in bindtextdomain() and strip '.UTF-8'
On Sun, Jan 29, 2017 at 10:48:34PM +0800, He X wrote:
> 1. agreed with rich, nplurals is important too; compiling the kernel,
> cannot update the patch
> 2. no other ways, musl will use generic config 100%, and then the
> exception, the run time error is hardcoded there; but i doubt if this
> really breaks binaries, the function is only called by libstdc++ itself.
> you cant only update the config, but does not update libstdc++. libstdc++
> exported the same abi for common binaries, wont break most dynamic-loaded
> binary in my view.
>
> btw, with 'p-> to q->', 'strip .UTF-8'(these two in the first thread), and
> these two patches, fcitx, chromium are working well.
>
> but there're some names like 'de_DE@...o', 'zh_CN.GBK', these should be
> stripped, either, any good ideas?
This has all been discussed before; see this email and others in the
thread:
http://www.openwall.com/lists/musl/2016/05/11/8
Masanori Ogino was going to work on some follow-up research, testing,
and/or implementation but didn't get around to it. I'm not aware of
any newer findings that contradict the direction suggested in that
thread.
For your specific examples, de_DE@...o would be searched in de_DE,
de@...o, and finally de; zh_CN.GBK would be invalid (non-UTF-8
encodings not permitted) but it's not clear to me how it should be
handled (rejection or rewriting at setlocale time, stripping .GBK at
translation load time, or leaving .GBK there and letting translation
fail).
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
