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: HTML stylesheets emit warnings when <para> used as rootelement


1) Given the following document:

<?xml version='1.0'?>
<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "docbookx.dtd"
<!ENTITY % xinclude PUBLIC "-//UBS//CORE//DTD XInclude V1.0//EN" "xinclude.dtd">

<para id="panel">
  <xi:include href="panel_common.dbk#xpointer(/para/child::*)"/> 

  <ulink url="/home/overview.html"><emphasis>OVERVIEW</emphasis></ulink>
  <ulink url="/overview/features.html">Features</ulink>
  ...snip - several more, similar lines...

xmllint validates the file with no errors, so the use of <para> as a root element is valid.
Out of curiosity, is there an easily accessible list of valid root elements in DocBook?

2) When I run xsltproc against the document, I get the following warning:

"No template named "para" exists in the context named "title" in the "en" localization."

(although correct HTML is produced nonetheless).

Do people agree that this counts as a bug in the stylesheets?  If so, I will raise a bug report.

3) For interest, and in case the response is "Well, it may be valid, but is it not a rather odd thing to do?" :-) perhaps I should explain our use of such documents...

Previously, we used to maintain panels for the various parts of our websites in HTML and keep them fixed on the page using frames.  Now that we have migrated all of our websites to DocBook, these panels are kept as DocBook source.  For all DocBook pages, we keep the panels fixed on the page by using CSS2 Fixed Positioning (see http://www.w3.org/TR/REC-CSS2/visuren.html#fixed-positioning).  So, each page XIncludes the appropriate panel.  However, certain areas of our websites are outside of our control and hence cannot be written in DocBook.  To maintain a fixed panel for those areas, we need to retain our frame-based approach.  This requires us to generate HTML files from the panels themselves, to be used by the frame-based areas.

It is true that we could code around the warning by wrapping every panel document in an <article> tag (say) and modifying the XInclude statements to say

<xi:include href="panel_home.dbk#panel"/>

instead of just

<xi:include href="panel_home.dbk"/>

but we would prefer to leave things as they are.

My tool chain is as follows:
DocBook DTD v4.2
DocBook XSL v1.56.1
libxml2 v2.4.22
libxslt v1.0.20

Best wishes


Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.

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

Powered by eList eXpress LLC