From: Thomas Klausner <wiz@NetBSD.org>
To: discuss@mdocml.bsd.lv
Subject: Re: distinct character, same glyph in Unicode
Date: Thu, 17 Mar 2011 23:00:33 +0100 [thread overview]
Message-ID: <20110317220033.GB22396@danbala.tuwien.ac.at> (raw)
In-Reply-To: <20110317190150.GA29893@iris.usta.de>
On Thu, Mar 17, 2011 at 08:01:50PM +0100, Ingo Schwarze wrote:
> Thus, the French ":o" (o diaeresis) - note that the Grand Robert
> explicitely lists this one as occurring in natively French words -
> is clearly not the same character as the German ":o" (o umlaut).
> Due to the limited number of characters in ISO-latin-1, i'm not
> surprised that this distinction was blurred - however, do you know
> why there is apparently no distinction in Unicode either?
> All sources i can find recommend using the "diaeresis" class of
> characters for German umlauts.
Sometimes, there's a need to distinguish between the umlaut sign and
the diaeresis sign. In these cases, the following recommendation by
ISO/IEC JTC 1/SC 2/WG 2 should be followed:
* To represent the umlaut use Combining Diaeresis (U+0308)
* To represent the diaeresis use Combining Grapheme Joiner (CGJ,
U+034F) + Combining Diaeresis (U+0308)
From http://en.wikipedia.org/wiki/Umlaut_%28diacritic%29 and
originally http://unicode.org/faq/char_combmark.html#18
Thomas
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2011-03-17 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110316211219.GA15999@harkle.bramka>
[not found] ` <20110316222835.GB15999@harkle.bramka>
[not found] ` <20110316223702.GB12736@iris.usta.de>
[not found] ` <20110317000813.GC15999@harkle.bramka>
[not found] ` <20110317012423.GE12736@iris.usta.de>
2011-03-17 19:01 ` Ingo Schwarze
2011-03-17 22:00 ` Thomas Klausner [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=20110317220033.GB22396@danbala.tuwien.ac.at \
--to=wiz@netbsd.org \
--cc=discuss@mdocml.bsd.lv \
/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 NNTP newsgroup(s).