Bruno Haible wrote on 2001-04-06 13:21 UTC:
> Forget about OUTPUT_CHARSET, it's nowhere
> documented. Only nl_langinfo(CODESET) is documented and standardized.
Applause!
> > Problems:
> > * Is OUTPUT_CHARSET a gnu extension, or part of some standard?
>
> OUTPUT_CHARSET is a glibc specific hack.
General remark:
Non-standard proprietary additions of environment variables on which the
C library reacts can be a very dangerous security risk and should be
*most strongly* discouraged. They add semantics to your applications
that most users and developers do not know about. It might look
convenient in some situations at first glance but in the end it is a
foolish idea if you carefully consider all associated risks introduced.
Markus
--
Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org, WWW: <http://www.cl.cam.ac.uk/~mgk25/>
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
