Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index




Em 31-10-2010 13:16, Sophie Gautier escreveu:
Hi André, all,

2010/10/31 André Schnabel<andre.schnabel@gmx.net>:
Hi *,

the BrOffice team was so kind to sponsor a server that would be able to host
a pootle installation for all our translations (LibO 3.4 and beyond).

Thanks a lot to the BrOffice team, this is a great and important
support for all our teams!

My pleasure, Sophie.
I hope there will be room for QA left....



We can also use this (with a very limited setup) for LibO 3.3 translations (
only the lo-bild.po files). The initial setup is more or less done, but we
need to fix some issues (e.g. self-registration does not work yet). I hope,
we have this in place as soon as we have the final UI strings for 3.3
(should early next week).

Ok, thank you for this info and for your work on this.

Hmmmm... I am sort of concerned on "self registration". Does it means that anyone can register and start adding suggestions to every string we have?. That can be hard to fix/clean later... Isn't better to have this under more strict control?

Regards
--
Olivier Hallot
Steering Commitee
The Document Foundation

--
E-mail to l10n+help@libreoffice.org for instructions on how to unsubscribe
List archives are available at http://www.libreoffice.org/lists/l10n/
All messages you send to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.