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

Hi :)

I think these translations are going to need to be done by more than 1 person!  

Perhaps IF people do happen to choose the same page as someone else then some 
sort of quick comparison to get the best ideas off both (or more) versions.  I 
am certain there are some great tools to help with collaboration and team work 
for translators!  I just had a quick look in my package manager and found LOTS.

I thought there were already teams in place already working with good tools.  
Perhaps there is a separate mailing list that people have missed?

Regards from
Tom :)

From: Alexander Thurgood <>
Sent: Wed, 26 January, 2011 15:22:11
Subject: [libreoffice-documentation] Re: General question about translation of 
documentation and organisation within Alfresco

Le 26/01/11 16:04, Jeremy Cartwright a écrit :

Hi Jeremy,

Alfresco  enables you to store translated versions of content against
the native language content item, so the relationship is always
maintained. It controls these translations with versioning and other
content services.

That sounds pretty interesting from where I'm sitting, although it would
be interesting to see exactly how it deals with versioning of the
translation, I guess much in the same way as versioning for an original
document ?

Setting it up seems relatively easy, and just becomes a matter of how
we want our directory structure. As it stands, the en-US versions are
located in Company Home/LibreOffice Documentation/catalog/all our books.

Off the cuff, my thoughts are we can modify our structure as:
1) Company Home/LibreOffice Documentation/en-US/all our books
or 2) Company Home/LibreOffice Documentation/l10n/language-COUNTRY/books
where for the first choice all translations (inc. en-US) share
identical structures, and the second choice the translated versions are
grouped in a 'special' spot.


I suppose it all boils down to whether contributors are going to provide
original documentation in their own language which can then be
translated into a myriad other languages, or whether we agree that en_US
is the reference language and any other language contributions can only
be translations thereof. The second option is, IMHO, more restrictive in
that it excludes, as I understand it, any possibility for original
contributions in a language other than EN. From this point of view, and
based on the fact that a lot of original documentation in the previous
OOo project actually came from non-English speaking projects (including
myself, having written both in English and French), it might be
preferable to have a l10n structure, but as I said, that is just my
personal opinion.

I would be more than happy to setup a space-tree if someone could
provide a translation of the current space-tree spaces, and some
consensus were reached regarding the tree setup.

Sure, I can provide you with translations into French no problem, in
German as well I guess, unless someone else here volunteers (a native
German speaker for example ?)


Unsubscribe instructions: E-mail to
List archive:
*** All posts to this list are publicly archived for eternity ***

Unsubscribe instructions: E-mail to
List archive:
*** All posts to this list are publicly archived for eternity ***


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.