- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Fri, 09 May 2014 11:55:37 -0700
- To: kawabata taichi <kawabata.taichi@gmail.com>, Koji Ishii <kojiishi@gluesoft.co.jp>
- CC: "www-style@w3.org" <www-style@w3.org>, "public-i18n-cjk@w3.org" <public-i18n-cjk@w3.org>
FWIW, I agree with Kawabata-san that the pairing of ruby should be defined in both specs. CSS needs to define it for layout purposes, even if the markup is not <ruby> markup. HTML needs to define it for semantic purposes, even if CSS is not used. Speech for example is a rendering of HTML ruby markup that does not use CSS layout. Yes, this creates the potential for divergence between the HTML and CSS specs. The editors of these specs must be diligent to prevent that from happening. But also, if the specs diverge it means that there is something to look at more closely, since at least one of them is not correct. Therefore writing the pairing algorithm twice can be a benefit, and hopefully implementors will help us to notice any such discrepencies and fix them. ~fantasai
Received on Friday, 9 May 2014 18:56:06 UTC