From: Koji Ishii (firstname.lastname@example.org)
Date: Tue Feb 22 2011 - 01:15:46 CST
There's a discussion going on in W3C CSS mailing list about specifications of the text-transform property, specifically how the "capitalize" value that titlecase specified span of text.
During the discussion, two cases were presented:
1. Titlecasing words starting with numeric glyphs (e.g., "99ers") can be "99Ers" if we follow the rules defined in 5.18 Case Mappings. Is this discussed here and it's up to implementations to define which words to apply titlecasing, or should this be fixed in Unicode spec?
2. We're thinking to use UAX #24 to separate words and then apply Titlecase_Mapping to every word. But doing so makes "a.m." to be "A.m." and it contradicts with the general publication rules. While I understand both separating words and titlecasing are ambiguous, cannot be perfect, and we must make compromises. But since Unicode defines these two rules separately, I guess there's a possibility that "word separating rules optimized for titlecasing" could be slightly different from general word separating rules. I haven't thought much about counter-cases for not doing so, but I wonder if anyone in this ML could have idea including whether we should do it or not, or we should include more other cases.
Any feedback is greatly appreciated.
This archive was generated by hypermail 2.1.5 : Tue Feb 22 2011 - 01:20:25 CST