Re: Fwd: SVG Fonts

Well, yeah, you can.  But you don't embed the encoding in the document, and
therefore you do not control the geometry.

So, there is an issue here  about bandwidth and document size.

If you can get away without specifying the exact font, SVG, via CSS allows
ways for you to try to pick the best font for an OS/browser.  You can
provide a list that will iterate through your choices, but eventually, given
total failure, will drop down to the default font for the browser.  Which
differs for different OS/browser combinatons.   If you can dictate the the
OS/browser, fonts are not an issue.  Narrow audience though.  If we had wide
adoption of stadard fonts, so that "font family" would have a chance of
sucess across browsers, that would help.  That has been attempted with web
fonts (and I may need education here) but I don't see that happenning.

I really don't understand why more engines do not implement SVG fonts.  You
have text metrics, you have path.  That will solve 99% of all requirements
and provide an excellent test bed to implement the rest.

Sorry, but we did this at BitFlash ~7 years ago.  In fact Chris demoed
dynamic flowing SVG text for BitFlash in Zurich in 2002? on an IPaq. (Ask
him)  It's not that hard.

(Rick shuts up)

On Sun, Sep 6, 2009 at 9:55 PM, Robert O'Callahan <[email protected]>wrote:

> On 7/09/09 1:53 PM, Rick wrote:
>
>> Mostly because you can provide exact geometry for the whole page, and not
>> worry about the registration of the text.  Because you provide it.  But
>> also, if you like, you can do a lot of cool things with a font that you
>> design.
>>
>
> But you can do these things with Truetype/Opentype fonts as well. Right?
> (In fact you can do more since you can have a proper shaping engine,
> hinting, etc.)
>
>
> Rob
> _______________________________________________
> dev-tech-svg mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-tech-svg
>



-- 
Cheers!
Rick