Re: translating numbers



O/H Khaled Hosny έγραψε:
I'm going to repeat what Djihed said, in Arabic we either use Arabic or
Arabic-Indic numbers according to locale. Now if we have a string "1" or
"2" and so on, we won't be able to translate it as people in Egypt (and
other Arabic counteries to the east of it) want "١" and "٢", while
others want to keep it "1" and "2".
By using place holder, %d, we can translate it %Id and let the locale
definition decide which system to be used.
Daniel, you put then something like

countdown = 3;
while (countdown>=0) {
  /* TRANSLATORS: This is the countdown number when taking the photograph.
* If you leave as is (that is, %d), it will show 3, 2, 1, 0. To enable to show the numbers in your
   * own language, use  %Id instead.
   */
  show_on_screen("%d");
}

Gettext will take the comment and add it in the PO file for the translators to see.

Simos
On Fri, Apr 25, 2008 at 07:27:17PM +0200, daniel g. siegel wrote:
using "1", "2", "3" as strings makes more sense to me, as we wont have
any other numbers. i commited it to trunk.

thanks!

daniel

On Wed, 2008-04-23 at 21:31 +0100, Djihed Afifi wrote:
 <في ر، 23-04-2008 عند 22:29 +0200 ، كتب daniel g. siegel:
hi!

in cheese we got a nice countdown widget, which just counts down from 3
to 1 and then shows a small camera. those three strings ("1", "2", and
"3" are not translated). should i make them translatable?

at least i think, there are some people, who do not use arabic numbers.

Hi!

Please work it out using variable placeholders, i.e %d and a comment.

That way, we, at the Arabic team (we use both Arabic and Hindu numerals
for different locales) could just use %Id and the application will
display the right numerals upon reading the locale.
If you use 1, 2, etc verbatim we will just copy them and nobody will get
the benefit.

Djihed



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]