> 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/uwp/print.md). # Print - [Print Library for UWP](https://docs.apryse.com/uwp/print/print.md): Print PDF files to a default printer with optimal compression. Learn how to get started with printing PDFs efficiently. Perfect for all your printing needs. The Apryse uwp SDK streamlines secure docum - [Printing a document with UWP](https://docs.apryse.com/uwp/print/printing.md): Learn how to optimize printing with Apryse's UWP PDF library. Follow step-by-step instructions to register and customize print options effortlessly. Master printing management for your documents today - [Code samples for printing PDFs in UWP](https://docs.apryse.com/uwp/print/samples.md): Learn how to combine multiple pages using PDF imposition with this sample. Arrange pages for printing or create a 'master' page from 'source' pages efficiently. The Apryse uwp SDK streamlines secure d - [APIs for PDF printing in UWP](https://docs.apryse.com/uwp/print/apis.md): Learn how to optimize print and PDF documents with utility classes in UWP using pdftron.PDF.PDFPrintManager. Enhance your document management now! The Apryse uwp SDK streamlines secure document proces --- # 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/uwp/print.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.