[css3-writing-modes] Character's intrinsic orientation and text-orientation property (was referring to Unicode

I understand and agreed with your suggestion for better wording referring to Unicode in this mail[1], but for this specific example, I think there's some misunderstanding between us.

> In the case of the 'text-orientation' property, the reasons for this
> are evidenced by the issue noted at the end of the property description:
> 
> "Issue: Need to define handling of EAW Ambiguous (A) symbols and punctuation."
> 
> In other words, the decision as to whether to rotate the glyphs for
> a given character in vertical text needs to be more clearly specified
> since this is *not* explicitly covered as part of the text of UAX11.

The description of the 'text-orientation' property[2] doesn't say "just use UAX11"; instead, it defines an algorithm using properties defined in UAX11. It was once discussed in www-style[3], but here's a copy of the pseudo algorithm:

IF ScriptOrientation=Translate || (EAW=F|W)
 Always upright
ELIF ScriptOrientation=Rotate # All chars are EAW=N
 Always sideways
ELIF ScriptOrientation=Horizontal # EAW=F|W are already excluded by first IF
 Sideways for ''vertical-right'', upright for ''upright''
ELIF # Script=Common|Inherited|Unknown
 IF EAW=H|N|Na
  Sideways
 ELSE # EAW=A
  ...

The "..." part is where the issue points to, and the one we discussed once in www-style[3].

I hope this matches to your original intention, except that we should use your suggested description for the Unicode property names.

[1] http://lists.w3.org/Archives/Public/www-style/2011May/0071.html

[2] http://dev.w3.org/csswg/css3-writing-modes/#text-orientation

[3] http://lists.w3.org/Archives/Public/www-style/2011Mar/0489.html



Regards,
Koji

Received on Sunday, 8 May 2011 12:35:26 UTC