Hi, in which situation can a user see this message?
Hi
Dne Tue, 26 Apr 2011 07:58:29 -0400 Marc Delisle marc@infomarc.info napsal(a):
in which situation can a user see this message?
It is shown on main page when translation is less than 80% complete (or whatever is set in $cfg['TranslationWarningThreshold']).
Michal Čihař a écrit :
Hi
Dne Tue, 26 Apr 2011 07:58:29 -0400 Marc Delisle marc@infomarc.info napsal(a):
in which situation can a user see this message?
It is shown on main page when translation is less than 80% complete (or whatever is set in $cfg['TranslationWarningThreshold']).
I cannot make the message appear because incomplete translations are not in the drop-down list of languages (now that libraries/language_stats.inc.php is no longer broken).
Hi
Dne Tue, 26 Apr 2011 08:28:39 -0400 Marc Delisle marc@infomarc.info napsal(a):
Michal Čihař a écrit :
Hi
Dne Tue, 26 Apr 2011 07:58:29 -0400 Marc Delisle marc@infomarc.info napsal(a):
in which situation can a user see this message?
It is shown on main page when translation is less than 80% complete (or whatever is set in $cfg['TranslationWarningThreshold']).
I cannot make the message appear because incomplete translations are not in the drop-down list of languages (now that libraries/language_stats.inc.php is no longer broken).
Translations bellow 50% percent are dropped, translations bellow 80% show warnings. So you need to choose something what fits between 50-80 percent. For example Finnish.
These thresholds were really just wild guesses, so I'm open to any adjustments.
PS: You can see the warning on demo server as well, but translations are not removed there, so all bellow 80% show it.
Michal Čihař a écrit :
Hi
Dne Tue, 26 Apr 2011 08:28:39 -0400 Marc Delisle marc@infomarc.info napsal(a):
Michal Čihař a écrit :
Hi
Dne Tue, 26 Apr 2011 07:58:29 -0400 Marc Delisle marc@infomarc.info napsal(a):
in which situation can a user see this message?
It is shown on main page when translation is less than 80% complete (or whatever is set in $cfg['TranslationWarningThreshold']).
I cannot make the message appear because incomplete translations are not in the drop-down list of languages (now that libraries/language_stats.inc.php is no longer broken).
Translations bellow 50% percent are dropped, translations bellow 80% show warnings. So you need to choose something what fits between 50-80 percent. For example Finnish.
OK I understand now :) I was thinking only about the dropping threshold.
These thresholds were really just wild guesses, so I'm open to any adjustments.
PS: You can see the warning on demo server as well, but translations are not removed there, so all bellow 80% show it.
On Tue, Apr 26, 2011 at 2:37 PM, Michal Čihař michal@cihar.com wrote:
Hi
Dne Tue, 26 Apr 2011 08:28:39 -0400 Marc Delisle marc@infomarc.info napsal(a):
Michal Čihař a écrit :
Hi
Dne Tue, 26 Apr 2011 07:58:29 -0400 Marc Delisle marc@infomarc.info napsal(a):
in which situation can a user see this message?
It is shown on main page when translation is less than 80% complete (or whatever is set in $cfg['TranslationWarningThreshold']).
I cannot make the message appear because incomplete translations are not in the drop-down list of languages (now that libraries/language_stats.inc.php is no longer broken).
Translations bellow 50% percent are dropped, translations bellow 80% show warnings. So you need to choose something what fits between 50-80 percent. For example Finnish.
These thresholds were really just wild guesses, so I'm open to any adjustments.
I would set the minimum requirement to 30%. Untranslated strings default to english anyway, right? If the user is warned about it's incompletion he won't be negatively surprised. Also, an average user that just needs simple table management probably needs only 10-20% of the translation anyway (just guessing).
I still think that allowing the use of (very) uncompleted translation would more likely get users involved in the translation project.
PS: You can see the warning on demo server as well, but translations are not removed there, so all bellow 80% show it.
-- Michal Čihař | http://cihar.com | http://blog.cihar.com
WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Hi
Dne Tue, 26 Apr 2011 15:19:21 +0200 Tyron Madlener tyronx@gmail.com napsal(a):
I would set the minimum requirement to 30%. Untranslated strings default to english anyway, right? If the user is warned about it's incompletion he won't be negatively surprised. Also, an average user that just needs simple table management probably needs only 10-20% of the translation anyway (just guessing).
Yes, having translated 10% top used strings would be good enough for many users. However we don't have any such metric, so we can just base on all strings.
Anyway I plan to lower the ratio for final release, the 50% percent was set intentionally too strict for rc to see if somebody will complain about dropped language. I think 30% will be reasonable (it would add 20 more translations compared to 50%).
I still think that allowing the use of (very) uncompleted translation would more likely get users involved in the translation project.
Indeed, that's why the warning about incomplete translation has been added.
Michal Čihař a écrit :
Hi
Dne Tue, 26 Apr 2011 15:19:21 +0200 Tyron Madlener tyronx@gmail.com napsal(a):
I would set the minimum requirement to 30%. Untranslated strings default to english anyway, right? If the user is warned about it's incompletion he won't be negatively surprised. Also, an average user that just needs simple table management probably needs only 10-20% of the translation anyway (just guessing).
Yes, having translated 10% top used strings would be good enough for many users. However we don't have any such metric, so we can just base on all strings.
Anyway I plan to lower the ratio for final release, the 50% percent was set intentionally too strict for rc to see if somebody will complain about dropped language. I think 30% will be reasonable (it would add 20 more translations compared to 50%).
We'll see the effect of this, starting with 3.4.0-rc2 which will be released in a few hours. Due to a bug, there were no dropped language files in 3.4.0-rc1.
I still think that allowing the use of (very) uncompleted translation would more likely get users involved in the translation project.
Indeed, that's why the warning about incomplete translation has been added.
-
Marc Delisle -
Michal Čihař -
Tyron Madlener