From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@sunsite.dk
Subject: Re: Echoing of 8-bit-characters broken after 4.3.2 (solved)
Date: Tue, 3 Mar 2009 20:46:43 +0000 [thread overview]
Message-ID: <20090303204643.4d5b4045@pws-pc> (raw)
In-Reply-To: <2493fbfb0903010157of50e9b5q1527e4ff0c639110@mail.gmail.com>
On Sun, 1 Mar 2009 10:57:53 +0100
Wolfgang Hukriede <whukriede@googlemail.com> wrote:
> Now, since this is a silent change under the hood and I cannot believe
> to be the only one to be hurt by it, may I suggest to place a hint
> into the man page (or maybe at least the faq)?
Index: Doc/Zsh/params.yo
===================================================================
RCS file: /cvsroot/zsh/zsh/Doc/Zsh/params.yo,v
retrieving revision 1.51
diff -u -r1.51 params.yo
--- Doc/Zsh/params.yo 6 Feb 2009 09:59:38 -0000 1.51
+++ Doc/Zsh/params.yo 3 Mar 2009 20:44:56 -0000
@@ -906,7 +906,12 @@
vindex(LC_CTYPE)
item(tt(LC_CTYPE) <S>)(
This variable determines the locale category for character handling
-functions.
+functions. If the tt(MULTIBYTE) option is in effect this variable or
+tt(LANG) should contain a value that reflects the character set in
+use, even if it is a single-byte character set, unless only the
+7-bit subset (ASCII) is used. For example, if the character set
+is ISO-8859-1, a suitable value might be tt(en_US.iso88591) (certain
+Linux distributions) or tt(en_US.ISO8859-1) (MacOS).
)
vindex(LC_MESSAGES)
item(tt(LC_MESSAGES) <S>)(
Index: Doc/Zsh/roadmap.yo
===================================================================
RCS file: /cvsroot/zsh/zsh/Doc/Zsh/roadmap.yo,v
retrieving revision 1.11
diff -u -r1.11 roadmap.yo
--- Doc/Zsh/roadmap.yo 14 Apr 2008 12:53:36 -0000 1.11
+++ Doc/Zsh/roadmap.yo 3 Mar 2009 20:44:56 -0000
@@ -50,6 +50,17 @@
There is some discussion of this in the shell FAQ,
http://zsh.dotsrc.org/FAQ/ . Note in particular that for combining
characters to be handled the option tt(COMBINING_CHARS) needs to be set.
+Because the shell is now more sensitive to the definition of the
+character set, note that if you are upgrading from an older version of
+the shell you should ensure that the appropriate variable, either
+tt(LANG) (to affect all aspects of the shell's operation) or
+tt(LC_CTYPE) (to affect only the handling of character sets) is set to
+an appropriate value. This is true even if you are using a
+single-byte character set including extensions of ASCII such as
+tt(ISO-8859-1) or tt(ISO-8859-15). See the description of tt(LC_CTYPE)
+in
+ifnzman(noderef(Parameters))\
+ifzman(zmanref(zshparam)).
subsect(Completion)
--
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/
next prev parent reply other threads:[~2009-03-03 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 9:57 Wolfgang Hukriede
2009-03-03 20:46 ` Peter Stephenson [this message]
2009-03-04 6:28 ` Wolfgang Hukriede
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090303204643.4d5b4045@pws-pc \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).