Dear developers: 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. As a second phase I intend to internationalize the language itself so it could be localized and used with kids and for programming teaching. Finally a translator to give support for international collaboration in education of youngsters. I would like to hear of anyone interested in this. Thanks in advance, Alcino Dall Igna Junior Lecturer at IC/UFAL - Brasil
-On [20100813 23:51], Alcino Dall'Igna Jr (adijbr@gmail.com) 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(-at-)in-nomine.org> / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B Only a life lived for others is worth living...
On Sat, Aug 14, 2010 at 10:18 AM, Jeroen Ruigrok van der Werven <asmodai@in-nomine.org> wrote:
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.
I think one way to solve this might be to include the original (English) error message as well as the translation. I've noticed this is how error messages are handled in localized versions of Oracle, and although I'm personally annoyed by it, I can see how some people might find it useful. For example:
cause.error() Traceback (most recent call last): File "<stdin>", line 1, in <module> NameError: name 'cause' is not defined
localized to Norwegian, could become:
cause.error() Tilbakesporing (nyeste kall sist): Fil "<stdin>", linje 1, i <module> NameError: navn 'cause' er ikke definert (name 'cause' is not defined)
I think translating the actual error text would make sense, but I'm not so sure about localizing the traceback output itself... Anders
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
participants (4)
-
"Martin v. Löwis" -
Alcino Dall'Igna Jr -
Anders Sandvig -
Jeroen Ruigrok van der Werven