Re: [docbook-apps] Copyright and dbtimestamp

2012-06-15 Thread DeanNelson
How about copyright start=2005 end=now 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

Re: [docbook-apps] Copyright and dbtimestamp

2012-06-15 Thread davep
On 15/06/12 08:01, deannel...@aol.com wrote: How about copyright start=2005 end=now 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,

Re: [docbook-apps] Copyright and dbtimestamp

2012-06-15 Thread Jirka Kosek
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 to

Re: [docbook-apps] Copyright and dbtimestamp

2012-06-14 Thread DeanNelson
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

Re: [docbook-apps] Copyright and dbtimestamp

2012-06-14 Thread davep
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