title: Understanding parsing SVG file format
body: <p>First off, <a href="https://gist.github.com/1234809" rel="nofollow">gist here</a></p>
  
  <p>Map.svg in the gist is the original Map I'm working with, got it off wikimedia commons.</p>
  
  <p>Now, there is a land mass off the eastern cost of Texas in that original svg.  I removed it using Inkscape, and it re-wrote the path in a strange new way.  The diff is included in the gist.</p>
  
  <p>Now this new way of writing the path blows up my parser logic, and I'm trying to understand what happened.  I'm hoping someone here knows more about the SVG file format that I do.  I will admit I have not read through the entire SVG standard spec, however the parts of it I did read didn't mention anything about missing commands or relative coordinates.  Then again I may have been looking at the incorrect spec, not sure.  </p>
  
  <p>The way I understood it, SVG path data was very straight forward, something like this:</p>
  
  <p><code>(M,L,C)[point{n}] .... [Z]</code> then repeat ad-nauseum</p>
  
  <p>Now the part I'm trying to understand is this new Inkscape has written out what seems like relative coordinates, without commands like L, or L being implied somehow.  My gut is telling me what has happened here is obvious to someone.  For what it's worth I'm doing my parsing in C.</p>