EdK Posted January 19, 2017 Share Posted January 19, 2017 New to Designer (and vector graphics in general). I have two simple vector-based images created in Autodesk Graphic (latest release). I exported them from Graphic as SVG files and opened the resulting SVG files in Designer. Here's the problem - both images, as viewed with Designer, differ from the original (e.g., compare before/after thumbnails for one of these below). Why? and how can I solve this? I'd rather not have to start from scratch in AD. If I had to guess, it looks as if using Graphic's Effects-options (drop shadow and the like) causes problems - just a guess and not sure what other incompatibilities are lurking. Excuse the possibly dumb question - learning.... Quote Link to comment Share on other sites More sharing options...
EdK Posted January 20, 2017 Author Share Posted January 20, 2017 Surprised there are no replies. Didn't realize I was diving into a deep unknown. I'll keep digging and report back... Quote Link to comment Share on other sites More sharing options...
EdK Posted January 21, 2017 Author Share Posted January 21, 2017 Still nothing. Next quiz will only contain easy questions.... B) Seriously - it is surprising that no one, especially Affinity-folks, have no insight/tips to offer on the subject of file format compatibility since it's an issue that's with us all of the time. Since I've heard nothing after two days I'll move on - lesson learned, just not the desired one. Quote Link to comment Share on other sites More sharing options...
MikeW Posted January 21, 2017 Share Posted January 21, 2017 It might help if you uploaded the as-exported SVG. R C-R 1 Quote Link to comment Share on other sites More sharing options...
EdK Posted January 21, 2017 Author Share Posted January 21, 2017 Thanks for the reply. Here's the SVG file as exported from Autodesk Graphic. It results in the right-most thumbnail, as shown in my OP, when opened in AD. Is this what you meant? Webitz Logo 2.svg Quote Link to comment Share on other sites More sharing options...
MikeW Posted January 21, 2017 Share Posted January 21, 2017 Yep, as exported from AutoDesk. I'll take a look in a few minutes. Quote Link to comment Share on other sites More sharing options...
Madame Posted January 21, 2017 Share Posted January 21, 2017 FWIW I downloaded your file. It looks different than the two examples above. Ie. it didn't import any dropshadows. Quote - Affinity Photo 2.3.0 - Affinity Designer 2.3.0 -Affinity Publisher 2.3.0 MacBook Pro 16 GB MacOS Sonoma 14.1.2 Link to comment Share on other sites More sharing options...
R C-R Posted January 21, 2017 Share Posted January 21, 2017 I tried viewing the downloaded example svg file in several browsers (Safari, Chrome, etc.) & they all show the file's appearance exactly like in AD. From this, I assume it is the svg export from Autodesk Graphic that is the problem, not AD. Quote All 3 1.10.8, & all 3 V23.0 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 Affinity Photo 1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7 Link to comment Share on other sites More sharing options...
R C-R Posted January 21, 2017 Share Posted January 21, 2017 FWIW I downloaded your file. It looks different than the two examples above. Ie. it didn't import any dropshadows. What did you use to view the downloaded file? Quote All 3 1.10.8, & all 3 V23.0 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 Affinity Photo 1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7 Link to comment Share on other sites More sharing options...
EdK Posted January 21, 2017 Author Share Posted January 21, 2017 I never downloaded the file from Graphic as an SVG until I did it this week in order to open it in AD. All previous downloads were PNG files to use in a website. Subsequent to the PNG downloads, I did the SVG download in order to see if Graphic's SVG file could be successfully exported and used in another program, AD in this case. Needless to say I was disappointed that the presumed compatibility wasn't there. I had hoped to use Graphic on my iPad Pro, AD on my PC and share graphics - with SVG seeming to be the only common format. Not looking to assign blame; trying to understand why standards aren't standard. Quote Link to comment Share on other sites More sharing options...
MikeW Posted January 21, 2017 Share Posted January 21, 2017 Excepting that I get the missing font message--the font name in the SVG is different than my ITC version--the SVG comes into AD like Madam's screen shot. So like your second screen shot of inside AD. Yep, it's missing the drop shadows and outer glow. Those things are easy to replace in AD. Some applications like InkScape will bring them in properly, however, if that logo is resized it will affect the resolution and so those bitmap type effects should be done in the end application and saved in that application's native file format so the design can be repurposed. The lines, they are in the SVG code if that is one of the differences you are talking about. A billion lines make up that grid. No idea if you want them there or not. SVG is a text format. Open that SVG file up and take a look at it. As you have the font, that too is easy to reset. The font names in the SVG file are not what technically you used in the Autodesk app. Which is why you too get font substitution--and InkScape will also likely substitute it. Here's my method of sharing files between applications. I prefer to draw in XDP--even if I have to return an AI file to the client. So I will do everything in XDP that I can, which typically means no bitmap effects, then port to AI and finish it off there. It's what I do even with bitmaps--if I need to return a PSD, I will still use something else and either my PSD export is fine, or if something PS specific needs done, I'll finish it off in it. I see your issue the same. Bitmap effects should simply be done in the final editing application. Mike Quote Link to comment Share on other sites More sharing options...
R C-R Posted January 21, 2017 Share Posted January 21, 2017 The problem with standards is to maximize compatibility between apps & operating systems they are usually designed so that support of some features are optional. Typically, a standard will specify some things that must be supported & others that may be ignored but must be handled without causing problems by or for a standards compliant app. Quote All 3 1.10.8, & all 3 V23.0 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 Affinity Photo 1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7 Link to comment Share on other sites More sharing options...
Madame Posted January 21, 2017 Share Posted January 21, 2017 What did you use to view the downloaded file? I was viewing the SVG in affinity designer, (this was a screenshot). There was no missing font, as the text is converted to curves. Quote - Affinity Photo 2.3.0 - Affinity Designer 2.3.0 -Affinity Publisher 2.3.0 MacBook Pro 16 GB MacOS Sonoma 14.1.2 Link to comment Share on other sites More sharing options...
EdK Posted January 21, 2017 Author Share Posted January 21, 2017 I thank one & all for your input. As a graphics-newbie it's what I hoped to learn. MikeW, the lines were there because I mistakenly exported without turning off the (grid) background. As for the font (American Typewriter), I'll try this again with a standard font to avoid the substitution and see what happens. A special thanks for describing your workflow. R C-R, I'll dig around and see what the required vs. optional elements are for SVG. I did this regularly with browser HTML compatibility. Slipped my mind here. I sent Graphic support an email, complete with PNG before/after and the SVG export from Graphic. I'll share their response when/if it arrives. Thanks again. Quote Link to comment Share on other sites More sharing options...
MikeW Posted January 21, 2017 Share Posted January 21, 2017 I was viewing the SVG in affinity designer, (this was a screenshot). There was no missing font, as the text is converted to curves. The text in the center is live text. The white outline is a curve though. Quote Link to comment Share on other sites More sharing options...
MikeW Posted January 21, 2017 Share Posted January 21, 2017 I thank one & all for your input. As a graphics-newbie it's what I hoped to learn. ... Thanks again. You're welcome. Sorry getting a response was a trying experience. Quote Link to comment Share on other sites More sharing options...
R C-R Posted January 21, 2017 Share Posted January 21, 2017 I was viewing the SVG in affinity designer, (this was a screenshot). There was no missing font, as the text is converted to curves. Odd. When I opened the file in AD, I got a missing font warning, & the file looked like the righthand screenshot in the first post. Were you using the latest beta or the retail version? Quote All 3 1.10.8, & all 3 V23.0 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 Affinity Photo 1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7 Link to comment Share on other sites More sharing options...
EdK Posted January 21, 2017 Author Share Posted January 21, 2017 As promised, here's the reply from Autodesk. It's as I guessed in my OP - Graphic doesn't export shadows (but they will in the future). Live & learn.... Any thoughts regarding their PDF recommendation (which I'll try shortly)? =========================== Hi Ed,Thanks for writing and sorry for the delayed reply. At this time Graphic will not export the shadow of the objects — this is something we will improve in a future update. You can however simulate the same by applying an 'Outer Glow' effect from the 'Appearance: Effects' panel and also reducing its opacity. See the attached file for a possible example.If the Appearance: Stroke panel is not visible, click on the ⓘ icon in the upper right corner of the window:IMAGE DELETED; FORUM DOESN'T SUPPORTBefore exporting as SVG you can also convert the text to outlines, to make sure it looks the same in the SVG. This command is found in the 'Modify' menu.PDF however is the universally accepted format for interchange of files with other apps, and we recommend using it if possible.Free Graphic resources and Mac plugins can be downloaded from http://graphicshapes.com Graphic Tutorials: http://graphic.com/tutorials/ If you encounter any other difficulties, support is here — just let us know and we're glad to help.Thanks for using Graphic!Cheers,BogdanBogdan Oancea - Autodesk, Inc. Quote Link to comment Share on other sites More sharing options...
MikeW Posted January 21, 2017 Share Posted January 21, 2017 PDF should be fine. It is what I would tend to use if I had effects that I wanted when importing to something else and also wanted those effects for a FPO object so I could replicate it "properly." About the drop shadows. This is as opened in InkScape... Now, the drop shadows are not a property of the object any longer. But they are there. One can look inside the SVG to see that the Blur property is present. <filter id="Shadow_22"> <feGaussianBlur in="SourceAlpha" stdDeviation="2.5"/> <feOffset dx="0" dy="2" result="offsetblur"/> <feFlood flood-color="#000000"/> <feComposite in2="offsetblur" operator="in"/> </filter> Mike Quote 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.