[Localization] Pootle 2.5 porting [Work in Progress]

Aneesh Dogra aneesh at sugarlabs.org
Fri Jul 5 02:19:51 EDT 2013


Okay. So, after looking into what pootle's vcs scripts do. I think we
cannot use them for our directory structure. The problem being that pootle
searches for checkouts, project-wise. That means it will look for only
checkouts/project/langs and where it assumes this to checkouts/project to
be a git/svn/vcs repository. We don't have individual projects in pootle.
We instead have a category wise listing. That means all the projects that
run on glucose are added in checkouts/glucose/ in their own directories.
And all their po files are used together under one name,
glucose.intranslations/glucose/langs.

The best bet would be to keep using our version of vcs updation scripts in
pootle-helpers.

I am now trying to port them to make them work on the latest pootle.


On Fri, Jul 5, 2013 at 11:17 AM, Aneesh Dogra <aneesh at sugarlabs.org> wrote:

> Hey Chris, could you add my public ssh key to pootle's account on
> gitorious? I'd like to clone the repositories again and checkout some of
> pootle's vcs functions. I am sending you my public ssh key in a separate
> email. Thanks.
>
>
> On Fri, Jul 5, 2013 at 10:55 AM, Chris Leonard <cjlhomeaddress at gmail.com>wrote:
>
>> I'm in GMT -5 whicj makes it a little hard to find a good time.
>>
>>
>> The hey thing now is figuring out how we hook up the VCS (it seems to
>> have changed a little) so we can commit striaght into the repo and also get
>> POT updates performed (pot updater script)
>>
>>
>>
>> On Fri, Jul 5, 2013 at 1:21 AM, Aneesh Dogra <aneesh at sugarlabs.org>wrote:
>>
>>> Hey Chris,
>>>
>>> I'd like to setup a small meeting if possible to talk a bit more about
>>> the pootle 2.5 instance and what all tasks need to be done in order to
>>> complete the porting. I live in India, timezone: GMT + 5:30. Let me know if
>>> you'll be free to have a little meeting today or tomorrow.
>>>
>>> Or if you don't have any minute to spare could you describe a little
>>> what scripts you want and what other modifications to the new pootle would
>>> you like.
>>>
>>> > On Jul 4, 2013 11:38 PM, "Aneesh Dogra" <aneesh at sugarlabs.org> wrote:
>>> >>
>>> >> The database was using latin1 character encoding which needed to be
>>> changed to utf8.
>>> >>
>>> >>
>>> >> On Thu, Jul 4, 2013 at 10:33 PM, Chris Leonard <
>>> cjlhomeaddress at gmail.com> wrote:
>>> >>>
>>> >>> Please document the process you folowed to set up the new Poolte
>>> instance on this page.
>>> >>>
>>> >>> http://wiki.sugarlabs.org/go/Service/translate/Poolte_2.5_migration
>>> >>>
>>> >>> What exactly did you change to resolve the data corruption?
>>> >>>
>>> >>>
>>> >>> cjl
>>> >>>
>>> >>>
>>> >>> On Thu, Jul 4, 2013 at 4:47 AM, Aneesh Dogra <aneesh at sugarlabs.org>
>>> wrote:
>>> >>>>
>>> >>>> Hey Chis,
>>> >>>>
>>> >>>> I think I have fixed that issue now. The language characters are
>>> rendering properly now. I have tested Arabic, Nepali, Mongolian, Yiddish,
>>> Uyghur, Arabic, Hindi and they all seem to render properly. Feel free to
>>> test some more and let me know if there are some more issues.
>>> >>>>
>>> >>>>
>>> >>>> On Thu, Jul 4, 2013 at 3:17 AM, Chris Leonard <
>>> cjlhomeaddress at gmail.com> wrote:
>>> >>>>>
>>> >>>>> Arabic as well.
>>> >>>>>
>>> >>>>> cjl
>>> >>>>>
>>> >>>>>
>>> >>>>> On Wed, Jul 3, 2013 at 5:39 PM, Cris <canderson at laptop.org> wrote:
>>> >>>>>>
>>> >>>>>> Aneesh,
>>> >>>>>>
>>> >>>>>> It seems that a few of the fonts are either missing or rendering
>>> incorrectly. I checked a few and at least Mongolian, Nepali, Yiddish, and
>>> Uyghur seem to be missing. The translated text just shows up as "?" marks.
>>> There are probably I did not see. Best if the language admins check that
>>> their project is viewable.
>>> >>>>>>
>>> >>>>>> Cris
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> On Wed, Jul 3, 2013 at 1:12 PM, Aneesh Dogra <
>>> aneesh at sugarlabs.org> wrote:
>>> >>>>>>>
>>> >>>>>>> Hey List,
>>> >>>>>>>
>>> >>>>>>> I have finally ported our ancient pootle to pootle 2.5 (with all
>>> translation and database files) and it seems to be working. Check
>>> http://newpootle.sugarlabs.org/
>>> >>>>>>>
>>> >>>>>>> The next job is to start porting pootle-helpers and make them
>>> work on 2.5. If someone can give me a starting point it would be greatly
>>> helpful. Are there any scripts that might not be useful anymore?
>>> >>>>>>>
>>> >>>>>>> Pootle 2.5 also includes some new inbuilt scripts like
>>> commit_to_vcs, which of course commits and pushes translation changed to
>>> the linked code repository [git/svn/vcs], so it probably supersedes our
>>> version in pootle-helpers.
>>> >>>>>>>
>>> >>>>>>> Any inputs welcome.
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>> _______________________________________________
>>> >>>>>>> Localization mailing list
>>> >>>>>>> Localization at lists.laptop.org
>>> >>>>>>> http://lists.laptop.org/listinfo/localization
>>> >>>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> _______________________________________________
>>> >>>>>> Localization mailing list
>>> >>>>>> Localization at lists.laptop.org
>>> >>>>>> http://lists.laptop.org/listinfo/localization
>>> >>>>>>
>>> >>>>>
>>> >>>>
>>> >>>
>>> >>
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/localization/attachments/20130705/463c348c/attachment-0001.html>


More information about the Localization mailing list