From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23555 invoked from network); 26 Jun 1997 15:59:56 -0000 Received: from euclid.skiles.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 26 Jun 1997 15:59:56 -0000 Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id LAA07016; Thu, 26 Jun 1997 11:51:59 -0400 (EDT) Resent-Date: Thu, 26 Jun 1997 11:51:06 -0400 (EDT) Message-Id: <9706261543.AA03628@tallowcross.uni-frankfurt.de> Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) In-Reply-To: <199706261338.PAA18046@sgi.ifh.de> X-Nextstep-Mailer: Mail 3.3 (Enhance 1.3) From: Uli Zappe Date: Thu, 26 Jun 97 17:43:17 +0200 To: Peter Stephenson , zsh-users@math.gatech.edu (Zsh users list) Subject: Re: FAQ, German Umlauts References: <199706261338.PAA18046@sgi.ifh.de> Resent-Message-ID: <"ixAyw2.0.ii1.g_eip"@euclid> Resent-From: zsh-users@math.gatech.edu X-Mailing-List: archive/latest/916 X-Loop: zsh-users@math.gatech.edu X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Peter Stephenson wrote: > The locale business is the standard way of telling the system > what is a character and what isn't (and all sorts of similar > things). [...] > It sounds like NEXTSTEP doesn't have that. Try looking in the > `ctype' manual page to see if there is anything corresponding to > it I did: No, there isn't. I.e. actually there is an *object class* for that purpose, but obviously zsh doesn't make use of *that*. > Zsh doesn't even decide; the system does and it seems to be > getting it wrong. But zsh is the *only* program with this problem on NEXTSTEP; so it can't be as simple as "zsh is right, but NEXTSTEP is wrong"... :-( perl, for instance, works perfectly well. > The old zsh, so far as I remember, didn't even have the locale > mechanism, so is unlikely to be able to do non-ASCII characters. > Even a reasonable attempt at 8-bit characters is fairly new. zsh 2.51 *can* deal perfectly with lower case Umlauts, as I said before. > To clarify, zsh doesn't need the locale system > either, it just supports it if it is available. Does this locale system consist of only the file /usr/lib/locale (so that I simply could install such a file), or is there a corresponding program that's necessary? > The alternative is Wolfgang Hukriede's suggestion of passing > through all characters. That's dangerous in general, so it would > have to be an option. Maybe it's not necessary to really pass thru *all* characters; I can't judge, though. Anyway, what do I have to do to make this option being implemented in future versions of zsh? Bye Uli _____________________________________________________________________ Uli Zappe E-Mail: uli@tallowcross.uni-frankfurt.de (NeXTMail,Mime,ASCII) PGP on request Lorscher Strasse 5 WWW: - D-60489 Frankfurt Fon: +49 (69) 9784 0007 Germany Fax: +49 (69) 9784 0042 staff member of NEXTTOYOU - the German NEXTSTEP/OPENSTEP magazine _____________________________________________________________________