Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   31559 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

nl_langinfo(3C)						       nl_langinfo(3C)

NAME
     nl_langinfo - language information

SYNOPSIS
     #include <nl_types.h>
     #include <langinfo.h>

     char *nl_langinfo (nl_item item);

DESCRIPTION
     nl_langinfo returns a pointer to a null-terminated string containing
     information relevant to a particular language or cultural area defined in
     the program's locale.  The manifest constant names and values of item are
     defined by langinfo.h.

     For example:

	  nl_langinfo (ABDAY_1);

     would return a pointer to the string ``Dim'' if the identified language
     was French and a French locale was correctly installed; or ``Sun'' if the
     identified language was English.

     Another example follows which shows the mechanism to change a locale's
     messages related to the following items given in nl_types(5):  T_FMT,
     D_FMT, D_T_FMT, YESSTR, NOSTR. These items are treated specially within
     nl_langinfo().  The items T_FMT, D_FMT, D_T_FMT, YESSTR, and NOSTR are
     retrieved from a special message catalog named Xopen_info which should be
     generated for each locale supported and installed in the appropriate
     directory.	 All of the following steps should be done as userid root.

	  Create the file: /tmp/Xopen_info.src containing the following five
	  lines corresponding to the items: T_FMT, D_FMT, D_T_FMT, YESSTR, and
	  NOSTR, respectively:

	       %H:%M:%S
	       %m/%d/%y
	       %a %b %e %H:%M:%S %Y
	       yes
	       no

	  Execute the following command in order to create the new message
	  catalog file:	 /usr/lib/locale/C/LC_MESSAGES/Xopen_info:

	       mkmsgs -i C /tmp/Xopen_info.src Xopen_info

	  Execute the following command in order to create the new message
	  catalog file:	 /usr/lib/locale/VSX4L0/LC_MESSAGES/Xopen_info:

	       mkmsgs -i VSX4L0 /tmp/Xopen_info.src Xopen_info

									Page 1

nl_langinfo(3C)						       nl_langinfo(3C)

SEE ALSO
     gettxt(3C), localeconv(3C), setlocale(3C), strftime(3C), langinfo(5),
     nl_types(5).

DIAGNOSTICS
     If setlocale has not been called successfully, or if langinfo data for a
     supported language is either not available or item is not defined
     therein, then nl_langinfo returns a pointer to the corresponding string
     in the C locale.  In all locales, nl_langinfo returns a pointer to an
     empty string if item contains an invalid setting.

NOTES
     The array pointed to by the return value should not be modified by the
     program.  Subsequent calls to nl_langinfo may overwrite the array.

     The nl_langinfo function is built on the functions localeconv, strftime,
     and gettxt [see langinfo(5)].  Where possible users are advised to use
     these interfaces to the required data instead of using calls to
     nl_langinfo.

									Page 2

Vote for polarhome