You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by scott hutinger <S-...@wiu.edu> on 2007/01/26 20:52:08 UTC
dita docs vrmlist (version 10 and 10.2)
The following is the list of what is printed on the 'version' number in
the docs. I am uncertain if they are all up to 10.2, but I think they
are. That's why I used email instead of an issue...
scott
[srh@scott src]$ grep 'vrmlist' `find . -name '*.ditamap'`
./ref/refderby.ditamap:<vrmlist><vrm version="10"/></vrmlist>
./devguide/derbydev.ditamap:<vrmlist><vrm version="10.2"/></vrmlist>
./tuning/tuningderby.ditamap:<vrmlist><vrm version="10"/></vrmlist>
./adminguide/derbyadmin.ditamap:<vrmlist><vrm version="10"/></vrmlist>
./pt_BR/ref/refderby.ditamap:<vrmlist><vrm version="10"/></vrmlist>
./pt_BR/adminguide/derbyadmin.ditamap:<vrmlist><vrm version="10"/></vrmlist>
./pt_BR/getstart/getstartderby.ditamap:<vrmlist><vrm
version="10.2"/></vrmlist>
./workingwithderby/WorkingWithDerby.ditamap:<vrmlist><vrm
version="10.2"/></vrmlist>
./getstart/getstartderby.ditamap:<vrmlist><vrm version="10.2"/></vrmlist>
./ja_JP/getstart/getstartderby.ditamap:<vrmlist><vrm
version="10.2"/></vrmlist>
./tools/derbytools.ditamap:<vrmlist><vrm version="10"/></vrmlist>
Re: dita docs vrmlist (version 10 and 10.2)
Posted by Andrew McIntyre <mc...@gmail.com>.
On 1/29/07, Laura Stewart <sc...@gmail.com> wrote:
> Do the ditamap files control this or the conrefs files?
> Is there a way to have the vrmlist call the conref "shortversionnumber" ???
As Scott pointed out, this version is in the ditamap file. For the
second question, I don't think that the ditamap is included in the
conref processing step, so it would require changes to the DITA
toolkit to allow for use of conrefs in the map.
andrew
Re: dita docs vrmlist (version 10 and 10.2)
Posted by scott hutinger <S-...@wiu.edu>.
The xslt file that does the version is in dita2fo-shell.xsl
Version <xsl:value-of select="//*[contains(@class,' topic/prodinfo
')]/vrmlist/vrm/@version"/>
which actually is the same as the shortversionnumber (meaning x.x :
10.2) I'm not quite certain what the differences would be between the
two (vrmlist/vrm/version and shortversionnumber. The word "Version" is
added, so vrmlist/vrm/@version might be the same as shortversionnumber,
although I don't know...(?)
So the version the .xsl file uses is in the ditamap files.
scott
Laura Stewart wrote:
> Do the ditamap files control this or the conrefs files?
> Is there a way to have the vrmlist call the conref
> "shortversionnumber" ???
>
>
> On 1/26/07, Jean T. Anderson <jt...@bristowhill.com> wrote:
>> I think it was Andrew who suggested a while back that we define one set
>> of variables for all books to use rather than define them in each book.
>> This is an example of why that would be good. At least that explains why
>> some books print out "Version 10" and others "Version 10.2".
>>
>> thanks for doing the research, Scott,
>>
>> -jean
>>
>> scott hutinger wrote:
>> > The following is the list of what is printed on the 'version'
>> number in
>> > the docs. I am uncertain if they are all up to 10.2, but I think they
>> > are. That's why I used email instead of an issue...
>> > scott
>> >
>> > [srh@scott src]$ grep 'vrmlist' `find . -name '*.ditamap'`
>> > ./ref/refderby.ditamap:<vrmlist><vrm version="10"/></vrmlist>
>> > ./devguide/derbydev.ditamap:<vrmlist><vrm version="10.2"/></vrmlist>
>> > ./tuning/tuningderby.ditamap:<vrmlist><vrm version="10"/></vrmlist>
>> > ./adminguide/derbyadmin.ditamap:<vrmlist><vrm version="10"/></vrmlist>
>> > ./pt_BR/ref/refderby.ditamap:<vrmlist><vrm version="10"/></vrmlist>
>> > ./pt_BR/adminguide/derbyadmin.ditamap:<vrmlist><vrm
>> > version="10"/></vrmlist>
>> > ./pt_BR/getstart/getstartderby.ditamap:<vrmlist><vrm
>> > version="10.2"/></vrmlist>
>> > ./workingwithderby/WorkingWithDerby.ditamap:<vrmlist><vrm
>> > version="10.2"/></vrmlist>
>> > ./getstart/getstartderby.ditamap:<vrmlist><vrm
>> version="10.2"/></vrmlist>
>> > ./ja_JP/getstart/getstartderby.ditamap:<vrmlist><vrm
>> > version="10.2"/></vrmlist>
>> > ./tools/derbytools.ditamap:<vrmlist><vrm version="10"/></vrmlist>
>> >
>>
>>
>
>
Re: dita docs vrmlist (version 10 and 10.2)
Posted by Laura Stewart <sc...@gmail.com>.
Do the ditamap files control this or the conrefs files?
Is there a way to have the vrmlist call the conref "shortversionnumber" ???
On 1/26/07, Jean T. Anderson <jt...@bristowhill.com> wrote:
> I think it was Andrew who suggested a while back that we define one set
> of variables for all books to use rather than define them in each book.
> This is an example of why that would be good. At least that explains why
> some books print out "Version 10" and others "Version 10.2".
>
> thanks for doing the research, Scott,
>
> -jean
>
> scott hutinger wrote:
> > The following is the list of what is printed on the 'version' number in
> > the docs. I am uncertain if they are all up to 10.2, but I think they
> > are. That's why I used email instead of an issue...
> > scott
> >
> > [srh@scott src]$ grep 'vrmlist' `find . -name '*.ditamap'`
> > ./ref/refderby.ditamap:<vrmlist><vrm version="10"/></vrmlist>
> > ./devguide/derbydev.ditamap:<vrmlist><vrm version="10.2"/></vrmlist>
> > ./tuning/tuningderby.ditamap:<vrmlist><vrm version="10"/></vrmlist>
> > ./adminguide/derbyadmin.ditamap:<vrmlist><vrm version="10"/></vrmlist>
> > ./pt_BR/ref/refderby.ditamap:<vrmlist><vrm version="10"/></vrmlist>
> > ./pt_BR/adminguide/derbyadmin.ditamap:<vrmlist><vrm
> > version="10"/></vrmlist>
> > ./pt_BR/getstart/getstartderby.ditamap:<vrmlist><vrm
> > version="10.2"/></vrmlist>
> > ./workingwithderby/WorkingWithDerby.ditamap:<vrmlist><vrm
> > version="10.2"/></vrmlist>
> > ./getstart/getstartderby.ditamap:<vrmlist><vrm version="10.2"/></vrmlist>
> > ./ja_JP/getstart/getstartderby.ditamap:<vrmlist><vrm
> > version="10.2"/></vrmlist>
> > ./tools/derbytools.ditamap:<vrmlist><vrm version="10"/></vrmlist>
> >
>
>
--
Laura Stewart
Re: dita docs vrmlist (version 10 and 10.2)
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
I think it was Andrew who suggested a while back that we define one set
of variables for all books to use rather than define them in each book.
This is an example of why that would be good. At least that explains why
some books print out "Version 10" and others "Version 10.2".
thanks for doing the research, Scott,
-jean
scott hutinger wrote:
> The following is the list of what is printed on the 'version' number in
> the docs. I am uncertain if they are all up to 10.2, but I think they
> are. That's why I used email instead of an issue...
> scott
>
> [srh@scott src]$ grep 'vrmlist' `find . -name '*.ditamap'`
> ./ref/refderby.ditamap:<vrmlist><vrm version="10"/></vrmlist>
> ./devguide/derbydev.ditamap:<vrmlist><vrm version="10.2"/></vrmlist>
> ./tuning/tuningderby.ditamap:<vrmlist><vrm version="10"/></vrmlist>
> ./adminguide/derbyadmin.ditamap:<vrmlist><vrm version="10"/></vrmlist>
> ./pt_BR/ref/refderby.ditamap:<vrmlist><vrm version="10"/></vrmlist>
> ./pt_BR/adminguide/derbyadmin.ditamap:<vrmlist><vrm
> version="10"/></vrmlist>
> ./pt_BR/getstart/getstartderby.ditamap:<vrmlist><vrm
> version="10.2"/></vrmlist>
> ./workingwithderby/WorkingWithDerby.ditamap:<vrmlist><vrm
> version="10.2"/></vrmlist>
> ./getstart/getstartderby.ditamap:<vrmlist><vrm version="10.2"/></vrmlist>
> ./ja_JP/getstart/getstartderby.ditamap:<vrmlist><vrm
> version="10.2"/></vrmlist>
> ./tools/derbytools.ditamap:<vrmlist><vrm version="10"/></vrmlist>
>