
UNISYS

RELEASE NOTICE FOR
1.0Scaling Font Service

Revised May 1, 1990
SECTION   TITLE	PAGE
1.0	Description of Program	2
2.0	Changes from Prior Version	4
3.0	Contents of Distribution Diskettes	6
4.0	Installation Procedures	9
4.1	Standalone Hard Disk Systems	9
4.2	Cluster Systems with Local File Storage	14
4.3	Server Hard Disk Systems	14
4.4	Shared Resource Processor Systems	15
4.5	Standalone Floppy Disk Systems	15
5.0	Required Files	16
5.1	For Local Scaling Font Service	16
5.2	For Font Database Customization 	17
6.0	System Software Compatibility	18
6.1	Workstation Environment	18
6.2	Shared Resource Processor	18
7.0	Hardware Information	18
7.1	Hardware Configurations Supported	18
7.2	Special Hardware Requirements	18
8.0	Resource RequirementsUtilization	19
8.1	Response Times	19
8.2	Memory RequirementsUtilization	20
8.3	Disk RequirementsUtilization	20
9.0	Certification Information	20
10.0	Supplementary Information	21
10.1	Installation Parameters	21
10.2	Line Drawing Characters	21
11.0	Documentation Updates	23
12.0	Status Codes	23
13.0	Known Errors and Omissions	24
1.0	Description of Program
This Release Notice describes version 1.0 of the Scaling Font Service.  This section and the sections that follow provide a description of the product, contents of the Distribution Diskettes, installation procedures, and other information pertinent to this release of the Scaling Font Service.
The Scaling Font Service is used to support  applications, such as Document Designer 2.0 or later, or OFIS Designer 2.0 or later, which display WYSIWYG typographic fonts.  Typographic fonts include proportional fonts in a wide variety of sizes and styles.  
The Scaling Font Service is interchangeable with the Font Service distributed with GPS 2.0 and later.  It serves the same requests, so only one of the two can be installed on the same system.  The Scaling Font Service has all the capabilities of the standard Font Service, and provides additional capabilities not provided by the standard Font Service.  
The Scaling Font Service is used in place of the standard Font Service and the Screen Font Database.  It is packaged together with outlines for the 35 fonts that are resident in Laser Writer II printers, and a font database which supports these fonts for display in WYSIWYG Document Designer.  This font database is a superset of the font database distributed with GPS 2.4.
The Scaling Font Service provides bitmapped fonts to applications such as Document Designer, OFIS Designer, GPS device drivers, and applications linked with the CCGI+ library.  These bitmap fonts are provided at any size, resolution and orientation supported by such applications.   These bitmaps are created onthefly from the outlines accessible to the Scaling Font Service.
The Scaling Font Service provides a much wider selection of fonts and sizes, up to 38 point, for WYSIWYG display by existing users of Document Designer 2.0, 2.1, 2.2 and OFIS Designer 2.0.
The Scaling Font Service provides a much wider selection of fonts and sizes, up to 76 point, for WYSIWYG display by users of Document Designer 2.3 and OFIS Designer 2.1.
The Scaling Font Service provides a much wider selection of fonts and sizes, up to 64 pixels in height, for applications created using the CCGI+ library.
The Scaling Font Service provides bitmapped fonts which can be downloaded to HP LaserJetcompatible printers.
The Scaling Font Service includes the following components:
A.	Font Service:  provides the same data to GPS device drivers and applications as is provided by 2.3 GPS font service and font database.  The service itself is implemented by the program [sys]<sys>ScalingFontService.run.
B.	Runtime Font Database:  called [sys]<gps>ScalingFont.dbs.
C.	Font Database Port Files:  which can be loaded into an editable font database.  These port files include only information about the scaling fonts (outlines) themselves.  They do not include the font data distributed with GPS.  Instead these port files are imported into a font database along with data from GPS.  This is comparable to the Screen Font Database distribution.
D.	Fonts:  matching each of the fonts that are resident in Laser Writer II printers, including:
Courier	Courier Bold	
Courier Italic	Courier Bold Italic
Helvetica	Helvetica Bold	
Helvetica Italic	Helvetica Bold Italic
Times Roman	Times Bold	
Times Italic	Times Bold Italic
Palatino	Palatino Bold	
Palatino Italic	Palatino Bold Italic
ITC Avant Garde Gothic	ITC Avant Garde Gothic Bold	
ITC Avant Garde Gothic Italic	ITC Avant Garde Gothic Bold Italic
New Century Schoolbook	New Century Schoolbook Bold	
New Century Schoolbook Italic	New Century Schoolbook Bold Italic
Helvetica Narrow	Helvetica Narrow Bold	
Helvetica Narrow Italic	Helvetica Narrow Bold Italic
ITC Bookman	ITC Bookman Bold	
ITC Bookman Italic	ITC Bookman Bold Italic
ITC Zapf Chancery Italic	ITC Zapf Dingbats
Greek
E.	37 Master (International) Font Outline Files:  35 font outline files which correspond to the fonts listed above, including all the characters in the corresponding PostScript character sets, and 2 font outline files (Dutch Roman and Swiss) containing the standard Bitstream character set, including many foreign and special symbols not in the PostScript character sets.
F.	37 Nationalized Font Outline Files:  33 font outline files which correspond to the fonts listed above, except Greek and ITC Zapf Dingbats, and which include only those characters required for the CTOS (or BTOS) character set; and 4 miscellaneous font outline files which contain supplementary characters drawn from the Swiss, Dutch Roman, Symbol and Helvetica fonts, required for the CTOS character set.  The nationalized font outline files are smaller than the complete outline files, allowing more font outlines to be held in memory simultaneously.
G.	Font Outline Nationalization Tool:  which automatically builds nationalized outline files for a customerdefined character set.
H.	Export Raster Font Utility:  retrieves scaled fonts from the scaling font service and generates .port files so that these scaled fonts can be imported into the font database.  The user can thereby scale commonly used fonts in advance so that retrieval of these fonts is rapid.  The cost is that the runtime font database will require more disk space.
2.0	Changes from Prior Version
This is the first release of the Scaling Font Service.  However, because the Scaling Font Service is used in place of the Screen Font Database, it is relevant to discuss differences with the Screen Font Database.
All of the characters which are obtained from scaling fonts are generated from outlines delivered by Bitstream.  The Font Service can shift the resulting bitmaps vertically.  But we (Unisys) do not have the ability to create new outlines.  This stands in contrast to the Screen Font Database, in which we were able to craft bitmap characters to serve special needs.  In particular, we created several glyphs in the Screen Font Database which served to represent unprintable formatting characters on the screen, at higher levels of visibility (codeV).  These glyphs in turn were similar to glyphs in the system font used to represent these characters on charactermapped monitors, enhanced to emphasize their semantics.  Since these were special purpose symbols, it is not surprising to find that there is no exact equivalent in the Bitstream outlines.  This section describes the differences between visible symbols delivered by the Scaling Font Service and those in the Screen Font Database.
Visible Backspace (08 hex):  a double arrow pointing left.  [In Screen Font Database and in system font this symbol is an arrow pointing left into a vertical bar].
Visible Tab (09 hex):  a double arrow pointing right.  [In Screen Font Database and in system font this symbol is an arrow pointing right into a vertical bar].
Visible Line Feed (0A hex):  an arrow pointing down and then left.  [In Screen Font Database and in system font this symbol is an arrow pointing down and then downwardleft].
Visible Form Feed (0C hex):  a double arrow pointing down.  [In Screen Font Database and in system font this symbol is an arrow point down and then downwardright].
Visible Paragraph Mark (89 hex):  looks just like the printable pilcrow (paragraph) symbol (1A hex).  [In Screen Font Database, this symbol has a rectangle around it].
Visible Heading Paragraph (8A hex):  looks just like the printable section symbol (17 hex).  [In Screen Font Database, this symbol has a rectangle around it].
Visible Table of Contents Paragraph (8B hex):  an unfilled square.  [In Screen Font Database it is an unfilled square with a rectangle around it].
Visible Outline Paragraph (8C hex):  a filled square.  [In Screen Font Database it is a filled square with a rectangle around it].
Visible Null (8D hex):  an empty set symbol.  [In Screen Font Database it is a slashed capital O with a rectangle around it].
Visible Nonbreaking Space (8F hex):  two short horizontal lines, one at the baseline, and one below.  [In Screen Font Database it is a short horizontal line with short strokes raised at each end, with a dot above].
Visible Discretionary Space (90 hex):  a short underline.  [In Screen Font Database it is a short underline with a dot above].
Visible Discretionary Hyphen (92 hex):  a short wavy line (like a tilde).  [In the Screen Font Database it is a wavy stroke over a hyphen].
3.0	Contents of Distribution Diskettes
The Scaling Font Service Distribution Diskettes are your master copies, and have been shipped writeprotected.  They should not be writeenabled, nor should they be used as working copies.
The distribution diskettes contain the following files.
Distribution diskette (1 of 5):
Directory <sys>
HDInstall.sub	Install.sub
Directory <CT>
CT903000.spd	
CT903008_10M.font	CT903008_12M.font
CT903009_10M.font	CT903009_12M.font
CT903010_10M.font	CT903010_12M.font
CT903011_10M.font	CT903011_12M.font
CT913012_10M.font	CT913012_12M.font
CT990011_10M.font	CT990011_12M.font
FontCapture.run	FontNatMsg.bin
FontNatMsg.txt	OutlineInstall.sub
ScalingFontCharacterSet.port
ScalingFontDemo
ScalingFontDevice.port
ScalingFontFamily.port
ScalingFontKey.port
ScalingFontPseudoFamily.port
ScalingFontRaster.port
ScalingFontReduction.port
ScalingFontService.run
ScalingFontTranslate.port
ScalingFontWidth.port
ServiceInstall.sub
Directory <ReleaseNote>
ReleaseNote
{Distribution diskette (2 of 5):
Directory <CT>
CT903001.spd	CT903002.spd	
CT903003.spd	CT903004.spd	
CT903005.spd	CT903006.spd	
CT903007.spd	CT903008.spd	
CT903009.spd	CT903010.spd	
CT903011.spd	CT903013.spd	
CT903014.spd	CT903015.spd	
CT903016.spd	CT903017.spd	
CT903018.spd	CT903019.spd	
CT903020.spd	CT903021.spd	
FONT3012.spd	FONT3030.spd}
{Distribution diskette (3 of 5):
Directory <CT>
CT903022.spd	CT903023.spd	
CT903024.spd	CT903025.spd	
CT903026.spd	CT903027.spd	
CT903028.spd	CT903029.spd	
CT903031.spd	CT903032.spd	
CT903033.spd	CT903034.spd	
CT913012.spd	CT923004.spd	
CT990003.spd	CT990011.spd	
FONT0003.spd	FONT0011.spd	
FontNationalize.run	NatInstall.sub}
{Distribution diskette (4 of 5):
Directory <CT>
FONT3000.spd	FONT3001.spd	
FONT3002.spd	FONT3003.spd	
FONT3004.spd	FONT3005.spd	
FONT3006.spd	FONT3007.spd	
FONT3008.spd	FONT3009.spd	
FONT3010.spd	FONT3011.spd	
FONT3013.spd	FONT3014.spd
FONT3015.spd	FONT3016.spd}
{Distribution diskette (5 of 5):
Directory <CT>
FONT3017.spd	FONT3018.spd
FONT3019.spd	FONT3020.spd
FONT3021.spd	FONT3022.spd
FONT3023.spd	FONT3024.spd
FONT3025.spd	FONT3026.spd
FONT3027.spd	FONT3028.spd
FONT3029.spd	FONT3031.spd
FONT3032.spd	FONT3033.spd
FONT3034.spd}
4.0	Installation Procedures
The Scaling Font Service should be used only on CTOS or BTOS systems which are equipped with hard disk, or in clusters where the server is equipped with hard disk.
The Scaling Font Service requires the Standard Software at revision level 10.3 or higher and GPS 2.4 or later to function correctly.  If you have not yet installed Standard Software or GPS at such a revision level, do so before installing the Scaling Font Service.
You must install the editable font database and Font Tool from the GPS installation diskettes before installing the Scaling Font Service.  If you have removed the editable font database directory from your system (named [sys]<FontDB>, by default), you must reinstall it from the GPS installation before installing Scaling Font Service.
If your editable database contains data from the Screen Font Database product (not in a separate variant), you must remove this information before installing Scaling Font Service.  Invoke the Font Tool, and enter the list of Font Keys.  Press CodeF10 to jump to the end of the list.  Delete every record with a font device type of Video120.
Scaling Font Service 1.0 can be installed on B26, B28, B38, B39, XE520, XE530, CWS, NGEN series 186, 286, 286i, 386, 386i, and SRP workstations.
Use the installation procedures described below (after updating the Standard Software revision level, if required).  Characters that you must type are shown in boldface.  Special keys, such as RETURN and GO, are shown in upper case.
4.1	Standalone Hard Disk Systems
A.	Insert the Scaling Font Service Distribution Diskette 1 of 5 into a floppy drive.  If this drive is not [f0], substitute the actual drive name for [f0] in the command forms below.
On a BTOS system, install the product as follows:
Command   Software Install		<RETURN>
  [Cmd File]
  [Files to]
  [Install file]		<GO>
