For context:
I am programatically generating SVG files and it would seem that “line” elements are problematic for the uploader and simply gives me the error: There was an error while uploading this file It may work if you try again later. If the issue persists, email the file to support@glowforge.com for help.
Now this SVG opens in browsers and Affinity Designer with no issues.
I can also export from Affinity Designer as SVG for Web and that file will upload just fine.
The major differences in the two files are some headers and the lines are converted to paths.
So the problem becomes that while I can just run it through Affinity Designer each time, it’s simply not efficient. That brings me to my question(s)…
Question(s):
Is there any documentation that specifies which SVG elements are supported and which are not?
Is there anyway to get verbose output from the file validation algorithm?
Is there anyway to get a standalone file validation application or script for those who want to quickly validate a file against the Glowforge application?
Are you having trouble with the line elements themselves, or perhaps the new line characters that are being used? And what makes you suspect these line elements?
I agree that access to a spec and output would be handy, but it doesn’t sound necessary here. Can you take a known-good svg and compare it to your generated one? There should be either a visual or bytecode difference between the two.
Without more details, I’d suspect malformed svg code in your generated file, which could be validated as above.
I think you may be onto something. I was going to try and upload the two files here (into this post) but my programmatic one, despite being displayed without issue in a few browsers and affinity designer, is kicked back by the forum. The error I get in the forum is something along the lines of not being able to determine size. That warning is along the lines of the feedback which I think would be super useful to people trying to upload files to the app.
However, I do understand that the more verbose warnings can make things worse for some users.
I initially suspected the lines as the affinity designer output is a pretty similar file with path elements instead of line elements. However, there is also the addition of a small preamble that the app might be looking for.
I will try and include the preamble and see if I can narrow down exactly which part is upsetting the app.
I’m not sure how hard this needs to be. Here’s a plain SVG with a single rectangle. After the header, it has a simple rectangle with x,y, height and width. If you replicate the bulk and put your own elements into the body, they should load just fine. I’ve manually edited SVG files many times, there’s not much “magic” in them.
And you’re absolutely right @eflyguy … not much magic in there which is why this stumped me.
My guess is they are one of the few applications actually validating SVG syntax and hence need the DTD, which makes the process much easier.
All in all, thanks everyone who helped kick start my brain.
