On 06/13/2012 04:27 PM, E. Liddell wrote: > In the case of this particular sample SVG, I think I do know what's going on, and > it's an Inkscape bug/unfeature, not anything to do with Trinity. > > Specifically, the portion of the SVG standard which deals with multiline text was > changed fairly late in the draft process, and Inkscape implements a version from > one of the earlier drafts rather than what made it into the standard. Therefore, > Inkscape's handling of flowed text is technically incorrect, and if you save a > file as "Inkscape SVG" there may be problems with some text. (There's a > second set of save options for something like "Plain SVG" or "Standard SVG" > which should be used for images containing text, or convert text to object before > exporting the file if it's going to be opened in something other than Inkscape.) Ah hah! We do have a svg expert among us :) Seriously, I've tried both inkscape and plain svg saves (I default to saving as "plain svg" just to be safe now) I haven't tried the text-to-object export yet, so that is something else to try. Great discussion E. I had no idea what the difference was between the various save options (still don't really understand it technically, but I do now understand the distinction) http://wiki.inkscape.org/wiki/index.php/Frequently_asked_questions#Are_Inkscape.27s_SVG_documents_valid_SVG.3F (and the FAQ below it) explain the distinction. It's VHS and Beta all over again, but it doesn't explain the go.svg issue as E pointed out. -- David C. Rankin, J.D.,P.E.