Follow the directions displayed on the screen.  These directions are selfguiding.  We have summarized these directions below.
On a CTOS system,  install the product as follows:

if 10.3 Standard Software, or later, has been installed:
Command   Install		<RETURN>
Install
  [Floppy ([f0])]		<GO>

or if you do not have the Install command:

Command   Submit		<RETURN>
Submit
  File List	[f0]<Sys>HdInstall.sub
  [Parameters]		<GO>
Follow the directions displayed on the screen.  These directions are selfguiding.  We have summarized these directions below.
The installation will first pause to display the following command form for Submit:
Submit
  File List	[f0]<ct>ServiceInstall.sub
  [Parameters]	[f0] [Sys]
  [Force Expansion?]
  [Show Expansion?]
To install the Scaling Font Service on a volume other than [Sys], such as [Sys], change [Sys] to the desired volume name, e.g., [Sys].  To add the commands to a command file other than the one you are using, specify it as the third parameter.  For example:
Submit
  File List	[f0]<ct>ServiceInstall.sub
  [Parameters]	[f0] [Sys] [sys]<sys>sys.cmds
  [Force Expansion?]
  [Show Expansion?]
Press GO.
The installation will pause with a warning that GPS 2.4 (or later) must already be installed, including the Font Tool and editable database.  Press GO if GPS 2.4, the Font Tool, and the editable database are installed.  Press ACTIONFINISH to terminate the installation if not.
The installation will next pause with the following command form for Path displayed on the screen:
Path
  [Volume]	sys
  [Directory]	FontDB
  [Default file prefix]
  [Password]
  [Node]
