Azona wrote: ↑February 16th, 2022, 2:16 pm
So i'm user of a skin and that have not been updated and sadly propely wont get updated any time soon as been more then 7 years. I got fonts linked but I gues need to edit somewhere to use them? I dont see any fonttyp in skins when editing.
Active Colors wrote: ↑February 17th, 2022, 4:11 pmI have checked the skin files and they are encoded with ANSI. You need to change the encoding of the file(s) to Unicode (sometimes named as UTF-16 LE or UTF-16-LE BOM or UCS-2 Little Endian).
This, followed by editing the sign in the skin after conversion, would work if the sign comes from the skin itself. If it comes from an online source, the conversion of the files won't be enough without font adjustment, IMHO - correct me if I'm wrong. You probably checked the skin and made sure that's all it takes though, I was just saying...
balala wrote: ↑February 17th, 2022, 6:50 pmSee the missing last e. But in fact this has no importance at all, since even if written correctly, a FontType option is invalid in a Rainmeter code.
Yes, I noticed the missing e, but skipped orthography related in favor of functionality related observations, as you already pointed out. Rainmeter will handle the former in its own way, either by ignoring the wrongly typed option or throwing an error.
Azona wrote: ↑February 16th, 2022, 9:18 am
I think sins last update I notice my °C lookde weird it had Â in front of it this was never issue before. so it looked like this Â°C instead of °C
Let's add one more: the best is to use the UTF-16 LE encoding, as said by jsmorley in his first reply, however even using UTF-8 or ANSI encoding, you can get the degree character if in the Text option you're using not °, but [\x00B0]. For instance the Text=%1[\x00B0]C option returns the proper degree symbol even on a file with UTF-8 encoding.