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

Re: [1.2T-LC] Glyphs and <text> offsets (ISSUE-2169)

From: Doug Schepers <schepers@w3.org>
Date: Fri, 31 Oct 2008 13:10:42 -0400
Message-ID: <490B3C12.4050107@w3.org>
To: fantasai <fantasai.lists@inkedblade.net>
CC: www-svg <www-svg@w3.org>

Hi, fantasai-

fantasai wrote (on 10/30/08 4:58 PM):
> http://dev.w3.org/SVG/profiles/1.2T/publish/text.html#CharactersAndGlyphs
> http://dev.w3.org/SVG/profiles/1.2T/publish/text.html#CharactersAndGlyphs
> Given that whether 'fi' is a single glyph or two glyphs depends on the
> fonts available, and given that the mapping of the <text> element's
> coordinates to letters depends on the number of glyphs, does this mean
> that assigning coordinates to letters in a word like
>   final
> depends on what fonts are available?
> If so, that seems like a problem.

This is functionality that has been in SVG since the beginning, and it
doesn't seem to have caused problems.  Indeed, authors do need to be
careful about specifying fonts when using glyph positioning, but with
SVG Fonts (and the downloadable Web fonts that will hopefully be
available soon through other W3C initiatives), authors can expect to
have a reasonable amount of control over this.

Still, this is something we could revisit in SVG 2.0 Core, if necessary.
 Perhaps we could indicate that glyph positioning negates the use of
ligatures; there is precedent in languages like TeX, which provides a
way to suppress undesired ligatures.  Another option would be a specific
property that controls whether ligatures are used; this might also be
desirable for letter-spacing.

While the SVG WG doesn't feel that there is a pressing need to address
this in SVG 1.2 Tiny, we are happy to work with the CSS and XSL WGs in
the future to solve this quirk.

Please let us know if this satisfies your comment.

Received on Friday, 31 October 2008 17:10:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:20 UTC