Enter the volume and directory which holds your editable font database.  By default, GPS 2.4 installs the editable font database in [sys]<FontDB>.  
Press GO to path to the directory containing the editable font database.  The Scaling Font Service .port files will be installed in this directory.
The installation will pause to allow you to check for sufficient disk space.  Press GO to invoke the Volume Status command, or press CANCEL then GO to eliminate this step.  You must press GO one more time to continue the installation.
The installation will next pause with the Deinstall Font Service command displayed on the screen.  If a font service is currently installed on your workstation, press GO to deinstall it.  If the font service is not currently installed on your workstation, press CANCEL, then GO.
The Scaling Font Service commands and programs will be installed on your system.
The installation will next pause with the following command form for Submit displayed on the screen ([f0] and [sys] might be different if you specified other choices in prior steps):
Submit
  File List	[f0]<ct>OutlineInstall.sub
  [Parameters]	[f0] [Sys] '' [sys]<sfs>
  [Force Expansion?]
  [Show Expansion?]
This allows you to specify a different volume or directory to hold the scalable font outline files, other than the default, which is [sys]<sfs>.  There are about 40 outline files, requiring 1750 sectors of disk.  For example, you might change [sys]<sfs> in this form to [d1]<sfs>.  You may name a directory that does not currently exist.
Press GO.
The installation procedure will create the directory (if necessary) and start copying font outline files to it.  It will pause for you to insert diskette 2 of 5, and then diskette 3 of 5, which contain the remainder of the outlines.  Press GO, and the remainder of the outlines will be installed.
The installation will next pause to ask whether you wish to install nationalization tools.  It allows you to decide whether to install master (international) outline files on your system and where to store them.  If you will not nationalize the font database or otherwise customize the character set, press CANCEL, then GO.  You will not use diskettes 4 and 5 of the installation, and can skip to step C.
B.	If you choose to install the nationalization tools, the following command form for Submit is displayed ([f0], [sys] and <sfs> might be different if you specified other choices in prior steps):
Submit
  File List	[f0]<ct>NatInstall.sub
  [Parameters]	[f0] [Sys] '' [sys]<sfs>
  [Force Expansion?]
  [Show Expansion?]
