On Wednesday, March 19, 2008, 2:04:16 AM, Felipe wrote:
FS> I will apply for SoC on SVG Fonts implementation. My task will be
FS> basic SVG Fonts support (i.e. reading of xml attributes, proper
FS> rendering and editing). I imagine that there are some extra stuff
FS> that could be done but would not necesarily be part of my task on
FS> SoC. I could work on those after completing the basic SVG Fonts support.
That would be excellent. Basic font rendering is a needed first step.
FS> I am starting this thread to discuss SVG Fonts related wished
FS> features. I will choose among these, which ones I think make sense
FS> to add to my SoC application and which I consider extra work to be done after SoC.
FS> one idea (probably to be implemented after SoC):
FS> Since SVG Fonts actually work as an alternative kind of font file
FS> (a font can be saved as .svg and then used by other SVG drawings)
FS> inkscape could have a font editing UI.
For an editing tool of course there is a lot that can be done, right
up to creating fonts. Although, fontforge already does that part
pretty well
In terms of conversion tools, Batik also does this conversion.
FS> It could have import
FS> scripts to load TrueType fonts and export them as SVG Fonts and
FS> vice-versa. I could also do it for other font types. One issue is
FS> in the exporters because obviously not everything SVG is capable
FS> of doing is supported by TrueType, or other font formats. So, we
FS> would commonly have to deal with glyph degradation when exporting fonts.
Yes. SVG fonts can do things other formats cannot (multicoloured
glyphs, animated glyphs, etc) and similarly other formats do things
SVG can't do (OpenType gsub tables, for example).
FS> Felipe Sanches ("JucaBlues" on irc)
--
Chris Lilley mailto:chris@...157...
Interaction Domain Leader
W3C Graphics Activity Lead
Co-Chair, W3C Hypertext CG