142 lines
9.3 KiB
HTML
142 lines
9.3 KiB
HTML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html lang="en-us" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="security" content="public" />
|
|
<meta name="Robots" content="index,follow" />
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|
<meta name="DC.Type" content="reference" />
|
|
<meta name="DC.Title" content="iSeries Access for Windows national language support (NLS) APIs" />
|
|
<meta name="abstract" content="iSeries Access for Windows national language support APIs enable your applications to get and save (query and change) the iSeries Access for Windows settings that are relevant to national language support." />
|
|
<meta name="description" content="iSeries Access for Windows national language support APIs enable your applications to get and save (query and change) the iSeries Access for Windows settings that are relevant to national language support." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikappdt.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiknlscodecharset.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikgennlsapis.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikconvnlsapis.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikdialogboxnlsapilist.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiknlsprogex.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikas400sysnameformat.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikcaexpressprogstd.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="nls" />
|
|
<meta name="DC.Language" content="en-us" />
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|
<!-- US Government Users Restricted Rights -->
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
|
<title>iSeries Access for Windows national language
|
|
support (NLS) APIs</title>
|
|
</head>
|
|
<body id="nls"><a name="nls"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1"><span class="keyword">iSeries Access for Windows</span> national language
|
|
support (NLS) APIs</h1>
|
|
<div><p><span class="keyword">iSeries™ Access for Windows<sup>®</sup></span> <strong>national
|
|
language support</strong> APIs enable your applications to get and save (query
|
|
and change) the <span class="keyword">iSeries Access for Windows</span> settings
|
|
that are relevant to national language support.</p>
|
|
<div class="section"><p>iSeries servers
|
|
support many national languages, through national language support (NLS).
|
|
NLS allows users to work on an iSeries system in the language of their
|
|
choice. The iSeries system
|
|
also ensures that the data that is sent to and received from the system appears
|
|
in the form and order that is expected. By supporting many different languages,
|
|
the system operates as intended, from both a linguistic and a cultural point
|
|
of view.</p>
|
|
</div>
|
|
<div class="section"><p>All iSeries systems
|
|
use a common set of program code, regardless of which language you use on
|
|
the system. For example, the program code on a U.S. English iSeries system
|
|
and the program code on a Spanish iSeries system are identical. Different
|
|
sets of textual data are used, however, for different languages. Textual data
|
|
is a collective term for menus, displays, lists, prompts, options, Online
|
|
help information, and messages. This means that you see <em>Help</em> for the
|
|
description of the function key for Online help information on a U.S. English
|
|
system, while you see <em>Ayuda</em> on a Spanish system. Using the same program
|
|
code with different sets of textual data allows the iSeries system to support more than one
|
|
language on a single system.</p>
|
|
</div>
|
|
<div class="section"><p>You can add convenient functions into your <span class="keyword">iSeries Access for Windows</span> applications,
|
|
including the capability to: </p>
|
|
<ul><li>Select from a list of installed national languages.</li>
|
|
<li>Convert character data from one code page to another. This permits computers
|
|
that use different code pages, such as personal computers and the iSeries server,
|
|
to share information.</li>
|
|
<li>Automatically replace the translatable text (caption and control names)
|
|
within dialog boxes. This expands the size of the controls according to the
|
|
text that is associated with them. The size of the dialog-box frame also is
|
|
adjusted automatically.</li>
|
|
</ul>
|
|
</div>
|
|
<div class="section"> <div class="note"><span class="notetitle">Note:</span> It is essential to build national language support considerations
|
|
into the design of the program right from the start. It is much harder to
|
|
add NLS or DBCS support after a program has been designed or coded.</div>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle"><span class="keyword">iSeries Access for Windows</span> NLS
|
|
APIs required files:</h4>
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="25.252525252525253%" id="d0e110">NLS API type</th>
|
|
<th valign="top" width="29.040404040404038%" id="d0e112">Header file</th>
|
|
<th valign="top" width="22.97979797979798%" id="d0e114">Import library</th>
|
|
<th valign="top" width="22.727272727272727%" id="d0e116">Dynamic Link Library</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" width="25.252525252525253%" headers="d0e110 ">General</td>
|
|
<td valign="top" width="29.040404040404038%" headers="d0e112 ">cwbnl.h</td>
|
|
<td rowspan="3" valign="top" width="22.97979797979798%" headers="d0e114 ">cwbapi.lib</td>
|
|
<td valign="top" width="22.727272727272727%" headers="d0e116 ">cwbnl.dll</td>
|
|
</tr>
|
|
<tr><td valign="top" width="25.252525252525253%" headers="d0e110 ">Conversion</td>
|
|
<td valign="top" width="29.040404040404038%" headers="d0e112 ">cwbnlcnv.h</td>
|
|
<td valign="top" width="22.727272727272727%" headers="d0e116 ">cwbnl1.dll</td>
|
|
</tr>
|
|
<tr><td valign="top" width="25.252525252525253%" headers="d0e110 ">Dialog-box</td>
|
|
<td valign="top" width="29.040404040404038%" headers="d0e112 ">cwbnldlg.h</td>
|
|
<td valign="top" width="22.727272727272727%" headers="d0e116 ">cwbnldlg.dll</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Programmer's Toolkit:</h4><p>The Programmer's Toolkit provides
|
|
NLS documentation, access to the NLS APIs header files, and links to sample
|
|
programs. To access this information, open the Programmer's Toolkit and select <span class="menucascade"><span class="uicontrol">Data Manipulation</span> > <span class="uicontrol">C/C++ APIs</span></span>.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzaiknlscodecharset.htm">Coded character sets</a></strong><br />
|
|
Graphic characters are printable or displayable symbols, such as
|
|
letters, numbers, and punctuation marks. A collection of graphic characters
|
|
is called a <em>graphic-character set,</em> and often simply a <em>character
|
|
set</em>.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaikgennlsapis.htm">iSeries Access for Windows general NLS APIs list</a></strong><br />
|
|
Find information about <span class="keyword">iSeries Access for Windows</span> general
|
|
NLS APIs.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaikconvnlsapis.htm">iSeries Access for Windows conversion NLS APIs list</a></strong><br />
|
|
This topic describes the <span class="keyword">iSeries Access for Windows</span> conversion
|
|
NLS APIs.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaikdialogboxnlsapilist.htm">iSeries Access for Windows dialog-box NLS API list</a></strong><br />
|
|
<span class="keyword">iSeries Access for Windows</span> dialog-box
|
|
NLS APIs are interfaces that are used to manipulate the translatable text
|
|
within dialog boxes.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaiknlsprogex.htm">Example: iSeries Access for Windows NLS APIs</a></strong><br />
|
|
This example illustrates using <span class="keyword">iSeries Access for Windows</span> NLS
|
|
APIs.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaikappdt.htm" title="Use Data Transformation and National Language Support (NLS) APIs to enable your applications to transform data.">iSeries Access for Windows Data Transformation and National Language Support (NLS) APIs</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="rzaikas400sysnameformat.htm" title="APIs that take an iSeries system name as a parameter accept names in the following formats.">iSeries system name formats for connection APIs</a></div>
|
|
<div><a href="rzaikcaexpressprogstd.htm" title="Most of the iSeries Access for Windows C/C++ APIs that accept string parameters exist in three forms: OEM, ANSI, or Unicode.">OEM, ANSI, and Unicode considerations</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |