Okay, found it (but no idea how to solve it...).
It's the change from 2003-06-09 06:30 fixing bug #114277.
The change is in xmlIO.c (xmlLoadExternalEntity) and
parser.c (xmlCreateFileParserCtxt): in my case,
..\../somepath/somefile.xml does exist, but is not
an URL... so I guess it gets messy later when trying
to resolve something like ../someotherdir/externalentity.ent
relative to somefile.xml.
Maybe try the attached test (I think it breaks on unix too):
~> xmllint --valid --noout "te st/src/src.xml"
te st/src/src.xml:1: error: failed to load external entity "../res/src.dtd"
<!DOCTYPE src SYSTEM "../res/src.dtd">
^
te st/src/src.xml:2: validity error: Validation failed: no DTD found !
<src/>
^
-sbi
-----Original Message----- From: Daniel Veillard [mailto:veillard redhat com] Sent: 05 September, 2003 10:17 To: Stéphane Bidoul Cc: xml gnome org Subject: Re: [xml] slashes and backslashes On Thu, Sep 04, 2003 at 10:03:41PM +0200, Stéphane Bidoul wrote:Hi, On Windows I frequently end up doing things like xmllint --noent ..\../somepath/somefile.xml (ie mixing / and \ in file names). It used to work (in 2.5.7) but stopped working now that I have recompiled libxml2 from a fresh CVS checkout. It fails when the parsed file references other external entities. Did something change in that area recently?Not that I remember, 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/
Attachment:
test.tgz
Description: Binary data