Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#237 Can't have a pathname with a non-base-string name.

HEAD
accepted
nobody
1
2014-09-23
2012-12-20
stassats
No

(pathname (string #\U042E))

Cannot coerce string Ю to a base-string.

Discussion

  • stassats
    stassats
    2012-12-20

    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.

     
  • 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.

     

  • Anonymous
    2013-01-13

    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...

     

  • Anonymous
    2013-06-11

    For reference, users needing unicode characters in file names should look at this thread which includes a workaround:
    http://www.mail-archive.com/ecls-list@lists.sourceforge.net/msg02624.html

     
  • Arto Bendiken
    Arto Bendiken
    2014-09-23

    • labels: --> pathname, utf-8
    • status: open --> accepted
    • Release: Unstable_git-CVS --> HEAD
     


Anonymous


Cancel   Add attachments