Change the final parameter ([sys]<sfs>) to indicate the directory into which you will store the master (international) outline files.  These require about 2400 sectors.  You may wish to use the same directory as you used (during the first two diskettes) for the nationalized outline files, since nationalized outline files will be recreated in this directory when you use the Nationalize Scaling Fonts utility.
Press GO.  
The installation procedure will create the directory (if necessary) and start copying master font outline files to it.  It will pause for you to insert diskette 4 of 5, and then diskette 5 of 5, which contain the remainder of the outlines.  Press GO, and the remainder of the master outlines will be installed.
C.	The remaining steps are required to obtain a runtime database for use by the Scaling Font Service.  These steps can take some time to complete.  At this point, you are finished with the installation diskettes.
The installation will next pause with the following command form for Font Tool displayed on the screen:
Font Tool
  [Batch mode commands]	import:Scaling generate
  [Variant database]	
The command form shown will import the data required by the Scaling Font Service into your editable database, and generate a new runtime database.  If you are ready to do this, press GO.  If you are ready to import the font data, but not ready to generate a new database, delete the word generate from the command form and press GO.
The installation will next pause with the following command form for Copy displayed on the screen:
Copy
  File from	Font.dbs
  File to	[sys]<Gps>ScalingFont.dbs
  [Overwrite ok?]	y
  [Confirm each?]
