Yes, the way it works is that when any option value is evaluated, it first gets the string value, then throws away any starting and ending quotes. In general, you never need to put quotes on any string values in options. However, leading and trailing spaces and/or tabs in option values are always ignored, unless they are clearly defined as a part of the string value, by enclosing them in quotes.krakoukas wrote: ↑August 10th, 2019, 12:58 pm Hi Balala
I'm doing such things because, sometimes in particular, especially during translations, I need white spaces. Let's have a example :
"Volume" in french becomes " Size" with white spaces
Code: Select all
SizeFR = "Volume" SizeENG = " Size" Size=[#Size[#Language]] SpeedFR = "Vitesse" SpeedENG = "Speed" Speed=[#Speed[#Language]] ClientsFR = "Clients" ClientsENG = " Clients" Clients=[#Clients[#Language]] RatioFR = " Ratio" RatioENG = "Ratio" Ratio=[#Ratio[#Language]]
So:
Code: Select all
[Variables]
myText= Some Text
Code: Select all
[Variables]
myText=" Some Text"
Just to ensure that the whole "quotes" thing is as confusing as possible...
It works this way so that when folks want to format their code with "white space", like
Code: Select all
FontSize = 12
FontColor = 255,255,255,255
The trailing spaces on the option name and the leading spaces on the option value are not taken into account and cause problems. Rainmeter in general ignores leading and trailing spaces and tabs in options.