Skip Menu |

This queue is for tickets about the Syntax-Highlight-Perl-Improved CPAN distribution.

Report information
The Basics
Id: 7984
Status: open
Priority: 0/
Queue: Syntax-Highlight-Perl-Improved

People
Owner: Nobody in particular
Requestors: allenday [...] ucla.edu
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 1.01
Fixed in: (no value)



Subject: <, >, & not escaped
you need to escape html metacharacters, e.g. '<' -> '&lt;'. i tried using this module from a CGI and to display the CGI's own source code in its output, and this bug botched it. i can do a post-highlight s///, but then some of the coloring goes away. would be better to do this internally.
From: davidcyl [...] cpan.org
[ALLENDAY - Tue Oct 12 23:37:55 2004]: Show quoted text
> you need to escape html metacharacters, e.g. '<' -> '&lt;'. i tried > using this module from a CGI and to display the CGI's own source > code in its output, and this bug botched it. i can do a post- > highlight s///, but then some of the coloring goes away. > > would be better to do this internally.
It's in the documentation... Substitutions Using define_substitution(), you can have the formatter substitute certain strings with others, after the original string has been parsed (but before formatting is applied). This is useful for escaping characters special to the output mode (eg, > and < in HTML) without them affecting the way the code is parsed. You can retrieve the current substitutions (as a hash-ref) via substitutions().
On Tue Oct 12 23:51:41 2004, guest wrote: Show quoted text
> It's in the documentation...
So can we close the ticket?
Subject: Re: [rt.cpan.org #7984] <, >, & not escaped
Date: Tue, 1 Feb 2011 15:22:38 -0800
To: bug-Syntax-Highlight-Perl-Improved [...] rt.cpan.org
From: "Allen Day, PhD" <allenday [...] ucla.edu>
yes On Mon, Jan 31, 2011 at 7:04 PM, Mike Doherty via RT < bug-Syntax-Highlight-Perl-Improved@rt.cpan.org> wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=7984 > > > On Tue Oct 12 23:51:41 2004, guest wrote:
> > It's in the documentation...
> > So can we close the ticket? >