gettxt(1) 맨 페이지 - 윈디하나의 솔라나라

개요

섹션
맨 페이지 이름
검색(S)

gettxt(1)

gettxt(1)                        User Commands                       gettxt(1)

NAME
       gettxt - retrieve a text string from a message database

SYNOPSIS
       gettxt msgfile : msgnum [dflt_msg]

DESCRIPTION
       gettxt  retrieves  a  text  string from a message file in the directory
       /usr/lib/locale/locale/LC_MESSAGES/. The directory name  locale  corre‐
       sponds  to the language in which the text strings are written; see set‐
       locale(3C).

       msgfile     Name of  the  file  in  the  directory  /usr/lib/locale/lo‐
                   cale/LC_MESSAGES  to retrieve msgnum from. The name of msg‐
                   file can be up to 14 characters in length, but may not con‐
                   tain either \0 (null) or the ASCII code for / (slash) or  :
                   (colon).


       msgnum      Sequence number of the string to retrieve from msgfile. The
                   strings  in  msgfile are numbered sequentially from 1 to n,
                   where n is the number of strings in the file.


       dflt_msg    Default string to be displayed if gettxt fails to  retrieve
                   msgnum  from  msgfile. Nongraphic characters must be repre‐
                   sented as alphabetic escape sequences.



       The text string to be retrieved is in the file msgfile, created by  the
       mkmsgs(1) utility and installed under the directory /usr/lib/locale/lo‐
       cale/LC_MESSAGES/.  You  control which directory is searched by setting
       the environment variable LC_MESSAGES. If LC_MESSAGES is  not  set,  the
       environment  variable  LANG will be used. If LANG is not set, the files
       containing  the  strings   are   under   the   directory   /usr/lib/lo‐
       cale/C/LC_MESSAGES/.


       If  gettxt  fails  to  retrieve a message in the requested language, it
       will try to retrieve the same  message  from  /usr/lib/locale/C/LC_MES‐
       SAGES/msgfile.  If this also fails, and if dflt_msg is present and non-
       null, then it will display the value of dflt_msg; if  dflt_msg  is  not
       present  or  is  null,  then  it  will  display the string "Message not
       found!!".

EXAMPLES
       Example 1 The environment variables LANG and LC_MESSAGES.



       If the environment variables LANG or LC_MESSAGES have not been  set  to
       other than their default values, the following example:


         example% gettxt UX:10 "hello world\n"




       will  try  to  retrieve the 10th message from /usr/lib/locale/C/UX/msg‐
       file. If the retrieval fails, the message "hello world," followed by  a
       newline, will be displayed.

ENVIRONMENT VARIABLES
       See  environ(7) for descriptions of the following environment variables
       that affect the execution of gettxt: LC_CTYPE and LC_MESSAGES.

       LC_CTYPE       Determines how gettxt handles characters. When  LC_CTYPE
                      is  set  to a valid value, gettxt can display and handle
                      text and filenames containing valid characters for  that
                      locale. gettxt can display and handle Extended UNIX Code
                      (EUC)  characters  where any individual character can be
                      1, 2, or 3 bytes wide. gettxt can also handle EUC  char‐
                      acters  of  1,  2, or more column widths. In the "C" lo‐
                      cale, only characters from ISO 8859-1 are valid.


       LC_MESSAGES    Determines how diagnostic and informative  messages  are
                      presented.  This  includes the language and style of the
                      messages, and the correct form of affirmative and  nega‐
                      tive responses. In the "C" locale, the messages are pre‐
                      sented  in  the default form found in the program itself
                      (in most cases, U.S. English).


FILES
       /usr/lib/locale/C/LC_MESSAGES/*

           default message files created by mkmsgs(1)


       /usr/lib/locale/locale/LC_MESSAGES/*

           message files for different languages created by mkmsgs(1)


USAGE
       The gettxt() APIs defined by the SVID standard are provided to  support
       historical  use,  and  to  support software requiring strict compliance
       with older standards. Otherwise, the use of the more modern and  widely
       supported gettext() APIs and tools is recommended.


       The  gettext(1)  command is the gettext replacement for the gettxt com‐
       mand.

ATTRIBUTES
       See attributes(7) for descriptions of the following attributes:

       tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE  TYPEAT‐
       TRIBUTE VALUE _ Availabilitytext/locale _ CSIEnabled


SEE ALSO
       exstr(1),  mkmsgs(1),  setlocale(3C),  gettxt(3C), attributes(7), envi‐
       ron(7)

HISTORY
       The gettxt command was added in Solaris 2.0.

Oracle Solaris 11.4               25 Nov 2024                        gettxt(1)
맨 페이지 내용의 저작권은 맨 페이지 작성자에게 있습니다.
RSS ATOM XHTML 5 CSS3