1 <?xml version="1.0" encoding="utf-8"?>

     2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->

     3 <!-- This component and the accompanying materials are made available under the terms of the License 

     4 "Eclipse Public License v1.0" which accompanies this distribution, 

     5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->

     6 <!-- Initial Contributors:

     7     Nokia Corporation - initial contribution.

     8 Contributors: 

     9 -->

    10 <!DOCTYPE concept

    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">

    12 <concept id="GUID-6D7F3D5C-BC1C-5657-993A-4D7E5712CAF5" xml:lang="en"><title>start

    13 stringtable</title><prolog><metadata><keywords/></metadata></prolog><conbody>

    14 <p> <codeph>start stringtable</codeph>  <varname>source-file</varname>  </p>

    15 <p>[<codeph>exportpath</codeph>  <varname>location</varname>] </p>

    16 <p>[<codeph>headeronly</codeph>] </p>

    17 <p> <codeph>end</codeph>  </p>

    18 <p>A <codeph>start stringtable</codeph> section specifies the source file

    19 for the string table. A string table is a collection of string identifiers

    20 with corresponding values. The source file is a simple text file with the

    21 file extension <filepath>.st</filepath>, and is used to generate the <filepath>.cpp</filepath> and <filepath>.h</filepath> files

    22 which contains the string constants required for the program. The header file

    23 location is added to the list of <xref href="GUID-50941508-B999-5FCC-B2B9-F29F5F2CA4C1.dita">userinclude</xref> directories

    24 so that the source files may include the generated header. The <filepath>.cpp</filepath> file

    25 is added to the list of source files, which are built into a component. </p>

    26 <p>For more information on string tables, refer to <xref href="GUID-27340D18-A31D-512E-920A-B06C784A978A.dita">String

    27 Pools</xref>. </p>

    28 <p> <b>Note:</b> The <filepath>.cpp</filepath> file need not be added explicitly

    29 into the list of sources, as this will be done implicitly while building the

    30 component. </p>

    31 <p>The optional <codeph>exportpath</codeph>  <varname>location</varname> specifies

    32 a directory location for the generated header file. </p>

    33 <p>The optional <codeph>headeronly</codeph> keyword causes only the <filepath>.h</filepath> file

    34 to be generated, and no <filepath>.cpp</filepath> files are generated or included

    35 into the project. If the <codeph>exportpath</codeph> is specified, the <filepath>.h</filepath> file

    36 is copied to the specified location. </p>

    37 <example><p>This example will generate <filepath>HttpStringConstants.cpp</filepath> and <filepath>HttpStringConstants.h</filepath> using

    38 the <filepath>HttpStringConstants.st</filepath> file, and export the <filepath>HttpStringConstants.h</filepath> to

    39 the <filepath>\epoc32\include</filepath> directory.</p><codeblock id="GUID-C38AB36E-AEE7-5D70-A7BF-929B07DFB234" xml:space="preserve">START STRINGTABLE HttpStringConstants.st

    40 EXPORTPATH    \epoc32\include

    41 END

    42 </codeblock></example>

    43 </conbody></concept>