Chris Leonard wrote on Wed, 2 May 2012 03:30:53 -0400:
> Something like a string-freeze would be very handy
This would mean a bug fix freeze as well as there are quite some of strings
that are hard-coded and untranslatable. I'm currently fixing these and hope
that we will have everything compeletely translatable for our v3.0 release.
> as I find the POT is still changing fairly frequently. I update Poolte to
> the latest and in a day or two, the POT file has changed again. This makes
> it hard for localizers to catch up with string changes.
I don't think so. As the gettext tools do, Pootle should be able to say which
strings are new - either fuzzy or untranslated.
The basic problem is that there is no (or let's say a seldom) data flow
between Pootle and the repository - in both directions. Pootle must regularly
and frequently update from the repository and merge repository stuff with its
stuff. Changes in Pootle must be quickly updated back into the repository by
merging with the existing .po files.
(By "merging" I mean a merging capability like msgmerge has, not just copying
one version over the other one. And by merging, it is no problem to have two
systems where .po files can be edited. Conflicts must be resolved then
similarly to conflicts during svn commits.)
The .po files are just a by-product (helpful for translaters, of course).
The leading files are the AbiWord string header files which define the
strings. This means that the leading system for strings has to be the
repository.
If you need help on the repository side (with a script or so), I volunteer,
but I unfortunately don't know anything about Pootle and its capabilities.
Ingo
Received on Wed May 2 17:22:59 2012
This archive was generated by hypermail 2.1.8 : Wed May 02 2012 - 17:22:59 CEST