From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: kzhr@d1.dion.ne.jp, michael.albinus@gmx.de, emacs-devel@gnu.org
Subject: Re: Multibyte and unibyte file names
Date: Wed, 23 Jan 2013 15:38:51 -0800 [thread overview]
Message-ID: <5100748B.80502@cs.ucla.edu> (raw)
In-Reply-To: <83bocfn2k1.fsf@gnu.org>
On 01/23/13 11:04, Eli Zaretskii wrote:
> encoding a file name,
> then removing its last "slash" as above, then decoding it again will
> yield a wrong or even an invalid string, right?
Yes, the code may be wrong for MS-Windows,
but since the problem can't possibly occur in a POSIXish
system, the code is correct as-is on POSIX. It's correct to
always treat a '/' byte as a directory separator, no matter what
the file name coding system is. This is de facto true already,
and as I understand it the next version of POSIX will require this
to be true for all encodings. Similarly, the next POSIX will
guarantee that '.' always stands for itself, in any encoding.
next prev parent reply other threads:[~2013-01-23 23:38 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 17:45 Multibyte and unibyte file names Eli Zaretskii
2013-01-23 18:08 ` Paul Eggert
2013-01-23 19:04 ` Eli Zaretskii
2013-01-23 23:38 ` Paul Eggert [this message]
2013-01-23 19:42 ` Michael Albinus
2013-01-23 20:05 ` Eli Zaretskii
2013-01-23 20:58 ` Michael Albinus
2013-01-24 16:37 ` Eli Zaretskii
2013-01-23 21:09 ` Stefan Monnier
2013-01-24 17:02 ` Eli Zaretskii
2013-01-24 18:25 ` Stefan Monnier
2013-01-24 18:38 ` Eli Zaretskii
2013-01-25 0:06 ` Stefan Monnier
2013-01-25 7:37 ` Eli Zaretskii
2013-01-25 11:36 ` Stefan Monnier
2013-01-25 20:31 ` Eli Zaretskii
2013-01-25 22:28 ` Stefan Monnier
2013-01-26 10:54 ` Eli Zaretskii
2013-01-26 11:34 ` Stefan Monnier
2013-01-26 13:16 ` Eli Zaretskii
2013-01-26 22:11 ` Stefan Monnier
2013-01-27 7:03 ` Eli Zaretskii
2013-01-27 8:46 ` Andreas Schwab
2013-01-27 9:40 ` Eli Zaretskii
2013-01-28 1:55 ` Stefan Monnier
2013-01-28 14:44 ` Eli Zaretskii
2013-01-28 15:21 ` Stefan Monnier
2013-02-02 17:19 ` Eli Zaretskii
2013-01-26 13:20 ` Stephen J. Turnbull
2013-01-26 3:04 ` Stephen J. Turnbull
2013-01-26 11:27 ` Eli Zaretskii
2013-01-26 13:03 ` Stephen J. Turnbull
2013-01-26 13:36 ` Eli Zaretskii
2013-01-26 16:26 ` Paul Eggert
2013-01-26 18:30 ` Stephen J. Turnbull
2013-01-26 17:10 ` Stephen J. Turnbull
2013-01-26 17:33 ` Eli Zaretskii
2013-01-26 18:06 ` Paul Eggert
2013-01-26 18:20 ` Eli Zaretskii
2013-01-26 18:56 ` Stephen J. Turnbull
2013-01-26 21:40 ` Stefan Monnier
2013-01-26 21:44 ` Stefan Monnier
2013-01-27 6:14 ` Eli Zaretskii
2013-01-26 16:05 ` Richard Stallman
2013-01-26 17:57 ` Stephen J. Turnbull
2013-01-26 22:16 ` Stefan Monnier
2013-01-24 10:00 ` Michael Albinus
2013-01-24 16:40 ` Eli Zaretskii
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=5100748B.80502@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kzhr@d1.dion.ne.jp \
--cc=michael.albinus@gmx.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 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).