If you did not generate a new database, press CANCEL, GO.  If you wish to store the new runtime font database on a volume and directory other than [sys]<gps>, edit the File to parameter.  Press GO to copy the font database.
The installation will next pause with the following command form for Install Scaling Font Service displayed on the screen:
{Install Scaling Font Service
  [Font database ([sys]<gps>ScalingFont.dbs)]		
  [Bytes of buffer space (8192)]
  [ of outline cache blocks @64K RAM (1)]
  [ of scaled metrics to cache @1.5K disk (200)]
  [Cache file ([sys]<gps>ScalingFont.metrics)]
  [Outline directory ([sys]<sfs>)]		[sys]<sfs>}
If you changed the File to parameter in the Copy command form above, enter that same name as the first parameter of the Install Scaling Font Service command form.  The last parameter indicates the directory into which you installed the outlines.  
Press GO to install the Scaling Font Service into memory.  Press CANCEL, and then GO if Context Manager is currently running, since you cannot install system services when Context Manager is running, or if you did not generate a new font database.
D.	In order to install the Scaling Font Service automatically whenever you reboot your system, add the following to [Sys]<Sys>sysinit.jcl (create this file, if it does not already exist):
$Run [Sys]<Sys>ScalingFontService.run
If you use a directory other than the default for outlines, or otherwise need to specify nondefault parameters, these must be included on the line to run the Scaling Font Service, following the required number of commas.  For example, since the outline directory is the 6th parameter, it will follow the 6th comma:
$Run [Sys]<Sys>ScalingFontService.run,,,,,,[d1]<sfs>
4.2	Cluster Systems with Local File Storage
Use the same procedure as is used to install on a standalone system.
4.3	Server Hard Disk Systems
If you can log into the server and access a floppy drive you can use the same procedure to install on a server as to install on a standalone system.  You can also install onto the server system from a locally booted cluster system, by substituting [sys] for [sys] in the command forms that are displayed during installation.
4.4	Shared Resource Processor Systems
You can install onto a Shared Resource Processor system from a locally booted cluster system, by substituting [sys] for [sys] in the command forms that are displayed during installation.
To install the Font Service on a Shared Resource Processor system running CTOSSRP 1.4 or later or XEBTOS 7.0 or later, you must add the following line to the file [Sys]<Sys>initfp00.jcl and reboot the Shared Resource Processor.
$Run [Sys]<Sys>ScalingFontService.run
To install the Font Service on a Shared Resource Processor system running CTOSXE 3.0 or later, you must add the following lines to the file [Sys]<Sys>SysInit.k.jcl (where k is the keyswitch: m, r, or n) and reboot the Shared Resource Processor.  In this example, the Scaling Font Service will be run on the GP00 board.
GP00
$Run [Sys]<Sys>ScalingFontService.run
With any Shared Resource Processor, if you use a directory other than the default for outlines, or otherwise need to specify nondefault parameters, these must be included on the line to run the Scaling Font Service, following the required number of commas.  For example, since the outline directory is the 6th parameter, it will follow the 6th comma:
$Run [Sys]<Sys>ScalingFontService.run,,,,,,[d1]<SFS>
4.5	Standalone Floppy Disk Systems
The Scaling Font Service is not designed to run on floppybased systems (Diskless Workstations).
5.0	Required Files
5.1	For Local Scaling Font Service
The following files are required on any workstation or system, standalone, server or cluster, on which the Scaling Font Service will be installed.
In the directory [Sys]<Sys>:
	ScalingFontService.run	DeinstallFS.run
