Hi Everyone,
I was looking into the translations of PMA. On the translation server, I found strings with colon (:) in them. For example see code at [0]. Shouldn't colon be outside '__()'function? That would keep all the field-value separators like colon away from the translation strings.
[0]: https://github.com/phpmyadmin/phpmyadmin/blob/master/index.php#L266
Regards, Dhananjay Nakrani.
Dhananjay Nakrani a écrit :
Hi Everyone,
I was looking into the translations of PMA. On the translation server, I found strings with colon (:) in them. For example see code at [0]. Shouldn't colon be outside '__()'function? That would keep all the field-value separators like colon away from the translation strings.
Hi Dhananjay, maybe in some language, the colon has to be replaced by the equivalent character in this language?
Hi
Dne Fri, 27 Jun 2014 00:26:29 +0530 Dhananjay Nakrani dhananjaynakrani@gmail.com napsal(a):
I was looking into the translations of PMA. On the translation server, I found strings with colon (:) in them. For example see code at [0]. Shouldn't colon be outside '__()'function? That would keep all the field-value separators like colon away from the translation strings.
The reason for that is that different languages have different colons (even if I skip some weird things, depending on charset used, unicode has two colons, one for standard charsets and one for double width like Chinese or Japanese - : and ：). And even if they have same colon, they for example expect to have space before it...
Generally, the string to translate should be always complete string you see in the UI, otherwise it's really hard to translate it properly into some languages.
Hi,
On Fri, Jun 27, 2014 at 2:21 AM, Michal Čihař michal@cihar.com wrote:
Hi
Dne Fri, 27 Jun 2014 00:26:29 +0530 Dhananjay Nakrani dhananjaynakrani@gmail.com napsal(a):
I was looking into the translations of PMA. On the translation server, I found strings with colon (:) in them. For example see code at [0]. Shouldn't colon be outside '__()'function? That would keep all the field-value separators like colon away from the translation strings.
The reason for that is that different languages have different colons (even if I skip some weird things, depending on charset used, unicode has two colons, one for standard charsets and one for double width like Chinese or Japanese - : and ：). And even if they have same colon, they for example expect to have space before it...
Generally, the string to translate should be always complete string you see in the UI, otherwise it's really hard to translate it properly into some languages.
-- Michal Čihař | http://cihar.com | http://phpmyadmin.net
Ohh, okay, so colon should be there. Thanks. :-)
Regards, Dhananjay Nakrani.
-
Dhananjay Nakrani -
Marc Delisle -
Michal Čihař