These tips and best practices apply to all pagelets that will be translated into multiple languages.

	Identify ALL culturally dependent data. Text messages are the most obvious example of locale-specific data, but there are many other parts of a service that can vary with language or location. These include: images, UI labels and buttons, icons, sounds, graphics, dates, times, measurements, honorifics and titles, phone numbers, and postal addresses. In ALI portal, the title bar for the portlet must also be localized; for details, see Modifying the Portlet Title Bar.
	Do not use compound messages (concatenated strings) to create text. Compound messages contain variable data. For example, in the text string “You have XX credits,” only the integer “XX” will vary. However, the position of the integer in the sentence is not the same in all languages. If the message is coded as a concatenated string, it cannot be translated without rewriting the code.
	Use the IDK to avoid encoding issues. All content is stored in the database in Unicode. The IDK handles encoding for international characters.

For details on implementing internationalization, see Using Internationalized Strings in Adaptive Tags.