[Crystaldoc-main] Splitting crystaldoc in lang and build packages

[Vincent K. <vi...@ie...>]

Le jeu 18/12/2003 =E0 19:06, Arthur Huillet a =E9crit :
> Vincent Knecht wrote:
> > Le jeu 18/12/2003 =E0 17:50, Arthur Huillet a =E9crit :
> >=20
> >=20
> >=20
> > for me there's no problem if you don't want to "downgrade"
> he'll see himself, but i'm sure he won't bare that for a long time :)

Pablo, please let us know what you think about the CS version to
translate

> >=20
> >=20
> > if we work on different versions, i'm not sure a common package is a
> > good idea.
>=20
> this is another problem than the one i'm discussing below, that's=20
> another reason for wich i'd rather support having the same version
> anyway, a version-independant and language-independant building process=
=20
> is something possible, right ? :)

if it's possible, okay
at least for now building our 0.96 french manual using 0.97
original files when translated one doesnt exists seem to produce
good output (don't have checked precisely); at least no no-go error

So there's hope to achieve this :-)
We should check if build process changed by diffing CS involved
makefiles/jamfiles

>=20
> > even if we work on the same version, there would be just a few
> > duplicated files ( mainly .def and .tex)

here i just forgot to mention texi2html & texi2html.init, which we took
out of CS CVS (needed for french terms, for toc headers as well as
navigation panel & others)
Pablo, maybe you'll want to add spanish terms in these two files ?

> > unless we want to share screenshots and images (this could annoy us
> > if we wanted to get localised screenshots), i'm not much for making
> > one additional package, that all people would need to build the manua=
l,
> > but surely a very few who'd build two or more language pack...
> >=20
> well the other solution is to make a full package for each release,=20
> containing the base plus the language pack
> for development though i'm for using differents modules for base and=20
> languages.
> I'd like us to take a decision rapidly about CVS :)

can you describe us how the retrieving and updating would differ ?
can a module (ie the base) be automatically retrieved when getting
one of the languages modules ?
if so, i buy ;-)

Wouldn't module splitting require having two (or 3 with 2 languages)
base directories for each (on local side) ?

> the third solution i don't like very much, is to do what we want to=20
> build, ie pablo could decide to modify original makefiles while we=20
> decide to use our own...if we have a central project (crystaldoc) i=20
> think there's a reason for that, then i don't support a non-universal=20
> solution for building.

please make your tests and let us know if it's possible...
as pointed above, maybe there's no problem to do that

Vincent