Re: Bug in Set Language when opened in ta_IN locale

I know what the bug is:

The po to strings conversion is wrong..

For example, consider this in .po file
#. LANG_FA_IR
#: po/tmp/xap_String_Id.h.h:297
msgid "Farsi"
msgstr "பார்சி"

This translation is mapped to File in ta-IN.strings file.
DLG_UP_File="பார்சி"

Farsi is a language but its translation is mapped to File. Clearly there is
something wrong in po2strings conversion.
Similarly, a lot of wrong conversions, I can see in ta-IN.strings file.

Thanks,
Vijay

>From: "vijay durairaj" <vijayd_81@hotmail.com>
>To: roland.kay@ox.compsoc.net, abiword-dev@abisource.com
>Subject: Re: Bug in Set Language when opened in ta_IN locale
>Date: Mon, 04 Apr 2005 00:16:25 -0600
>
>
>Thanks for looking into this.
>
>I have filed the bug. Bug# 8768
>http://bugzilla.abisource.com/show_bug.cgi?id=8768
>
>Thanks,
>Vijay
>
>>From: Roland Kay <roland.kay@ox.compsoc.net>
>>To: abiword-dev@abisource.com
>>Subject: Re: Bug in Set Language when opened in ta_IN locale
>>Date: Mon, 4 Apr 2005 06:58:26 +0100 (BST)
>>
>>
>>
>>I can confirm the problem with nonsense being displayed in the Set
>>Language dialog with LANG=ta_IN.UTF-8. I have a screenshot that I'll
>>attach once a bug report has been opened for this.
>>
>>While investigating, I wrote a quick patch for bug 8694 which changes the
>>asserts that occur for blank translations (i.e. FOO="") to a warning
>>message. Without this running in a Tamil locale generates 400+ asserts,
>>which is annoying.
>>
>>http://bugzilla.abisource.com/show_bug.cgi?id=8694
>>
>>Best wishes,
>>
>>R.
>
>
Received on Tue Apr 5 01:15:53 2005