Ian Jeffray

NAPS2 is called NASP2 in Windows - why? Error?

I confirm all characters entities tested work fine in Chrome, Firefox, Edge, Photoshop, Inkscape. Great! Thanks.

A more authoritative reference to the XML spec and defined entities: https://www.w3.org/TR/xml/#sec-predefined-ent

Update - as far as I can tell, SVG follows baseline XML encoding rules. https://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references#Character_reference_overview Thus the only named entities for encoding are lt gt amp quot and apos. Everything else should be ampsersand-hash encoded. Thus, frasl should definitely be removed from zint.

Hi Robin, This does indeed fix the warning with GCC 8.2 Thanks, Ian From: Robin Stuart g3rrk@users.sourceforge.net Sent: 30 October 2019 07:53 To: [zint:tickets] 168@tickets.zint.p.re.sourceforge.net Subject: [zint:tickets] #168 trivial - malloc warning using gcc 8 on linux Hi Ian, I have added a small patch which should overcome this warning, although in practice rs_init_gf is never called with a value which would make this a problem. When you get the opportunity I would appreciate it if you could...

Hi Robin, Well, this is curious. & " < > are all good. But frasl. it causes the SVG to fail to render in both Firefox and Chrome. And Inkscape just quietly ignores it. The SVG is well-formed as far as I see, but there must be some "interesting" rules for what entities are supported within SVG, I guess. ⁄ works fine, as does a bare backslash. Remove special processing for backslash, then, I guess. How odd. Ian From: Robin Stuart g3rrk@users.sourceforge.net Sent: 30 October 2019 08:47 To: [zint:tickets]...

trivial - malloc warning using gcc 8 on linux

Not tested it yet, but patch looks sane. Perhaps quot and frasl should be handled this way too... c.f. https://www.whatsmyip.org/html-characters/