From b685a652d386d1c27a52e31008f0e1da6e73aaad Mon Sep 17 00:00:00 2001
From: Bruno Haible gettext
offers one of these standards. See section 10 The Programmer's View.
+GNU gettext
offers one of these standards. See section 10 The Programmer's View.
@@ -557,10 +557,10 @@ contains all original program strings. It has sets of pointers to
exactly where in C sources each string is used. All translations
are set to empty. The letter t in `.pot´ marks this as
a Template PO file, not yet oriented towards any particular language.
-See section 4.1 Invoking the xgettext
Program, for more details about how one calls the
+See section 4.1 Invoking the xgettext
Program, for more details about how one calls the
xgettext
program. If you are really lazy, you might
be interested at working a lot more right away, and preparing the
-whole distribution setup (see section 12 The Maintainer's View). By doing so, you
+whole distribution setup (see section 12 The Maintainer's View). By doing so, you
spare yourself typing the xgettext
command, as make
should now generate the proper things automatically for you!
@@ -569,7 +569,7 @@ should now generate the proper things automatically for you!
The first time through, there is no `lang.po´ yet, so the
msgmerge
step may be skipped and replaced by a mere copy of
`package.pot´ to `lang.po´, where lang
-represents the target language. See section 5 Creating a New PO File for details.
+represents the target language. See section 5 Creating a New PO File for details.
@@ -577,7 +577,7 @@ Then comes the initial translation of messages. Translation in itself is a whole matter, still exclusively meant for humans, and whose complexity far overwhelms the level of this manual. Nevertheless, a few hints are given in some other chapter of this -manual (see section 11 The Translator's View). You will also find there indications +manual (see section 11 The Translator's View). You will also find there indications about how to contact translating teams, or becoming part of them, for sharing your translating concerns with others who target the same native language. @@ -594,14 +594,14 @@ of PO file format are taken care of for you, but you have to acquire some familiarity with PO mode itself. Besides main PO mode commands (see section 2.3 Main PO mode Commands), you should know how to move between entries (see section 2.4 Entry Positioning), and how to handle untranslated entries -(see section 6.4 Untranslated Entries). +(see section 6.4 Untranslated Entries).
If some common translations have already been saved into a compendium PO file, translators may use PO mode for initializing untranslated entries from the compendium, and also save selected translations into -the compendium, updating it (see section 6.11 Using Translation Compendia). Compendium files +the compendium, updating it (see section 6.11 Using Translation Compendia). Compendium files are meant to be exchanged between members of a given translation team.
@@ -647,8 +647,8 @@ out of recent C sources. The refreshing operation adjusts all references to C source locations for strings, since these strings move as programs are modified. Also,msgmerge
comments out as
obsolete, in `lang.po´, those already translated entries
-which are no longer used in the program sources (see section 6.5 Obsolete Entries). It finally discovers new strings and inserts them in
-the resulting PO file as untranslated entries (see section 6.4 Untranslated Entries). See section 6.1 Invoking the msgmerge
Program, for more information about what
+which are no longer used in the program sources (see section 6.5 Obsolete Entries). It finally discovers new strings and inserts them in
+the resulting PO file as untranslated entries (see section 6.4 Untranslated Entries). See section 6.1 Invoking the msgmerge
Program, for more information about what
msgmerge
really does.
@@ -678,7 +678,7 @@ distribution.
Once the PO file is complete and dependable, the msgfmt
program
is used for turning the PO file into a machine-oriented format, which
may yield efficient retrieval of translations by the programs of the
-package, whenever needed at runtime (see section 8.3 The Format of GNU MO Files). See section 8.1 Invoking the msgfmt
Program, for more information about all modes of execution
+package, whenever needed at runtime (see section 8.3 The Format of GNU MO Files). See section 8.1 Invoking the msgfmt
Program, for more information about all modes of execution
for the msgfmt
program.
@@ -688,7 +688,7 @@ with the GNU gettext
library, usually through the operation of
make
, given a suitable `Makefile´ exists for the project,
and the resulting executable is installed somewhere users will find it.
The MO files themselves should also be properly installed. Given the
-appropriate environment variables are set (see section 9.3 Magic for End Users), the
+appropriate environment variables are set (see section 9.3 Magic for End Users), the
program should localize itself automatically, whenever it executes.
diff --git a/doc/gettext_10.html b/doc/gettext_10.html
index 9015f50d3..09949bbfc 100644
--- a/doc/gettext_10.html
+++ b/doc/gettext_10.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
-
One aim of the current message catalog implementation provided by @@ -28,9 +28,9 @@ later explain our solution of this dilemma. -
catgets
catgets
@@ -63,9 +63,9 @@ therefore part of all Unix implementation (implementations, which are -
@@ -78,7 +78,7 @@ for the functions and the needed definitions are in the
-
+
catopen
is used like in this:
open
.
-
+
This handle is of course used in the catgets
function which can
be used like this:
@@ -129,7 +129,7 @@ should better be const char *
, but the standard is published in
- + The last of these function functions is used and behaves as expected:
@@ -144,9 +144,9 @@ After this nocatgets
call using the descriptor is legal anymore.
-catgets
Interface?!catgets
Interface?!@@ -165,9 +165,9 @@ more easy to manage.
-gettext
gettext
@@ -182,7 +182,7 @@ The main points about this solution is that it does not follow the method of normal file handling (open-use-close) and that it does not burden the programmer so many task, especially the unique key handling. Of course here also a unique key is needed, but this key is the message -itself (how long or short it is). See section 10.3 Comparing the Two Interfaces for a more +itself (how long or short it is). See section 10.3 Comparing the Two Interfaces for a more detailed comparison of the two methods.
@@ -196,9 +196,9 @@ in using this library will be interested in this description. -@@ -267,11 +267,11 @@ your language.
-@@ -345,9 +345,9 @@ unreliabilities.
-@@ -385,10 +385,10 @@ The value of the locale is determined through
-gettext
usesgettext
uses@@ -420,7 +420,7 @@ recommended that all msgids be US-ASCII strings.
bind_textdomain_codeset
function can be used to specify the
output character set for message catalogs for domain domainname.
The codeset argument must be a valid codeset name which can be used
@@ -452,9 +452,9 @@ global variable errno is set accordingly.
-@@ -574,7 +574,7 @@ purpose.
ngettext
function is similar to the gettext
function
as it finds the message catalogs in the same way. But it takes two
extra arguments. The msgid1 parameter must contain the singular
@@ -604,7 +604,7 @@ Please note that the numeric value n has to be passed to the
dngettext
is similar to the dgettext
function in the
way the message catalog is selected. The difference is that it takes
two extra parameter to provide the correct plural form. These two
@@ -615,7 +615,7 @@ parameters are handled in the same way ngettext
handles them.
dcngettext
is similar to the dcgettext
function in the
way the message catalog is selected. The difference is that it takes
two extra parameter to provide the correct plural form. These two
@@ -640,9 +640,9 @@ possibility of extensions to not prevent the use of new languages).
-
-
-
+
+
+
The information about the plural form selection has to be stored in the
header entry of the PO file (the one with the empty msgid
string).
The plural form information looks like this:
@@ -668,7 +668,7 @@ value of nplurals
.
- + The following rules are known at this point. The language with families are listed. But this does not necessarily mean the information can be generalized for the whole family (as can be easily seen in the table @@ -876,11 +876,11 @@ Slovenian -
gettext
in GUI programsgettext
in GUI programs@@ -957,7 +957,7 @@ fine:
char * @@ -1032,9 +1032,9 @@ quite some memory and disk space by doing this. -10.2.7 Optimization of the *gettext functions
+10.2.7 Optimization of the *gettext functions
@@ -1087,10 +1087,10 @@ find the result through a single cache lookup.
-10.3 Comparing the Two Interfaces
+10.3 Comparing the Two Interfaces
@@ -1140,7 +1140,7 @@ by#include <libintl.h> @@ -1155,9 +1155,9 @@ can use any that becomes available.- + The same procedure can be done for the
@@ -1234,12 +1234,12 @@ little bit. But it is not impossible to overcome.gettext_noop
invocations -(see section 3.5 Special Cases of Translatable Strings). One usually definesgettext_noop
as a +(see section 3.6 Special Cases of Translatable Strings). One usually definesgettext_noop
as a no-op macro. So you should consider the following code for your project:-
catgets
allows same original entry to have different translations, butgettext
has another, scalable approach for solving ambiguities -of this kind: See section 10.2.2 Solving Ambiguities. +of this kind: See section 10.2.2 Solving Ambiguities.10.4 Using libintl.a in own programs
+10.4 Using libintl.a in own programs
Starting with version 0.9.4 the library
-libintl.h
should be @@ -1250,7 +1250,7 @@ and the library in directories selected using the$(prefix)
.10.5 Being a
+gettext
grok10.5 Being a
gettext
grokTo fully exploit the functionality of the GNU
gettext
library it @@ -1263,7 +1263,7 @@ is a list comments:
dcgettext
function as long as no new catalog is loaded. But
if dcgettext
is not called the program also cannot find the
-LANGUAGE
variable be changed (see section 10.2.7 Optimization of the *gettext functions). A
+LANGUAGE
variable be changed (see section 10.2.7 Optimization of the *gettext functions). A
solution for this is very easy. Include the following code in the
language switching function.
@@ -1327,7 +1327,7 @@ language switching function.
}
-
+
The variable _nl_msg_cat_cntr
is defined in `loadmsgcat.c´.
You don't need to know what this is for. But it can be used to detect
whether a gettext
implementation is GNU gettext and not non-GNU
@@ -1337,11 +1337,11 @@ system's native gettext implementation.
-There are two competing methods for language independent messages: @@ -1373,7 +1373,7 @@ see the Programming for Internationalization FAQ.
-catgets
catgets
There have been a few discussions of late on the use of @@ -1418,7 +1418,7 @@ of all Unix systems.
-Now it seems kind of wasteful to me to have two different systems @@ -1463,7 +1463,7 @@ the future.
-X/Open agreed very late on the standard form so that many diff --git a/doc/gettext_11.html b/doc/gettext_11.html index eec39cdc8..66baaee52 100644 --- a/doc/gettext_11.html +++ b/doc/gettext_11.html @@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->-
Free software is going international! The Translation Project is a way @@ -92,7 +92,7 @@ you can work on.
-This is now official, GNU is going international! Here is the @@ -142,7 +142,7 @@ document, please e-mail to `translation@iro.umontreal.ca´.
-Facing this internationalization effort, a few users expressed their @@ -219,7 +219,7 @@ software. -
On a larger scale, the true solution would be to organize some kind of @@ -263,7 +263,7 @@ reaches the Translation Project coordinator. -
I also think GNU will need sooner than it thinks, that someone setup @@ -288,7 +288,7 @@ overwhelming task, the time to put delegations in place.
-I suggest we look for volunteer coordinators/editors for individual @@ -351,7 +351,7 @@ consistent. -
Taking French for example, there are a few sub-cultures around computers @@ -373,7 +373,7 @@ means soon!
-I expect the next big changes after the official release. Please note @@ -410,7 +410,7 @@ this also seems to work). -
If we get any inquiries about GNU gettext
, send them on to:
@@ -464,7 +464,7 @@ subscribe as they see fit, as long as each team is represented in it.
There will surely be some discussion about this messages after the diff --git a/doc/gettext_12.html b/doc/gettext_12.html index d05ce12fd..b29f5ec26 100644 --- a/doc/gettext_12.html +++ b/doc/gettext_12.html @@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->-
The maintainer of a package has many responsibilities. One of them is ensuring that the package will install easily on many platforms, -and that the magic we described earlier (see section 9 The User's View) will work +and that the magic we described earlier (see section 9 The User's View) will work for installers and end users.
@@ -52,7 +52,7 @@ for changes. -
Some free software packages are distributed as tar
files which unpack
@@ -85,11 +85,11 @@ use this as an opportunity to unflatten their package structure.
@@ -186,7 +186,7 @@ never try to solve a team's problem on your own.
-gettextize
Programgettextize
ProgramSome files are consistently and identically needed in every package @@ -196,8 +196,8 @@ in your package. This program has the following synopsis:
gettextize [ option... ] [ directory ] @@ -213,8 +213,8 @@ and accepts the following options:
gettext
code
available on the system, but it might disturb some mechanism the
@@ -225,13 +225,13 @@ maintainer is used to apply to the sources. Because running
gettextize
logs all changes (file additions, modifications ans removals) in a
file called `ChangeLog´ in each affected directory.
@@ -352,7 +352,7 @@ changes needed in each.
So, here comes a list of files, each one followed by a description of
all alterations it needs. Many examples are taken out from the GNU
-gettext
0.11.1 distribution itself, or from the GNU
+gettext
0.11.2 distribution itself, or from the GNU
hello
distribution (http://www.franken.de/users/gnu/ke/hello
or http://www.gnu.franken.de/ke/hello/) You may indeed
refer to the source code of the GNU gettext
and GNU hello
@@ -363,9 +363,9 @@ gettext functionality.
-
@@ -394,16 +394,24 @@ src/xgettext.c
Hash-marked comments and white lines are ignored. All other lines list those source files containing strings marked for translation -(see section 3.2 How Marks Appear in Sources), in a notation relative to the top level +(see section 3.3 How Marks Appear in Sources), in a notation relative to the top level of your whole distribution, rather than the location of the `POTFILES.in´ file itself.
+
+When a C file is automatically generated by a tool, like flex
or
+bison
, that doesn't introduce translatable strings by itself,
+it is recommended to list in `po/POTFILES.in´ the real source file
+(ending in `.l´ in the case of flex
, or in `.y´ in the
+case of bison
), not the generated C file.
+
@@ -425,14 +433,14 @@ that these languages are currently supported by your package. If you
want to further restrict, at installation time, the set of installed
languages, this should not be done by modifying the `LINGUAS´ file,
but rather by using the LINGUAS
environment variable
-(see section 9.2 Magic for Installers).
+(see section 9.2 Magic for Installers).
@@ -452,8 +460,8 @@ needing to mess with `po/Makefile.in.in´.
-
-
+
+
GNU gettext comes with a `Rules-quot´ file, containing rules for
building catalogs `en@quot.po´ and `en@boldquot.po´. The
effect of `en@quot.po´ is that people who set their LANGUAGE
@@ -471,7 +479,7 @@ GUI programs. To enable it, similarly add en@boldquot
to the
`configure.in´ or `configure.ac´ - this is the source from which
@@ -482,14 +490,14 @@ GUI programs. To enable it, similarly add en@boldquot
to the
PACKAGE=gettext -VERSION=0.11.1 +VERSION=0.11.2 AC_DEFINE_UNQUOTED(PACKAGE, "$PACKAGE") AC_DEFINE_UNQUOTED(VERSION, "$VERSION") AC_SUBST(PACKAGE) @@ -500,13 +508,13 @@ or, if you are using GNUautomake
, by a line like this:-AM_INIT_AUTOMAKE(gettext, 0.11.1) +AM_INIT_AUTOMAKE(gettext, 0.11.2)Of course, you replace `gettext´ with the name of your package, -and `0.11.1´ by its version numbers, exactly as they +and `0.11.2´ by its version numbers, exactly as they should appear in the packagedtar
file name of your distribution -(`gettext-0.11.1.tar.gz´, here). +(`gettext-0.11.2.tar.gz´, here).
intl/Makefile
to the AC_OUTPUT
line.
-If you haven't suppressed the `intl/´ subdirectory, @@ -587,9 +595,9 @@ AC_CONFIG_AUX_DIR([subdir]) -
@@ -639,9 +647,9 @@ piece of m4
code will be the same for all projects using GNU
@@ -655,7 +663,7 @@ independently from the `intl/´ directory.
-Here are a few modifications you need to make to your main, top-level @@ -742,7 +750,7 @@ to `Makefile.am´ are already made by running `gettextize&ac
-Some of the modifications made in the main `Makefile.in´ will @@ -862,11 +870,11 @@ dist: Makefile $(DISTFILES) -
@@ -903,7 +911,7 @@ to 0 in C preprocessor expressions.
-
+
`gettext.h´ is a convenience header file for conditional use of
`<libintl.h>´, depending on the ENABLE_NLS
macro. If
ENABLE_NLS
is set, it includes `<libintl.h>´; otherwise it
@@ -942,9 +950,9 @@ package that needs it should contain a copy of it on its own.
@@ -957,10 +965,10 @@ The primary macro is, of course, AM_GNU_GETTEXT
.
-
-
+
The AM_GNU_GETTEXT
macro tests for the presence of the GNU gettext
function family in either the C library or a separate libintl
library (shared or static libraries are both supported) or in the package's
@@ -1023,7 +1031,7 @@ The complexities that AM_GNU_GETTEXT
deals with are the following:
gettext
in the C library, for example
glibc. Some have it in a separate library libintl
. GNU libintl
might have been installed as part of the GNU gettext
package.
@@ -1059,10 +1067,10 @@ and LTLIBINTL
variables.
-
-
+
The AM_ICONV
macro tests for the presence of the POSIX
iconv
function family in either the C library or a separate
libiconv
library. If found, it sets the am_cv_func_iconv
@@ -1086,7 +1094,7 @@ The complexities that AM_ICONV
deals with are the following:
iconv
in the C library, for example
glibc. Some have it in a separate library libiconv
, for example
OSF/1 or FreeBSD. Regardless of the operating system, GNU libiconv
diff --git a/doc/gettext_13.html b/doc/gettext_13.html
index 5d09046c5..ac72cf2f7 100644
--- a/doc/gettext_13.html
+++ b/doc/gettext_13.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
-
While the presentation of gettext
focuses mostly on C and
@@ -23,10 +23,10 @@ approach.
-
@@ -96,7 +96,7 @@ The language's library should have a string formatting facility where the arguments of a format string are denoted by a positional number or a name. This is needed because for some languages and some messages with more than one substitutable argument, the translation will need to -output the substituted arguments in different order. See section 3.4 Special Comments preceding Keywords. +output the substituted arguments in different order. See section 3.5 Special Comments preceding Keywords.
gettext
's `intl/´ directory in
-your package, as described in section 12 The Maintainer's View. This allows you to
+your package, as described in section 12 The Maintainer's View. This allows you to
have internationalization on all kinds of platforms. Note that when you
then distribute your package, it legally falls under the GNU General
Public License, and the GNU project will be glad about your contribution
@@ -150,7 +150,7 @@ and plural handling).
-For the programmer, the general procedure is the same as for the C @@ -163,7 +163,7 @@ underlying language runtime.
-The translator works exactly as in the C language case. The only @@ -174,7 +174,7 @@ strings.
-
For the maintainer, the general procedure differs from the C language
@@ -194,7 +194,7 @@ invokes the AM_GNU_GETTEXT
autoconf macro via
XGETTEXT_OPTIONS
-variable in `po/Makevars´ (see section 12.4.3 `Makefile´ pieces in `po/´) should be adjusted to
+variable in `po/Makevars´ (see section 12.4.3 `Makefile´ pieces in `po/´) should be adjusted to
match the xgettext
options for that particular programming language.
If the package uses more than one programming language with gettext
support, it becomes necessary to change the POT file construction rule
@@ -205,13 +205,13 @@ that language, and to combine the resulting files using msgcat
.
-gettext
, ngettext
programs
TEXTDOMAIN
TEXTDOMAINDIR
gettext
, ngettext
programs
TEXTDOMAIN
TEXTDOMAINDIR
I18N3
defined at build time, no translation.
-TranslateResourceStrings
function in the gettext
-13.5.13 wxWindows library
+13.5.13 wxWindows library
@@ -1165,10 +1165,10 @@ yes
-13.5.14 YCP - YaST2 scripting language
+13.5.14 YCP - YaST2 scripting language
@@ -1232,10 +1232,10 @@ fully portable
-13.5.15 Tcl - Tk's scripting language
+13.5.15 Tcl - Tk's scripting language
@@ -1313,9 +1313,9 @@ argument is given.
-13.5.16 Perl
+13.5.16 Perl
@@ -1380,9 +1380,9 @@ use
-13.5.17 PHP Hypertext Preprocessor
+13.5.17 PHP Hypertext Preprocessor
@@ -1446,9 +1446,9 @@ On platforms without gettext, the functions are not available.
-13.5.18 Pike
+13.5.18 Pike
@@ -1512,7 +1512,7 @@ On platforms without gettext, the functions are not available.
-13.6 Internationalizable Data
+13.6 Internationalizable Data
Here is a list of other data formats which can be internationalized
@@ -1522,7 +1522,7 @@ using GNU gettext.
-
13.6.1 POT - Portable Object Template
+13.6.1 POT - Portable Object Template
@@ -1541,9 +1541,9 @@ gettext
-13.6.2 Resource String Table
+13.6.2 Resource String Table
@@ -1563,7 +1563,7 @@ fpk
-13.6.3 Glade - GNOME user interface description
+13.6.3 Glade - GNOME user interface description
diff --git a/doc/gettext_14.html b/doc/gettext_14.html
index 15fe7aa63..e31698ee9 100644
--- a/doc/gettext_14.html
+++ b/doc/gettext_14.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - 14 Concluding Remarks
@@ -10,7 +10,7 @@ Go to the first, previous
-
14 Concluding Remarks
+14 Concluding Remarks
We would like to conclude this GNU gettext
manual by presenting
@@ -22,9 +22,9 @@ about Native Language Support matters.
-
14.1 History of GNU gettext
+14.1 History of GNU gettext
@@ -121,10 +121,10 @@ manipulating PO files.
-14.2 Related Readings
+14.2 Related Readings
diff --git a/doc/gettext_15.html b/doc/gettext_15.html
index c5e280cea..d3e3bbd07 100644
--- a/doc/gettext_15.html
+++ b/doc/gettext_15.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - A Language Codes
@@ -10,10 +10,10 @@ Go to the first, previous
-
A Language Codes
+A Language Codes
@@ -201,6 +201,9 @@ Interlingue.
- `ik´
-
Inupiak.
+
- `io´
+
-
+Ido.
- `is´
-
Icelandic.
@@ -213,7 +216,7 @@ Inuktitut.
- `ja´
-
Japanese.
-
- `jw´
+
- `jv´
-
Javanese.
- `ka´
@@ -498,6 +501,9 @@ Vietnamese.
- `vo´
-
Volapük; Volapuk.
+
- `wa´
+
-
+Walloon.
- `wo´
-
Wolof.
diff --git a/doc/gettext_16.html b/doc/gettext_16.html
index 6ac89be64..98288dcd0 100644
--- a/doc/gettext_16.html
+++ b/doc/gettext_16.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - B Country Codes
@@ -10,10 +10,10 @@ Go to the first, previous
-
B Country Codes
+B Country Codes
diff --git a/doc/gettext_17.html b/doc/gettext_17.html
index d6757e3ec..dd06ecb50 100644
--- a/doc/gettext_17.html
+++ b/doc/gettext_17.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - Program Index
@@ -10,7 +10,7 @@ Go to the first, previous
-
Program Index
+Program Index
Jump to:
@@ -24,33 +24,33 @@ Jump to:
g
-- gettext, gettext
-
- gettextize
+
- gettext, gettext
+
- gettextize
m
-- msgattrib
-
- msgcat
-
- msgcmp
-
- msgcomm
-
- msgconv
-
- msgen
-
- msgexec
-
- msgfilter
-
- msgfmt
-
- msggrep
-
- msginit
-
- msgmerge
-
- msgunfmt
-
- msguniq
+
- msgattrib
+
- msgcat
+
- msgcmp
+
- msgcomm
+
- msgconv
+
- msgen
+
- msgexec
+
- msgfilter
+
- msgfmt
+
- msggrep
+
- msginit
+
- msgmerge
+
- msgunfmt
+
- msguniq
n
-- ngettext, ngettext
+
- ngettext, ngettext
x
-- xgettext
+
- xgettext
diff --git a/doc/gettext_18.html b/doc/gettext_18.html
index 168539928..7a6773e6c 100644
--- a/doc/gettext_18.html
+++ b/doc/gettext_18.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - Option Index
@@ -10,7 +10,7 @@ Go to the first, previous
-
Option Index
+Option Index
Jump to:
@@ -18,414 +18,426 @@ Jump to:
-
-- --add-comments,
xgettext
option
- - --add-location,
msgattrib
option
- - --add-location,
msgcat
option
- - --add-location,
msgcomm
option
- - --add-location,
msgconv
option
- - --add-location,
msgen
option
- - --add-location,
msgfilter
option
- - --add-location,
msggrep
option
- - --add-location,
msgmerge
option
- - --add-location,
msguniq
option
- - --add-location,
xgettext
option
- - --alignment,
msgfmt
option
- - --backup,
msgmerge
option
- - --c++,
xgettext
option
- - --check,
msgfmt
option
- - --check-accelerators,
msgfmt
option
- - --check-compatibility,
msgfmt
option
- - --check-domain,
msgfmt
option
- - --check-format,
msgfmt
option
- - --check-header,
msgfmt
option
- - --clear-fuzzy,
msgattrib
option
- - --clear-obsolete,
msgattrib
option
- - --compendium,
msgmerge
option
- - --copy,
gettextize
option
- - --copyright-holder,
xgettext
option
- - --debug,
xgettext
option
- - --default-domain,
xgettext
option
- - --directory,
msgattrib
option
- - --directory,
msgcat
option
- - --directory,
msgcmp
option
- - --directory,
msgcomm
option
- - --directory,
msgconv
option
- - --directory,
msgen
option
- - --directory,
msgexec
option
- - --directory,
msgfilter
option
- - --directory,
msgfmt
option
- - --directory,
msggrep
option
- - --directory,
msgmerge
option
- - --directory,
msguniq
option
- - --directory,
xgettext
option
- - --domain,
msggrep
option
- - --exclude-file,
xgettext
option
- - --expression,
msgfilter
option
- - --extended-regexp,
msggrep
option
- - --extract-all,
xgettext
option
- - --file,
msgfilter
option
- - --file,
msggrep
option
- - --files-from,
msgcat
option
- - --files-from,
msgcomm
option
- - --files-from,
xgettext
option
- - --fixed-strings,
msggrep
option
- - --force,
gettextize
option
- - --force-po,
msgattrib
option
- - --force-po,
msgcat
option
- - --force-po,
msgcomm
option
- - --force-po,
msgconv
option
- - --force-po,
msgen
option
- - --force-po,
msgfilter
option
- - --force-po,
msggrep
option
- - --force-po,
msgmerge
option
- - --force-po,
msgunfmt
option
- - --force-po,
msguniq
option
- - --force-po,
xgettext
option
- - --foreign-user,
xgettext
option
- - --fuzzy,
msgattrib
option
- - --help,
gettextize
option
- - --help,
msgattrib
option
- - --help,
msgcat
option
- - --help,
msgcmp
option
- - --help,
msgcomm
option
- - --help,
msgconv
option
- - --help,
msgen
option
- - --help,
msgexec
option
- - --help,
msgfilter
option
- - --help,
msgfmt
option
- - --help,
msggrep
option
- - --help,
msginit
option
- - --help,
msgmerge
option
- - --help,
msgunfmt
option
- - --help,
msguniq
option
- - --help,
xgettext
option
- - --ignore-case,
msggrep
option
- - --indent,
msgattrib
option
- - --indent,
msgcat
option
- - --indent,
msgcomm
option
- - --indent,
msgconv
option
- - --indent,
msgen
option
- - --indent,
msgfilter
option
- - --indent,
msggrep
option
- - --indent,
msgmerge
option
- - --indent,
msgunfmt
option
- - --indent,
msguniq
option
- - --indent,
xgettext
option
- - --input,
msgexec
option
- - --input,
msgfilter
option
- - --input,
msginit
option
- - --intl,
gettextize
option
- - --java,
msgfmt
option
- - --java,
msgunfmt
option
- - --java2,
msgfmt
option
- - --join-existing,
xgettext
option
- - --keep-header,
msgfilter
option
- - --keyword,
xgettext
option
- - --language,
xgettext
option
- - --less-than,
msgcat
option
- - --less-than,
msgcomm
option
- - --locale,
msgfmt
option, --locale, msgfmt
option
- - --locale,
msginit
option
- - --locale,
msgunfmt
option, --locale, msgunfmt
option
- - --location,
msggrep
option
- - --more-than,
msgcat
option
- - --more-than,
msgcomm
option
- - --msgid,
msggrep
option
- - --msgstr,
msggrep
option
- - --msgstr-prefix,
xgettext
option
- - --msgstr-suffix,
xgettext
option
- - --multi-domain,
msgcmp
option
- - --multi-domain,
msgmerge
option
- - --no-changelog,
gettextize
option
- - --no-fuzzy,
msgattrib
option
- - --no-hash,
msgfmt
option
- - --no-location,
msgattrib
option
- - --no-location,
msgcat
option
- - --no-location,
msgcomm
option
- - --no-location,
msgconv
option
- - --no-location,
msgen
option
- - --no-location,
msgfilter
option
- - --no-location,
msggrep
option
- - --no-location,
msgmerge
option
- - --no-location,
msguniq
option
- - --no-location,
xgettext
option
- - --no-obsolete,
msgattrib
option
- - --no-translator,
msginit
option
- - --obsolete,
msgattrib
option
- - --omit-header,
msgcomm
option
- - --omit-header,
xgettext
option
- - --only-fuzzy,
msgattrib
option
- - --only-obsolete,
msgattrib
option
- - --output,
xgettext
option
- - --output-dir,
xgettext
option
- - --output-file,
msgattrib
option
- - --output-file,
msgcat
option
- - --output-file,
msgcomm
option
- - --output-file,
msgconv
option
- - --output-file,
msgen
option
- - --output-file,
msgfilter
option
- - --output-file,
msgfmt
option
- - --output-file,
msggrep
option
- - --output-file,
msginit
option
- - --output-file,
msgmerge
option
- - --output-file,
msgunfmt
option
- - --output-file,
msguniq
option
- - --quiet,
msgfilter
option
- - --quiet,
msgmerge
option
- - --regexp=,
msggrep
option
- - --repeated,
msguniq
option
- - --resource,
msgfmt
option
- - --resource,
msgunfmt
option
- - --set-fuzzy,
msgattrib
option
- - --set-obsolete,
msgattrib
option
- - --silent,
msgfilter
option
- - --silent,
msgmerge
option
- - --sort-by-file,
msgattrib
option
- - --sort-by-file,
msgcat
option
- - --sort-by-file,
msgcomm
option
- - --sort-by-file,
msgconv
option
- - --sort-by-file,
msgen
option
- - --sort-by-file,
msgfilter
option
- - --sort-by-file,
msggrep
option
- - --sort-by-file,
msgmerge
option
- - --sort-by-file,
msguniq
option
- - --sort-by-file,
xgettext
option
- - --sort-output,
msgattrib
option
- - --sort-output,
msgcat
option
- - --sort-output,
msgcomm
option
- - --sort-output,
msgconv
option
- - --sort-output,
msgen
option
- - --sort-output,
msgfilter
option
- - --sort-output,
msggrep
option
- - --sort-output,
msgmerge
option
- - --sort-output,
msgunfmt
option
- - --sort-output,
msguniq
option
- - --sort-output,
xgettext
option
- - --statistics,
msgfmt
option
- - --strict,
msgattrib
option
- - --strict,
msgcat
option
- - --strict,
msgcomm
option
- - --strict,
msgconv
option
- - --strict,
msgen
option
- - --strict,
msgfilter
option
- - --strict,
msgfmt
option
- - --strict,
msggrep
option
- - --strict,
msgmerge
option
- - --strict,
msgunfmt
option
- - --strict,
msguniq
option
- - --strict,
xgettext
option
- - --suffix,
msgmerge
option
- - --tcl,
msgfmt
option
- - --tcl,
msgunfmt
option
- - --to-code,
msgcat
option
- - --to-code,
msgconv
option
- - --to-code,
msguniq
option
- - --translated,
msgattrib
option
- - --trigraphs,
xgettext
option
- - --unique,
msgcat
option
- - --unique,
msgcomm
option
- - --unique,
msguniq
option
- - --untranslated,
msgattrib
option
- - --update,
msgmerge
option
- - --use-first,
msgcat
option
- - --use-first,
msguniq
option
- - --use-fuzzy,
msgfmt
option
- - --verbose,
msgfmt
option
- - --verbose,
msgmerge
option
- - --verbose,
msgunfmt
option
- - --version,
gettextize
option
- - --version,
msgattrib
option
- - --version,
msgcat
option
- - --version,
msgcmp
option
- - --version,
msgcomm
option
- - --version,
msgconv
option
- - --version,
msgen
option
- - --version,
msgexec
option
- - --version,
msgfilter
option
- - --version,
msgfmt
option
- - --version,
msggrep
option
- - --version,
msginit
option
- - --version,
msgmerge
option
- - --version,
msgunfmt
option
- - --version,
msguniq
option
- - --version,
xgettext
option
- - --width,
msgattrib
option
- - --width,
msgcat
option
- - --width,
msgcomm
option
- - --width,
msgconv
option
- - --width,
msgen
option
- - --width,
msgfilter
option
- - --width,
msggrep
option
- - --width,
msginit
option
- - --width,
msgmerge
option
- - --width,
msgunfmt
option
- - --width,
msguniq
option
- - --width,
xgettext
option
- - -<,
msgcat
option
- - -<,
msgcomm
option
- - ->,
msgcat
option
- - ->,
msgcomm
option
- - -a,
msgfmt
option
- - -a,
xgettext
option
- - -c,
gettextize
option
- - -c,
msgfmt
option
- - -C,
msgfmt
option
- - -C,
msgmerge
option
- - -C,
xgettext
option
- - -c,
xgettext
option
- - -D,
msgattrib
option
- - -D,
msgcat
option
- - -D,
msgcmp
option
- - -D,
msgcomm
option
- - -D,
msgconv
option
- - -D,
msgen
option
- - -D,
msgexec
option
- - -D,
msgfilter
option
- - -D,
msgfmt
option
- - -d,
msgfmt
option, -d, msgfmt
option
- - -D,
msggrep
option
- - -D,
msgmerge
option
- - -d,
msgunfmt
option
- - -d,
msguniq
option
- - -D,
msguniq
option
- - -D,
xgettext
option
- - -d,
xgettext
option
- - -e,
msgfilter
option
- - -E,
msggrep
option
- - -e,
msggrep
option
- - -f,
gettextize
option
- - -F,
msgattrib
option
- - -F,
msgcat
option
- - -f,
msgcat
option
- - -F,
msgcomm
option
- - -f,
msgcomm
option
- - -F,
msgconv
option
- - -F,
msgen
option
- - -F,
msgfilter
option
- - -f,
msgfilter
option
- - -f,
msgfmt
option
- - -f,
msggrep
option
- - -F,
msggrep
option
- - -F,
msgmerge
option
- - -F,
msguniq
option
- - -f,
xgettext
option
- - -F,
xgettext
option
- - -h,
msgattrib
option
- - -h,
msgcat
option
- - -h,
msgcmp
option
- - -h,
msgcomm
option
- - -h,
msgconv
option
- - -h,
msgen
option
- - -h,
msgexec
option
- - -h,
msgfilter
option
- - -h,
msgfmt
option
- - -h,
msggrep
option
- - -h,
msginit
option
- - -h,
msgmerge
option
- - -h,
msgunfmt
option
- - -h,
msguniq
option
- - -h,
xgettext
option
- - -i,
msgattrib
option
- - -i,
msgcat
option
- - -i,
msgcomm
option
- - -i,
msgconv
option
- - -i,
msgen
option
- - -i,
msgexec
option
- - -i,
msgfilter
option
- - -i,
msggrep
option
- - -i,
msginit
option
- - -i,
msgmerge
option
- - -i,
msgunfmt
option
- - -i,
msguniq
option
- - -i,
xgettext
option
- - -j,
msgfmt
option
- - -j,
msgunfmt
option
- - -j,
xgettext
option
- - -K,
msggrep
option
- - -k,
xgettext
option
- - -l,
msgfmt
option, -l, msgfmt
option
- - -l,
msginit
option
- - -l,
msgunfmt
option, -l, msgunfmt
option
- - -L,
xgettext
option
- - -m,
msgcmp
option
- - -M,
msggrep
option
- - -m,
msgmerge
option
- - -m,
xgettext
option
- - -M,
xgettext
option
- - -n,
msgattrib
option
- - -n,
msgcat
option
- - -n,
msgcomm
option
- - -n,
msgfilter
option
- - -N,
msggrep
option
- - -n,
msguniq
option
- - -n,
xgettext
option
- - -o,
msgattrib
option
- - -o,
msgcat
option
- - -o,
msgcomm
option
- - -o,
msgconv
option
- - -o,
msgen
option
- - -o,
msgfilter
option
- - -o,
msgfmt
option
- - -o,
msggrep
option
- - -o,
msginit
option
- - -o,
msgmerge
option
- - -o,
msgunfmt
option
- - -o,
msguniq
option
- - -o,
xgettext
option
- - -p,
xgettext
option
- - -q,
msgmerge
option
- - -r,
msgfmt
option
- - -r,
msgunfmt
option
- - -s,
msgattrib
option
- - -s,
msgcat
option
- - -s,
msgcomm
option
- - -s,
msgconv
option
- - -s,
msgen
option
- - -s,
msgfilter
option
- - -s,
msgmerge
option
- - -s,
msgunfmt
option
- - -s,
msguniq
option
- - -s,
xgettext
option
- - -t,
msgcat
option
- - -t,
msgconv
option
- - -T,
msggrep
option
- - -t,
msguniq
option
- - -T,
xgettext
option
- - -u,
msgcat
option
- - -u,
msgcomm
option
- - -U,
msgmerge
option
- - -u,
msguniq
option
- - -V,
msgattrib
option
- - -V,
msgcat
option
- - -V,
msgcmp
option
- - -V,
msgcomm
option
- - -V,
msgconv
option
- - -V,
msgen
option
- - -V,
msgexec
option
- - -V,
msgfilter
option
- - -v,
msgfmt
option
- - -V,
msgfmt
option
- - -V,
msggrep
option
- - -V,
msginit
option
- - -V,
msgmerge
option
- - -v,
msgmerge
option
- - -v,
msgunfmt
option
- - -V,
msgunfmt
option
- - -V,
msguniq
option
- - -V,
xgettext
option
- - -w,
msgattrib
option
- - -w,
msgcat
option
- - -w,
msgcomm
option
- - -w,
msgconv
option
- - -w,
msgen
option
- - -w,
msgfilter
option
- - -w,
msggrep
option
- - -w,
msginit
option
- - -w,
msgmerge
option
- - -w,
msgunfmt
option
- - -w,
msguniq
option
- - -w,
xgettext
option
- - -x,
xgettext
option
+ - --add-comments,
xgettext
option
+ - --add-location,
msgattrib
option
+ - --add-location,
msgcat
option
+ - --add-location,
msgcomm
option
+ - --add-location,
msgconv
option
+ - --add-location,
msgen
option
+ - --add-location,
msgfilter
option
+ - --add-location,
msggrep
option
+ - --add-location,
msgmerge
option
+ - --add-location,
msguniq
option
+ - --add-location,
xgettext
option
+ - --alignment,
msgfmt
option
+ - --backup,
msgmerge
option
+ - --c++,
xgettext
option
+ - --check,
msgfmt
option
+ - --check-accelerators,
msgfmt
option
+ - --check-compatibility,
msgfmt
option
+ - --check-domain,
msgfmt
option
+ - --check-format,
msgfmt
option
+ - --check-header,
msgfmt
option
+ - --clear-fuzzy,
msgattrib
option
+ - --clear-obsolete,
msgattrib
option
+ - --compendium,
msgmerge
option
+ - --copy,
gettextize
option
+ - --copyright-holder,
xgettext
option
+ - --debug,
xgettext
option
+ - --default-domain,
xgettext
option
+ - --directory,
msgattrib
option
+ - --directory,
msgcat
option
+ - --directory,
msgcmp
option
+ - --directory,
msgcomm
option
+ - --directory,
msgconv
option
+ - --directory,
msgen
option
+ - --directory,
msgexec
option
+ - --directory,
msgfilter
option
+ - --directory,
msgfmt
option
+ - --directory,
msggrep
option
+ - --directory,
msgmerge
option
+ - --directory,
msguniq
option
+ - --directory,
xgettext
option
+ - --domain,
msggrep
option
+ - --exclude-file,
xgettext
option
+ - --expression,
msgfilter
option
+ - --extended-regexp,
msggrep
option
+ - --extract-all,
xgettext
option
+ - --file,
msgfilter
option
+ - --file,
msggrep
option
+ - --files-from,
msgcat
option
+ - --files-from,
msgcomm
option
+ - --files-from,
xgettext
option
+ - --fixed-strings,
msggrep
option
+ - --force,
gettextize
option
+ - --force-po,
msgattrib
option
+ - --force-po,
msgcat
option
+ - --force-po,
msgcomm
option
+ - --force-po,
msgconv
option
+ - --force-po,
msgen
option
+ - --force-po,
msgfilter
option
+ - --force-po,
msggrep
option
+ - --force-po,
msgmerge
option
+ - --force-po,
msgunfmt
option
+ - --force-po,
msguniq
option
+ - --force-po,
xgettext
option
+ - --foreign-user,
xgettext
option
+ - --fuzzy,
msgattrib
option
+ - --help,
gettextize
option
+ - --help,
msgattrib
option
+ - --help,
msgcat
option
+ - --help,
msgcmp
option
+ - --help,
msgcomm
option
+ - --help,
msgconv
option
+ - --help,
msgen
option
+ - --help,
msgexec
option
+ - --help,
msgfilter
option
+ - --help,
msgfmt
option
+ - --help,
msggrep
option
+ - --help,
msginit
option
+ - --help,
msgmerge
option
+ - --help,
msgunfmt
option
+ - --help,
msguniq
option
+ - --help,
xgettext
option
+ - --ignore-case,
msggrep
option
+ - --indent,
msgattrib
option
+ - --indent,
msgcat
option
+ - --indent,
msgcomm
option
+ - --indent,
msgconv
option
+ - --indent,
msgen
option
+ - --indent,
msgfilter
option
+ - --indent,
msggrep
option
+ - --indent,
msgmerge
option
+ - --indent,
msgunfmt
option
+ - --indent,
msguniq
option
+ - --indent,
xgettext
option
+ - --input,
msgexec
option
+ - --input,
msgfilter
option
+ - --input,
msginit
option
+ - --intl,
gettextize
option
+ - --java,
msgfmt
option
+ - --java,
msgunfmt
option
+ - --java2,
msgfmt
option
+ - --join-existing,
xgettext
option
+ - --keep-header,
msgfilter
option
+ - --keyword,
xgettext
option
+ - --language,
xgettext
option
+ - --less-than,
msgcat
option
+ - --less-than,
msgcomm
option
+ - --locale,
msgfmt
option, --locale, msgfmt
option
+ - --locale,
msginit
option
+ - --locale,
msgunfmt
option, --locale, msgunfmt
option
+ - --location,
msggrep
option
+ - --more-than,
msgcat
option
+ - --more-than,
msgcomm
option
+ - --msgid,
msggrep
option
+ - --msgstr,
msggrep
option
+ - --msgstr-prefix,
xgettext
option
+ - --msgstr-suffix,
xgettext
option
+ - --multi-domain,
msgcmp
option
+ - --multi-domain,
msgmerge
option
+ - --no-changelog,
gettextize
option
+ - --no-fuzzy,
msgattrib
option
+ - --no-hash,
msgfmt
option
+ - --no-location,
msgattrib
option
+ - --no-location,
msgcat
option
+ - --no-location,
msgcomm
option
+ - --no-location,
msgconv
option
+ - --no-location,
msgen
option
+ - --no-location,
msgfilter
option
+ - --no-location,
msggrep
option
+ - --no-location,
msgmerge
option
+ - --no-location,
msguniq
option
+ - --no-location,
xgettext
option
+ - --no-obsolete,
msgattrib
option
+ - --no-translator,
msginit
option
+ - --no-wrap,
msgattrib
option
+ - --no-wrap,
msgcat
option
+ - --no-wrap,
msgcomm
option
+ - --no-wrap,
msgconv
option
+ - --no-wrap,
msgen
option
+ - --no-wrap,
msgfilter
option
+ - --no-wrap,
msggrep
option
+ - --no-wrap,
msginit
option
+ - --no-wrap,
msgmerge
option
+ - --no-wrap,
msgunfmt
option
+ - --no-wrap,
msguniq
option
+ - --no-wrap,
xgettext
option
+ - --obsolete,
msgattrib
option
+ - --omit-header,
msgcomm
option
+ - --omit-header,
xgettext
option
+ - --only-fuzzy,
msgattrib
option
+ - --only-obsolete,
msgattrib
option
+ - --output,
xgettext
option
+ - --output-dir,
xgettext
option
+ - --output-file,
msgattrib
option
+ - --output-file,
msgcat
option
+ - --output-file,
msgcomm
option
+ - --output-file,
msgconv
option
+ - --output-file,
msgen
option
+ - --output-file,
msgfilter
option
+ - --output-file,
msgfmt
option
+ - --output-file,
msggrep
option
+ - --output-file,
msginit
option
+ - --output-file,
msgmerge
option
+ - --output-file,
msgunfmt
option
+ - --output-file,
msguniq
option
+ - --quiet,
msgfilter
option
+ - --quiet,
msgmerge
option
+ - --regexp=,
msggrep
option
+ - --repeated,
msguniq
option
+ - --resource,
msgfmt
option
+ - --resource,
msgunfmt
option
+ - --set-fuzzy,
msgattrib
option
+ - --set-obsolete,
msgattrib
option
+ - --silent,
msgfilter
option
+ - --silent,
msgmerge
option
+ - --sort-by-file,
msgattrib
option
+ - --sort-by-file,
msgcat
option
+ - --sort-by-file,
msgcomm
option
+ - --sort-by-file,
msgconv
option
+ - --sort-by-file,
msgen
option
+ - --sort-by-file,
msgfilter
option
+ - --sort-by-file,
msggrep
option
+ - --sort-by-file,
msgmerge
option
+ - --sort-by-file,
msguniq
option
+ - --sort-by-file,
xgettext
option
+ - --sort-output,
msgattrib
option
+ - --sort-output,
msgcat
option
+ - --sort-output,
msgcomm
option
+ - --sort-output,
msgconv
option
+ - --sort-output,
msgen
option
+ - --sort-output,
msgfilter
option
+ - --sort-output,
msggrep
option
+ - --sort-output,
msgmerge
option
+ - --sort-output,
msgunfmt
option
+ - --sort-output,
msguniq
option
+ - --sort-output,
xgettext
option
+ - --statistics,
msgfmt
option
+ - --strict,
msgattrib
option
+ - --strict,
msgcat
option
+ - --strict,
msgcomm
option
+ - --strict,
msgconv
option
+ - --strict,
msgen
option
+ - --strict,
msgfilter
option
+ - --strict,
msgfmt
option
+ - --strict,
msggrep
option
+ - --strict,
msgmerge
option
+ - --strict,
msgunfmt
option
+ - --strict,
msguniq
option
+ - --strict,
xgettext
option
+ - --suffix,
msgmerge
option
+ - --tcl,
msgfmt
option
+ - --tcl,
msgunfmt
option
+ - --to-code,
msgcat
option
+ - --to-code,
msgconv
option
+ - --to-code,
msguniq
option
+ - --translated,
msgattrib
option
+ - --trigraphs,
xgettext
option
+ - --unique,
msgcat
option
+ - --unique,
msgcomm
option
+ - --unique,
msguniq
option
+ - --untranslated,
msgattrib
option
+ - --update,
msgmerge
option
+ - --use-first,
msgcat
option
+ - --use-first,
msguniq
option
+ - --use-fuzzy,
msgfmt
option
+ - --verbose,
msgfmt
option
+ - --verbose,
msgmerge
option
+ - --verbose,
msgunfmt
option
+ - --version,
gettextize
option
+ - --version,
msgattrib
option
+ - --version,
msgcat
option
+ - --version,
msgcmp
option
+ - --version,
msgcomm
option
+ - --version,
msgconv
option
+ - --version,
msgen
option
+ - --version,
msgexec
option
+ - --version,
msgfilter
option
+ - --version,
msgfmt
option
+ - --version,
msggrep
option
+ - --version,
msginit
option
+ - --version,
msgmerge
option
+ - --version,
msgunfmt
option
+ - --version,
msguniq
option
+ - --version,
xgettext
option
+ - --width,
msgattrib
option
+ - --width,
msgcat
option
+ - --width,
msgcomm
option
+ - --width,
msgconv
option
+ - --width,
msgen
option
+ - --width,
msgfilter
option
+ - --width,
msggrep
option
+ - --width,
msginit
option
+ - --width,
msgmerge
option
+ - --width,
msgunfmt
option
+ - --width,
msguniq
option
+ - --width,
xgettext
option
+ - -<,
msgcat
option
+ - -<,
msgcomm
option
+ - ->,
msgcat
option
+ - ->,
msgcomm
option
+ - -a,
msgfmt
option
+ - -a,
xgettext
option
+ - -c,
gettextize
option
+ - -c,
msgfmt
option
+ - -C,
msgfmt
option
+ - -C,
msgmerge
option
+ - -C,
xgettext
option
+ - -c,
xgettext
option
+ - -D,
msgattrib
option
+ - -D,
msgcat
option
+ - -D,
msgcmp
option
+ - -D,
msgcomm
option
+ - -D,
msgconv
option
+ - -D,
msgen
option
+ - -D,
msgexec
option
+ - -D,
msgfilter
option
+ - -d,
msgfmt
option, -d, msgfmt
option
+ - -D,
msgfmt
option
+ - -D,
msggrep
option
+ - -D,
msgmerge
option
+ - -d,
msgunfmt
option
+ - -d,
msguniq
option
+ - -D,
msguniq
option
+ - -D,
xgettext
option
+ - -d,
xgettext
option
+ - -e,
msgfilter
option
+ - -E,
msggrep
option
+ - -e,
msggrep
option
+ - -f,
gettextize
option
+ - -F,
msgattrib
option
+ - -F,
msgcat
option
+ - -f,
msgcat
option
+ - -F,
msgcomm
option
+ - -f,
msgcomm
option
+ - -F,
msgconv
option
+ - -F,
msgen
option
+ - -F,
msgfilter
option
+ - -f,
msgfilter
option
+ - -f,
msgfmt
option
+ - -f,
msggrep
option
+ - -F,
msggrep
option
+ - -F,
msgmerge
option
+ - -F,
msguniq
option
+ - -f,
xgettext
option
+ - -F,
xgettext
option
+ - -h,
msgattrib
option
+ - -h,
msgcat
option
+ - -h,
msgcmp
option
+ - -h,
msgcomm
option
+ - -h,
msgconv
option
+ - -h,
msgen
option
+ - -h,
msgexec
option
+ - -h,
msgfilter
option
+ - -h,
msgfmt
option
+ - -h,
msggrep
option
+ - -h,
msginit
option
+ - -h,
msgmerge
option
+ - -h,
msgunfmt
option
+ - -h,
msguniq
option
+ - -h,
xgettext
option
+ - -i,
msgattrib
option
+ - -i,
msgcat
option
+ - -i,
msgcomm
option
+ - -i,
msgconv
option
+ - -i,
msgen
option
+ - -i,
msgexec
option
+ - -i,
msgfilter
option
+ - -i,
msggrep
option
+ - -i,
msginit
option
+ - -i,
msgmerge
option
+ - -i,
msgunfmt
option
+ - -i,
msguniq
option
+ - -i,
xgettext
option
+ - -j,
msgfmt
option
+ - -j,
msgunfmt
option
+ - -j,
xgettext
option
+ - -K,
msggrep
option
+ - -k,
xgettext
option
+ - -l,
msgfmt
option, -l, msgfmt
option
+ - -l,
msginit
option
+ - -l,
msgunfmt
option, -l, msgunfmt
option
+ - -L,
xgettext
option
+ - -m,
msgcmp
option
+ - -M,
msggrep
option
+ - -m,
msgmerge
option
+ - -m,
xgettext
option
+ - -M,
xgettext
option
+ - -n,
msgattrib
option
+ - -n,
msgcat
option
+ - -n,
msgcomm
option
+ - -n,
msgfilter
option
+ - -N,
msggrep
option
+ - -n,
msguniq
option
+ - -n,
xgettext
option
+ - -o,
msgattrib
option
+ - -o,
msgcat
option
+ - -o,
msgcomm
option
+ - -o,
msgconv
option
+ - -o,
msgen
option
+ - -o,
msgfilter
option
+ - -o,
msgfmt
option
+ - -o,
msggrep
option
+ - -o,
msginit
option
+ - -o,
msgmerge
option
+ - -o,
msgunfmt
option
+ - -o,
msguniq
option
+ - -o,
xgettext
option
+ - -p,
xgettext
option
+ - -q,
msgmerge
option
+ - -r,
msgfmt
option
+ - -r,
msgunfmt
option
+ - -s,
msgattrib
option
+ - -s,
msgcat
option
+ - -s,
msgcomm
option
+ - -s,
msgconv
option
+ - -s,
msgen
option
+ - -s,
msgfilter
option
+ - -s,
msgmerge
option
+ - -s,
msgunfmt
option
+ - -s,
msguniq
option
+ - -s,
xgettext
option
+ - -t,
msgcat
option
+ - -t,
msgconv
option
+ - -T,
msggrep
option
+ - -t,
msguniq
option
+ - -T,
xgettext
option
+ - -u,
msgcat
option
+ - -u,
msgcomm
option
+ - -U,
msgmerge
option
+ - -u,
msguniq
option
+ - -V,
msgattrib
option
+ - -V,
msgcat
option
+ - -V,
msgcmp
option
+ - -V,
msgcomm
option
+ - -V,
msgconv
option
+ - -V,
msgen
option
+ - -V,
msgexec
option
+ - -V,
msgfilter
option
+ - -v,
msgfmt
option
+ - -V,
msgfmt
option
+ - -V,
msggrep
option
+ - -V,
msginit
option
+ - -v,
msgmerge
option
+ - -V,
msgmerge
option
+ - -v,
msgunfmt
option
+ - -V,
msgunfmt
option
+ - -V,
msguniq
option
+ - -V,
xgettext
option
+ - -w,
msgattrib
option
+ - -w,
msgcat
option
+ - -w,
msgcomm
option
+ - -w,
msgconv
option
+ - -w,
msgen
option
+ - -w,
msgfilter
option
+ - -w,
msggrep
option
+ - -w,
msginit
option
+ - -w,
msgmerge
option
+ - -w,
msgunfmt
option
+ - -w,
msguniq
option
+ - -w,
xgettext
option
+ - -x,
xgettext
option
diff --git a/doc/gettext_19.html b/doc/gettext_19.html
index 8ae39e753..f1b5e54f0 100644
--- a/doc/gettext_19.html
+++ b/doc/gettext_19.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - Variable Index
@@ -10,7 +10,7 @@ Go to the first, previous
-
Variable Index
+Variable Index
Jump to:
@@ -22,26 +22,26 @@ Jump to:
l
-- LANG, environment variable, LANG, environment variable
-
- LANGUAGE, environment variable, LANGUAGE, environment variable
-
- LC_ALL, environment variable
-
- LC_COLLATE, environment variable
-
- LC_CTYPE, environment variable
-
- LC_MESSAGES, environment variable
-
- LC_MONETARY, environment variable
-
- LC_NUMERIC, environment variable
-
- LC_TIME, environment variable
-
- LINGUAS, environment variable
+
- LANG, environment variable, LANG, environment variable
+
- LANGUAGE, environment variable, LANGUAGE, environment variable
+
- LC_ALL, environment variable
+
- LC_COLLATE, environment variable
+
- LC_CTYPE, environment variable
+
- LC_MESSAGES, environment variable
+
- LC_MONETARY, environment variable
+
- LC_NUMERIC, environment variable
+
- LC_TIME, environment variable
+
- LINGUAS, environment variable
m
-- MSGEXEC_LOCATION, environment variable
-
- MSGEXEC_MSGID, environment variable
+
- MSGEXEC_LOCATION, environment variable
+
- MSGEXEC_MSGID, environment variable
t
-- TEXTDOMAIN, environment variable, TEXTDOMAIN, environment variable
-
- TEXTDOMAINDIR, environment variable, TEXTDOMAINDIR, environment variable
+
- TEXTDOMAIN, environment variable, TEXTDOMAIN, environment variable
+
- TEXTDOMAINDIR, environment variable, TEXTDOMAINDIR, environment variable
diff --git a/doc/gettext_2.html b/doc/gettext_2.html
index c419d890d..d793b2213 100644
--- a/doc/gettext_2.html
+++ b/doc/gettext_2.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - 2 PO Files and PO Mode Basics
@@ -174,7 +174,7 @@ can judge if the translation requires further modification, or is
acceptable as is. Once satisfied with the translation, she then removes
this fuzzy attribute. The msgmerge
program inserts this
when it combined the msgid
and msgstr
entries after fuzzy
-search only. See section 6.3 Fuzzy Entries.
+search only. See section 6.3 Fuzzy Entries.
- c-format
-
@@ -189,7 +189,7 @@ soon as the
xgettext
program generates a new template file.
In case the c-format flag is given for a string the msgfmt
does some more tests to check to validity of the translation.
-See section 8.1 Invoking the msgfmt
Program.
+See section 8.1 Invoking the msgfmt
Program.
@@ -303,9 +303,9 @@ When PO mode is active in a window, the letters `PO´ appear
in the mode line for that window. The mode line also displays how
many entries of each kind are held in the PO file. For example,
the string `132t+3f+10u+2o´ would tell the translator that the
-PO mode contains 132 translated entries (see section 6.2 Translated Entries,
-3 fuzzy entries (see section 6.3 Fuzzy Entries), 10 untranslated entries
-(see section 6.4 Untranslated Entries) and 2 obsolete entries (see section 6.5 Obsolete Entries). Zero-coefficients items are not shown. So, in this example, if
+PO mode contains 132 translated entries (see section 6.2 Translated Entries,
+3 fuzzy entries (see section 6.3 Fuzzy Entries), 10 untranslated entries
+(see section 6.4 Untranslated Entries) and 2 obsolete entries (see section 6.5 Obsolete Entries). Zero-coefficients items are not shown. So, in this example, if
the fuzzy entries were unfuzzied, the untranslated entries were translated
and the obsolete entries were deleted, the mode line would merely display
`145t´ for the counters.
@@ -571,7 +571,7 @@ have the special property of being able to work even when the cursor
is not into some PO file entry, and one may use them for nicely
correcting this situation. But even these commands will fail on a
truly empty PO file. There are development plans for the PO mode for it
-to interactively fill an empty PO file from sources. See section 3.3 Marking Translatable Strings.
+to interactively fill an empty PO file from sources. See section 3.4 Marking Translatable Strings.
diff --git a/doc/gettext_20.html b/doc/gettext_20.html
index 35f4f9deb..37fb3c388 100644
--- a/doc/gettext_20.html
+++ b/doc/gettext_20.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - PO Mode Index
@@ -10,7 +10,7 @@ Go to the first, previous
-
PO Mode Index
+PO Mode Index
Jump to:
@@ -46,28 +46,28 @@ Jump to:
a
-- auxiliary PO file
+
- auxiliary PO file
c
- commands
-
- comment out PO file entry
-
- consulting program sources
-
- consulting translations to other languages
+
- comment out PO file entry
+
- consulting program sources
+
- consulting translations to other languages
- current entry of a PO file
-
- cut and paste for translated strings
+
- cut and paste for translated strings
e
-- editing comments
-
- editing multiple entries
-
- editing translations
-
etags
, using for marking strings
-- exiting PO subedit
+
- editing comments
+
- editing multiple entries
+
- editing translations
+
etags
, using for marking strings
+- exiting PO subedit
f
-- find source fragment for a PO file entry
+
- find source fragment for a PO file entry
i
@@ -75,40 +75,40 @@ Jump to:
l
-- looking at the source to aid translation
+
- looking at the source to aid translation
m
-- marking strings for translation
-
- moving by fuzzy entries
-
- moving by obsolete entries
-
- moving by translated entries
-
- moving by untranslated entries
+
- marking strings for translation
+
- moving by fuzzy entries
+
- moving by obsolete entries
+
- moving by translated entries
+
- moving by untranslated entries
- moving through a PO file
o
-- obsolete active entry
+
- obsolete active entry
p
-- pending subedits
+
- pending subedits
s
-- starting a string translation
+
- starting a string translation
- string normalization in entries
-
- subedit minor mode
+
- subedit minor mode
t
-- `TAGS´, and marking translatable strings
+
- `TAGS´, and marking translatable strings
u
-- use the source, Luke
-
- using obsolete translations to make new entries
-
- using translation compendia
+
- use the source, Luke
+
- using obsolete translations to make new entries
+
- using translation compendia
diff --git a/doc/gettext_21.html b/doc/gettext_21.html
index 16f26617e..549af4875 100644
--- a/doc/gettext_21.html
+++ b/doc/gettext_21.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - Autoconf Macro Index
@@ -10,7 +10,7 @@ Go to the first, previous
-
Autoconf Macro Index
+Autoconf Macro Index
Jump to:
@@ -18,8 +18,8 @@ Jump to:
a
-- AM_GNU_GETTEXT
-
- AM_ICONV
+
- AM_GNU_GETTEXT
+
- AM_ICONV
diff --git a/doc/gettext_22.html b/doc/gettext_22.html
index 50735dbef..23d31e0c1 100644
--- a/doc/gettext_22.html
+++ b/doc/gettext_22.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - General Index
@@ -10,7 +10,7 @@ Go to the first, previous
-
General Index
+General Index
Jump to:
@@ -68,171 +68,176 @@ Jump to:
_
-_
, a macro to mark strings for translation
-_nl_msg_cat_cntr
+_
, a macro to mark strings for translation
+_nl_msg_cat_cntr
a
-- `ABOUT-NLS´ file
-
- `acconfig.h´ file
-
- accumulating translations
-
- `aclocal.m4´ file
-
- adding keywords,
xgettext
- - apply a filter to translations
-
- apply command to all translations in a catalog
-
- attribute manipulation
-
- attribute, fuzzy
-
- attributes of a PO file entry
-
- attributes, manipulating
-
- autoconf macros for
gettext
- - auxiliary PO file
-
- available translations
-
- awk
+
- `ABOUT-NLS´ file
+
- `acconfig.h´ file
+
- accumulating translations
+
- `aclocal.m4´ file
+
- adding keywords,
xgettext
+ - ambiguities
+
- apply a filter to translations
+
- apply command to all translations in a catalog
+
- attribute manipulation
+
- attribute, fuzzy
+
- attributes of a PO file entry
+
- attributes, manipulating
+
- autoconf macros for
gettext
+ - auxiliary PO file
+
- available translations
+
- awk
b
-- backup old file, and
msgmerge
program
- - bash
-
- bibliography
+
- backup old file, and
msgmerge
program
+ - bash
+
- bibliography
- big picture
-
- bind_textdomain_codeset
+
- bind_textdomain_codeset
- bug report address
c
-- C and C-like languages
-
- C trigraphs
-
- catalog encoding and
msgexec
output
- catclose
, a catgets
function
-catgets
, X/Open specification
-catgets
, a catgets
function
-catopen
, a catgets
function
+- C and C-like languages
+
- C trigraphs
+
- catalog encoding and
msgexec
output
+ catclose
, a catgets
function
+catgets
, X/Open specification
+catgets
, a catgets
function
+catopen
, a catgets
function
- character encoding
-
- charset conversion at runtime
-
- charset of PO files
-
- check format strings
-
- checking of translations
-
- clisp
-
- clisp C sources
+
- charset conversion at runtime
+
- charset of PO files
+
- check format strings
+
- checking of translations
+
- clisp
+
- clisp C sources
- codeset
- comments in PO files
-
- Common Lisp
-
- compare PO files
-
- comparison of interfaces
-
- compatibility with X/Open
msgfmt
- - compendium
-
- compendium, creating
-
- concatenate PO files
-
- concatenating PO files into a compendium
-
- convert binary message catalog into PO file
-
- convert translations to a different encoding
-
- converting a package to use
gettext
- - country codes
-
- create new PO file
-
- creating a new PO file
-
- creating compendia
+
- Common Lisp
+
- compare PO files
+
- comparison of interfaces
+
- compatibility with X/Open
msgfmt
+ - compendium
+
- compendium, creating
+
- concatenate PO files
+
- concatenating PO files into a compendium
+
- concatenation of strings
+
- convert binary message catalog into PO file
+
- convert translations to a different encoding
+
- converting a package to use
gettext
+ - country codes
+
- create new PO file
+
- creating a new PO file
+
- creating compendia
- currency symbols
d
- date format
-
- dcngettext
-
- debugging messages marked as format strings
-
- dialect
-
- disabling NLS
-
- dngettext
-
- domain ambiguities
-
- duplicate elimination
-
- duplicate removal
+
- dcngettext
+
- debugging messages marked as format strings
+
- dialect
+
- disabling NLS
+
- dngettext
+
- domain ambiguities
+
- duplicate elimination
+
- duplicate removal
e
-- editing comments in PO files
-
- editing translations
-
- Emacs Lisp
+
- editing comments in PO files
+
- editing translations
+
- Emacs Lisp
- encoding
-
- encoding conversion
-
- encoding conversion at runtime
-
- encoding for your language
-
- encoding list
-
- encoding of PO files
+
- encoding conversion
+
- encoding conversion at runtime
+
- encoding for your language
+
- encoding list
+
- encoding of PO files
- evolution of packages
-
- extracting parts of a PO file into a compendium
+
- extracting parts of a PO file into a compendium
f
-- file format, `.mo´
+
- file format, `.mo´
- file format, `.po´
- files, `.po´ and `.mo´
- files, `.pot´
-
- filter messages according to attributes
-
- find common messages
-
- force use of fuzzy entries
-
- format strings
-
- Free Pascal
-
- fuzzy entries
+
- filter messages according to attributes
+
- find common messages
+
- force use of fuzzy entries
+
- format strings
+
- Free Pascal
+
- fuzzy entries
g
-- gawk
-
- generate binary message catalog from PO file
-
- generate translation catalog in English
-
gettext
files
+- gawk
+
- generate binary message catalog from PO file
+
- generate translation catalog in English
+
gettext
files
gettext
installation
-gettext
interface
-gettext
, a programmer's view
-- `gettext.h´ file
-
gettext
vs catgets
-gettextize
program, usage
-- GUI programs
+
gettext
interface
+gettext
, a programmer's view
+- `gettext.h´ file
+
gettext
vs catgets
+gettextize
program, usage
+- GUI programs
h
-- hash table, inside MO files
+
- hash table, inside MO files
- he, she, and they
-
- header entry of a PO file
-
- history of GNU
gettext
+ - header entry of a PO file
+
- help option
+
- history of GNU
gettext
i
- i18n
- importing PO files
-
- include file `libintl.h´, include file `libintl.h´, include file `libintl.h´, include file `libintl.h´
+
- include file `libintl.h´, include file `libintl.h´, include file `libintl.h´, include file `libintl.h´
- initialization
-
- initialize new PO file
-
- initialize translations from a compendium
+
- initialize new PO file
+
- initialize translations from a compendium
- installing
gettext
- - interface to
catgets
+ - interface to
catgets
- internationalization
-
- ISO 3166
-
- ISO 639
+
inttypes.h
+- ISO 3166
+
- ISO 639
j
-- Java
-
- Java mode, and
msgfmt
program
- - Java mode, and
msgunfmt
program
+ - Java
+
- Java mode, and
msgfmt
program
+ - Java mode, and
msgunfmt
program
+ - Java, string concatenation
k
-- keyboard accelerator checking
+
- keyboard accelerator checking
l
- l10n
-
- language codes
-
- language selection
-
- language selection at runtime
-
- large package
-
libiconv
library
-libintl
for Java
-libintl
library
-librep
Lisp
-- `LINGUAS´ file
+
- language codes
+
- language selection
+
- language selection at runtime
+
- large package
+
libiconv
library
+libintl
for Java
+libintl
library
+librep
Lisp
+- `LINGUAS´ file
- link with `libintl´
-
- Linux, Linux, Linux
-
- Lisp
-
- list of translation teams, where to find
+
- Linux, Linux, Linux
+
- Lisp
+
- list of translation teams, where to find
- locale facet, LC_ALL
- locale facet, LC_COLLATE
- locale facet, LC_CTYPE, locale facet, LC_CTYPE, locale facet, LC_CTYPE
@@ -242,159 +247,164 @@ Jump to:
- locale facet, LC_RESPONSES
- locale facet, LC_TIME, locale facet, LC_TIME
- locale facets
-
locale
program
+locale
program
- localization
m
-- magic signature of MO files
-
- `Makevars´ file
-
- manipulating PO files
-
- marking string initializers
-
- marking strings that require translation
+
- magic signature of MO files
+
- `Makevars´ file
+
- manipulating PO files
+
- marking string initializers
+
- marking strings that require translation
+
- marking strings, preparations
- marking translatable strings
-
- menu entries
-
- menu, keyboard accelerator support
-
- merge PO files
-
- merging two PO files
-
- message catalog files location
+
- menu entries
+
- menu, keyboard accelerator support
+
- merge PO files
+
- merging two PO files
+
- message catalog files location
- messages
-
- migration from earlier versions of
gettext
- - mnemonics of menu entries
-
- MO file's format
-
- modify message attrributes
-
msgattrib
program, usage
-msgcat
program, usage
-msgcmp
program, usage
-msgcomm
program, usage
-msgconv
program, usage
-msgen
program, usage
-msgexec
program, usage
-msgfilter
filter and catalog encoding
-msgfilter
program, usage
-msgfmt
program, usage
-msggrep
program, usage
-msginit
program, usage
-msgmerge
program, usage
-msgunfmt
program, usage
-msguniq
program, usage
+- migration from earlier versions of
gettext
+ - mnemonics of menu entries
+
- MO file's format
+
- modify message attrributes
+
msgattrib
program, usage
+msgcat
program, usage
+msgcmp
program, usage
+msgcomm
program, usage
+msgconv
program, usage
+msgen
program, usage
+msgexec
program, usage
+msgfilter
filter and catalog encoding
+msgfilter
program, usage
+msgfmt
program, usage
+msggrep
program, usage
+msginit
program, usage
+msgmerge
program, usage
+msgunfmt
program, usage
+msguniq
program, usage
- multi-line strings
n
-N_
, a convenience macro
+N_
, a convenience macro
- Native Language Support
- Natural Language Support
- newlines in PO files
-
- ngettext
+
- ngettext
- NLS
- number format
o
-- Object Pascal
-
- obsolete entries
-
- optimization of
gettext
functions
- - orthography
-
- output to stdout,
xgettext
+ - Object Pascal
+
- obsolete entries
+
- optimization of
gettext
functions
+ - orthography
+
- output to stdout,
xgettext
- overview of
gettext
p
-- package and version declaration in `configure.in´
-
- package build and installation options
-
- package maintainer's view of
gettext
- - Pascal
-
- Perl
-
- PHP
-
- Pike
-
- plural form formulas
-
- plural forms
-
- plural forms, in MO files
+
- package and version declaration in `configure.in´
+
- package build and installation options
+
- package maintainer's view of
gettext
+ - paragraphs
+
- Pascal
+
- Perl
+
- PHP
+
- Pike
+
- plural form formulas
+
- plural forms
+
- plural forms, in MO files
- PO files' format
- PO mode (Emacs) commands
-
- PO template file
-
- portability problems with
sed
- - `POTFILES.in´ file
+
- PO template file
+
- portability problems with
sed
+ - `POTFILES.in´ file
- preparing programs for translation
-
- problems with
catgets
interface
- - programming languages
-
- Python
+
- problems with
catgets
interface
+ - programming languages
+
- Python
q
-- quotation marks, quotation marks
-
- quote characters, use in PO files
+
- quotation marks, quotation marks
+
- quote characters, use in PO files
r
-- related reading
-
- RST
+
- related reading
+
- RST
s
-- scripting languages
-
- search messages in a catalog
-
- selecting message language
-
- setting up
gettext
at build time
- - setting up
gettext
at run time
- - several domains
+
- scripting languages
+
- search messages in a catalog
+
- selecting message language
+
- sentences
+
- setting up
gettext
at build time
+ - setting up
gettext
at run time
+ - several domains
- sex
-
- sgettext
+
- sgettext
- she, he, and they
-
- shell scripts
-
- Smalltalk
-
- sorting
msgcat
output
- - sorting
msgmerge
output
- - sorting
msgunfmt
output
- - sorting output of
xgettext
- - specifying plural form in a PO file
-
- standard output, and
msgcat
- - standard output, and
msgmerge
program
+ - shell scripts
+
- Smalltalk
+
- sorting
msgcat
output
+ - sorting
msgmerge
output
+ - sorting
msgunfmt
output
+ - sorting output of
xgettext
+ - specifying plural form in a PO file
+
- standard output, and
msgcat
+ - standard output, and
msgmerge
program
+ - string concatenation
- string normalization in entries
-
- supported languages,
xgettext
+ - style
+
- supported languages,
xgettext
t
-- Tcl
-
- Tcl mode, and
msgfmt
program
- - Tcl mode, and
msgunfmt
program
+ - Tcl
+
- Tcl mode, and
msgfmt
program
+ - Tcl mode, and
msgunfmt
program
- template PO file
-
- testing `.po´ files for equivalence
-
- Tk's scripting language
-
- translated entries
-
- translating menu entries
+
- testing `.po´ files for equivalence
+
- Tk's scripting language
+
- translated entries
+
- translating menu entries
- translation aspects
-
- Translation Matrix
+
- Translation Matrix
- Translation Project
-
- turning off NLS support
+
- turning off NLS support
- tutorial of
gettext
usage
u
-- unify duplicate translations
-
- untranslated entries
-
- update translations from a compendium
-
- upgrading to new versions of
gettext
+ - unify duplicate translations
+
- untranslated entries
+
- update translations from a compendium
+
- upgrading to new versions of
gettext
v
-- version control for backup files,
msgmerge
+ - version control for backup files,
msgmerge
w
-wxWindows
library
+wxWindows
library
x
-xargs
, and output from msgexec
-xgettext
program, usage
-xmodmap
program, and typing quotation marks
+xargs
, and output from msgexec
+xgettext
program, usage
+xmodmap
program, and typing quotation marks
y
-- YaST2 scripting language
-
- YCP
+
- YaST2 scripting language
+
- YCP
diff --git a/doc/gettext_3.html b/doc/gettext_3.html
index 3b8903ab0..25b415d56 100644
--- a/doc/gettext_3.html
+++ b/doc/gettext_3.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - 3 Preparing Program Sources
@@ -29,7 +29,7 @@ needing translation.
Presuming that your set of programs, or package, has been adjusted
so all needed GNU gettext
files are available, and your
-`Makefile´ files are adjusted (see section 12 The Maintainer's View), each C module
+`Makefile´ files are adjusted (see section 12 The Maintainer's View), each C module
having translated C strings should contain the line:
@@ -154,9 +154,287 @@ is not multithread-safe.
-3.2 How Marks Appear in Sources
+3.2 Preparing Translatable Strings
+
+Before strings can be marked for translations, they sometimes need to
+be adjusted. Usually preparing a string for translation is done right
+before marking it, during the marking phase which is described in the
+next sections. What you have to keep in mind while doing that is the
+following.
+
+
+
+
+-
+
+Decent English style.
+
+
-
+
+Entire sentences.
+
+
-
+
+Split at paragraphs.
+
+
-
+
+Use format strings instead of string concatenation.
+
+
+
+Let's look at some examples of these guidelines.
+
+
+
+
+Translatable strings should be in good English style. If slang language
+with abbreviations and shortcuts is used, often translators will not
+understand the message and will produce very inappropriate translations.
+
+
+
+
+"%s: is parameter\n"
+
+
+
+This is nearly untranslatable: Is the displayed item a parameter or
+the parameter?
+
+
+
+
+"No match"
+
+
+
+The ambiguity in this message makes it ununderstandable: Is the program
+attempting to set something on fire? Does it mean "The given object does
+not match the template"? Does it mean "The template does not fit for any
+of the objects"?
+
+
+
+
+In both cases, adding more words to the message will help both the
+translator and the English speaking user.
+
+
+
+
+Translatable strings should be entire sentences. It is often not possible
+to translate single verbs or adjectives in a substitutable way.
+
+
+
+
+printf ("File %s is %s protected", filename, rw ? "write" : "read");
+
+
+
+Most translators will not look at the source and will thus only see the
+string "File %s is %s protected"
, which is unintelligible. Change
+this to
+
+
+
+
+printf (rw ? "File %s is write protected" : "File %s is read protected",
+ filename);
+
+
+
+This way the translator will not only understand the message, she will
+also be able to find the appropriate grammatical construction. The French
+translator for example translates "write protected" like "protected
+against writing".
+
+
+
+Often sentences don't fit into a single line. If a sentence is output
+using two subsequent printf
statements, like this
+
+
+
+
+printf ("Locale charset \"%s\" is different from\n", lcharset);
+printf ("input file charset \"%s\".\n", fcharset);
+
+
+
+the translator would have to translate two half sentences, but nothing
+in the POT file would tell her that the two half sentences belong together.
+It is necessary to merge the two printf
statements so that the
+translator can handle the entire sentence at once and decide at which
+place to insert a line break in the translation (if at all):
+
+
+
+
+printf ("Locale charset \"%s\" is different from\n\
+input file charset \"%s\".\n", lcharset, fcharset);
+
+
+
+You may now ask: how about two or more adjacent sentences? Like in this case:
+
+
+
+
+puts ("Apollo 13 scenario: Stack overflow handling failed.");
+puts ("On the next stack overflow we will crash!!!");
+
+
+
+Should these two statements merged into a single one? I would recommend to
+merge them if the two sentences are related to each other, because then it
+makes it easier for the translator to understand and translate both. On
+the other hand, if one of the two messages is a stereotypic one, occurring
+in other places as well, you will do a favour to the translator by not
+merging the two. (Identical messages occurring in several places are
+combined by xgettext, so the translator has to handle them once only.)
+
+
+
+
+Translatable strings should be limited to one paragraph; don't let a
+single message be longer than ten lines. The reason is that when the
+translatable string changes, the translator is faced with the task of
+updating the entire translated string. Maybe only a single word will
+have changed in the English string, but the translator doesn't see that
+(with the current translation tools), therefore she has to proofread
+the entire message.
+
+
+
+
+Many GNU programs have a `--help´ output that extends over several
+screen pages. It is a courtesy towards the translators to split such a
+message into several ones of five to ten lines each. While doing that,
+you can also attempt to split the documented options into groups,
+such as the input options, the output options, and the informative
+output options. This will help every user to find the option he is
+looking for.
+
+
+
+
+
+Hardcoded string concatenation is sometimes used to construct English
+strings:
+
+
+
+
+strcpy (s, "Replace ");
+strcat (s, object1);
+strcat (s, " with ");
+strcat (s, object2);
+strcat (s, "?");
+
+
+
+In order to present to the translator only entire sentences, and also
+because in some languages the translator might want to swap the order
+of object1
and object2
, it is necessary to change this
+to use a format string:
+
+
+
+
+sprintf (s, "Replace %s with %s?", object1, object2);
+
+
+
+
+A similar case is compile time concatenation of strings. The ISO C 99
+include file <inttypes.h>
contains a macro PRId64
that
+can be used as a formatting directive for outputting an `int64_t´
+integer through printf
. It expands to a constant string, usually
+"d" or "ld" or "lld" or something like this, depending on the platform.
+Assume you have code like
+
+
+
+
+printf ("The amount is %0" PRId64 "\n"), number);
+
+
+
+After marking, this cannot become
+
+
+
+
+printf (gettext ("The amount is %0") PRId64 "\n"), number);
+
+
+
+because it would simply be invalid C syntax. It cannot become
+
+
+
+
+printf (gettext ("The amount is %0" PRId64 "\n")), number);
+
+
+
+because the value of PRId64
is not known to xgettext
, and
+even if were, there would be three or more possibilities, and the
+translator would have to translate three or more strings that differ in
+a single letter.
+
+
+
+The solution for this problem is to change the code like this:
+
+
+
+
+char buf1[100];
+sprintf (buf1, "%0" PRId64, number);
+printf (gettext ("The amount is %s\n"), buf1);
+
+
+
+This means, you put the platform dependent code in one statement, and the
+internationalization code in a different statement. Note that a buffer length
+of 100 is safe, because all available hardware integer types are limited to
+128 bits, and to print a 128 bit integer one needs at most 54 characters,
+regardless whether in decimal, octal or hexadecimal.
+
+
+
+
+All this applies to other programming languages as well. For example, in
+Java, string contenation is very frequently used, because it is a compiler
+built-in operator. Like in C, in Java, you would change
+
+
+
+
+System.out.println("Replace "+object1+" with "+object2+"?");
+
+
+
+into a statement involving a format string:
+
+
+
+
+System.out.println(
+ MessageFormat.format("Replace {0} with {1}?",
+ new Object[] { object1, object2 }));
+
+
+
+
+3.3 How Marks Appear in Sources
+
@@ -182,7 +460,7 @@ return the proper translation, as far as possible or wanted, for the
argument string. Most localizable strings are found in executable
positions, that is, attached to variables or given as parameters to
functions. But this is not universal usage, and some translatable
-strings appear in structured initializations. See section 3.5 Special Cases of Translatable Strings.
+strings appear in structured initializations. See section 3.6 Special Cases of Translatable Strings.
@@ -207,7 +485,7 @@ sources for those trying to keep them within 79 or 80 columns.
-
+
Many packages use `_´ (a simple underline) as a keyword,
and write `_("Translatable string")´ instead of `gettext
("Translatable string")´. Further, the coding rule, from GNU standards,
@@ -241,9 +519,9 @@ an example of string not requiring translation!
-3.3 Marking Translatable Strings
+3.4 Marking Translatable Strings
@@ -260,7 +538,7 @@ translation in some language, for the package being internationalized.
-
+
The set of program sources, targetted by the PO mode commands describe
here, should have an Emacs tags table constructed for your project,
prior to using these PO file commands. This is easy to do. In any
@@ -282,7 +560,7 @@ format Emacs can understand.
-
+
For packages following the GNU coding standards, there is
a make goal tags
or TAGS
which constructs the tag files in
all directories and for all files containing source code.
@@ -302,18 +580,18 @@ fill in while you mark strings as translatable in your program sources.
- ,
-
-
+
Search through program sources for a string which looks like a
candidate for translation (
po-tags-search
).
- M-,
-
-
+
Mark the last string found with `_()´ (
po-mark-translatable
).
- M-.
-
-
+
Mark the last string found with a keyword taken from a set of possible
keywords. This command with a prefix allows some management of these
keywords (
po-select-mark-and-mark
).
@@ -321,7 +599,7 @@ keywords (po-select-mark-and-mark
).
-
+
The , (po-tags-search
) command searches for the next
occurrence of a string which looks like a possible candidate for
translation, and displays the program source in another Emacs window,
@@ -373,8 +651,8 @@ first tags file, this reinitialization might be considered spurious.
-
-
+
+
The M-, (po-mark-translatable
) command will mark the
recently found string with the `_´ keyword. The M-.
(po-select-mark-and-mark
) command will request that you type
@@ -432,10 +710,10 @@ prefer `_´, as this one is already built in the M-,
-
3.4 Special Comments preceding Keywords
+3.5 Special Comments preceding Keywords
-
+
In C programs strings are often used within calls of functions from the
printf
family. The special thing about these format strings is
that they can contain format specifiers introduced with %. Assume
@@ -503,8 +781,8 @@ only a heuristic. In the `.po´ file the entry is marked using th
-
-
+
+
The careful reader now might say that this again can cause problems.
The heuristic might guess it wrong. This is true and therefore
xgettext
knows about special kind of comment which lets
@@ -541,16 +819,16 @@ to use must contain the string xgettext:no-c-format.
If a string is marked with c-format and this is not correct the
user can find out who is responsible for the decision. See
-section 4.1 Invoking the xgettext
Program to see how the --debug option can be
+section 4.1 Invoking the xgettext
Program to see how the --debug option can be
used for solving this problem.
-3.5 Special Cases of Translatable Strings
+3.6 Special Cases of Translatable Strings
-
+
The attentive reader might now point out that it is not always possible
to mark translatable string with gettext
or something like this.
Consider the following case:
@@ -577,7 +855,7 @@ Consider the following case:
While it is no problem to mark the string "a default message"
it
is not possible to mark the string initializers for messages
.
What is to be done? We have to fulfill two tasks. First we have to mark the
-strings so that the xgettext
program (see section 4.1 Invoking the xgettext
Program)
+strings so that the xgettext
program (see section 4.1 Invoking the xgettext
Program)
can find them, and second we have to translate the string at runtime
before printing them.
@@ -610,7 +888,7 @@ from the array. So one solution can look like this:
Please convince yourself that the string which is written by
fputs
is translated in any case. How to get xgettext
know
-the additional keyword gettext_noop
is explained in section 4.1 Invoking the xgettext
Program.
+the additional keyword gettext_noop
is explained in section 4.1 Invoking the xgettext
Program.
diff --git a/doc/gettext_4.html b/doc/gettext_4.html
index 2b7f28964..925de8ec9 100644
--- a/doc/gettext_4.html
+++ b/doc/gettext_4.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - 4 Making the PO Template File
@@ -10,9 +10,9 @@ Go to the first, previous<
-
4 Making the PO Template File
+4 Making the PO Template File
@@ -23,11 +23,11 @@ This section explains how to use xgettext
for this purpose.
-
4.1 Invoking the xgettext
Program
+4.1 Invoking the xgettext
Program
xgettext [option] [inputfile] ...
@@ -40,7 +40,7 @@ input files.
-4.1.1 Input file location
+4.1.1 Input file location
@@ -52,8 +52,8 @@ Input files.
-
- `--files-from=file´
-
-
-
+
+
Read the names of the input files from file instead of getting
them from the command line.
@@ -61,8 +61,8 @@ them from the command line.
-
- `--directory=directory´
-
-
-
+
+
Add directory to the list of directories. Source files are
searched relative to this list of directories. The resulting `.po´
file will be written relative to the current directory, though.
@@ -75,7 +75,7 @@ If inputfile is `-´, standard input is read.
-
4.1.2 Output file location
+4.1.2 Output file location
@@ -83,16 +83,16 @@ If inputfile is `-´, standard input is read.
-
- `--default-domain=name´
-
-
-
+
+
Use `name.po´ for output (instead of `messages.po´).
- `-o file´
-
- `--output=file´
-
-
-
+
+
Write output to specified file (instead of `name.po´ or
`messages.po´).
@@ -100,21 +100,21 @@ Write output to specified file (instead of `name.po´ o
-
- `--output-dir=dir´
-
-
-
+
+
Output files will be placed in directory dir.
-
+
If the output file is `-´ or `/dev/stdout´, the output
is written to standard output.
-4.1.3 Choice of input file language
+4.1.3 Choice of input file language
@@ -122,9 +122,9 @@ is written to standard output.
-
- `--language=name´
-
-
-
-
+
+
+
Specifies the language of the input files. The supported languages
are
C
, C++
, ObjectiveC
, PO
, Python
,
Lisp
, EmacsLisp
, librep
, Java
, awk
,
@@ -134,8 +134,8 @@ are C
, C++
, ObjectiveC
, PO
,
-
- `--c++´
-
-
-
+
+
This is a shorthand for
--language=C++
.
@@ -147,7 +147,7 @@ extension.
-4.1.4 Operation mode
+4.1.4 Operation mode
@@ -155,16 +155,16 @@ extension.
-
- `--join-existing´
-
-
-
+
+
Join messages with existing file.
- `-x file´
-
- `--exclude-file=file´
-
-
-
+
+
Entries from file are not extracted. file should be a PO or
POT file.
@@ -172,8 +172,8 @@ POT file.
-
- `--add-comments[=tag]´
-
-
-
+
+
Place comment block with tag (or those preceding keyword lines)
in output file.
@@ -181,7 +181,7 @@ in output file.
-
4.1.5 Language=C/C++ specific options
+4.1.5 Language=C/C++ specific options
@@ -189,20 +189,20 @@ in output file.
-
- `--extract-all´
-
-
-
+
+
Extract all strings.
- `-k keywordspec´
-
- `--keyword[=keywordspec]´
-
-
-
+
+
Additional keyword to be looked for (without keywordspec means not to
use default keywords).
-
+
If keywordspec is a C identifer id,
xgettext
looks
for strings in the first argument of each call to the function or macro
id. If keywordspec is of the form
@@ -222,15 +222,15 @@ explicitly disabled, are gettext
, dgettext:2
,
-
- `--trigraphs´
-
-
-
-
+
+
+
Understand ANSI C trigraphs for input.
- `--debug´
-
-
-
+
+
Use the flags c-format and possible-c-format to show who was
responsible for marking a message as a format string. The latter form is
used if the
xgettext
program decided, the format form is used if
@@ -249,39 +249,39 @@ adjacent strings, and escaped end of lines for continued strings.
-4.1.6 Output details
+4.1.6 Output details
- `--force-po´
-
-
+
Always write an output file even if no message is defined.
- `-i´
-
- `--indent´
-
-
-
+
+
Write the .po file using indented style.
- `--no-location´
-
-
+
Do not write `#: filename:line´ lines.
- `-n´
-
- `--add-location´
-
-
-
+
+
Generate `#: filename:line´ lines (default).
- `--strict´
-
-
+
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
@@ -290,19 +290,26 @@ GNU extensions.
-
- `--width=number´
-
-
-
+
+
Set the output page width. Long strings in the output files will be
split across multiple lines in order to ensure that each line's width
(= number of screen columns) is less or equal to the given number.
+
- `--no-wrap´
+
-
+
+Do not break long message lines. Message lines whose width exceeds the
+output page width will not be split into several lines. Only file reference
+lines which are wider than the output page width will be split.
+
- `-s´
-
- `--sort-output´
-
-
-
-
+
+
+
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
@@ -310,16 +317,16 @@ for the translator to understand each message's context.
-
- `--sort-by-file´
-
-
-
+
+
Sort output by file location.
- `--omit-header´
-
-
+
Don't write header with `msgid ""´ entry.
-
+
This is useful for testing purposes because it eliminates a source
of variance for generated
.gmo
files. With --omit-header
,
two invocations of xgettext
on the same files with the same
@@ -327,7 +334,7 @@ options at different times are guaranteed to produce the same results.
- `--copyright-holder=string´
-
-
+
Set the copyright holder in the output. string should be the
copyright holder of the surrounding package. (Note that the msgstr
strings, extracted from the package's sources, belong to the copyright
@@ -343,7 +350,7 @@ simply because
xgettext
was first used in the GNU project.
- `--foreign-user´
-
-
+
Omit FSF copyright in output. This option is equivalent to
`--copyright-holder="´. It can be useful for packages outside the GNU
project that want their translations to be in the public domain.
@@ -352,23 +359,23 @@ project that want their translations to be in the public domain.
-
- `--msgstr-prefix[=string]´
-
-
-
+
+
Use string (or "" if not specified) as prefix for msgstr entries.
- `-M [string]´
-
- `--msgstr-suffix[=string]´
-
-
-
+
+
Use string (or "" if not specified) as suffix for msgstr entries.
-4.1.7 Informative output
+4.1.7 Informative output
@@ -376,16 +383,16 @@ Use string (or "" if not specified) as suffix for msgstr entries.
-
- `--help´
-
-
-
+
+
Display this help and exit.
- `-V´
-
- `--version´
-
-
-
+
+
Output version information and exit.
diff --git a/doc/gettext_5.html b/doc/gettext_5.html
index 975785024..f614030be 100644
--- a/doc/gettext_5.html
+++ b/doc/gettext_5.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - 5 Creating a New PO File
@@ -10,9 +10,9 @@ Go to the first, previous<
-
5 Creating a New PO File
+5 Creating a New PO File
@@ -44,26 +44,26 @@ the header entry of this file.
-
5.1 Invoking the msginit
Program
+5.1 Invoking the msginit
Program
msginit [option]
-
-
+
+
The msginit
program creates a new PO file, initializing the meta
information with values from the user's environment.
-5.1.1 Input file location
+5.1.1 Input file location
@@ -71,8 +71,8 @@ information with values from the user's environment.
-
- `--input=inputfile´
-
-
-
+
+
Input POT file.
@@ -84,7 +84,7 @@ POT file. If it is `-´, standard input is read.
-5.1.2 Output file location
+5.1.2 Output file location
@@ -92,8 +92,8 @@ POT file. If it is `-´, standard input is read.
-
- `--output-file=file´
-
-
-
+
+
Write output to specified PO file.
@@ -106,7 +106,7 @@ standard output.
-5.1.3 Output details
+5.1.3 Output details
@@ -114,15 +114,15 @@ standard output.
-
- `--locale=ll_CC´
-
-
-
+
+
Set target locale. ll should be a language code, and CC should
be a country code. The command `locale -a´ can be used to output a list
of all installed locales. The default is the user's locale setting.
- `--no-translator´
-
-
+
Declares that the PO file will not have a human translator and is instead
automatically generated.
@@ -130,17 +130,24 @@ automatically generated.
-
- `--width=number´
-
-
-
+
+
Set the output page width. Long strings in the output files will be
split across multiple lines in order to ensure that each line's width
(= number of screen columns) is less or equal to the given number.
+
- `--no-wrap´
+
-
+
+Do not break long message lines. Message lines whose width exceeds the
+output page width will not be split into several lines. Only file reference
+lines which are wider than the output page width will be split.
+
-5.1.4 Informative output
+5.1.4 Informative output
@@ -148,25 +155,25 @@ split across multiple lines in order to ensure that each line's width
-
- `--help´
-
-
-
+
+
Display this help and exit.
- `-V´
-
- `--version´
-
-
-
+
+
Output version information and exit.
-5.2 Filling in the Header Entry
+5.2 Filling in the Header Entry
@@ -211,7 +218,7 @@ Before starting a translation, it is a good idea to get in touch with
your translation team, not only to make sure you don't do duplicated work,
but also to coordinate difficult linguistic issues.
-
+
In the Free Translation Project, each translation team has its own mailing
list. The up-to-date list of teams can be found at the Free Translation
Project's homepage, http://www.iro.umontreal.ca/contrib/po/HTML/,
@@ -219,14 +226,14 @@ in the "National teams" area.
- Content-Type
-
-
-
+
+
Replace `CHARSET´ with the character encoding used for your language,
in your locale, or UTF-8. This field is needed for correct operation of the
msgmerge
and msgfmt
programs, as well as for users whose
-locale's character encoding differs from yours (see section 10.2.4 How to specify the output character set gettext
uses).
+locale's character encoding differs from yours (see section 10.2.4 How to specify the output character set gettext
uses).
-
+
You get the character encoding of your locale by running the shell command
`locale charmap´. If the result is `C´ or `ANSI_X3.4-1968´,
which is equivalent to `ASCII´ (= `US-ASCII´), it means that your
@@ -234,7 +241,7 @@ locale is not correctly configured. In this case, ask your translation
team which charset to use. `ASCII´ is not usable for any language
except Latin.
-
+
Because the PO files must be portable to operating systems with less advanced
internationalization facilities, the character encodings that can be used
are limited to those supported by both GNU libc
and GNU
@@ -249,11 +256,11 @@ are limited to those supported by both GNU libc
and GNU
BIG5
, BIG5-HKSCS
, GBK
, GB18030
, SHIFT_JIS
,
JOHAB
, TIS-620
, VISCII
, UTF-8
.
-
+
In the GNU system, the following encodings are frequently used for the
corresponding languages.
-
+
ISO-8859-1
for
@@ -304,8 +311,8 @@ corresponding languages.
-
-
+
+
When single quote characters or double quote characters are used in
translations for your language, and your locale's encoding is one of the
ISO-8859-* charsets, it is best if you create your PO files in UTF-8
@@ -317,7 +324,7 @@ real quote characters, whereas users in ISO-8859-* locales will see the
vertical apostrophe and the vertical double quote instead (because that's
what the character set conversion will transliterate them to).
-
+
To enter such quote characters under X11, you can change your keyboard
mapping using the xmodmap
program. The X11 names of the quote
characters are "leftsinglequotemark", "rightsinglequotemark",
@@ -339,7 +346,7 @@ Set this to 8bit
.
-
This field is optional. It is only needed if the PO file has plural forms.
You can find them by searching for the `msgid_plural´ keyword. The
-format of the plural forms field is described in section 10.2.5 Additional functions for plural forms.
+format of the plural forms field is described in section 10.2.5 Additional functions for plural forms.
diff --git a/doc/gettext_6.html b/doc/gettext_6.html
index 23fad1983..2c1a7b003 100644
--- a/doc/gettext_6.html
+++ b/doc/gettext_6.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - 6 Updating Existing PO Files
@@ -10,15 +10,15 @@ Go to the first, previous<
-
6 Updating Existing PO Files
+6 Updating Existing PO Files
-6.1 Invoking the msgmerge
Program
+6.1 Invoking the msgmerge
Program
msgmerge [option] def.po ref.pot
@@ -39,7 +39,7 @@ is used to produce better results.
-6.1.1 Input file location
+6.1.1 Input file location
@@ -55,8 +55,8 @@ References to the new sources.
-
- `--directory=directory´
-
-
-
+
+
Add directory to the list of directories. Source files are
searched relative to this list of directories. The resulting `.po´
file will be written relative to the current directory, though.
@@ -65,16 +65,16 @@ file will be written relative to the current directory, though.
-
- `--compendium=file´
-
-
-
-Specify an additional library of message translations. See section 6.11 Using Translation Compendia.
+
+
+Specify an additional library of message translations. See section 6.11 Using Translation Compendia.
This option may be specified more than once.
-6.1.2 Operation mode
+6.1.2 Operation mode
@@ -82,15 +82,15 @@ This option may be specified more than once.
-
- `--update´
-
-
-
+
+
Update def.po. Do nothing if def.po is already up to date.
-6.1.3 Output file location
+6.1.3 Output file location
@@ -98,21 +98,21 @@ Update def.po. Do nothing if def.po is already up to date
-
- `--output-file=file´
-
-
-
+
+
Write output to specified file.
-
+
The results are written to standard output if no output file is specified
or if it is `-´.
-6.1.4 Output file location in update mode
+6.1.4 Output file location in update mode
The result is written back to def.po.
@@ -122,19 +122,19 @@ The result is written back to def.po.
- `--backup=control´
-
-
-
+
+
Make a backup of def.po
- `--suffix=suffix´
-
-
+
Override the usual backup suffix.
-
+
The version control method may be selected via the --backup
option
or through the VERSION_CONTROL
environment variable. Here are the
values:
@@ -176,7 +176,7 @@ The backup suffix is `~´, unless set with --suffix
-6.1.5 Operation modifiers
+6.1.5 Operation modifiers
@@ -184,44 +184,44 @@ The backup suffix is `~´, unless set with --suffix
- `--multi-domain´
-
-
-
+
+
Apply ref.pot to each of the domains in def.po.
-6.1.6 Output details
+6.1.6 Output details
- `--force-po´
-
-
+
Always write an output file even if it contains no message.
- `-i´
-
- `--indent´
-
-
-
+
+
Write the .po file using indented style.
- `--no-location´
-
-
+
Do not write `#: filename:line´ lines.
- `--add-location´
-
-
+
Generate `#: filename:line´ lines (default).
- `--strict´
-
-
+
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
@@ -230,19 +230,26 @@ GNU extensions.
-
- `--width=number´
-
-
-
+
+
Set the output page width. Long strings in the output files will be
split across multiple lines in order to ensure that each line's width
(= number of screen columns) is less or equal to the given number.
+
- `--no-wrap´
+
-
+
+Do not break long message lines. Message lines whose width exceeds the
+output page width will not be split into several lines. Only file reference
+lines which are wider than the output page width will be split.
+
- `-s´
-
- `--sort-output´
-
-
-
-
+
+
+
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
@@ -250,15 +257,15 @@ for the translator to understand each message's context.
-
- `--sort-by-file´
-
-
-
+
+
Sort output by file location.
-6.1.7 Informative output
+6.1.7 Informative output
@@ -266,24 +273,24 @@ Sort output by file location.
-
- `--help´
-
-
-
+
+
Display this help and exit.
- `-V´
-
- `--version´
-
-
-
+
+
Output version information and exit.
- `-v´
-
- `--verbose´
-
-
-
+
+
Increase verbosity level.
- `-q´
@@ -292,30 +299,30 @@ Increase verbosity level.
-
- `--silent´
-
-
-
-
+
+
+
Suppress progress indicators.
-6.2 Translated Entries
+6.2 Translated Entries
Each PO file entry for which the msgstr
field has been filled with
-a translation, and which is not marked as fuzzy (see section 6.3 Fuzzy Entries),
+a translation, and which is not marked as fuzzy (see section 6.3 Fuzzy Entries),
is said to be a translated entry. Only translated entries will
later be compiled by GNU msgfmt
and become usable in programs.
Other entry types will be excluded; translation will not occur for them.
-
+
Some commands are more specifically related to translated entry processing.
@@ -323,21 +330,21 @@ Some commands are more specifically related to translated entry processing.
- t
-
-
+
Find the next translated entry (
po-next-translated-entry
).
- T
-
-
+
Find the previous translated entry (
po-previous-translated-entry
).
-
-
-
-
+
+
+
+
The commands t (po-next-translated-entry
) and T
(po-previous-translated-entry
) move forwards or backwards, chasing
for an translated entry. If none is found, the search is extended and
@@ -345,25 +352,25 @@ wraps around in the PO file buffer.
-
+
Translated entries usually result from the translator having edited in
-a translation for them, section 6.6 Modifying Translations. However, if the
+a translation for them, section 6.6 Modifying Translations. However, if the
variable po-auto-fuzzy-on-edit
is not nil
, the entry having
received a new translation first becomes a fuzzy entry, which ought to
be later unfuzzied before becoming an official, genuine translated entry.
-See section 6.3 Fuzzy Entries.
+See section 6.3 Fuzzy Entries.
-6.3 Fuzzy Entries
+6.3 Fuzzy Entries
-
-
+
+
Each PO file entry may have a set of attributes, which are
qualities given a name and explicitely associated with the translation,
using a special system comment. One of these attributes
@@ -386,7 +393,7 @@ might mark some entries as being fuzzy.
-
+
Also, the translator may decide herself to mark an entry as fuzzy
for her own convenience, when she wants to remember that the entry
has to be later revisited. So, some commands are more specifically
@@ -397,26 +404,26 @@ related to fuzzy entry processing.
- z
-
-
+
Find the next fuzzy entry (
po-next-fuzzy-entry
).
- Z
-
-
+
Find the previous fuzzy entry (
po-previous-fuzzy-entry
).
- TAB
-
-
+
Remove the fuzzy attribute of the current entry (
po-unfuzzy
).
-
-
-
-
+
+
+
+
The commands z (po-next-fuzzy-entry
) and Z
(po-previous-fuzzy-entry
) move forwards or backwards, chasing for
a fuzzy entry. If none is found, the search is extended and wraps
@@ -424,9 +431,9 @@ around in the PO file buffer.
-
-
-
+
+
+
The command TAB (po-unfuzzy
) removes the fuzzy
attribute associated with an entry, usually leaving it translated.
Further, if the variable po-auto-select-on-unfuzzy
has not
@@ -448,8 +455,8 @@ to chase another entry, leaving the entry fuzzy.
-
-
+
+
The translator may also use the DEL command
(po-fade-out-entry
) over any translated entry to mark it as being
fuzzy, when she wants to easily leave a trace she wants to later return
@@ -464,9 +471,9 @@ still exists.
-6.4 Untranslated Entries
+6.4 Untranslated Entries
@@ -486,7 +493,7 @@ are easily recognizable by the fact they end with `msgstr ""´
-
+
The work of the translator might be (quite naively) seen as the process
of seeking for an untranslated entry, editing a translation for
it, and repeating these actions until no untranslated entries remain.
@@ -498,26 +505,26 @@ processing.
- u
-
-
+
Find the next untranslated entry (
po-next-untranslated-entry
).
- U
-
-
+
Find the previous untranslated entry (
po-previous-untransted-entry
).
- k
-
-
+
Turn the current entry into an untranslated one (
po-kill-msgstr
).
-
-
-
-
+
+
+
+
The commands u (po-next-untranslated-entry
) and U
(po-previous-untransted-entry
) move forwards or backwards,
chasing for an untranslated entry. If none is found, the search is
@@ -525,11 +532,11 @@ extended and wraps around in the PO file buffer.
-
-
+
+
An entry can be turned back into an untranslated entry by
merely emptying its translation, using the command k
-(po-kill-msgstr
). See section 6.6 Modifying Translations.
+(po-kill-msgstr
). See section 6.6 Modifying Translations.
@@ -540,9 +547,9 @@ if some untranslated string still exists.
-6.5 Obsolete Entries
+6.5 Obsolete Entries
@@ -568,7 +575,7 @@ after the fact.
-
+
Moreover, some commands are more specifically related to obsolete
entry processing.
@@ -577,27 +584,27 @@ entry processing.
- o
-
-
+
Find the next obsolete entry (
po-next-obsolete-entry
).
- O
-
-
+
Find the previous obsolete entry (
po-previous-obsolete-entry
).
- DEL
-
-
+
Make an active entry obsolete, or zap out an obsolete entry
(
po-fade-out-entry
).
-
-
-
-
+
+
+
+
The commands o (po-next-obsolete-entry
) and O
(po-previous-obsolete-entry
) move forwards or backwards,
chasing for an obsolete entry. If none is found, the search is
@@ -613,10 +620,10 @@ introducing useless msgid
values.
-
-
-
-
+
+
+
+
However, it is possible to comment out an active entry, so making
it obsolete. GNU gettext
utilities will later react to the
disappearance of a translation by using the untranslated string.
@@ -626,7 +633,7 @@ translated entry), then it is first made fuzzy. If it is already fuzzy,
then the entry is merely commented out, with confirmation. If the entry
is already obsolete, then it is completely deleted from the PO file.
It is easy to recycle the translation so deleted into some other PO file
-entry, usually one which is untranslated. See section 6.6 Modifying Translations.
+entry, usually one which is untranslated. See section 6.6 Modifying Translations.
@@ -644,10 +651,10 @@ merely tries to provide handy tools for helping her to do so.
-6.6 Modifying Translations
+6.6 Modifying Translations
@@ -673,40 +680,40 @@ using the following commands for modifying the translations.
- RET
-
-
+
Interactively edit the translation (
po-edit-msgstr
).
- LFD
-
- C-j
-
-
-
+
+
Reinitialize the translation with the original, untranslated string
(
po-msgid-to-msgstr
).
- k
-
-
+
Save the translation on the kill ring, and delete it (
po-kill-msgstr
).
- w
-
-
+
Save the translation on the kill ring, without deleting it
(
po-kill-ring-save-msgstr
).
- y
-
-
+
Replace the translation, taking the new from the kill ring
(
po-yank-msgstr
).
-
-
+
+
The command RET (po-edit-msgstr
) opens a new Emacs
window meant to edit in a new translation, or to modify an already existing
translation. The new window contains a copy of the translation taken from
@@ -714,14 +721,14 @@ the current PO file entry, all ready for edition, expunged of all quoting
marks, fully modifiable and with the complete extent of Emacs modifying
commands. When the translator is done with her modifications, she may use
C-c C-c to close the subedit window with the automatically requoted
-results, or C-c C-k to abort her modifications. See section 6.8 Details of Sub Edition,
+results, or C-c C-k to abort her modifications. See section 6.8 Details of Sub Edition,
for more information.
-
-
-
+
+
+
The command LFD (po-msgid-to-msgstr
) initializes, or
reinitializes the translation with the original string. This command is
normally used when the translator wants to redo a fresh translation of
@@ -729,7 +736,7 @@ the original string, disregarding any previous work.
-
+
It is possible to arrange so, whenever editing an untranslated
entry, the LFD command be automatically executed. If you set
po-auto-edit-with-msgid
to t
, the translation gets
@@ -738,7 +745,7 @@ The default value for po-auto-edit-with-msgid
is nil
.
-
+
In fact, whether it is best to start a translation with an empty
string, or rather with a copy of the original string, is a matter of
taste or habit. Sometimes, the source language and the
@@ -752,11 +759,11 @@ if this requires some extra editing work to get rid of the original.
-
-
-
-
-
+
+
+
+
+
The command k (po-kill-msgstr
) merely empties the
translation string, so turning the entry into an untranslated
one. But while doing so, its previous contents is put apart in
@@ -788,8 +795,8 @@ entries, the translation is also uncommented prior to saving.
-
-
+
+
The command y (po-yank-msgstr
) completely replaces the
translation of the current entry by a string taken from the kill ring.
Following Emacs terminology, we then say that the replacement
@@ -823,7 +830,7 @@ yanking commands themselves.
-
+
To better illustrate the operation of killing and yanking, let's
use an actual example, taken from a common situation. When the
programmer slightly modifies some string right in the program, his
@@ -861,10 +868,10 @@ See section `Keyboard Macros' in The Emacs Editor.
-6.7 Modifying Comments
+6.7 Modifying Comments
@@ -886,31 +893,31 @@ they are not meant for the translator to modify. See section 6.6 Modifying Translations.
+so the general indications given for those apply here. See section 6.6 Modifying Translations.
- #
-
-
+
Interactively edit the translator comments (
po-edit-comment
).
- K
-
-
+
Save the translator comments on the kill ring, and delete it
(
po-kill-comment
).
- W
-
-
+
Save the translator comments on the kill ring, without deleting it
(
po-kill-ring-save-comment
).
- Y
-
-
+
Replace the translator comments, taking the new from the kill ring
(
po-yank-comment
).
@@ -922,12 +929,12 @@ strings, and behave much the same way as they do, except that they handle
this part of PO file comments meant for translator usage, rather
than the translation strings. So, if the descriptions given below are
slightly succinct, it is because the full details have already been given.
-See section 6.6 Modifying Translations.
+See section 6.6 Modifying Translations.
-
-
+
+
The command # (po-edit-comment
) opens a new Emacs window
containing a copy of the translator comments on the current PO file entry.
If there are no such comments, PO mode understands that the translator wants
@@ -937,22 +944,22 @@ removed before edition, and reinstated after. For translator comments
pertaining to obsolete entries, the uncommenting and recommenting operations
are done twice. Once in the editing window, the keys C-c C-c
allow the translator to tell she is finished with editing the comment.
-See section 6.8 Details of Sub Edition, for further details.
+See section 6.8 Details of Sub Edition, for further details.
-
+
Functions found on po-subedit-mode-hook
, if any, are executed after
the string has been inserted in the edit buffer.
-
-
-
-
-
-
+
+
+
+
+
+
The command K (po-kill-comment
) gets rid of all
translator comments, while saving those comments on the kill ring.
The command W (po-kill-ring-save-comment
) takes
@@ -991,9 +998,9 @@ regular Emacs commands C-y (yank
) and M-y
-6.8 Details of Sub Edition
+6.8 Details of Sub Edition
@@ -1006,25 +1013,25 @@ of Emacs, which are described below.
- C-c C-c
-
-
+
Complete edition (
po-subedit-exit
).
- C-c C-k
-
-
+
Abort edition (
po-subedit-abort
).
- C-c C-a
-
-
+
Consult auxiliary PO files (
po-subedit-cycle-auxiliary
).
-
-
-
+
+
+
The window's contents represents a translation for a given message,
or a translator comment. The translator may modify this window to
her heart's content. Once this is done, the command C-c C-c
@@ -1034,8 +1041,8 @@ sight or if buffers were switched.
-
-
+
+
If the translator becomes unsatisfied with her translation or comment,
to the extent she prefers keeping what was existent prior to the
RET or # command, she may use the command C-c C-k
@@ -1046,14 +1053,14 @@ whole effect of last edition.
-
-
+
+
The command C-c C-a (po-subedit-cycle-auxiliary
)
allows for glancing through translations
already achieved in other languages, directly while editing the current
translation. This may be quite convenient when the translator is fluent
at many languages, but of course, only makes sense when such completed
-auxiliary PO files are already available to her (see section 6.10 Consulting Auxiliary PO Files).
+auxiliary PO files are already available to her (see section 6.10 Consulting Auxiliary PO Files).
@@ -1081,7 +1088,7 @@ in the editing window, as ending with two < in a row.
-
+
When a translation (or a comment) is being edited, the translator may move
the cursor back into the PO file buffer and freely move to other entries,
browsing at will. If, with an edition pending, the translator wanders in the
@@ -1094,7 +1101,7 @@ the translator should better be comfortable at handling many Emacs windows!
-
+
Pending subedits may be completed or aborted in any order, regardless
of how or when they were started. When many subedits are pending and the
translator asks for quitting the PO file (with the q command), subedits
@@ -1103,11 +1110,11 @@ are automatically resumed one at a time, so she may decide for each of them.
-6.9 C Sources Context
+6.9 C Sources Context
@@ -1144,7 +1151,7 @@ overall organization, than to programmation itself.
-
+
The following commands are meant to help the translator at getting
program source context for a PO file entry.
@@ -1153,35 +1160,35 @@ program source context for a PO file entry.
- s
-
-
+
Resume the display of a program source context, or cycle through them
(
po-cycle-source-reference
).
- M-s
-
-
+
Display of a program source context selected by menu
(
po-select-source-reference
).
- S
-
-
+
Add a directory to the search path for source files
(
po-consider-source-path
).
- M-S
-
-
+
Delete a directory from the search path for source files
(
po-ignore-source-path
).
-
-
-
-
+
+
+
+
The commands s (po-cycle-source-reference
) and M-s
(po-select-source-reference
) both open another window displaying
some source program file, and already positioned in such a way that
@@ -1226,10 +1233,10 @@ available for a single string to translate.
-
-
-
-
+
+
+
+
Program source files are usually found relative to where the PO
file stands. As a special provision, when this fails, the file is
also looked for, but relative to the directory immediately above it.
@@ -1247,9 +1254,9 @@ one of the directories she does not want anymore on the search path.
-6.10 Consulting Auxiliary PO Files
+6.10 Consulting Auxiliary PO Files
@@ -1262,8 +1269,8 @@ at once, for translators preferring to work in this way.
-
-
+
+
An auxiliary PO file is an existing PO file meant for the same
package the translator is working on, but targeted to a different mother
tongue language. Commands exist for declaring and handling auxiliary
@@ -1278,41 +1285,41 @@ Here are the auxiliary file commands available in PO mode.
- a
-
-
+
Seek auxiliary files for another translation for the same entry
(
po-cycle-auxiliary
).
- C-c C-a
-
-
+
Switch to a particular auxiliary file (
po-select-auxiliary
).
- A
-
-
+
Declare this PO file as an auxiliary file (
po-consider-as-auxiliary
).
- M-A
-
-
+
Remove this PO file from the list of auxiliary files
(
po-ignore-as-auxiliary
).
-
-
-
-
+
+
+
+
Command A (po-consider-as-auxiliary
) adds the current
PO file to the list of auxiliary files, while command M-A
(po-ignore-as-auxiliary
just removes it.
-
-
+
+
The command a (po-cycle-auxiliary
) seeks all auxiliary PO
files, round-robin, searching for a translated entry in some other language
having an msgid
field identical as the one for the current entry.
@@ -1324,8 +1331,8 @@ so repeating a will eventually yield back the original PO file.
-
-
+
+
The command C-c C-a (po-select-auxiliary
) asks the translator
for her choice of a particular auxiliary file, with completion, and
then switches to that selected PO file. The command also checks if
@@ -1345,7 +1352,7 @@ their msgid
entries written by the same GNU gettext
to
-
+
However, PO files initially created by PO mode itself, while marking
strings in source files, are normalised differently. So are PO
files resulting of the the `M-x normalize´ command. Until these
@@ -1355,13 +1362,13 @@ fully resolved, the translator should stay aware of normalisation issues.
-6.11 Using Translation Compendia
+6.11 Using Translation Compendia
-
+
A compendium is a special PO file containing a set of
translations recurring in many different packages. The translator can
use gettext tools to build a new compendium, to add entries to her
@@ -1372,10 +1379,10 @@ already translated entries, from translations kept in the compendium.
-
6.11.1 Creating Compendia
+6.11.1 Creating Compendia
@@ -1387,11 +1394,11 @@ files and extracting a message subset from a PO file.
-6.11.1.1 Concatenate PO Files
+6.11.1.1 Concatenate PO Files
-
-
+
+
To concatenate several valid PO files into one compendium file you can
use `msgcomm´ or `msgcat´ (the latter preferred):
@@ -1470,9 +1477,9 @@ files or postprocess the result using `msgattrib --translated --no-fuzzy&a
-6.11.1.2 Extract a Message Subset from a PO File
+6.11.1.2 Extract a Message Subset from a PO File
@@ -1492,7 +1499,7 @@ msggrep --location src/getopt.c -o compendium.po file.po
-
6.11.2 Using Compendia
+6.11.2 Using Compendia
You can use a compendium file to initialize a translation from scratch
@@ -1501,9 +1508,9 @@ or to update an already existing translation.
-6.11.2.1 Initialize a New Translation File
+6.11.2.1 Initialize a New Translation File
@@ -1518,9 +1525,9 @@ msgmerge --compendium compendium.po -o file.po /dev/null file.pot
-
6.11.2.2 Update an Existing Translation File
+6.11.2.2 Update an Existing Translation File
diff --git a/doc/gettext_7.html b/doc/gettext_7.html
index 0de9a8902..20cae6e8a 100644
--- a/doc/gettext_7.html
+++ b/doc/gettext_7.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - 7 Manipulating PO Files
@@ -10,9 +10,9 @@ Go to the first, previous<
-
7 Manipulating PO Files
+7 Manipulating PO Files
@@ -22,7 +22,7 @@ complete set of tools for this purpose.
-
+
When merging two packages into a single package, the resulting POT file
will be the concatenation of the two packages' POT files. Thus the
maintainer must concatenate the two existing package translations into
@@ -32,7 +32,7 @@ possible conflicts that arose during the merge.
-
+
When a translator takes over the translation job from another translator,
but she uses a different character encoding in her locale, she will
convert the catalog to her character encoding. This is best done through
@@ -48,8 +48,8 @@ that source file and use `msgmerge´.
-
-
+
+
When a translator wants to adjust some translation catalog for a special
dialect or orthography -- for example, German as written in Switzerland
versus German as written in Germany -- she needs to apply some text
@@ -66,14 +66,14 @@ that's why it's better to use the original POT file if available.
-
+
When a translator wants to check her translations, for example according
to orthography rules or using a non-interactive spell checker, she can do
so using the `msgexec´ program.
-
+
When third party tools create PO or POT files, sometimes duplicates cannot
be avoided. But the GNU gettext
tools give an error when they
encounter duplicate msgids in the same file and in the same domain.
@@ -91,7 +91,7 @@ completely translated.
-
+
`msgattrib´ can be used to select and extract only the fuzzy
or untranslated messages of a translation catalog.
@@ -104,19 +104,19 @@ catalogs. It copies each message's msgid to its msgstr.
-
7.1 Invoking the msgcat
Program
+7.1 Invoking the msgcat
Program
msgcat [option] [inputfile]...
-
-
+
+
The msgcat
program concatenates and merges the specified PO files.
It finds messages which are common to two or more of the specified PO files.
By using the --more-than
option, greater commonality may be requested
@@ -130,7 +130,7 @@ to define them. File positions from all PO files will be cumulated.
-7.1.1 Input file location
+7.1.1 Input file location
@@ -142,8 +142,8 @@ Input files.
-
- `--files-from=file´
-
-
-
+
+
Read the names of the input files from file instead of getting
them from the command line.
@@ -151,8 +151,8 @@ them from the command line.
-
- `--directory=directory´
-
-
-
+
+
Add directory to the list of directories. Source files are
searched relative to this list of directories. The resulting `.po´
file will be written relative to the current directory, though.
@@ -165,7 +165,7 @@ If inputfile is `-´, standard input is read.
-
7.1.2 Output file location
+7.1.2 Output file location
@@ -173,21 +173,21 @@ If inputfile is `-´, standard input is read.
-
- `--output-file=file´
-
-
-
+
+
Write output to specified file.
-
+
The results are written to standard output if no output file is specified
or if it is `-´.
-7.1.3 Message selection
+7.1.3 Message selection
@@ -195,8 +195,8 @@ or if it is `-´.
-
- `--less-than=number´
-
-
-
+
+
Print messages with less than number definitions, defaults to infinite
if not set.
@@ -204,8 +204,8 @@ if not set.
-
- `--more-than=number´
-
-
-
+
+
Print messages with more than number definitions, defaults to 0 if not
set.
@@ -213,8 +213,8 @@ set.
-
- `--unique´
-
-
-
+
+
Shorthand for `--less-than=2´. Requests that only unique messages be
printed.
@@ -222,7 +222,7 @@ printed.
-
7.1.4 Output details
+7.1.4 Output details
@@ -230,45 +230,45 @@ printed.
-
- `--to-code=name´
-
-
-
+
+
Specify encoding for output.
- `--use-first´
-
-
+
Use first available translation for each message. Don't merge several
translations into one.
- `--force-po´
-
-
+
Always write an output file even if it contains no message.
- `-i´
-
- `--indent´
-
-
-
+
+
Write the .po file using indented style.
- `--no-location´
-
-
+
Do not write `#: filename:line´ lines.
- `-n´
-
- `--add-location´
-
-
-
+
+
Generate `#: filename:line´ lines (default).
- `--strict´
-
-
+
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
@@ -277,19 +277,26 @@ GNU extensions.
-
- `--width=number´
-
-
-
+
+
Set the output page width. Long strings in the output files will be
split across multiple lines in order to ensure that each line's width
(= number of screen columns) is less or equal to the given number.
+
- `--no-wrap´
+
-
+
+Do not break long message lines. Message lines whose width exceeds the
+output page width will not be split into several lines. Only file reference
+lines which are wider than the output page width will be split.
+
- `-s´
-
- `--sort-output´
-
-
-
-
+
+
+
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
@@ -297,15 +304,15 @@ for the translator to understand each message's context.
-
- `--sort-by-file´
-
-
-
+
+
Sort output by file location.
-7.1.5 Informative output
+7.1.5 Informative output
@@ -313,41 +320,41 @@ Sort output by file location.
-
- `--help´
-
-
-
+
+
Display this help and exit.
- `-V´
-
- `--version´
-
-
-
+
+
Output version information and exit.
-7.2 Invoking the msgconv
Program
+7.2 Invoking the msgconv
Program
msgconv [option] [inputfile]
-
+
The msgconv
program converts a translation catalog to a different
character encoding.
-7.2.1 Input file location
+7.2.1 Input file location
@@ -359,8 +366,8 @@ Input PO file.
-
- `--directory=directory´
-
-
-
+
+
Add directory to the list of directories. Source files are
searched relative to this list of directories. The resulting `.po´
file will be written relative to the current directory, though.
@@ -373,7 +380,7 @@ If no inputfile is given or if it is `-´, standard
-
7.2.2 Output file location
+7.2.2 Output file location
@@ -381,8 +388,8 @@ If no inputfile is given or if it is `-´, standard
-
- `--output-file=file´
-
-
-
+
+
Write output to specified file.
@@ -394,7 +401,7 @@ or if it is `-´.
-7.2.3 Conversion target
+7.2.3 Conversion target
@@ -402,8 +409,8 @@ or if it is `-´.
-
- `--to-code=name´
-
-
-
+
+
Specify encoding for output.
@@ -414,36 +421,36 @@ The default encoding is the current locale's encoding.
-7.2.4 Output details
+7.2.4 Output details
- `--force-po´
-
-
+
Always write an output file even if it contains no message.
- `-i´
-
- `--indent´
-
-
-
+
+
Write the .po file using indented style.
- `--no-location´
-
-
+
Do not write `#: filename:line´ lines.
- `--add-location´
-
-
+
Generate `#: filename:line´ lines (default).
- `--strict´
-
-
+
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
@@ -452,18 +459,25 @@ GNU extensions.
-
- `--width=number´
-
-
-
+
+
Set the output page width. Long strings in the output files will be
split across multiple lines in order to ensure that each line's width
(= number of screen columns) is less or equal to the given number.
+
- `--no-wrap´
+
-
+
+Do not break long message lines. Message lines whose width exceeds the
+output page width will not be split into several lines. Only file reference
+lines which are wider than the output page width will be split.
+
- `-s´
-
- `--sort-output´
-
-
-
+
+
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
@@ -471,15 +485,15 @@ for the translator to understand each message's context.
-
- `--sort-by-file´
-
-
-
+
+
Sort output by file location.
-7.2.5 Informative output
+7.2.5 Informative output
@@ -487,41 +501,41 @@ Sort output by file location.
-
- `--help´
-
-
-
+
+
Display this help and exit.
- `-V´
-
- `--version´
-
-
-
+
+
Output version information and exit.
-7.3 Invoking the msggrep
Program
+7.3 Invoking the msggrep
Program
msggrep [option] [inputfile]
-
+
The msggrep
program extracts all messages of a translation catalog
that match a given pattern or belong to some given source files.
-7.3.1 Input file location
+7.3.1 Input file location
@@ -533,8 +547,8 @@ Input PO file.
-
- `--directory=directory´
-
-
-
+
+
Add directory to the list of directories. Source files are
searched relative to this list of directories. The resulting `.po´
file will be written relative to the current directory, though.
@@ -547,7 +561,7 @@ If no inputfile is given or if it is `-´, standard
-
7.3.2 Output file location
+7.3.2 Output file location
@@ -555,8 +569,8 @@ If no inputfile is given or if it is `-´, standard
-
- `--output-file=file´
-
-
-
+
+
Write output to specified file.
@@ -568,7 +582,7 @@ or if it is `-´.
-7.3.3 Message selection
+7.3.3 Message selection
@@ -618,8 +632,8 @@ expressions if -E is given, or fixed strings if -F is given.
-
- `--location=sourcefile´
-
-
-
+
+
Select messages extracted from sourcefile. sourcefile can be
either a literal file name or a wildcard pattern.
@@ -627,97 +641,97 @@ either a literal file name or a wildcard pattern.
-
- `--domain=domainname´
-
-
-
+
+
Select messages belonging to domain domainname.
- `-K´
-
- `--msgid´
-
-
-
+
+
Start of patterns for the msgid.
- `-T´
-
- `--msgstr´
-
-
-
+
+
Start of patterns for the msgstr.
- `-E´
-
- `--extended-regexp´
-
-
-
+
+
Specify that pattern is an extended regular expression.
- `-F´
-
- `--fixed-strings´
-
-
-
+
+
Specify that pattern is a set of newline-separated strings.
- `-e pattern´
-
- `--regexp=pattern´
-
-
-
+
+
Use pattern as a regular expression.
- `-f file´
-
- `--file=file´
-
-
-
+
+
Obtain pattern from file.
- `-i´
-
- `--ignore-case´
-
-
-
+
+
Ignore case distinctions.
-7.3.4 Output details
+7.3.4 Output details
- `--force-po´
-
-
+
Always write an output file even if it contains no message.
- `--indent´
-
-
+
Write the .po file using indented style.
- `--no-location´
-
-
+
Do not write `#: filename:line´ lines.
- `--add-location´
-
-
+
Generate `#: filename:line´ lines (default).
- `--strict´
-
-
+
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
@@ -726,28 +740,35 @@ GNU extensions.
-
- `--width=number´
-
-
-
+
+
Set the output page width. Long strings in the output files will be
split across multiple lines in order to ensure that each line's width
(= number of screen columns) is less or equal to the given number.
+
- `--no-wrap´
+
-
+
+Do not break long message lines. Message lines whose width exceeds the
+output page width will not be split into several lines. Only file reference
+lines which are wider than the output page width will be split.
+
- `--sort-output´
-
-
+
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
- `--sort-by-file´
-
-
+
Sort output by file location.
-7.3.5 Informative output
+7.3.5 Informative output
@@ -755,41 +776,41 @@ Sort output by file location.
-
- `--help´
-
-
-
+
+
Display this help and exit.
- `-V´
-
- `--version´
-
-
-
+
+
Output version information and exit.
-7.4 Invoking the msgfilter
Program
+7.4 Invoking the msgfilter
Program
msgfilter [option] filter [filter-option]
-
+
The msgfilter
program applies a filter to all translations of a
translation catalog.
-7.4.1 Input file location
+7.4.1 Input file location
@@ -797,16 +818,16 @@ translation catalog.
-
- `--input=inputfile´
-
-
-
+
+
Input PO file.
- `-D directory´
-
- `--directory=directory´
-
-
-
+
+
Add directory to the list of directories. Source files are
searched relative to this list of directories. The resulting `.po´
file will be written relative to the current directory, though.
@@ -819,7 +840,7 @@ If no inputfile is given or if it is `-´, standard
-
7.4.2 Output file location
+7.4.2 Output file location
@@ -827,8 +848,8 @@ If no inputfile is given or if it is `-´, standard
-
- `--output-file=file´
-
-
-
+
+
Write output to specified file.
@@ -840,7 +861,7 @@ or if it is `-´.
-7.4.3 The filter
+7.4.3 The filter
The filter can be any program that reads a translation from standard
@@ -849,7 +870,7 @@ used filter is `sed´.
-
+
Note: It is your responsibility to ensure that the filter can cope
with input encoded in the translation catalog's encoding. If the
filter wants input in a particular encoding, you can in a first step
@@ -862,7 +883,7 @@ locale, by using the LC_ALL
environment variable.
-
+
Note: Most translations in a translation catalog don't end with a newline
character. For this reason, it is important that the filter
recognizes its last input line even if it ends without a newline, and that
@@ -874,7 +895,7 @@ does not have this limitation.
-7.4.4 Useful filter-options when the filter is `sed´
+7.4.4 Useful filter-options when the filter is `sed´
@@ -882,16 +903,16 @@ does not have this limitation.
-
- `--expression=script´
-
-
-
+
+
Add script to the commands to be executed.
- `-f scriptfile´
-
- `--file=scriptfile´
-
-
-
+
+
Add the contents of scriptfile to the commands to be executed.
- `-n´
@@ -900,49 +921,49 @@ Add the contents of scriptfile to the commands to be executed.
-
- `--silent´
-
-
-
-
+
+
+
Suppress automatic printing of pattern space.
-7.4.5 Output details
+7.4.5 Output details
- `--force-po´
-
-
+
Always write an output file even if it contains no message.
- `--indent´
-
-
+
Write the .po file using indented style.
- `--keep-header´
-
-
+
Keep the header entry, i.e. the message with `msgid ""´, unmodified,
instead of filtering it. By default, the header entry is subject to
filtering like any other message.
- `--no-location´
-
-
+
Do not write `#: filename:line´ lines.
- `--add-location´
-
-
+
Generate `#: filename:line´ lines (default).
- `--strict´
-
-
+
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
@@ -951,18 +972,25 @@ GNU extensions.
-
- `--width=number´
-
-
-
+
+
Set the output page width. Long strings in the output files will be
split across multiple lines in order to ensure that each line's width
(= number of screen columns) is less or equal to the given number.
+
- `--no-wrap´
+
-
+
+Do not break long message lines. Message lines whose width exceeds the
+output page width will not be split into several lines. Only file reference
+lines which are wider than the output page width will be split.
+
- `-s´
-
- `--sort-output´
-
-
-
+
+
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
@@ -970,15 +998,15 @@ for the translator to understand each message's context.
-
- `--sort-by-file´
-
-
-
+
+
Sort output by file location.
-7.4.6 Informative output
+7.4.6 Informative output
@@ -986,35 +1014,35 @@ Sort output by file location.
-
- `--help´
-
-
-
+
+
Display this help and exit.
- `-V´
-
- `--version´
-
-
-
+
+
Output version information and exit.
-7.5 Invoking the msguniq
Program
+7.5 Invoking the msguniq
Program
msguniq [option] [inputfile]
-
-
+
+
The msguniq
program unifies duplicate translations in a translation
catalog. It finds duplicate translations of the same message ID. Such
duplicates are invalid input for other programs like msgfmt
,
@@ -1029,7 +1057,7 @@ discarded.
-7.5.1 Input file location
+7.5.1 Input file location
@@ -1041,8 +1069,8 @@ Input PO file.
-
- `--directory=directory´
-
-
-
+
+
Add directory to the list of directories. Source files are
searched relative to this list of directories. The resulting `.po´
file will be written relative to the current directory, though.
@@ -1055,7 +1083,7 @@ If no inputfile is given or if it is `-´, standard
-
7.5.2 Output file location
+7.5.2 Output file location
@@ -1063,8 +1091,8 @@ If no inputfile is given or if it is `-´, standard
-
- `--output-file=file´
-
-
-
+
+
Write output to specified file.
@@ -1076,7 +1104,7 @@ or if it is `-´.
-7.5.3 Message selection
+7.5.3 Message selection
@@ -1084,23 +1112,23 @@ or if it is `-´.
-
- `--repeated´
-
-
-
+
+
Print only duplicates.
- `-u´
-
- `--unique´
-
-
-
+
+
Print only unique messages, discard duplicates.
-7.5.4 Output details
+7.5.4 Output details
@@ -1108,45 +1136,45 @@ Print only unique messages, discard duplicates.
-
- `--to-code=name´
-
-
-
+
+
Specify encoding for output.
- `--use-first´
-
-
+
Use first available translation for each message. Don't merge several
translations into one.
- `--force-po´
-
-
+
Always write an output file even if it contains no message.
- `-i´
-
- `--indent´
-
-
-
+
+
Write the .po file using indented style.
- `--no-location´
-
-
+
Do not write `#: filename:line´ lines.
- `-n´
-
- `--add-location´
-
-
-
+
+
Generate `#: filename:line´ lines (default).
- `--strict´
-
-
+
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
@@ -1155,18 +1183,25 @@ GNU extensions.
-
- `--width=number´
-
-
-
+
+
Set the output page width. Long strings in the output files will be
split across multiple lines in order to ensure that each line's width
(= number of screen columns) is less or equal to the given number.
+
- `--no-wrap´
+
-
+
+Do not break long message lines. Message lines whose width exceeds the
+output page width will not be split into several lines. Only file reference
+lines which are wider than the output page width will be split.
+
- `-s´
-
- `--sort-output´
-
-
-
+
+
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
@@ -1174,15 +1209,15 @@ for the translator to understand each message's context.
-
- `--sort-by-file´
-
-
-
+
+
Sort output by file location.
-7.5.5 Informative output
+7.5.5 Informative output
@@ -1190,34 +1225,34 @@ Sort output by file location.
-
- `--help´
-
-
-
+
+
Display this help and exit.
- `-V´
-
- `--version´
-
-
-
+
+
Output version information and exit.
-7.6 Invoking the msgcomm
Program
+7.6 Invoking the msgcomm
Program
msgcomm [option] [inputfile]...
-
+
The msgcomm
program finds messages which are common to two or more
of the specified PO files.
By using the --more-than
option, greater commonality may be requested
@@ -1231,7 +1266,7 @@ cumulated.
-7.6.1 Input file location
+7.6.1 Input file location
@@ -1243,8 +1278,8 @@ Input files.
-
- `--files-from=file´
-
-
-
+
+
Read the names of the input files from file instead of getting
them from the command line.
@@ -1252,8 +1287,8 @@ them from the command line.
-
- `--directory=directory´
-
-
-
+
+
Add directory to the list of directories. Source files are
searched relative to this list of directories. The resulting `.po´
file will be written relative to the current directory, though.
@@ -1266,7 +1301,7 @@ If inputfile is `-´, standard input is read.
-
7.6.2 Output file location
+7.6.2 Output file location
@@ -1274,8 +1309,8 @@ If inputfile is `-´, standard input is read.
-
- `--output-file=file´
-
-
-
+
+
Write output to specified file.
@@ -1287,7 +1322,7 @@ or if it is `-´.
-7.6.3 Message selection
+7.6.3 Message selection
@@ -1295,8 +1330,8 @@ or if it is `-´.
-
- `--less-than=number´
-
-
-
+
+
Print messages with less than number definitions, defaults to infinite
if not set.
@@ -1304,8 +1339,8 @@ if not set.
-
- `--more-than=number´
-
-
-
+
+
Print messages with more than number definitions, defaults to 1 if not
set.
@@ -1313,8 +1348,8 @@ set.
-
- `--unique´
-
-
-
+
+
Shorthand for `--less-than=2´. Requests that only unique messages be
printed.
@@ -1322,39 +1357,39 @@ printed.
-
7.6.4 Output details
+7.6.4 Output details
- `--force-po´
-
-
+
Always write an output file even if it contains no message.
- `-i´
-
- `--indent´
-
-
-
+
+
Write the .po file using indented style.
- `--no-location´
-
-
+
Do not write `#: filename:line´ lines.
- `-n´
-
- `--add-location´
-
-
-
+
+
Generate `#: filename:line´ lines (default).
- `--strict´
-
-
+
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
@@ -1363,18 +1398,25 @@ GNU extensions.
-
- `--width=number´
-
-
-
+
+
Set the output page width. Long strings in the output files will be
split across multiple lines in order to ensure that each line's width
(= number of screen columns) is less or equal to the given number.
+
- `--no-wrap´
+
-
+
+Do not break long message lines. Message lines whose width exceeds the
+output page width will not be split into several lines. Only file reference
+lines which are wider than the output page width will be split.
+
- `-s´
-
- `--sort-output´
-
-
-
+
+
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
@@ -1382,20 +1424,20 @@ for the translator to understand each message's context.
-
- `--sort-by-file´
-
-
-
+
+
Sort output by file location.
- `--omit-header´
-
-
+
Don't write header with `msgid ""´ entry.
-7.6.5 Informative output
+7.6.5 Informative output
@@ -1403,34 +1445,34 @@ Don't write header with `msgid ""´ entry.
-
- `--help´
-
-
-
+
+
Display this help and exit.
- `-V´
-
- `--version´
-
-
-
+
+
Output version information and exit.
-7.7 Invoking the msgcmp
Program
+7.7 Invoking the msgcmp
Program
msgcmp [option] def.po ref.pot
-
+
The msgcmp
program compares two Uniforum style .po files to check that
both contain the same set of msgid strings. The def.po file is an
existing PO file with the translations. The ref.pot file is the last
@@ -1442,7 +1484,7 @@ used to produce better diagnostics.
-7.7.1 Input file location
+7.7.1 Input file location
@@ -1458,8 +1500,8 @@ References to the sources.
-
- `--directory=directory´
-
-
-
+
+
Add directory to the list of directories. Source files are
searched relative to this list of directories.
@@ -1467,7 +1509,7 @@ searched relative to this list of directories.
-
7.7.2 Operation modifiers
+7.7.2 Operation modifiers
@@ -1475,15 +1517,15 @@ searched relative to this list of directories.
-
- `--multi-domain´
-
-
-
+
+
Apply ref.pot to each of the domains in def.po.
-7.7.3 Informative output
+7.7.3 Informative output
@@ -1491,42 +1533,42 @@ Apply ref.pot to each of the domains in def.po.
-
- `--help´
-
-
-
+
+
Display this help and exit.
- `-V´
-
- `--version´
-
-
-
+
+
Output version information and exit.
-7.8 Invoking the msgattrib
Program
+7.8 Invoking the msgattrib
Program
msgattrib [option] [inputfile]
-
-
+
+
The msgattrib
program filters the messages of a translation catalog
according to their attributes, and manipulates the attributes.
-7.8.1 Input file location
+7.8.1 Input file location
@@ -1538,8 +1580,8 @@ Input PO file.
-
- `--directory=directory´
-
-
-
+
+
Add directory to the list of directories. Source files are
searched relative to this list of directories. The resulting `.po´
file will be written relative to the current directory, though.
@@ -1552,7 +1594,7 @@ If no inputfile is given or if it is `-´, standard
-
7.8.2 Output file location
+7.8.2 Output file location
@@ -1560,8 +1602,8 @@ If no inputfile is given or if it is `-´, standard
-
- `--output-file=file´
-
-
-
+
+
Write output to specified file.
@@ -1573,48 +1615,48 @@ or if it is `-´.
-7.8.3 Message selection
+7.8.3 Message selection
- `--translated´
-
-
+
Keep translated messages, remove untranslated messages.
- `--untranslated´
-
-
+
Keep untranslated messages, remove translated messages.
- `--no-fuzzy´
-
-
+
Remove `fuzzy' marked messages.
- `--only-fuzzy´
-
-
+
Keep `fuzzy' marked messages, remove all other messsages.
- `--no-obsolete´
-
-
+
Remove obsolete #~ messages.
- `--only-obsolete´
-
-
+
Keep obsolete #~ messages, remove all other messages.
-7.8.4 Attribute manipulation
+7.8.4 Attribute manipulation
-
+
Attributes are modified after the message selection/removal has been
performed.
@@ -1623,33 +1665,33 @@ performed.
- `--set-fuzzy´
-
-
+
Set all messages `fuzzy'.
- `--clear-fuzzy´
-
-
+
Set all messages non-`fuzzy'.
- `--set-obsolete´
-
-
+
Set all messages obsolete.
- `--clear-obsolete´
-
-
+
Set all messages non-obsolete.
- `--fuzzy´
-
-
+
Synonym for `--only-fuzzy --clear-fuzzy´: It keeps only the fuzzy
messages and removes their `fuzzy' mark.
- `--obsolete´
-
-
+
Synonym for `--only-obsolete --clear-obsolete´: It keeps only the
obsolete messages and makes them non-obsolete.
@@ -1657,39 +1699,39 @@ obsolete messages and makes them non-obsolete.
-
7.8.5 Output details
+7.8.5 Output details
- `--force-po´
-
-
+
Always write an output file even if it contains no message.
- `-i´
-
- `--indent´
-
-
-
+
+
Write the .po file using indented style.
- `--no-location´
-
-
+
Do not write `#: filename:line´ lines.
- `-n´
-
- `--add-location´
-
-
-
+
+
Generate `#: filename:line´ lines (default).
- `--strict´
-
-
+
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
@@ -1698,18 +1740,25 @@ GNU extensions.
-
- `--width=number´
-
-
-
+
+
Set the output page width. Long strings in the output files will be
split across multiple lines in order to ensure that each line's width
(= number of screen columns) is less or equal to the given number.
+
- `--no-wrap´
+
-
+
+Do not break long message lines. Message lines whose width exceeds the
+output page width will not be split into several lines. Only file reference
+lines which are wider than the output page width will be split.
+
- `-s´
-
- `--sort-output´
-
-
-
+
+
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
@@ -1717,15 +1766,15 @@ for the translator to understand each message's context.
-
- `--sort-by-file´
-
-
-
+
+
Sort output by file location.
-7.8.6 Informative output
+7.8.6 Informative output
@@ -1733,34 +1782,34 @@ Sort output by file location.
-
- `--help´
-
-
-
+
+
Display this help and exit.
- `-V´
-
- `--version´
-
-
-
+
+
Output version information and exit.
-7.9 Invoking the msgen
Program
+7.9 Invoking the msgen
Program
msgen [option] inputfile
-
+
The msgen
program creates an English translation catalog. The
input file is the last created English PO file, or a PO Template file
(generally created by xgettext). Untranslated entries are assigned a
@@ -1775,7 +1824,7 @@ the header entry, whereas msgen
doesn't.
-7.9.1 Input file location
+7.9.1 Input file location
@@ -1787,8 +1836,8 @@ Input PO or POT file.
-
- `--directory=directory´
-
-
-
+
+
Add directory to the list of directories. Source files are
searched relative to this list of directories. The resulting `.po´
file will be written relative to the current directory, though.
@@ -1801,7 +1850,7 @@ If inputfile is `-´, standard input is read.
-
7.9.2 Output file location
+7.9.2 Output file location
@@ -1809,8 +1858,8 @@ If inputfile is `-´, standard input is read.
-
- `--output-file=file´
-
-
-
+
+
Write output to specified file.
@@ -1822,36 +1871,36 @@ or if it is `-´.
-7.9.3 Output details
+7.9.3 Output details
- `--force-po´
-
-
+
Always write an output file even if it contains no message.
- `-i´
-
- `--indent´
-
-
-
+
+
Write the .po file using indented style.
- `--no-location´
-
-
+
Do not write `#: filename:line´ lines.
- `--add-location´
-
-
+
Generate `#: filename:line´ lines (default).
- `--strict´
-
-
+
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
@@ -1860,18 +1909,25 @@ GNU extensions.
-
- `--width=number´
-
-
-
+
+
Set the output page width. Long strings in the output files will be
split across multiple lines in order to ensure that each line's width
(= number of screen columns) is less or equal to the given number.
+
- `--no-wrap´
+
-
+
+Do not break long message lines. Message lines whose width exceeds the
+output page width will not be split into several lines. Only file reference
+lines which are wider than the output page width will be split.
+
- `-s´
-
- `--sort-output´
-
-
-
+
+
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
@@ -1879,15 +1935,15 @@ for the translator to understand each message's context.
-
- `--sort-by-file´
-
-
-
+
+
Sort output by file location.
-7.9.4 Informative output
+7.9.4 Informative output
@@ -1895,34 +1951,34 @@ Sort output by file location.
-
- `--help´
-
-
-
+
+
Display this help and exit.
- `-V´
-
- `--version´
-
-
-
+
+
Output version information and exit.
-7.10 Invoking the msgexec
Program
+7.10 Invoking the msgexec
Program
msgexec [option] command [command-option]
-
+
The msgexec
program applies a command to all translations of a
translation catalog.
The command can be any program that reads a translation from standard
@@ -1932,15 +1988,15 @@ across all invocations.
-
+
A special builtin command called `0´ outputs the translation, followed
by a null byte. The output of `msgexec 0´ is suitable as input for
`xargs -0´.
-
-
+
+
During each command invocation, the environment variable
MSGEXEC_MSGID
is bound to the message's msgid, and the environment
variable MSGEXEC_LOCATION
is bound to the location in the PO file
@@ -1948,7 +2004,7 @@ of the message.
-
+
Note: It is your responsibility to ensure that the command can cope
with input encoded in the translation catalog's encoding. If the
command wants input in a particular encoding, you can in a first step
@@ -1962,7 +2018,7 @@ locale, by using the LC_ALL
environment variable.
-7.10.1 Input file location
+7.10.1 Input file location
@@ -1970,16 +2026,16 @@ locale, by using the LC_ALL
environment variable.
-
- `--input=inputfile´
-
-
-
+
+
Input PO file.
- `-D directory´
-
- `--directory=directory´
-
-
-
+
+
Add directory to the list of directories. Source files are
searched relative to this list of directories. The resulting `.po´
file will be written relative to the current directory, though.
@@ -1992,7 +2048,7 @@ If no inputfile is given or if it is `-´, standard
-
7.10.2 Informative output
+7.10.2 Informative output
@@ -2000,16 +2056,16 @@ If no inputfile is given or if it is `-´, standard
-
- `--help´
-
-
-
+
+
Display this help and exit.
- `-V´
-
- `--version´
-
-
-
+
+
Output version information and exit.
diff --git a/doc/gettext_8.html b/doc/gettext_8.html
index 5bc1047be..5e369c4ac 100644
--- a/doc/gettext_8.html
+++ b/doc/gettext_8.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - 8 Producing Binary MO Files
@@ -10,29 +10,29 @@ Go to the first, previous<
-
8 Producing Binary MO Files
+8 Producing Binary MO Files
-8.1 Invoking the msgfmt
Program
+8.1 Invoking the msgfmt
Program
msgfmt [option] filename.po ...
-
+
The msgfmt
programs generates a binary message catalog from a textual
translation description.
-8.1.1 Input file location
+8.1.1 Input file location
@@ -42,8 +42,8 @@ translation description.
-
- `--directory=directory´
-
-
-
+
+
Add directory to the list of directories. Source files are
searched relative to this list of directories. The resulting `.po´
file will be written relative to the current directory, though.
@@ -56,7 +56,7 @@ If an input file is `-´, standard input is read.
-
8.1.2 Operation mode
+8.1.2 Operation mode
@@ -64,27 +64,27 @@ If an input file is `-´, standard input is read.
-
- `--java´
-
-
-
-
+
+
+
Java mode: generate a Java
ResourceBundle
class.
- `--java2´
-
-
+
Like --java, and assume Java2 (JDK 1.2 or higher).
- `--tcl´
-
-
-
+
+
Tcl mode: generate a tcl/msgcat `.msg´ file.
-8.1.3 Output file location
+8.1.3 Output file location
@@ -92,13 +92,13 @@ Tcl mode: generate a tcl/msgcat `.msg´ file.
-
- `--output-file=file´
-
-
-
+
+
Write output to specified file.
- `--strict´
-
-
+
Direct the program to work strictly following the Uniforum/Sun
implementation. Currently this only affects the naming of the output
file. If this option is not given the name of the output file is the
@@ -117,7 +117,7 @@ If the output file is `-´, output is written to st
-
8.1.4 Output file location in Java mode
+8.1.4 Output file location in Java mode
@@ -125,22 +125,22 @@ If the output file is `-´, output is written to st
-
- `--resource=resource´
-
-
-
+
+
Specify the resource name.
- `-l locale´
-
- `--locale=locale´
-
-
-
+
+
Specify the locale name, either a language specification of the form ll
or a combined language and country specification of the form ll_CC.
- `-d directory´
-
-
+
Specify the base directory of classes directory hierarchy.
@@ -153,7 +153,7 @@ is written under the specified directory.
-8.1.5 Output file location in Tcl mode
+8.1.5 Output file location in Tcl mode
@@ -161,14 +161,14 @@ is written under the specified directory.
-
- `--locale=locale´
-
-
-
+
+
Specify the locale name, either a language specification of the form ll
or a combined language and country specification of the form ll_CC.
- `-d directory´
-
-
+
Specify the base directory of `.msg´ message catalogs.
@@ -180,7 +180,7 @@ written in the specified directory.
-8.1.6 Input file interpretation
+8.1.6 Input file interpretation
@@ -188,15 +188,15 @@ written in the specified directory.
-
- `--check´
-
-
-
+
+
Perform all the checks implied by
--check-format
, --check-header
,
--check-domain
.
- `--check-format´
-
-
-
+
+
Check language dependent format strings.
If the string represents a format string used in a
@@ -215,19 +215,19 @@ used in a
printf
-like function and so msgfmt
might rep
errors where there are none.
To solve this problem the programmer can dictate the decision to the
-xgettext
program (see section 3.4 Special Comments preceding Keywords). The translator should not
+xgettext
program (see section 3.5 Special Comments preceding Keywords). The translator should not
consider removing the flag from the #, line. This "fix" would be
reversed again as soon as msgmerge
is called the next time.
- `--check-header´
-
-
-Verify presence and contents of the header entry. See section 5.2 Filling in the Header Entry,
+
+Verify presence and contents of the header entry. See section 5.2 Filling in the Header Entry,
for a description of the various fields in the header entry.
- `--check-domain´
-
-
+
Check for conflicts between domain directives and the
--output-file
option
@@ -235,18 +235,18 @@ option
-
- `--check-compatibility´
-
-
-
-
+
+
+
Check that GNU msgfmt behaves like X/Open msgfmt. This will give an error
when attempting to use the GNU extensions.
- `--check-accelerators[=char]´
-
-
-
-
-
+
+
+
+
Check presence of keyboard accelerators for menu items. This is based on
the convention used in some GUIs that a keyboard accelerator in a menu
item string is designated by an immediately preceding `&´ character.
@@ -261,9 +261,9 @@ instead of `&´.
-
- `--use-fuzzy´
-
-
-
-
+
+
+
Use fuzzy entries in output. Note that using this option is usually wrong,
because fuzzy messages are exactly those which have not been validated by
a human translator.
@@ -272,7 +272,7 @@ a human translator.
-
8.1.7 Output details
+8.1.7 Output details
@@ -280,13 +280,13 @@ a human translator.
-
- `--alignment=number´
-
-
-
+
+
Align strings to number bytes (default: 1).
- `--no-hash´
-
-
+
Don't include a hash table in the binary file. Lookup will be more expensive
at run time (binary search instead of hash table lookup).
@@ -294,7 +294,7 @@ at run time (binary search instead of hash table lookup).
-
8.1.8 Informative output
+8.1.8 Informative output
@@ -302,54 +302,54 @@ at run time (binary search instead of hash table lookup).
-
- `--help´
-
-
-
+
+
Display this help and exit.
- `-V´
-
- `--version´
-
-
-
+
+
Output version information and exit.
- `--statistics´
-
-
+
Print statistics about translations.
- `-v´
-
- `--verbose´
-
-
-
+
+
Increase verbosity level.
-8.2 Invoking the msgunfmt
Program
+8.2 Invoking the msgunfmt
Program
msgunfmt [option] [file]...
-
+
The msgunfmt
program converts a binary message catalog to a
Uniforum style .po file.
-8.2.1 Operation mode
+8.2.1 Operation mode
@@ -357,22 +357,22 @@ Uniforum style .po file.
-
- `--java´
-
-
-
-
+
+
+
Java mode: input is a Java
ResourceBundle
class.
- `--tcl´
-
-
-
+
+
Tcl mode: input is a tcl/msgcat `.msg´ file.
-8.2.2 Input file location
+8.2.2 Input file location
@@ -388,7 +388,7 @@ If no input file is given or if it is `-´, standar
-8.2.3 Input file location in Java mode
+8.2.3 Input file location in Java mode
@@ -396,16 +396,16 @@ If no input file is given or if it is `-´, standar
-
- `--resource=resource´
-
-
-
+
+
Specify the resource name.
- `-l locale´
-
- `--locale=locale´
-
-
-
+
+
Specify the locale name, either a language specification of the form ll
or a combined language and country specification of the form ll_CC.
@@ -418,7 +418,7 @@ separated with an underscore. The class is located using the
CLASSPATH
-8.2.4 Input file location in Tcl mode
+8.2.4 Input file location in Tcl mode
@@ -426,14 +426,14 @@ separated with an underscore. The class is located using the CLASSPATH
- `--locale=locale´
-
-
-
+
+
Specify the locale name, either a language specification of the form ll
or a combined language and country specification of the form ll_CC.
- `-d directory´
-
-
+
Specify the base directory of `.msg´ message catalogs.
@@ -445,7 +445,7 @@ located in the specified directory.
-8.2.5 Output file location
+8.2.5 Output file location
@@ -453,8 +453,8 @@ located in the specified directory.
-
- `--output-file=file´
-
-
-
+
+
Write output to specified file.
@@ -466,26 +466,26 @@ or if it is `-´.
-8.2.6 Output details
+8.2.6 Output details
- `--force-po´
-
-
+
Always write an output file even if it contains no message.
- `-i´
-
- `--indent´
-
-
-
+
+
Write the .po file using indented style.
- `--strict´
-
-
+
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
@@ -494,19 +494,26 @@ GNU extensions.
-
- `--width=number´
-
-
-
+
+
Set the output page width. Long strings in the output files will be
split across multiple lines in order to ensure that each line's width
(= number of screen columns) is less or equal to the given number.
+
- `--no-wrap´
+
-
+
+Do not break long message lines. Message lines whose width exceeds the
+output page width will not be split into several lines. Only file reference
+lines which are wider than the output page width will be split.
+
- `-s´
-
- `--sort-output´
-
-
-
-
+
+
+
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
@@ -514,7 +521,7 @@ for the translator to understand each message's context.
-
8.2.7 Informative output
+8.2.7 Informative output
@@ -522,34 +529,34 @@ for the translator to understand each message's context.
-
- `--help´
-
-
-
+
+
Display this help and exit.
- `-V´
-
- `--version´
-
-
-
+
+
Output version information and exit.
- `-v´
-
- `--verbose´
-
-
-
+
+
Increase verbosity level.
-8.3 The Format of GNU MO Files
+8.3 The Format of GNU MO Files
@@ -558,7 +565,7 @@ which appears below.
-
+
The first two words serve the identification of the file. The magic
number will always signal GNU MO files. The number is stored in the
byte order of the generating machine, so the magic number really is
@@ -606,7 +613,7 @@ translated tables, making the system information very easy to find.
-
+
The size S of the hash table can be zero. In this case, the
hash table itself is not contained in the MO file. Some people might
prefer this because a precomputed hashing table takes disk space, and
@@ -627,7 +634,7 @@ machines, a correct alignment will speed things up.
-
+
Plural forms are stored by letting the plural of the original string
follow the singular of the original string, separated through a
NUL byte. The length which appears in the string descriptor
diff --git a/doc/gettext_9.html b/doc/gettext_9.html
index fc782157a..4f084b96c 100644
--- a/doc/gettext_9.html
+++ b/doc/gettext_9.html
@@ -1,7 +1,7 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - 9 The User's View
@@ -10,7 +10,7 @@ Go to the first, previous<
-
9 The User's View
+9 The User's View
When GNU gettext
will truly have reached its goal, average users
@@ -43,11 +43,11 @@ for both installers and end users.
-
9.1 The Current `ABOUT-NLS´ Matrix
+9.1 The Current `ABOUT-NLS´ Matrix
@@ -57,7 +57,7 @@ may check the distribution for the `ABOUT-NLS´ information file,
some `ll.po´ files, often kept together into some `po/´
directory, or for an `intl/´ directory. Internationalized packages
have usually many `ll.po´ files, where ll represents
-the language. section 9.3 Magic for End Users for a complete description of the format
+the language. section 9.3 Magic for End Users for a complete description of the format
for ll.
@@ -75,10 +75,10 @@ Translation Project sites, and also on most GNU archive sites.
-9.2 Magic for Installers
+9.2 Magic for Installers
@@ -97,7 +97,7 @@ produces programs totally unable to translate messages.
-
+
Internationalized packages have usually many `ll.po´
files. Unless
translations are disabled, all those available are installed together
@@ -109,20 +109,20 @@ codes, stating which languages are allowed.
-9.3 Magic for End Users
+9.3 Magic for End Users
-
+
We consider here those packages using GNU gettext
internally,
and for which the installers did not disable translation at
configure time. Then, users only have to set the LANG
environment variable to the appropriate `ll_CC´
-combination prior to using the programs in the package. See section 9.1 The Current `ABOUT-NLS´ Matrix.
+combination prior to using the programs in the package. See section 9.1 The Current `ABOUT-NLS´ Matrix.
For example, let's presume a German site. At the shell prompt, users
merely have to execute `setenv LANG de_DE´ (in csh
) or
`export LANG; LANG=de_DE´ (in sh
). They could even do
diff --git a/doc/gettext_foot.html b/doc/gettext_foot.html
index 9e75451f4..87ad64aa7 100644
--- a/doc/gettext_foot.html
+++ b/doc/gettext_foot.html
@@ -1,14 +1,14 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - Footnotes
-GNU gettext tools, version 0.11.1
+GNU gettext tools, version 0.11.2
Native Language Support Library and Tools
-Edition 0.11.1, 5 March 2002
+Edition 0.11.2, 22 April 2002
Ulrich Drepper
Jim Meyering
François Pinard
@@ -36,7 +36,7 @@ variables.
Additions are welcome. Send appropriate information to
bug-glibc-manual@gnu.org.
-This document was generated on 7 March 2002 using the
+This document was generated on 24 April 2002 using the
texi2html
translator version 1.52a.
diff --git a/doc/gettext_toc.html b/doc/gettext_toc.html
index c272ae277..803c04e2a 100644
--- a/doc/gettext_toc.html
+++ b/doc/gettext_toc.html
@@ -1,14 +1,14 @@
+ from gettext.texi on 24 April 2002 -->
GNU gettext utilities - Table of Contents
-GNU gettext tools, version 0.11.1
+GNU gettext tools, version 0.11.2
Native Language Support Library and Tools
-Edition 0.11.1, 5 March 2002
+Edition 0.11.2, 22 April 2002
Ulrich Drepper
Jim Meyering
François Pinard
@@ -35,299 +35,300 @@
- 3 Preparing Program Sources
- 3.1 Triggering
gettext
Operations
- - 3.2 How Marks Appear in Sources
-
- 3.3 Marking Translatable Strings
-
- 3.4 Special Comments preceding Keywords
-
- 3.5 Special Cases of Translatable Strings
+
- 3.2 Preparing Translatable Strings
+
- 3.3 How Marks Appear in Sources
+
- 3.4 Marking Translatable Strings
+
- 3.5 Special Comments preceding Keywords
+
- 3.6 Special Cases of Translatable Strings
- - 4 Making the PO Template File
+
- 4 Making the PO Template File
-- 4.1 Invoking the
xgettext
Program
+ - 4.1 Invoking the
xgettext
Program
-- 4.1.1 Input file location
-
- 4.1.2 Output file location
-
- 4.1.3 Choice of input file language
-
- 4.1.4 Operation mode
-
- 4.1.5 Language=C/C++ specific options
-
- 4.1.6 Output details
-
- 4.1.7 Informative output
+
- 4.1.1 Input file location
+
- 4.1.2 Output file location
+
- 4.1.3 Choice of input file language
+
- 4.1.4 Operation mode
+
- 4.1.5 Language=C/C++ specific options
+
- 4.1.6 Output details
+
- 4.1.7 Informative output
- - 5 Creating a New PO File
+
- 5 Creating a New PO File
-
- 6 Updating Existing PO Files
+
- 6 Updating Existing PO Files
-- 6.1 Invoking the
msgmerge
Program
+ - 6.1 Invoking the
msgmerge
Program
-- 6.1.1 Input file location
-
- 6.1.2 Operation mode
-
- 6.1.3 Output file location
-
- 6.1.4 Output file location in update mode
-
- 6.1.5 Operation modifiers
-
- 6.1.6 Output details
-
- 6.1.7 Informative output
+
- 6.1.1 Input file location
+
- 6.1.2 Operation mode
+
- 6.1.3 Output file location
+
- 6.1.4 Output file location in update mode
+
- 6.1.5 Operation modifiers
+
- 6.1.6 Output details
+
- 6.1.7 Informative output
- - 6.2 Translated Entries
-
- 6.3 Fuzzy Entries
-
- 6.4 Untranslated Entries
-
- 6.5 Obsolete Entries
-
- 6.6 Modifying Translations
-
- 6.7 Modifying Comments
-
- 6.8 Details of Sub Edition
-
- 6.9 C Sources Context
-
- 6.10 Consulting Auxiliary PO Files
-
- 6.11 Using Translation Compendia
+
- 6.2 Translated Entries
+
- 6.3 Fuzzy Entries
+
- 6.4 Untranslated Entries
+
- 6.5 Obsolete Entries
+
- 6.6 Modifying Translations
+
- 6.7 Modifying Comments
+
- 6.8 Details of Sub Edition
+
- 6.9 C Sources Context
+
- 6.10 Consulting Auxiliary PO Files
+
- 6.11 Using Translation Compendia
- - 7 Manipulating PO Files
+
- 7 Manipulating PO Files
-- 7.1 Invoking the
msgcat
Program
+ - 7.1 Invoking the
msgcat
Program
- - 7.2 Invoking the
msgconv
Program
+ - 7.2 Invoking the
msgconv
Program
- - 7.3 Invoking the
msggrep
Program
+ - 7.3 Invoking the
msggrep
Program
- - 7.4 Invoking the
msgfilter
Program
+ - 7.4 Invoking the
msgfilter
Program
-- 7.4.1 Input file location
-
- 7.4.2 Output file location
-
- 7.4.3 The filter
-
- 7.4.4 Useful filter-options when the filter is `sed´
-
- 7.4.5 Output details
-
- 7.4.6 Informative output
+
- 7.4.1 Input file location
+
- 7.4.2 Output file location
+
- 7.4.3 The filter
+
- 7.4.4 Useful filter-options when the filter is `sed´
+
- 7.4.5 Output details
+
- 7.4.6 Informative output
- - 7.5 Invoking the
msguniq
Program
+ - 7.5 Invoking the
msguniq
Program
- - 7.6 Invoking the
msgcomm
Program
+ - 7.6 Invoking the
msgcomm
Program
- - 7.7 Invoking the
msgcmp
Program
+ - 7.7 Invoking the
msgcmp
Program
- - 7.8 Invoking the
msgattrib
Program
+ - 7.8 Invoking the
msgattrib
Program
-- 7.8.1 Input file location
-
- 7.8.2 Output file location
-
- 7.8.3 Message selection
-
- 7.8.4 Attribute manipulation
-
- 7.8.5 Output details
-
- 7.8.6 Informative output
+
- 7.8.1 Input file location
+
- 7.8.2 Output file location
+
- 7.8.3 Message selection
+
- 7.8.4 Attribute manipulation
+
- 7.8.5 Output details
+
- 7.8.6 Informative output
- - 7.9 Invoking the
msgen
Program
+ - 7.9 Invoking the
msgen
Program
- - 7.10 Invoking the
msgexec
Program
+ - 7.10 Invoking the
msgexec
Program
- - 8 Producing Binary MO Files
+
- 8 Producing Binary MO Files
-- 8.1 Invoking the
msgfmt
Program
+ - 8.1 Invoking the
msgfmt
Program
-- 8.1.1 Input file location
-
- 8.1.2 Operation mode
-
- 8.1.3 Output file location
-
- 8.1.4 Output file location in Java mode
-
- 8.1.5 Output file location in Tcl mode
-
- 8.1.6 Input file interpretation
-
- 8.1.7 Output details
-
- 8.1.8 Informative output
+
- 8.1.1 Input file location
+
- 8.1.2 Operation mode
+
- 8.1.3 Output file location
+
- 8.1.4 Output file location in Java mode
+
- 8.1.5 Output file location in Tcl mode
+
- 8.1.6 Input file interpretation
+
- 8.1.7 Output details
+
- 8.1.8 Informative output
- - 8.2 Invoking the
msgunfmt
Program
+ - 8.2 Invoking the
msgunfmt
Program
-- 8.2.1 Operation mode
-
- 8.2.2 Input file location
-
- 8.2.3 Input file location in Java mode
-
- 8.2.4 Input file location in Tcl mode
-
- 8.2.5 Output file location
-
- 8.2.6 Output details
-
- 8.2.7 Informative output
+
- 8.2.1 Operation mode
+
- 8.2.2 Input file location
+
- 8.2.3 Input file location in Java mode
+
- 8.2.4 Input file location in Tcl mode
+
- 8.2.5 Output file location
+
- 8.2.6 Output details
+
- 8.2.7 Informative output
- - 8.3 The Format of GNU MO Files
+
- 8.3 The Format of GNU MO Files
- - 9 The User's View
+
- 9 The User's View
-
- 10 The Programmer's View
+
- 10 The Programmer's View
-- 10.1 About
catgets
+ - 10.1 About
catgets
- - 10.2 About
gettext
+ - 10.2 About
gettext
-- 10.2.1 The Interface
-
- 10.2.2 Solving Ambiguities
-
- 10.2.3 Locating Message Catalog Files
-
- 10.2.4 How to specify the output character set
gettext
uses
- - 10.2.5 Additional functions for plural forms
-
- 10.2.6 How to use
gettext
in GUI programs
- - 10.2.7 Optimization of the *gettext functions
+
- 10.2.1 The Interface
+
- 10.2.2 Solving Ambiguities
+
- 10.2.3 Locating Message Catalog Files
+
- 10.2.4 How to specify the output character set
gettext
uses
+ - 10.2.5 Additional functions for plural forms
+
- 10.2.6 How to use
gettext
in GUI programs
+ - 10.2.7 Optimization of the *gettext functions
- - 10.3 Comparing the Two Interfaces
-
- 10.4 Using libintl.a in own programs
-
- 10.5 Being a
gettext
grok
- - 10.6 Temporary Notes for the Programmers Chapter
+
- 10.3 Comparing the Two Interfaces
+
- 10.4 Using libintl.a in own programs
+
- 10.5 Being a
gettext
grok
+ - 10.6 Temporary Notes for the Programmers Chapter
-- 10.6.1 Temporary - Two Possible Implementations
-
- 10.6.2 Temporary - About
catgets
- - 10.6.3 Temporary - Why a single implementation
-
- 10.6.4 Temporary - Notes
+
- 10.6.1 Temporary - Two Possible Implementations
+
- 10.6.2 Temporary - About
catgets
+ - 10.6.3 Temporary - Why a single implementation
+
- 10.6.4 Temporary - Notes
- - 11 The Translator's View
+
- 11 The Translator's View
-
- 12 The Maintainer's View
+
- 12 The Maintainer's View
-- 12.1 Flat or Non-Flat Directory Structures
-
- 12.2 Prerequisite Works
-
- 12.3 Invoking the
gettextize
Program
- - 12.4 Files You Must Create or Alter
+
- 12.1 Flat or Non-Flat Directory Structures
+
- 12.2 Prerequisite Works
+
- 12.3 Invoking the
gettextize
Program
+ - 12.4 Files You Must Create or Alter
-- 12.4.1 `POTFILES.in´ in `po/´
-
- 12.4.2 `LINGUAS´ in `po/´
-
- 12.4.3 `Makefile´ pieces in `po/´
-
- 12.4.4 `configure.in´ at top level
-
- 12.4.5 `config.guess´, `config.sub´ at top level
-
- 12.4.6 `aclocal.m4´ at top level
-
- 12.4.7 `acconfig.h´ at top level
-
- 12.4.8 `Makefile.in´ at top level
-
- 12.4.9 `Makefile.in´ in `src/´
-
- 12.4.10 `gettext.h´ in `lib/´
+
- 12.4.1 `POTFILES.in´ in `po/´
+
- 12.4.2 `LINGUAS´ in `po/´
+
- 12.4.3 `Makefile´ pieces in `po/´
+
- 12.4.4 `configure.in´ at top level
+
- 12.4.5 `config.guess´, `config.sub´ at top level
+
- 12.4.6 `aclocal.m4´ at top level
+
- 12.4.7 `acconfig.h´ at top level
+
- 12.4.8 `Makefile.in´ at top level
+
- 12.4.9 `Makefile.in´ in `src/´
+
- 12.4.10 `gettext.h´ in `lib/´
- - 12.5 Autoconf macros for use in `configure.in´
+
- 12.5 Autoconf macros for use in `configure.in´
- - 13 Other Programming Languages
+
- 13 Other Programming Languages
-- 13.1 The Language Implementor's View
-
- 13.2 The Programmer's View
-
- 13.3 The Translator's View
-
- 13.4 The Maintainer's View
-
- 13.5 Individual Programming Languages
+
- 13.1 The Language Implementor's View
+
- 13.2 The Programmer's View
+
- 13.3 The Translator's View
+
- 13.4 The Maintainer's View
+
- 13.5 Individual Programming Languages
-- 13.5.1 C, C++, Objective C
-
- 13.5.2 sh - Shell Script
-
- 13.5.3 bash - Bourne-Again Shell Script
-
- 13.5.4 Python
-
- 13.5.5 GNU clisp - Common Lisp
-
- 13.5.6 GNU clisp C sources
-
- 13.5.7 Emacs Lisp
-
- 13.5.8 librep
-
- 13.5.9 GNU Smalltalk
-
- 13.5.10 Java
-
- 13.5.11 GNU awk
-
- 13.5.12 Pascal - Free Pascal Compiler
-
- 13.5.13 wxWindows library
-
- 13.5.14 YCP - YaST2 scripting language
-
- 13.5.15 Tcl - Tk's scripting language
-
- 13.5.16 Perl
-
- 13.5.17 PHP Hypertext Preprocessor
-
- 13.5.18 Pike
+
- 13.5.1 C, C++, Objective C
+
- 13.5.2 sh - Shell Script
+
- 13.5.3 bash - Bourne-Again Shell Script
+
- 13.5.4 Python
+
- 13.5.5 GNU clisp - Common Lisp
+
- 13.5.6 GNU clisp C sources
+
- 13.5.7 Emacs Lisp
+
- 13.5.8 librep
+
- 13.5.9 GNU Smalltalk
+
- 13.5.10 Java
+
- 13.5.11 GNU awk
+
- 13.5.12 Pascal - Free Pascal Compiler
+
- 13.5.13 wxWindows library
+
- 13.5.14 YCP - YaST2 scripting language
+
- 13.5.15 Tcl - Tk's scripting language
+
- 13.5.16 Perl
+
- 13.5.17 PHP Hypertext Preprocessor
+
- 13.5.18 Pike
- - 13.6 Internationalizable Data
+
- 13.6 Internationalizable Data
- - 14 Concluding Remarks
-
-
- A Language Codes
-
- B Country Codes
-
- Program Index
-
- Option Index
-
- Variable Index
-
- PO Mode Index
-
- Autoconf Macro Index
-
- General Index
+
- 14 Concluding Remarks
+
+
- A Language Codes
+
- B Country Codes
+
- Program Index
+
- Option Index
+
- Variable Index
+
- PO Mode Index
+
- Autoconf Macro Index
+
- General Index
-This document was generated on 7 March 2002 using the
+This document was generated on 24 April 2002 using the
texi2html
translator version 1.52a.
diff --git a/doc/iso-639.texi b/doc/iso-639.texi
index 24fe2f01a..b007b4adb 100644
--- a/doc/iso-639.texi
+++ b/doc/iso-639.texi
@@ -116,6 +116,8 @@ Indonesian (formerly in).
Interlingue.
@item ik
Inupiak.
+@item io
+Ido.
@item is
Icelandic.
@item it
@@ -124,7 +126,7 @@ Italian.
Inuktitut.
@item ja
Japanese.
-@item jw
+@item jv
Javanese.
@item ka
Georgian.
@@ -314,6 +316,8 @@ Uzbek.
Vietnamese.
@item vo
Volap@"{u}k; Volapuk.
+@item wa
+Walloon.
@item wo
Wolof.
@item xh
diff --git a/doc/version.texi b/doc/version.texi
index 450d73e5a..bcf990e62 100644
--- a/doc/version.texi
+++ b/doc/version.texi
@@ -1,4 +1,4 @@
-@set UPDATED 5 March 2002
-@set UPDATED-MONTH March 2002
-@set EDITION 0.11.1
-@set VERSION 0.11.1
+@set UPDATED 22 April 2002
+@set UPDATED-MONTH April 2002
+@set EDITION 0.11.2
+@set VERSION 0.11.2
diff --git a/man/bind_textdomain_codeset.3 b/man/bind_textdomain_codeset.3
index d451be0bb..37cf23231 100644
--- a/man/bind_textdomain_codeset.3
+++ b/man/bind_textdomain_codeset.3
@@ -10,7 +10,7 @@
.\" GNU gettext source code and manual
.\" LI18NUX 2000 Globalization Specification
.\"
-.TH BIND_TEXTDOMAIN_CODESET 3 "May 2001" "GNU gettext 0.11.1"
+.TH BIND_TEXTDOMAIN_CODESET 3 "May 2001" "GNU gettext 0.11.2"
.SH NAME
bind_textdomain_codeset \- set encoding of message translations
.SH SYNOPSIS
diff --git a/man/bindtextdomain.3 b/man/bindtextdomain.3
index 4b56a286f..ad617a983 100644
--- a/man/bindtextdomain.3
+++ b/man/bindtextdomain.3
@@ -10,7 +10,7 @@
.\" GNU gettext source code and manual
.\" LI18NUX 2000 Globalization Specification
.\"
-.TH BINDTEXTDOMAIN 3 "May 2001" "GNU gettext 0.11.1"
+.TH BINDTEXTDOMAIN 3 "May 2001" "GNU gettext 0.11.2"
.SH NAME
bindtextdomain \- set directory containing message catalogs
.SH SYNOPSIS
diff --git a/man/gettext.3 b/man/gettext.3
index ab343d968..391bcc4a6 100644
--- a/man/gettext.3
+++ b/man/gettext.3
@@ -10,7 +10,7 @@
.\" GNU gettext source code and manual
.\" LI18NUX 2000 Globalization Specification
.\"
-.TH GETTEXT 3 "May 2001" "GNU gettext 0.11.1"
+.TH GETTEXT 3 "May 2001" "GNU gettext 0.11.2"
.SH NAME
gettext, dgettext, dcgettext \- translate message
.SH SYNOPSIS
diff --git a/man/msgattrib.1 b/man/msgattrib.1
index 4e488f1ac..75d04e449 100644
--- a/man/msgattrib.1
+++ b/man/msgattrib.1
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGATTRIB "1" "March 2002" "GNU gettext 0.11" GNU
+.TH MSGATTRIB "1" "April 2002" "GNU gettext 0.11.2" GNU
.SH NAME
msgattrib \- attribute matching and manipulation on message catalog
.SH SYNOPSIS
@@ -92,6 +92,10 @@ write out strict Uniforum conforming .po file
\fB\-w\fR, \fB\-\-width\fR=\fINUMBER\fR
set output page width
.TP
+\fB\-\-no\-wrap\fR
+do not break long message lines, longer than
+the output page width, into several lines
+.TP
\fB\-s\fR, \fB\-\-sort\-output\fR
generate sorted output
.TP
diff --git a/man/msgattrib.1.html b/man/msgattrib.1.html
index 8c7e4ffc6..dae8ee196 100644
--- a/man/msgattrib.1.html
+++ b/man/msgattrib.1.html
@@ -372,6 +372,19 @@ write out strict Uniforum conforming .po file
set output page width
+
+
+
+--no-wrap
+
+
+
+
+do not break long message lines, longer than the output page
+width, into several lines
+
diff --git a/man/msgcat.1 b/man/msgcat.1
index 2d4662c1b..ccdac593b 100644
--- a/man/msgcat.1
+++ b/man/msgcat.1
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGCAT "1" "March 2002" "GNU gettext 0.11" GNU
+.TH MSGCAT "1" "April 2002" "GNU gettext 0.11.2" GNU
.SH NAME
msgcat \- combines several message catalogs
.SH SYNOPSIS
@@ -85,6 +85,10 @@ write out strict Uniforum conforming .po file
\fB\-w\fR, \fB\-\-width\fR=\fINUMBER\fR
set output page width
.TP
+\fB\-\-no\-wrap\fR
+do not break long message lines, longer than
+the output page width, into several lines
+.TP
\fB\-s\fR, \fB\-\-sort\-output\fR
generate sorted output
.TP
diff --git a/man/msgcat.1.html b/man/msgcat.1.html
index 694983466..c2afdb76b 100644
--- a/man/msgcat.1.html
+++ b/man/msgcat.1.html
@@ -305,6 +305,19 @@ write out strict Uniforum conforming .po file
set output page width
+
+
+
+--no-wrap
+
+
+
+
+do not break long message lines, longer than the output page
+width, into several lines
+
diff --git a/man/msgcmp.1 b/man/msgcmp.1
index 36423d323..14bacd7fe 100644
--- a/man/msgcmp.1
+++ b/man/msgcmp.1
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGCMP "1" "March 2002" "GNU gettext 0.11" GNU
+.TH MSGCMP "1" "April 2002" "GNU gettext 0.11.2" GNU
.SH NAME
msgcmp \- compare message catalog and template
.SH SYNOPSIS
diff --git a/man/msgcomm.1 b/man/msgcomm.1
index 73ffd4d8d..f8ff982a9 100644
--- a/man/msgcomm.1
+++ b/man/msgcomm.1
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGCOMM "1" "March 2002" "GNU gettext 0.11" GNU
+.TH MSGCOMM "1" "April 2002" "GNU gettext 0.11.2" GNU
.SH NAME
msgcomm \- match two message catalogs
.SH SYNOPSIS
@@ -77,6 +77,10 @@ write out strict Uniforum conforming .po file
\fB\-w\fR, \fB\-\-width\fR=\fINUMBER\fR
set output page width
.TP
+\fB\-\-no\-wrap\fR
+do not break long message lines, longer than
+the output page width, into several lines
+.TP
\fB\-s\fR, \fB\-\-sort\-output\fR
generate sorted output
.TP
diff --git a/man/msgcomm.1.html b/man/msgcomm.1.html
index 048be5818..e5676119a 100644
--- a/man/msgcomm.1.html
+++ b/man/msgcomm.1.html
@@ -278,6 +278,19 @@ write out strict Uniforum conforming .po file
set output page width
+
+
+
+--no-wrap
+
+
+
+
+do not break long message lines, longer than the output page
+width, into several lines
+
diff --git a/man/msgconv.1 b/man/msgconv.1
index 28e836ebc..3fa679191 100644
--- a/man/msgconv.1
+++ b/man/msgconv.1
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGCONV "1" "March 2002" "GNU gettext 0.11" GNU
+.TH MSGCONV "1" "April 2002" "GNU gettext 0.11.2" GNU
.SH NAME
msgconv \- character set conversion for message catalog
.SH SYNOPSIS
@@ -59,6 +59,10 @@ strict Uniforum output style
\fB\-w\fR, \fB\-\-width\fR=\fINUMBER\fR
set output page width
.TP
+\fB\-\-no\-wrap\fR
+do not break long message lines, longer than
+the output page width, into several lines
+.TP
\fB\-s\fR, \fB\-\-sort\-output\fR
generate sorted output
.TP
diff --git a/man/msgconv.1.html b/man/msgconv.1.html
index 6c0962e87..c284436b8 100644
--- a/man/msgconv.1.html
+++ b/man/msgconv.1.html
@@ -239,6 +239,19 @@ strict Uniforum output style
set output page width
+
+
+
+--no-wrap
+
+
+
+
+do not break long message lines, longer than the output page
+width, into several lines
+
diff --git a/man/msgen.1 b/man/msgen.1
index e137a687e..a15ee3ff5 100644
--- a/man/msgen.1
+++ b/man/msgen.1
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGEN "1" "March 2002" "GNU gettext 0.11" GNU
+.TH MSGEN "1" "April 2002" "GNU gettext 0.11.2" GNU
.SH NAME
msgen \- create English message catalog
.SH SYNOPSIS
@@ -56,6 +56,10 @@ strict Uniforum output style
\fB\-w\fR, \fB\-\-width\fR=\fINUMBER\fR
set output page width
.TP
+\fB\-\-no\-wrap\fR
+do not break long message lines, longer than
+the output page width, into several lines
+.TP
\fB\-s\fR, \fB\-\-sort\-output\fR
generate sorted output
.TP
diff --git a/man/msgen.1.html b/man/msgen.1.html
index 1300e67eb..519996197 100644
--- a/man/msgen.1.html
+++ b/man/msgen.1.html
@@ -215,6 +215,19 @@ strict Uniforum output style
set output page width
+
+
+
+--no-wrap
+
+
+
+
+do not break long message lines, longer than the output page
+width, into several lines
+
diff --git a/man/msgexec.1 b/man/msgexec.1
index d38cf86ce..75b9a3be3 100644
--- a/man/msgexec.1
+++ b/man/msgexec.1
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGEXEC "1" "March 2002" "GNU gettext 0.11" GNU
+.TH MSGEXEC "1" "April 2002" "GNU gettext 0.11.2" GNU
.SH NAME
msgexec \- process translations of message catalog
.SH SYNOPSIS
diff --git a/man/msgfilter.1 b/man/msgfilter.1
index 0a8c6ba51..d04bd4edb 100644
--- a/man/msgfilter.1
+++ b/man/msgfilter.1
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGFILTER "1" "March 2002" "GNU gettext 0.11" GNU
+.TH MSGFILTER "1" "April 2002" "GNU gettext 0.11.2" GNU
.SH NAME
msgfilter \- edit translations of message catalog
.SH SYNOPSIS
@@ -70,6 +70,10 @@ strict Uniforum output style
\fB\-w\fR, \fB\-\-width\fR=\fINUMBER\fR
set output page width
.TP
+\fB\-\-no\-wrap\fR
+do not break long message lines, longer than
+the output page width, into several lines
+.TP
\fB\-s\fR, \fB\-\-sort\-output\fR
generate sorted output
.TP
diff --git a/man/msgfilter.1.html b/man/msgfilter.1.html
index ced988476..f2bcd35e8 100644
--- a/man/msgfilter.1.html
+++ b/man/msgfilter.1.html
@@ -278,6 +278,19 @@ strict Uniforum output style
set output page width
+
+
+
+--no-wrap
+
+
+
+
+do not break long message lines, longer than the output page
+width, into several lines
+
diff --git a/man/msgfmt.1 b/man/msgfmt.1
index b96e2ae06..4d6a11ea9 100644
--- a/man/msgfmt.1
+++ b/man/msgfmt.1
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGFMT "1" "March 2002" "GNU gettext 0.11" GNU
+.TH MSGFMT "1" "April 2002" "GNU gettext 0.11.2" GNU
.SH NAME
msgfmt \- compile message catalog to binary format
.SH SYNOPSIS
diff --git a/man/msggrep.1 b/man/msggrep.1
index 9662a967e..85056778f 100644
--- a/man/msggrep.1
+++ b/man/msggrep.1
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGGREP "1" "March 2002" "GNU gettext 0.11" GNU
+.TH MSGGREP "1" "April 2002" "GNU gettext 0.11.2" GNU
.SH NAME
msggrep \- pattern matching on message catalog
.SH SYNOPSIS
@@ -100,6 +100,10 @@ strict Uniforum output style
\fB\-w\fR, \fB\-\-width\fR=\fINUMBER\fR
set output page width
.TP
+\fB\-\-no\-wrap\fR
+do not break long message lines, longer than
+the output page width, into several lines
+.TP
\fB\-\-sort\-output\fR
generate sorted output
.TP
diff --git a/man/msggrep.1.html b/man/msggrep.1.html
index 536c398fb..a7ed13648 100644
--- a/man/msggrep.1.html
+++ b/man/msggrep.1.html
@@ -377,6 +377,19 @@ strict Uniforum output style
set output page width
+
+
+
+--no-wrap
+
+
+
+
+do not break long message lines, longer than the output page
+width, into several lines
+
diff --git a/man/msginit.1 b/man/msginit.1
index 0c2b3b83d..d1b708644 100644
--- a/man/msginit.1
+++ b/man/msginit.1
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGINIT "1" "March 2002" "GNU gettext 0.11" GNU
+.TH MSGINIT "1" "April 2002" "GNU gettext 0.11.2" GNU
.SH NAME
msginit \- initialize a message catalog
.SH SYNOPSIS
@@ -36,6 +36,10 @@ assume the PO file is automatically generated
.TP
\fB\-w\fR, \fB\-\-width\fR=\fINUMBER\fR
set output page width
+.TP
+\fB\-\-no\-wrap\fR
+do not break long message lines, longer than
+the output page width, into several lines
.SS "Informative output:"
.TP
\fB\-h\fR, \fB\-\-help\fR
diff --git a/man/msginit.1.html b/man/msginit.1.html
index e698a6292..a11afef50 100644
--- a/man/msginit.1.html
+++ b/man/msginit.1.html
@@ -144,6 +144,19 @@ assume the PO file is automatically generated
set output page width
+
+
+
+--no-wrap
+
+
+
+
+do not break long message lines, longer than the output page
+width, into several lines
+
diff --git a/man/msgmerge.1 b/man/msgmerge.1
index 65b0248f4..93dace9f2 100644
--- a/man/msgmerge.1
+++ b/man/msgmerge.1
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGMERGE "1" "March 2002" "GNU gettext 0.11" GNU
+.TH MSGMERGE "1" "April 2002" "GNU gettext 0.11.2" GNU
.SH NAME
msgmerge \- merge message catalog and template
.SH SYNOPSIS
@@ -102,6 +102,10 @@ strict Uniforum output style
\fB\-w\fR, \fB\-\-width\fR=\fINUMBER\fR
set output page width
.TP
+\fB\-\-no\-wrap\fR
+do not break long message lines, longer than
+the output page width, into several lines
+.TP
\fB\-s\fR, \fB\-\-sort\-output\fR
generate sorted output
.TP
diff --git a/man/msgmerge.1.html b/man/msgmerge.1.html
index 95cfdb981..84bc2a845 100644
--- a/man/msgmerge.1.html
+++ b/man/msgmerge.1.html
@@ -375,6 +375,19 @@ strict Uniforum output style
set output page width
+
+
+
+--no-wrap
+
+
+
+
+do not break long message lines, longer than the output page
+width, into several lines
+
diff --git a/man/msgunfmt.1 b/man/msgunfmt.1
index f105a5054..ed83754af 100644
--- a/man/msgunfmt.1
+++ b/man/msgunfmt.1
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGUNFMT "1" "March 2002" "GNU gettext 0.11" GNU
+.TH MSGUNFMT "1" "April 2002" "GNU gettext 0.11.2" GNU
.SH NAME
msgunfmt \- uncompile message catalog from binary format
.SH SYNOPSIS
@@ -71,6 +71,10 @@ write strict uniforum style
\fB\-w\fR, \fB\-\-width\fR=\fINUMBER\fR
set output page width
.TP
+\fB\-\-no\-wrap\fR
+do not break long message lines, longer than
+the output page width, into several lines
+.TP
\fB\-s\fR, \fB\-\-sort\-output\fR
generate sorted output
.SS "Informative output:"
diff --git a/man/msgunfmt.1.html b/man/msgunfmt.1.html
index 5da8f18cb..2ee4c09a0 100644
--- a/man/msgunfmt.1.html
+++ b/man/msgunfmt.1.html
@@ -285,6 +285,19 @@ write strict uniforum style
set output page width
+
+
+
+--no-wrap
+
+
+
+
+do not break long message lines, longer than the output page
+width, into several lines
+
diff --git a/man/msguniq.1 b/man/msguniq.1
index 7d01dbe9a..cab6ddd0e 100644
--- a/man/msguniq.1
+++ b/man/msguniq.1
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGUNIQ "1" "March 2002" "GNU gettext 0.11" GNU
+.TH MSGUNIQ "1" "April 2002" "GNU gettext 0.11.2" GNU
.SH NAME
msguniq \- unify duplicate translations in message catalog
.SH SYNOPSIS
@@ -74,6 +74,10 @@ write out strict Uniforum conforming .po file
\fB\-w\fR, \fB\-\-width\fR=\fINUMBER\fR
set output page width
.TP
+\fB\-\-no\-wrap\fR
+do not break long message lines, longer than
+the output page width, into several lines
+.TP
\fB\-s\fR, \fB\-\-sort\-output\fR
generate sorted output
.TP
diff --git a/man/msguniq.1.html b/man/msguniq.1.html
index 7c4fe3a35..29c9e15b5 100644
--- a/man/msguniq.1.html
+++ b/man/msguniq.1.html
@@ -278,6 +278,19 @@ write out strict Uniforum conforming .po file
set output page width
+
+
+
+--no-wrap
+
+
+
+
+do not break long message lines, longer than the output page
+width, into several lines
+
diff --git a/man/ngettext.3 b/man/ngettext.3
index 351c59cbe..b0f204422 100644
--- a/man/ngettext.3
+++ b/man/ngettext.3
@@ -10,7 +10,7 @@
.\" GNU gettext source code and manual
.\" LI18NUX 2000 Globalization Specification
.\"
-.TH NGETTEXT 3 "May 2001" "GNU gettext 0.11.1"
+.TH NGETTEXT 3 "May 2001" "GNU gettext 0.11.2"
.SH NAME
ngettext, dngettext, dcngettext \- translate message and choose plural form
.SH SYNOPSIS
diff --git a/man/textdomain.3 b/man/textdomain.3
index 9030d39c3..141ca93e3 100644
--- a/man/textdomain.3
+++ b/man/textdomain.3
@@ -10,7 +10,7 @@
.\" GNU gettext source code and manual
.\" LI18NUX 2000 Globalization Specification
.\"
-.TH TEXTDOMAIN 3 "May 2001" "GNU gettext 0.11.1"
+.TH TEXTDOMAIN 3 "May 2001" "GNU gettext 0.11.2"
.SH NAME
textdomain \- set domain for future gettext() calls
.SH SYNOPSIS
diff --git a/man/xgettext.1 b/man/xgettext.1
index 7cc46802a..c518e0167 100644
--- a/man/xgettext.1
+++ b/man/xgettext.1
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH XGETTEXT "1" "March 2002" "GNU gettext 0.11" GNU
+.TH XGETTEXT "1" "April 2002" "GNU gettext 0.11.2" GNU
.SH NAME
xgettext \- extract gettext strings from source
.SH SYNOPSIS
@@ -99,6 +99,10 @@ write out strict Uniforum conforming .po file
\fB\-w\fR, \fB\-\-width\fR=\fINUMBER\fR
set output page width
.TP
+\fB\-\-no\-wrap\fR
+do not break long message lines, longer than
+the output page width, into several lines
+.TP
\fB\-s\fR, \fB\-\-sort\-output\fR
generate sorted output
.TP
diff --git a/man/xgettext.1.html b/man/xgettext.1.html
index d3571a123..d67fb8e30 100644
--- a/man/xgettext.1.html
+++ b/man/xgettext.1.html
@@ -386,6 +386,19 @@ write out strict Uniforum conforming .po file
set output page width
+
+
+
+--no-wrap
+
+
+
+
+do not break long message lines, longer than the output page
+width, into several lines
+