[In this email, I assume that you are using XXE to author DocBook
documents.]
Ken Doran wrote:
> My XXE document contains not only chapter numbers, but also section
> numbers and subsection numbers. And I can see all of these heading
> numbers when viewing my document with XXE. The chapter, section, and
> subsection numbers are also displayed in the HTML file that I can
> generate from my source document using XXE and view independently using
> Internet Explorer or Netscape. So far, so good...
>
> When a colleague generated a PDF from my XML source, however, the PDF
> displayed only chapter numbers, but _no_ section or subsection numbers.
> I took a peek at the XML file saved by XXE and did not see any section
> or subsection numbers. But I'm not sure if the problem lies with our
> PDF conversion process (done outside of XXE) or in the raw XML source
> document created by XXE.
This is normal. Chapter and sections numbers are not part of the markup.
* When a document is rendered on screen by XXE, the CSS style sheet
contains rules that generate Chapter and sections numbers.
Excerpts of <XXE_install_dir>/config/docbook/css/collapsible.imp:
---
chapter > title:first-child:before {
content: collapser() " Chapter " counter(n-, decimal) ": ";
}
sect1 > title:first-child:before {
content: collapser() " " counter(n-) " ";
}
---
* When a document is converted to HTML by XXE or *any other tool*
(Saxon, xsltproc, Xalan, MSXML, etc), the XSLT style sheet contains
templates that generate Chapter and sections numbers *if the right XSLT
style sheet parameters have been specified*
See http://www.sagehill.net/docbookxsl/SectionNumbering.html
* When a document is converted to XSL-FO (and then to PDF, RTF, etc) by
XXE or *any other tool* (Saxon, xsltproc, Xalan, MSXML, etc), the XSLT
style sheet contains templates that generate Chapter and sections
numbers *if the right XSLT style sheet parameters have been specified*
See http://www.sagehill.net/docbookxsl/FOSectionNumbering.html
> Is this another one of those "artificial restrictions" imposed in XXE
> Standard Version (although we're _not_ using XXE to perform the PDF
> conversion)? Is this an XXE bug? Or are we likely doing something
> incorrect in our PDF creation process (the details of which are unknown
> to me)?**
This is not an XXE bug.
This is not related to the restrictions of XXE Standard Edition.
Yes, this is related to the tool you use to convert DocBook to PDF or to
the way you convert DocBook to PDF. And this is probably extremely easy
to fix.
The person who has attempted to convert your XML document to PDF needs
to read the documentation of her/his conversion tool and/or read the
documentation of the XSLT style sheets that are used to do the
conversion
(http://docbook.sourceforge.net/release/xsl/current/doc/reference.html)
> Yes, I realize that the best (and maybe quickest) solution probably lies
> in convincing my cheap boss to buy the Professional Edition of XXE...
> Nonetheless, although XXE Standard Version doesn't perform PDF
> conversions and a few other tasks,
Nothing forces you to do that.
You should give XSL Utility
(http://www.xmlmind.com/foconverter/xslutility.html), which is part of
XMLmind FO Converter Personal Edition
(http://www.xmlmind.com/foconverter/persoedition.html), a try.
> it's my understanding that raw XML files created by XXE should not be
> restricted or compromised in any way.
This is the case. XML files created by XXE Standard Edition are *not*
restricted or compromised in any way.
Compromising XML files created by XXE Standard Edition would be like
shooting ourselves in the foot. By giving away tools such as XXE
Standard Edition and XFC Personal Edition, we are trying to promote the
use of XML as well as the use of our products.
