W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2010

[Bug 10829] i18n comment : ruby code samples

From: <bugzilla@jessica.w3.org>
Date: Thu, 30 Sep 2010 09:27:25 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P1FQD-0008T4-ET@jessica.w3.org>

fantasai <fantasai.bugs@inkedblade.net> changed:

           What    |Removed                     |Added
                 CC|                            |fantasai.bugs@inkedblade.ne
                   |                            |t

--- Comment #2 from fantasai <fantasai.bugs@inkedblade.net> 2010-09-30 09:27:24 UTC ---
(In reply to comment #1)
> Would the white space actually affect the rendering? i.e. why is the whitespace
> bad?

Chinese and Japanese do not use white space to separate words or other
linguistic constructs. Therefore in these languages white space should not be
introduced between characters.

The white space collapsing rules in CSS2.1 do allow UAs to collapse white space
surrounding a line feed to nothing; however this is not normatively required,
and only IE has implemented this behavior. Additionally, the css3-ruby spec
still does not define its interaction with white space collapsing rules. Even
the line break transformation rules were normatively defined (which they will
be in css3-text), to correctly collapse away white space between the base
characters when using Pinyin ruby, the white space processing rules would have
to ignore the ruby text.

Given these complications, it is therefore safer to not include such white
space in the source markup, and the HTML5 spec should adopt such a practice in
its examples.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 30 September 2010 09:27:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:25 UTC