Intention;;Pul53dr1v3r;; I planned to use it for "customized language" option. So when someone enters his language code, for example es-ES, the name (Variable) at the same time changes the file name suffix, link language (Link=https://weather.com/#Num#/weather/today/l/
) and some option in measures. All at once. And if (sb)somebody make a mistake entering the code, it shouldn't make a mess and stop him to enter a new one etc.
It seems that your method could be simplified if it's main purpose is to utilize different variables, measures, and meters to support languages.
To start, renaming a file will not allow you to use those item in your skin immediately; you MUST refresh the skin to use the renamed file.
Since you need to refresh after an end user selects his language (or you rename a file or you use !WriteKeyValue), why not just write a new #language# variable, and use "@includeLanguage=Lang#Language#.inc" in your skin. That file will include all the variables, measures and meters to support the selected language.
How does your end user know that he should enter a certain 'number' for his language?
Do you have a reference chart showing number for a language?
To me it is easler just to offer the available languages in a meter, that when clicked, sets the 'language' variable and refreshes.
Relying on the end user to manually enter a value and hope they don't enter something that crashes the skin seems like asking for trouble.
There are a number of skins that offer translated version, for example see Modules
by Sephirotess, they may help you achieve translations.
Without seeing your entire skin with language options you want to implement, it is not possible to give you a solution.