Skip to main content

India’s Quest for a National Language!

    A popular misconception among Indians is that Hindi is our National Language. In reality, it is as absurd as saying Hinduism is our National Religion. The fact is that, Hindi is not our National Language; we do not have a National Language or a National Religion. Neither our constitution nor our law recognizes the existence of a National Language. So, from where the idea of Hindi being our National Language came is not clear. 
   Though majority of the people speak hindi, an even more majority want their children to speak in English. Everyone from a politician to bus driver, want their children to speak in English. This truth has been well established though the politicians are shy to accept this.
   India is a country with so many different languages and it is impossible to impose one among these as the national language. It is a very controversial issue and has been so for many years. Article 343 of our constitution dictates that "the official language of the Union shall be Hindi in Devanagari script," it also puts forth English as the other official language. The status of being the official language will not automatically make a language the national language. The law and the constitution have to give this recognition, which in Hindi's case has not happened. This was made clear in a ruling by a bench headed by Chief Justice S J Mukhopadhaya in the Gujarat High Court in January 2010 in a hearing regarding issuing of directions that packaged commodities must contain details about goods in Hindi. 
  For anything to be called national, it should have done something to inspire the aspiration of the people and also aid that aspiration. English has done it perfectly. In the words of Kamaraj, the then TN CM, who spoke out against hindi in 1950s, ‘If majority is the criteria, crow not peacock which should be the national bird’. The next decade will be India’s litmus test for role of Indians in global affairs, from making a pitch to security council and surpassing china’s economy. We can always preserve and grow our classical languages without hurting English, which will play a key role in India’s growth.
   There is a long lasting battle going on every now and then regarding this issue between the Hindi speakers and other language speakers, especially so in Tamil Nadu. This battle started even before independence, as early as the 1930s. The first agitation was between 1937 and 1940 in Tamil Nadu, after that the second one was between 45 and 50, in 65, in 68, in 86; this has always been an ongoing process. It emerged every now and then sparking a lot of controversy and unleashing a lot of hatred. There has not been any major attempt to set a National Language in so many years and so this battle is in a hibernation state for that duration and any attempt to revive the National Language campaign will definitely unleash it again. 
   Anti Hindi in TamilNadu: 
Dominance of Hindi can be seen in many areas, especially, in Rupee note, Govt. Job application forms, College admission forms, school books in which most of the leaders who fought for independence will be either from north or west or east & not many from south / especially tamil nadu. How many school students in India knows about leaders who fought for freedom from South India? What is the need for such dominance? Moreover, South Indian scripts are completely different than Devangiri scripts, so why students are forced to adapt new things?

The only question is "Do we really need a national language?"

Comments

Popular posts from this blog

Google re-branded the support Android libraries to AndroidX

It is important to note, you cannot mix AppCompat and Jetpack in the same project. You must convert everything to use Jetpack if you want to upgrade. The support library artifacts are being deprecated and all future development is going into AndroidX , so there's no avoiding this migration. Alan Viverette sums this up nicely: “There won’t be a 29.0.0, so Android Q APIs will only be in AndroidX” The stable release of 28.0.0 will be the final feature release packaged as android.support . All subsequent feature releases will only be made available as androidx-packaged artifacts. Below tips will give you a clearer transition path. The current version of AppCompat (v28.x) is exactly the same as AndroidX (v1.x). In fact, the AppCompat libraries are machine generated by changing maven coordinates and package names of the AndroidX codebase. For example, android.support.v7.app.AppCompatActivity is now androidx.appcompat.app.AppCompatActivity For a complete listi

Android Beginners Guide

                                                                                                               Android Operation System: Android is an operating system based on Linux with a Java programming interface. It provides tools, e.g. a compiler, debugger and a device emulator as well as its own Java Virtual machine (Dalvik Virtual Machine - DVM). Android is created by the Open Handset Alliance which is lead by Google. Android uses a special virtual machine, e.g. the Dalvik Virtual Machine. Dalvik uses special bytecode. Therefore you cannot run standard Java bytecode on Android. Android provides a tool "dx" which allows to convert Java Class files into "dex" (Dalvik Executable) files. Android applications are packed into an .apk (Android Package) file by the program "aapt" (Android Asset Packaging Tool) To simplify development Google provides the Android Development Tools (ADT) for Eclipse. The ADT performs automatically the conversion f

Android Pi migration(28 API support)

I am here to give some inputs on android PI migration. .  Apps must target at least API level 28 to ensure it is built on the latest APIs optimized for security and performance . From August 2019, new apps must target at least Android 9.0 (API level 28) . The objective here is to make sure that your existing app works as-is on Android 9. Because some platform changes might affect the way your app behaves, some adjustments might be necessary, but you do not need to use new APIs or change your targetSdkVersion. Android Service Problem On Oreo, startService() will throw IllegalStateException. This can be fixed by changing it to startForegroundService(). but it also stops the service immediately if you don’t bind to the Notification with Service.startForeground() within 5 seconds. For other background service we decided to use the WorkManager . Implementation: Since we have minSdkVersion 19, We migrated to workmanger for scheduled tasks and we still use JobIntentSer