Le Wed, 1 Dec 2010 22:00:12 +0930,
Michael Wheatland <email@example.com> a écrit :
On Wed, Dec 1, 2010 at 8:00 PM, Charles-H. Schulz <
I have several people who alerted me about this sentence:
"In order to ensure a quality end product the website will be
developed in English initially then will be opened up to native
language groups within the LibreOffice community to translate and
adapt to best suit the language and culture."
This is written in the i18n wiki page about Drupal. I think the
Native-language teams will be very reluctant to follow english, as
they like to do things their own way. So please let's not impose
frames such as this to communities who just got out of the infamous
Collabnet infrastructure, and ask them what they want first.
I am very keen to get any feedback from the Native Language teams.
To address your concerns, the site must be designed in one language
in order not to cause confusion with administering the
infrastructure, setting up workflows (documentation and designs),
designing the interface and implementing the foundations on which the
community will be built.
I cannot think of any way to develop a fully structured site without
initial development in a single language.
To give you an example: What if Google decided that every language
team should develop their own search engine without input from any
other team? We are simply trying to avoid chaos during the initial
I think -that's my personal feeling here- that we need to have
flexibility; it's one thing to translate a page in several languages,
but it's another one if teams start to open a new, specific page in
their language. If Drupal can do that, then I think it's good.
We already have a very strong multi-national, multi-lingual team
working on the website and I would invite any and all people to have
their input into the site structure and join the Drupal website
development team. If people cannot speak English, I encourage
submissions in other languages and we can use automatic translators
to communicate through the mailing list.
I will adjust the phrasing of the paragraph you have highlighted, but
let me assure you that when the time comes for inputting content and
pages on the site every language will be invited to contribute at the
same time (including English). We simply need to set up the
infrastructure in a common language so we are all pulling in the same
One thing to note is that the main site infrastructure will be
multilingual by default (not English). Project teams such as the
marketing, website, documentation and design teams, just to name a
few, will be multilingual which will lower the barriers for all
languages to get involved with the project and not segregate the
You mentioned the infamous Collabnet infrastructure and we would be
very interested to hear opinions about how the ideal Native Langauge
team infrastructure could be setup? What features, workflows and
tools do all Native Language teams need?
I would appreciate it if you would communicate this back to the
people who have raised concern.
Sure, so thanks to Marc who forwarded this to the l10n list, and I
clarified that if possible the discussion should happen on our present
Unsubscribe instructions: E-mail to firstname.lastname@example.org
List archive: http://www.libreoffice.org/lists/website/
*** All posts to this list are publicly archived for eternity ***
Impressum (Legal Info)
: 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