Re: [xml] let's push down the bug: xmlBuildURI



On Fri, Dec 13, 2002 at 05:36:13PM +0100, Stefano Zacchiroli wrote:
This bug is really more serious than the other one because it applies to
xmlBuildURI which is used widely in the code.

   hum, okay

The only way to solve the problem here is really to keep somewhere
information about what was escaped or the original uri itself, but this

  yes

requires API changes,

  No 

at least in xmlParseURI* and xmlURIUNescapeString
functions.

  keep the original string in xmlBuildURI, it's a parameter anyway,
if it's absolute you can use it directly. However for more complex
cases yes it is hard to fix.

May I procede in try a fix even if it implies an API change?

  No API change, sorry. this has to be doable without.

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]