W3C home > Mailing lists > Public > public-i18n-cjk@w3.org > July to September 2012

Re: [css3-text] Better wording than "known to be language X" (was line-break questions/comments

From: Nat McCully <nmccully@adobe.com>
Date: Tue, 28 Aug 2012 11:21:45 -0700
To: David Singer <singer@apple.com>
CC: Koji Ishii <kojiishi@gluesoft.co.jp>, Glenn Adams <glenn@skynav.com>, W3C Style <www-style@w3.org>, "public-i18n-cjk@w3.org" <public-i18n-cjk@w3.org>, "ML public-i18n-core (public-i18n-core@w3.org)" <public-i18n-core@w3.org>
Message-ID: <C7239632-CEE0-4F4C-B97A-D83E7B01443B@adobe.com>
Sorry to jump in. I think that due to ambiguities in context possible with today's parsing engines and problematic issues with how to set mixed language text, the easy way out is to have the preferred rule set specified in the markup. Deriving the correct language is too hard, and the designer really might have a bias on how they want the text to look. A Japanese design would dictate following a Japanese standard for line breaks and leading and grid, regardless of the language or glyphset of the content. It should be possible to specify "set this paragraph according to Japanese rules".


--Nat


On Aug 28, 2012, at 9:19, "David Singer" <singer@apple.com> wrote:

> One problem is the verb 'known' which implies some knowledge on the part of some reader, i.e. the verb identifies an agent outside the scope of the specification.  Perhaps it would be better to use a verb that talks about what the reader is told, rather than what they deduce or conclude?  
> 
> "identified as language [x]"
> "identified by the rules of the enclosing context as being in language [x]" (a bit wordy)
> "labeled as language [x]" (though some identification is not via 'labelling')
> 
> David Singer
> Multimedia and Software Standards, Apple Inc.
> 
> 
Received on Wednesday, 29 August 2012 11:00:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 29 August 2012 11:00:16 GMT