[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [docbook-apps] resolving catalogs on Windows
> -----Original Message----- > From: Georges Schmitz > > Here comes the command (of course all in one line): > > D:\LHM\Doku\Spec\AdminTool\edit>java > > -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.j > axp.DocumentBuilderFactoryImpl > > -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SA > XParserFactoryImpl > > -Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apac > he.xerces.parsers.XIncludeParserConfiguration > com.icl.saxon.StyleSheet > -x org.apache.xml.resolver.tools.ResolvingXMLReader > -y org.apache.xml.resolver.tools.ResolvingXMLReader > -r org.apache.xml.resolver.tools.CatalogResolver > -u > -o "admin.htm" > "admin.xml" > "cdocbook.xsl" > admon.graphics.path="../../common/images/decorative/" > use.extensions="1" > > ("cdocbook.xsl" is resolved by the catalog) If I replace "admin.xml" > by the uri "file:///D:/LHM/Doku/Spec/AdminTool/edit/admin.xml" > (absolute path) then processing is successful. This works also if > I use "file:/" instead of "file:///", but I think that xsltproc > only accepts the notation with 3 slashes (probably the official > form). But "admin.xml" is a valid uri too, or am I wrong here? Yes, I think it is a valid relative URI. But something apparently happens during all the parsing and resolving. Anyway, I use almost exactly the same configuration for Saxon as you do, except for -u. If you remove the -u option, it should work. Or keep -u and write file:admin.xml and file:cdocbook.xsl. But am not sure if this is actually allowed according to RFC 2396 and other authorities. URI syntax seems like a tricky area. /MJ
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]