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: Thu, 16 Jan 2014 05:52:09 +0200	[thread overview]
Message-ID: <83k3e037o6.fsf@gnu.org> (raw)
In-Reply-To: <20140115214257.45af1076@bother.homenet>

> Date: Wed, 15 Jan 2014 21:42:57 +0000
> From: Chris Vine <chris@cvine.freeserve.co.uk>
> Cc: mhw@netris.org, guile-user@gnu.org
> 
> I am not sure what you mean, as I am not talking about internal use.

Then I probably didn't understand why you mentioned the external
encoding.  How is that relevant to the issue at hand?

I'm saying that Guile does needs to know how to convert a file name
when it needs to pass it to library functions and system calls.  So
The POSIX system calls may be "encoding agnostic", but Guile simply
cannot be.

> As it happens (although this is beside the point) using a byte value or
> sequence in a filename which the operating system reserves as the '/'
> character, for a purpose other than designating a pathname, or a NUL
> character for designating anything other than end of filename, is not
> POSIX compliant and will not work on any operating system I know of,
> including windows.

Windows is not Posix-compliant, so all bets are off.  As a matter of
fact, there _are_ DBCS codepages where the second byte can be '\'.



  reply	other threads:[~2014-01-16  3:52 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
2014-01-15 21:42       ` Chris Vine
2014-01-16  3:52         ` Eli Zaretskii [this message]
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=83k3e037o6.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).