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

Re: localisation: status, migration to pootle

From: Daniel Shahaf <danielsh_at_elego.de>
Date: Thu, 8 Aug 2013 21:39:04 +0300

Mattias Engdegård wrote on Thu, Aug 08, 2013 at 19:40:00 +0200:
> 8 aug 2013 kl. 08.21 skrev Daniel Shahaf:
>> Mattias Engdegård wrote on Wed, Aug 07, 2013 at 23:43:36 +0200:
>>> Sorry about the late reply; I rarely have time to read the
>>> development
>>> list. It seems unlikely that many translators do - how are they
>>> notified
>>> about the need to update their translations? It is common to have
>>> this as
>>> an explicit step in the release process; perhaps I have missed the
>>> broadcasts so far.
>> We don't have such a step. I don't know if such announcements have
>> been
>> sent, but .de translator Jens Seidel also expressed interest in having
>> such --- so perhaps we [c|sh]ould do that in the future.
> Please consider that a strong suggestion then. After all, there can be
> no surprise at the lack of translations if nobody thought of telling the
> translators.
> The usual way is to alert the translators when a release is about to be
> made, but leaving them some time to actually do the work -- maybe a week
> or two. It could be a good idea to notify them each time a new release
> branch is forked off as well, since a lot of strings may have changed
> from the previous release and that will give a little more time for
> preparation.

Should we retroactively send a round of "Hey, 1.8.x has been released,
please update translations on trunk and 1.8.x" ?

Can you update docs/community/releasing.part.html or roadmap.html with
a reminder to consider sending a Call For Translations to translators?
Received on 2013-08-08 20:39:51 CEST

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