From: Henrik Motakef <henrik.motakef@web.de>
Subject: Re: Why won't PSGML use http system identifiers?
Date: 30 Oct 2002 21:31:46 +0100 [thread overview]
Message-ID: <87n0ov8y8d.fsf@pokey.henrik-motakef.de> (raw)
In-Reply-To: apobee$hlb$1$830fa78d@news.demon.co.uk
Puff Addison <puff@theaddisons.demon.co.uk> writes:
> >Or better yet, why does not it use catalogs like xsltproc? With xsltproc you
> >can use URLs in XML, but the catalog says where the files are locally.
> >
> Surely it does? Check the documentation on "Enitity
> Management". Works for me.
It doesn't support the XML catalog format proposed by (IIRC) OASIS,
like xsltproc does. However, xsltproc also understands the "old"
format, which also happens to be way more maintainable, so I fail to
see a reason to use the new style anyway...
Regards
Henrik
prev parent reply other threads:[~2002-10-30 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 19:28 Why won't PSGML use http system identifiers? D. D. Brierton
2002-10-29 20:03 ` Henrik Motakef
2002-10-30 8:06 ` Arto V. Viitanen
2002-10-30 10:13 ` Puff Addison
2002-10-30 20:31 ` Henrik Motakef [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87n0ov8y8d.fsf@pokey.henrik-motakef.de \
--to=henrik.motakef@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).