Difference between revisions of "Internationalization"

From Eclipsepedia

Jump to: navigation, search
Line 3: Line 3:
 
Some Eclipse plug-ins use [[ICU4J]] APIs when working with locale-specific content.
 
Some Eclipse plug-ins use [[ICU4J]] APIs when working with locale-specific content.
  
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 techniques using String objects as keys.
+
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.
  
 
----
 
----
 
Back to [[Eclipse Project]] home
 
Back to [[Eclipse Project]] home

Revision as of 15:07, 14 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.


Back to Eclipse Project home