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


I would like to propose that unlike what existed under Sun and Oracle, the linguistic communities 
_including_ the English speaking community, are all identified by a specific language marker and 
that all the lists that do not use that language marker are explicitly multilingual.

The status quo under Sun and Oracle came from the fact that both Sun and Oracle were American based 
and mostly English speaking structures but we have no reason to reproduce that in the TDF.


That basically means that:

All the English speaking lists are @en.libreoffice.org

And that all the lists @libreoffice.org are multilingual.

This is the only way to ensure that no linguistic community has more power in the decision process 
than any other which is a basic requirement for all democratic process.

There are enough multilingual people in the respective communities to ensure that the communication 
gap is bridged in all those lists.


Jean-Christophe Helary
----------------------------------------
fun: http://mac4translators.blogspot.com
work: http://www.doublet.jp (ja/en > fr)
tweets: http://twitter.com/brandelune


--
E-mail to discuss+help@documentfoundation.org for instructions on how to unsubscribe
List archives are available at http://www.documentfoundation.org/lists/discuss/
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.