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: DOCBOOK-APPS: BUG: doclifter and ISO character entities


Part of the implementation in doclifter 1.0.0 for handling ISO character
entities in XML output is broken.

In the Bugs And Warnings section of the doclifter man page, I notice the

  When generating XML, doclifter currently generates ISO SGML entity
  inclusions rather than the more technically correct XHMTL sets. This
  accommodates an apparent deficiency in the xsl-stylesheets
  distribution and may change in the future.

Can you clarify the background on that?

In practice, I've found that what it's actually doing in some instances
is generating invalid XML. For example, doclifter will generate:

  <?xml version="1.0" encoding="ISO-8859-1"?>
  <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
                     "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"; [
  <!ENTITY % ISOpub PUBLIC "ISO 8879:1986//ENTITIES Publishing//EN"

But for XML, if it generates any ISO character entity declarations at
all in the internal DTD subset, they should look like this:

  <!ENTITY % ISOpub PUBLIC "ISO 8879:1986//ENTITIES Publishing//EN//XML"

The ISO SGML entities are different from the XML ones, and if an XML
parser/XSLT engine ends up pulling in the SGML entities instead of the
XML ones, it'll break -- the SGML entities don't 'work' with XML.

Anyway, I don't understand why doclifter needs to generate entity
declarations for the ISO entities at all, because both the DocBook SGML
and XML DTDs already include the correct entity declarations -- so the
ISO entity declarations doclifter generates are actually redundant.


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

Powered by eList eXpress LLC