W3C

Proposed Corrections for Requirements for Japanese Text Layout

This document:
http://www.w3.org/International/errata/jlreq-proposed.html
Last modified:
$Date: 2010/03/02 18:09:07 $
This document records reported errors in the document:
http://www.w3.org/TR/2009/NOTE-jlreq-20090529/
The latest version of the document:
http://www.w3.org/TR/jlreq/

Abstract

This document lists reports of errors in the Working Group Note Requirements for Japanese Text Layout published on 4 June 2009. After approval by the Japanese Layout Task Force the approved errata are published in Errata for Requirements for Japanese Text Layout.

Table of Contents

1. Introduction

Each erratum has one of three statuses: proposed, accepted and declined. Proposed corrections are those that have been submitted to the Working Group but which still need technical review and endorsement from the group. Accepted errata are described in Errata for Requirements for Japanese Text Layout. Declined corrections are those that have not been accepted after technical review.

Comments on the specification or these errata may be sent to www-i18n-comments@w3.org, which is publicly archived.

2. Proposed corrections

[E1] Grids in Fig. 77-79
Reported by Tony Graham
Comment In Section 3.1.9, Positioning of Closing Brackets, Full Stops, Commas and Middle Dots at Line End [1], figures 77 and 78 each show the kihon-hanmen grid and some characters that are "off grid" w.r.t. it. In contrast, figure 79 shows the actual "character frame" of each fullwidth and half-width character. All three figures have lines that end with solid setting. AFAICT, figures 77 and 78 could just as easily have been drawn to show the character frames, or figure 79 could have been drawn to show the kihon-hanmen grid. Is there a reason for the change in perspective about the grid for these figures within the one section?
Status Proposed on 2009-07-06.
[E2] Reference to Fig. 110/111
Reported by Tony Graham
Comment The second reference to Fig. 110 in Section 3.3.1, Usage of Ruby [1], should be to Fig. 111.
Status Proposed on 2009-07-07.
[E5] "the add same space"?
Reported by Tony Graham
Comment In Section 3.7.3, Jidori Processing [1], I suspect that the text "the add same space" should be "add the same space".
Status Proposed on 2009-07-07.
[E6] Typo, bunrikinshi
Reported by Tony Graham
Comment Is Section 3.8.1, Necessity for Line Adjustment [1], I suspect that "may not" should be "may not be" or even "need not be" in: the line end may not aligned to the other alignment position.
Status Proposed on 2009-07-07.
[E7] Typo, bunrikinshi
Reported by Tony Graham
Comment In Section 3.8.4, Procedures for Inter-Character Space Expansion [2], "bunrikinshi" is used twice without further explanation.
Status Proposed on 2009-07-07.
[E9] Fig. 157; "to line adjustment"
Reported by Tony Graham
Comment Several figures, e.g., Fig. 45-46, include "to line adjustment". "Line adjustment" is a good noun phrase, but it seems to me that it doesn't work so well a verb, and it may be better to change "to line adjustment" to "to adjust line".
Status Proposed on 2009-07-10
[E10] Fig. 157; "to line adjustment"
Reported by Tony Graham
Comment

Reviewing the document again for the purposes of XSL FO, I already knew there were three types of ruby -- mono-ruby, jukugo-ruby, and group-ruby -- but I had trouble finding the definition of group-ruby.

