IntroductionThe Eclipse Babel Project is a proposed open source project under the Eclipse Technology Project.
This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process document) and is written to declare its intent and scope. This proposal is written to solicit additional participation and input from the Eclipse community. You are invited to comment on and/or join the project. Please send all feedback to the http://www.eclipse.org/newsportal/thread.php?group=eclipse.technology.babel newsgroup.
Eclipse is a global community. It is in everyone’s interest to ensure that Eclipse is available and translated in as many locales as possible. We are proposing a set of tools to make the job of globalizing Eclipse projects easier. We also want to provide ways for people world wide, who are interested, to contribute translations in their language of choice.
IBM and BEA are jointly proposing a globalization project at Eclipse. The project will include tools and activities that are needed to adapt the Eclipse deliverables to properly run in multiple locales and to translate selected Eclipse projects into multiple different languages (French, Japanese, German, etc). The project could include tools to aid in the following areas: Enablement testing (E.g. can the software run in different language environments and handle multiple scripts, etc.), translatability testing (is it ready for translation?), preparation for translation (preparation of resource bundles), Translation testing (Is the translation acceptable?), etc.
Software globalization is more than just translating strings! The following are the potential features for the Eclipse Babel Project:
Stream line the creation of National Language (NL) fragments
- JDT Editor currently has the function to globalize strings in Java programs. PDE also has the ability to create NL fragment project for any plug-in project. However, the two functions are not very well streamlined together. Eclipse Babel Project will better integrate the functions together to make it easier for programmers to create the NL fragment project for the plug-in project they are working on.
Translation File Preparation Tools
- Validate syntax of resource bundle files
- to list a few common Java resource bundle files syntax problems: missing "=" in Java resource bundle files, missing continuation chars, hard-coded font in html files (hard-coded font may not be available in other locales)
- Spell check resource bundle files
- spell checked resource bundle files will improve software quality and reduce translation questions
- Add translation instructions
- need ability to add translation instructions. For example, instructions telling translators not to translate certain keywords
- Mark non-translatable strings or files
- need ability to mark certain strings or files to be non-translatable
- Indicate single and double quote handling
- depending on whether the strings would be processed by Java MessageFormat class, quotes may need to be duplicated in order to be displayed correctly
Globalization Enablement Test Tools
- pseudo translation generation tool for testing layout, encoding, and unexternalized strings
- find the enablement problems that hinder translations
- host the translation files on server
- allow contributors to translate strings in translation files
- allow contributors to search the translation repository for common translated terms
- protect keys, non-translatable strings and files
- committers review and release translation files back to repository
- build NL fragments
Translation Verification Tools
- display and check if the translation make sense in the context of the use case
- display and check if the translations are consistent from project to project
OrganizationThe work of the Eclipse Babel Project can be organized under 2 broad umbrellas:
- A community and process framework via which translations to existing components of the platform can be contributed and organized into the production of localized releases. This infrastructure would allow various interested and capable parties to contribute translations for different parts of different components, and define a process by which those translations are verified, approved merged, and ultimately delivered in a localized release.
- Technology (tools and features both standalone and incorporated into other projects) which ensures that the ongoing development of the Eclipse Platform results in artifacts that are easily localized.
- Richard Gronback, Borland
- John Graham, Sybase
Proposed Initial CommittersThe following companies will contribute initial committers to get the project started:
- Chris Nguyen (firstname.lastname@example.org) - CoLead
- Kit Lo (email@example.com) - CoLead
- Paul Colton (firstname.lastname@example.org)
- Nigel Westbury (email@example.com)
- Jess Garms (firstname.lastname@example.org)
- Werner Keil (email@example.com)
- Daniel McGowan (firstname.lastname@example.org)
We welcome additional committers to the project.
Interested PartiesIBM and BEA, as the submitter of this proposal, welcomes interested parties to post to the newsgroup and ask to be added to the list as interested parties or to suggest changes to this document. A number of companies have expressed interest in the project and/or its components thus far. This list will be updated periodically to reflect the growing interest in this project:
- Discovery Machine, Howard Lewis (email@example.com)
- Sybase, John Graham (firstname.lastname@example.org)