From: Harald Hanche-Olsen <hanche@ma...> - 2006-02-05 23:14:12
Seems that the pathname code won't handle non-ASCII filenames anymore,
since the unicode support was added - since all pathnames are supposed
to be SIMPLE-STRINGs. For example, typing #p"Würzburg" produces an
error, and DIRECTORY fails if pointed at a directory which contains a
file with such a name.
This arose on c.l.lisp; I am just mentioning it here so knowledgeable
beings can discuss any remedies.
I might add that there probably are at least two kinds of filesystems
out there: One where filenames use some 8-bit character set, possibly
not even properly specified by the OS vendor (most unixes?) and one
where filenames are encoded as UTF-8. The latter happens on MacOS X,
and seems to be enforced by the filesystem. Both behaviours need to
Get latest updates about Open Source Projects, Conferences and News.