RE: [docbook-apps] Modularization technique

[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.

Jeff Beal

> -----Original Message-----
> From: Taro Ikai [mailto:tikai@ABINITIO.COM]
> Sent: Monday, August 11, 2003 2:32 PM
> To: docbook-apps@lists.oasis-open.org
> Cc: Bob Stayton
> Subject: [docbook-apps] Modularization technique
> 
> 
> I am now facing a problem in breaking down a book into sub-documents. 
> Bob Stayton described the problem once:
> 
>     
> http://lists.oasis-open.org/archives/docbook/200002/msg00200.html  (*)
> 
> Bob talks about the use of <xi:include> and <olink> as a 
> solution for this
> problem at his web site:
> 
>     http://www.sagehill.net/docbookxsl/ModularDoc.html
> 
> I am concerned that once I switch to using <olink>, it will be nearly 
> impossible to reimport the document into FrameMaker. 
> 
> I want to edit my sub-documents with a validating editor 
> (Emacs w/ psgml), 
> 
> so I'm tempted to go with Option B cited in Bob's original post(*).
> 
> Is my concern about mapping the <olink>'ed DocBook documents to 
> FrameMaker files unwarranted? 
> 
> Are there grave concerns with using the Option B?
> 
> What 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: 
> docbook-apps-help@lists.oasis-open.org
> 
> 
>