George Cristian Bina wrote: George,
Yes, the XML Catalogs are the answer. When you create a new file, from templates and select XML Spec then you get that starting with
<?xml version="1.0" encoding="UTF-8"?> <?oxygen RNGSchema="http://www.w3.org/XML/1998/06/schema/xmlspec.rng" type="xml"?> <spec>
and the above location is resolved to a local copy by the XML catalog we provide for the XML Spec framework.
Yep, I don't know why I didn't think directly about catalogs for that. I'd need more Christmas holidays :-) Unfortunately, it seems that catalogs are not taken into account to resolve stylesheet URIs (xsl:import and xsl:include's href.) And quite weird is that even by setting "Saxon / Advanced / URI Resolver" to org.apache.xml.resolver.tools.CatalogResolver (with the correct JAR in com.oxygenxml.additional.classpath) as well as xml.catalog.files to d:/apps/oxygen-xml-10/frameworks/catalog.xml (or file:///d:/..., it does not work neither,) the stylesheet modules are still resolevd from the absolute location (without using catalogs.) Any idea what's going wrong? Don't you think stylesheet module URIs should be resolved against catalogs used in oXygen?
Imagine a framework for XProc, with document templates, default schema, custom actions to invoke an XProc processor, etc.
I can imagine that, indeed :-) Regards, -- Florent Georges http://www.fgeorges.org/