Daniel Burrows <[EMAIL PROTECTED]> (11/03/2006): > On Sat, Mar 11, 2006 at 06:52:49PM +0100, Thomas Huriaux <[EMAIL PROTECTED]> > was heard to say: > > Daniel Burrows <[EMAIL PROTECTED]> (11/03/2006): > > > Would I be correct in understanding that with this change, the > > > French documentation is now autogenerated and hence should be removed > > > from version control? > > > > Yes, you're right. It is autogenerated, using strings from the po file > > if available, otherwise English strings, so that the translation remains > > always 100 % up-to-date, but sometimes contains English strings. > > Hm, it seems there isn't any way to generate one documentation translation > at a time -- you have to generate all the translations /plus/ the pot in > each go? That's, um, kind of awkward to integrate into the build process... > > Let's see if I have the dependency chain down, anyway. Maybe the low-level > utilities can be used to get a proper build set up. > > po4a/po/aptitude.pot => master file, depends on en/aptitude.xml.
po4a-gettextize > po4a/po/??.po => translations for ??, depends on > po4a/po/aptitude.pot. po4a-updatepo > ??/aptitude.xml => translated documentation, depends on po4a/po/??.po > and po4a/add_??/addendum.1.?? po4a-translate > So far so good, so I just need to figure out the incantations to generate > each file from its dependencies...or use the super-all-in-one-script that > regenerates the world whenever a dependency changes (and in reality most > changes I'll see are changes that impact the whole world anyway). I don't have time tonight to provide a full patch if you prefer not to use this "super-all-in-one-script". I will try to have a look at it tomorrow. Cheers, -- Thomas Huriaux
signature.asc
Description: Digital signature
