Users achieve localization of programs by setting proper values to special environment variables, prior to executing those programs, identifying which locale should be used.
In a nutshell, one could say that internationalization is the operation by which further localizations are made possible.
Also, very roughly said, when it comes to multi-lingual messages, internationalization is usually taken care of by programmers, and localization is usually taken care of by translators. There are many attributes that are needed to define a country’s cultural conventions.
There are a whole host of routines and functions provided to aid programmers in developing internationalized software and which allow them to access the data stored in a particular locale.
When someone presently refers to a particular locale, they are obviously referring to the data stored within that particular locale.
They have no confidence at all that the dream might ever become true.
Yet some have not lost hope, and have organized themselves.
In this manual, we use Usually, programs are written and documented in English, and use English at execution time to interact with users.
This is true not only of GNU software, but also of a great deal of proprietary and free software.
By , one refers to the operation by which a program, or a set of programs turned into a package, is made aware of and able to support multiple languages.
This is a generalization process, by which the programs are untied from calling only English strings or other English specific habits, and connected to generic ways of doing the same, instead.
Program developers may use various techniques to internationalize their programs. GNU , one means the operation by which, in a set of programs already internationalized, one gives the program all needed information so that it can adapt itself to handle its input and output in a fashion which is correct for some native language and cultural habits.