[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Notifying translators about the state of translations (was: Re: [PATCH] Polish translation for subversion messages)

From: Erik Hülsmann <e.huelsmann_at_gmx.net>
Date: 2004-05-26 23:53:22 CEST
('binary' encoding is not supported, stored as-is) Resend to dev@ list...

>Marcin Kasperski <Marcin.Kasperski@softax.com.pl> writes:
>> I'd recommend organizing some process of notifying translators
>> about changes (there is single subversion package of english
>> texts but a few translations which are to change). Maybe
>> something like daemon regularly generating .pot file, checking
>> for the amount of changes since previous notification was
>> generated and sending some notification to subversion-dev or to
>> translators when a lot of things changed? Or, otherwise, the
>> decision that messages should not be changed between beta and
>> final release - and the habit of reviewing translations every
>> time beta is published?

Hi Karl,

I had your request in a large pile of mails to respond to. It took
me a while to get through.

>Can someone describe in pseudocode how this should work, and what
>dependencies such a tool would have? I could try to code it up in
>Python and install it as a hook.

I was thinking of a weekly update as a cron job or something like
that. I don't see the need for every commit which changes a _()
to be followed by a series of commits to the language files.

The msgattrib program (available in GNU gettext) can be used to
filter messages wich certain attributes. I believe there are
three attributes which together indicate the state of the translation
quite well:

= untranslated
= fuzzy
= obsolete

I suppose it is possible to script these stats as:

 $ make gnu-locale-po-update

 $ msgattrib --untranslated -o - de.po | grep '^msgid "' | wc -l
 $ msgattrib --only-fuzzy -o - de.po | grep '^msgid "' | wc -l
 $ msgattrib --only-obsolete -o - de.po | grep '^msgid "' | wc -l

The output might look something like this:

Subversion translation file state reminder

  xx untranslated messages
  yy fuzzy messages
  zz obsolete messages



And send these stats to a list. Which list would be suitable for
that? That way, anybody wanting to contribute could subscribe to
that list and be notified automatically.




To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 26 23:53:45 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.