XML incompatibility, SnipSVG being unstable, and styles on the HEAD section

Unread post by **Tim Green** » Fri Oct 18, 2024 6:11 am

Hi Gianni,

Thanks for reporting this, I can reproduce it on a MacBook Pro with M3 Max. The first time it happens it gets triggered if you resize quickly. After that it happens more easily. We're looking into it.

gianniangelini · Mon Oct 21, 2024 9:58 am

Hi,

just adding a piece of information that can maybe be useful to know...

I asked a colleague to test the app on a Windows laptop, and she had no issues at all. Is maybe something related to the Mac's version only?? Do you want me to run specific tests on my Mac?

Thanks!

Unread post by **Tim Green** » Tue Oct 22, 2024 2:52 pm

gianniangelini wrote: Mon Oct 21, 2024 9:58 am I asked a colleague to test the app on a Windows laptop, and she had no issues at all. Is maybe something related to the Mac's version only?? Do you want me to run specific tests on my Mac?

No, that's OK, we are already working on it. The Mac systems the developers were testing on are older and slower M1 systems, and the resize error you are seeing wasn't happening there, but I can reproduce it on my M3 Max MacBook Pro. So it appears to be a timing issue. There is also a compatibility issue with Sequoia that needs to be addressed. We are working on both issues and an update will be coming soon.

Thu Nov 07, 2024 3:54 pm

Hi Gianni,
Please give this updated (beta) version a test run:

https://www.helpandmanual.com/download/snipsvg-v150.dmg

The resize error should be gone. If it still persists on your machine, we'd like to know a.s.a.p.

gianniangelini · Tue Nov 19, 2024 5:23 pm

Hi!

I've just tested this last version. It works flawlessly now! I've resized, typed text, added colors etc., no issues.
I'll use it in production as much as possible, and keep you posted if I find anything else of interest.
Thank you so much!

As a side note, I've deleted the <style> section from the head of the XML code, just to see what happens, and I noticed that the file still shows up complete in SnipSVG, while it's not fully displayed in the browser (see screenshot). You know I'm a bit fixated with "clean code", and I would like to see all styles inline for compatibility... so I'm just wondering, if your code can display an image in SnipSVG without the style section in the header, why not getting rid of it altogether? Wouldn't it be a positive in the long term? Just contributing ideas, you go your way, of course...

Thanks again for all your hard work, and for your ready support! Much appreciated!!

Tue Nov 19, 2024 5:47 pm

deleted the <style> section from the head of the XML code, just to see what happens

I suggest to keep it, it's there for a reason

gianniangelini · Tue Nov 26, 2024 5:09 pm

Hi,

some more issues... (version 1.5.400)

1) I tried to type hex code for a color... I can't. Are color code fields read only? (see screenshot_1.png) If yes, is that possible to make them editable? I had to type an hex color code manually into the XML code...
2) Again issues with visualizing text on SVG: see screenshot_2).

