Sie sind hier: Startseite / Program / Wednesday Secondary Track / The next step of LibreOffice non-English local communities - based on current status of Japanese LoCo -

The next step of LibreOffice non-English local communities - based on current status of Japanese LoCo -

In office productive suites, local communities has very important role to connect between developers community and end-users. We want to share good practices about UI translation, Japanese postal card support and community works of the enterprise use in Japanese local community, and to hava a discussion about the next step of local communities.

Naruhiko Ogasawara
Shinji Enoki
17.Oct.2012 from 12:30 to 13:30
60 minutes

Details of the Talk


For Free/Libre office productive suites as LibreOffice, the local communities (LoCo) have a very important role, "bridge" between upstream development community and end users who are unfamilier about FLOSS way, and not good at English.
I say "bridge", it contains several jobs:
  1. Sending bug reports or functional requests (sometimes they are "local" issue; especially in CJK regions) to upstream
  2. Translation about UI, Help and documentation (includes announcements)
  3. Outreaching to local users (public relations)

Current State in Japan

Good Practices in Japan

We've two "good practices," they could be common knowlegde of most of non-English LoCos.
  1. A patch supports Japanese local paper size (Japanese Postcard (Hagaki)) accepted and released as a part of 3.6.x
    point 1. How to integrate local specified specification in main development community.
  2. In 3.6.1, UI translation coverage became 100%!
    point 2. How to let UI translate coverage up and keep high qualities of translation.

Remaining Problems:

Most biggest one is outreaching.  According to questionnaire by Japanese major web media "IT Pro Active," LibreOffice users are almost 2/3 by OOo/AOO users.
We have to consider how to promote for OOo users to migrate LibreOffice from OOo.
Other small issues; Coverage of help translation is not good enough, and lack of code-level committers to solve CJK specific issues.

Let's Discuss!

LibreOffice is really active and awesome project.  LoCo has a very important part to improve the project worldwide.
Are our practices common in LoCos? Do we have common problems? How we can solve them? What is the next step of LoCos?

Sponsored By

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 GNU Lesser General Public License ( LGPL v.3 ).


"LibreOffice" and "The Document Foundation" are registered 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.

Privacy Policy || Impressum (Legal Info)