# \[BUG\] Hidden unicode characters in script editors

**URL:** <https://forum.inductiveautomation.com/t/bug-hidden-unicode-characters-in-script-editors/64981>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [October 9, 2022, 1:39am UTC](https://forum.inductiveautomation.com/t/bug-hidden-unicode-characters-in-script-editors/64981 "2022-10-09T01:39:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\
**Post date:** [October 9, 2022, 1:39am UTC](https://forum.inductiveautomation.com/t/bug-hidden-unicode-characters-in-script-editors/64981/1 "2022-10-09T01:39:55Z")

</div>

Looks like this is a bug in the new script editor (not sure if it exists in the old one) but there are certain unicode characters that don't show up, and can cause errors in compilation:

### Example \u200b

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/7/b7f76f249a8c153be7a0d1b55a355c065e4d1b3a.png)

I know that VSCode has a fix in place for these invisible characters that highlights them, but thought it might be worth noting incase others had the same issue. I actually got this hidden character from copying out of the javadocs in [this page](https://files.inductiveautomation.com/sdk/javadoc/ignition81/8.1.20/com/inductiveautomation/ignition/common/JsonUtilities.html).

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/c/fc224137ca577a4f944c61a6a0b34457cd1d8e48.png)

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/b/2b3865a35d304ef761dcce82ba0e4839e62bb879.png)

---

<div class="post-metadata">

**Author:** ![KathyApplebaum](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kathyapplebaum/32/7261_2.png) [@KathyApplebaum](https://forum.inductiveautomation.com/u/KathyApplebaum)\
**Post date:** [October 10, 2022, 2:58pm UTC](https://forum.inductiveautomation.com/t/bug-hidden-unicode-characters-in-script-editors/64981/2 "2022-10-10T14:58:47Z")

</div>

> Looks like this is a bug in the new script editor (not sure if it exists in the old one) but there are certain unicode characters that don't show up

To be fair, that's a zero width space, so it shouldn't show up. But we can definitely get it out of the docs for future versions.

If this winds up being a problem with other copy/pasted text, it might be worth a post at [ideas.inductiveautomation.com](http://ideas.inductiveautomation.com) to see if we can highlight those.

---

<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:** [October 10, 2022, 3:25pm UTC](https://forum.inductiveautomation.com/t/bug-hidden-unicode-characters-in-script-editors/64981/3 "2022-10-10T15:25:07Z")

</div>

On the plus side, it looks like Java 17 will remove those zero width joiners: [[JDK-8266779] Use \<wbr\> instead of ZERO\_WIDTH\_SPACE - Java Bug System](https://bugs.openjdk.org/browse/JDK-8266779)

In the interim, yeah, an ideas post would be good to gauge how useful this would be. There aren't that many non-displayable characters you can possibly enter in a Swing text area, so hopefully it's not that common.

---

<div class="post-metadata">

**Author:** ![KathyApplebaum](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kathyapplebaum/32/7261_2.png) [@KathyApplebaum](https://forum.inductiveautomation.com/u/KathyApplebaum)\
**Post date:** [October 10, 2022, 5:18pm UTC](https://forum.inductiveautomation.com/t/bug-hidden-unicode-characters-in-script-editors/64981/4 "2022-10-10T17:18:02Z")

</div>

> [@paul-griffith](#):
>
> it looks like Java 17 will remove those zero width joiners

Oh, nice, I'll close our ticket then. We're moving to Java 17 as soon as we can anyways.
