# An encode bug in designer

**URL:** <https://forum.inductiveautomation.com/t/an-encode-bug-in-designer/59187>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [May 4, 2022, 3:20am UTC](https://forum.inductiveautomation.com/t/an-encode-bug-in-designer/59187 "2022-05-04T03:20:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [May 4, 2022, 3:44pm UTC](https://forum.inductiveautomation.com/t/an-encode-bug-in-designer/59187/2 "2022-05-04T15:44:46Z")

</div>

This looks like it's probably the same bug described in this other post:

> [@\[BUG-6009\]Bug unicode text displaying incorrectly when embedded in another view](https://forum.inductiveautomation.com/t/bug-unicode-text-displaying-incorrectly-when-embedded-in-another-view/58750):
>
> Version 8.1.15 When I create a text object and create a binding with unicode characters it looks as I would expect [image] binding: return u'({}{})'.format(u'▼' if value \< 0 else u'▲', abs(value)) When I embed that view in another view it seems that the unicode text gets converted to non-unicode [image] but… this only happens in the designer. It looks like I would expect in a client. I spent more time than I’m willing to admit trying to “fix it” before realizing it worked like it should …

I'm working with @plo to get an issue created in our system to track this bug.

---

_[View the full topic](https://forum.inductiveautomation.com/t/an-encode-bug-in-designer/59187)._