W3C home > Mailing lists > Public > www-svg@w3.org > October 2008

Re: [1.2T-LC] i18n comment 5: Characters and glyphs (ISSUE-2106)

From: Doug Schepers <schepers@w3.org>
Date: Fri, 10 Oct 2008 22:59:54 -0400
Message-ID: <48F016AA.4040809@w3.org>
To: ishida@w3.org
CC: www-svg@w3.org, public-i18n-core@w3.org

Hi, I18N-

ishida@w3.org wrote (on 10/10/08 3:43 PM):
> Comment from the i18n review of: 
> http://www.w3.org/TR/2008/WD-SVGMobile12-20080915/
> Comment 5 At http://www.w3.org/International/reviews/0810-svg-tiny/ 
> Editorial/substantive: E Tracked by: RI
> Location in reviewed document: 10.4
> [httphttp://www.w3.org/TR/SVGMobile12/text.html#TextElement]
> Comment: "The 'text' element renders its first glyph (after
> bidirectionality reordering) at the initial current text position,
> which is established by the 'x' and 'y' attributes on the 'text'
> element (with possible adjustments due to the value of the
> 'text-anchor' property). After the glyph(s) corresponding to the
> given character is (are) rendered, the current text position is
> updated for the next character. In the simplest case, the new current
> text position is the previous current text position plus the glyphs'
> advance value."
> I think this should say "the current text position is updated for the
> next glyph" not "character", since there are numerous scripts where a
> combining character combines to the left of the glyph for the base
> character or characters in left-to-right text (for a simple example,
> see the second para at
> http://rishida.net/scripts/myanmar/#vsplacement, where the second
> glyph from the left is displayed before the two characters that
> follow it). The current text makes it sound like most scripts are
> like English.

Fixed.  Please let us know if this satisfies your comment.

Received on Saturday, 11 October 2008 03:00:29 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:15 UTC