Hi,
Your message wasn't quite clear I think because you put element names in angle brackets, and those didn't survive.

I think you are asking why articleinfo/date does not appear in the output. The stylesheets do not automatically output everything in *info, because some elements are meant for internal use and not for publication. Everyone wants different information to be output. The elements that appear on the title page are controlled by the titlepage spec file. See this reference for more information about how to configure it for your customization layer:

http://www.sagehill.net/docbookxsl/HTMLTitlePage.html

Bob Stayton
Sagehill Enterprises
[EMAIL PROTECTED]


----- Original Message ----- From: "Chad A." <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, August 07, 2008 9:38 AM
Subject: [docbook-apps] Bug in Docbook XSL articleinfo/date?


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

When I ran the my Docbook XML document through the Docbook XSL
stylesheets to produce a XSL-FO stylesheet, I noticed that it didn't
handle the  element under the  element.  It does handle the  element,
though.  (If I recall correctly, they both markup the same
information.)  Is this a bug in the XSL stylesheets?  I know where the
offending code is, and to fix it I wrote a customization layer to
handle the error, but shouldn't the XSL stylesheet handle it if the
element is part of the spec?

Should I submit a bug report (and patch)?

Chad
http://www.neomantic.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: http://getfiregpg.org

iEYEARECAAYFAkibKNQACgkQ7Ps2z1aSPDEqrwCcC1q6CpLTKef0o//NL3ni5GO+
m7gAniKHwVMhYs7upYQePWi1IJYWlnto
=z1sB
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to