Convert lowercase to uppercase

[jsmorley]

I think there is no (good) solution for this?

Nothing that will let you have your cake and allow you to eat it as well. You either have to convert to upper case and use string.gsub() which doesn't care about the byte-width of characters, or use my first approach which will maintain the string case as is, but will likely fail on Unicode in the @Resources path.

Lua is fine with Unicode, with the exception of any functions that depend on string "length" or character "position". A single mutli-byte Unicode character is seen as two characters by Lua. Lua lives in an 8-bit world...

[balala]

if you store the path variables in the .inc file in upper case, it will work fine, unless you are "displaying" the path in the skin, in which case converting to upper case might not look great.

Yes, but still will work.

[balala]

Lua lives in an 8-bit world...

8-bit? Didn't evolve?

[balala]

And finally it seems I found the solution, even without using a lua script.
The idea is to use jsmorley's very simple substitution. But that substitution doesn't work, due to the reserved characters, contained into the path of the file (the Path variable). So, I thought I should have to replace the \ characters to something not reserved (like -), then make jsmorley's substitution (Substitute="(?i)#@#":"#*@*#") and finally convert back the eventually remaining - characters, to \:

Code: Select all

[Rainmeter]
Update=-1

[Variables]
Path=

[MeasureString]
Measure=String
String=#Path#
Substitute="\":"-"

[MeasureResources]
Measure=String
String=#@#
Substitute="\":"-"

[MeasureString2]
Measure=String
String=[MeasureString]
RegExpSubstitute=1
Substitute="(?i)[MeasureResources]":"#*@*#","-":"\"

jsmorley (or/and obviously anyone else), could you please test this solution, to see if it works for you as well? You have to add the Path variable, which I didn't post. [MeasureString2] should have to return the path given by the Path variable, appropriately (using or not using the #@# variable, depending on what path did you give).

[jsmorley]

Seems ok. I would probably not use a character like "-" that is valid in a path or file name, but maybe "!" which isn't. Just be sure whatever you use isn't a reserved character in regular expression.

[balala]

Seems ok. I would probably not use a character like "-" that is valid in a path or file name, but maybe "!" which isn't. Just be sure whatever you use isn't a reserved character in regular expression.

Yes, you're right, however the exclamation mark (!) is a valid character in file names. But this is just a small detail, I'll find something to use. The question was if this approach works. Thanks for testing it.

And one more big thanks for all the help. Your replies was extremely useful, I wouldn't got it to work, without your help. So, thank again...

[jsmorley]

Perhaps "]]". "]" is not reserved in PCRE regular expression, and while I suppose possible in a path, the double close brackets is certainly not likely. Note that "[" IS reserved.

[balala]

Perhaps "]]". "]" is not reserved in PCRE regular expression, and while I suppose possible in a path, the double close brackets is certainly not likely. Note that "[" IS reserved.

Yes, I also thought to something longer than one single character. Will have to test it later, but I think "]]" is a good idea. Thanks again.

[jsmorley]

Yes, I also thought to something longer than one single character. Will have to test it later, but I think "]]" is a good idea. Thanks again.

Actually, I think ">" or "<" will do. Those are not reserved in regular expression, and not allowed in Windows path or file names, since in DOS they mean "redirect".

You must stay away from [ \ ^ $ . | ? * + ( )

[balala]

Actually, I think ">" or "<" will do. Those are not reserved in regular expression, and not allowed in Windows path or file names, since in DOS they mean "redirect".

You must stay away from [ \ ^ $ . | ? * + ( )

Yes, probably ">" and "<" are good ideas.
About the reserved characters, are the "{" and "}" also reserved, beside those listed by you?