W3C home > Mailing lists > Public > public-i18n-core@w3.org > January to March 2005

RE: feedback on Char Model

From: Richard Ishida <ishida@w3.org>
Date: Fri, 4 Feb 2005 10:17:57 -0000
To: <kuro@bhlab.com>
Cc: <public-i18n-core@w3.org>
Message-Id: <20050204101757.D90314F408@homer.w3.org>

Hello Kuro-san,

Thankyou for your comment below.  We discussed this during a teleconference
[1] on the 20th Jan and concluded that your interpretation is indeed
correct, but that your rewrite contains errors.  The opinion of the group
was that we should leave the text as it is.

But thankyou anyway for taking the time to draw this to our attention.



Richard Ishida

contact info:

W3C Internationalization:

Publication blog:

> -----Original Message-----
> From: i18n-editor-request@w3.org 
> [mailto:i18n-editor-request@w3.org] On Behalf Of Richard Ishida
> Sent: 10 January 2005 16:47
> To: 'Editor'
> Subject: FW: feedback on Char Model
> (Edited) comment from Kurosaka-san.
> [[
> Here's the part of Char Model that I felt a little bit misleading.
> In
> http://www.w3.org/TR/charmod/#sec-RefProcModel
> C078 reads:
>   Specifications MUST NOT allow the use of surrogate code points.
> My interpretation of it is that the spec should no allow the 
> Unicode surrogate code points as a character by its own 
> right.  It is not the intention to forbid use of surrogate 
> pairs in UTF-16, is it? (If it is, I'd further question what 
> UTF-16 is good for without surrogate pairs.)
> I'd phrase this such as:
>   Specifications MUST NOT allow surrogate code points as independent
>   characters; surrogate code points should be allowed only in
>   UTF-16 encoding when they form valid surrogate pairs.
> ]]
Received on Friday, 4 February 2005 10:17:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:01:07 UTC