unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: Filename encoding
Date: Wed, 15 Jan 2014 16:34:26 -0500	[thread overview]
Message-ID: <87mwixrkt9.fsf@netris.org> (raw)
In-Reply-To: <834n553w64.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 15 Jan 2014 21:02:59 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Mark H Weaver <mhw@netris.org>
>> Date: Wed, 15 Jan 2014 13:14:39 -0500
>> Cc: guile-user@gnu.org
>> 
>> My hope is that this will become less of an issue over time, as systems
>> increasingly standardize on UTF-8.  I see no other good solution.
>> 
>> Thoughts?
>
> MS-Windows filesystems will not standardize on UTF-8 in any observable
> future.

Well, I understand that MS has standardized on UTF-16 (right?) but what
matters from Guile's perspective is the encoding used by the POSIX-style
interfaces that Guile uses, such as 'open'.  Do you know what encoding
that is on Windows?

> Likewise, in some Far Eastern cultures, non-UTF encoding are still
> widely used.

*nod*

> An "other good solution" is to decode file names into Unicode based
> representation (which can be UTF-8) for internal handling, then encode
> them back into the locale-specific encoding when passing them to
> system calls and library functions that receive file names.  This is
> what Emacs does.

That's what Guile does too.  Internally, all strings are Unicode.  At
present we use either Latin-1 or UTF-32, but I intend to change the
internal representation to UTF-8 at some point.

   Thanks,
     Mark



  reply	other threads:[~2014-01-15 21:34 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 [this message]
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
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=87mwixrkt9.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=eliz@gnu.org \
    --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).