incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <>
Subject RE: Native Language vs l10n
Date Fri, 17 Jun 2011 20:30:41 GMT
Khirano san,

On ooo-dev we are talking now about how to support language communities.
Please help my understanding.  I am ignorant.  I have too many questions.  Answer in parts
may be good.

 - Dennis


Does the Japanese Language Project do any work to prepare distributions for the Japanese Language
community?  Could it do so?

Does it provide the translation work for the distribution?

Is all of the release internationalization done in the language pack? 

I see
I see SVN subtree for the JA language project.  I see ja project issues in
the combined Bugzilla issue tracker.  The SVN and Bugzilla infrastructure seems to be in English.
 Could this work separately?

I also see

I think this is mirror of

What is your thinking about parts of Japanese language project working separate from Apache
development?  About coordination of language pack and Apache release and QA?  About ways to
avoid delays in release to users in language communities?

-----Original Message-----
From: Rob Weir [] 
Sent: Friday, June 17, 2011 12:50
Subject: Re: Native Language vs l10n

[ ... ]
For things that impact the product release, things like code contributions,
documentation, translations, etc., things that actually could make the bits
and bytes of the release different, I think it is very important that these
pieces are done in Apache.  And by being in the Apache project, they are
covered by the Apache 2.0 license and by our consensus decision making

For the activities that do not impact the actual contents of the release,
things like user support, country- or language-specific marketing activities
and so on, for these I could see other models working as well.  Remember,
with any Apache project, anyone is free to take the project's source code,
translate it, build it and market it or even sell it.  This could be done
with modifications and enhancements.  This is all possible under the Apache
2.0 license, whether you participate in the project or not.

So if there are existing groups that do such activities under Sun/Oracle, then they can continue to do so, by using Apache OpenOffice.

But when we start talking about the Apache project, then we are not talking
about "groups" joining.  We're talking about individuals joining.  I don't
think we want to have independent, autonomous groups within an Apache

But I wonder whether one solution is this:

1) Strong existing language projects continue to operate independently,
according to their own rules.

2) They ensure that their work is all done under Apache 2.0 license so it is
usable by Apache OpenOffice as well as by LibreOffice

3) Language projects each appoint at least one member to join the Apache
OpenOffice project as a liaison.


View raw message