Google Weather (JD Edition) by Jelle Dekkers (Original by fivetwofoureight)

[JelleDekkers]

So I came across this skin on DeviantArt, and I thought about making an updated version, seeing how the comment section is complaining about the skin not working anymore. So, naturally, I did. Aside from the layout (it was quite big) and weather provider issues of the original, I wanted to have more than just two colors for the skin. So with this one, you can have any color and the skin will choose an appropriate text color based on that. Hovering over the forecast temperature will show you the minimum temperature for that day, by the way. The weather provider used here is Weather.com's JSON API and Nominatim to determine the coordinates for the given location.

Change log

2021-01-29

• Updated the header image.
• Fixed the minimum version requirement.

2020-12-05

• Updated the weather parser to include the option to choose 12/24-hour formats for the sunrise/set and moonrise/set times. Not that it actually matters in this skin, but I like to keep things updated.

2020-12-02

• Changed the file encoding from ANSI to UCS-2 LE BOM because someone reported having issues with the degree symbols.
• Fixed a (pretty severe) issue in the color system.

Credits

• Ben Emrick for the preview background.
• fivetwofoureight for the original and for giving me permission to do this.

[ms310]

For me the degree symbols don't appear.

2020-12-02_10h35_55.png

[jsmorley]

While it's fine for me, I can't promise that it will work everywhere in the world. The skin .ini file should really be encoded as UTF-16 LE, and not ANSI. All Rainmeter skin .ini and .inc files should really be encoded as UTF-16 LE Unicode.

[balala]

Works here as well (Eastern Europe).

[JelleDekkers]

For me the degree symbols don't appear.

2020-12-02_10h35_55.png

I've never seen this happen before, but I'll fix it.

[balala]

I've never seen this happen before, but I'll fix it.

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.

[JelleDekkers]

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.

I've just updated all of my (weather) skins to use UCS-2 LE BOM

[ms310]

I've just updated all of my (weather) skins to use UCS-2 LE BOM

Thank you!