In the directory [Sys]<sfs>:
CT903000.spd	CT903001.spd
CT903002.spd	CT903003.spd
CT903004.spd	CT903005.spd
CT903006.spd	CT903007.spd
CT903008.spd	CT903009.spd
CT903010.spd	CT903011.spd
CT903013.spd	CT903014.spd
CT903015.spd	CT903016.spd
CT903017.spd	CT903018.spd
CT903019.spd	CT903020.spd
CT903021.spd	CT903022.spd
CT903023.spd	CT903024.spd
CT903025.spd	CT903026.spd
CT903027.spd	CT903028.spd
CT903029.spd	CT903031.spd
CT903032.spd	CT903033.spd
CT903034.spd	CT913012.spd	
CT923004.spd	CT990003.spd	
CT990011.spd	FONT3012.spd	
FONT3030.spd	
In the directory [Sys]<sfs>:
ScalingFont.dbs	ScalingFont.metrics
The file ScalingFont.dbs above can be stored on another volume and named anything, so long as the name is specified (as the first parameter) when the Scaling Font Service is installed.  The outline files (those ending in .spd) can be stored on another volume if the volume and directory named are specified (as the sixth parameter) when the Scaling Font Service is installed.
The file ScalingFont.metrics is created automatically by the Install Scaling Font Service command.
5.2	For Font Database Customization 
The following files are required on any workstation or system, standalone, server or cluster, on which the scaling font database will be customized.
In the directory [Sys]<Sys>:
	FontCapture.run	FontForms.lib	
	FontTool.run	FontToolMsg.bin	
	IsamServer.run
In the directory in which the Font Tool is run:
	FontCharacterSet.isam	FontDevice.data
	FontFamily.data	FontKey.isam
	FontPseudoFamily.isam	FontRaster.isam
	FontReduction.data	FontTranslate.isam
	FontWidth.isam	FontIsam.config
In addition to the above, to nationalize the scaling fonts the following files are required:
In the directory [Sys]<Sys>:
FontNationalize.run
In a directory pathed to before running the nationalization tool:
FONT0003.spd	FONT0011.spd	
FONT3000.spd	FONT3001.spd	
FONT3002.spd	FONT3003.spd	
FONT3004.spd	FONT3005.spd	
FONT3006.spd	FONT3007.spd	
FONT3008.spd	FONT3009.spd	
FONT3010.spd	FONT3011.spd	
FONT3013.spd	FONT3014.spd
FONT3015.spd	FONT3016.spd
FONT3017.spd	FONT3018.spd
FONT3019.spd	FONT3020.spd
FONT3021.spd	FONT3022.spd
FONT3023.spd	FONT3024.spd
FONT3025.spd	FONT3026.spd
FONT3027.spd	FONT3028.spd
FONT3029.spd	FONT3031.spd
FONT3032.spd	FONT3033.spd
FONT3034.spd
6.0	System Software Compatibility
6.1	Workstation Environment
Scaling Font Service can be used under CTOS 9.8 or later, CTOSVM 2.2 or later, BTOS 8.2 or later, BTOS II 3.0.1 or later.  Use of the Scaling Font Service requires installation of GPS 2.4 or later.  
6.2	Shared Resource Processor
Scaling Font Service can be used under CTOSSRP 1.4 or later, XEBTOS 7.0 or later, or CTOSXE 3.0 or later.  Use of the Scaling Font Service requires installation of GPS 2.4 or later.
7.0	Hardware Information
7.1	Hardware Configurations Supported
Scaling Font Service 1.0 can be installed on B26, B28, B38, B39, XE520, XE530, CWS, NGEN series 186, 286, 286i, 386, 386i, and SRP workstations.
7.2	Special Hardware Requirements
Utilization of the Scaling Font Service with Document Designer or OFIS Designer requires a high resolution (1024x768) monitor.
8.0	Resource RequirementsUtilization
8.1	Response Times
We have evaluated performance of the Scaling Font Service by testing response times in WYSIWYG Document Designer.  Document Designer accesses the Scaling Font Service when:
	a font is used which has not previously been used, at that size, during the current session.
	a character is used within a font, which has not been retrieved previously during the session.
