W3C home > Mailing lists > Public > www-style@w3.org > May 2014

Re: [css-text] I18N-ISSUE-315: Reference to line breaking in KLREQ

From: Richard Ishida <ishida@w3.org>
Date: Thu, 29 May 2014 17:54:52 +0100
Message-ID: <5387665C.80305@w3.org>
To: fantasai <fantasai.lists@inkedblade.net>, "Phillips, Addison" <addison@lab126.com>, "CSS WWW Style (www-style@w3.org)" <www-style@w3.org>
CC: www International <www-international@w3.org>
The i18n WG is satisfied with this resolution and has closed this issue.
Thanks!
RI





On 09/05/2014 00:45, fantasai wrote:
> On 01/24/2014 10:21 AM, Phillips, Addison wrote:
>> State:
>>      OPEN WG Comment
>> Product:
>>      CSS3-text
>> Raised by:
>>      Richard Ishida
>> Opened on:
>>      2013-12-11
>> Description:
>>      5.2. Breaking Rules for Punctuation: the ‘line-break’ property
>>
>> http://www.w3.org/TR/2013/WD-css-text-3-20131010/#line-break-property
>>
>>      "The rules here are following guidelines from KLREQ for Korean,
>>       which don't allow the Chinese/Japanese-specific breaks. However,
>>       the resulting behavior could use some review and feedback to make
>>       sure they are correct, particularly when “word basis” breaking is
>>       used (‘word-break: keep-all’) in Korean."
>>
>>      I don't see what this is referring to. The rules below seem to all
>>      be relevant to either Japanese or Chinese.
>
> Right. The question is whether Korean should have the same allowances
> as Chinese and Japanese. Notice there are special line breaks that are
> allowed *only* when the language is *known* to be Chinese or Japanese.
> We could allow them also if the language is known to be Korean. However,
> KLREQ does not seem to allow these breaks, so we did not allow these
> special breaks for Korean.
>
> In general, we need closer review of line-breaking for Korean, since we
> have received very few comments on Korean line-breaking rules.
>
> ~fantasai
>
>
Received on Thursday, 29 May 2014 16:55:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:43 UTC