unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Chris Vine <chris@cvine.freeserve.co.uk>
Cc: guile-user@gnu.org
Subject: Re: Filename encoding
Date: Wed, 15 Jan 2014 23:00:18 +0200	[thread overview]
Message-ID: <83sisp2c65.fsf@gnu.org> (raw)
In-Reply-To: <20140115195051.3272023c@bother.homenet>

> Date: Wed, 15 Jan 2014 19:50:51 +0000
> From: Chris Vine <chris@cvine.freeserve.co.uk>
> Cc: guile-user@gnu.org
> 
> POSIX system calls are encoding agnostic.  The filename is just a series
> of bytes terminating with a NUL character.  All guile needs to know is
> what encoding the person creating the filesystem has adopted in naming
> files and which it needs to map to.

This doesn't work well, because you cannot easily take apart and
construct file names in encoding-agnostic ways.  For example, some
multibyte sequence in an arbitrary encoding could include the '/' or
'\' characters, so searching for directory separators could fail,
unless you use multibyte-aware string functions (which is a nuisance,
because these functions only support a single locale at a time).

So I think using UTF-8 internally is a much better way.



  reply	other threads:[~2014-01-15 21:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 12:52 Filename encoding Chris Vine
2014-01-15 18:14 ` Mark H Weaver
2014-01-15 19:02   ` Eli Zaretskii
2014-01-15 21:34     ` Mark H Weaver
2014-01-16  3:46       ` Eli Zaretskii
2014-01-15 19:50   ` Chris Vine
2014-01-15 21:00     ` Eli Zaretskii [this message]
2014-01-15 21:42       ` Chris Vine
2014-01-16  3:52         ` Eli Zaretskii
2014-01-15 21:47     ` Mark H Weaver
2014-01-15 22:32       ` Chris Vine
2014-01-16  3:55       ` Eli Zaretskii
2014-01-15 23:29     ` Ludovic Courtès
2014-01-16  4:00       ` Eli Zaretskii
2014-01-16 13:03         ` Ludovic Courtès
2014-01-16 14:07           ` John Darrington
2014-01-16 16:12             ` Eli Zaretskii
2014-01-16 16:09           ` Eli Zaretskii
2014-01-16 15:36         ` Mark H Weaver

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83sisp2c65.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=chris@cvine.freeserve.co.uk \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).