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.
Difference between revisions of "Internationalization Support"
(→User Interfaces: Added proposal 2) |
m (→Babel) |
||
| Line 27: | Line 27: | ||
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 [http://babel.eclipse.org here]. | 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 [http://babel.eclipse.org here]. | ||
| + | |||
| + | Babel RCP plug-in could be used to help localize messages, check for errors. | ||
Revision as of 11:59, 19 June 2008
{{#eclipseproject:technology.higgins}}
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.
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.
Other Internationalization Consideration
Other coding practices from the guidelines should be followed. Automated testing on internationalized configurations should be considered.
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.