week 10 bug fix submission (SF PDK version): Bug 1892, Bug 1897, Bug 1319. Also 3 or 4 documents were found to contain code blocks with SFL, which has been fixed. Partial fix for broken links, links to Forum Nokia, and the 'Symbian platform' terminology issues.
<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
<!-- This component and the accompanying materials are made available under the terms of the License
"Eclipse Public License v1.0" which accompanies this distribution,
and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
<!-- Initial Contributors:
Nokia Corporation - initial contribution.
Contributors:
-->
<!DOCTYPE concept
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
<concept id="GUID-DC77555F-ADAF-5BCA-A5D6-89B8CDC69848" xml:lang="en"><title>Localisation
Overview</title><shortdesc>Overview of localisation support that is available with Symbian
platform. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
<section id="GUID-D6B74179-E4D2-58C7-8052-FC4D3A8B8901"><title>Purpose</title> <p>Localisation
allows the Symbian device to handle locale-sensitive information: for example
language used and how the date and currency are displayed. This collection
makes up what Symbian platform defines as a locale. </p> <p>On Symbian platform,
the locale settings are stored in class <xref href="GUID-53299759-C2DD-3ABC-A055-9AFE7C5081C6.dita"><apiname>TLocale</apiname></xref>. </p> </section>
<section id="GUID-1FB54949-51E2-5CE5-A048-32C55B21F90A"><title>Architecture</title> <p>There
are two sets of locale settings, those that are hard-coded into the phone
and those that are stored in a <filepath>locale.dll</filepath>. The device
creator produces both the hard-coded localisation settings and the locale.dll. </p> </section>
<section id="GUID-659B3E29-4867-5051-87BE-A23189CE8F7D"><title>Description</title> <p>The
localisation API is used to set locale-sensitive information that can be changed
by the user; namely, locale, calendar settings, country code, currency format,
date and time format, numerical values and time zone information. </p> </section>
<section id="GUID-FDB7C3AB-1731-4A8B-878A-257529491AA5"><title>Using Localisation
Support</title> <p>The locale DLL is created by the phone manufacturer and
only the settings application provided by the UI vendor can change the settings
or values. </p> <p>The locale setup process is controlled by the <xref href="GUID-BF4C6A23-EE56-3C92-B980-9D6CB5EB4784.dita"><apiname>EStart</apiname></xref> component
and goes through three phases: </p> <ul>
<li id="GUID-F908A0E6-94B9-5481-B272-21A65EA99D29"><p>Set the hard-coded defaults, </p> </li>
<li id="GUID-7B2080BD-B4B6-5668-8B65-8604C5017A6B"><p>Load the locale from
the HAL settings and load the required locale, and </p> </li>
<li id="GUID-41FF6A2A-90D7-53F0-BBCD-F75089EB0111"><p>Request update notifications </p> </li>
</ul> <p>The device creator produces both the hard-coded values and the <filepath>locale.dll</filepath>. </p> <p>The
locale DLL files are named on the pattern <filepath>eloc1.XYZ</filepath>,
where <codeph>XYZ</codeph> is the language number as defined by <xref href="GUID-698538DF-DCDC-347B-BD32-DD9EB896BAFB.dita"><apiname>TLanguage</apiname></xref> enumeration
defined in <filepath>e32lang.h</filepath>. </p> </section>
</conbody><related-links>
<link href="GUID-C497F36F-BCA8-569D-826A-64EAD75C887C.dita"><linktext>Locale Settings
Overview</linktext></link>
<link href="GUID-80698E62-E310-59CA-A524-5CF44C437BE4.dita"><linktext>Base Starter</linktext>
</link>
</related-links></concept>