Home > Information > FAQ > Papyrus DocEXEC Resource Management

Printer friendly version

Frequently Asked Questions about AFP

Questions about the Papyrus System

Papyrus DocEXEC Data Interface

Papyrus DocEXEC Resource Management

Papyrus DocEXEC Application Development

Papyrus DocEXEC Paper Handling Capabilities

Papyrus DocEXEC Statement Formatting Capabilities

Papyrus Designer related questions

Papyrus and SAP related questions

Terms and Abbreviations


Papyrus DocEXEC Resource Management

Resources are the fonts, logos and forms needed at time of formatting, viewing and printing to be able to generate and present the document correctly. If the correct resources are not used at time of formatting, viewing or printing the document will not just be lower quality, IT WILL BE WRONG! Resource management is a key to quality ensured document production.


Q: Do resources (font, forms, logos) need to be converted to internal format?

A: No. The Papyrus System uses the AFP resource formats directly.


Q: Is the resource (font, forms, logos) format standard or proprietary?

A: Standard. The Papyrus System uses the fully documented resource formats of the AFP architecture. This includes resolution independent Adobe outline fonts. If you already have AFP resources NO CONVERSION is required. Most other resources like MS True Type and TIFF can be converted with the Font Converter.


Q: Does the developer have to maintain resource tables for different printers?

A: No. As a single resource library is used for printing to all types of hardware, no other libraries or resource formats have to be managed manually.


Q: Does resource table information have to be maintained manually?

A: No. Papyrus reads all the information required, like forms and logos sizes and character width information from the resources directly.


Q: Are resource tables required for document formatting?

A: No. As the Papyrus DocEXEC also can run on a users laptop computer, such a requirement would not be sensibly manageable.


Q: Does the product support standard forms source code languages?

A: Yes. IBM OGL is the standard language, but also Xerox FDL can be converted and single document pages from most Windows products like PageMaker can be imported as forms through the Papyrus Printer Driver.


Q: Does the developer have support to deal with different resolutions?

A: Yes. Papyrus and AFP offer that support. Regardless the use of outline fonts, the document has to be committed to a resolution at formatting. The unavoidable differences between 240, 300 and 600 dpi can be checked at development time.



Q: Does the user have to define all relationships between objects manually?

A: No. These relationships are extracted automatically from the AFP resources on import to the database. In the following a query can be set up, which shows in which documents a certain font, forms or text element is used. This database can also be used to build export packages for software distribution systems.


Q: Can resources be converted or generated from other formats?

A: Yes. Adobe or TrueType Outline fonts can be converted to AFP font formats. TIFF images can be converted to PSEG or compressed IOCA. Forms can be converted from FDL or from Windows products to AFP.


Q: Does your product ensure that the proper resources are used for printing?

A: Yes. The AFP architecture enables this. IBM PSF and Papyrus Server dynamically control the use of resources in the printer from a single resource library. This is also done by Papyrus Server for Xerox Metacode and for HP-PCL4/5. In this manner the operator can choose whether he wants to print the document on a 240 dpi IPDS or 300 dpi Xerox Metacode machine without reformatting the output.

 

© 2008 ISIS Marketing GmbH - legal disclaimerImpressum • ISIS is not associated with Research Software Design (RSD), nor it's Papyrus Bibliography software.