The SVG file contains a lot of coordinates, so I’m not sure if that’s the issue or what. We’re running Omeka version 2.3 and the latest version of Neatline (2.5.1).
When I put this SVG file into Oxygen, I’m getting parsing errors–attributes and elements that aren’t properly declared, mostly. I’m reasonably certain that it’s the structure of the file that’s the problem, rather than the size. Could you try editing the XML to correct those errors and give it another try?
Thanks for the response. I’m also getting the parsing errors, but confused as to the exact problem. For example, it tells me “Error at line 14, column 25: no declaration found for element ‘svg’” and yet a few lines above I see what appears to be a clear declaration of the svg element:
… But perhaps this is outdated? I’ll dig around some more, but I’m confused as to what the issue seems to be. Clearly, though, it’s the XML file and not Neatline.
Argh. I never did figure this out… I really am not sure what to do. Any recommendations for good documentation online regarding troubleshooting svg errors? I have downloaded and am using a trial version of Oxygen, but I have no idea how to fix the errors in the file, all of which are phrased similar to: "Attribute “xmlns:dc” is not allowed to appear in element “svg” ". I downloaded Inkscape, opened the svg file in it, and saved as “optimized” svg to see if that helps, but it doesn’t - same parsing error in Neatline, same errors in Oxygen. Yet when I paste this same svg file text into this site, the image appears fine in the browser. Honestly I am at a total loss - from what I’ve read online, there should be no problem with xml namespaces in svg elements. Or am I missing some kind of other declaration to allow svg elements to have namespace declarations?
