W3C home > Mailing lists > Public > www-svg@w3.org > April 2011

Re: SVG Font Blog Post Question

From: Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de>
Date: Sat, 30 Apr 2011 12:11:33 +0100
To: www-svg@w3.org, jeremie.patonnier@gmail.com, jason@sosponsored.com
Message-Id: <201104301311.34535.Dr.O.Hoffmann@gmx.de>
 Jeremie Patonnier: 
...
>The main problem here is that using SVG font is impossible at the 
>editing stage because Firefox nor IE support such a font format.
...

At least for smaller amounts of text there is an option to work around
such gaps and bugs of current browsers:
For each glyph put an element symbol, svg or g into the defs containing
the required shapes and a title representing the character and maybe
some additional metadata with information for further processing.

Each time such a glyph is needed, it can be referenced, positioned, 
transformed and decorated independently with a use element.
If some (PHP-) skript or something like this is used, the generation of
such a document is not necessarily very complex and one does not
need other formats and no raster images or conversion tools.

If only g and use do the job, it is possible as well to limit the document
to SVG tiny 1.1, what means, that this is interpretable with older
mobile devices as well ;o)

Concerning accessibility I think, one should add a desc element to such
documents with a simple text description of what this workaround means
and that it is only used to work around bugs and gaps in some common
viewers. Then the audience is informed about the problem and has a
good chance to understand why the document got so huge - and why 
one does not have to read the rest of the file, if one uses the text 
alternative. Doing it this way, there is no need anymore to add a
title to each of these glyphs in the defs ;o)


Olaf
Received on Saturday, 30 April 2011 11:12:04 GMT

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