From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: File name completion on Mac OS X with German umlauts
Date: Thu, 13 Mar 2008 00:23:29 +0100 [thread overview]
Message-ID: <f7ccd24b0803121623g24810ce1y45a974c7907a887c@mail.gmail.com> (raw)
In-Reply-To: <u63vrk3p1.fsf@gnu.org>
On Wed, Mar 12, 2008 at 10:55 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> In particular, I don't see why file names with "X" and "Ⅹ" are okay
> for you, but the two types of "ü" are not. I think they are both
> exhibiting the same problem.
Well, the first two, U+0058 LATIN CAPITAL LETTER X and U+2169 ROMAN
NUMERAL TEN, are meant to be semantically distinct.
However, U+00FC LATIN SMALL LETTER U WITH DIAERESIS is supposed to be
semantically identical to U+0075 LATIN SMALL LETTER U plus U+0308
COMBINING DIAERESIS. In the first case, we're talking about different
abstract characters represented with different codepoints. In the
second case, we're talking about the same abstract character. Other
than a byte comparison, there is no distinction between both ü. You
wouldn't expect a font supporting Unicode to represent U+00FC
different that U+0075 plus U+0308.
Juanma
next prev parent reply other threads:[~2008-03-12 23:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 11:53 File name completion on Mac OS X with German umlauts Markus
2008-03-09 14:39 ` Peter Dyballa
2008-03-09 15:22 ` Nikolaj Schumacher
[not found] ` <mailman.8596.1205073587.18990.help-gnu-emacs@gnu.org>
2008-03-09 21:44 ` Markus
2008-03-09 23:21 ` Peter Dyballa
[not found] ` <mailman.8623.1205104885.18990.help-gnu-emacs@gnu.org>
2008-03-10 18:57 ` Markus
2008-03-10 21:01 ` Peter Dyballa
[not found] ` <mailman.8673.1205182919.18990.help-gnu-emacs@gnu.org>
2008-03-10 21:25 ` Markus
2008-03-10 22:49 ` Peter Dyballa
[not found] ` <mailman.8682.1205189384.18990.help-gnu-emacs@gnu.org>
2008-03-11 21:24 ` Markus
2008-03-11 22:14 ` Peter Dyballa
[not found] ` <mailman.8727.1205273706.18990.help-gnu-emacs@gnu.org>
2008-03-13 22:11 ` Markus
2008-03-13 23:11 ` Peter Dyballa
[not found] ` <mailman.8870.1205449910.18990.help-gnu-emacs@gnu.org>
2008-03-16 12:51 ` Markus
2008-03-16 14:21 ` Peter Dyballa
[not found] ` <mailman.8598.1205076134.18990.help-gnu-emacs@gnu.org>
2008-03-09 21:47 ` Markus
2008-03-12 15:44 ` Nikolaj Schumacher
2008-03-12 18:46 ` Eli Zaretskii
2008-03-12 21:25 ` Nikolaj Schumacher
2008-03-12 21:55 ` Eli Zaretskii
2008-03-12 23:23 ` Juanma Barranquero [this message]
2008-03-13 4:28 ` Eli Zaretskii
2008-03-13 8:18 ` Juanma Barranquero
2008-03-13 13:49 ` Nikolaj Schumacher
2008-03-13 14:17 ` Juanma Barranquero
2008-03-13 14:18 ` Juanma Barranquero
2008-03-13 20:10 ` Eli Zaretskii
2008-03-13 21:03 ` Juanma Barranquero
[not found] ` <mailman.8859.1205442242.18990.help-gnu-emacs@gnu.org>
2008-03-13 22:09 ` Markus
2008-03-13 23:08 ` Peter Dyballa
[not found] ` <mailman.8794.1205357174.18990.help-gnu-emacs@gnu.org>
2008-03-17 14:07 ` Piet van Oostrum
2008-03-17 16:44 ` Nikolaj Schumacher
2008-03-17 20:24 ` Eli Zaretskii
2008-03-18 18:05 ` Nikolaj Schumacher
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=f7ccd24b0803121623g24810ce1y45a974c7907a887c@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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).