DLI Implementation and Reference Guide - Datalogics

5.10 DLI Implementation and Reference Guide
dlpdftextdestroy
After placing the DLPDFTEXT area, or after finishing with any DLPDFTEXT area,
Concepts and Facilities: Guide to the DL Pager Composition System
destroy the text area with the dlpdftextdestroy function call:
void dlpdftextdestroy (DLPDFTEXT *)
After destroying a DLPDFTEXT area, the memory for the text and other information is
released, and the text area may no longer be used by an application.
Performance Considerations
The Unicode and multibyte functions in DLI described above represent an order of
magnitude of performance improvements and run-time memory usage. In addition,
Datalogics can offer some notes and tips on performance and other considerations:
• Do not create separate DLPDFCONTENT areas for each DLPDFTEXT string. In
general, each DLPDFCONTENT area created represents additional overhead during
both creation and processing of a PDF file, increased file size, and slower rendering
of a PDF page. Best performance is usually obtained by using one DLPDFCONTENT
area per page, and pasting all content into this content area.
• Avoid using both single-byte and multibyte versions of fonts. This results in
increased creation time to subset two different fonts, as well as slower rendering
and processing of PDF files.
• If you are typesetting in Chinese, Japanese or Korean, and are certain that readers
of a PDF file will have the appropriate Acrobat language pack installed for their
reader, consider using the Adobe OpenType fonts (subtype 0 CID fonts), and not
embedding or subsetting. Though you will not be able to use the functionality
described in this chapter, this could prove to generate faster and smaller PDF files.
See the WideText sample application included beginning with the DLI v3.0.4
release for a demonstration of how to set Unicode text using these fonts.