DynaPDF Manual - Page 689

Previous Page 688   Index   Next Page 690

Function Reference
Page 689 of 818
diSubject
= 4,
diTitle
= 5,
diCompany
= 6,
diPDFX_Ver
= 7,
// GetInDocInfo() or GetInDocInfoEx()
diCustom
= 8,
// Not supported -> Use SetDocInfoEx()
diPDFX_Conf
= 9,
// GetInDocInfo() or GetInDocInfoEx()
diCreationDate = 10, // Available after a PDF file was imported
diModDate
= 11
// GetInDocInfo() or GetInDocInfoEx()
}TDocumentInfo;
The function sets or changes a document info entry. This function is implemented in an Ansi and
Unicode compatible version. The Ansi Version supports Ansi strings of the code page 1252. To
create a documents info entry in an arbitrary 8 bit or CJK encoding convert the string to Unicode
with the function ConvToIncode() and use the Unicode version to set the entry.
Return values:
If the function succeeds the return value is 1. If the function fails the return value is 0.
SetDocInfoEx
Syntax:
LBOOL pdfSetDocInfoEx(
const PPDF* IPDF,
// Instance pointer
TDocumentInfo DInfo, // see SetDocInfo() above
const char* Key,
// User defined key
const char* Value)
// The value for a specific key
The function sets or changes a document info entry. This function supports also user defined keys
which can be created or changed if necessary. If the parameter DInfo is set to diCustom the
parameter Key must contain a unique key.
The following keywords are reserved and must not be used as user defined keys:
Author
CreationDate
GTS_PDFXVersion
Keywords
ModifyDate
Producer
Subject
Title
Trapped
Note that the function does not check whether a reserved key is used. Using such a key causes
maybe errors which are mostly not reported in viewer applications.
User defined keys should be defined as 7 bit ASCII string and the usage of special characters like /,
\, #, or character codes higher than 127 should be avoided. The value of the document info entry
should not contain binary data.
Remarks:
 

Previous topic: SetDefBitsPerPixel, SetDocInfo

Next topic: SetDrawDirection, SetEMFFrameDPI


Start Chat