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

Re: Revisiting SVG Fonts

From: Charles Pritchard <chuck@jumis.com>
Date: Tue, 01 Nov 2011 15:27:12 -0700
Message-ID: <4EB07240.4030004@jumis.com>
To: Erik Dahlstrom <ed@opera.com>
CC: www-svg@w3.org
> On Mon, 31 Oct 2011 18:21:02 -0700, Charles Pritchard 
> <chuck@jumis.com> wrote:
> ...
>> What's the status of ligatures on those SVG Tiny viewers?
>> Is there a maximum length that a ligature can be?
>> For instance, could 80 characters be used?
> There probably is some implementation-dependent limit yes. The spec 
> itself doesn't limit the string length for @unicode on <glyph>.
> I'm pretty sure it would work ok if you happened to have an 80 
> characters ligature in an svgfont, but it's not really a common case :)
Consider it a very nasty hack/work-around to display scanned text or 
hand-written text while maintaining machine readable DOM.

<text class="line1">first line of text</text>
or even:
<text>[unicode private char] another line of text</text>

I'm just brainstorming here, but it's been in my mind awhile... 
representing non-standard scripts, scanned text and hand-written text.

Of course it breaks down quickly when editing, but it does break-down 
into human readable form.

Thanks for engaging me in this. I'll take a peek inside some of the code 
bases to see what WebKit and Moz setup for their buffer lengths.

This thread has been about stretchin the use of SVG fonts (as well as 
implementing them sooner rather than later re: embedding svg in WOFF). 
So, I hope I didn't stray too far off topic.

Received on Wednesday, 2 November 2011 00:14:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:33 UTC