mkmsgs man page on IRIX

Man page or keyword search:  
man Server   31559 pages
apropos Keyword Search (all sections)
Output format
IRIX logo
[printable version]



mkmsgs(1)							     mkmsgs(1)

NAME
     mkmsgs - create message files for use by gettxt

SYNOPSIS
     mkmsgs [-o] [-i locale] inputstrings msgfile

DESCRIPTION
     The mkmsgs utility is used to create a file of text strings that can be
     accessed using the text retrieval tools [see gettxt(1), srchtxt(1),
     exstr(1), and gettxt(3C)].	 It will take as input a file of text strings
     for a particular geographic locale [see setlocale(3C)] and create a file
     of text strings in a format that can be retrieved by both gettxt(1) and
     gettxt(3C).  By using the -i option, you can install the created file
     under the /usr/lib/locale/locale/LC_MESSAGES directory (locale
     corresponds to the language in which the text strings are written).

     inputstrings
		 the name of the file that contains the original text strings.

     msgfile	 the name of the output file where mkmsgs writes the strings
		 in a format that is readable by gettxt(1) and gettxt(3C).
		 The name of msgfile can be up to 14 characters in length, but
		 may not contain either \0 (null) or the ASCII code for /
		 (slash) or :  (colon).

     -i locale	 install msgfile in the /usr/lib/locale/locale/LC_MESSAGES
		 directory.  Only super-user user or a member of group bin can
		 create or overwrite files in this directory.  Directories
		 under /usr/lib/locale will be created if they don't exist.

     -o		 overwrite msgfile, if it exists.

     The input file contains a set of text strings for the particular
     geographic locale.	 Text strings are separated by a newline character.
     Nongraphic characters must be represented as alphabetic escape sequences.
     Messages are transformed and copied sequentially from inputstrings to
     msgfile.  To generate an empty message in msgfile, leave an empty line at
     the correct place in inputstrings.

     Strings can be changed simply by editing the file inputstrings.  New
     strings must be added only at the end of the file; then a new msgfile
     file must be created and installed in the correct place.  If this
     procedure is not followed, the retrieval function will retrieve the wrong
     string and software compatibility will be broken.

EXAMPLES
     The following example shows an input message source file C.str:
	  File %s:\t cannot be opened\n
	  %s: Bad directory\n
	       .
	       .
	       .

									Page 1

mkmsgs(1)							     mkmsgs(1)

	  write error\n
	       .
	       .

     The following command uses the input strings from C.str to create text
     strings in the appropriate format in the file UX in the current
     directory:
	  mkmsgs C.str UX

     The following command uses the input strings from FR.str to create text
     strings in the appropriate format in the file UX in the directory
     /usr/lib/locale/french/LC_MESSAGES/UX.
	  mkmsgs -i french FR.str UX

     These text strings would be accessed if you had set the environment
     variable LC_MESSAGES=french and then invoked one of the text retrieval
     tools listed at the beginning of the DESCRIPTION section.

FILES
     /usr/lib/locale/locale/LC_MESSAGES/*   message files created by mkmsgs

SEE ALSO
     exstr(1), gettxt(1), srchtxt(1), gettxt(3C), setlocale(3C)

									Page 2

[top]

List of man pages available for IRIX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net