[pypy-dev] (no subject)

[Samuel Villamonte]

+1 here! May I suggest using Transifex? That way you could crowdsource
translation not only to Spanish but to other languages. Some documentation
is available here:

http://docs.transifex.com/developer/client/
http://docs.transifex.com/developer/formats/gettext
http://docs.transifex.com/faq/#the-open-source-project-definition

Disclamer:
1. I know nothing about RPython nor PyPy internals, but from what I gather
about the patch it could be handled through gettext .PO files, right?
2. I do have an account at Transifex and volunteer at the Coursera Global
Translator community, In fact, Coursera is translating an introductory
Python course:

https://www.coursera.org/course/interactivepython1

Regards,


2015-05-04 5:05 GMT-05:00 Carl Friedrich Bolz <cfbolz at gmx.de>:

> Hi Laura,
>
> Thanks for kicking this off. Just a brief comment: I am strongly for
> trying to get multi-language support into PyPy, particularly error messages
> and docstrings. The actual translations would have to be crowd-sourced of
> course, but there are various tools for that.
>
> There are a few technical questions that need discussing, but those are
> probably solvable.
>
> (actually on the technical side I think there is a good reason why pypy is
> well-positioned to implement this: our error messages are already a bit
> different than CPython's, so code that depends on the precise error string
> is anyway potentially broken on pypy.)
>
> Cheers,
>
> Carl Friedrich
> On May 4, 2015 01:27, <lac at openend.se> wrote:
>
>> Hello gang.
>>
>> Mario Reingart has been trying to internationalise CPython
>> since at least 2012.
>>
>> Here is his lastest proposal, for GSOC.
>>
>> http://www.google-melange.com/gsoc/proposal/public/google/gsoc2015/reingart/5634387206995968
>>
>> The PSF declined to fund it.
>>
>> He's written a PEP about it, which apparantly isn't in the list of
>> PEPs anywhere, and has had this discussion, such as it was on the
>> python-dev mailing list.
>>
>> http://bugs.python.org/issue16344 seems to have the arguments against
>> having it put into Cpython.
>>
>> The arguments against seem very weak to me.
>>
>> My idea is that it would be good to intenationalise
>> PyPy and then we can capture all the
>> people who want to teach Python in the non-english speaking world.
>> Mariano already has written a book about using web2py, but as far
>> as I know we are perfectly compliant with this.  Mariano didn't
>> know anything about PyPy when I wrote to him about it.  The idea
>> that it was a completely Python compliant version was news to him...
>> an indication that we lack international communication presence.
>> This could be a way out of obscurity.
>>
>> Poor old Mariano has been fighting this fight since before 2012.
>> He is sad and unhappy.  Mostly he is sad and unhappy because people
>> won't discuss what he wants, or move from -- ideals fine, implementation
>> well, would be better this way --- or any sort of reasonable discussion.
>> 'Hung out to dry' comes to mind.
>>
>> I sincerely suspect that the people here will support this idea,
>> but may  argue that in pypy there are better ways to do it, and, well
>> we will get it done.  But in any case, please be kind to Mariano,
>> since he has already suffered enough for the cause.
>>
>> ps -- funding it comes later.  I'd like to get Mariano paid.
>> But I'd like to get some sort of idea that we want to go forward
>> with this before I make a different note on how I would like to
>> approach funding this.
>>
>> Take care all,
>> Laura
>>
>> _______________________________________________
>> pypy-dev mailing list
>> pypy-dev at python.org
>> https://mail.python.org/mailman/listinfo/pypy-dev
>>
>
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> https://mail.python.org/mailman/listinfo/pypy-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20150504/dfad1574/attachment.html>