Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: multibyte FAQ (MacOS X)
- X-seq: zsh-workers 22093
- From: Andrey Borzenkov <arvidjaar@xxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: PATCH: multibyte FAQ (MacOS X)
- Date: Sun, 18 Dec 2005 18:26:12 +0300
- Cc: "Jun T." <takimoto-j@xxxxxxxxxxxxxxxxx>
- In-reply-to: <a06001000bfcb1deaed2f@xxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <200512141831.jBEIV3qQ028002@xxxxxxxxxxxxxx> <a06001000bfcb1deaed2f@xxxxxxxxxxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 18 December 2005 17:14, Jun T. wrote:
> In MacOS X, configure does not enable multibyte by default, because
> __STDC_ISO_10646__ is not defined. So "./configure; make" gives a zsh
> without multibyte support, although it supports "\u....".
[...]
> (2) In MacOS X, the standard file system is HFS+ which stores filenames in
> Unicode but in fully decomposed form. This means the filename returned by
> the completion is also in decomposed form; the filename is displayed
> correctly, but it can't be edited correctly. And if I go up/down in the
> history stack the prompt is destroyed.
>
I wonder, when decomposition happens? I.e. consider a program that takes file
name as parameter and compares it with result of readdir? Or even worse, it
reads it from stdin or file?
To be sure - do you mean that e.g. accented characters are internally kept as
two characters? Does it agree with <http://www.unicode.org/reports/tr15/>?
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDpX+dR6LMutpd94wRAsXsAKDHBAOweRBjjSKqKRhfTyEKM6sa6QCfdN8v
xiqrixpfro2fHjHwSMAZo5g=
=igh5
-----END PGP SIGNATURE-----
Messages sorted by:
Reverse Date,
Date,
Thread,
Author