[Localization] Arabic translation

[Simon Schampijer]

On 09/21/2010 05:13 PM, Khaled Hosny wrote:
> On Tue, Sep 21, 2010 at 04:33:26PM +0200, Simon Schampijer wrote:
>> On 09/21/2010 03:04 PM, Khaled Hosny wrote:
>>> As for the %.0s, we are using it as place holder since the first three
>>> plural forms in Arabic (0, 1 and 2) should not contain the numeral value
>>> as the Arabic word used already denote the number. %.0s will just print
>>> nothing (a zero length string), it is just a hack to prevent application
>>> crashing. A better solution is to used named variable, %(week)d or
>>> something, and this will allow reordering and omitting unused
>>> variables, which is often needed in translations.
>>
>> Hmm, ok. Actually we do 'crash' with this hack [1]. As the current
>> Sugar code expect the conversion specifier to be present.
>
> AFAICT, it worked fine when I tested it (that hack was suggested after a
> discussion here IIRC), but that was a while ago.

I think the discussion you are referring to is: 
http://lists.laptop.org/pipermail/localization/2008-August/001352.html

>> There is a new formatter in Python 2.6 [2], however a python bug
>> report [3] suggest that there are still issues when used with
>> gettext and that using named variables would work fine. However
>> either change would need changes in the string itself, so we would
>> have to port the existing translations or ask translators to
>> translate another time.
>
> Proper fixes are always desired, even if it means a bit more work.

Sure. I have updated http://bugs.sugarlabs.org/ticket/2354

Regards,
    Simon