W3C home > Mailing lists > Public > www-international@w3.org > January to March 2014

Re: [css3-writing-modes] i18n-ISSUE-279: text-combine-horizontal & full/half-width characters

From: John Daggett <jdaggett@mozilla.com>
Date: Wed, 26 Mar 2014 21:28:16 -0700 (PDT)
To: Richard Ishida <ishida@w3.org>
Cc: www-style@w3.org, www International <www-international@w3.org>
Message-ID: <1779496343.7912986.1395894496864.JavaMail.zimbra@mozilla.com>

Richard Ishida wrote:

> I still find this a little confusing in the CR version of the spec. 
> I think the phrase:
> 
> " when the combined text consists of more than one character, then any 
> full-width characters must first be converted to their non-full-width 
> equivalents"
> 
> suggests, with the example that follows, and that uses
> text-combine-upright: digits 2;, that ordinary full-width characters
> in the content are affected by the digits keyword. Whereas, i
> suspect that what is meant is
> 
> " when the combined text consists of more than one character, then any 
> properties that would display non-full-width characters as full-width 
> characters must be disabled by text-combine-upright"

You're confusing the conditions for applying a combination with how
the combination is performed. The definition of the 'digits' value
implies that value only affects a "maximal sequence of consecutive
ASCII digits". It has no affect on full-width digits. If the 'all'
value is used instead, then a sequence of full-width digits would be
first converted to half-width digits before a combined form is laid
out.

The reason for this is that full-width digit glyphs are not the ideal
form to use if compression is required. If you search the www-style
archives for "text-combine-horizontal half-width", you'll find many
posts discussing this last fall, along with examples and details
regarding this.

Regards,

John Daggett
Received on Thursday, 27 March 2014 04:28:53 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:36 UTC