From: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org, brakjoller@gmail.com
Subject: Re: [brakjoller@gmail.com: setting utf-16 as file-name-coding-system locks up emacs]
Date: Tue, 10 Aug 2004 13:01:17 +0100 [thread overview]
Message-ID: <4118B90D.9060007@gnu.org> (raw)
In-Reply-To: <200408101144.UAA13100@etlken.m17n.org>
[-- Attachment #1.1: Type: text/plain, Size: 1730 bytes --]
Kenichi Handa wrote:
>In article <c99f54dd040810043627699b54@mail.gmail.com>, Mattis <brakjoller@gmail.com> writes:
>
>
>
>>> Are they real question marks? Have you checked them with
>>> "C-x ="?
>>>
>>>
>>Yes, they are real question marks.
>>
>>
>
>Hmmm, then something is different in Windows port.
>
>
>>I do not know how to proceed. It definitely seems like the low level
>>emacs functions do not support all characters under Windows. Is this
>>considered a bug or a non-feature?
>>
>>
>
>I have no idea because I have almost no knowledge about
>Windows. Jason, do you know why
>
>
>
The functions that deal with file names in the C library on Windows
return ? for characters that are not supported by the system locale,
even though NTFS supports Unicode file names. The answer would be to use
Unicode-aware Win32 API functions instead of the standard C library, but
such functions are only supported on some versions of Windows, so
determining when to use them and when not to is a problem.
It is quite unusual for users to enter filenames in languages other than
their own, and Emacs is certainly not the only application that has this
problem (try "dir" in the windows command prompt for example), so this
has not been high priority. It is probably appropriate to look at this
in the next version of Emacs that uses Unicode internally. To do so now
is too big a change for feature-freeze, I think and we already have a
big change to support Unicode on the clipboard to install (which has
more benefits to users than file names IMHO).
>(let ((file-name-coding-system 'raw-text))
> (directory-files DIRECTORY_NAME))
>
>returns `?' in file names if they are encoded in utf-16-le?
>
>
[-- Attachment #1.2: Type: text/html, Size: 2616 bytes --]
[-- Attachment #2: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next parent reply other threads:[~2004-08-10 12:01 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 ` Jason Rumney [this message]
2004-08-10 16:49 ` Re: [brakjoller@gmail.com: setting utf-16 as file-name-coding-system locks up emacs] 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
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=4118B90D.9060007@gnu.org \
--to=jasonr@gnu.org \
--cc=brakjoller@gmail.com \
--cc=emacs-devel@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.
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).