[BATIK-22] Temporary support for alt-glyph and SVG fonts

• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Affects Version/s: 1.0 Beta 1
• Component/s: GVT Text
• Environment: Operating System: All; Platform: PC
• Assignee: Batik Developer's Mailing list
• Reporter: Vincent Hardy
• Created: 02/Feb/01 14:21
• Updated: 16/Nov/04 19:05
• Resolved: 16/Nov/04 19:05

Description

Right now, Batik does not support alt-glyph and SVG fonts.
There is a way to have some temporary (limited) support
(email from Bill Haneman):

I have had a look at altGlyph. Fun stuff but very
complex, lots of fall-back behavior. Actually supporting
it requires support for SVG fonts, external fonts via
CSS, etc.

I think that if we can change the bridge so that
we don't choke when SVG font elements are present
(and just ignore them or create dummy elements)
then we can do a much nicer thing and treat altGlyph
elements just like tspans. This is in fact what the spec says
one should do if the alternate glyphs are not available/
realizable for some reason... an altGlyph element contains
unicode characters which are substituted with alternate
glyphs if available, the interim solution would be
to use default fonts in place of SVG fonts or externally
referenced fonts, just rendering the unicode characters
in the normal way.

Perhaps you could discuss this level of support for the
font element (creating a do-nothing element) with Stephane
or Thierry? Or maybe I could do a trivial implementation of
SVGFontElementBridge.