all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Nils Gösche" <cartan@cartan.de>
Cc: 12807@debbugs.gnu.org
Subject: bug#12807: AW: bug#12807: 24.2; Emacs cannot edit file with funny Unicode characters in the file name	on Windows
Date: Tue, 06 Nov 2012 05:57:45 +0200	[thread overview]
Message-ID: <83lief2xja.fsf@gnu.org> (raw)
In-Reply-To: <001601cdbba1$bc4cf020$34e6d060$@de>

> From: Nils Gösche <cartan@cartan.de>
> Cc: <12807@debbugs.gnu.org>
> Date: Mon, 5 Nov 2012 23:05:57 +0100
> 
> > Yes, but the Explorer and the Notepad are about the only programs that
> > do.  Many others don't.  Emacs is one of them.
> 
> »About the only« is a bit of an exaggeration ;-)  Anything that is written
> in C# or Java shouldn't have that problem; or Common Lisp, come to think of
> it. But yeah, back in the old days, pretty much nobody felt like using
> wchar_t instead of char everywhere in C. I didn't, either, back then. (Not
> to mention that in the really old days, wchar_t didn't even exist ;-)

Using wchar_t is not going to solve the whole problem, unfortunately.
The problem is that the mainline Emacs code uses APIs that don't
accept wide characters.  Examples include 'stat', 'access', 'open',
'fopen', etc.  To fix the problem, we'd need to provide our own
implementation of these APIs that would accept a UTF-8 encoded file
name, then re-encode the file name in UTF-16, and call the Unicode
APIs as part of the implementation.  This is a large job.






      reply	other threads:[~2012-11-06  3:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 20:52 bug#12807: 24.2; Emacs cannot edit file with funny Unicode characters in the file name on Windows Nils Gösche
2012-11-05 21:47 ` Eli Zaretskii
2012-11-05 22:05   ` bug#12807: AW: " Nils Gösche
2012-11-06  3:57     ` Eli Zaretskii [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

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

  git send-email \
    --in-reply-to=83lief2xja.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=12807@debbugs.gnu.org \
    --cc=cartan@cartan.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.