Skip to content

start:

L10n Pilot Process

Localization Pilot Process


1. Introduction
2. Collaboration Goals
3. Translation
4. Localization Testing
5. Communication
6. How to Participate

1. Introduction

Starting with a short survey in June 2004, Sun Globalization (G11n) Engineering group responsible for localization of several SO/OO.o languages has been working with corresponding OO.o community leads to improve collaboration effort in translation and localization testing (meeting minutes). These languages are:

German
French
Italian
Spanish
Swedish
Brazilian Portuguese
Japanese
Korean
Simplified Chinese
Traditional Chinese

In short, we (Sun G11n, OO.o communities) have agreed on a set of high level goals, identified each other's capacity, shared the processes and tools, and agreed to experiment collaborative work in OO.o 2.0/SO8 l10n based on shared goals. This web page provides current status of such effort. Also available on this page are links to the tools that Sun G11n has been using for translation and localization testing for various Sun products and services.

As it is called a pilot, tools and processes mentioned here are not in their final state and may need enhancement (hence, this webpage for everyone who cares!). Also the languages referred on this page limit to those that are listed above at this time.


Top

2. Collaboration Goals

2.1 Short Term

- We experiment joint effort on -a subset of- immediate release (i.e. OO.o2.0/SO8), in the areas of translation, linguistic review, and localization testing
- We assess existing Sun G11n tools and processes in comparison to the others that are known to the Community
- We enhance communication between each other.

2.2 Long Term

- We join forces throughout product releases to ensure quality of localized OO.o/SO products, by collaborating in the areas of translation, linguistic review, and localization testing
- We set up a localization process that is easy to follow, open, and can be shared with all OO.o Communities

Sun G11n open-sources translation tools.

Top

3. Translation

3.1 Process

Most of SO translation is outsourced today. For several languages, there are linguists within Sun G11n who evaluate the quality of translations and ensure consistent quality across Sun's localized products. Due to a historical reason being that Sun has provided all translations in the past, most Communities have expressed that they're not experienced in translation. In the pilot process, we have agreed that the Community translates and quality-assures a small portion of translatable component (UI, Online Help), while Sun G11n provides the rest of translation. Each of Sun's linguists and the corresponding Community have formed a team to ensure the translation quality of the product. There are some languages that Sun will continue to provide translation of entire OO.o2.0/SO8 content, and the reasons are indicated below:
  • German - Community lead expressed that there are no volunteers for translation, perhaps because they may not see the needs ("Sun provides excellent quality German SO already.")
  • Korean - There are not enough contributors or members in the Korean OO.o Community yet.
  • Swedish - There is no OO.o Community.
As the rest of the Communities contributes to translation at this time, they also experiment translation tools that are developed and used by Sun G11n.



Top

3.2 Translation Tools

3.2.1 At a glance

Sun has developed and is currently using several tools in its translation process. Sun is looking into open-sourcing them for further enhancement and wider acceptance in the Open Source communities:

Tools
 Description
Sun Translation Editor (STE)
  • A stand-alone, downloadable application written in Java; handles XML based xlz/xlf file formats
  • Downloadable through G11n Portal
  • Advantages of using STE <link to Tim's email justification>
  • Manual (.pdf)
Sun Gloss
  • Web-based glossary database
  • Read-only access to G11n Portal users
  • Allows users to search existing terminology and suggest new terminology (languages in Section 1.)
  • Allows users to build glossaries, given Import access right (languages not listed in Section 1.)
Translation Style Guide
  • Available for each language (mentioned in Section 1)
  • Defines stylistic preferences to ensure OO.o/SO translation maintains consistency with other Sun products
  • Plays a crucial role with Sun Gloss, in helping translators with consistent translation quality
Linguistic QA Matrix (.sxc)
  • A spreadsheet format
  • Used to assess and provide feedback on translation quality
G11n Portal
  • A workflow management tool designed for Sun G11n and external vendor interaction
  • Gateway to STE and Sun Gloss
  • Requires user access

Top

3.2.2 Using the tools

