friedkiwi/ibm-information-center
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
14ed2849c6
ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzakd_5.4.0.1/rzakdmstfontname.htm

298 lines
18 KiB
HTML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?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="FONTNAME (Font name) keyword in printer files" />
<meta name="abstract" content="Use this file-level, record-level, or field-level keyword to specify the TrueType font name for printing a named or constant field within a record." />
<meta name="description" content="Use this file-level, record-level, or field-level keyword to specify the TrueType font name for printing a named or constant field within a record." />
<meta name="DC.subject" content="FONTNAME (Font name) keyword, Font name (FONTNAME) keyword" />
<meta name="keywords" content="FONTNAME (Font name) keyword, Font name (FONTNAME) keyword" />
<meta name="DC.Relation" scheme="URI" content="rzakdmstprkey.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="rzakdmstfontname" />
<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>FONTNAME (Font name) keyword in printer files</title>
</head>
<body id="rzakdmstfontname"><a name="rzakdmstfontname"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">FONTNAME (Font name) keyword in printer files</h1>
<div><p>Use this file-level, record-level, or field-level keyword to specify
the TrueType font name for printing a named or constant field within a record.</p>
<div class="section"><p>The format of the keyword is:</p>
<pre> FONTNAME('font-name-string' | &amp;font-name-field
(*POINTSIZE height-value | &amp;height-value-field
width-value | &amp;width-value-field)
[(*ROTATION rotation-value | &amp;rotation-value-field)]
[(*CODEPAGE [library-name/ | &amp;library-name-field/]
code-page-name | &amp;code-page-name-field)]
[(*IGCCODEPAGE [library-name/ | &amp;library-name-field/]
IGC-code-page-name | &amp;IGC-code-page-name-field)])</pre>
<p>When a program-to-system field is described for a FONTNAME
parameter, the program-to-system field is allowed only when the keyword is
used at the record or field level.</p>
<p>The font-name parameter is required.
It can be up to 125 characters long.</p>
<p>You can specify the font-name
as a constant string or as a program-to-system field, as shown in the following
examples:</p>
<ul><li><samp class="codeph">('font-name-string'...</samp></li>
<li><samp class="codeph">(&amp;field1...</samp></li>
</ul>
<div class="p">The following fonts are included in<span class="keyword"><font color="Purple">i5/OS™</font></span> (installed with option 43 – Additional fonts): <ul><li>Monotype Sans WT</li>
<li>Monotype Sans WT J</li>
<li>Monotype Sans WT K</li>
<li>Monotype Sans WT ME</li>
<li>Monotype Sans WT SC (see note)</li>
<li>Monotype Sans WT TC</li>
<li>Monotype Sans Duospace WT</li>
<li><img src="./delta.gif" alt="Start of change" />Monotype Sans Duospace WT IN<img src="./deltaend.gif" alt="End of change" /></li>
<li>Monotype Sans Duospace WT J</li>
<li><img src="./delta.gif" alt="Start of change" />Monotype Sans Duospace WT J EA<img src="./deltaend.gif" alt="End of change" /></li>
<li>Monotype Sans Duospace WT K</li>
<li><img src="./delta.gif" alt="Start of change" />Monotype Sans Duospace WT K EA<img src="./deltaend.gif" alt="End of change" /></li>
<li>Monotype Sans Duospace WT ME</li>
<li>Monotype Sans Duospace WT SC (see note)</li>
<li><img src="./delta.gif" alt="Start of change" />Monotype Sans Duospace WT SC EA<img src="./deltaend.gif" alt="End of change" /></li>
<li>Monotype Sans Duospace WT TC</li>
<li><img src="./delta.gif" alt="Start of change" />Monotype Sans Duospace WT TC EA<img src="./deltaend.gif" alt="End of change" /></li>
<li><img src="./delta.gif" alt="Start of change" />Monotype Sans Duospace WT TC TW EA<img src="./deltaend.gif" alt="End of change" /></li>
<li>Monotype Sans Duospace Ext B (see note)</li>
<li>Times New Roman WT</li>
<li><img src="./delta.gif" alt="Start of change" />Times New Roman WT IN<img src="./deltaend.gif" alt="End of change" /></li>
<li>Times New Roman WT J</li>
<li>Times New Roman WT K</li>
<li>Times New Roman WT ME</li>
<li>Times New Roman WT SC</li>
<li>Times New Roman WT TC</li>
<li>Thorndale Duospace WT</li>
<li>Thorndale Duospace WT J</li>
<li>Thorndale Duospace WT K</li>
<li>Thorndale Duospace WT ME</li>
<li>Thorndale Duospace WT SC</li>
<li>Thorndale Duospace WT TC</li>
</ul>
</div>
<div class="note"><span class="notetitle">Note:</span> <img src="./delta.gif" alt="Start of change" />A resource access table included with <span class="keyword"><font color="Purple">i5/OS</font></span> option
43 links the Monotype Sans Duospace Ext B font to the Monotype Sans WT SC,
Monotype Sans Duospace WT SC and Monotype Sans Duospace WT SC EA fonts. This
makes the characters of this extension font available to documents that specify
either of these three base fonts.<img src="./deltaend.gif" alt="End of change" /></div>
<p>When you specify the font-name
as a program-to-system field, the field must exist in the same record format
as the FONTNAME keyword. It must be defined as data type A (character), usage
P (program-to-system), and its length must not exceed 125 characters.</p>
<p>Use
the point-size parameter to further define a TrueType font, which requires
a point size. Specify the point-size parameter as an expression of the form
(*POINTSIZE height-value width-value). The height-value specifies the point
size for the height of the font. The width-value specifies the point size
for the width of the font. If the font is to be uniformly scaled (height and
width the same), then you only need to specify the height value. If you want
to specify a width value, then you must also specify the height value. The
valid values for the height and width parameters are 0.1 through 999.9.</p>
<p>If
you omit the point-size parameter, unpredictable results will occur when the
file is printed.</p>
<p>You can specify the height-value and width-value as
constants, as program-to-system fields, or as a combination of both, as shown
in the following examples:</p>
<ul><li><samp class="codeph">(*POINTSIZE height-value width-value)...</samp></li>
<li><samp class="codeph">(*POINTSIZE &amp;field1 &amp;field2)...</samp></li>
<li><samp class="codeph">(*POINTSIZE &amp;field1 width-value)...</samp></li>
<li><samp class="codeph">(*POINTSIZE height-value &amp;field2)...</samp></li>
</ul>
<p>When you specify the height-value or width-value as a program-to-system
field, the fields must exist in the same record format as the FONTNAME keyword.
They must be defined as length 4 with 1 decimal position, data type S (zoned
decimal), and usage P (program-to-system).</p>
<p>Use the optional rotation
parameter to specify the clockwise rotation, in degrees, for the printed characters.
Specify the rotation parameter as an expression of the form</p>
<pre>[(*ROTATION rotation-value | &amp;rotation-value-field)]</pre>
<p>Valid values are integers 0, 90, 180, and 270. To achieve vertical printing
of a field, specify a rotation value of 270 and also specify the field-level
TXTRTT keyword.</p>
<p>You can specify the rotation value as a constant or
as a program-to-system field, as shown in the following examples:</p>
<ul><li><samp class="codeph">[(*ROTATION rotation)]...</samp></li>
<li><samp class="codeph">[(*ROTATION &amp;field1)]...</samp></li>
</ul>
<p>When you specify the rotation value as a program-to-system field,
the field must exist in the same record format as the FONTNAME keyword. It
must be defined as length 3, data type S (zoned decimal), and usage P (program-to-system).</p>
<p>Use
the optional code-page-name parameter to print single-byte EBCDIC data with
a TrueType font. If you do not specify either the optional code-page-name
parameter or the optional igccode-page-name parameter, the print data must
be Unicode-encoded. The code-page-name parameter can be up to 8 characters
in length. The single-byte code page must be a font resource (*FNTRSC) object
with the code page (CDEPAG) attribute that reflects the encoding of the print
data.</p>
<p>Use the optional library-name parameter to further qualify the
code page. If library-name is not specified, *LIBL is used to search for the
code page. If *LIBL is used, the system-supplied font libraries are added
to the library list when searching for the requested code page.</p>
<div class="note"><span class="notetitle">Note:</span> If
an application uses private resources (for example, fonts, page segments,
overlays, or GDF files not distributed with the system), be aware of the following
information. When referencing these resources, if you specify *LIBL or you
do not specify a library name, the resources must be available through the
library list used by the application creating the spooled file.</div>
<p>The
code page is validated at print time. An error message is issued if it is
not valid.</p>
<p>You can specify the library name and code page name as constants
or as program-to-system fields, as shown in the following examples:</p>
<ul><li><samp class="codeph">[(*CODEPAGE [library-name/] code-page-name)]...</samp></li>
<li><samp class="codeph">[(*CODEPAGE [library-name/] &amp;field1)]...</samp></li>
<li><samp class="codeph">[(*CODEPAGE [&amp;field2/] code-page-name)]...</samp></li>
<li><samp class="codeph">[(*CODEPAGE [&amp;field2/] &amp;field1)]...</samp></li>
</ul>
<p>When you specify the library name as a program-to-system field, the
field must exist in the same record format as the FONTNAME keyword. It must
be defined as length of 10, data type A (character), and usage P (program-to-system).</p>
<p>When
you specify the code page name as a program-to-system field, the field must
exist in the same record format as the FONTNAME keyword. It must be defined
as length of 8, data type A (character), and usage P (program-to-system).</p>
<p>Use
the optional igccode-page-name parameter to print double-byte EBCDIC data
with a TrueType font. If you do not specify either the optional code-page-name
parameter or the optional igccode-page-name parameter, the print data must
be UCS-2 or UTF-16 encoded. The igccode-page-name parameter can be up to 8
characters in length. The double-byte code page must be a font resource (*FNTRSC)
object with the code page (CDEPAG) attribute that reflects the encoding of
the print data.</p>
<p>Use the optional library-name parameter to further qualify
the double-byte code page. If library-name is not specified, *LIBL is used
to search for the double-byte code page. If *LIBL is used, the system-supplied
font libraries are added to the library list when searching for the requested
double-byte code page.</p>
<div class="note"><span class="notetitle">Note:</span> If an application uses private
resources (for example, fonts, page segments, overlays, or GDF files not distributed
with the system), be aware of the following information. When referencing
these resources, if you specify *LIBL or you do not specify a library name,
the resources must be available through the library list used by the application
creating the spooled file.</div>
<p>The double-byte code page is validated
at print time. An error message is issued if it is not valid. You can specify
the library name and double-byte code page name as constants or as program-to-system
fields, as shown in the following examples:</p>
<ul><li><samp class="codeph">[(*IGCCODEPAGE [library-name/] igccode-page-name)]...</samp></li>
<li><samp class="codeph">[(*IGCCODEPAGE [library-name/] &amp;field1)]...</samp></li>
<li><samp class="codeph">[(*IGCCODEPAGE [&amp;field2/] igccode-page-name)]...</samp></li>
<li><samp class="codeph">[(*IGCCODEPAGE [&amp;field2/] &amp;field1)]...</samp></li>
</ul>
<p>When you specify the library name as a program-to-system field, the
field must exist in the same record format as the FONTNAME keyword. It must
be defined as length of 10, data type A (character), and usage P (program-to-system).</p>
<p>When
you specify the double-byte code page name as a program-to-system field, the
field must exist in the same record format as the FONTNAME keyword. It must
be defined as length of 8, data type A (character), and usage P (program-to-
system).</p>
<div class="note"><span class="notetitle">Note:</span> When a printer file is created and a character set and code
page are specified for the font character set (FNTCHRSET) parameter, column
spacing is done using this printer file level parameter. Any fonts or code
pages specified in the FONTNAME keyword are ignored and the font and code
page specified in the printer file parameter FNTCHRSET is used.</div>
<p>Specify
DEVTYPE(*AFPDS) on the CRTPRTF command when FONTNAME is specified in the file.
If DEVTYPE is changed to anything other than *AFPDS, the keyword is ignored
and a warning message is issued at print time.</p>
<p>FONTNAME with *CODEPAGE
cannot be specified at the same level as the FONT, FNTCHRSET, or CDEFNT keyword,
and it cannot be specified with the CCSID keyword.</p>
<p>FONTNAME with *IGCCODEPAGE
cannot be specified at the same level as the IGCCDEFNT keyword and it cannot
be specified with the CCSID keyword.</p>
<p>FONTNAME without *CODEPAGE or *IGCCODEPAGE
cannot be specified at the same level as the FONT, FNTCHRSET, CDEFNT or IGCCDEFNT
keyword.</p>
<p>FONTNAME without *CODEPAGE or *IGCCODEPAGE can only be specified
with the CCSID keyword (with the *NOCONVERT parameter). Use this combination
to print Unicode data, using a field with data type G. If FONTNAME without
*CODEPAGE or *IGCCODEPAGE is specified at the file level or record level,
it will be used to print the Unicode data, even if a FNTCHRSET keyword is
used to specify an AFP™ Unicode migration font.</p>
<p>Option indicators are
valid for this keyword.</p>
</div>
<div class="section"><h4 class="sectiontitle">Example</h4><p>The following example shows how to specify
the FONTNAME keyword.</p>
<div class="note"><span class="notetitle">Note:</span> By using the code examples, you agree to the
terms of the <a href="codedisclaimer.htm">Code license and disclaimer information</a>.</div>
<pre>|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
A*
A R REC1 FONTNAME('Monotype Sans Duospace WT' +
A (*POINTSIZE 15.1) +
A (*CODEPAGE USERLIB/CDP1))
A*
A FLD1A 14G 3 8FONTNAME('Monotype Sans WT' +
A (*POINTSIZE 10.0)) +
A CCSID(13488 *NOCONVERT)
A*
A FLD2A 6A 4 8FONTNAME('Monotype Sans Duospace WT' +
A (*POINTSIZE 99.9) +
A (*CODEPAGE USERLIB/&amp;DATA1))
A DATA1 8A P
A*
A FLD3A 10G 5 8FONTNAME('Times New Roman WT J' +
A (*POINTSIZE 5.0 3.0) +
A (*ROTATION 270) +
A (*IGCCODEPAGE +
A USERLIB/IGCCDP1))
A*
A FLD4A 10O 7 8FONTNAME('Times New Roman WT J' +
A (*POINTSIZE 7.0 5.0) +
A (*ROTATION 270) +
A (*CODEPAGE USERLIB/CDP2) +
A (*IGCCODEPAGE +
A USERLIB/IGCCDP2)) +
A TXTRTT(90)
A*
A FLD5A 8A 8 8</pre>
<p>FLD1A is printed
using a TrueType font called Monotype Sans WT, with Unicode data, a CCSID
of 13488, and a point size of 10.0.</p>
<p>FLD2A is printed using a TrueType
font called Monotype Sans Duospace WT. It allows the application program to
specify the code page name by setting the field &amp;DATA1. The code page
exists in library USERLIB. The point size is 99.9.</p>
<p>FLD3A
is printed using a TrueType font called Times New Roman WT J, a double-byte
code page IGCCDP1, which exists in library USERLIB, a vertical point size
of 5.0 and a horizontal point size of 3.0. The individual characters is rotated
270 degrees in a clockwise direction.</p>
<p>FLD4A is printed
using a TrueType font called Times New Roman WT J, code page CDP2, which exists
in library USERLIB, double-byte code page IGCCDP2, which exists in library
USERLIB, a vertical point size of 7.0 and a horizontal point size of 5.0.
The individual characters is rotated 90 degrees in a clockwise direction.
The text is also rotated 270 degrees, resulting in vertical printing.</p>
<p>FLD5A
is printed using a TrueType font called Monotype Sans Duospace WT, code page
CDP1, which exists in library USERLIB, and a point size of 15.1.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakdmstprkey.htm" title="See the valid keyword entries for defining printer files in this topic.">Keyword entries for printer files (positions 45 through 80)</a></div>
</div>
</div>
</body>
</html>
Reference in New Issue View Git Blame Copy Permalink