On May 25, 2017, at 6:25 PM, Vikram Rawat <vikramrawa...@gmail.com> wrote: > > Hello Bakul, > > I am just an R programmer(by which i mean i don't understand programming > much). I was looking for an alternative way to python. I really don't > understand what you said but i want to let you all know one thing. > > English hasonly 26 characters but those are not sufficient for languages like > hindi, bengali, gurumukhi, malyalam and many other phonetic languages. So we > use entire keyboard to type letters. > > In the above example सोम is a proper word with a meaning we just simply can't > ignore ो or letters like that at all.
See the current Go language rules for identifiers in the language reference, which do not allow vowel signs as part of an identifier (they do not belong to unicode category "Letter"). As Rob pointed out, https://github.com/golang/go/issues/5167 <https://github.com/golang/go/issues/5167> covers this issue. To allow vowel signs in an identifier, the language definition has to change. As per the discussion on that page it appears this issue won't be resolved in Go1. This is probably because very few people care about this issue so it gets a low priority. Most Indian programmers seem fine using English identifiers in any case. I would like to see this fixed because I consider it a language bug. I suggested a solution which is simple to implement. At present no such Indic identifier exists so not everything in the ecosystem needs to be fixed right away! One can start with the compiler. Other tools can be fixed later as per need. But realistically this is a low priority item -- don't hold your breath! And don't wait for Go2 either! > Please tell me what to do. I really want to write program in my language > because there arenone written yet. This is a separate issue and should be discussed outside of this group but some remarks: Just choosing identifiers in your language does not mean you are "writing programs in your language". You will also be using standard libraries which have english names for exported functions, variables and types etc. My advice is to stick to English. Until there is a complete ecosystem in Hindi or whatever local language (meaning libraries, documentation etc. etc.) the user has to know English in any case and using Hindi names means you will have fewer people who can help you! If you really want to work with Hindi, my advice is to work on Hindi language related tools. In general s/w support for most Indian languages is lagging far far behind English (and I suspect other European languages + Chinese, Japanese & Korean). But this is best discussed offline and not on this list. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
