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

Re: Draft new ruby markup for HTML extension (ed comments)

From: Robin Berjon <robin@w3.org>
Date: Wed, 20 Feb 2013 17:34:53 +0100
Message-ID: <5124FB2D.5020105@w3.org>
To: Richard Ishida <ishida@w3.org>
CC: public-i18n-cjk@w3.org
Hi Richard,

On 13/02/2013 19:40 , Richard Ishida wrote:
> Many thanks for getting this draft out and for the hard
> work you put into it!

Not at all, it's a pleasure :)

> [1] Mono-ruby for individual base characters in Japanese
> Why the 'in Japanese'?  Mono-ruby isn't specific to Japanese.

Indeed. To be honest, this is straight from the HTML 5 draft. I mostly 
focused on changing the processing, adding new elements, and updating 
elements to match (I think that this is because a lot of the original 
material seems to have been developed for the JLREQs).

Change applied.

> I would propose, instead:
> "Annotations (the ruby text) are associated individually with each
> ideographic character (the base text). In Japanese this is typically
> hiragana or katakana characters used to provide readings of kanji
> characters."

Thanks, applied.

> [2] Jukugo ruby
> "The distinction is captured in this example: "
> Actually the example doesn't quite capture it - the illustration makes
> jukugo ruby look like group ruby. It isn't. See the examples at the
> bottom of http://rishida.net/blog/?p=469 and you'll notice that gaps
> open up in some cases, because jukugo styling is basically just a
> special kind of ruby overhang where one character (and not more) can
> overhang an adjacent base character if it doesn't fit on its own base
> character.  Nor does jukugo styling prevent breakup of the underlying
> base characters.

I understand that that's an issue but I am not the best person to 
produce a new example (as you saw when last I did). Could you provide a 
better example?

> [3] Jukugo ruby
> "both base text and ruby annotations are implicitly placed in common
> containers so that the grouping information is captured"
> See my other emails on this for substantive issues

I believe that there is a misunderstanding with the container model that 
the document you will provide here should dissipate.

> If you mark up exactly as shown, you will actually introduce a bunch of
> unwanted spaces because of the line breaks.

Fixed, thanks.

> [5] same section
> "♥<rt>Heart<rtc lang=fr>Cœur"
> There has to be a closing tag after Cœur, otherwise the parser will see
> "Cœur ☘" and get confused.

Good catch! Thanks, fixed.

Robin Berjon - http://berjon.com/ - @robinberjon
Received on Wednesday, 20 February 2013 16:35:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:10:24 UTC