Admin tsn : Page créée avec « == Introduction == === Scope === A locale is a set of 2 parameters, one to define the user’s language, the other one to define the country. A locale is used to identify a country, a language or a dialect. The language parameter is composed by 2 lower cases whose list is defined by the [http://www.loc.gov/standards/iso639-2/php/code_list.php ISO 639-2 Langage Code List] [R1]. For instance, “fr” means French whereas “en” means English. The country para... »

2025-04-23T09:32:35Z

Page créée avec « == Introduction == === Scope === A locale is a set of 2 parameters, one to define the user’s language, the other one to define the country. A locale is used to identify a country, a language or a dialect. The language parameter is composed by 2 lower cases whose list is defined by the [http://www.loc.gov/standards/iso639-2/php/code_list.php ISO 639-2 Langage Code List] [R1]. For instance, “fr” means French whereas “en” means English. The country para... »

Nouvelle page

== Introduction ==
=== Scope ===
A locale is a set of 2 parameters, one to define the user’s language, the other one to define the country. A locale is used to identify a country, a language or a dialect.

The language parameter is composed by 2 lower cases whose list is defined by the [http://www.loc.gov/standards/iso639-2/php/code_list.php ISO 639-2 Langage Code List] [R1]. For instance, “fr” means French whereas “en” means English.

The country parameter is composed by 2 upper cases whose list is defined by the [http://www.iso.org/iso/fr/country_codes/iso_3166_code_lists/french_country_names_and_code_elements.htm ISO 3166 French Country Names and Code Elements] [R2]. France is designated by “FR”, Belgium by “BE” and United Kingdom by “GB”.

The association of a language parameter and a country parameter leads to a full definition of all language varieties. As a result, the fr_FR locale points out French language spoken in France whereas the fr_BE locale points out French language spoken in Belgium.

Here is a use case of the Locale object :

<syntaxhighlight lang="java">
// French locale
Locale france = new Locale("fr", "FR");

// French locale language
Locale french = new Locale("fr");

// Belgium locale
Locale belgium = new Locale("fr", "BE");
</syntaxhighlight>

Moreover, some locales are defined as constants of the class. This is the case for French language (Locale.FRENCH), French locale (Locale.FRENCH) or English language (Locale.ENGLISH).

The second Java component i18n is the ResourceBundle. It is in charge of retrieving a given locale. However, the ResourceBundle is an abstract class, therefore a concrete implementation of the ResoureBundle, namely the PropertyResourceBundle, is used. This implementation is based on a basic file name, “properties”, and, for a given locale, it goes for the translation if it is available. To do that, it checks if a properties file, whose name is <basic file name>_<language code>_<country code>, exists.

If necessary it goes for a translation that is more common, that is to say only based on the language and whose properties file would be named <basic file name>_<language code>.

If the need still arises, it goes for the basic file to retrieve a translation.

For example, in the following code :

<syntaxhighlight lang="java">
ResourceBundle bundle = ResourceBundle.getBundle("message");
</syntaxhighlight>

If the current locale (for example the default language of the operating system) is fr_FR, here is the order of the files research :

3.1. message_fr_FR.propertie,<br>
3.2. message_fr.properties,<br>
3.3. message.properties.

It is possible to get back a particular ResourceBundle by specifying explicitly the locale to be used :

<syntaxhighlight lang="java">
ResourceBundle bundle = ResourceBundle.getBundle("message", Locale.ENGLISH);
</syntaxhighlight>

Afterwards, in order to get an internationalized message, for example a message associated to the key “HelloWorld” in the properties file, the method getString(String key) must be used :

<syntaxhighlight lang="java">
String message = bundle.getString("HelloWorld");
</syntaxhighlight>

=== Javadoc ===

=== Links ===

=== Useful Documents ===

=== Package Overview ===

== Features Description ==
=== Exception and internationalization ===
As indicated in the SRS document (requirements PBD-LOG_850), we should create an error message only when it is the only option i.e. Java basic errors suit. In this case, it is mandatory to add a particular error message, the procedure is the following one :

* Find a unique identifier (one key, see the following chapter for the definition rule) for the message and a short and relevant text,
* Modify the PatriusMessages class and add it to the enumeration, in US English which is the default language, e;g. FOO_MESSAGE("foo message for testing purpose") or BAR_MESSAGE("another foo message for testing purpose {0} {1}") with 2 expected arguments,
* Add this message to the translation files PatriusMessages_<language>.properties, one per language, in the directory …/src/main/resources/META-INF/localization, with the following form “key=text”. The text is translated in the required language, one has to be carful with the arguments location if there are some of them (they can be inverted).

N.B. : For languages which use accents like French, each accented character has to be written with a specific coding. The list of the characters and their equivalent coding is available on the following web site : [http://www.utf8-chartable.de/ http://www.utf8-chartable.de/]

If a class is necessary for a specific message type, it has to inherit from the one of the following java classes : Exception or RuntimeException.

Example :

<syntaxhighlight lang="java">
public class MyFutileException extends Exception implements ExceptionContextProvider {
...
private ExceptionContext exceptionContext ; /** compulsory variable */
...
MyFutileException(final Locale locale,final Object ... args) {
exceptionContext.addMessage(locale,PatriusMessages.PDB_FUTILE_EXCEPTION,args)
}
...
}
</syntaxhighlight>

In this case, a unique identifier as well as the original text of the message and its translations are also needed in the translation files.

== Getting Started ==

== Contents ==
=== Interfaces ===

=== Classes ===

User Manual 4.16 Errors management and internationalization - Historique des versions