Re: Translations and changelogs
On Fri, Jan 23, 2004 at 01:23:38AM +0100, Denis Barbier wrote:
> This is an option, but I was referring to this part:
> ] Mandrake folks define an aliased po module containing all po directories
> ] http://cvs.mandrakesoft.com/cgi-bin/cvsweb.cgi/CVSROOT/modules
So, if I understand correctly, this works this way:
1. The translator checks out the po-module
2. It contains a bunch of directories each one of which just includes the
po files for all translations - so only one level of directories
3. When updated, these files can be committed directly from these
one-level directories, would nevertheless land in the right directories.
This would be a great way of handling translations! We are currently
parsing all of the ru.po files into our CVS (renamed) and editing them
there. The current problem is how to find out where these files belong to
in the d-i source tree. If we took over the Mandrake way, this would
almost automagically solve this problem!
> Sorry I was unclear, this script should only:
> a. Look at debian/changelog to find UNRELEASED sections.
Joey Hess mentioned "translation-only" uploads, which would not have any
changes but the translations, which would result in _not_ having an
UNRELEASED section. At the same time, sowewhere in partman thread, it has
beed suggested to create an UNRELEASED section immediately after release.
Maybe we could just notice whether UNRELEASED exists....
> b. Report PO files updated after the last upload.
That's what my script does. I'm still looking for a better output form for
this - currently is is a bunch of "Updated xx.po translation" strings on
the stdout.
> If it is run from inside a package directory, it displays the
> debian/changelog which will be generated by your script. But when run
Including something like "Accept/Decline/Panic"-question? Agreed. Probably
also executing dch a second time, to let the maintainer add some lyric to
the changelog :)
> from top-level debian-installer, it could produce a status report for all
> packages, maybe maintainers could find this tool useful and then accept
> that translators do not update debian/changelog.
What would this status report include? Something like "coutrychooser has
10 updated translations, an upload is recommended."? BTW, this would be a
case for another script, which would call the first one - or something
like this, maybe with a subroutine or the like - I actually like the
modularity of unix ;)
--
Nikolai Prokoschenko
nikolai@prokoschenko.de / Jabber: pronik@jabber.org
Reply to: