db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren" <m.v.lunte...@gmail.com>
Subject Re: translated documents - are starting to deviate
Date Fri, 26 Jan 2007 21:46:52 GMT
On 1/26/07, Jean T. Anderson <jta@bristowhill.com> wrote:
> Myrna van Lunteren wrote:
> > Hi,
> >
> > I noticed in re DERBY-2214 that at least one of the Brazilian doc
> > pages has not kept up with current changes to the English - at least
> > on trunk.
> >
> > I am wondering how we should handle this.
> >
> > Any thoughts?
>
> Hmmm... on the thread titled "dita docs vrmlist (version 10 and 10.2)" I
> just 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".
>
> If we keep version variables specific to a book (instead of defining
> them at a higher level), then if a given translation in the trunk hasn't
> been updated to incorporate information in the newest release, people
> would know. Taking Getting Started as an example, the version for that
> translated book could be left at 10.1 to clearly indicate that it has
> not incorporated 10.2 features yet.
>
>  -jean
>
>
Maybe a default value, that can be overwritten by each document if
applicable? Not sure if that is possible/feasible.

Also, maybe we could/should exclude those not-completely current books
from a new release branch? So they don't end up in any releases?

Myrna

Mime
View raw message