This document discusses internationalization and localization. Internationalization is the process of creating applications that can adapt to different languages and regions, abbreviated as I18N. Localization is adapting an application for a specific language or region through translation and locale-specific components, abbreviated as L10N. The document covers internationalization elements like numbers, dates, Unicode, and properties files. It also discusses the JSTL formatting tag library for internationalizing JSP applications.

1. Slide 1 of 30
Internationalization

2. Slide 2 of 30
Objectives
 Introduction to Internationalization
 Internationalization Process
 Internationalization Elements

3. Slide 3 of 30
 Need of Internationalization
– Not all countries across the world speak or
understand English language
– Symbols for currency vary across countries
– Date and Time are represented differently in
some countries
– Spelling also varies amongst some countries
 Alternatives to Solve the Problem
– Develop the entire product in the desired
language
– Translate the entire product in the desired
language

4. Slide 4 of 30
 The process of creating applications which
can adapt and adjust to various countries,
languages and regions is known as
internationalization. The word
“internationalization” is often abbreviated as
I18N.
 The process of adapting an application for a
specific language or country by addition of
locale-specific components and translation
of text is referred to as localization. The
word “localization” is often abbreviated as
L10N.

5. Slide 5 of 30
 The same executable application can run
worldwide
 Textual elements such as labels and
messages for GUI are not hard-code.
 Support for new language does not require
recompilation
 Culturally dependent data, such as date and
currency appear formats that conform.
 Internationalized programs are localized
quickly

6. Slide 6 of 30
 Numbers: The NumberFormat class is used to create locale-specific
formats for
– Numbers
– Currencies
– Percentages
 Methods

7. Slide 7 of 30
 Date and Time: The date and time format
should conform to the conventions of the
end user’s locale.
 The method below is used to get the
DateFormat:
– getDateInstance(style, locale)

8. Slide 8 of 30
 Unicode provides a unique number for every
character irrespective of platform, program or
language. Unicode is a 16-bit character
encoding system that supports the world’s
major languages. The primitive data type char
in Java is based on Unicode encoding.

9. Slide 9 of 30
1.Creating the Properties File
2.Defining the Locale
– Locale(String language, String country)
– Locale(String language)
1.Using the ResourceBundle class
2.Fetching the Text from Resource Bundle

10. Slide 10 of 30
I18N & Formatting Tag Library
Slide 10 of 9
I18N & Formatting Tag Library
setLocale bundle setBundle message

11. Slide 11 of 30
I18N & Formatting Tag Library
<%@ taglib uri =
"http://java.sun.com/jsp/jstl/fmt" prefix =
“fmt" %>
<fmt:setLocale value=“lc_CC” scope=“page |
request | session | application” />
<fmt:bundle basename=“basename”>
Body Content
</fmt:bundle>
<fmt:setBundle basename=“basename”
var=“varName” scope=“page | request |
session | application” />
<fmt:message key=“messageKey”>
<fmt:param />
Slide 11 of 9

12. Slide 12 of 30
I18N & Formatting Tag Library
– <fmt:formatNumber value=“numValue”
[type=“{number|currency|percent}”]
[maxIntegerDigits=“maxIntegerDigits”]
[minIntegerDigits=“minIntegerDigits”]
[maxFractionDigits=“maxFractionDigits”]
[minFractionDigits=“minFractionDigits”] [var=“varName”]
[scope=“{page|request|session|application}”] />
– <fmt:formatDate value=“date” [type=“{time|date|both}”]
[dateStyle=“{default|short|medium|long|full}”]
[timeStyle=“{default|short|medium|long|full}”]
[var=“varName”] [timeZone=“timeZone”]
[scope=“{page|request|session|application}”]
[pattern=“dd-MM-yy”] />
Slide 12 of 9

13. Slide 13 of 30
Date – Time Pattern
Slide 13 of 9

14. Slide 14 of 30