Hi
Dne Mon, 15 Sep 2008 18:59:24 +0200 Crack piotrprz@gmail.com napsal(a):
2008/9/4 Michal Čihař michal@cihar.com:
Dne Thu, 04 Sep 2008 11:03:09 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca napsal(a):
I don't believe the cost is significant; besides, the same question could be asked about any page we load (when you are on the Search page you only need those messages) because some are less frequently used that others.
It's also easier to manipulate just one file, for our translators.
I'm also for merging, but the strings should be somehow separated, to allow identification by translators which ones are needed only for setup script.
Then should I prefix all setup script strings with eg. "Setup_" ($strSetup_stringName)?
I think there should be some prefix, so that translators can easily distinguish comments only used in setup. Comments anyone?
Michal Čihař a écrit :
Hi
Dne Mon, 15 Sep 2008 18:59:24 +0200 Crack piotrprz@gmail.com napsal(a):
2008/9/4 Michal Čihař michal@cihar.com:
Dne Thu, 04 Sep 2008 11:03:09 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca napsal(a):
I don't believe the cost is significant; besides, the same question could be asked about any page we load (when you are on the Search page you only need those messages) because some are less frequently used that others.
It's also easier to manipulate just one file, for our translators.
I'm also for merging, but the strings should be somehow separated, to allow identification by translators which ones are needed only for setup script.
Then should I prefix all setup script strings with eg. "Setup_" ($strSetup_stringName)?
I think there should be some prefix, so that translators can easily distinguish comments only used in setup. Comments anyone?
Indeed a prefix is useful. We already have many prefixes, for example $strBinLog. We currently don't use underscores in message names so messages could be named like
$strSetupShowForm = 'Show form';