The dialogue between Patrick and Sebastian
prompts a further question:
> On Thu, Feb 06, 2003 at 01:39:11PM -0500, Patrick Durusau wrote:
Not sure of the distinction you are making.
> > I was thinking of each stroke of the glyph being represented by a vector
> > in the SVG. All of the vectors for a particular glyph combine together
> > to describe the glyph.
> well, I'd like to see an example of Melissa's existing
> coding before committing myself, but to take a simple example,
> how can SVG record the idea that this <stroke> goes "down",
> and is regarded as the first to be made? say the glyph has
> 3 strokes, and you think you know the order they come in. How
> do you express that precedence in pure SVG? ok, so you
> can use class attributes, but thats a bit of a hack.
<lachance-ecnahcal> Certain maps are designed to be read upside down. Can
one not approach SVG as a set of graphic palindromic dragons (bunches of
vectorial rays) with a scalable tail and multiheadedness with variable
directionality? :Up: and :down: strokes may lead to the same glyph but by
different paths. There is also the case of the boustrophedon to consider.
Francois Lachance, Scholar-at-large,
knows no "no exit" in a hypertext
every cul-de-sac is an invitation to turn