From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21407 invoked by alias); 17 Nov 2013 04:58:12 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 31994 Received: (qmail 12992 invoked from network); 17 Nov 2013 04:57:57 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-100.6 required=5.0 tests=BAYES_00, RCVD_IN_BL_SPAMCOP_NET,USER_IN_WHITELIST autolearn=no version=3.3.2 Resent-From: Geoff Wing Resent-Date: Sun, 17 Nov 2013 15:57:57 +1100 Resent-Message-ID: <20131117045757.GA27929@primenet.com.au> Resent-To: zsh-workers@zsh.org X-Biglobe-Sender: Content-Type: text/plain; charset=iso-2022-jp Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: Util/helpfiles and locale From: "Jun T." In-Reply-To: <131112224807.ZM10883@torch.brasslantern.com> Date: Thu, 14 Nov 2013 12:08:59 +0900 Content-Transfer-Encoding: quoted-printable Message-Id: References: <131112224807.ZM10883@torch.brasslantern.com> To: "zsh-workers@zsh.org" X-Mailer: Apple Mail (2.1510) On 2013/11/13, at 15:48, Bart Schaefer = wrote: > On my Ubuntu box it chooses en_AG.utf8 even though the default locale = is > set to en_US.utf8. On my somewhat older CentOS host it chooses = en_AU.utf8. >=20 > Does it really not matter which of these is used? I tested (on Fedora 17) several locales for building help docs by, e.g., $ lc_ctype=3D'-fja_JP.utf8' make runhelp and found that the only difference is the character used by colcrt for hyphenation (split a word at the end of a line): '=1B$B!>=1B(B' (Unicode: U+2010, UTF-8: E2 80 90) if any of UTF-8 = locales is used, '-' (ASCII minus, 0x2D) if C locale is used (lc_ctype=3D'-fC'), and a two-byte code 0xA1 0xBE if ja_JP.eucjp is used. ('=1B$B!>=1B(B' and '-' may look almost identical with some = fonts) Obviously EUC encoding must be avoided, but I feel using UTF-8 encoding = may not be the best way, if we must consider the possibility that the = machine on which a user views the docs is different from the host on which the = docs are built, and the user's OS (or terminal) doesn't support UTF-8. If the zsh document sources (the .yo files) are pure ASCII (I guess they = are, and I guess yodl doesn't support UTF-8), then always using the C locale when building the run-help docs would be the best and simplest way. On 2013/11/10, at 17:57, Martin Vaeth = wrote: > 2. It does not work out-of-the box: With current man/groff versions, > one must export (an empty) GROFF_NO_SGR, MANWIDTH=3D80, possibly > unset MANPL, MANROFFSEQ, set utf8-aware locales etc. Are you sure utf8-aware locale is necessary? Did you try LC_CTYPE=3DC on = your Gentoo box?