77 lines
4.9 KiB
HTML
77 lines
4.9 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="Positional entry considerations for printer files that use UTF-16 data" />
|
|||
|
|
<meta name="abstract" content="See DDS for describing printer files by position in this topic. Positions that are not mentioned have no special considerations for UTF-16. In these topics, UTF-16 also implies UCS-2." />
|
|||
|
|
<meta name="description" content="See DDS for describing printer files by position in this topic. Positions that are not mentioned have no special considerations for UTF-16. In these topics, UTF-16 also implies UCS-2." />
|
|||
|
|
<meta name="DC.subject" content="UTF-16, positional entry consideration, positional entries, UTF-16 considerations" />
|
|||
|
|
<meta name="keywords" content="UTF-16, positional entry consideration, positional entries, UTF-16 considerations" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="dspfil.htm" />
|
|||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2001, 2006" />
|
|||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2001, 2006" />
|
|||
|
|
<meta name="DC.Format" content="XHTML" />
|
|||
|
|
<meta name="DC.Identifier" content="ucs2pos" />
|
|||
|
|
<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>Positional entry considerations for printer files that use UTF-16 data</title>
|
|||
|
|
</head>
|
|||
|
|
<body id="ucs2pos"><a name="ucs2pos"><!-- --></a>
|
|||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|||
|
|
<h1 class="topictitle1">Positional entry considerations for printer files that use UTF-16 data</h1>
|
|||
|
|
<div><p>See DDS for describing printer files by position in this topic.
|
|||
|
|
Positions that are not mentioned have no special considerations for UTF-16.
|
|||
|
|
In these topics, UTF-16 also implies UCS-2.</p>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Length (positions 30 through 34)</h4><p>Specify the length
|
|||
|
|
of the field in these positions. The length of a field containing UTF-16 data
|
|||
|
|
can range from 1 through 16 383 code units. When determining the program
|
|||
|
|
length of a field containing UTF-16 data, consider the following conditions:</p>
|
|||
|
|
<ul><li>Each UTF-16 code unit is 2 bytes long.</li>
|
|||
|
|
<li>Specify the program length of the field as the number of UTF-16 code units
|
|||
|
|
(count surrogate pairs as two code units). For example, a field containing
|
|||
|
|
3 UTF-16 code units has 6 bytes of data.</li>
|
|||
|
|
<li>The field's default print length is equal to the field's program length,
|
|||
|
|
or 2 times the number of UTF-16 code units.</li>
|
|||
|
|
<li>After converting between UTF-16 data and EBCDIC, the resulting data might
|
|||
|
|
be equal to, longer than or shorter than the original length data. This depends
|
|||
|
|
on the target CCSID specified on the CHRID parameter of the printer file.
|
|||
|
|
For example, 1 UTF-16 code unit consists of 2 bytes of data. That code unit
|
|||
|
|
might convert to 1 SBCS character composed of 1 byte of data,
|
|||
|
|
1 graphic-DBCS character composed of 2 bytes of data, or 1 bracketed DBCS
|
|||
|
|
character composed of 4 bytes of data.</li>
|
|||
|
|
<li>You can use the alternate-field-length parm on the CCSID keyword to specify
|
|||
|
|
the field's print length separately from the program length.</li>
|
|||
|
|
</ul>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Data type (position 35)</h4><p>The only valid data type
|
|||
|
|
for UTF-16 data is the G data type.</p>
|
|||
|
|
<dl><dt class="dlterm">G (Graphic)</dt>
|
|||
|
|
<dd>Type G in combination with the CCSID keyword to specify that this field
|
|||
|
|
contains UTF-16 data. <p>Normally, the field contains graphic-DBCS data if
|
|||
|
|
you specified G. In combination with the CCSID keyword, however, the field
|
|||
|
|
now contains UTF-16 data.</p>
|
|||
|
|
</dd>
|
|||
|
|
</dl>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><h4 class="sectiontitle">Decimal positions (positions 36 and 37)</h4><p>Leave these
|
|||
|
|
positions blank when using UTF-16 data.</p>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div>
|
|||
|
|
<div class="familylinks">
|
|||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dspfil.htm" title="This topic describes Unicode considerations for positional entries and keyword entries for printer files. It also describes the CCSID keyword for Unicode data in printer files.">Unicode considerations for printer files</a></div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
</body>
|
|||
|
|
</html>
|