W3C home > Mailing lists > Public > www-svg@w3.org > January 2000

RE: Text 'width' and 'height'

From: Jon Ferraiolo <jferraio@Adobe.COM>
Date: Tue, 11 Jan 2000 08:48:06 -0800
Message-Id: <200001111644.IAA05702@mail-345.corp.Adobe.COM>
To: paolini@us.ibm.com
Cc: www-svg@w3.org, Gaetan Frenoy <gaetan.frenoy@aspentech.com>
At 10:28 AM 1/11/00 -0600, paolini@us.ibm.com wrote:
>
>
>Hello all,
>
>Thought I'd add my two cents on text width and height to the discussion.
>As an implementor of SVG,  it seems to me that making this information
>[optionally] available in the file may very well speed rendering  in some
>cases (I'm thinking tspans and such), and certainly would make migrating to
>SVG from other markup languages a little easier.  The danger of course is
>that there may not be a be an exact match on what is rendered and what is
>given/expected for a whole host of reasons (font matching comes to mind
>here first and foremost)....
>
>Mike Paolini
>IBM SVG Team

Mike,
Regarding font matching, there is the option in SVG of expressing your font
data as "SVG fonts" (e.g., include <font> elements inside your SVG
document) so that the fonts rendered will have the same metrics as the
original fonts. (Of course, SVG fonts have some drawbacks, such as lack of
hinting and potentially larger file sizes as glyph outlines are expressed
as SVG path data.)

Beside SVG fonts, there is also the web font feature from CSS2, which is
part of the SVG specification (i.e., SVG supports the @font-face rule). The
problem with CSS2 web fonts is deciding which web font format to use, as
different implementations support different web font formats.

Jon Ferraiolo
SVG Editor
Adobe Systems Incorporated
Received on Tuesday, 11 January 2000 11:46:03 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:18 GMT