This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: [docbook-apps] Modularization technique
- From: "Bob Foster" <bob at objfac dot com>
- To: "Jeff Beal" <jeff dot beal at ansys dot com>,<docbook-apps at lists dot oasis-open dot org>
- Cc: "Bob Stayton" <bobs at sco dot com>
- Date: Mon, 11 Aug 2003 19:38:01 -0500
- Subject: Re: [docbook-apps] Modularization technique
- References: <E08C8F26F6901D42B1201763D125853801A5CEA3@ntdevexc.win.ansys.com>
From: "Jeff Beal" <jeff.beal@ansys.com>
> Good XML editors have their own mechanisms for dealing with this problem.
> (In fact, I don't consider an editor to be good unless it has such a
> mechanism.) Epic wraps the DOCTYPE declarations with XML comments.
> Emacs/PSGML uses local buffer variables to point to the parent document.
> XMetal uses a processing instruction to point to the DTD. WordPerfect has
a
> catalog that maps the root element to the DTD. I've never used
FrameMaker,
> so I don't know if it passes my "good XML editor" test, but I would expect
> it to have some sort of workaround.
The problem is that external entities must be separately validatable, right?
How do any of these solutions help? Unless, of course, the entities can only
be validated by the editor.
Seems like a more appropriate solution would be to use a validator that
allows the DTD to be specified outside the document. (And an editor that
allows same.)
Bob Foster
---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org