The namespace prefix should not be fixed at all, if it really is behaving
as a namespace attribute. You should also be able to assign two different
prefixes to the same namespace name and use both prefixes to mean the same
thing. Can you point out where a fixed prefix seems to be required?
Also, regarding d:bookinfo, that is just an artifact of where the docbook5
stylesheets are coming from. They are generated from the docbook4
stylesheets by adding the namespace to element names. That's it. To make
maintenance easier and more consistent, the stylesheets were updated to
handle both DocBook4 and DocBook5 elements, so both bookinfo and info are
recognized, and the stylesheet whichever one is matched in your source
file. That's one nice feature of a templating language like XSL. If you
don't use a template, no harm done. So far we haven't had a conflict, but
I keep watching.
Bob Stayton
Sagehill Enterprises
DocBook Consulting
[EMAIL PROTECTED]
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[email protected]>
Sent: Monday, March 12, 2007 6:11 AM
Subject: RE: [docbook-apps] Updating title page customizations for Docbook
V5.0
Hi Bob,
thanks for the information -- I downloaded the snapshot of docbook5-xsl,
and the title page templates are kicking in now, as expected, with no major
problems based on quick testing. Sorry to have neglected to check the bug
database before posting.
I originally chose to use "docbook" instead of "d" as my namespace prefix,
but it seems that "d" is hard-wired into template/titlepage.xsl. Is "d" the
ultimate prefix everyone is using for DocBook V5.0, or would it be worth it
to make this configurable? It's not a big deal in practice as I can just
declare both namespace prefixes with the same URI (seems to work), but it
is kind of messy to have two.
Also, in the generated XSL file I see references to "d:bookinfo", but since
that has been deprecated in favor of the new generic "info" element, I
think those are redundant. I don't mention "bookinfo" in my custom title
page spec, so I don't know where they come from, if not from
template/titlepage.xsl. Curious but harmless.
Best regards
Jere
-----Original Message-----
From: ext Bob Stayton [mailto:[EMAIL PROTECTED]
Sent: 9. maaliskuuta 2007 19:22
To: Kapyaho Jere (Nokia-TP-MSW/Tampere);
[email protected]
Subject: Re: [docbook-apps] Updating title page customizations
for Docbook V5.0
Hi,
I think the problem of the template/titlepage.xsl was fixed in
SVN, so you should try the snapshot version of docbook5-xsl.
Bob Stayton
Sagehill Enterprises
DocBook Consulting
[EMAIL PROTECTED]
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, March 09, 2007 2:49 AM
Subject: [docbook-apps] Updating title page customizations for
Docbook V5.0
Hi,
I have been updating our internal specification tool chain to
use DocBook
V5.0. We have a hefty DocBook XSL stylesheet customization
layer, but I was
making good progress, at least after I realized that I needed
to add the
DocBook namespace prefix to all my customization layer templates... :)
Anyway, the title page customization seems to cause some
trouble. My title
page customizations are not coming through; in fact I don't
get a title
page at all. I suspect this is because the templates in my
generated custom
title page stylesheet are not matching the DocBook elements correctly,
probably because of namespace issues.
I'm a bit lost as to what I should do with the title page spec
XML file, so
that processing it with template/titlepage.xsl would produce
the right kind
of templates. I'm currently using the DocBook V5.0 XSL
stylesheets v1.72.0,
so I'm dealing with namespaces already, but the
template/titlepage.xsl is
exactly the same in both the original and DocBook V5.0 versions of the
DocBook XSL stylesheets (v1.72.0), which makes me wonder.
Is there a way to do this already now, or is there an update
pending for
the template/titlepage.xsl in the DocBook V5.0 stylesheets? I think
titlepage.xsl would need to be aware of the DocBook namespace
prefix used
in the customization layer to generate the correct templates
so that they
match, perhaps using a stylesheet parameter.
I tried this in my customtitlepagespec.xml file:
<t:titlepage t:element="docbook:book" t:wrapper="fo:block">
<t:titlepage-content t:side="recto">
etc.
but this copies the "docbook:" namespace prefix to the name of the
template, among other places, and also complains about the
namespace prefix
not being declared (even when it is, in the t:templates element).
Any ideas about what to do or where to look?
--Jere
--
Jere Käpyaho ([EMAIL PROTECTED])
Specialist, Developer Platform Standardization @
Technology Platforms @
Nokia Corporation
---------------------------------------------------------------------
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]
