Re: [xslt] libxslt escaping urls when outputting HTML

[Philipp Dunkel <philipp dunkel org>]

If you remember we had this discussion about a month ago as well. Back
then I gave up.
I just wanted you to think about one thing:
Invention is using things that exist in a totally unpredicted new way.
There seem to be a lot of people having troubles with URL-escaping, some
of them resorting to patching libxslt (I did for my own use, but did not
distribute since I don't want to fork or even put down your great work,
especially since in terms of experience and knowledge your are by far
the better programmer). Now This part of libxslt is not really that much
of a core functionality, that it really matters that much. And the
behavior that is currently there is absolutely the right thing as a
default. But if it's not really a core issue, why not make it a runtime
option. I could, during initialization just call IllegalEscaping(1); and
the URL-escaping would be turned of and left up to me to do within the
XSL.
I need it and modified libxslt according to my needs, but is that the
right way to do things for an issue like that? I don't think so. So why
not take a more practical approach and make this change choosable at
init-time. It would eliminate this discussion and make everyone happy: A
standards compliant parser by default. WIth some neat extras if you
really need them for a specific instance.
Now this is just a thought, and I presume you have had it before.Non the
less, I would be quite interrested in hearing your reasoning about why
not to follow a path like that.

TTY Philipp

On Fri, 2002-09-13 at 14:14, Daniel Veillard wrote:
> On Fri, Sep 13, 2002 at 01:36:45PM +0200, Peter Jacobi wrote:
> > Hi Daniel,
> > 
> > I'm disagreeing with you in this case.
> 
>   Hum, I'm not sure.
> 
> > > > Uhm, forgive me if I am mistaken, but isn't "," an ASCII character?
> > > 
> > >   Hum, maybe it wasn't precisely the right thing to point to, but
> > > RFC 2396 is the core spec in this respect. And ',' is in the reserved set.
> > > 
> > 
> > Characters in the reserved set may occur in a RFC2396 URI
> > and in fact an URI changes meaning, whether it is escaped or not,
> > so it's not good to always escape them. 
> 
>   reread what I said in my first answer ... It depends on the context
> and in the specific case he pointed out this might not have been escaped.
> but to not rely on it being left as-is.
> 
> > The application generating the URI must have some clue whether
> > one particular ',' needs escaping or not.
> 
>   Yes, depends on the part of the URI where it is present.
> 
> Daniel
> 
> -- 
> Daniel Veillard      | Red Hat Network https://rhn.redhat.com/
> veillard@redhat.com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
> http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
> _______________________________________________
> xslt mailing list, project page http://xmlsoft.org/XSLT/
> xslt@gnome.org
> http://mail.gnome.org/mailman/listinfo/xslt