> 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/tips-miscellaneous/pdf-filename-unicode-compliance-tips.md).

# PDF filename Unicode compliance tips

Swing PDF Converter supports Unicode compliant file naming from version 5.6 on MS Windows.

This compliance includes toolbar icon UI, LotusScript API and Java API.

If computed PDF file names are not readable on your operating system (shown as rectangles, question marks or any other generic symbol) like on image below then most common reason for this is wrong Windows localization.

<img src="https://3331713008-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MlCAurE6RSGoCmtmAET%2F-MlFkt17oqAZqykkfGto%2F-MlFlGmiTe7YBdEI5dxa%2Fno_Font.png?alt=media&amp;token=17760872-5029-40d4-947c-0bc18a3aebae" alt="" data-size="line"> < - Far eastern symbols shown on European Windows localization.&#x20;

Also, bad localization settings can cause same symbols shown in Lotus Notes and Windows application fields and forms.

If you for example work in USA and receive a Notes Database from Japan, then symbols in Japanese Database might not be visible on your computer.

Localization should be changed to Japanese, this will force MS Windows to install all required fonts and resources for Japanese language.

Once this is done localization can be safely reverted to US without loss of Japanese resources.

&#x20;[Here's the link for help page that describes how to change localization.](https://www.tenforums.com/tutorials/68106-change-country-region-home-location-windows-10-a.html)


---

# 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/tips-miscellaneous/pdf-filename-unicode-compliance-tips.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.