...

Would it be possible to automatically generate .pot files for contributed modules?

I mean that every time a module is changed from cvs by developers the .pot file shoud be automaticcaly updated by the cvs sistem or by some cron script.

This will free developers of one of their task.

What do you think about this?

This has been suggested before. I think it is a good idea, but we'd need somebody to write a script to do it.

And a CVS user only used for this purpose, to commit changed PO files (note that most commit messages will have pairs this way). Goba

Uwe Hermann wrote:

Hi,

On Mon, Dec 12, 2005 at 10:48:31PM +0100, Gerhard Killesreiter wrote:

...

This has been suggested before. I think it is a good idea, but we'd need somebody to write a script to do it.

Is it possible to (easily) automate this?

I don't think it would be hard. All we'd need to do is a cronjob that runs the scripts once a day (some time before the packages are rebuilt) and created the POT files using extractor.php.

What happens if there's a CVS conflict?

We would simply overwrite the POT file in CVS. They should not be edited by hand, I think and there shoudl not be any conflicts. Cheers, Gerhard

Konstantin Käfer wrote:

but updating the POT files every day will probably cause lots of CVS traffic. Additionally, I don't think it's a good idea to let translators translate strings that are not (yet) stable.

Anything that is on a CVS branch of a module, theme, etc (either HEAD or DRUPAL-4-6 or DRUPAL-4-7, or ...) is packaged for download regularly. So users downloading tarballs from any of these branches will use unstable code if you have unstable code in the branch downloaded. Having translators get unstable strings is a minor problem compared to this IMHO. The rule is to have stable code on stable branches (anything but HEAD). BTW if the PO files are not comitted to the repository, but only packaged to the download, then the CVS commits will not be a problem, but then storing previously generated files might help a lot, since not many files change a day (at least compared to the lots of modules now in contrib). This way one would only be able to get the PO files from the tarballs, which might be a problem for CVS attached users (like me :). Goba

...

but updating the POT files every day will probably cause lots of CVS

You can commit only if there's a change, that means low traffic.

And if that is too much, we can run the script on a weekly basis instead. Having such script sounds like a handy tool regardless of the frequency it is run. Most of us are used to dealing with high volume mailing lists anyway. -- Dries Buytaert :: http://www.buytaert.net/