Re: Handling non-translatable charcacters

Yup - that's the one.  Known as "En Dash".

I'll post here what I eventually do.


Jon P
 

> On Feb 10, 2023, at 2:10 PM, Justin Taylor <[email protected]> wrote:
> 
> 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 <[email protected]>
>> 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.
>> 
>> 
>> 
> -- 
> This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
> To post a message email: [email protected]
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/web400
> or email: [email protected]
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/web400.
> 

-- 
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: [email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: [email protected]
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.