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"
m (→Overview) |
m (→Components: Added summary of proposal) |
||
| Line 10: | Line 10: | ||
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. | 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. | |
== User Interfaces == | == User Interfaces == | ||
Internationalizing Browser extensions and RCP plug-ins | Internationalizing Browser extensions and RCP plug-ins | ||
Revision as of 11:33, 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.
User Interfaces
Internationalizing Browser extensions and RCP plug-ins