To allow your application to support different languages:
In the resource file for your application, use unique symbolic IDs, also known as a logical name, for all UI texts that need to appear on the screen.
Note: The S60 platform provides some unique symbolic IDs that you can use in your code, which means that the UI texts used for these IDs match those used elsewhere in the device. Do not define any values for these symbolic IDs.
For information on the recommended structure of the unique symbolic IDs, see Appendix LOC file template.
For each language your application supports, create a resource file as follows:
Create a text
file with the extension lNN
, where NN is a two digit
number that matches the Symbian OS language code for your target language.
For more information, see Appendix Symbian OS and S60 locale IDs.
The file naming suggestion reflects the S60 platform convention, Symbian
OS uses <application_name>_NN.rls
.
Define all the symbolic IDs using the following syntax:
#define symbolicID "value in target language"
Each symbolic ID must be on its own line.
Repeat for each supported language.
For information, see Appendix LOC file template.
Create a file to include the compiled localization files in your resource file, as follows:
Create a text
file with the extension loc
.
The file naming
suggestion reflects the S60 platform naming convention, Symbian OS uses <application_name>.rls
.
Add #ifdef
, #elif
,
and #include
statements for including the appropriate
languages in your application resource files. An example syntax is as follows:
#ifndef __LOCALIZATION_LOC__ #define __LOCALIZATION_LOC__ #ifdef LANGUAGE_SC // language code for default #include "..\data\localization.l01" #elif LANGUAGE_01 // language code for UK #include "..\data\localization.l01" #endif #endif
Include your loc
file
in your resource file.
Add your supported
language codes to the LANG
statement in your project mmp
file.
Build your resource files
Note: Some IDEs do not fully support building resource files for different languages, so you may need to use the command line interface of the Symbian build chain.
Include the appropriate compiled resource files in your deployment package.
For more information on deploying, see Deploying.
The following localization strategies are available:
Create an installation package for each language your application supports and add only the appropriate compiled resource file to the package
Create an installation package that includes support for more than one language, which means there is more than one compiled resource file in the package. The mobile device user selects the desired language upon installation, and only the compiled resource file is installed
Create an installation package that includes support for more than one language, which means there is more than one compiled resource file in the package.