Guest Posted August 6, 2021 Share Posted August 6, 2021 I was looking at the Designer 1.10 release notes and was pleasantly surprised to see 'Improved SVG import/export' among them. However, I'm really curious as to what that actually entails as I'm not really seeing anything new. I'm also still flummoxed by the SVG export options; export, small size, high-quality, and flatten. My best guess at what each of these do is the following: export: standard, unminified output small size: minified output (why not simply call it minified) high quality: scaled up and minified (why on earth is it scaled as it's vector? What exactly is high quality SVG output?) flatten: rasterize everything and base64 encode it in a PNG (why not call it rasterize, and why bother exporting to SVG at all?) I was also hoping to see the Affinity SVG -> Figma issue resolved, but all Affinity exported SVGs are still importing into Figma at 1 x 1px. Also, the additional namespace xmlns:serif="http://www.serif.com/" declaration is still there, along with silly serif:id="example" so all SVG docs exported from Affinity products still do not pass validation (ie. there is no attribute "serif:id"). There is an existing attribute id in the SVG spec, why not just use that? Do we really need a duplicate namespaced attribute? Quote Link to comment Share on other sites More sharing options...
Staff Dan C Posted August 10, 2021 Staff Share Posted August 10, 2021 On 8/6/2021 at 12:50 PM, Bryan Rieger said: I was looking at the Designer 1.10 release notes and was pleasantly surprised to see 'Improved SVG import/export' among them. However, I'm really curious as to what that actually entails as I'm not really seeing anything new. I can confirm that the following lines from the RC2 Designer Beta are the fixes being referred to here - On 8/1/2021 at 6:21 PM, MattP said: - Fix for SVG export failing to correctly deal with stretched text when the user selects 'flatten transforms' - Fix for SVG import not functioning correctly with whitespace between the keyword "translate" and the following opening bracket There is also another line for "SVG Import and Export tweaks", unfortunately I don't have any more information regarding this line currently, so I'm checking with our team now On 8/6/2021 at 12:50 PM, Bryan Rieger said: I was also hoping to see the Affinity SVG -> Figma issue resolved, but all Affinity exported SVGs are still importing into Figma at 1 x 1px. As far as I understood, unticking 'SetViewBox' when exporting to SVG allows the file to be opened in Figma correctly - can you please try this for me and let me know? On 8/6/2021 at 12:50 PM, Bryan Rieger said: Also, the additional namespace xmlns:serif="http://www.serif.com/" declaration is still there, along with silly serif:id="example" so all SVG docs exported from Affinity products still do not pass validation (ie. there is no attribute "serif:id"). There is an existing attribute id in the SVG spec, why not just use that? Do we really need a duplicate namespaced attribute? Unfortunately I'm not technically well versed enough in regards to SVGs to comment on this, however I'm aware that many other users have reported this previously and it is already logged with our developers, so I'll be sure to 'bump' this now for you! Quote Please note - I am currently out of the office for a short while whilst recovering from surgery (nothing serious!), therefore will not be available on the Forums during this time. Should you require a response from the team in a thread I have previously replied in - please Create a New Thread and our team will be sure to reply as soon as possible. Many thanks! Link to comment Share on other sites More sharing options...
Guest Posted August 10, 2021 Share Posted August 10, 2021 7 minutes ago, Dan C said: As far as I understood, unticking 'SetViewBox' when exporting to SVG allows the file to be opened in Figma correctly - can you please try this for me and let me know? Thanks for following up Dan! Yes, unticking More -> SetViewBox did indeed fix the Figma problem. Might be an idea to bubble that up to be more obvious somehow, as I definitely wouldn't have associated that it was the solution to the Figma import size problem. Quote Link to comment Share on other sites More sharing options...
Staff Dan C Posted August 10, 2021 Staff Share Posted August 10, 2021 No problem at all, thanks for your feedback! I do agree this could be made clearer - for example an FAQ post here on the forums would be a good place to start for other users searching for similar issues. I'll be sure to suggest this to the team Quote Please note - I am currently out of the office for a short while whilst recovering from surgery (nothing serious!), therefore will not be available on the Forums during this time. Should you require a response from the team in a thread I have previously replied in - please Create a New Thread and our team will be sure to reply as soon as possible. Many thanks! Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.