Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: PATCH: multibyte FAQ (MacOS X)

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
Version: GnuPG v1.4.2 (GNU/Linux)


Messages sorted by: Reverse Date, Date, Thread, Author