W3C home > Mailing lists > Public > public-i18n-cjk@w3.org > January to March 2014

[Bug 24369] Reason for ‘ruby base span’ attribute to come back

From: <bugzilla@jessica.w3.org>
Date: Tue, 25 Mar 2014 18:01:00 +0000
To: public-i18n-cjk@w3.org
Message-ID: <bug-24369-3862-ts7l5VN3jz@http.www.w3.org/Bugs/Public/>

Richard Ishida <ishida@w3.org> changed:

           What    |Removed                     |Added
                 CC|                            |ishida@w3.org

--- Comment #1 from Richard Ishida <ishida@w3.org> ---
There may be more than one bug rolled together here. 

I guess my first question is how widespread is the use case for putting all the
annotations at the end of the paragraph? I can see how there is more of an
opportunity for this in Chinese than in Japanese (which has lots of kana gaps),
but is it really a common approach, or just something that 'you could do'.

Over the years I have come across people suggesting all sorts of possible ways
to stretch ruby, with a little shoe-horning, to do things that were outside its
main use cases (eg. phonetic descriptions, linguistic glosses, ...).  Adding
functionality to cover all those requirements is likely to add several more
years before ruby is implemented, given the way things have been progressing,
so recently I've been concentrating on pushing for support for the core use
cases, so that at least we can cover the the majority of needs in a timely way.

Note, also, that you can handle some of the rbspan issues by using empty rt
elements, rather than rp. I think this avoids twisting the semantics. For
example, you can associate the 


    <rtc lang=“zh-cmn-Latn">
        <rp lang=“zh-cmn”>(<strong>上方段落的普通話漢語拼音:</strong></rp>

Where you run into problems is when you have double-sided ruby that doesn't
match and you want to use these really long runs of rb followed by rt.

You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 25 March 2014 18:01:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:59:20 UTC