W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2011

[Bug 13113] Parsing algorithm should not preclude Complex Ruby

From: <bugzilla@jessica.w3.org>
Date: Fri, 07 Oct 2011 23:53:27 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RCKEJ-00015M-6z@jessica.w3.org>

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

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|NEEDSINFO                   |

--- Comment #15 from fantasai <fantasai.bugs@inkedblade.net> 2011-10-07 23:53:22 UTC ---
Since I neither have access to a Japanese library, nor the time and patience
necessary to tabulate the kind of data set you're requesting, you're getting
the next best thing: scans from a magazine lent me by someone I randomly met on
the BART. The magazine is Mangajin issue 53, published March 1995, and the
tagline is "Japanese Pop Culture & Language Learning". Here are two
representative pages and diagrammed extracts from them.

Several articles furigana over the kanji. Example:
They are formatted using jukugo ruby. (Jukugo ruby formats like a word-to-word
association, but line-breaks differently: the associated kana must be kept wih
their kanji base.) This colorized extract shows the association of kana to
The ratio of compound words to simple words is 2:1. The rest of the page holds
close to this ratio.

Other parts of the magazine use double-annotated ruby. Example:
Notice the line-breaking behavior and the word associations.
Here is a diagrammed exerpt. The ruby base is in red. The first annotation
(romaji) is in blue. The second annotation (English transliteration) is green:

Here is real-world use of complex ruby. You can of course continue to argue
that the use case is unimportant, but it exists.

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 Friday, 7 October 2011 23:53:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:05 UTC