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   9087 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

CATGETS(3)		 BSD Library Functions Manual		    CATGETS(3)

NAME
     catgets — retrieve string from message catalog

LIBRARY
     Standard C Library (libc, -lc)

SYNOPSIS
     #include <nl_types.h>

     char *
     catgets(nl_catd catd, int set_id, int msg_id, const char *s);

DESCRIPTION
     The catgets() function attempts to retrieve message msg_id of set set_id
     from the message catalog referenced by the descriptor catd.  The argument
     s points to a default message which is returned if the function is unable
     to retrieve the specified message.

RETURN VALUES
     If the specified message was retrieved successfully, catgets() returns a
     pointer to an internal buffer containing the message string; otherwise it
     returns s.

ERRORS
     The catgets() function will fail if:

     [EBADF]		The catd argument is not a valid message catalog
			descriptor open for reading.

     [EINTR]		The operation was interrupted by a signal.

     [ENOMSG]		The message identified by set_id and msg_id is not in
			the message catalog.

SEE ALSO
     gencat(1), catclose(3), catopen(3), nls(7)

STANDARDS
     The catgets() function conforms to X/Open Portability Guide Issue 4,
     Version 2 (“XPG4.2”).

     Major Unix vendors are split over the adoption of the two most important
     message catalog specifications: catgets or gettext(3).  The primary con‐
     cern with the catgets interface is that every translatable string has to
     define a number (or a symbolic constant) which must correspond to the
     message in the catalog.  Duplicate message IDs are not allowed.  Con‐
     structing message catalogs is difficult.

BSD			       February 12, 2003			   BSD

                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 

Vote for polarhome