In most files language strings are being included directly with the __() function, however in server_status.php in the first lines of code are a huge amount of variables being set to the language strings, that are later used. Like those:
$strShowStatusDelayed_writesDescr = __('The number of INSERT DELAYED rows written.'); $strShowStatusFlush_commandsDescr = __('The number of executed FLUSH statements.'); $strShowStatusHandler_commitDescr = __('The number of internal COMMIT statements.');
Does that have any particular reason?
Le 2011-05-15 05:25, Tyron Madlener a écrit :
In most files language strings are being included directly with the __() function, however in server_status.php in the first lines of code are a huge amount of variables being set to the language strings, that are later used. Like those:
$strShowStatusDelayed_writesDescr = __('The number of INSERT DELAYED rows written.'); $strShowStatusFlush_commandsDescr = __('The number of executed FLUSH statements.'); $strShowStatusHandler_commitDescr = __('The number of internal COMMIT statements.');
Does that have any particular reason?
Yes. The current logic builds the messages using the message names:
if (isset($GLOBALS['strShowStatus' . $name . 'Descr'])) { echo $GLOBALS['strShowStatus' . $name . 'Descr']; }
On Sun, May 15, 2011 at 1:41 PM, Marc Delisle marc@infomarc.info wrote:
Le 2011-05-15 05:25, Tyron Madlener a écrit :
In most files language strings are being included directly with the __() function, however in server_status.php in the first lines of code are a huge amount of variables being set to the language strings, that are later used. Like those:
$strShowStatusDelayed_writesDescr = __('The number of INSERT DELAYED rows written.'); $strShowStatusFlush_commandsDescr = __('The number of executed FLUSH statements.'); $strShowStatusHandler_commitDescr = __('The number of internal COMMIT statements.');
Does that have any particular reason?
Yes. The current logic builds the messages using the message names:
if (isset($GLOBALS['strShowStatus' . $name . 'Descr'])) { echo $GLOBALS['strShowStatus' . $name . 'Descr']; }
Oh, I see. Thanks!
-- Marc Delisle http://infomarc.info
Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Another question: If I remove or alter an existing language string do I have to do anything or does the pootle system automatically recognizes any changes?
On Sun, May 15, 2011 at 2:28 PM, Tyron Madlener tyronx@gmail.com wrote:
On Sun, May 15, 2011 at 1:41 PM, Marc Delisle marc@infomarc.info wrote:
Le 2011-05-15 05:25, Tyron Madlener a écrit :
In most files language strings are being included directly with the __() function, however in server_status.php in the first lines of code are a huge amount of variables being set to the language strings, that are later used. Like those:
$strShowStatusDelayed_writesDescr = __('The number of INSERT DELAYED rows written.'); $strShowStatusFlush_commandsDescr = __('The number of executed FLUSH statements.'); $strShowStatusHandler_commitDescr = __('The number of internal COMMIT statements.');
Does that have any particular reason?
Yes. The current logic builds the messages using the message names:
if (isset($GLOBALS['strShowStatus' . $name . 'Descr'])) { echo $GLOBALS['strShowStatus' . $name . 'Descr']; }
Oh, I see. Thanks!
-- Marc Delisle http://infomarc.info
Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Tyron Madlener a écrit :
Another question: If I remove or alter an existing language string do I have to do anything or does the pootle system automatically recognizes any changes?
In the GSoC context, you don't have to do anything else. When your code is merged to the Sourceforge.net repository by your mentor, he will regenerate the .po files so that translators can work on the new strings via Pootle.
On Mon, May 23, 2011 at 6:54 PM, Marc Delisle marc@infomarc.info wrote:
Tyron Madlener a écrit :
Another question: If I remove or alter an existing language string do I have to do anything or does the pootle system automatically recognizes any changes?
In the GSoC context, you don't have to do anything else. When your code is merged to the Sourceforge.net repository by your mentor, he will regenerate the .po files so that translators can work on the new strings via Pootle.
Ok thanks.
-- Marc Delisle http://infomarc.info
What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
-
Marc Delisle -
Tyron Madlener