W3C home > Mailing lists > Public > www-i18n-comments@w3.org > May 2001

Re: Comments for PR-ruby-20010406

From: Martin Duerst <duerst@w3.org>
Date: Tue, 15 May 2001 16:23:17 +0900
Message-Id: <>
To: Susan Lesch <lesch@w3.org>, www-i18n-comments@w3.org, w3c-i18n-ig@w3.org
Hello Susan,

Many thanks for your very valuable comments!

At 13:58 01/04/21 -0700, Susan Lesch wrote:
>Belated congratulations on your Ruby Annotation Proposed Recommendation [1].
>These are minor editorial comments, mainly typos I missed earlier.
>Globally stylesheet -> style sheet (one way or the other)

I used 'style sheet', as on http://www.w3.org/Style/.

>In A., the file extension for xhtml-ruby-1.mod is ".mod". Just a note that
>even though it is application/xml-dtd, MacIE 5.0 downloaded it as a MOD
>music file. Older MacIEs didn't seem to; I don't know why.

This is alligned with XHTML modularization, so we can't change it

>There are two appendix Cs.


>"B. Notes on design decisions" is missing in the TOC.
>In http://www.w3.org/TR/2001/PR-ruby-20010406/style.css:
>     .content {
>         font-family: monospace;
>         color: blue;
>         font-weight: bold;
>     }
>blue is very close to the current W3C TR unvisited link color, #00c.
>(see http://www.w3.org/StyleSheets/TR/base.css). Could you use black?

Done. Also removed bold, to bring this closer to XHTML Modularization.

>In http://www.w3.org/TR/2001/PR-ruby-20010406/encodings:
>For reader's convenience
>For readers' convenience (or, For the reader's convenience)


>Below, a section and paragraph number is followed by a quote and then
>a suggestion.
>1. pars. 4 and 5


>1.1 second to last par.
>"...each ruby annotation may be associated with different, but
>     overlapping, parts of the base text..."
>How are the parts "overlapping"? They look distinct. Maybe say
>"adjacent"? Or maybe this means "different, or overlapping."

They are different because they don't start and end at the same
place. They are overlapping because the (partly) cover the
same part of the base. In the example, 'Month' and 'Expiration
Date' are associated with different parts of the base text
(the base text for 'Month' is much shorter), but these base
texts are overlapping.

>3. last par.


>3.1 par. 1
>"...section 3.2 (font size), section 3.3 (positioning), and 3.4
>     (presentation of ruby markup)..."
>"3.4" could be "section 3.4" and link as the other two do (or
>maybe you had a reason why 3.4 is not linked).


>Helpful as it is, I'm not sure this sentence needs repeating in 3.2
>since it is in 1.1.
>"...In fact, the name "ruby" originated from the name of the 5.5pt
>     font size in British printing, which is about half the 10pt font
>     size commonly used for normal text."

Specs are not always read from start to end. So we decided to have
it in both places.

>3.5 list item 2
>Ruby that represent
>Ruby that represents

Changed to 'Ruby text that represents'

>ruby that contain
>ruby that contains

same as above.

>3.5 par. 2
>detailled (twice)


>3.5 last par.


>B. par. 2


>C. Notes on backwards compatibility par. 2
>For historical reason
>For historical reasons (or, For a historical reason)


>C. Glossary, Complex ruby markup
>fine-grained (to match the other occurrences)


>C. Hiragana and Katakana
>character of that script
>a character of that script (or, characters of that script)

I'm not sure here. My impression was that for definitions,
the style without any article exists. But maybe I'm wrong.

>C. Ideograph
>Character that is used
>A character that is used


>You might consider cutting the change notes if and when you go to

Done. But a section 'changes from proposed recommendation'
is still in.

>References, XSL
>et. al.
>et al.


>References, XSLT


>[1] http://www.w3.org/TR/2001/PR-ruby-20010406/
>Best wishes for your project,

Many thanks again!

Regards,   Martin.
Received on Tuesday, 15 May 2001 03:23:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:39:56 UTC