This section provides information and procedures for customizing the .NET client. Modify the Strings.xml file to customize the .NET client.
Typically, modifications to the Strings.xml file
are performed by each user on the mobile device. Alternatively,
you can copy the Strings.xml file to a PC and
use a UTF-8-capable text editor to edit the strings. Then, copy
the Strings.xml file back to the PDA, and restart
the .NET client to see the changes on the mobile device.
You may need to develop procedures for deploying updated Strings.xml files to mobile device users. You may want to consider using a remote device management tool, such as Afaria, to place new images and files on PDAs.
To customize language for the .NET client:
Obtain the proper language files and related font files, and download the files to your mobile device.
Obtain or create localized user interface graphics, logos, and icons, using the sizes recommended for your device. Download the files to your mobile device.
Modify the Strings.xml file on your mobile device:
Specify the appropriate language-related resource values, such as language, font, and text orientation.
Translate message strings to the language, such as error and validation messages.
Translate user interface strings to the language, especially user profile fields and prompts.
Update the user interface graphics, logos, and icons file names.
See “Understanding the Strings.xml file” for information before you start.
When you restart the application, the.NET client:
Checks the device’s regional settings for the current language code and country code. For example, a PDA set to “Dutch (Belgium)” would be “nl-BE.”
Checks for the string localization file that matches the language and country code; in this case, Strings.nl-BE.xml for Dutch Belgium.
If the file does not exist, the client looks for an alternative file that contains the language code, but no country code (for example, Strings.nl.xml, a generic Dutch localization file).
If that is not found, the client defaults to the Strings.xml file with default English strings.
Localizing the .NET client
This procedure assumes you have changed the regional setting, downloaded any necessary fonts or character sets, and moved localized graphics files to the mobile device.
Navigate to the Strings.xml file.
Make a copy of the Strings.xml file, and include the language and country code in the new file name. For example:
Strings.nl-BE.xml for Dutch Belgium Strings.fr-CA.xml for French Canadian Strings.fr-FR.xml for French
Modify the new file on your mobile device:
Specify the appropriate language-related resource values, such as language, font, and text orientation. See Table 3 for information about the resource values.
Translate message strings to the language, such as error and validation messages. See “Messages in Strings.xml” for default messages.
Translate user interface strings to the language, especially user profile fields and prompts. See “Strings in Strings.xml” for default strings.
Update the user interface graphics, logos, and icons file names. See “Images in Strings.xml” for information about graphics.
See “Understanding the Strings.xml file” for information about working with the Strings.xml file (or the localized version of the file).
Save the file and close it.
You can also localize the template files, as described in “Understanding the device template files”. The template files include some language strings.
Restart the application. The .NET client should detect the regional language and country codes, locate the localized Strings.xml file, and present the localized interface.
Any reference to the Strings.xml file
extends to your localized version of the file, such as Strings.nl-BE.xml.
The Strings.xml file includes a section of messages that can be localized to a different language, or that can be customized to use terms and phrasing more meaningful for a business setting, or for an individual user. See “Messages in Strings.xml” for message text.
The Strings.xml file includes a section of graphics. You can obtain or create localized graphics, and replace the defaults included with the .NET client. After the .NET client is installed, replace the images on the device with new images, and update the graphic file names in Strings.xml. See “Images in Strings.xml” for graphics file names.
The Strings.xml file includes sections for changing Unwired Accelerator strings and icons that appear on the mobile device user interface.
For user interface strings, such as “Menu,” customize the default text that comes with the .NET client. See “Strings in Strings.xml” for string text.
Additional user interface strings appear in the template
files. You can customize or localize these strings. See “Understanding the device template files” for information.
For icons, such as buttons, you can obtain or create custom graphics, and replace the defaults included with the .NET client. After the .NET client is installed, replace the default icons on the device with new icons, and update the icon file names in Strings.xml. See “Images in Strings.xml” for icon file names.
