OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [docbook-apps] Modularization technique


On Mon, Aug 11, 2003 at 07:38:01PM -0500, Bob Foster wrote:
> 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.)

Yes, xmllint (included with libxml2) can validate a system entity
with an external DTD reference:

xmllint --dtdvalid "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"; --noout myfile.xml

-- 

Bob Stayton                                 400 Encinal Street
Publications Architect                      Santa Cruz, CA  95060
Technical Publications                      voice: (831) 427-7796
The SCO Group                               fax:   (831) 429-1887
                                            email: bobs@sco.com


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]