Special characters problem

RE: Special characters problem

jesusa310 — Fri, 04 Jun 2021 13:37:16 GMT

lesson learnt: hire testers funny enough to use emoticons on their comments :)

RE: Special characters problem

jesusa310 — Fri, 04 Jun 2021 13:36:16 GMT

Ok, it is clear to me now that the encoding WE8ISO8859P1 does not support "€" symbol

https://forums.devart.com/viewtopic.php?t=21974

https://stackoverflow.com/questions/29085485/how-to-store-%E2%82%AC-in-oracle-we8iso8859p1

I think the best solution is to update the encoding settings at the database level.

Thanks for your ideas

RE: Special characters problem

Stefan Helzle — Fri, 04 Jun 2021 12:59:29 GMT

A while ago we had an issue with users entering emojis in the mobile app. By default MySQL can only store 2-byte characters but emojis are 4-byte. This just breaks when storing to DB.

Was discovered in production ...

RE: Special characters problem

jesusa310 — Fri, 04 Jun 2021 12:56:32 GMT

It is interesting that I have just discovered that the problem only happens with the euro € symbol..

RE: Special characters problem

Stefan Helzle — Fri, 04 Jun 2021 12:17:18 GMT

WE8ISO8859P1 only stores 8 bit characters. I suggest to change this to a charset which support unicode.

RE: Special characters problem

jesusa310 — Fri, 04 Jun 2021 11:07:52 GMT

Thanks, removing the symbols is not desired because the users want to see them, so I think is better to substitute them.

However I would prefer to do the configuration at the DB level, as doing it in the code will require to change multiple places.

RE: Special characters problem

gayathris876948 — Fri, 04 Jun 2021 10:54:03 GMT

REGEX would probably work, but you could also use out-of-the-box Appian functions.

The stripwith() function will remove any characters you define as invalid. So if you wanted to specifically remove the some symbols, you can use stripwith() like this:

stripwith(

[Text Here],

"@*^<>+)/("

)