File code:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<svg width="800" height="600" viewBox="0 0 800 600" role="img"
xmlns="http://www.w3.org/2000/svg"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xpl="http://www.helpxplain.com/namespaces/xplain"
version="1.1">
<style>
a { color: #0070C0 }
body {
margin: 0;
padding: 0;
}
p {
line-height: 1.2em;
margin: 0;
padding: 0;
}
h1,h2,h3 {
line-height: 1.2em;
margin: 0 0 0.5em 0;
padding: 0;
}
ul {
margin-top: 0; margin-bottom: 0;
}
ol {
margin-top: 0; margin-bottom: 0;
}
li {
line-height: 1.2em;
}
</style>
<g id="shape1" class="xplitem shape" transform="translate(317.7,185.45)" style="--xpl-w:170.32;--xpl-h:170.32;--xpl-valign:middle;">
<ellipse fill="#F6FFF4" fill-rule="evenodd" stroke-width="2" stroke="#000000" cx="85.16" cy="85.16" rx="84.16" ry="84.16"></ellipse>
<switch>
<foreignObject x="20" y="6.66" width="130.32" height="157"><body xmlns="http://www.w3.org/1999/xhtml"><p style="text-align:center;font-family:Arial;font-size:36px"><span style="font-size:128px">i</span></p></body></foreignObject>
<g style="font-family:Arial, Helvetica, sans-serif;font-size:128px;fill:#000000;text-anchor:middle;--xpl-margins:18,0,18,0;"><text x="85.16" y="134.66" dy="-0.12em">i</text></g>
</switch>
</g>
</svg>

Thanks!

Wed Nov 27, 2024 12:17 am

The hex field is read-only.

As for the text glitch: this is the same error as before. In version 1.5 this is fixed already. Did you create this object with an older version? Or was the object copied from an file created with an older version? Or was the object copied from the favorites gallery? It must be something like that. Same cure as before for existing objects: apply a different font size, then reapply the old one.

gianniangelini · Wed Dec 11, 2024 4:05 pm

Hi Alexander!

I'm attaching a short video to show the issue with font size (apparently, it happens only with big font size??) - mp4, added fake svg extension in order to be able to upload it... - sorry, just realized it doesn't get uploaded: is there a way to send you an mp4 (it's compressed, 3 MB)?

About the hex code field... A recurrent situation for professional tech writers is having hex code to use from a style guide, so it would be important to be able to paste those codes in an editable text field. Is that a feature you would consider adding?

Thanks!

BertholdL · Unread post by **BertholdL** » Fri Dec 13, 2024 9:01 am

The hex field is read-only.

Is it? In my SnipSVG Vers. 1.5.0 Build 400 (Win) I can enter a hex number in the color dialog. What could be the reason?

BertholdL · Unread post by **BertholdL** » Fri Dec 13, 2024 10:04 am

Hi Gianni,

as long as you cannot enter the hex number, you can use a converter and enter RGB:
https://www.rgbtohex.net/hex-to-rgb/

gianniangelini · Thu Mar 06, 2025 6:25 pm

BertholdL wrote: Fri Dec 13, 2024 10:04 am Hi Gianni,

as long as you cannot enter the hex number, you can use a converter and enter RGB:
https://www.rgbtohex.net/hex-to-rgb/

Hi BertholdL!

Interesting indeed!
I work on a Mac, and I confirm I can not edit the exadecimal value. I can not edit the RGB, either.
By "EDIT", I mean typing the value using my keyboard. I can still set the RGB by using the arrows.

Is that maybe a Mac-specific issue??

The problem with converting to RGB is, as I guess you know, that color spaces never match perfectly. Of course, that's pretty irrelevant, from a practical point of view, but I think being able to edit the exa value (for example, by copying and pasting an exa value from a style guide) should be a standard feature on professional graphic tools.

That was my point.

Thanks!

Unread post by **Tim Green** » Fri Mar 07, 2025 9:34 am

Hi Gianni,

Thanks for reporting this. I just checked and it seems that the hex field in the color picker on the Mac version is currently read-only. We're looking into this

gianniangelini · Fri Apr 11, 2025 4:20 pm

Hi,

Thanks for releasing a new version, I'm trying it out (2.0.491)! This tool is very interesting, and it's nice you keep updating it. As I previously wrote, SVG is a very interesting format in technical communication, definitely undervalued, so thank you so much for investing time and effort in it.

I just want to confirm that there are still issues with paragraph spacing when changing font size. I'm not attaching any screenshot, because it's basically the same issue we've already discussed in this thread, easy to check by changing font and see if the web browser displays like the app.

I hope it can help!

Thanks!

Help+Manual Forums

XML incompatibility, SnipSVG being unstable, and styles on the HEAD section

Re: XML incompatibility, SnipSVG being unstable, and styles on the HEAD section

Re: XML incompatibility, SnipSVG being unstable, and styles on the HEAD section

Re: XML incompatibility, SnipSVG being unstable, and styles on the HEAD section

Re: XML incompatibility, SnipSVG being unstable, and styles on the HEAD section

Re: XML incompatibility, SnipSVG being unstable, and styles on the HEAD section

Re: XML incompatibility, SnipSVG being unstable, and styles on the HEAD section

Re: XML incompatibility, SnipSVG being unstable, and styles on the HEAD section

Re: XML incompatibility, SnipSVG being unstable, and styles on the HEAD section

Re: XML incompatibility, SnipSVG being unstable, and styles on the HEAD section

Re: XML incompatibility, SnipSVG being unstable, and styles on the HEAD section

Re: XML incompatibility, SnipSVG being unstable, and styles on the HEAD section

Re: XML incompatibility, SnipSVG being unstable, and styles on the HEAD section

Re: XML incompatibility, SnipSVG being unstable, and styles on the HEAD section

Re: XML incompatibility, SnipSVG being unstable, and styles on the HEAD section