
Check it out on GitHub!
This probably is caused by what jsmorley described in his above reply (the wrong encoding of files).JelleDekkers wrote: ↑December 2nd, 2020, 9:01 am I've never seen this happen before, but I'll fix it.
I've just updated all of my (weather) skins to use UCS-2 LE BOMbalala wrote: ↑December 2nd, 2020, 9:42 am This probably is caused by what jsmorley described in his above reply (the wrong encoding of files).
There is an extremely easy solution. Beside reencoding the files, replace the ° signs in the Substitute options of WebParser measures of both files, @Resources\WeatherParser.inc and @Resources\WeatherParserDaily.inc, with [\x00B0]. So for instance the Substitute="#Substitute#", "(.+)":"\1°", "":"--" option of the [mCurrentTemperature] measure of the @Resources\WeatherParser.inc file should be replaced by Substitute="#Substitute#", "(.+)":"\1[\x00B0]", "":"--".
Probably the reencoding should be enough, however I still suggest to replace the signs, as described above.
Thank you!JelleDekkers wrote: ↑December 2nd, 2020, 9:45 am I've just updated all of my (weather) skins to use UCS-2 LE BOM![]()
No, the skin doesn't work for me either. Probably the author, JelleDekkers will be needed here.iwantdrconnors wrote: ↑October 26th, 2021, 11:08 am Skin does not want to work anymore. Don't know if it is because Sweden (where I live) have changed weather system (warning system).