- From: Koji Ishii <kojiishi@gluesoft.co.jp>
- Date: Mon, 27 Aug 2012 08:13:43 -0400
- To: 'Glenn Adams' <glenn@skynav.com>
- CC: W3C Style <www-style@w3.org>, "public-i18n-cjk@w3.org" <public-i18n-cjk@w3.org>
>>> The phrases "known to be X [language]" are completely undefined as far as >>> the current text is concerned. If you want to have one note that covers all X, >>> then by all means do so, but don't just leave it in such an undefined state. >> >> Did you follow the link? I think it's well-defined in Terminology section. The >> section also has examples you requested. > > yes; my problem is the phrase "known to be Japanese or Chinese" does not map > to "if the content language contains 'ja' or 'zh' or equivalent as its primary language > subtag". same for the phrase "known to be Turkish" which also appears in another > context in this document I agree that your suggested wording is easier to understand for HTML authors, but it's not accurate because CSS does not define what the content document format is and how content document determines the language. CSS Selectors Level 3[1] informatively recommends content document to use BCP47, but it's still content document that defines language syntax of the content document. The wording in our Terminology section[2] looks almost the same as the one in CSS Selectors Level 3 to me; it defines our syntax, but does not define content document syntax. It's hard for me to find good wording to improve this without being incorrect. If you have suggested wording, I can run it by fantasai to put into the spec. [1] http://www.w3.org/TR/css3-selectors/#lang-pseudo [2] http://dev.w3.org/csswg/css3-text/#content-language Regards, Koji
Received on Monday, 27 August 2012 12:14:16 UTC