Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
(pathname (string #\U042E))
Cannot coerce string Ю to a base-string.
On a related note, (directory "directory-with-utf8-filenames") produces misencoded pathnames. Perhaps there should be some way to control the external-format used for file-system queries.
You seem to have CSS turned off.
Please don't fill out this field.
Juan Jose Garcia Ripoll
Right now ECL does not support UTF8 pathnames and it is not likely to do so in the short term. This is a nontrivial change in the handling of the C library and not very much portable.
Not only are the various operating systems behaving differently here, but the various file systems also do.
A reason why UTF-8 might make some sense in the future would be its compatibility with C strings, though; passing pure bytes to the OS is problematic (libc open(2) and fopen(2) for instance assume NUL terminated strings), so we can't really support a generic external-format like for file contents and stream transfers and pass actual bytes to the OS...
For reference, users needing unicode characters in file names should look at this thread which includes a workaround:
Does http://comments.gmane.org/gmane.lisp.ecl.general/10405 help?