From: Werner Donné (firstname.lastname@example.org)
Date: Sun Mar 02 2003 - 14:03:19 PST
You don't loose interoperability at all. The system identifier in the
document type declaration is only a default. You can still pass such a
document to someone who uses a catalog. The default will be ignored in
Only the public identifier provides interoperability. You can't rely
on the system identifier for that.
I have proposed the solution because I understood from the original posting
that using an alternative entity resolver was a problem. Well, it is not
that difficult, as shown in the attached example. If you build it you'll
get the file xep.jar. If you put it in the classpath of XEP, you can use
the class be.re.tools.XEP with the following synopsis:
-fo file_or_url or -xml file_or_url -xsl file_or_url
The -c option is for specifying a catalog.
Jirka Kosek wrote:
> On Fri, 28 Feb 2003, [ISO-8859-1] Werner Donné wrote:
>>A simple solution is to download the entities containing the DTD and to
>>specify a local system identifier in your document type declarations. It
>>will be used if no other resolution mechanism is available.
> But this way you loose easy interoperability as <!DOCTYPE points to some
> local resource present only on your computer. Using globaly accessible
> system identifier (http://...) for easy interop and catalog files for
> local resolution is right way to go.
-- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: email@example.com
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to firstname.lastname@example.org from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
This archive was generated by hypermail 2.1.5 : Sun Mar 02 2003 - 13:58:24 PST