Re: Handling non-translatable charcacters

[Justin Taylor <jtaylor.0ab@xxxxxxxxx>]

Is that the %E2%80%93 character?  I got burned by that this week and
haven't found a good solution yet.

Thanks


date: Thu, 9 Feb 2023 16:59:15 -0500
> from: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
> subject: [WEB400] Handling non-translatable charcacters
>
> Has anyone come up with an easy way of handling characters such as the
> "elongated" hyphen character so beloved by Microsoft?
>
> Every so often the JSON payload that I pull from a web service includes
> characters like this (assumedly copy/pasted from a Word doc) and it causes
> the DATA-INTO (for example) to fail.  I can think of a number of possible
> ways to handle this but hate reinventing the wheel and I can't believe I'm
> the first to encounter it.
>
> Changing the target fields to UTF-8 etc. to accommodate this is just not
> an option.
>
> Is anyone handling this?
>
>
> Jon P.