From: Wolfgang Hukriede <whukriede@ifm.uni-kiel.de>
To: uli@tallowcross.uni-frankfurt.de, pws@ifh.de, zsh-users@math.gatech.edu
Subject: Re: FAQ, German Umlauts
Date: Wed, 25 Jun 1997 22:46:47 +0200 (MET DST) [thread overview]
Message-ID: <199706252046.WAA23971@sally.ifm.uni-kiel.de> (raw)
Hello!
On Wed, 25 Jun 97 18:40:26 +0200 Uli Zappe <uli@tallowcross.uni-frankfurt.de>
wrote:
> while it is great that zsh is able to deal with the lower case
> German letters
>
> d (ae)
> v (oe)
> | (ue) and
> _ (ss)
>
> unfortunately it doesn't do so yet with the capital letters
>
> D (AE)
> V (OE)
> \ (UE)
>
> Does anybody know if this will be fixed in the foreseeable future?
That is, because your (otherwise fabulous) operating-system encodes
Ae as 0205, Oe as 0226, Ue as 0232, which codes are in the range 0200
to 0237. This range does not display anything under the latin-1 encoding.
Now:
On Wed, 25 Jun 1997 15:49:45 +0200 Peter Stephenson <pws@ifh.de> wrote:
> Subject: Z-Shell Frequently Asked Questions (monthly posting)
> Changes since last issue:
>
> 3.6: New question on displaying eight bit characters.
>
> 3.6: How do I make the completion list use eight bit characters?
>
> You are probably creating files with non-ASCII characters, such as
> accented characters, and find they show up in the completion list as
> \M-i or something such. This is because the library routines
> (not zsh itself) which test whether a character is printable have
> replied that it is not; zsh has simply found a way to show them
> anyway.
>
> The answer, under a modern POSIXy operating system, is to find a
> locale where these are treated as printable characters. Zsh has
> handling for locales built in and will recognise when you set a
> relevant variable. You need to look in /usr/lib/locale to find one
> which suits you; the subdirectories correspond to the locale names.
> The simplest possibility is likely to be en_US, so that the simplest
> answer to your problem is to set
>
> LC_CTYPE=en_US
>
> when your terminal is capable of showing eight bit characters. If
> you only have a default domain (called C), you may need to have some
> additional files installed on your system.
Peter, I think you're on the wrong road here. The locale settings cannot
change hardware-properties, can they?
Why don't you just pass through all 8-bit-encodings, or possibly add (yet
another) zsh-option, which at least allows this. You simply cannot tell
something about the users hardware. Even if you get everything right so far,
when say, someone changes his/her terminal font or encoding vector, it's
immediately broken again. If at all, these settings belong under complete
user-control. You're asking way too much from the locale system here.
Wolfgang.
next reply other threads:[~1997-06-25 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-06-25 20:46 Wolfgang Hukriede [this message]
1997-06-26 8:00 ` Peter Stephenson
1997-06-26 12:01 ` Uli Zappe
1997-06-26 13:38 ` Peter Stephenson
1997-06-26 15:43 ` Uli Zappe
1997-06-26 21:43 ` Zefram
1997-06-26 23:01 ` Uli Zappe
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=199706252046.WAA23971@sally.ifm.uni-kiel.de \
--to=whukriede@ifm.uni-kiel.de \
--cc=pws@ifh.de \
--cc=uli@tallowcross.uni-frankfurt.de \
--cc=zsh-users@math.gatech.edu \
/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).