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

# Version 11.9.1 Changelog (December 11, 2025)

Review the 11.9.1 change log for the Apryse Server SDK.

## New In This Release

Version 11.9.1 is primarily a bugfix release.

### Bugfixes

* **\[xod]** Temporarily disabled previous fix `Fixed a rendering issue with text at small font size for XOD (and XPS) files that are converted from PDF with embedded TrueType fonts`, because it caused some text in a specific document to disappear when rendering from PDF to image.
* **\[node]** Corrected NodeJS to only require GLIBC 2.17 at minimum on Linux. In 11.9 this was unintentionally set to GLIBC 3.4.30.

### Office Fidelity

* **\[xlsx]** Improved handling of `ExcelMaxAllowedCellCount` for documents with a large number of empty rows. Each empty row now counts as one cell towards the cell count.
* **\[office]** Improved font substitution for CJK fonts on Linux.


---

# 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-11/11-9-1.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.