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

[Arthur H. <art...@fr...>]

  > i was speaking of making our own makefiles based on CS one, and check
> which changes occured beetween CS 0.96 and CS 0.97 to make sure our
> makefiles can cope with these two different CS versions.
> 
> And i see at least one good reason we need a "link" with CS,
> it's simply for including english texinfo file when we don't provide a
> translated one. Probably through the use of $CRYSTAL.
> 
> There are 2 or 3 solutions if you really don't want to rely on CS:
> - producing a partial manual (ie. just the translated chapters)
> - import all english file (& pictures), then translate them
> - check out CS files from CVS (the CVS version or the 0.96.4) when
>   building manual (automatically on our CVS) then delete them ?

Yeah, sure, we need the original english files included, but in fact 
after some reflexion your 2nd solution seems the best to me. That way we 
produce a complete manual, independant from CS.

  >>the building process is a different work than translation, then i 
see no
>>reason for wich we shouldn't make another module :)
>>
>>if you're thinking as an enduser then what's possible for CVS is that :
>>
>>cvs co base
>>cd base
>>cvs co fr
>>
>>(note it would depend on our building process)
> 
> that's the whole point, we can therefore not rely on relatives paths
don't tell me we were going to use a same base with just one line 
modified, for both french and spanish translation :)

i really hope you're wrong and i think you are, this should be possible 
to make some script taht will look for a FR/ or SP/ subdirectory to make 
the documentation, or even a script than will look for all subdirs with 
2 letters like UK/ US/ AU/ CA/ etc !

> 
> 
>>>Wouldn't module splitting require having two (or 3 with 2 languages)
>>>base directories for each (on local side) ?
>>
>>that's even the definition of a cvs module :)
>>
>>
>>I hope we will be able to find a solution for this building process.
>>
>>To my mind we need cvs modules. Or we're gonna die under an horrible 
>>garbage 3 days after having committed our changes :)
> 
> 
> where would the garbage come from ? do you mean from potential mistake
> or what ?
because each modification to the building process, will have to be done 
twice on TWO differents local repositories.
That's the problem.
If we include spanish tr. to our current module crystaldoc, since we 
don't care about spanish when translating french, since when translating 
spanish, pablo doesn't care about french, and since when one of us will 
make modifications to the building process, then he doesn't care about 
any translation at all ; i don't see any reason for wich we should have 
to checkout/update something larger than useful, deleting useless 
directories, and being warned by the cvs server that we deleted some dirs...
There are 3 different ways for crystaldoc for the moment, those are
-Building process
-Spanish Translation
-French Translation
they are independant, ie working on one doesn't need the other, even if 
we finally include the building process into the translations directly 
(seems dangerous to me)....

A.H.