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

Hi Marc,

On Mon, Nov 15, 2010 at 4:04 PM, Marc Paré <> wrote:
Le 2010-11-15 06:20, Alexander Thurgood a écrit :

Hi Marc,

Le 15/11/10 11:40, Marc Paré a écrit :

Would there be any idea on how to do this efficiently?

Within the OOo project, this task was carried out by the N-L leads and
co-leads. Annoucements were made on the OOo announcement lists, then
translated by the N-L leads/co-leads and then posted to the
corresponding list.

It actually worked pretty well IMHO.


Has this been setup?

No, it's on a volunteer basis, so the one who can do it, does it. The
native language groups have different size, different objectives and
different organization. So, we (native-lang groups) know that the
communication should be bi-directional, but it is a 'should', not a
'must'. So often you will have people listening to one or another
group and propagate the information else where. And sometime,
something that is really relevant for a group won't be for another, so
the last one won't bother about it. It's up to each group to determine
what is important for him.
If you have something really important to share and you want to touch
the native language group, then go on the l10n list.

Kind regards
Founding member of The Document Foundation

E-mail to for instructions on how to unsubscribe
List archives are available at
All messages you send to this list will be publicly archived and cannot be deleted


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.