×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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 mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
