74 lines
5.0 KiB
HTML
74 lines
5.0 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Scenario: A single server supporting English, Japanese, and German" />
|
||
|
|
<meta name="abstract" content="In this scenario, there is a single server supporting English, Japanese, and German users and applications." />
|
||
|
|
<meta name="description" content="In this scenario, there is a single server supporting English, Japanese, and German users and applications." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsinstallscenarios.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbagsmultlngsingsysscen" />
|
||
|
|
<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>Scenario: A single server supporting English, Japanese, and German</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbagsmultlngsingsysscen"><a name="rbagsmultlngsingsysscen"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Scenario: A single server supporting English, Japanese, and German</h1>
|
||
|
|
<div><p>In this scenario, there is a single server supporting English,
|
||
|
|
Japanese, and German users and applications.</p>
|
||
|
|
<p>The primary language of the system is English (NLV
|
||
|
|
2924). The system has also been loaded with secondary languages of Japanese
|
||
|
|
(NLV 2962) and German (2929). Because 2924 is the primary language, the default
|
||
|
|
system settings and i5/OS™ localization preference is set to English. Because
|
||
|
|
these three NLVs are installed, each user can work with the system in English,
|
||
|
|
German, or Japanese.</p>
|
||
|
|
<p>The users see their language of choice and i5/OS localization
|
||
|
|
preference from the initial sign-on screen by the use of a subsystem description
|
||
|
|
for each secondary language.</p>
|
||
|
|
<p>The user has also created a database file in which the fields of interest
|
||
|
|
are defined to contain Unicode. Because Unicode provides a unique number for
|
||
|
|
every character on any platform, in any program,and in any language, one field
|
||
|
|
can contain English, German, and Japanese.</p>
|
||
|
|
<p>The following example shows the SQL statement used to create a database
|
||
|
|
containing a Unicode field named "PART_NAME" and a non-Unicode field named
|
||
|
|
"STOCK_NUMBER":</p>
|
||
|
|
<pre>CREATE TABLE SAMPLE (PART_NAME GRAPHIC (10) CCSID 1200
|
||
|
|
NOT NULL WITH DEFAULT, STOCK_NUMBER INT NOT NULL WITH DEFAULT 0)</pre>
|
||
|
|
<p>If the user wants to display this data with a web service or Unicode enabled
|
||
|
|
application, then Unicode is the natural encoding for web use and no conversion
|
||
|
|
is needed. To get the correct localization and interface preference for the Java™ application,
|
||
|
|
the user needs to set the Java locale to the correct value: <samp class="codeph">en_US</samp> for
|
||
|
|
English, <samp class="codeph">Jp_JA</samp> for Japanese, and <samp class="codeph">de_DE</samp> for
|
||
|
|
German.</p>
|
||
|
|
<p>If the user wants to display this data with a 5250 session, then the Unicode
|
||
|
|
field must be converted to the CCSID of the display device. The user only
|
||
|
|
has to set the user profile's CCSID value to the correct value (37 for English,
|
||
|
|
1399 for Japanese, and 278 for German) to tell the system what the user's
|
||
|
|
preference is for the display. This service is provided automatically by the
|
||
|
|
system if requested with the CCSID keyword and the *CONVERT parameter in DDS.</p>
|
||
|
|
<p>To print the Unicode data, the user specifies the *NOCONVERT parameter
|
||
|
|
of the CCSID keyword, and a TrueType font using the FONTNAME keyword. The
|
||
|
|
unconverted Unicode data can be printed with PSF/400 or with Host Print Transform.</p>
|
||
|
|
<p>The following figure illustrates this scenario.</p>
|
||
|
|
<br /><img src="nls503.gif" alt="Scenario: a single server supporting English, Japanese, and German" /><br /></div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbagsinstallscenarios.htm" title="Use these scenarios to better understand multilingual support.">Scenarios: Set up i5/OS with a national language version</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|