×
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.
On Fri, Jun 21, 2024 at 7:19 PM Scott Klement
<midrange-l@xxxxxxxxxxxxxxxx> wrote:
Use the http_urlEncode() routine in HTTPAPI.
Really? I'd looked at it (and its various friends) in the source
member, and it appeared that (1) it simply translated EBCDIC, and (2)
it was what HTTPAPI was already using.
The web service in question is Google's geo-coding API. It works just
fine if I send it an address that's directly representable in ASCII.
But even one diacritical, and it's rejected. If I manually
percent-encode the diacritical using the charts at
https://www.w3schools.com/tags/ref_urlencode.ASP
it is accepted if I percent-encode it according to the "UTF-8" column,
but is rejected if I use the "Windows-1252" column (which is as it
should be).
It gets more interesting from there: one of the fields I'm capturing
and parsing in the reply is the "formal address" field, that
(theoretically) is a fully canonical version of the address I sent.
And by the time the reply gets translated back into EBCDIC, the
diacritical (specifically the lowercase n-tilde in "La Cañada
Flintridge") comes back as two unrelated characters.
--
JHHL
midrange.com
