Let me try to get the discussion started:
An SVG may use a font that is not on the rendering computer. CSS allows an artist to define a list of alternative fonts to use instead. In principle, the use of an SVG font or a WOFF font would avoid this problem, but Inkscape supports neither.
The scope of Abhishek's work will be limited to parsing a font list correctly and getting Inkscape to use the first available font in the list. It does not include things like adding a way to define the list or to enable/disable fonts in the list for testing.
One question is when should the CSS entry be turned into a list? It could be done in the initial parsing of the CSS but I have a feeling it might be better done later. One could even imagine that it be done at the last moment, then a list could be created using the existing font name entry box.
Tav
On Thu, 2011-06-16 at 07:31 -0400, Abhishek Sharma wrote:
I am eagerly waiting for all of your responses !!!!!
On Wed, Jun 15, 2011 at 1:37 PM, Abhishek Sharma <sharma.abhishek.it@...400...> wrote: Hello everybody,
I am a selected candidate for GSoC 2011 and contributed to inkscape in GSoC 2010 as well. I am looking to start the development of font fall back support in inkscape. As discussed with my mentor Tavmjong its a required item and shall be very helpful to inkscape. And as all the readers of this mail might have guessed, I am writing this mail to have the inputs of inskcape developers on this. I would love to have your comments which can help me answer questions like - Where to look into the code, What to change, What to add should it be anew class or an added functionality to a pre-existing class, questions of these sort. Waiting earnestly for all of your responses :) -- Regards, Abhishek Sharma-- Regards,
Abhishek Sharma