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] | [Elist Home]

Subject: RE: DOCBOOK-APPS: Suppressing <?xml version="1.0"> added by XMeta L

What error does saxon give you?  I have similar files, and saxon doesn't
complain about the XML declaration.  However, Saxon would complain about
multiple DOCTYPE declarations.  (Any XML parser will -- multiple DOCTYPE
declarations -- even in external entities -- render the document malformed.)
I use Epic instead of XMetal, however, and Epic gets around this problem
with what they call fragment headers.  (Basically, DOCTYPE declarations
wrapped in a comment that Epic understands.)  Other editors I've seen use
processing instructions or a "default DOCTYPE" setting for editing external
entities.  I don't know how XMetal does this, but it seems that it doesn't
do it in a reasonable fashion.


-----Original Message-----
From: Zhuravleva, Tatyana [mailto:Tatyana.Zhuravleva@scala.net]
Sent: Monday, June 17, 2002 10:17 AM
To: docbook-apps@lists.oasis-open.org
Subject: DOCBOOK-APPS: Suppressing <?xml version="1.0"> added by XMetaL

I'm a newbie, thinking of using XMetaL for DocBook.

One of the things I got stuck with right in the beginning is that XMetaL
adds <?xml version="1.0">  to my chapter files (external entities), even
when opening in "Edit as a partial document" mode. 
And saxon doesn't like it. Can anybody tell, am I doing anything wrong?
I'm going to have lots of files, so removing the line manually is not an
option for me. Sorry if it's offtopic.


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

Powered by eList eXpress LLC