Rainmeter Forums

Hi, experts!

Does anyone has experinced such a behavior like depicted in the screenshot: There are definitely no such signs in the ini-file (coding is UCS-2 Little Endian);

i'm using notepadd++ and the latest beta 4.1.0 r2917

Please pack and upload the whole Ikarus1969 config. Just to check...

The whole config contains too much skins, sorry.

The skin-ini ("clock.ini") does not have any asian characters in it.

Or do you have any specific suspicion?

zip up clock.ini and attach it.

I don't see anything right off. I would go through your suite and ensure that all .ini AND .inc files (if you have any) are encoded as UCS-2 little Endian. This is certainly an encoding issue of some kind.

Since your Windows is likely using a German locale, I think any files encoded as ANSI are going to give Rainmeter some issues, due to the differences in the Extended ASCII character set with a German codepage.

No, it's something about that particular skin...

I get this in the log:

Invalid bang: !Se팜ᚽݡ耀iable (Clock\Clock.ini)

So I can't spot it right off, but there is something about that skin that Rainmeter hates. Or at least the About / Log panel hates.

Try this for me.

Open the clock.ini file in Notepad++.

Use Edit / Select all to select all text

Use Encoding, and select Change to ANSI

Save the file.

Use Encoding, and select Change to UCS-2 LE BOM

Save the file.

Now load it in Rainmeter. Do you get the same issue?

I did what you've suggested and don't get errors for this skin: Whatever it was, i hope it doesn't come back.

Thank you for having a look at it!

ikarus1969 wrote:I did what you've suggested and don't get errors for this skin:
Screenshot Rainmeter Dialog.png

Whatever it was, i hope it doesn't come back.

Thank you for having a look at it!

I suspect that that skin was at some point encoded as ANSI, and when you put the German characters in it, those were put in using the Extended ASCII character set (which is what ANSI is more or less). Then you encoded the file as UCS-2 LE BOM, but those characters were left in some kind of weird state. I think the key is to select all text when you use "Change to..." from Encoding.

You might want to do this same exercise with your other skins to be safe.