X Internationalization

• Ability to widen sales opportunities in world markets due to a common source base for global application development.
• Reduce time writing workarounds for other languages by following a complete API set for Input and Output Methods.
• Ability to enhance compatibility and interoperability of global applications by following a common reference implementation.
• Ability to extend new features to suit their own needs and to participate in the evolution of the code base.
• Decreased time to market through stable, market tested code implementation.

The X Window system is the foundation of the current implementations of Gnome and OpenOffice. By having a unifying framework for globalization in X, the Gnome desktop and OpenOffice can take advantage of a consistent and integrated internationalization framework and thus avoid platform specific code.

Sun has a commitment to help raise the standards of open platform application development. Sun actively participates in many industry-wide forums which promote universal application development across platforms and languages such as Java, XML, Mozilla, X.Org, Li18nux, and now the GNOME Foundation and OpenOffice.org.
Opening the X internationalization code is another opportunity to emphasize its desire for active participation in the formation of industry standards for global application development. With high quality industry standards, more applications will be available which work across all versions of UNIX, including Solaris and Linux. If this framework is adopted, more language engines will be available which are compatible with Solaris.

X Input Method Framework
	- IIIMF based i18n libX11 library (xiiimp.so)
	  -------------------------------------------
	  When used with an extended API, allows X application to have 	
	  locale independent input method capability.
	
	- XIM Patch for IIIMP Client-Adapter
	  ----------------------------------
	  Patch to X.Org's xc/lib/X11. Provides easier way for 		
	  developers to modify the X library to work with IIIMP 		
	  (Internet/Intranet Input Method Protocol)
	
	- XIM BackEnd Module (htt_xbe)
	  ----------------------------
	  Bridge module between X applications and IIIMP server
	
	- IIIMF Input Method Server
	  -------------------------
	  Provides a connection between the language engine and the     
          application
	  
	- Language engine interface drivers (under CM, XCI)
	  -------------------------------------------------
	  Provides the interface to language engines
	
	- Language engines
		* mle.so (for Korean, Traditional and Simplified Chinese)
		* New pinyin (newpy.so) for Simplified Chinese
		* Generic composition engine for European languages
	  --------------------------------------------------	
	  Input event conversion from the keyboard to language         	
	  character sets	
		
	-IIIMP watch dog Module (htt)	
	 ----------------------------
	  Safeguard to make sure IIIMP server always up and running
		
X Output Method Frameworks
	_ Complex Text Layout engine support
	  ----------------------------------
	  Support for bi-directional rendering of Hebrew and Arabic characters.
	
X Locale Convertor Module
	  support for eucJP, shift-JIS, Big5, GBK and all
	  Unicode (UTF-8) locales

IIIMF Input Method Server Libraries
	- Language Engine SPI Library (SunIM Library)
	  -------------------------------------------
	  Common interface to plug in language engines to IIIM server
	  
	- Code Converter Library (P-I Conv)
	  ---------------------------------
	  API to plug in code convertor modules from multiple UNIX       	
	  layouts such as ICU, iconv etc.
	  
	- IM Developer Kit Library(IMdkit)
	  ---------------------------------
	  API to plug in IM protocol support to IIIM server
	  such as XIMP 4.0, XIMCP, IIIMP

 

Based on the X11R6 framework, Sun has further enhanced these components to provide a split shared object model. What this means is that the XOM, XIM, and XLC shared objects have been separated so they can all be loaded by libX11 independently. With the locale specific portions live in separate libraries, this will help reduce the core X lib size by 20-30% and enables dynamic configurability of the internationalized X library. Users will be able to select the most suitable configuration of the X library environment to safisfy their primary language and needs. In addition, the XIM architecture has been enhanced to enable multiple language input environment, whereby users can select the most suitable Input Method model that will meet their practical needs.

For example, users who want to make use of the Chinese language can easily choose the specific Chinese XOM object. On the other hand, there will be users who do not use Chinese, and this set of users can use an XOM object which provides less functionality, which may give them better performance. As for localization engineers, the inherent benefit is that they do not need to develop new xlibI18n shared object for every new locales introduced.

For open source developers, administrator of Xlib, they may want to know these modules so that they can easily load these dynamically loadable modules correctly, depending upon which modules are needed.
For Input Method/language engine developers, the Input Method/language engine interface modules is something that will be highly beneficial for them. It can provide them with an opportunity to design various Input Method solutions that can scale from Personal Digital Assistant (PDA) to Internet/Intranet based network computing and meet the needs of the various platform providers.
For X Application Developers, they do not have to care about these modules as they will be provided transparently. However, they will need to use the appropriate I18n aware XIM/XOM APIs.
For integrators, these modules will enable them to package the relevant modules to their users' requirements in a flexible manner.

There is no significant performance degradation found. In fact the absolute time required to execute these functions is so small that users will not notice the difference at all.