Document Designer keeps bitmaps for individual characters around in memory andor its own disk file during a session, and the time to display text in the fonts already retrieved does not depend on the Font Service.  Document Designer 2.3 partitions each font by character code range, so that bitmaps are stored in 2K blocks.  In smaller fonts, Document Designer will hold the entire font in relatively few blocks, and will rarely need to access the Font Service for more characters.  In large fonts, Document Designer will occasionally need to go back to the font service to retrieve additional characters, not previously used.
For the performance test we ran Document Designer on a cluster workstation, with the Scaling Font Service installed locally.  The following performance measurements were made on a 386 processor.  The Scaling Font Service uses no floating point operations; hence the presence of a floating point coprocessor does not affect performance. 
If the font service has already loaded the outline, the typical time to retrieve all the commonly used characters of a font is 3 seconds.
An additional lag of 1.0 to 1.4 seconds occurs when the Font Service must load into memory different outlines than it currently has loaded.  By default, the font service can hold outlines in memory for 2 or 3 fonts at one time.  This can be increased by use of the [ of outline cache blocks] field of the installation form.
The first request to retrieve any character of a font is about 3 seconds slower if the scaled metrics do not already exist in the cache file.  This cache contains the bounding box of the font, the width of each character, and the amount of space required by each character's bitmap.  The entire font must be scaled by the Font Service the first time that a font is required in a particular orientation and size, etc.  If the cache file is large enough to hold the metrics of all the fonts you use, you will never encounter this additional delay after the first days of use of the Scaling Font Service.
By contrast, when the font has been prescaled in the font database, using the Export Raster Fonts utility, the time required to retrieve all the commonly used characters of a font is 0.6 to 0.7 seconds.  This includes Document Designer overhead which is built into all of the above timings.  
Hence, if the outline is already loaded, and the metrics of the font at the requested size have been established by previous use, the extra cost of scaling a font onthefly is less than 2.5 seconds.
8.2	Memory RequirementsUtilization
The Scaling Font Service requires approximately 130K of memory.  
If you need to minimize memory usage, we recommend installing the Scaling Font Service only on the server workstation.  If memory is not an issue, install the Scaling Font Service locally.
8.3	Disk RequirementsUtilization
The Scaling Font Service requires about 2800 sectors of disk for the program, database and outlines.  By default, the Scaling Font Service uses 610 sectors for the scaled metrics cache.
If you need to minimize disk usage, we recommend installing the Scaling Font Service only on the server workstation.  If disk space is not an issue, install the Scaling Font Service locally.
9.0	Certification Information
No certification information applies to the Scaling Font Service.
10.0	Supplementary Information
10.1	Installation Parameters
The Scaling Font Service is loaded into memory instead of the standard Font Service, by use of the Install Scaling Font Service command.
Install Scaling Font Service
  [Font database ([sys]<gps>ScalingFont.dbs)]
  [Bytes of buffer space (8192)]
  [ of outline cache blocks @64K RAM (1)]
  [ of scaled metrics to cache @1.5K disk (200)]
  [Cache file ([sys]<gps>ScalingFont.metrics)]
  [Outline directory ([sys]<sfs>)]
