108 lines
6.8 KiB
HTML
108 lines
6.8 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="Code globalized applications that use bidirectional data" />
|
||
|
|
<meta name="abstract" content="When you are developing NLV-enabled applications, consider these restrictions in this topic." />
|
||
|
|
<meta name="description" content="When you are developing NLV-enabled applications, consider these restrictions in this topic." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdevelopingappsprog.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsccsidref.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsbidi.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsbidiguidechklist.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsbidi.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="rbagsbidicodedispguide" />
|
||
|
|
<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>Code globalized applications that use bidirectional data</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbagsbidicodedispguide"><a name="rbagsbidicodedispguide"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Code globalized applications that use bidirectional data</h1>
|
||
|
|
<div><p>When you are developing NLV-enabled applications, consider these
|
||
|
|
restrictions in this topic.</p>
|
||
|
|
<ul><li>Bidirectional language display layout <p>The presentation of data should
|
||
|
|
have a right-to-left orientation. Literals should appear on the right side
|
||
|
|
of the fields that they describe. The following examples illustrate a U.S.
|
||
|
|
English display with a left-to-right orientation and the same display in a
|
||
|
|
right-to-left orientation.</p>
|
||
|
|
<p><span class="uicontrol">Left-to-right layout of a U.S.
|
||
|
|
English display</span> <br /><img src="rbags530.gif" alt="An illustration of the left-to-right layout of a U.S. English display" /><br /></p>
|
||
|
|
<p><span class="uicontrol">Right-to-left
|
||
|
|
layout of a U.S. English display</span> <br /><img src="rbags531.gif" alt="An illustration of the previous graphic in reversed (right-to-left) layout of a U.S. English display" /><br /></p>
|
||
|
|
</li>
|
||
|
|
<li>Long fields in bidirectional languages <p>Avoid defining input fields
|
||
|
|
that span more than one line. When the field is displayed or printed as one
|
||
|
|
entity, the result for bidirectional languages is not what the user intended.</p>
|
||
|
|
</li>
|
||
|
|
<li>Variable positioning in bidirectional languages <p>Your application must
|
||
|
|
allow for variables to be in any order. For example, consider the following
|
||
|
|
message in English:</p>
|
||
|
|
<pre>File &1 in library &2 not found</pre>
|
||
|
|
<p>When translated to another language, the message might look
|
||
|
|
like this:</p>
|
||
|
|
<pre>dnuof ton &2 yrarbil ni &1 eliF</pre>
|
||
|
|
<p>In
|
||
|
|
this case, variable 2 is positioned before variable 1.</p>
|
||
|
|
</li>
|
||
|
|
<li>CHECK(RL) and CHECK(RB) keywords with bidirectional languages <p>These
|
||
|
|
options are valid only for display stations capable of right-to-left movement,
|
||
|
|
and have the following restrictions:</p>
|
||
|
|
<ul><li>Option indicators are not valid with cursor control codes.</li>
|
||
|
|
<li>CHECK(RZ) and CHECK(RB) are not valid with these keywords.</li>
|
||
|
|
<li>A field that spans more than one line gives a warning message.</li>
|
||
|
|
<li>The check digit for modulus checking is the farthest-right byte in the
|
||
|
|
field.</li>
|
||
|
|
<li>CHECK(RL) applies to character fields only.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>Online information for bidirectional languages <p>The
|
||
|
|
special bidirectional tags have a restriction. When combining online help
|
||
|
|
information from several panel groups that do not have the same value for
|
||
|
|
the BIDI tag, the user must use the hot key sequence to read the opposite
|
||
|
|
orientation of the online help information.</p>
|
||
|
|
</li>
|
||
|
|
<li>CCSIDs for bidirectional languages <p>As bidirectional languages have
|
||
|
|
special character sets that are unique, no exchange of data into other languages
|
||
|
|
is feasible. You might need to use data mapping between EBCDIC
|
||
|
|
and ASCII data streams, however. For example, you need data mapping between
|
||
|
|
EBCDIC and ASCII data streams if you are using Distributed
|
||
|
|
Relational Database Architecture™ (DRDA<sup>®</sup>).</p>
|
||
|
|
<p>When exchanging data in a
|
||
|
|
language that uses Latin characters and when special characters that are not
|
||
|
|
part of the invariant character set are needed, use CCSID 00424 for Hebrew
|
||
|
|
and CCSID 00420 for Arabic for data mapping to take place. For a list of supported
|
||
|
|
CCSIDs, see CCSIDs.</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<p>See Work with bidirectional data for more information about bidirectional
|
||
|
|
data. This topic also includes a checklist for bidirectional data that provides
|
||
|
|
guidelines to follow when you create applications with bidirectional support.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbagsdevelopingappsprog.htm" title="As you develop your globalized applications, the national language version environment often requires that you pay additional attention to how you prepare and compile your code.">Programming considerations in globalized application design</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbagsccsidref.htm" title="Read this topic for useful information about CCSIDs on i5/OS.">CCSID reference information</a></div>
|
||
|
|
<div><a href="rbagsbidi.htm" title="Arabic and Hebrew languages use an alphabet written and read from right to left. Numerics and Latin text imbedded in the right-to-left text are written and read from left to right; therefore, these languages are called bidirectional languages.">Work with bidirectional data</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rbagsbidiguidechklist.htm" title="When you create an application with bidirectional support, follow the guidelines in this table.">Checklist: Bidirectional support guidelines</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|