If I try this, the WebParser result is a "bla bla URL is not UTF-8 encoded". If however, while still having the UCS-2 LE BOM encoded file (and the InputSearch variable set to ) I convert it to UTF-8 in Notepad++ (which would turn into ) the WebParser would do its job and display the results properly.SilverAzide wrote: ↑August 4th, 2020, 4:17 pm OK, I need a little assistance with an issue illustrated by this skin but not directly weather.com related.
Can someone try using the location search feature in this skin and try to search for the text ? Take note of the "accented-L" symbol, it's not a latin letter L. The WebParser is returning nothing, and I can't figure out why. If you open your browser and use the exact string that WebParser is using ( ), it is working perfectly. Searching for also works, of course, but that's not the URL that's going out... I tried a custom header of "Accepts-Language: pl-PL", but that didn't help (the header is mentioned in the OSM API docs).
Using the latin "L" works, but that's not what normal users would enter. Is there some behind the scenes Unicode handling going on in the browsers but not in WebParser?
So, my guess is that it's not a WebParser issue, but an encoding one. WebParser is happy to take whatever encoded string and use it in the URL and it will work, but since we use UCS-2 LE BOM in our Rainmeter .INI-s and Nominatim expects a UTF-8 encoded string, issues like these will occur. The solution, in my view, is to find a way to convert the string from UCS-2 LE BOM to UTF-8 when passing it as a parameter in the URL. Another solution is to find some hypothetical Nominatim parameter that would convert whatever encoding we use to a UTF-8 automatically in the URL.