AFP Container Architecture

Size: px

Start display at page:

Download "AFP Container Architecture"

Natalie Paul
5 years ago
Views:

1 AFP Container Architecture Reinhard Hohensee Distinguished Engineer October 24, 2003 Ricoh

2 Topics Rationale Overview of Architecture Object-type Registry Container Structure Include Object (IOB) System Issues 2

3 Rationale Pre-1994 AFP data objects (all IBM-defined): Text: PTOCA (Presentation Text Object Content Architecture) Graphics: GOCA (Graphics Object Content Architecture) Image: IOCA (Image Object Content Architecture); also an older version called IM Image Bar Codes: BCOCA (Bar Code Object Content Architecture) Significant growth in new data formats starting in late 1980s PostScript, TIFF, JPEG (JFIF), etc. Sophisticated definition of color in new formats, e.g, PostScript-2 *** Needed to extend the AFP architecture to allow customers to leverage emerging de-facto standard data formats *** 3

4 Overview of Architecture Formal architecture for supporting non-oca objects in AFP environments Two types: Presentation objects: rendered on page; e.g. EPS Non-presentation objects: support rendering but not directly rendered; e.g. Color Mapping Table, TrueType/OpenType fonts Presentation object: Processed on page as complete peer with OCA objects Developed in own presentation space according to the object definition Object defines its presentation space size Object defines how its presentation space mixes with other data on page (e.g. what parts of object are transparent/opaque) Object presentation space mapped to MO:DCA object area just as the OCAobject spaces are mapped to the MO:DCA object area Objects to be supported driven by customer requirements 4

5 Overview (contd) Non-presentation object: Not directly invoked for inclusion on page Sent to printer in support of presentation Doesn t need to define presentation semantics size, foreground/background since it is never directly included on page 5

6 Container Presentation Space Concepts 6

7 Object-type Registry Each object-type to be supported in containers must be formally registered in the MO:DCA architecture (Appendix D in MO:DCA Reference) Registry uses an ISO OID sub-tree to assign a unique object-type identifier (OID) to the object (not to be confused with an object OID that may be generated for an instance of a specific object) Object-type OID must be specified (using the X 10 triplet) on structured fields that envelope, include, map the object Object must be well-behaved : Must be formally defined in a published specification Presentation objects must be limited to a single page ( paginated ), must define the presentation space size, and must define foreground (which mixes opaque) and background (which mixes transparent) 7

8 Object-type Registry (contd) Example presentation object: Portable Document Format (PDF): Single-page Object with Transparency. This is a presentation object consisting of a PDF file that defines a single page containing text, graphics, and image using PDF operators. Definition: The PDF file format is defined in the Portable Document Format Reference Manual, Adobe Systems Inc. Presentation Space Size: The (x,y) coordinates of the lower-left corner and upper-right corner are specified by the required MediaBox key in the Page Object dictionary Foreground: The painted portions of the object presentation space Background: The unpainted portions of the object presentation space Component ID (49) Object-type OID X'06072B ' 8

9 Object-type Registry (contd) Example non-presentation object: TrueType/OpenType Font Resource Object: This is a font resource object that may be referenced by a data object. Definition: The TrueType font format is defined in the TrueType Reference Manual, 1999, Apple Computer Inc.. It is a subset of the OpenType font format, which is defined in the OpenType Specification, 2000, Microsoft Corporation and Adobe Systems, Inc. Presentation Space Size: N/A, this is not a page-level presentation object Foreground: N/A, this is not a page-level presentation object Background: N/A, this is not a page-level presentation object Component ID (51) Object-type OID X'06072B ' 9

10 Container Structure Structured fields Begin Object Container (BOC): must specify name of object and object-type OID Object Container Data (OCD): carries object data End Object Container (EOC) Map Container Data: specifies mapping of object presentation space to object area; only needed if container placed directly in page stream (not recommended) Container Data Descriptor (CDD): currently does not specify any information; only needed if container placed directly in page stream (not recommended) 10

11 Valid Container Structures 11

12 Include Object (IOB) Allows the data stream to reference the object in its native, unaltered format Allows the object to be treated as a resource Mapped with Map Data Resource (MDR) structured field Allows multiple instances of the same object to be included using different presentation characteristics (size, clip window, rotation, etc.) IOB specifies the presentation parameters that are normally carried in the Object Environment Group (OEG): Object Area measurement units, size, position, rotation Mapping option for object presentation space to object area mapping (scale-tofit, scale-to-fill, center-and-trim, position-and-trim, position) Offset of object presentation space in object area if a position or position-andtrim mapping is specified ** When also specified in the OEG, the IOB parameters always override ** 12

13 Include Object (IOB) (contd) 13

14 IOB to Mapped Resource 14

15 IOB to Mapped and Pre-RIP d Resource 15

16 System Issues Not all container objects that are supported in the architecture can normally be supported directly in printers RIP royalties Non-optimum formats result in high throughput penalties Example: Infocolor 130+ supports EPS and PDF page objects May need server-level transforms Ideal solution: dynamic object-level transforms that are invoked pre-spool for an AFP file 16

17 Object-level Transform 17

18 Summary *** The AFP container architecture allows customers to integrate popular de-facto standard data formats such as EPS, PDF, TIFF, and JPEG (JFIF) into their AFP workflows. These formats can be mixed with traditional AFP data formats, and can be processed as resources for high print performance. *** 18

AFP Support for TrueType/Open Type Fonts and Unicode

AFP Support for TrueType/Open Type Fonts and Unicode Reinhard Hohensee Distinguished Engineer October 24, 2003 Ricoh Topics What is Unicode? What are TrueType and OpenType fonts? Why have we extended the