Both STE and Sun Gloss (and each user's guide) access are available only through G11n Portal which requires user access at this time. To be granted user access, send the following information to sofia.nilsson@sun.com:

First Name:
Last Name:
OO.o Login Name:
Email Address:
Phone Number:
Address:
City:
Country:
State/Province:
Zip:
Language (you're contributing):

Please note that Mozilla (not Mozilla Firefox) is the recommended browser for the G11n Portal. It can be downloaded from http://www.mozilla.org/products/mozilla1.x/

Top

4. Localization Testing

4.1 Process

Sun G11n is currently in process of scheduling a meeting with OO.o community leads to discuss l10n testing process. Further details are to be published, after the meeting(s). We expect the meetings to take place within November.

4.2 Testing Tools

4.2.1 At a glance

Sun G11n has developed a set of tools to be used in the localization testing process:
Tools
 Description
Test Plan
  • Contains a high level test strategy
  • Defines platforms, locales, test cycles to perform
  • Describes steps to participate in l10n testing
Test Cases
  • As OO.o/SO is a huge product to test every possible behavior, Sun G11n team developed user-focused, scenario-based Test Cases where many of traditional test case items are covered as part of performing a scenario.
TCM (Test Case Management)

- About TCM
- TCM Log-in
  • Web-based tool to manage test cases and test results
  • Allows users to import test cases (languages not listed in Section 1.)
  • Community leads can give access to their contributors, sign up test areas for individuals, modify test cases (including translating them) for their languages.

4.2.2 Using the tools

TCM is available to all users who are given accounts by TCM administrator. Such administration is currently done by each of OO.o community leads and a few Sun g11n QA engineers. Please send the following information to tcmrequest@l10n.openoffice.org or to your Native-Lang Community lead, in order to sign up for specific areas of your testing interests (See Table in Section 4 of the Test Plan):

OO.o Login Name:
Language of the product you're testing:
Platform (i.e. W2K, WXP, Fedora, Solaris10/x86, etc.):
Test Areas of your interest (i.e. Calc-2, Overall-1, etc):


Top

5. Communication

5.1 Short Term

The pilotprocess@l10n.openoffice.org mailing alias has been set up for specific communication on this pilot process. The alias consists of the Sun G11n and OO.o Community team members who are participating in translation/linguistic QA and/or l10n QA, and coordination of these areas:
Languages
 OO.o Native-Lang
Community leads		 Sun G11n
- translation
 Sun G11n
- l10n QA
German
 Andre Schnabel Monica Badia
 Petr Dudacek
French Sophie Gautier Brigitte Le Grand
 Petr Dudacek
Italian Riccardo Losselli (translation)
Davide Dozza (QA)		 Monica Badia Petr Dudacek
Spanish Richard Holt
Alexandro Colorado
 Aridane Vilardaga-Viera Petr Dudacek
Swedish
 None Sofia Nilsson
 Ian McDonnell
Brazilian Portuguese
 Claudio Ferreira Filho Gusta Marques Petr Dudacek
Japanese
 Shu Minari
Nakata Maho (translation)
 Reiko Saito
 Naoyuki Ishimura
Korean
 Jeongkyu Kim Dawn Dong-Eun Lee Simford Dong
Chinese (Simp/Trad)
 Pui-Lam Wong Serena Xiao
 Simford Dong


Other Sun SO G11n team and their roles:
Roles Sun G11n Description
OO.o Community Tools Support (Sun Translation Editor)
 Tim Foster
 - answers technical questions raised by OO.o communities on STE
Linguistic QA Matrix
 Monica Badia (EMEA)
Reiko Saito (APAC)
 - responsible for maintaining the matrix to capture important quality assessment of translations
G11n Tools Champion (Sun Gloss, Portal)
 Sofia Nilsson - grants user access to OO.o communities for Portal/SunGloss/Sun Translation Editor
SO internationalization engineer
 Karl Hong
 - works with base team on i18n issues
SO G11n Central Engineer
 Ian McDonnell
(iano@openoffice.org)
 - owner of translation issues (translation@openoffice.org)
- prepares source files for translation for hand-off to translators
- checks and imports translated files to the source
SO G11n QA lead
 Naoyuki Ishimura - main contact for l10n QA related issues
- TCM administrator
Program Manager - SO/OO.o Pilot process
 Irina Stamatoiu
 - leads OO.o community translation/testing pilot process
Translation Vendor Manager
 Magdy Abdel Koddous
 - manages translation/language QA work flow with Sun  language leads and partners
SO G11n program manager
 Young Joo Song - responsible for project schedule, scope, and general OO.o communication
- OO.o l10n co-lead

5.2 Long Term

Move the communication to one of the more generic OO.o mailing alias (dev@l10n.openoffice.org), if/when this process is adopted to more Native-Lang projects, and a wider distribution is appropriate.

Top

6. How to participate

Many of Sun G11n's existing tools have been internally developed to accommodate daily needs to interact with partners ("vendors") and require Sun G11n's administration at this time, which we believe is inappropriate for the use with OO.o communities. Nevertheless, we welcome your participation and would like to hear from you, whether it is translation, linguistic review, localization testing, or evaluation of our tools that you may be interested in!

For general suggestions or comments on the tools and processes, send email to dev@l10n.openoffice.org with specific reference.


6.1 All Participants

  • All contributors to OO.o must sign Joint Copyright Agreement (JCA).
  • What is JCA? - FAQ about JCA.
  • Where is JCA form? - This is link to a PDF format of JCA form.

6.2 Languages listed in this page

  • Sun G11n has met and communicated mainly with each of community leads since June. If you were not available in the past, but would like to contribute in collaboration areas mentioned on this page (including evaluation of tools), follow steps noted in the Sections 3.2.2 and 4.2.2. In addition, let your community leads know. Welcome!

6.3 Other Native-Lang Projects

  • If you're interested in using Sun Gloss to build a glossary, search terms in other languages that you're familiar with, and evaluate STE for the future use, follow steps in 3.2.2 of this webpage.
  • You may also choose to import l10n test cases to TCM, use it to have an overview of testing coverage, generate various reports, and manage testing projects in your community. Refer to Section 4.2.2 in such a case.
  • There's a discussion about setting up a translation process using .po files. For details, refer to the document written by Javier Sola.

Top

Revision 1.4, 07/27/05
Contact Young Joo Song