W3C home > Mailing lists > Public > public-i18n-cjk@w3.org > October to December 2013

Re: [css3-writing-modes] Re-Summary of Tr in UTR#50 and text-orientation discussions

From: Asmus Freytag <asmusf@ix.netcom.com>
Date: Thu, 17 Oct 2013 15:19:20 -0700
Message-ID: <52606268.4060001@ix.netcom.com>
To: "Ishii, Koji a | Koji | BLD" <koji.a.ishii@mail.rakuten.com>
CC: Eric Muller <emuller@adobe.com>, public-i18n-cjk@w3.org
On 10/17/2013 2:44 PM, Ishii, Koji a | Koji | BLD wrote:
> Am I? I don't think I said whether it's normative or informative, just
> pointed out that what it says. Is that incorrect?
>
>
> On 10/18/13 2:21 AM, "Eric Muller" <emuller@adobe.com> wrote:
>
> On 10/15/2013 5:23 AM, Koji Ishii wrote:
>> 1. UTR50 says method A.
> I think you are going too far. UTR50 provides an informative property.
> "informative" has a formal meaning in Unicode:
>
> ---
> D35 Informative property: A Unicode character property whose values are
> provided for information only.
>
> A conformant implementation of the Unicode Standard is free to use or
> change informative property values as it may require, while remaining
> conformant to the standard.
> ---
>
> This leaves a very large degree of freedom to users of UTR50, with no
> *formal* obligation.
Hmm.

The minute some other specification *references* an informative UTR or 
property, the normative status of these are no longer based on Unicode's 
definition of property status, but on the type of reference. If the 
other specification requires "conformance to the Unicode Standard" then 
D35 holds, but if it says "conformance to this specification includes 
implementation of TR50" then D35 is no longer relevant. The clear intent 
of such a conformance requirement would be to limit what its users could 
do to the ordinary description of the algorithm or property in the TR.

An intermediate status would obtain if the specification pointed out 
options (e.g. tailoring) described in the UTR.

A./

>
> As for the *intent*, I think it is also informational. I read it as
> "here is one additional piece of data (the u or r after the T), that
> some users could find useful". There is no implication, from Unicode,
> that using that piece of data is better (or worse) than not using it.
>
> If the property were to become more formal, Adobe would most likely ask
> that u/r part be dropped, or split in its own informal property.
>
> Eric.
>
>
>
>
>
>
>
>
>
>
>
Received on Thursday, 17 October 2013 22:19:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:10:24 UTC