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: Ishii, Koji a | Koji | BLD <koji.a.ishii@mail.rakuten.com>
Date: Thu, 17 Oct 2013 22:11:29 +0000
To: Eric Muller <emuller@adobe.com>, "public-i18n-cjk@w3.org" <public-i18n-cjk@w3.org>
Message-ID: <CE868F0E.44787%koji.a.ishii@mail.rakuten.com>
Oh, I think I understand what you're talking about; I once used the word
"conformant," to mean the same behavior as written in the spec, but from
Sylvain's response, I'm guessing the word is stronger and inappropriate.
If you mean that, I apologize. Is that what you're trying to teach me?


On 10/18/13 6:44 AM, "Ishii, Koji a | Koji | BLD"
<koji.a.ishii@mail.rakuten.com> 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.

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:12:06 UTC

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