This is pretty neat. I've not taken a close look at the implementation but I'll definitely do that (if it isn't a whole lot of effort could you please describe/

This is pretty neat. I've not taken a close look at the implementation but I'll definitely do that (if it isn't a whole lot of effort could you please describe/document the design and approach taken ?) I've had thoughts about solving this problem previously but never acted on it. My thoughts on this however were along the lines of providing the ability to re-define the keywords and builtins as part of the interpreter itself in such a way that even the prompt could accept non-english input. Thinking about this is natural when one is Indian[1] and ends up working with some really talented people who have weak English skills simply because their primary education was conducted entirely in a non-English medium. A lot of words used to express programming ideas are difficult for non-native English speakers to remember even if the ideas themselves are not (think abstraction, encapsulation, introspection, reentrant, idempotent ...etc) and the effort required to remember and use them correctly when communicating with other devs is higher (IMHO) for non-native English developers. Of course this is non an India specific issue, and of course English is the lingua franca of technology but that shouldn't be the barrier to entry for learning programming. kudos on the effort once again ! [1] one country, and a multitude (22 according to http://en.wikipedia.org/wiki/List_of_languages_by_number_of_native_speakers_in_India http://en.wikipedia.org/wiki/List_of_languages_by_number_of_... ) of 'official languages'