> 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/xamarin/changelogs/version-6/v6-7-1.md).

# Version 6.7.1 Changelog (December 6, 2016)

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

In this version, both binding projects for Xamarin.Android and Xamarin.iOS have significant changes. New blog posts can be found here for more information. [Xamarin.Android](/xamarin/get-started/xamarin-android/integrate-android.md#integrate-with-nuget) and [Xamarin.iOS](/xamarin/guides.md).

## Xamarin.Android

* All support dependencies are now added through NuGet packages.
* **Full version only** New `Convert` APIs to convert word to PDF.
* New `OutlineDialogFragment` that lists all outline in the document.
* New `UserBookmarkDialogFragment` that lists all user added bookmarks in the document. Supports adding, renaming, re-arranging and deleting bookmarks.
* New `ThumbnailsViewFragment` that shows all pages in the document in grid view. Supports page modification such as adding, re-arranging, deleting, and rotating pages.

## Xamarin.iOS

* Updated to use dynamic framework binding, applications will no longer need to include any extra resources, such as tools-strings.bundle.
* New `Convert` APIs to convert word to PDF.


---

# 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/xamarin/changelogs/version-6/v6-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.