From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, brakjoller@gmail.com
Subject: Re: [brakjoller@gmail.com: setting utf-16 as file-name-coding-system locks up emacs]
Date: Fri, 13 Aug 2004 10:46:35 +0900 (JST) [thread overview]
Message-ID: <200408130146.KAA19518@etlken.m17n.org> (raw)
In-Reply-To: <411B631E.4050006@gnu.org> (message from Jason Rumney on Thu, 12 Aug 2004 13:31:26 +0100)
In article <411B631E.4050006@gnu.org>, Jason Rumney <jasonr@gnu.org> writes:
> Part of this discussion has occured off list, so you may not have seen
> my previous mail on this.
> Currently Emacs uses the standard C library functions for file I/O on
> all platforms. In my judgement, changing this would be too much work to
> take on during feature-freeze, especially since it is complicated by the
> fact that the full Unicode API is not supported on all versions of Windows.
Of course, I agree that we shouldn't change the current
behaviour now. I was talking about what to do in
emacs-unicode.
> In future when this is implemented, I do not see the need for
> "windows-file-name" coding-system. In the versions of Windows where the
> Unicode API is fully supported, there is no need for
> file-name-coding-system, since it is known to be
> utf-16-le-with-signature. In the cases where those APIs are not
> supported, then file-name-coding-system should be used with the standard
> C library as now.
Ok, I see.
---
Ken'ichi HANDA
handa@m17n.org
prev parent reply other threads:[~2004-08-13 1:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1BtYdG-0004bH-IO@fencepost.gnu.org>
[not found] ` <200408091228.VAA10104@etlken.m17n.org>
[not found] ` <c99f54dd0408091315edacc8d@mail.gmail.com>
[not found] ` <200408100133.KAA11854@etlken.m17n.org>
[not found] ` <c99f54dd0408100341410de4d5@mail.gmail.com>
[not found] ` <200408101058.TAA12976@etlken.m17n.org>
[not found] ` <c99f54dd040810043627699b54@mail.gmail.com>
[not found] ` <200408101144.UAA13100@etlken.m17n.org>
2004-08-10 12:01 ` [brakjoller@gmail.com: setting utf-16 as file-name-coding-system locks up emacs] Jason Rumney
2004-08-10 16:49 ` Mattis
2004-08-10 17:15 ` Stefan Monnier
2004-08-11 10:59 ` Mattis
2004-08-11 14:57 ` Stefan Monnier
2004-08-12 8:22 ` Mattis
2004-08-12 11:00 ` Jason Rumney
2004-08-12 11:36 ` Kenichi Handa
2004-08-12 12:31 ` Jason Rumney
2004-08-13 1:46 ` Kenichi Handa [this message]
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200408130146.KAA19518@etlken.m17n.org \
--to=handa@m17n.org \
--cc=brakjoller@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).