From: Ismael Olea <ismael.olea@hispalinux.es>
To: Alan Westhagen <afw@u.washington.edu>
Cc: docbook-tools-discuss <docbook-tools-discuss@sources.redhat.com>
Subject: Re: Indirection
Date: Fri, 13 May 2005 09:31:00 -0000 [thread overview]
Message-ID: <1115976677.13436.143.camel@lisergia> (raw)
In-Reply-To: <42811E15.5000604@u.washington.edu>
El mar, 10-05-2005 a las 13:48 -0700, Alan Westhagen escribió:
This seems to be an XML/SGML incompatibility I've never had time to
study.
For me the alternative was using the XML tool-chain. I'm in love with
xmlto :-D
> I have a lot of documents written in docbook xml which, up until
> recently, worked fine with docbook-tools.
>
> A typical header looks like this:
>
> <?xml version="1.0"?>
> <!DOCTYPE article PUBLIC "=//OASIS//DTD DocBook XML V4.2//EN"
> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
> [
> ]>
>
> I can no longer process the documents with docbook-tools. I believe
> the element that has changed is the dtd located at oasis-open.org.
>
> Since I have no power to correct what is installed at
> oasis-open.org, I would like to use local files, but with indirection,
> so that I do not have to change all the documents each time I
> upgrade my system.
>
> I tried to use a symbolic link as the system identifier. Emacs was
> happy with that, but docbook-tools broke.
>
> I tried putting OVERRIDE YES in the catalog file, but the tools
> still insist on being able to open the file referenced by the
> system identifier.
>
> Does anyone have a simple way of setting up indirection, catalog
> based or otherwise, for docbook tools? My setup is standard
> RedHat Enterprise Linux.
>
> Best regards,
> Alan
prev parent reply other threads:[~2005-05-13 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 20:48 Indirection Alan Westhagen
2005-05-11 10:35 ` Indirection Éric Bischoff
2005-05-13 9:31 ` Ismael Olea [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1115976677.13436.143.camel@lisergia \
--to=ismael.olea@hispalinux.es \
--cc=afw@u.washington.edu \
--cc=docbook-tools-discuss@sources.redhat.com \
/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).