Re: [docbook-apps] Copyright and dbtimestamp

[DeanNelson@aol.com]

Ok, I found the issue inside my layers.

 

However, this issue should be able to work easier than shutting off the multi year combination parameters. I assume that the dbtimestamp is being evaluated after the multi-year-combination template of the copyright/year?

 

Is there a way to get the dbtimestamp evaluated earlier?

 

 

 

In a message dated 6/14/2012 2:40:10 P.M. Pacific Daylight Time, DeanNelson@aol.com writes:

Greetings,

 

I am hitting a snag. I don't want to continually update my copyright year in my docs. So I used the dbtimestamp  PI to pick out the year and put that in an ENTITY included with all my docs. Sounded simple.

 

 

    <!ENTITY CURRENT_YEAR "<?dbtimestamp format='Y' padding='0'?>" >

Then I used this to fill in the year in the copyright field in my XML.

 

 

<section>

    <sectioninfo>

        <copyright id="met-copyright">

            <year>2005-&CURRENT_YEAR;</year>

            <holder>My Company</holder>

        </copyright>

 

 

However, when I used xsltproc/fop1.0 to process it as normal, I get"

 

    Copyright (c) 2005- My Company

 

So I did some more looking in my customization layer and I could only find where I set up the combining of copyright years and disabled that.

 

<xsl:param name="make.single.year.ranges" select="0"/>

<xsl:param name="make.year.ranges" select="0"/>

 

What else could it be? I use the dbtimestamp elsewhere and it works fine, even as an ENTITY.

 

Regards,

Dean Nelson