> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/core/changelogs/version-6/6-8.md). # Version 6.8.0 Changelog (2018-04-06) World's #1 PDF SDK Library for Web, Mobile, Server, Desktop ### New Features * Built-in XLSX-to-PDF conversion support. * Export to individual separations using PDFDraw. * PDF documents can now be secured using PDF 2.0 AES256 Encryption. * Expanded UTF8 encoding for PDF 2.0. * Improved support for many annotation properties in the XFDF specification. * PDF.Convert can now convert markdown files to PDF * PDFDraw now supports very high resolution output via tiled rendering. * PDFDoc.FDFUpdate(fdfdoc) which will intelligently update the annotations in the PDF with those in the FDF document. In particular it does this in a manner that will minimize the modifications to the PDF. This can be used to sync the PDF document with the annotation state exported from WebViewer and incrementally save any annotation changes. * Text highlight annotations are now more aesthetically pleasing. ### Performance Improvements * Overprint preview handling has been optimized. * Linearized save on documents with many pages is now significantly faster. * Added caching for high-dimensional sampled functions and complex Postscript functions -- rendering speed improved by 5x on some documents. * Greatly improved speed and memory usage while converting text files to PDF. * Conversion from CalRGB to device colorspaces is now more than 2x faster. * Repeated calls to PDF.GetPage are now much faster, particularly for documents with many pages. ### Bugfixes * Lots of improvements and fixes to Office to PDF conversion outputs. * More robust handling of corrupt documents. * Improved stability when used in an interactive environment. * Many other miscellaneous bug fixes. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.apryse.com/core/changelogs/version-6/6-8.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.