Re: [Python-Dev] i18n
-On [20100813 23:51], Alcino Dall'Igna Jr ([email protected]) wrote: >I'm starting a project that aims at first to internationalize the python >interpreter, so it could be localized. I want to know if this could be >considered for the main trunk of python. I doubt you will be able to localize much with regard to the interpreter. The only thing that really comes to mind are the error and exception messages, but you will never be able to localize the errors themselves. The problem there is that if they seek help on international fora for Python, other people might have no clue what the (error) message even means. The only portable way around that is if you start assigning each and every message in the interpreter an integer that's unique. That way one is always able to identify across languages which exact message is being referred to. I think AIX did something similar. >As a second phase I intend to internationalize the language itself so it could >be localized and used with kids and for programming teaching. I think this is not going to be helpful in the long run. The upside is that you are teaching programming in their native language. The more heavy downside is that you are creating a programming dialect that requires extensive rewriting (which might or might not be automated) in order to be compatible with the Python the rest of the world uses. This is frustrating for the budding programmer. Especially if they seek help using the various help fora available to them. Aside from that, the way Python is using English idiom in its syntax does not necessarily mean you can translate it 1-on-1 to a target language. If-then-else might become very convoluted in, say, Japanese. So what then will the added benefit be for the main trunk of Python? Personally I think it would be much more valuable if the Python documentation had some volunteers working on it to get it translated to their own language. Just my EUR 0,05. -- Jeroen Ruigrok van der Werven / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B Only a life lived for others is worth living... ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] i18n
> I'm starting a project that aims at first to internationalize the python > interpreter, so it could be localized. I want to know if this could be > considered for the main trunk of python. It's not exactly clear what you are proposing, but most likely, the answer is "no". If you plan to internationalize the keywords and the names of the library functions, then this can never go into Python. Translating the doc strings might be ok. However, instead of doing so, I recommend that you join the project to translate the Python documentation, at pootle.python.org. This will not only help children, but any user of the language who isn't very good at the English language. Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] mingw support?
Am 14.08.2010 08:35, schrieb Zooko O'Whielacronx: > On Sat, Aug 7, 2010 at 2:14 PM, Steve Holden wrote: >> There have certainly been demonstrations that Python can be compiled >> with mingw, but as far as I am aware what's missing is a developer >> sufficiently motivated to integrate that build system into the >> distributions and maintain it. > > It looks like quite a lot of activity on > http://bugs.python.org/issue3871 . I find it surprising that nobody > mentioned it before on this thread. Perhaps nobody who has been > posting to this thread was aware of this activity. Or one of these: http://bugs.python.org/issue1412448 http://bugs.python.org/issue1597850 http://bugs.python.org/issue3754 http://bugs.python.org/issue5026 http://bugs.python.org/issue6335 Because there is so many of them, all different, I didn't want to pick out any specific. Notice that #3871 is really two patch: the original one (from Roumen), and the one by Руслан, who basically hijacked the issue. Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
