Unix/Linux Go Back    

RedHat 9 (Linux i386) - man page for xgettext (redhat section 1)

Linux & Unix Commands - Search Man Pages
Man Page or Keyword Search:   man
Select Man Page Set:       apropos Keyword Search (sections above)

XGETTEXT(1)				       GNU				      XGETTEXT(1)

       xgettext - extract gettext strings from source

       xgettext [OPTION] [INPUTFILE]...

       Extract translatable strings from given input files.

       Mandatory  arguments  to  long options are mandatory for short options too.  Similarly for
       optional arguments.

   Input file location:
       INPUTFILE ...
	      input files

       -f, --files-from=FILE
	      get list of input files from FILE

       -D, --directory=DIRECTORY
	      add DIRECTORY to list for input files search

       If input file is -, standard input is read.

   Output file location:
       -d, --default-domain=NAME
	      use NAME.po for output (instead of messages.po)

       -o, --output=FILE
	      write output to specified file

       -p, --output-dir=DIR
	      output files will be placed in directory DIR

       If output file is -, output is written to standard output.

   Choice of input file language:
       -L, --language=NAME
	      recognise the specified language (C, C++, ObjectiveC, PO, Python, Lisp,  EmacsLisp,
	      librep, Java, awk, YCP, Tcl, RST, Glade)

       -C, --c++
	      shorthand for --language=C++

       By default the language is guessed depending on the input file name extension.

   Operation mode:
       -j, --join-existing
	      join messages with existing file

       -x, --exclude-file=FILE.po
	      entries from FILE.po are not extracted

       -c, --add-comments[=TAG]
	      place comment block with TAG (or those preceding keyword lines) in output file

   Language=C/C++ specific options:
       -a, --extract-all
	      extract all strings

       -k, --keyword[=WORD]
	      additional  keyword  to  be  looked for (without WORD means not to use default key-

       -T, --trigraphs
	      understand ANSI C trigraphs for input

	      more detailed formatstring recognition result

   Output details:
       -e, --no-escape
	      do not use C escapes in output (default)

       -E, --escape
	      use C escapes in output, no extended chars

	      write PO file even if empty

       -i, --indent
	      write the .po file using indented style

	      do not write '#: filename:line' lines

       -n, --add-location
	      generate '#: filename:line' lines (default)

	      write out strict Uniforum conforming .po file

       -w, --width=NUMBER
	      set output page width

	      do not break long message lines, longer than the output page  width,  into  several

       -s, --sort-output
	      generate sorted output

       -F, --sort-by-file
	      sort output by file location

	      don't write header with `msgid ""' entry

	      set copyright holder in output

	      omit FSF copyright in output for foreign user

       -m, --msgstr-prefix[=STRING]
	      use STRING or "" as prefix for msgstr entries

       -M, --msgstr-suffix[=STRING]
	      use STRING or "" as suffix for msgstr entries

   Informative output:
       -h, --help
	      display this help and exit

       -V, --version
	      output version information and exit

       Written by Ulrich Drepper.

       Report bugs to <bug-gnu-gettext@gnu.org>.

       Copyright (C) 1995-1998, 2000-2002 Free Software Foundation, Inc.
       This  is  free software; see the source for copying conditions.	There is NO warranty; not

       The full documentation for xgettext is maintained as a Texinfo manual.  If  the	info  and
       xgettext programs are properly installed at your site, the command

	      info xgettext

       should give you access to the complete manual.

GNU gettext 0.11.4			    July 2002				      XGETTEXT(1)
Unix & Linux Commands & Man Pages : ©2000 - 2018 Unix and Linux Forums

All times are GMT -4. The time now is 10:05 AM.