From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/11037 Path: news.gmane.org!.POSTED!not-for-mail From: He X Newsgroups: gmane.linux.lib.musl.general Subject: Re: Re: a bug in bindtextdomain() and strip '.UTF-8' Date: Mon, 13 Feb 2017 22:12:13 +0800 Message-ID: References: <20170129155507.GK1533@brightrain.aerifal.cx> <20170129163329.GL1533@brightrain.aerifal.cx> <20170208143147.GY1533@brightrain.aerifal.cx> <20170211023610.GA1520@brightrain.aerifal.cx> <20170212023422.GE1520@brightrain.aerifal.cx> <20170213132816.GG1520@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c123458ee4ff905486a09fa X-Trace: blaine.gmane.org 1486995167 21665 195.159.176.226 (13 Feb 2017 14:12:47 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 13 Feb 2017 14:12:47 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-11052-gllmg-musl=m.gmane.org@lists.openwall.com Mon Feb 13 15:12:43 2017 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1cdHMx-0005KP-DY for gllmg-musl@m.gmane.org; Mon, 13 Feb 2017 15:12:43 +0100 Original-Received: (qmail 15980 invoked by uid 550); 13 Feb 2017 14:12:46 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 15962 invoked from network); 13 Feb 2017 14:12:46 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=sS4MMf2YhE3or/M4Zavvh1p2JChfTS9GcOPtKLND5as=; b=ho5KplF+/QjejNjyKL2NR9f9HScBL0FkVQsmkQsiL+aXkyGi0Ca678VgaopgsR+dnS 84fVWTZ0L6QrGcnshvFvKmC8QVcFQUjUWdMCKeJL1mcVgnEqPMONhb1VjK+pN+WslQqJ cErZdxGkp/jZHuyJs4S85q0pS+scvKPFv5v2/bTihygok/uY1xIktQnoO3aHBOCacN85 Skr5yEEfo6fs6Dl8o7w8AbYVLwGUYin3UvpviuonAsj+hWFuifr1Gt4UdLMn6ULWdFcP HQtNGIZhZgazCaKLEj+7fF4pDCK/QaAilfdan2bssNcG4t0GhCkGa0J6Euviv5HvgU+F eAfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=sS4MMf2YhE3or/M4Zavvh1p2JChfTS9GcOPtKLND5as=; b=WwyHtLwBALxwO75Hvq4Dj6OrLsMGdyx4enqPsW+jKPeVMfxckerHToSwGrtqyrkLBr HlpPbBz7pHiw0sJPppyXL3Ks4RVxiND9vxDSbFnqwMgjBnx9eSqY4ML8hiN190odr/hY 474qDjq/gLhXs9ua3Nk8pFadIPQBoFMGfbvlZc8bWa2l/35SV8XeEDObaDIaOqG2p4Uu nNgfuebM1FycVZsMaKZx1jo4+SNebcNOhV4VpHIkNK+T0djZjDJa+1KDafQA5LsffTeh sHm55zwocA8hxvue1QEbJGaEbXeIykRL8THGi6vzpk0OMTbNlZG6zQcUD1lSoylYH/Sz I6Qg== X-Gm-Message-State: AMke39m9rqxzhAzgs94JktK+dhERDqobioPWROC+zWc0nXuX533IlmKTuoPNoV6i7qaupzG7VbjHTbRCzGG82g== X-Received: by 10.159.39.199 with SMTP id b65mr10080454uab.3.1486995153890; Mon, 13 Feb 2017 06:12:33 -0800 (PST) In-Reply-To: <20170213132816.GG1520@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:11037 Archived-At: --94eb2c123458ee4ff905486a09fa Content-Type: text/plain; charset=UTF-8 I dont know how, but it's indeed GBK, even with musl, vim indeed generated GBK set files, maybe it's because im using gnu gettext(without-included-gettext). I think we should avoid this issue depending on a check of libc, rather than assuming all .mo files are UTF-8 set. 2017-02-13 21:28 GMT+08:00 Rich Felker : > On Mon, Feb 13, 2017 at 04:01:31PM +0800, He X wrote: > > New find, as you can see, zh_CN is different from zh_CN.UTF-8, it's GBK > > codeset, we can't strip .UTF-8 easily, or we will get a lot of junk: > > That's on glibc; your "finding" is irrelevant to musl, where the > encoding for all locales is UTF-8. > > Rich > --94eb2c123458ee4ff905486a09fa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I dont know how, but it's indeed GBK, even with musl, = vim indeed generated GBK set files, maybe it's because im using gnu get= text(without-included-gettext). I think we should avoid this issue dependin= g on a check of libc, rather than=C2=A0assuming all .mo files are UTF-8 set= .

2017-02-13= 21:28 GMT+08:00 Rich Felker <dalias@libc.org>:
On Mon, Feb 13, 2017 at 04:01:31PM +08= 00, He X wrote:
> New find, as you can see, zh_CN is different from zh_CN.UTF-8, it'= s GBK
> codeset, we can't strip .UTF-8 easily, or we will get a lot of jun= k:

That's on glibc; your "finding" is irrelevant to musl,= where the
encoding for all locales is UTF-8.

Rich

--94eb2c123458ee4ff905486a09fa--