sorry, you are right. I misunderstood you. I first viewed your example in ASV6, where it renders fine. Then after your second mail I viewed your example in ASV3 and saw the bug. That's definitely a bug.
I originally thought you mean "by connecting" that it connects (or doesn't) the offset value of the stroke-dashing from the previous segment to the following segment. I saw that there are rendering differences between the viewers, how they handle the offset in path segments. The working group is going to mandate the behaviour about these offsets now. It's still open in which direction (use the remainer of the past segment or restart with the original offset). In your case, in ASV3, this is definitely a bug which is fixed in ASV6. Too bad that ASV6 is not going to be released ... Andreas --- In [email protected], "ACasualObserver" <[EMAIL PROTECTED]> wrote: > > Hi, > > Thanks for your response. > > I was (and still am) under impression that d="M4000 1000 L4000 > 1300M7000 1000 L8000 5000" means that the "pen" should be moved from > point 4000,1300 (end of first segment) to point 7000,1000 without > drawing anything. Isn't this always the correct behavior? > > If the length of the first segment is changed to anything more than or > equal to 360 (the first part of dasharray is 360), ASV works > correctly. For example d="M4000 1000 L4000 1500M7000 1000 L8000 5000" > works. > > Ahmad > > --- In [email protected], "Andreas Neumann" <neumann@> > wrote: > > > > Hi, > > > > indeed there are differences. Thanks for pointing this out. > > > > But how do you know what the correct behaviour is? Should one start > > again with stroking for each segment or continue from the last segment? > > > > As far as I know there is no strict definition for this problem in the > > spec. > > > > We will discuss this in the SVG working group and try to come up with > > a solution. > > > > One problem with SVG tiny implementations is that they don't have > > direct control of the rendering because they forward it to a graphics > > library. SVG full implementations can of course calculate the lines > > segments themselves, because they have more computing power available. > > > > We'll get back about this. > > > > Andreas > > > > --- In [email protected], "ACasualObserver" <svg@> wrote: > > > > > > I noticed that if there is path element that consists of more than one > > > segment and one segment is shorter than the first part of dasharray, > > > ASV connects the line segments. Corel and FireFox display correctly. > > > > > > 1- Is this a known bug? > > > 2- Is there anyway around it? > > > > > > Example: > > > > > > <?xml version="1.0"?> > > > <svg xml:space="preserve" viewBox="0 0 9000 6000" > > > xmlns="http://www.w3.org/2000/svg"; > > > xmlns:xlink="http://www.w3.org/1999/xlink"; > > > > <path style="stroke:#000000;fill:none;stroke-width:20; > > > stroke-dasharray:360,120;" > > > d="M4000 1000 L4000 1300M7000 1000 L8000 5000"/> > > > </svg> > > > > > > ----- To unsubscribe send a message to: [EMAIL PROTECTED] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ---- Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
