> 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-7-1.md).

# Version 6.7.1 Changelog (2016-11-14)

World's #1 PDF SDK Library for Web, Mobile, Server, Desktop

### New Features

* Support for JavaScript actions. This can be enabled using PDFNet.EnableJavaScript(true) and includes the following interactive PDF features :
  * Automatically recalculated fields.
  * Verification of user input.
* Built-in DOC-to-PDF conversion support.
* Export to individual separations using PDFDraw.
  * Rather than converting to an output format such as RGB, PDFDraw can now preserve separations. Output can be in the form of a single N-channel TIFF, or to a number of output files, one for each separate ink in the source document.
* Support for the "cloudy" and "nozoom" annotation styles.
* Stream documents to PDFViewCtrl during conversion to PDF, through new Universal Conversion interface. (Available on PDFNet Mobile SDK for Android and PDFNet Mobile SDK for UWP.) Supports the following file types:
  * Office file conversion support: .docx, .pptx, .doc. (with the optional office conversion module)
  * Image conversion support: .bmp, .jpg, .tif, .png, .gif
  * Image collections (zip archives with any type of image internally)
  * plain text file formats

### Performance Improvements

* Faster shape rasterization (0-20%).
* JBig2 decoding performance improvements (3-5x faster in many cases).
* JPEG2000: for the majority of JPEG 2000 encoded images, decoding is now faster and uses much less memory.
* faster CMYK->RGB conversion in many cases.
* parsing improvements: much improved performance on files with complex content streams.

### Bugfixes

* Overprint preview handling has been improved.
* 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-7-1.md?ask=<question>&goal=<user_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.