Forum Discussion
Svg files for SL360 on the roadmap?
In addition, the PPT method is only for the simplest of images--from my testing, more complex images will often yield poor results. And sometimes PowerPoint's import will cause translation issues itself that get "inherited" when brought into SL360.
At best, what we have now is a fair but inadequate "band-aid."
Direct SVG import with perfect results from the original SVG is needed--badly. ASAP. Yesterday if possible. ;) :)
Hi Gerry,
I have a quick question for you. I was also on the bandwagon for this update, and now that they have incorporated it, my workload has doubled! I used to use the workaround with PPT and got very good at it. Now I cannot use that method any longer, and all SVGs come in as un-manipulatable (sorry for that word!) objects! I cannot change colors, break them apart, or anything that I could do before with a PPT > SL SVG. Any ideas on what I can do? Do you know any way to get these images to be changeable once in SL? Any ideas welcomed!
Thanks,
Reina
- DarrenNash3 years agoCommunity Member
Thing to remember here is that you are bringing an svg into PowerPoint, which then converts it to a PowerPoint editable graphic, which you then can recolor, then save out as a png for SL360. So the SVG is not being imported into SL360 but you are using PowerPoint simply as an image editor and convertor. If you use illustrator on a daily basis then using PowerPoint is pointless. Using an SVG directly in SL360 would mean resizing in the slide and no loss of quality at any size or resolution. Once in SL360 you cannot edit the png files colors.
- DiarmaidCollins3 years agoCommunity Member
Hi Darren. That's not at all what happens (happened) with SVGs and Powerpoint. You mention in your next point that the example I use could easily have been created in Storyline, and yes, that is true, but that is not what the example was about.
The example clearly illustrated that, at the time, SVGs could be imported into Powerpoint and then the Powerpoint slide could then be imported into Storyline and all the vector goodness of the SVG could be retained, and, more importantly, edited within Storyline EXACTLY like a shape because that's what it was. It was most definitely NOT a 'save as PNG' option as you describe.
This was a methodology actually endorsed and described by Articulate, so you're not really helping Access Pointe with your suggestion.
The problem Reina is describing is the unfortunate by-product of Articulate attempting to be super-clever and simply adopt native SVG file insertion but it breaks so many useful functionalities that is not an 'acceptable' solution, compared to what was offered before.