# Is this an encoding problem? **URL:** \ **Category:** Ignition\ **Created:** [November 23, 2021, 1:11am UTC](https://forum.inductiveautomation.com/t/is-this-an-encoding-problem/53370 "2021-11-23T01:11:58Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![wangjun\_ming\_1996](https://avatars.discourse-cdn.com/v4/letter/w/ee59a6/32.png) [@wangjun\_ming\_1996](https://forum.inductiveautomation.com/u/wangjun_ming_1996)\ **Post date:** [November 23, 2021, 1:11am UTC](https://forum.inductiveautomation.com/t/is-this-an-encoding-problem/53370/1 "2021-11-23T01:11:58Z")
I use another software to write python script and copy to Ignition. Then Ignition prompt Red wavy line. I don’t know what’s going on. Is this an encoding problem? I use UTF-8 encoding now. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/1/2152769aae3365f1367927895a8dfe06f67370fb.png) ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [November 23, 2021, 4:11am UTC](https://forum.inductiveautomation.com/t/is-this-an-encoding-problem/53370/2 "2021-11-23T04:11:23Z")
> [@wangjun\_ming\_1996](#): > > I use another software to write python script and copy to Ignition. How do you do this? If it's a file copy, try using UTF-8 without BOM (I suspect there is a BOM there that you can't see.) Also, clicking on the red marker on the right will tell you the error. ---
**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:** [November 23, 2021, 5:13pm UTC](https://forum.inductiveautomation.com/t/is-this-an-encoding-problem/53370/3 "2021-11-23T17:13:32Z")
Very unlikely that it’s an encoding problem. More likely, our syntax checker is looking for whitespace after the first #. When it doesn’t find whitespace, it’s flagging it as a problem even though it will run just fine. ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [November 23, 2021, 5:18pm UTC](https://forum.inductiveautomation.com/t/is-this-an-encoding-problem/53370/4 "2021-11-23T17:18:21Z")
Just typing it in doesn’t show an error, nor copy/paste when I was taking a quick look last night. It’s what made me think of the BOM possibility. ---
**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:** [November 23, 2021, 5:39pm UTC](https://forum.inductiveautomation.com/t/is-this-an-encoding-problem/53370/5 "2021-11-23T17:39:49Z")
Thanks Jordan, just came here to say we tested it here as well and came to the same conclusion. What threw me is this isn’t what I typically see with encoding issues, but an invisible character makes total sense. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [November 23, 2021, 5:47pm UTC](https://forum.inductiveautomation.com/t/is-this-an-encoding-problem/53370/6 "2021-11-23T17:47:44Z")
FWIW, y’all should check out python’s latest guidance for dealing with “Trojan Source” security issues: > **[PEP 672 -- Unicode-related Security Considerations for Python](https://www.python.org/dev/peps/pep-0672/)** > > The official home of the Python Programming Language More info here: > **[Trojan Source: tricks (no treats) with Unicode \[LWN.net\]](https://lwn.net/Articles/874951/)** > > A new security vulnerability that was disclosed > on November 1 has some interesting properties. "Trojan Source", as it has been > dubbed, is effectively an attack on human perceptions, especially as they > are filtered through the tools used for...