catgetmsg(3int) [ultrix man page]
catgetmsg(3int) catgetmsg(3int) Name catgetmsg - get message from a message catalog Syntax #include <nl_types.h> char *catgetmsg(catd, set_num, msg_num, buf, buflen) nl_catd catd; int set_num, msg_num, buflen; char *buf; Description The function has been superceded by the function. You should use the function to get messages from a message catalog. You might want to rewrite calls to the function so that they use the function. The function is available for compatibility with XPG-2 conformant software and might not be available in the future. For more information on using see the reference page. The function attempts to read up to buflen -1 bytes of a message string into the area pointed to by buf . The parameter is an integer value containing the size in bytes of buf. The return string is always terminated with a null byte. The parameter catd is a catalog descriptor returned from an earlier call to and identifies the message catalog containing the message set ( set_num) and the program message ( msg_num). The arguments set_num and msg_num are defined as integer values for maximum portability. Where possible, you should use symbolic names for message and set numbers, rather hard-coding integer values into your source programs. If you use symbolic names, you must run prior to and be sure the appropriate include file is used in your program. Return Value If successful, returns a pointer to the message string in buf. Otherwise, if catd is invalid or if set_num or msg_num are not in the mes- sage catalog, returns a pointer to an empty (null) string. See Also intro(3int), gencat(1int), catopen(3int), catgets(3int), nl_types(5int) Guide to Developing International Software catgetmsg(3int)
Check Out this Related Man Page
gencat(1int) gencat(1int) Name gencat - generate a formatted message catalog Syntax gencat catalog_file [source_file ...] Description The command takes one or more message source files and either creates a new catalog or merges new message text into an existing catalog. You should use the extension for message text files (for example, ) and the extension for catalogs (for example, ) to process files with the command. In some cases, a formatted message catalog exists that has the same name the one that is creating. When this occurs, merges the messages from the source message catalogs into this existing formatted message catalog. The command merges the source message catalogs into the formatted message catalog in the same manner as it merges a group of source message catalogs. If a source message catalog contains the same set number or message number as a set or message in the formatted message catalog, the source message catalog set or message has precedence. For example, if both the source and formatted message catalogs contain a message number 25, the message text for message 25 in the source message catalog replaces the message text in the formatted message catalog. Thus, when source message catalogs are merged with formatted message catalogs, the formatted catalogs are updated. If you do not specify a source file, the command accepts message source data from standard input. Numeric message source files are portable between X/Open systems. For information on the source format for messages files, see the Guide to Developing International Software. Restrictions The command does not accept mnemonic identifiers. You must run the command if you want to use mnemonic identifiers. See Also extract(1int), mkcatdefs(1int), trans(1int), catgets(3int), catopen(3int), intro(3int), environ(5int) Guide to Developing International Software gencat(1int)