Skip Menu |

This queue is for tickets about the SVG CPAN distribution.

Report information
The Basics
Id: 22327
Status: open
Priority: 0/
Queue: SVG
People
Owner: ronan [...] cpan.org
Requestors: Jan.Ploski [...] offis.de
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Fri Oct 20 04:06:37 2006 Jan.Ploski [...] offis.de - Ticket created
Subject: Unescaped ampersands in xlink:href attributes
Date: Fri, 20 Oct 2006 10:06:01 +0200
To: bug-SVG [...] rt.cpan.org
From: Jan Ploski <Jan.Ploski [...] offis.de>
Reporting a bug against SVG-2.33: The ampersand characters in xlink:href are output unescaped by SVG::xmlify. This is against the XML specification and not tolerated by the Adobe SVG viewer.
  Thu Sep 20 15:28:59 2007 ronan [...] cpan.org - Taken
  Fri Sep 21 08:19:04 2007 ronan [...] cpan.org - Correspondence added
This is by design, not a bug. It is up to the implementer to escape their own strings when they want to, and I can not assume what they want. Early versions of the module used to automatically escape characters and too many people (correctly) complained, so I took it out. If the user insists on sending unescaped text, then I assume that the user knows what they want. The module has an xml-escaping method $svg->xmlescp($string) to assist people who want escaping. Refer to the POD for assistance for versions after 2.26. Ronan
  Fri Sep 21 08:19:10 2007 The RT System itself - Status changed from 'new' to 'open'
  Fri Sep 21 08:19:16 2007 ronan [...] cpan.org - Status changed from 'open' to 'rejected'
  Sat Jun 05 16:22:34 2010 jpl [...] plosquare.com - Correspondence added
From: jpl [...] plosquare.com
Automatic escaping should be an option. Right now you are forcing the client to implement escaping in EVERY location where a -href (or any other attribute, for that matter) is passed to SVG. It smells of broken abstraction - I want to talk to an SVG generator, not to some low-level XML-emitting module which deals with raw bytes. To make things worse, the signature of xmlescp was changed between 2.49 and 2.50, so it is not easy to safely apply your proposed workaround. On Fri Sep 21 08:19:04 2007, RONAN wrote: Show quoted text
> This is by design, not a bug. > > It is up to the implementer to escape their own strings when they want > to, and I can not assume what they want. Early versions of the module > used to automatically escape characters and too many people (correctly) > complained, so I took it out. > > If the user insists on sending unescaped text, then I assume that the > user knows what they want. > > > The module has an xml-escaping method $svg->xmlescp($string) to assist > people who want escaping. Refer to the POD for assistance for versions > after 2.26. > > Ronan
  Sat Jun 05 16:22:35 2010 The RT System itself - Status changed from 'rejected' to 'open'
  Wed May 16 02:51:43 2012 SZABGAB [...] cpan.org - Correspondence added
Could you please send a test case and maybe even an implementation for such *optional* behavior? Please, fork the repository here: https://github.com/szabgab/SVG