Re: Stats (not) updating correctly

["Domingo Becker" <domingobecker gmail com>]

> > Other ideas to make transtators life easier ?
>
> I suspect that the right answer is to do a merge on fetch, perhaps with
> some caching.  So when you go to transifex and get the file, it checks
> to see if the pot file is newer than the po.  If so, it does a merge and
> then hands you the merged po.  When the translator commits back, then,
> the commit is the merged file.  If the translator is instead using the
> VCS directly, then I think that doing a msgmerge probably isn't the
> worse thing (and could be scripted as well)
>

Why not get a process launched when transifex gets a pot update?
If transifex gets a pot update, then would look at the existing po
files and updates them.
We would be taking the merge to the maintainer side.
Then the status page would show the new untranslated strings.

> Similarly, the status pages would need to do the same.  And to avoid the
> pain of lots of repeated msgmerge'ing, you may want to keep stats cached
> with an associated .pot and .po modification time.  Then you only have
> to regenerate the stat if the modification times have changed
>

Domingo Becker