Jeu George writes:
> In a threaded model of the SQL tool different users will be working
> in different threads, and this is where thread safety is required.
You are right: in this case using setlocale, mblen and related
functions are of no use to you, and the ISO C++ locale model is the
way to go.
> I would like to know if anybody from this mailing list is familiar this.
I'm not familiar with it, but you can find reference material on the
web at http://mip.ups-tlse.fr/~grundman/KCC/library-html/ch11.b.html
and http://www.dinkumware.com/refcpp.html.
> In the directory /usr/lib/locale we have differnt directories that have
> names of different locales. Right???
Yes.
> In each of these when have some more directories like LC_COLLATE,
> LC_CTYPE etc.. Unlike in en_US.UTF-8 dir where we have all the attributes
> ie LC_COLLATE LC_CTYPE LC_MESSAGES LC_MONETARY LC_NUMERIC LC_TIME
> LO_LTYPE, in other directories like fr.UTF-8 we have only LC_MESSAGES,
> what does this mean???
Once you have done "localedef -i fr -f UTF-8 fr.UTF-8", the fr.UTF-8
directory should contain the LC_COLLATE etc. files as well.
> UTF-8 is supposed to cover character of all the major languages that are
> used in the world today. Then what is the purpose of having differnt
> locales like de.UTF-8 de.UTF-8@euro en_US.UTF-8 es.UTF-8
The LC_CTYPE locales of these should all be identical, except for very
minor differences. The other parts (LC_COLLATE, LC_TIME etc.) reflect
local cultural habits - sorting order, time display format etc. -
which are codeset independent.
The distinction between de.UTF-8 and de.UTF-8@euro, however, does not
make sense. Maybe these two are identical?
Bruno
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
