Hi Friedel et al.,
good to know you're making progress in version 2.x. Btw. we ordered a
new Pootle server for the OO.o community so we can get rid of the old
infrastructure. We may need your help Friedel to set up a Pootle 2.x on
the machine (and yes with a Linux ;-) ). That's the good news the bad
one is, we won't have this server in place for the current 3.3
translation round, sorry.
Cheers,
Frank
F Wolff schrieb:
Op Di, 2010-06-22 om 14:42 +0200 skryf Rafaella Braconi:
Hi Olivier,
Hi everybody
On 22.06.10 11:59, Olivier Hallot wrote:
Hi Rafaella
It is (so far) in the UI.
Please take a look, for instance, at the CUI folder as it contains all
strings for the options, the dialogs, tab pages and customization.
This is something ready from the begining of the project. Other
folders seems to have the same problem, and I have no way to easily
point what went wrong.
the problem is always that whenever there is a resource shifting it's
very difficult to keep the translations... I wonder if 3.2 tmx files
would help to recover old translations.
They can be found at:
http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/tmx32/
In summary, pt-BR UI got back to 90% of translated strings (from 100%)
and that does not seem correct with respect to the new features
announced for OO 3.3.
On a side note, I really think we need a version control on the po
files...
I think that a more powerful translation memory in Pootle would help...
I am surprised to hear that the PO files aren't in version control - it
has many advantages, so I would strongly recommend it. Translation
memory in Pootle will solve some of the issues we are talking about, but
I still believe we need a way to find specific versions of the
translations reliably.
The upcoming version of Pootle has made good progress towards giving
translation memory in the online translation interface. Although the
final bits aren't implemented yet, I hope we can have it reasonably
soon. I'd really appreciate it if people can get involved - at least
for working towards a user interface for it. For the case of OOo
(especially if stuff moved around), I think using TMX files during the
upgrade and/or pomigrate2 is still the better solution anyway, since a
cleaner migration to a new version means less review work, whereas
translation memory would mean more information for translators, but
requiring lots of review.
Keep well
Friedel
--
Recently on my blog:
http://translate.org.za/blogs/friedel/en/content/emotions-and-localisation
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: dev-h...@l10n.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: dev-h...@l10n.openoffice.org
