srchtxt(1)srchtxt(1)NAMEsrchtxt - to display contents of, or to search for a text string in,
message data bases
SYNOPSISsrchtxt [-s] [-l locale] [-m msgfile, ...] [text]
OPTIONS
Suppress printing of the message sequence numbers of the messages being
displayed. Access files in the directory
/usr/lib/locale/locale/LC_MESSAGES. Access files specified by one or
more msgfiles. If msgfile contains a / character, then msgfile is
interpreted as a pathname; else, it will be assumed to be in the direc‐
tory determined as described above. For specifying more than one msg‐
file, use commas to separate the filenames.
OPERANDS
search for the text string specified by 'text' and display each one
that matches. 'text' can take the form of a regular expression (see
ed(1)).
If the -s option is not specified, the displayed text is pre‐
fixed by message sequence numbers. The message sequence numbers
are enclosed in angle brackets: <msgfile:msgnum>. name of the
file where the displayed text occured. sequence number in msg‐
file where the the displayed text occured. This display is in
the format used by gettxt(1) and gettxt(3C).
DESCRIPTION
The srchtxt utility is used to display all the text strings in message
data bases, or to search for a text string in message data bases (see
mkmsgs(1)). These databases are files in the directory
/usr/lib/locale/locale/LC_MESSAGES (see setlocale(3C)), unless a file
name given with the -m option contains a /. The directory locale can be
viewed as the name of the language in which the text strings are writ‐
ten. If the -l option is not specified, the files accessed will be
determined by the value of the environment variable LC_MESSAGES. If
LC_MESSAGES is not set, the files accessed will be determined by the
value of the environment variable LANG. If LANG is not set, the files
accessed will be in the directory /usr/lib/locale/C/LC_MESSAGES, which
contains default strings. If no text argument is present, then all the
text strings in the files accessed will be displayed.
EXAMPLES
The following examples show uses of srchtxt
Example 1:
If message files have been installed in a locale named french by using
mkmsgs(1), then you could display the entire set of text strings in the
french locale (/usr/lib/locale/french/LC_MESSAGES/*) by typing:
srchtxt-l french
Example 2:
If a set of error messages associated with the UNIX operating system
have been installed in the file UX in the french locale
(/usr/lib/locale/french/LC_MESSAGES/UX), then, using the value of the
LANG environment variable to determine the locale to be searched, you
could search that file in that locale for all messages dealing with
files by typing: LANG=french; export LANG srchtxt-m UX “[Ff]ichier”
If /usr/lib/locale/french/LC_MESSAGES/UX contained the following
strings: Erreur E/S\n Liste d'arguments trop longue\n Fichier inexis‐
tant\n Argument invalide\n Trop de fichiers ouverts\n Fichier trop
long\n Trop de liens\n Argument hors du domaine\n Identificateur sup‐
prime\n Etreinte fatale\n . . .
then the following strings would be displayed: <UX:3>Fichier inexis‐
tant\n <UX:5>Trop de fichiers ouverts\n <UX:6>Fichier trop long\n
Example 3:
If a set of error messages associated with the UNIX operating system
have been installed in the file UX and a set of error messages associ‐
ated with the INGRESS database product have been installed in the file
ingress, both in the german locale, then you could search for the pat‐
tern [Dd]atei in both the files UX and ingress in the german locale by
typing: srchtxt-l german -m UX, ingress "[Dd]atei"
FILES
default files created by mkmsgs(1) message files created by mkmsgs(1)SEE ALSOed(1), gettxt(1), mkmsgs(1).
gettxt(3C), setlocale(3C) in the “Programmer's Reference Manual”.
DIAGNOSTICS
The error messages produced by srchtxt are intended to be self-explana‐
tory. They indicate an error in the command line or encountered while
searching for a particular locale and/or message file.
srchtxt(1)
