On 25/08/2010 21:26, Guido van Rossum wrote: > [snip...] >> If (3) could enter the main trunk it would be a great help by itself. >> In this case access to international help is useless due the original >> difficulties with the language, remember I'm talking about kids >> mainly, and 1st stage to programming for youngsters. There are two >> main ways to do this, one is using codes as indicated, but I prefer >> using the more generally accepted and used, with messages catalogs >> using gettext and the like. > That sounds painful, but in general I am okay with the idea of > translating messages. I think the system messages (those that go with > IOError and OSError) may already be translated. How to do it without > off-putting the core developers may end up being a research problem. > :-) > +1 - a difficult problem to solve (socially and architecturally but not technologically) but users are likely to appreciate it. A downside (from experience with .NET which takes this approach - logic and class names are all English but error messages are localized) is that you then get bug reports with localized error messages. It makes frequent visits to google translate unavoidable... All the best, Michael -- http://www.ironpythoninaction.com/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4