It may be better if the three types of ruby were each defined in a separate subsection of Section 3.3.1, "Usage of Ruby". Headings would make the definitions easier to identify, rather than reading through most of a paragraph to find the term "group-ruby" (and the background highlight of the term doesn't show up when the document is printed).

Another way that I confused myself is that the types are defined in the order mono-ruby, jukugo-ruby, then group-ruby, but are then discussed in the following sections in the order mono-ruby, group-ruby, then jukugo-ruby.

Lastly, the "note 5" about the reading of a kanji compound word was initially confusing to me because it likened it to "attaching ruby in katakana to kanji and/or kana base characters", but that hadn't been covered at that point. After reading the note twice, I had to give up and go on to the next point, which of course was about attaching ruby in katakana to kanji and/or kana base characters. It may help if the note also used the term "group-ruby" and/or had a cross-reference to the definition of attaching ruby in katakana to kanji and/or kana base characters.

Status Proposed on 2009-10-28
[E11] Fig. 109
Status Proposed on 2009-10-28
Reported by Tony Graham
Comment

2. Should the first 'another word' be 'word'? Should both of them?

[E12] 3.3.3, note 3
Reported by Tony Graham
Comment

1. Would it be useful to also mention dictionaries or educational meterials as examples of where small kana would be used in ruby annotation?

Status Proposed on 2009-10-28.
[E13] 3.3.3, note 3
Reported by Tony Graham
Comment

2. Would it be useful to include a figure contrasting the use and non-use of small-kana in ruby, e.g., a variant of fig. 109?

Status Proposed on 2009-10-28.
[E14] Kana?
Reported by Tony Graham
Comment

The term "kana", meaning both hiragana and katakana, is not defined in the document, though it is used in several places, including a section title.

FWIW, the connection between "ideographic" and "kanji" is also not defined, and a reader who did not already know would have to work it out from Fig. 1 and Section 2.1.2.

Status Proposed on 2009-10-29.
[E16] Fig. 119
Reported by Tony Graham
Comment

FWIW, Fig. 129 [2] hyphenates the compounds "nakatsuki-ruby" and "katatsuki-ruby" (and places the horizontal example below the vertical).

Status Proposed on 2009-10-29.
[E17] "adjacent ruby"?
Reported by Tony Graham
Comment

"adjacent" appears to be used in two senses when describing ruby.

Section 3.3.5 contains:

For mono-ruby, base characters and adjacent ruby characters are handled as one object

Section 3.3.6 contains:

inter-character space between each adjacent ruby character

inter-character space between each adjacent ruby characters

inter-character space between each adjacent base character (x2)

For group-ruby, base characters and adjacent ruby characters are handled as one object, and internal line-breaks are prohibited. Also, for an object constructed with base characters and adjacent ruby characters it is prohibited to insert additional spaces between each character for line adjustment.

Section 3.3.7 contains:

type of script of the adjacent characters

Section 3.3.8 contains:

spacing between base characters and their adjacent characters in the main text

It seems to me that sequential characters are being described as adjacent and that base and ruby characters are also being described as adjacent. Would it be better to use a different word for one of these two cases?

Status Proposed on 2009-10-29.
[E18] More than three ruby characters with jukugo-ruby?
Reported by Tony Graham
Comment

This is probably similar to my earlier confusion about mono-ruby with more than three ruby characters [1].

The second paragraph of Section 3.3.7, "Positioning of Jukugo-ruby with Respect to Base Characters", begins:

If there is any kanji character in a given kanji compound word which needs more than three ruby characters, the jukugo-ruby layout cannot be used.

However, the alternative methods in Fig. 130 and Fig. 131 are both described as jukugo-ruby and both show three or fewer ruby characters per kanji.

1. Should "jukugo-ruby" in the first sentence be "mono-ruby"?

2. It's not clear to me whether the examples in Fig. 131 are correct for both nakatsuki-ruby and katatsuki-ruby or whether only katatsuki-ruby is being illustrated in this figure.

3. Who or what decides whether the maximum overhang over another base character is either a full character width or one and a half times the full-width of a ruby character?

Status Proposed on 2009-10-29.
[E19] Fig 197
Reported by Tony Graham
Comment

The paragraph before Fig. 197 [1] describes the single figure as "are examples with the same jukugo-ruby as in [Fig.195] and [Fig.195] ..."

The figure shows the same jukugo-ruby as Fig. 195 and Fig. 196. The text should be corrected.

Status Proposed on 2009-12-10.
[E20] Section 3.3.8, last list
Reported by Tony Graham
Comment

In the last list in Section 3.3.8, "Adjustments of Ruby with Length Longer than that of the Base Characters", [1]:

- Item "e" covers "Jukugo-ruby at the line head or at the line end", but item "f" covers "Jukugo-ruby at the line head" and item "g" covers "Jukugo-ruby at the line end". Is this overlap correct?

- Note 2, following the list, includes:

The handling and positioning of these complexes with adjacent characters is discussed in Appendix F Positioning of Jukugo-ruby as a complete table, following 3.9 About Character Classes.

Appendix F is more than just a table, and there are sections and other appendices between Section 3.9 and Appendix F.

Status Proposed on 2009-12-10

2. Accepted corrections

[E3] 'Three' in "ruby text with more than three characters"?
Reported by Tony Graham
Comment In Section 3.3.5, Positioning Mono-ruby with Respect to Base Characters [1], there are several references to "attaching more than three hiragana ruby characters to a single base character" or "ruby text with more than three characters". However, the paragraph before Section 3.3.5 explains that the following sections assume "ruby is half the size of the base characters", and though Figures 121 and 122 are titled as showing "ruby text with more than three characters", in each case they show ruby text of exactly three characters.
Status Proposed on 2009-07-07. Accepted as editorial fix by JLTF, 2010-02-15
[E4] 'Three' in "ruby text with more than three characters"?
Reported by Tony Graham
Comment Also but unrelated, in Figure 120, "icharacter" should be "character" in "icharacter frame of ruby character".
Status Proposed on 2009-07-07. Accepted as editorial fix by RI, 2010-02-07
[E8] Fig. 157; "to line adjustment"
Reported by Tony Graham
Comment Figure 157 has "cavses" instead of "causes".
Status Proposed on 2009-07-10. Accepted as editorial fix by RI, 2010-02-07
[E15] Fig. 119
Reported by Tony Graham
Comment

The text within Fig. 119 [1] contains "nakatuki" and "katatuki" instead of Hepburn-style "nakatsuki" and "katatsuki".

Status Proposed on 2009-10-29. Accepted as editorial fix by RI, 2010-02-07

3. Declined corrections

There are currently no declined corrections.