Florian Schweikert wrote:
> at the moment we are evaluating XMLMind (using the Standard Edition for
> this task), as we are using DocBook for our rising XML Authoring System.
> 
> Unfortunately, we can't get our setup running. The problem is, that we
> do not start with DocBook directly, but have an own dtd (boc.dtd) that
> references DocBook and a couple of Entity Files. As soon as opening a
> file containing one of the entities, an error message appears.
> 
> Can you please help us to overcome this problem? Attached you will find
> dummy copies of the problem files.

--> In your case, the behavior of XMLmind XML Editor seems to be
strictly compliant with the XML standard.

* You cannot open bookmws.xml in XMLmind XML Editor because
  ** it references entities such as "ToolName" which seems to be defined
the boc.dtd external subset
  ** and bookmws.xml has no <!DOCTYPE> which relates it to boc.dtd.

* You cannot open ADOxx.xml in XMLmind XML Editor because
  ** it references entity "MWS" which points to bookmws.xml
  ** and there is a problem with bookmws.xml.



--> The problem is that bookmws.xml starts with:
---
<?xml version="1.0"?>
---

A document can start with:
---
<?xml version="1.0"?>
---

An external entity such as bookmws.xml *cannot* start with:
---
<?xml version="1.0"?>
---

Excerpt of http://www.w3.org/TR/REC-xml/#TextEntities:
---
External parsed entities should each begin with a text declaration.

Text Declaration

[77] TextDecl ::= '<?xml' VersionInfo? EncodingDecl S? '?>'
---

If you edit bookmws.xml using a text editor and replace
---
<?xml version="1.0"?>
---
by
---
<?xml version="1.0" encoding='UTF-8'?>
---
you'll be able open ADOxx.xml in XMLmind XML Editor (but you'll get a
warning about the "MWS" entity ``not being managed'').



--> If you really want to work that way, that is, using entities defined
in the boc.dtd external subset, I would frankly recommend to use an XML
editor other than XMLmind's (due to XMLmind's important limitations
regarding the handling of external entities).


Reply via email to