The default name of the scaled metrics cache file is [sys]<gps>ScalingFont.metrics. This cache file is created and built by the Scaling Font Service itself over time, and data in it are reused whenever the Scaling Font Service is run.
The size of the metrics file, in sectors, is 3 times the number of metrics to cache.  If the number of scaled metrics is left blank, the size of scaled metrics cache file is left unchanged.  If it did not previously exist, it is allocated to 610 sectors, by default.  If the metrics file does already exist, and the number of scaled metrics is specified differently than before, the font metrics file is either extended or truncated.  
All outline files must be located in the outline directory.  The outlines for 2 to 3 fonts can be buffered in memory, for each outline cache block allocated, up to a maximum of 8 outline cache blocks.
The scaling font service is deinstalled by the Deinstall Font Service command, distributed with the Generic Print System, 2.0 or later.
10.2	Line Drawing Characters
The CTOS system font includes ruling characters in the hex code range of C0 through FC.  Similar characters are accessed in this range via the Scaling Font Service.  Whereas the system font contains three types of rulings: single, double and thick; the Scaling Font Service contains only single and double rulings.  Character codes which normally access thick rulings will access the corresponding double ruling via the Scaling Font Service.
Be aware that ruling characters do not match characters in corresponding fonts available on PostScript printers.  These characters will not print on PostScript printers.  The only supported device driver for printing documents containing ruling characters is the HP LaserJet device driver, using the HpScale font device type, which downloads fonts from the Scaling Font Service to PCLcompatible printers.
Ruling characters for all proportional fonts in the Scaling Font Service are square, whereas they are only 60 as wide as they are tall in the system font.  That is, the width of each ruling is equal to the point size height of the font.  Thus the width of a 12 point ruling character is 16th inch or 20 pixels at 120 dpi.  The character code BF has been defined in the Scaling Font Service as a space with the width of a ruling.  The use of this character simplifies the effort of creating rulings that connect correctly.  
However, if you must place text within the rulings, using Document Designer or OFIS Designer, you will need to set tabs that are an even multiple of the ruling width.   Only use point sizes that are multiples of 3.  The pixel width of the font is 53 of the point size.   To set tab stops that are a multiple of the pixel width, you must remember that each tick mark in the ruler is equal to 12 pixels, and that codeshift or codeshift will move the cursor one pixel when the tabs menu is displayed.  For example, to set even tabs every 40 pixels, bring up the tab menu, move the cursor three tick marks to the right of the left margin, press codeshift four times, and press E.
For sanity's sake, we advise use of the Courier (monospaced) font when using ruling characters to create onscreen rulings as this avoids the above complexities.
11.0	Documentation Updates
Standard documentation for the Scaling Font Service is found in the manuals Using the Font Tool and GPS Programmer's Guide.
12.0	Status Codes
The Scaling Font Service can return any of the status codes which are returned by the standard the Font Service.  These are described in the section on Font Services in the Status Codes Manual, third edition (page 3386 and following).  In addition to these errors, the Scaling Font Service can also return the following error codes:
13915	An error was encountered when opening an outline file.  Be sure that all the outline files are present in the directory specified when installing the Scaling Font Service ([sys]<sfs>, by default).  Verify that no access violations or disk errors are encountered when accessing each outline file.
13916	Invalid parameters.  For example, the parameters passed to the Scaling Font Service are incomplete or specify a font size that is out of range.
13917	Scaling keys too complex.  The font database names more scaling font keys or outlines than the font service can uniquely identify.  Deinstalling the font service, and deleting the metrics cache, before reinstalling the Scaling Font Service, will temporarily work around the problem.  The permanent solution is to reduce the number of font keys in the font database which reference distinct combinations of outlines, character sets, and device type.
	The Scaling Font Service caches highly compressed (binary) representations of the device type, outlines and character sets indicated by various font keys referenced in calls to the Scaling Font Service.  Each of these is assigned a unique 8bit ID which makes up half the unique 16bit handle used to identify each font in the small and medium format calls.  (The other bits indicate the point size of the font.)  These handles are used to reaccess fonts on successive calls to the Scaling Font Service (by Document Designer, for example) and to obtain font metrics cached in prior calls.  This error indicates that the space for identifying distinct fonts has been exhausted.  It is impossible to assign a unique font handle for reaccessing the font.  No more than 256 distinct scaling font keys can be referenced, or 256 outline files qualified by distinct character sets.
13918	An invalid outline file was accessed.  If this occurs, reinstall the outlines from the distribution media, and renationalize them if necessary.
13919	An unanticipated error was detected in the Speedo portion of the Scaling Font Service, supplied by Bitstream, Inc.
13920	An unanticipated error was detected in the portion of the Scaling Font Service implemented by Unisys.
13921	Outline names too long.  The Scaling Font Service caches the names of outline files used for scaled fonts in a fixed area of the metrics cache file, which is mirrored in memory.  This area has room for 194 outline names, if the 12character naming conventions in the released product are followed.  If you are adding more outlines than this (e.g., purchased from Bitstream), rename them to use shorter names (e.g., omit the .SFO suffix) and modify the font database accordingly.  There is an architectural limit of 256 outlines, which can be accommodated with 8character names.
The following error code is not returned by the Scaling Font Service, but is returned by the standard Font Service, distributed with GPS 2.4 or later, if you use the standard Font Service with a font database generated for use with the Scaling Font Service:
13914	Scaling Font Service required.  This error will occur if the reduced font key in a request for font data indicates that the font should be scaled onthefly.  It will also occur if the application (such as the HP LaserJet device driver) requires a font in a format that can only be supported by the Scaling Font Service.
13.0	Known Errors and Omissions
Document Designer 2.2 and earlier, or OFIS Designer 2.0 will GP fault (exit or fall into the debugger) when the Scaling Font Service returns an error code.  This will happen, for example, if a referenced outline file cannot be accessed by the Scaling Font Service.  This could have happened when using the Screen Font Database as well.  However, errors rarely occur within the standard Font Service since all scaled fonts are imbedded in the runtime font database.  This problem is corrected in Document Designer 2.3 and in OFIS Designer 2.1.
	<End of Document>