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"
| Line 5: | Line 5: | ||
Most Eclipse plug-ins use a special [http://www.eclipse.org/eclipse/platform-core/documents/3.1/message_bundles.html Eclipse message bundle] mechanism for working with translated strings. This mechanism uses traditional Java message.properties files, but without using String-based keys. This has much better memory usage characteristics than traditional approaches. | Most Eclipse plug-ins use a special [http://www.eclipse.org/eclipse/platform-core/documents/3.1/message_bundles.html Eclipse message bundle] mechanism for working with translated strings. This mechanism uses traditional Java message.properties files, but without using String-based keys. This has much better memory usage characteristics than traditional approaches. | ||
| − | For Bidirectional locales, like Arabic and Hebrew, some new Bidi-specific APIs were added to Eclipse 3.2 that inject directional markers into strings with implicit left-to-right meaning (such as file paths and URLs) in order to render them properly when the text is mixed. This was a necessary due to an apparent bug in rendering these strings containing mixed text on Windows. The problem appears more frequently on Windows platforms (vs Linux), but has also been found to occur on Linux in certain cases. See the Unicode [http://www.unicode.org/reports/tr9/ Bidirectional algorithm] for the specifics on how strings are normally rendered in bidirectional locales. | + | For Bidirectional locales, like Arabic and Hebrew, some new [[New Bidi APIs | Bidi-specific APIs]] were added to Eclipse 3.2 that inject directional markers into strings with implicit left-to-right meaning (such as file paths and URLs) in order to render them properly when the text is mixed. This was a necessary due to an apparent bug in rendering these strings containing mixed text on Windows. The problem appears more frequently on Windows platforms (vs Linux), but has also been found to occur on Linux in certain cases. See the Unicode [http://www.unicode.org/reports/tr9/ Bidirectional algorithm] for the specifics on how strings are normally rendered in bidirectional locales. |
---- | ---- | ||
Back to [[Eclipse Project]] home | Back to [[Eclipse Project]] home | ||
Revision as of 14:15, 16 June 2006
This page is a hub for resources relating to preparing Eclipse for use in other languages and locales (also known by the abbreviation i18n). This work involves translating strings into other languages (often called NLS for Natural Language Support), handling bi-directional text (BIDI), and preparing content such as dates and times in a format appropriate for a given locale.
Some Eclipse plug-ins use ICU4J APIs when working with locale-specific content.
Most Eclipse plug-ins use a special Eclipse message bundle mechanism for working with translated strings. This mechanism uses traditional Java message.properties files, but without using String-based keys. This has much better memory usage characteristics than traditional approaches.
For Bidirectional locales, like Arabic and Hebrew, some new Bidi-specific APIs were added to Eclipse 3.2 that inject directional markers into strings with implicit left-to-right meaning (such as file paths and URLs) in order to render them properly when the text is mixed. This was a necessary due to an apparent bug in rendering these strings containing mixed text on Windows. The problem appears more frequently on Windows platforms (vs Linux), but has also been found to occur on Linux in certain cases. See the Unicode Bidirectional algorithm for the specifics on how strings are normally rendered in bidirectional locales.
Back to Eclipse Project home