Some time ago there was a discussion about using variablenames in languagefiles. Since then, I saw those names appear between "#".
In the current helptext I see the $ appear again, but it's escaped out, for instance $pgv_lang[login_aut] appears in the helpfile as \$pgv_lang[login_aut] and shows on the screen as text.
I understand the editor puts the \ in front.
So.... how can I use variables in helptext now?
Boudewijn
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
Some time ago there was a discussion about using variablenames in languagefiles. Since then, I saw those names appear between "#".
In the current helptext I see the $ appear again, but it's escaped out, for instance $pgv_lang[login_aut] appears in the helpfile as \$pgv_lang[login_aut] and shows on the screen as text.
I understand the editor puts the \ in front.
So.... how can I use variables in helptext now?
Boudewijn
This is a real problem :-(
For al developers... Please keep in your mind:
If you want to use a variable inside a lang-message do the following:
$pgv_lang["xxx"] = "Message and the $var I want to use inside it";
should be:
$pgv_lang["xxx"] = "Message and the #VAR# I want to use inside it";
And inside the scipt where $pgv_lang["xxx"] is used:
Instead of
print $pgv_lang["xxx"];
use:
print str_replace("#VAR#", $var, $pgv_lang["xxx"]);
Else we get probs with the language editor :-(
bye, Kurt
Hi people,
The problems with the $ and # are solved now.
In the, already translated, files I have replaced the $ by #.
Botak helped me to change the code.
So we have a new help_text.php.
To get it working you also have to replace the functions_print.php.
I will put them in the patch section.
The files are also in the cvs.
*Jans*