На 01.04.10 20:46, Werner Dittmann написа:
Yesterday I did quite some updates to the German translation, worked
thru the procedures etc. At the end I uploaded to resulting de.po file
to pootle. Pootle somewhow reports 100% translated
I am not sure why this is happening. Could it be that the English
strings somehow got into the German properties file?
(BTW it reported
this also when there were about 20 original untranslated messages).
Until now nothing has happend - who triggers a conversion to properties
and the checkin into SC SVN?
When I log in on Pootle, I select SIP Communicator, then click on a
language. I then have a "Translation" (or sth similar) tab when I click
on it I see the "language.po" file and right underneath it I see a
"Commit to VCS" link. I don't know who has the right to use this link so
I've just given you administrator privileges on Pootle so you should now
have it too.
The pootle online page shows a lot of suggestions (for German at least)
- who is responsible to prcess these? How can a suggestion acknowledged,
revised or discarded? By whom? Again, no docu on the pootle site.
If you weren't able to handle them before, you could try again, should
probably work with your admin privileges.
So again, don't bother with the conversions! Do it all through the web!
I don't agree here - doing it all thru the Web seems to cause too much delay
(see my notes above) until the whole cycle:
translate via Web IF - updating SC SVN - SVN update local files - testing -
fixing via Web IF
Well now as soon as you click on to "Commit to VCS" button you should
have them online. If committing is only reserved to admins then I guess
others could do the translations online and then download the .po files
and convert them to properties if they need to test and don't want to
wait for a build.
I seem to recall that Martin mentioned the pootle guys were planning on
adding native .properties support so this process should become easier
in the future.
Again I agree Pootle is probably not perfect as it is but it is a lot
better than what we used to have. Besides I am thinking that we are
probably not doing everything right yet so please, let's all be patient
until we get to know Pootle.
Of course if anyone has a suggestion for a better solution then please
speak up. In any case, keep in mind that when we installed Pootle _all_
languages were dwindling between around 25% and 30% and we didn't even
_know_ this, so I really don't think that going back to simply "no
pootle" is a good idea.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org