Re: Call for consensus - I18N issues in process/guide doc

Masataka Ohta <[email protected]> Tue, 18 Mar 97 18:22:17 JST
Newsgroups gmane.ietf.url
Message-ID <[email protected]>
Edward;

> >> Does this mean we have consensus?
> >
> >No.
> >
> >How can you uniquely encode a German letter 'A' with umlaut in UTF-8?
> >
> >A single "character" of 'A with diaeresis' or two "character" sequences
> >of 'A' and "combining mark of diaeresis"?
> 
> Can you say "equivalence class"? How about "normal form"?

OK. We can agree that ISO 2022 based encoding is perfectly fine
with "equvalence class" and "normal form".

> >Note that my sentence is confusing becasue the definition of "character" in
> >ISO 10646/UTF-8 is broken and confusing.

> On the contrary, we do have consensus.

No. The confusion is your problem.

> Much of what you say appears to come from misunderstandings of this type in
> *both* directions due to such differences. You say that
> 
> U+00C4          LATIN CAPITAL LETTER A WITH DIAERESIS
> 
> and
> 
> U+0041 0308     LATIN CAPITAL LETTER A, COMBINING DIAERESIS
> 
> are not the same

No. I say "a German letter 'A' with umlaut". Or, I can say
"a German character 'A' with umlaut".

							Masataka Ohta