Determination of language codes from a locale

[Markus Elfring]

By forcing every implementation to understand and define whatever
is meant by "_NL_IDENTIFICATION_LANGUAGE" and "nl_langinfo".

Would you like to suggest different symbols and better function interfaces with
clear data structures to improve the involved API situation?

Regards,
Markus

 

[Kenny McCormack]

Twink and Kenny have this exactly backward. CBFalconer is sometimes
wrong (way too often wrong). But he is not deliberatly
disruptive of the Newsgroup. T&K rarely (*vanishingly* rarely)
post anything useful or constructive.

I'm sure the Witch of the West would say that she (and Ms. East as well)
is/are a good witch. I respectfully, disagree.

You and CBF probably think you are the good ones, too.

 

[David R Tribble]

Would you like to suggest different symbols and better function interfaces with
clear data structures to improve the involved API situation?

IIRC, the current ISO C standard does not require the
implementation to be aware of any external environment variables
for its operation. (That's not to say that a given implementation
cannot use environment variable settings, it's just that ISO C does
not /require/ it.)

So it's not a question of symbol names, but about requiring
certain environment variables to exist in the first place. On some
systems, the very notion of "environment variable" is an unknown
concept.

Also, it's an uphill battle to add X/Open or POSIX functionality to
the ISO C standard library. How would MS/Win32 applications
deal with them, for example, in light of the fact that the Win32
platform already has its own locale functions?


FWIW, I've taken a different approach in my various proposals for
ISO C library enhancements. I borrow the most useful and most
general functionality from several sources (primarily POSIX and
Win32, but also others) and invent an entirely new set of function
and variable names to embody them. That way, no single existing
implementation is favored over the others, but the functionality
still covers all (or most) of them.

See
http://david.tribble.com/letters.html#c-proposals

-drt

 

[Markus Elfring]

Also, it's an uphill battle to add X/Open or POSIX functionality to
the ISO C standard library. How would MS/Win32 applications
deal with them, for example, in light of the fact that the Win32
platform already has its own locale functions?

Is there a growing demand to complete the standard programming interfaces?
Are more extensions needed for locale data to express personal preferences?

Regards,
Markus