Ada binding to Adobe Font Metrics
Date/Time of Processing: Tuesday 24 May 1994 06:08:45Pm Overall Assessment of System: OK Classification of System: B Basis of Classification -- Syntax Errors PASS Completeness PASS Independence from External Libraries FAIL Independence from a Specific Ada Compiler PASS Explanations for failures -- System withs non-standard library units that are not provided Number of ... Files 2 Library Units 2 Lines 551 Statements 214 Comments 189 Unidentified Withed Units -- 1 unidentified withed units
languages/ada/bindings/adobefm: File Name Size --------- ---- README 1,762 adobefm.zip 19,313 Totals ============== ============== 2 Files 21,075
ASSET_A_337: Ada Binding to ADOBE Font Metrics. This set of packages provide an Ada binding to Adobe Font Metrics. They utilize an AFM parser written in C. Together these files provide the functionality to parse Adobe Font Metrics files and store the information in predefined data structures. It is intended to work with an application program that needs font metric information. The program can be used as is by making a procedure call to parse an AFM file and have the data stored, or an application developer may wish to customize the code. This program is based on the document "Adobe Font Metrics Files, Specification Version 2.0". AFM files are separated into distinct sections of different data. Because of this, the parseAFM program can parse a specified file to only save certain sections of information based on the application's needs. A record containing the requested information will be returned to the application. AFM files are divided into five sections of data: 1) The Global Font Information 2) The Character Metrics Information 3) The Track Kerning Data 4) The Pair-Wise Kerning Data 5) The Composite Character Data. Basically, the application can request any of these sections independent of what other sections are requested. In addition, in recognizing that many applications will want ONLY the x-width of characters and not all of the other character metrics information, there is a way to receive only the width information so as not to pay the storage cost for the unwanted data. An application should never request both the "quick and dirty" char metrics (widths only) and the Character Metrics Information since the Character Metrics Information will contain all of the character widths as well.
1 Feb 93 1993 Alex Blakemore Initial release to ASSET 12 Nov 93 1993 ASSET Initial release to the PAL
This prologue must be included in all copies of this software. Restrictions on use or distribution: NONE
This software and its documentation are provided "AS IS" and without any expressed or implied warranties whatsoever. No warranties as to performance, merchantability, or fitness for a particular purpose exist. The user is advised to test the software thoroughly before relying on it. The user must assume the entire risk and liability of using this software. In no event shall any person or organization of people be held responsible for any direct, indirect, consequential or inconsequential damages or lost profits.