W3C home > Mailing lists > Public > www-style@w3.org > January 2007

Re: [CSS3 Text] Japanese Iteration Marks

From: MURAKAMI Shinyu <murakami@antenna.co.jp>
Date: Fri, 12 Jan 2007 01:13:39 +0900
To: www-style@w3.org
Message-Id: <20070111232159.90ED.MURAKAMI@antenna.co.jp>
Hi fantasai,

The answer of your question about Japanese iteration marks is found in
the Rule Book:
文字の組方ルールブック
ISBN4-88888-312-2
it is on your site!
http://fantasai.inkedblade.net/style/discuss/line-breaking/ja/rule-book/


see the rule f of the page 8.
http://fantasai.inkedblade.net/style/discuss/line-breaking/ja/rule-book/8-9.jpg


f.
くり返し符号(々、ゝ、ゞ、〳〵など)が行頭にくることは許容し、そのま
ま行頭に組む。
[Iteration marks are allowed to appear at beginning of line and they are
put on the beginning of line as is.]

*
もとの字を重ねる方式もある。(ただし、古典物などでとくに原文の表記を
生かす必要のあるときなど、また、地名・人名など固有名詞の場合はこの限り
ではない。)
[There is a way repeating the appropriate character (instead of the
iteration mark). (But this way is not applicable when the original text
is important, for example in classics, or in proper nouns such as place
or person names.]

*
行頭にくることを禁止し、前の行を調整して一字追い出すか、またはくり
返し符号を前行に追い込み方式もある。(以下の例は、前行の字間をあけて一字
追い出している。)
[There is a way not allowing iteration marks at beginning of line, for
that the preceding line are adjusted to push the last character out or
to push the iteration mark in the preceding line. (In the following
example, the character spacing of the preceding line is widened and one
character is pushed out.)]


To sum up, the most common rule: iteration marks are allowed at the
beginning of line as is without any replacing.

There are two optional ways (not so often used).

* replacing to appropriate character (but this way is limited and very
difficult to automate. I think it is not necessary in the CSS spec!)

* iteration marks are not allowed at the beginning of line
("strict" line breaking)


best regards,

-- 
Shinyu Murakami
Antenna House XSL Formatter team
http://www.antennahouse.com



On Wed, 10 Jan 2007 20:05:07 +1300
fantasai <fantasai.lists@inkedblade.net> wrote:

> 
> CSS3 Text introduces a property to control whether strict or loose
> line breaking rules are used in Japanese:
> 
>    http://www.w3.org/TR/css3-text/#word-break

> 
> One of the differences between strict and loose is allowing breaks before
> Japanese iteration marks. I have read in various sources that when there's
> a break before an iteration mark, the iteration mark should be replaced
> with the appropriate character. Wikipedia describes and illustrates this
> behavior here:
> 
>    http://en.wikipedia.org/wiki/Iteration_mark

>    http://en.wikipedia.org/wiki/Reference_mark#Repetition_marks

> 
> I am currently speccing this in CSS3 Text. What I have so far is
> 
>     | If the UA breaks before a Japanese iteration mark, it should* replace
>     | the iteration mark the character represented by the iteration mark:
>     |
>     |   * the corresponding Han character, for IDEOGRAPHIC ITERATION
>     |     MARK (U+3005) and VERTICAL IDEOGRAPHIC ITERATION MARK (U+303B)
>     |   * the (appropriately-voiced) corresponding Hiragana character,
>     |     for HIRAGANA ITERATION MARK (U+309D) and HIRAGANA VOICED ITERATION
>     |     MARK (U+309E)
>     |   * the (appropriately-voiced) corresponding Katakana character,
>     |     for KATAKANA ITERATION MARK (U+30FD) and KATAKANA VOICED ITERATION
>     |     MARK (U+30FE)
>     |
>     | A sequence of <var>N</var> iteration marks corresponds to the sequence
>     | of <var>N</var> characters that immediately precedes it. If an iteration
>     | mark does not correspond to a character of the matching script type,
>     | then the iteration mark must not be replaced.
> 
> This text doesn't address the vertical iteration marks U+3031-3035, however.
> I'm not sure exactly how those work. Can anyone explain what behavior is
> expected?
> 
> * I am currently using 'should' rather than 'must'. Let me know if I should
>    change that (or anything else).
> 
> ~fantasai
> 


Received on Thursday, 11 January 2007 16:14:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:49 GMT