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

# Version 6.10.0 Changelog (2019-03-04)

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

### New Features

* PDF Compare/Diff API (PDFDoc.appendVisualDiff)
* Snap to Geometry API (in PDF Viewers) \[Only on Windows]

### Improvements and Bugfixes

* Updated XFDF export/import to better support Measure Tools, Redaction Annotations and Form Field Tooltips.
* Support for file sizes greater than 4gb on 32 bit platforms
* Many improvements and fixes to Office to PDF conversion outputs.
* Reduced memory usage during parsing and rendering.
* Reduced the number of unnecessary resources pulled in by page import.
* Improvements to font substitution logic.
* Better handling for corrupt documents, especially corrupted streams.
* 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.apryse.com/core/changelogs/version-6/6-10.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
