Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ srchtxt(1) — mips UMIPS RISC/os 5.01

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

ed(1)

exstr(1)

gettxt(1)

mkmsgs(1)

gettxt(3C)

setlocale(3C)



SRCHTXT(1)          RISC/os Reference Manual           SRCHTXT(1)



NAME
     srchtxt - display contents of, or search for a text string
          in, message data bases

SYNOPSIS
     srchtxt [-s] [-l locale] [-m msgfile, ...]  [text]

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 data bases 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
     LCMESSAGES. If LCMESSAGES 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.

     The meanings of the options are as follows:

     -s          suppress printing of the message sequence
                 numbers of the messages being displayed

     -l locale   access files in the directory
                 /usr/lib/locale/locale/LC_MESSAGES.  If -m
                 msgfile is also supplied, locale is ignored for
                 msgfiles containing a /.

     -m msgfile  access file(s) specified by one or more
                 msgfiles.  If msgfile contains a / character,
                 then msgfile is interpreted as a pathname; oth-
                 erwise, it will be assumed to be in the direc-
                 tory determined as described above.  To specify
                 more than one msgfile, separate the file names
                 using commas.

     text        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
     prefixed by message sequence numbers. The message sequence
     numbers are enclosed in angle brackets:  <msgfile:msgnum>.




                        Printed 11/19/92                   Page 1





SRCHTXT(1)          RISC/os Reference Manual           SRCHTXT(1)



     msgfile     name of the file where the displayed text
                 occurred

     msgnum      sequence number in msgfile where the displayed
                 text occurred

     This display is in the format used by gettxt(1) and
     gettxt(3C).

INTERNATIONAL FUNCTIONALITY
     srchtxt can search the characters from supplementary code
     sets of text strings in the message handling facility for a
     text string.

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 error messages dealing with
          files by typing:

               LANG=french; export LANG
               srchtxt -m UX "[Ff]ichier"

          If /usr/lib/locale/french/s-1LC_MESSAGES/s-1UX con-
          tained the following strings:

               Erreur E/S\n
               Liste d'arguments trop longue\n
               Fichier inexistant\n
               Argument invalide\n
               Trop de fichiers ouverts\n
               Fichier trop long\n
               Trop de liens\n
               Argument hors du domaine\n
               Identificateur supprim\n



 Page 2                 Printed 11/19/92





SRCHTXT(1)          RISC/os Reference Manual           SRCHTXT(1)



               Etreinte fatale\n
                 .
                 .
                 .

          then the following strings would be displayed:
               <UX:3>Fichier inexistant\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 associated with the INGRESS
          data base product have been installed in the file
          ingress, both in the german locale, then you could
          search for the pattern [Dd]atei in both the files UX
          and ingress in the german locale by typing:

               srchtxt -l german -m UX,ingress "[Dd]atei"

FILES
     /usr/lib/locale/C/LC_MESSAGES/*         default files
                                             created by mkmsgs(1)

     /usr/lib/locale/locale/LC_MESSAGES/*    message files
                                             created by mkmsgs(1)

SEE ALSO
     ed(1), exstr(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-explanatory.  They indicate an error in the command
     line or errors encountered while searching for a particular
     locale and/or message file.
















                        Printed 11/19/92                   Page 3



Typewritten Software • bear@typewritten.org • Edmonds, WA 98026