Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: German Umlauts still don't work
- X-seq: zsh-workers 3341
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Uli Zappe <uli@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: German Umlauts still don't work
- Date: Wed, 2 Jul 1997 21:01:03 -0700
- In-reply-to: <9707030152.AA15017@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- References: <19742.199706262142@xxxxxxxxxxxxxxxxxxxxxxx> <9707030152.AA15017@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
On Jul 3, 3:52am, Uli Zappe wrote:
} Subject: German Umlauts still don't work
}
} the German Umlaut problem I brought up a few days ago is more
} difficult to solve than expected.
}
} Peter Stephenson suggested to patch utils.c which is the only
} source file in zsh making use of isprint(c) which delivers incorrect
} results for NEXTSTEP.
I presume you also did `setopt PRINTEIGHTBIT` after applying that patch?
Just checking ...
} I tried that, but it didn't change a thing. Obviously there is
} another part of the zsh source that's limiting zsh's behaviour; it's
} definitely *not* the isprint(c) part (which would be easy to
} replace by the correct NXIsPrint(c) for the NEXTSTEP version, BTW).
Is the symptom that the characters display as \M-a, or simply that they
lose the umlauts? What's your `stty -a` output?
} Does anyone have an idea where to look?
With some grepping, I can't find any output of file names that doesn't
pass through the right functions, except fprintdir() which seems to always
output the raw string (so it can't be accidentally \M-ifying it).
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author