> 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/troubleshooting/general-issues/thai-symbols-not-shown-in-pdf-document.md).

# Thai symbols not shown in PDF document

To convert documents with Thai symbols one of the required fonts must be installed on the system

When converting documents with Thai symbols, SWING Seascape checks if **Angsana New** font is installed on system. Font *Angsana New* is the most common Thai font on Microsoft Windows.

If *Angsana New* cannot be found, SWING Seascape checks for **Garuda** font, which can be freely downloaded from [the web](http://slice-of-thai.com/fonts/Garuda.ttf).

Finally, if both fonts are not present, SWING Seascape will look for **Arial Unicode MS**.

Follow these steps to install downloaded fonts:

* Download the font to your computer
* If the font is compressed, unzip it
* In Windows Explorer right-click on the font file and select **Install for all users**

![](https://3331713008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MlCAurE6RSGoCmtmAET%2Fuploads%2FJZhUMuwDaktM6V4VY4J2%2Fimage.png?alt=media\&token=ca12d4f4-fe54-4135-9d68-af63bca4675a)

* Close Notes client and all other Notes applications (Designer, Administrator, etc.) and then start it again

{% hint style="info" %}
It is important that font is **installed for all users**. If the font is installed just for the current user Windows will be able to use it but it won't be available for Seascape
{% 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/troubleshooting/general-issues/thai-symbols-not-shown-in-pdf-document.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.