# \[IGN-5692\] Tagpaths with åäö not found in Embedded Veiw

**URL:** <https://forum.inductiveautomation.com/t/ign-5692-tagpaths-with-aao-not-found-in-embedded-veiw/56999>\
**Category:** Ignition\
**Created:** [March 9, 2022, 7:14am UTC](https://forum.inductiveautomation.com/t/ign-5692-tagpaths-with-aao-not-found-in-embedded-veiw/56999 "2022-03-09T07:14:55Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [November 2, 2022, 3:59pm UTC](https://forum.inductiveautomation.com/t/ign-5692-tagpaths-with-aao-not-found-in-embedded-veiw/56999/16 "2022-11-02T15:59:55Z")

</div>

This issue hasn't yet been picked up to be worked on.

I had a typo in my earlier sample; you could try `-Dfile.encoding=UTF-8` as a JVM argument to the designer launcher and/or providing the `file.encoding` property as a `wrapper.java.additional` property in the `ignition.conf` file. If the problem is a file encoder being created with default platform encoding somewhere, that would force Java on Windows to use a 'better' charset, which might fix this issue.

---

_[View the full topic](https://forum.inductiveautomation.com/t/ign-5692-tagpaths-with-aao-not-found-in-embedded-veiw/56999)._