On 14.6.2012 23:57, deannel...@aol.com wrote:
> 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
On 15/06/12 08:01, deannel...@aol.com wrote:
How about
or something like that?
Yes. It's the idea I like.
Sort of keeping docbook up to date without doing anything?
regards
In a message dated 6/14/2012 10:19:29 P.M. Pacific Daylight Time,
da...@dpawson.co.uk writes:
On 14/06/12 22:
How about
or something like that?
In a message dated 6/14/2012 10:19:29 P.M. Pacific Daylight Time,
da...@dpawson.co.uk writes:
On 14/06/12 22:57, deannel...@aol.com wrote:
> Ok, I found the issue inside my layers.
>
> However, this issue should be able to work easier than shutting
On 14/06/12 22:57, deannel...@aol.com wrote:
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 copyri
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 dbti
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.
" >
Then I used this to fill in the year in the copyright field in
