Forum Discussion
Hello everyone,
Thank you for these valuable pieces of information. It looks like the focus of the thread got steered towards issues with SVG, but there seem to be a few different (but related) issues across the different posts.
I would like to start with the issue presented by Mark since he got this thread going. The degradation observed here is the scaling between the original image and the published output. EDIT/Rephrased to avoid confusion: "Unlike vector image formats like SVGs, EMFs, or WMFs, raster image formats like PNGs and JPGS will suffer a loss of quality when scaling."
Screenshots in general are best displayed without any scaling. As an example, Here is a basic html page referencing a screenshot of a Wikipedia page taken on a 1920 x 1080 monitor without using Storyline. If the page is viewed in full screen on a monitor with the same resolution, there is little to no degradation. However, once the browser is resized down, the degradation starts to manifest as early as 80%. If we take the same page, and view it on a 1366x768 display, the text becomes barely readable while the images are still ok. Our best practice document suggests to use images that do not need to be scaled to mitigate the loss of quality in the published output. Zoom images can also be used to display images at their original dimensions.
Matthew, thanks for breaking down the SVG problems into different points. For 1 and 2, would you be able to attach the raw SVG file here so that we can take a closer look? If not, you may use the same upload link in the support case to send it to us privately. For point number 3, this is something that we are aware of and are currently working on. I’ll skip number 4 because we cannot reproduce the issue either. Point number 5 is expected behavior for SVGs that have transparent areas. There is nothing being “hit” which is why the state is not being triggered, much like how an illustration with non-filled areas behaves. You could try filling these areas within the SVG with a solid color to get the behavior you desire. Point number 6 is definitely not a feature request and is something we will fix. Thanks for bringing that to our attention! Cropping SVGS (point 7) on the other hand is a feature request that we are not working on currently.
And thank you Diarmaid for sharing that helpful tip along with your feedback about SVGs. I'd like to assure you that these points have made their way to support and have been made aware of the issues highlighted in this thread.
- MarkKirby-c9f943 years agoCommunity Member
Can you post a link to "the same page, and view it on a 1366x768 display, the text becomes barely readable" so we can compare (otherwise what was the point of posting the wiki page link? Of course none of this solves the problem.