[Localization] POT inconsistent against code for Record activity

Korakurider korakurider at gmail.com
Mon Jul 14 05:23:59 EDT 2008


On Mon, Jul 14, 2008 at 2:16 PM, Sayamindu Dasgupta <sayamindu at gmail.com> wrote:
> Hello,
>
> The main issue here seems to be the fact that the location of the
> Record repository has changed (earlier, the Record POT was fetched
> from a SVN repository). Is this going the repository from where
> further Record development will be happening in the future ? In that
> case, I'll switch over to the new repository.
   From http://lists.laptop.org/pipermail/sugar/2008-July/006904.html,
the latest source is obviously in git , but Daniel Drake could have
official words on the move.

Cheers,
/Korakurider

>
> Thanks,
> Sayamindu
>
> On Mon, Jul 14, 2008 at 10:43 AM, Korakurider <korakurider at gmail.com> wrote:
>> Hello.
>>
>> I noticed right now record-activity.po is based on old POT.
>>
>> Here is a record in the PO:
>>   #: constants.py:106
>>   #, python-format
>>   msgid "%(1)s hours, %(2)s minutes, %(1)s seconds remaining"
>>
>> Apparently one of placeholders is incorrect, but this has been fixed in repo
>> at the commit of
>> http://dev.laptop.org/git?p=users/dsd/record;a=blob;f=po/Record.pot;hb=52e8f3ed365ff53e3fba2bb5a013559bedebdbc1
>>
>> Header of the PO declares "POT-Creation-Date: 2007-12-20 09:20-0500\n",
>> that is even inconsistent to POT in git.
>> (In your explanation, POT is generated on Pootle server from source code, right?
>>  it seems not to work for this activity)
>>
>> Could you please take a look and fix it?  Thanks in advance.
>>
>>
>> Translators:
>>   You would need to review your translations after the correct POT is merged.
>>
>> Developers:
>>    Currently POT is automatically generated by weekly batch job on
>> Pootle server and is merged into each PO.
>>    But it seems that few people monitoring it actually.
>>    I would suggest you (at least owner of activities that is
>> translated on Pootle) to check regularly if string changes have been
>> correctly merged to POs.
>>    Without that translator might work against wrong strings and it
>> would result poor quality of product...
>>
>>    And I believe we need to document in our development process who
>> to check/maintain the consistency,
>>    while I don't know who is the right one.
>>
>> Cheers,
>> /Korakurider
>>
>
>
>
> --
> Sayamindu Dasgupta
> [http://sayamindu.randomink.org/ramblings]
>


More information about the Localization mailing list