W3C home > Mailing lists > Public > www-svg@w3.org > February 2000

"current" position for multiple <path> elements

From: Arnold, Curt <Curt.Arnold@hyprotech.com>
Date: Fri, 11 Feb 2000 13:27:25 -0700
Message-ID: <00E567D938B9D311ACEC00A0C9B468730C7575@THOR>
To: "'www-svg@w3.org'" <www-svg@w3.org>
In the following SVG file:

<?xml version='1.0' standalone='no' ?>
<!DOCTYPE svg SYSTEM 'svg-19991203.dtd' >
<svg width='700' height='700' >
<g style='text-rendering:optimizeLegibility;shape-rendering:default'>
<text x='5' y='20' style='font-size:24'>
<rect x='40' y='100' width='560' height='440' style='fill:#FFFFA0' />
<g style='fill:none; stroke:black; stroke-width:3' >
<path d='L 70,110 v 370 M 70 295 h 400' />
<g style='fill:none; stroke:blue; stroke-width:1'>
<path d='M 70 448.664 80 429.381 90 399.853 100 366.107'/>
<path d='L 110 327.541 120 284.756 130 241.971 140 204.609'/>

There are two successive path elements (which is allowed by the DTD).  The first element uses an explicit moveto, the second one was intended to draw a line from the last coordinate 100, 366.107 to

I've tested this on two different implementations neither of which did what I expected.  The Adobe plug in rejected the second path since it was missing a moveto.  The IBM SVG Browser used 0,0 as the
current position for the path.

If the Adobe implementation is correct that every path must start with an explicit moveto, then that should be stated in the spec (if it is, I can't find it).  If the IBM behavior is right, then that
should be explicitly stated.  And if a new path should start with its current position being the terminal position for the last path, then that should be stated.
Received on Friday, 11 February 2000 15:29:56 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:46:47 UTC