It's a stretch to even call some of the keywords in some languages words (car, cdr, con?). They're just tokens to feed to the compiler or interpreter, like parenthesis.
Even when full English words are used, it's rarely in the conventional meaning. English speaker or not, you'll have to learn what the word actually means in the given programming language.
But they won't be able to. Having a few keywords in your own language is vastly different from 'being able to solve problems in your local language'. It sounds like you don't understand programming.
If you take a look at the actual project you'll see that translating the language features to another language (and alphabet!) is cool, but not actually enough once you want to start interacting with libraries.
Which essentially means that without learning english, you will be stuck in a technical ghetto with the only way out being to learn english, or reimplement the world.
I still think this is highly interesting as a teaching tool; showing kids what is possible without requiring them to learn english may be a good motivator to actually learning english, but this doesn't seem to have many applications beyond as an introductory teaching tool.
People say my name is spelled funny or is too long...but it's not my problem, it's English's problem. Its only 6 characters in my native tongue.
In the same vein, what other ideas or concepts from non-natives are we missing because we are forcing them to learn a new language AND then to program? Furthermore, when we in the West talk about open-source, diversity and equity, we're still speaking in English. We're leaving a huge population out because the barrier to entry is learning English. If non-native speakers are now able to solve their own local problems in their local language, this is a boon for humanity and why we should encourage efforts to break down barriers like this.
I for one, welcome this endeavour and thank elangoc for his work on this.