Our booth at OSCON this year will likely feature "i18n" as a theme, whichmeans "internationalization" (a numeronym it's called -- check Wikipedia).

Our school is hoping to offer courses in the native languages ofother-than-Anglo speakers eventually, though for the moment we're anEnglish-only shop, in terms of language of instruction (our students arefrom all walks of life and from all over the world).

What we teach though is polyglot: PHP, Perl, Python (the original Planguages in LAMP-stack), Java, C#, JavaScript, Calculus, Ruby on Rails,HTML/CSS and Android, also some overview courses.

So the English could be swapped out for Portuguese or Russian orKyrgyzstani or whatever.

I think some of schools make it their goal to teach a low level "fordummies" kind of bastardized "business English" and then make that thebedrock upon which computer languages are learned. The language ofinstruction is "bad English" one might say.

On the contrary, whereas Python is a great ESL "project language "(learnPython via English as a technical application), the goal could just as wellbe to use the "high culture" most literary form of each native language(e.g Portuguese) such that each student gets a fully loaded culturallysophisticated language of instruction.

If you're a native Chinese speaker, you deserve your course-ware inChinese, and so on.

On the other hand, Business English (BE) is indeed a useful and importanttool around the world.

Esperanto went nowhere.

So BE might also be one of our courses.

It's just I don't think we're likely to force BE as the language ofinstruction for something as nuanced and technical as a computer languageor calculus.

You need to use your native language more likely.

Plus, with unicode, you can write the source code in your own language butfor a few keywords, as I'm showing of in the exhibit / trial over onedu-sig (Python discussion list):