Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Internationalization Support"

(Higgins Internationalization Proposed Implementation Plan)
Line 21: Line 21:
 
== Higgins Internationalization Proposed Implementation Plan ==
 
== Higgins Internationalization Proposed Implementation Plan ==
 
* Phase 1 - There will be several parts to this first pilot phase:  
 
* Phase 1 - There will be several parts to this first pilot phase:  
** David to drive the I18N requirements and code changes for IdAS in support of his project. This will be the pilot project to run through the current proposed I18N standard as noted [http://www.eclipse.org/resources/?category=Internationalization here].  
+
** David to drive the I18N requirements and code changes for IdAS API package in support of his project. This will be the pilot project to run through the current proposed I18N standard as noted [http://www.eclipse.org/resources/?category=Internationalization here].  
 
** Once David and team are done with this project, they will document on wiki their findings and summary.  
 
** Once David and team are done with this project, they will document on wiki their findings and summary.  
 
** During this phase it is incumbent on other Higgins committers and/or component owners to review and voice any opinions, concerns or provide input on the general I18N requirements that are being applied in this pilot phase. The intent would be to learn from this pilot and then apply this standard and process across all Higgins components in future phases.
 
** During this phase it is incumbent on other Higgins committers and/or component owners to review and voice any opinions, concerns or provide input on the general I18N requirements that are being applied in this pilot phase. The intent would be to learn from this pilot and then apply this standard and process across all Higgins components in future phases.

Revision as of 12:14, 3 July 2008

{{#eclipseproject:technology.higgins}}

Higgins logo 76Wx100H.jpg

This page is information for active committers and contributors about Internationalization of the Higgins project.

Draft

Overview

This page is to propose the Internationalization guidelines for Higgins projects.

All components and solutions must support internationalization. The goal is to have Higgins code internationalized, such that other users could localize the code to their native deployment requirements. Eclipse Globalization Guidelines. Two proposals were reviewed at the 19-June-08 Higgins Developer call:

Proposal 1

Use a Higgins common messages package and place all translatable strings in this properties file. The STS component is using org.eclipse.higgins.messages. This creates a common component, but makes translation a little less flexible and all components would carry the strings for all packages. This might make managing Higgins translation packs easier, when using multiple components in a solution.

Proposal 2

Because the Higgins components are packaged as OSGi bundles (plugins) the Eclipse guidelines for Internationalization would apply (many of the guidelines would still apply, if using Proposal 1). Guidelines and 'how to' instructions for development and testing located here.

Each Higgins OSGi Plug-in would have its own properties file containing the translatable strings. the messages can be translated component by component. There are more files to handle, but it makes the component translation more independent.

After discussion and review at this meeting, it was decided that Proposal 2 would be the one Higgins would adopt for the next step (phase 1 noted below) to adopt I18N requirements for Higgins components.

Higgins Internationalization Proposed Implementation Plan

  • Phase 1 - There will be several parts to this first pilot phase:
    • David to drive the I18N requirements and code changes for IdAS API package in support of his project. This will be the pilot project to run through the current proposed I18N standard as noted here.
    • Once David and team are done with this project, they will document on wiki their findings and summary.
    • During this phase it is incumbent on other Higgins committers and/or component owners to review and voice any opinions, concerns or provide input on the general I18N requirements that are being applied in this pilot phase. The intent would be to learn from this pilot and then apply this standard and process across all Higgins components in future phases.
  • Phase 2 - Brian/Mary will leverage the phase 1 work to do the following:
    • Host/broadcast any updates to the I18N standard that come out of phase 1 pilot experience to the Higgins community.
    • Help identify/prioritize the next Higgins components that should next adopt/update their code to support the I18N requirements and facilitate/drive getting these next round of components compliant with the I18N standard.

Other Internationalization Consideration

Other coding practices

Other coding practices from the guidelines should be followed. Automated testing on internationalized configurations should be considered.

Internationalization of the Browser Plug-ins should follow the same conventions, but may be constrained by the browser conventions.

Babel

Actual translations and language packs can be provided by consumers. An incubator project, Babel, supplies a set of tools to import *.property files from projects and make the translation possible through a community of translator. Translations could also be contributed by consumers. Babel should be explored to see if the Higgins could exploit the translator community for language pack development. Babel project/tools in Eclipse found here.

Babel RCP plug-in could be used to help localize messages, check for errors.

Back to the top