App restores file encoding from history
Posted: 07.08.2026 10:51
I've been using Rainmeter skins for years, some time ago, I created one that uses WebParser to fetch info from sites. I use this primarily to check sites for app updates. Rainmeter downloads a WebParserDump file, essentially the web site source. I then use basic regexp to get the required info and perform checks against saved version against latest version. Works well for just about any basic html site.
I recently added Python site (https://www.python.org/downloads/windows/) and found the file encoding to be wrong, CT shows encoding is cp1252 and all I am getting is gibberish, no matter how the file is opened, ie, Hex, Text, Binary, Edit Anyway. Changing the encoding is doing nothing. According to the Rainmeter forum, this is an editor issue, topic is here. The first post shows screenshots displaying the problem.
I am hoping this can be resolved as it is concerning that encodings can be remembered across files that have been deleted!
Thanks for your help.
I recently added Python site (https://www.python.org/downloads/windows/) and found the file encoding to be wrong, CT shows encoding is cp1252 and all I am getting is gibberish, no matter how the file is opened, ie, Hex, Text, Binary, Edit Anyway. Changing the encoding is doing nothing. According to the Rainmeter forum, this is an editor issue, topic is here. The first post shows screenshots displaying the problem.
So this means that CT is assigning this cp1252 encoding for some reason. But what is worse, is that deleting the file, then performing Debug=2 to download a different site, one I know works fine, then also assigns the same cp1252 encoding to the newly created WebParser.txt file, which it shouldn't do.Quote from JSMorley on Rainmeter forum:
WebParser with Debug=2 will read the site, open an empty WebPaserDump.txt file, and uhm... dump the site contents into it. WebParser doesn't try to set any encoding on WebParserDump.txt, it will be seen by editors as ANSI if it contains only ANSI characters and will be seen by editors as UTF-8 w/o BOM otherwise.
I am hoping this can be resolved as it is concerning that encodings can be remembered across files that have been deleted!
Thanks for your help.