> 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/how-to/how-to-enable-international-characters.md).

# How to enable international characters

If international characters (Cyrillic, Chinese, Indian, Japanese, etc..) are not shown in converted PDF document it is most probably because international character support is not enabled.

There are two ways to enable this option depending on the type of PDF Converter deployment: 

## PDF toolbar icon

* Open Swing PDF Converter database in Lotus Notes
* From the main menu select "PDF Settings"

![](https://3331713008-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MlCAurE6RSGoCmtmAET%2F-MlE_KiSJhpL3zHYAuvx%2F-MlE_sP-WVUMvgWgF9GI%2Fimage.png?alt=media\&token=8df4019a-9491-4d4a-8083-4aaf4b68a1b3)

* Open the desired Settings document
* In the "PDF Settings" document select "Fonts" tab and change the "Embed all fonts" setting to "Yes"

![](https://3331713008-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MlCAurE6RSGoCmtmAET%2F-MlE_KiSJhpL3zHYAuvx%2F-MlE_yel-TKzCYSyRtaH%2Fimage.png?alt=media\&token=d4581302-0679-4b13-bbfb-0a203e79796b)

* Save and close the Settings document

## API

In **LotusScript API** use setting:

`swPDF.PDFSettings.EnableFontEmbedding = True`

In **Java API** use setting:

`SwPDFSettings.setEnableFontEmbedding(boolean)`

## Asian/Arabic fonts not embedded to pdf document 

Please read the following article in the Troubleshooting section:

{% content-ref url="/pages/-MlFTEJv7\_jVD70H6wSZ" %}
[PDF fonts not embedded for Asian/Arabic documents](/pdf-converter-for-notes/troubleshooting/general-issues/pdf-fonts-not-embedded-for-asian-arabic-documents.md)
{% endcontent-ref %}


---

# 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/how-to/how-to-enable-international-characters.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.