76 lines
5.1 KiB
HTML
76 lines
5.1 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="Unicode considerations for printer files" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.subject" content="UTF-16, printer files, DDS file considerations, DDS file considerations" />
|
||
|
|
<meta name="keywords" content="UTF-16, printer files, DDS file considerations, DDS file considerations" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="kickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="ucs2pos.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="ucs2kwd.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="dspfil" />
|
||
|
|
<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>Unicode considerations for printer files</title>
|
||
|
|
</head>
|
||
|
|
<body id="dspfil"><a name="dspfil"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Unicode considerations for printer files</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p>Unicode is a universal encoding scheme for written characters and text
|
||
|
|
that enables the exchange of data internationally. A Unicode field can contain
|
||
|
|
all types of characters used on an iSeries™ server, including ideographic
|
||
|
|
(DBCS) characters. The term <em>code unit</em> is used in this topic to mean
|
||
|
|
the minimal bit combination that can represent a unit of encoded text for
|
||
|
|
processing or interchange.</p>
|
||
|
|
<p>DDS printer files support two transformation formats (encoding forms) of
|
||
|
|
Unicode:</p>
|
||
|
|
<ul><li><strong>UTF-16</strong> is a 16-bit encoding form designed to provide code values
|
||
|
|
for over a million characters and a superset of UCS-2. UTF-16 data is stored
|
||
|
|
in graphic data types. The CCSID value for data in UTF-16 format is 1200. <p>A
|
||
|
|
UTF-16 code unit is 2 bytes in length. A UTF-16 character can be 1 or 2 code
|
||
|
|
units (2 or 4 bytes) in length. A UTF-16 data string can contain any character,
|
||
|
|
including UTF-16 surrogates and combining characters.</p>
|
||
|
|
</li>
|
||
|
|
<li><strong>UCS-2</strong> is the Universal Character Set coded in 2 octets, which means
|
||
|
|
that characters are represented in 16 bits per character. UCS-2 data is stored
|
||
|
|
in graphic data types. The CCSID value for data in UCS-2 format is 13488. <p>UCS-2
|
||
|
|
is a subset of UTF-16 and can no longer support all of the characters defined
|
||
|
|
by Unicode. UCS-2 is identical to UTF-16 except that UTF-16 also supports
|
||
|
|
combining characters and surrogates. If you do not need combining characters
|
||
|
|
and surrogates, you might choose to use UCS-2.</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="ucs2pos.htm">Positional entry considerations for printer files that use UTF-16 data</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="ucs2kwd.htm">Keyword considerations for printer files that use UTF-16 data (positions 45 through 80)</a></strong><br />
|
||
|
|
The CCSID keyword for printer files specifies that a G-type field supports UTF-16 data instead of DBCS-graphical data.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="kickoff.htm" title="You can use data description specifications (DDS) to define printer files. This topic provides the information you need to code the positional and keyword entries that define these files.">DDS for printer files</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|