Hi all
new setup script is translatable and brings tons of new strings to translate. They currently live in separate language file (as development was separate, it was only reasonable option), but I think we should merge it. Piotr do you have any objections?
I had several reasons for using separate files: - I don't expect seeing setup script fully translated anytime soon, hence it uses separate files - I didn't want to add 29 KB of text which is used usually only once, when installing PMA for the first time
If my reasons aren't a problem for you I can make necessary changes and files can be merged.
Piotr Przybylski a écrit :
I had several reasons for using separate files:
- I don't expect seeing setup script fully translated anytime soon,
hence it uses separate files
- I didn't want to add 29 KB of text which is used usually only once,
when installing PMA for the first time
In fact, at installation time it might be important to reassure first-time users in their own language.
If my reasons aren't a problem for you I can make necessary changes and files can be merged.
Hi,
On Sep 4, 2008, at 8:54 AM, Marc Delisle <Marc.Delisle@cegepsherbrooke.qc.ca
wrote:
Piotr Przybylski a écrit :
I had several reasons for using separate files:
- I don't expect seeing setup script fully translated anytime soon,
hence it uses separate files
- I didn't want to add 29 KB of text which is used usually only once,
when installing PMA for the first time
In fact, at installation time it might be important to reassure first-time users in their own language.
Quite true, i agree that localization is important - but what is the performance cost of loading every time an extra 29KB of language strings that are only rarely used? I don't know - and it could be trivial compared to the hassle of maintaining ./lang and ./scripts/ setup_lang/ seperately. I only propose it in case the extra performance hit is significant, which I doubt.
~Isaac
If my reasons aren't a problem for you I can make necessary changes and files can be merged.
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Isaac Bennetch a écrit :
Hi,
On Sep 4, 2008, at 8:54 AM, Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
Piotr Przybylski a écrit :
I had several reasons for using separate files:
- I don't expect seeing setup script fully translated anytime soon,
hence it uses separate files
- I didn't want to add 29 KB of text which is used usually only once,
when installing PMA for the first time
In fact, at installation time it might be important to reassure first-time users in their own language.
Quite true, i agree that localization is important - but what is the performance cost of loading every time an extra 29KB of language strings that are only rarely used? I don't know - and it could be trivial compared to the hassle of maintaining ./lang and ./scripts/setup_lang/ seperately. I only propose it in case the extra performance hit is significant, which I doubt.
~Isaac
If my reasons aren't a problem for you I can make necessary changes and files can be merged.
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.
Marc
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.
-
Isaac Bennetch -
Marc Delisle -
Michal Čihař -
Piotr Przybylski