Revision Date: September 13, 2006 Case ID: n/a Description: Support has been added to PDPageDrawContentsToMemory for DeviceRGBA and Lab colorspaces for rasterization. These can be used as colorspace names to be passed to the method, and will generate RGB + alpha information (DeviceRGBA) or 24-bit Lab color information (Lab), as you prefer. Note that there is also experimental support for LabA (Lab + alpha) rasterizations, but there are still some known issues in certain situations; we do not recommend attempting LabA rasterizations for Production work at this time. Optional samples for both the RGBA and Lab/LabA rasterizations can be downloaded from the Knowledgebase of the Datalogics website via http://www.datalogics.com/support.asp
Revision Date: September 13, 2006 Case ID: 14466 Description: The PDWordGetNthCharStyle API has been revised to correspond to its description within the Adobe documentation, and minimize some confusion that had resulted in the past. As the wording of the documentation had suggested, it now accepts an index to character styles, not an index to style by character. Documentation: Acrobat and PDF Library API Reference
Revision Date: September 13, 2006 Case ID: n/a Description: The PDFontGetMetrics and PDFontSetMetrics API declarations were corrected. These now accept an ASSize_t parameter in place of the undefined type os_size_t. Documentation: Acrobat and PDF Library API Reference
Revision Date: September 13, 2006 Case ID: n/a Description: For the PDFLInit API, the PDFLDataRec stucture now accepts the flag kpdflinitignorecurrentdirectory, which will ignore the current working directory when searching for fonts. The kpdflinitignoredefaultdirectories flag implies this behavior as well, as it has in previous releases. Documentation: Acrobat and PDF Library API Reference
Revision Date: September 13, 2006 Case ID: n/a Description: Production requirements at some sites specified that no temporary data of any kind should be written to disk at any point in the process. In previous releases, work files had been written to disk, even when the final output was not. (i.e. Final output was returned in memory instead.) A change was made to the Adobe PDF Library so that temporary metadata streams are now written to the temporary APDFL filesystem instead of the default filesystem. With this enhancement, APDFL is now able to write no processing data to disk, if so desired.
Revision Date: September 1, 2006 Case ID: 20028 Description: A problem was reported when merging two files in memory and attempting to call ASFileSetEOF, at which point the application would freeze. It was found that a combination of circumstances could lead to a point where an internal lock was not being released, causing the application to wait endlessly. This has now been corrected.
Revision Date: September 8, 2006 Case ID: 19973 Description: In PostScript print output, a gsave was being placed before the %%BeginPageSetup of a page instead of after the %%EndPageSetup, leading to problems when customer-added setpagedevice calls (added via callbacks during page setup) were reset during the next grestore. The gsave portion of the page's gsave/grestore pair has now been moved so that it falls just after the call to the client-supplied PSPrintAfterBeginPageSetup callback.
Revision Date: August 2, 2006 Case ID: 19972, 20026 Description: A problem was reported on some Solaris systems in which font resource location searches were not including system directories. A problem in CoolType that deactivated system font location searches was found and removed.
Revision Date: August 24, 2006 Case ID: 19969 Description: The dlpdfcontenttext method was returning an exception when WinCP1255 encoding was specified. This was traced to a problem in an internal call to PDEFontGetNumCodeBytes, which was not accepting fonts which are remapped to glyphids, and was causing the observed APDFL exception. An internal DLI revision was made, and it now assumes that all fonts with a single-byte translation table are single-byte fonts, for the purposes of noting that characters are used.
Revision Date: July 11, 2006 Case ID: 19860 Description: Output page scaling was incorrect when printing to Legal-sized pages. A problem was found in page-scaling calculations that were attempting to make a best-fit of document to paper, which resulted in a transposition of printer paper dimension values during the output resizing. This has been corrected.
Revision Date: July 14, 2006 Case ID: 19637 Description: An exception of "Expected an array object" was seen when attempting to merge two documents, one of which contained a bad tree structure. The merging process has been enhanced to suppress exceptions in these cases since the output process can continue. If the exception occurs, the problem document's structure tree is removed, but the exception is not propagated any further.
Revision Date: July 12, 2006 Case ID: 19570 Description: An exception was being returned when attempts were made to change a "Keywords" entry in the InfoDictionary (i.e. in cases where an entry already existed). A mismatch was found between where the data actually resided and where the PDDocSetInfo() or PDDocSetXAPMetadataProperty() methods assumed it was, and thus the exception would be raised. This has been corrected.
Revision Date: April 7, 2006 Case ID: 19547 Description: An Acrobat error occurred when trying to display a document containing an imported page graphic. It was found that a process importing the PDF page when constructing the new document had assumed that the documented graphic state in effect at the beginning of a page's content stream was still in effect, and thus it attempted to directly set a color value under the assumption that the color model was DeviceGray. An error did not surface until Acrobat attempted to display the page later. Since the color was not in a 1-channel colorspace at that point, there were not enough operators for the colorspace set. dlpdfcontentreferenceform() was changed to explicitly set the default graphic state before placing a form, to ensure that the graphic state was known before further data was brought in.
Revision Date: February 8, 2006 Case ID: 19518 Description: PDPageDrawContentsToWindow and related methods were found to be discarding the Device Context clipping region, leading to errors when a user attempted to clip that region drawn to in the Device Context. An enhancement was made to store the clipping region used in case it was referenced later.
Revision Date: Case ID: 19334 Description: In a case where several Java Virtual Machines were sharing the same object, processes finishing early were hanging on their dlpdfterm() calls until a longer-running process could catch up, at which point all would then terminate. Internal changes were made to ensure that each process would now be fully independent by eliminating the chance of accidental interference with each other.
Revision Date: January 17, 2006 Case ID: 19228 Description: A problem was reported when attempting to merge two particular documents. It was found that if one document had a TrueType font file without a Macintosh-format CMap, a crash would occur. This was resolved by restructuring the processing & writing of the CMaps to resemble that of the Unicode-format CMap streams, which are recognized as being optional.
Revision Date: January 10, 2006 Case ID: 19221 Description: A multithreaded Library application was unexpectedly exiting when multiple PDFLInit calls were invoked in its code. This was resulting in a parent process termination before the last child process had completed. Logic has been added using thread counters and flags to ensure that each thread invokes PDFLInit and PDFLTerm only in matched pairs, and that a PDFLTerm does not occur until the last thread has completed.
Revision Date: March 15, 2006 Case ID: 19217 Description: A process attempting to merge multiple PDF files in memory before writing output was returning a "Bad parameter" exception. It was found that a tree naming routine was reaching an arbitrary testing limit while attempting to verify a unique name, and the returned exception was interpreted as a bad parameter. The test limit handling has been improved to allow the routine to complete its task.
Revision Date: December 28, 2005 Case ID: 19084, 19195 Description: A Library viewing application was showing screen refresh problems when changing its active window. A problem was found in Library modules that were attempting to read ahead and preload font information, and improved synchronization was made between background font reading and current display settings.
Revision Date: December 6, 2005 Case ID: 19144 Description: PDF output from the Library was not PDF/A compliant due to obj and endobj keywords not being followed by an EOL (End of Line) marker. This has been corrected.
Revision Date: October 6, 2005 Case ID: 18878 Description: When generating non-postscript output to a PCL device using a v7.x Library application, unwanted clipping would sometimes occur, leading to only partial output of the page image, and whitespace everywhere else. Problems with page scaling values and clipping boundaries were found and corrected. This was reported as Datalogics case #18878, and was later reported as Adobe bug number 1245000.
Revision Date: October 18, 2005 Case ID: 18794 Description: In print jobs for documents greater than 64,000 pages, a variable overflow problem prevented printing of all pages, printing only the remainder count (those left over after dividing by 64,000). A page counter variable problem was found, and the tracking variable's capacity was expanded from 16 to 32 bits.
Revision Date: December 8, 2005 Case ID: 18670, 19137 Description: Calls to PDPageDrawContentsToMemory for high-resolution images were occasionally failing due to unhandled exceptions. There were two problems identified: not detecting that an attempted memory allocation for output had failed, and not detecting that an excessively large rendering was incomplete. Internal tests were added to check for each condition and return the appropriate exception when required. In particular, requesting an extremely high resolution for which sufficient memory cannot be allocated for the size of the document will now be recognized as a problem before errors occur.
Revision Date: May 17, 2006 Case ID: 18317 Description: An access violation was occurring while attempting to process a document in which individual pages could be handled with no problems, but the document if taken as a whole would exhibit inconsistent behavior when stepping through pages. A memory handling problem was found and corrected.