Yep. And programming languages, while they use English keywords, are not English. They are languages in their own right, and "translating" words is not a good idea, because that's creating a new language.
A less hack-y solution might be for new languages to start incorporating more languages in their choices of keywords and class names.
Suppose someone were designing a new language (let's call it Foolang), and these were some of the keywords:
* publico, privado, protegido (access specifiers in Spanish)
* eetha/akhra (if/else in Arabic)
* zhen/jia (true/false in Mandarin)
I think this would be an interesting experiment. It would have to be a compelling language in its own right though.
Still, a language monoculture is more convenient for most programmers. As an English-speaking programmer, I'd hate to have to maintain, say, Chinese code.