| OTM 4.5 not handling Non Ascii Characters
We are running on OTM 4.5 and our Python scripts crash whenever we receive a non-ascii character in an order file. We have been able to replace the non-ascii characters with a similar ascii character but this only works for a one to one replacement. We are also receiving ½ characters (U+00BD), which crash the python scripts, and are unable to replace these with a single character. Has anyone run across this issue and, if so, how did you resolve it?
Thanks! |