> For the complete documentation index, see [llms.txt](https://docs.swingsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swingsoftware.com/pdf-converter-for-notes/getting-started/pdf-converter-terminology/pdf-package.md).

# PDF package

Before proceeding to use the SWING PDF Converter software, it is useful to familiarize yourself with the various terminologies used throughout this application.

A **PDF Package** is a single PDF document which acts as a container for other PDF documents. SWING PDF Converter provides the ability to export multiple emails or documents to a PDF Package.&#x20;

The created PDF Package will also contain a view with the same columns as in the original Notes view (e.g. **Date**, **From**, **To** and **Subject** columns) so users can sort, search and navigate through converted documents or emails similarly as in Notes.

PDF Packages are also known as **PDF Portfolios**.

After the PDF Package has been created, you can browse through converted files using Adobe Reader document view (supported in versions 8 and higher) as shown in the following screenshot:

![](https://3331713008-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MlCAurE6RSGoCmtmAET%2F-MlEcJIe1NFp0o6ppq2B%2F-MlEcWT70SGvKQFB955g%2Fimage.png?alt=media\&token=addf1f71-c356-4606-9394-03dbd944f435)

{% hint style="info" %}
**Note:** Not all PDF readers support viewing of PDF Packages. It is recommended that you use the latest version of Adobe Reader.
{% endhint %}


---

# 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.swingsoftware.com/pdf-converter-for-notes/getting-started/pdf-converter-terminology/pdf-package.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.
