Re: [xslt] output escaping (again!)



On Sun, Mar 23, 2003 at 06:07:34PM -0500, Bruce Miller wrote:
> Daniel Veillard wrote:
> > On Sun, Mar 23, 2003 at 03:47:06PM -0500, Bruce Miller wrote:
> >>The following two similar URI's are _different_ (and maybe invalid):
> >>  (2)  data:text/plain%2CHello%2C%20World   (No <data> part)
> >>  (3)  data:text/plain,Hello, World     (space & 2nd comma not allowed)
> > 
> >   Spaces are not allowed, not negociable. Maybe in IRI though 
> > I do think it's a bad idea and I'm not the only one !
> 
> Well, of course that was the point: Only (1) was valid!
> 
> The space, base64, etc are all red herring issues 
> (not that I'm accusing you of intentionally sidetracking me).
> 
> Here's a simpler example to get to the point:
>   (4) data:text/plain,Hello
>   (5) data:text/plain%2CHello
> 
> Case (4) is valid, but libxml won't let me create it.

  As I say and repeat, it's fixed in CVS.

> Case (5) is INVALID -- rfc2397 _requires_ the "," and 
> data component --- libxml creates invalid URLs!! :>

  what can I say ?

> >>Alas, str:encode-uri isn't implemented in libxml, nor anywhere else, according
> >>to http://www.exslt.org/.
> > 
> > 
> >  wrong it's available at the xsltproc level !
> 
> Indeed it _is_ there now! [I didn't reallize how old my libxslt had gotten!]
> So, if libxml wouldn't go second guessing me, I should be able to create
> any valid URL, right?

 no idea, only test will show.

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/



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]