*/
#undef HAVE_ALLOCA_H
+/* Define to 1 if you have the `argz_count' function. */
+#undef HAVE_ARGZ_COUNT
+
/* Define to 1 if you have the <argz.h> header file. */
#undef HAVE_ARGZ_H
+/* Define to 1 if you have the `argz_next' function. */
+#undef HAVE_ARGZ_NEXT
+
+/* Define to 1 if you have the `argz_stringify' function. */
+#undef HAVE_ARGZ_STRINGIFY
+
/* Define to 1 if you have the `asprintf' function. */
#undef HAVE_ASPRINTF
/* Define to 1 if you have the `atexit' function. */
#undef HAVE_ATEXIT
+/* Define to 1 if the compiler understands __builtin_expect. */
+#undef HAVE_BUILTIN_EXPECT
+
/* Define to 1 if you have the `canonicalize_file_name' function. */
#undef HAVE_CANONICALIZE_FILE_NAME
/* Define to 1 if you have the <dlfcn.h> header file. */
#undef HAVE_DLFCN_H
-/* Define to 1 if you don't have `vprintf' but do have `_doprnt.' */
-#undef HAVE_DOPRNT
-
/* Define if you have the declaration of environ. */
#undef HAVE_ENVIRON_DECL
-/* Define if you have the declaration of errno. */
-#undef HAVE_ERRNO_DECL
-
/* Define to 1 if you have the `fwprintf' function. */
#undef HAVE_FWPRINTF
/* Define to 1 if you have the <limits.h> header file. */
#undef HAVE_LIMITS_H
-/* Define to 1 if you have the <locale.h> header file. */
-#undef HAVE_LOCALE_H
-
/* Define if you have the 'long double' type. */
#undef HAVE_LONG_DOUBLE
/* Define if you have the 'long long' type. */
#undef HAVE_LONG_LONG
-/* Define to 1 if you have the <malloc.h> header file. */
-#undef HAVE_MALLOC_H
+/* Define to 1 if you have the <mach-o/dyld.h> header file. */
+#undef HAVE_MACH_O_DYLD_H
/* Define to 1 if you have the `memmove' function. */
#undef HAVE_MEMMOVE
_GNU_SOURCE is defined. */
#undef HAVE_NL_LOCALE_NAME
-/* Define to 1 if you have the <nl_types.h> header file. */
-#undef HAVE_NL_TYPES_H
-
/* Define if your printf() function supports format strings with positions. */
#undef HAVE_POSIX_PRINTF
/* Define to 1 if you have the <string.h> header file. */
#undef HAVE_STRING_H
+/* Define to 1 if you have the `strstr' function. */
+#undef HAVE_STRSTR
+
/* Define to 1 if you have the `strtoul' function. */
#undef HAVE_STRTOUL
declarations. */
#undef HAVE_VISIBILITY
-/* Define to 1 if you have the `vprintf' function. */
-#undef HAVE_VPRINTF
-
/* Define if you have the 'wchar_t' type. */
#undef HAVE_WCHAR_T
/* Define to 1 if the system has the type `_Bool'. */
#undef HAVE__BOOL
-/* Define to 1 if you have the `__argz_count' function. */
-#undef HAVE___ARGZ_COUNT
-
-/* Define to 1 if you have the `__argz_next' function. */
-#undef HAVE___ARGZ_NEXT
-
-/* Define to 1 if you have the `__argz_stringify' function. */
-#undef HAVE___ARGZ_STRINGIFY
+/* Define to 1 if you have the `_NSGetExecutablePath' function. */
+#undef HAVE__NSGETEXECUTABLEPATH
/* Define to 1 if you have the `__fsetlocking' function. */
#undef HAVE___FSETLOCKING
/* If using the C implementation of alloca, define if you know the
direction of stack growth for your system; otherwise it will be
- automatically deduced at run-time.
+ automatically deduced at runtime.
STACK_DIRECTION > 0 => grows toward higher addresses
STACK_DIRECTION < 0 => grows toward lower addresses
STACK_DIRECTION = 0 => direction of growth unknown */
used. */
#undef __GETOPT_PREFIX
-/* Define to empty if `const' does not conform to ANSI C. */
-#undef const
-
/* Define to `__inline__' or `__inline' if that's what the C compiler
calls it, or to nothing if 'inline' is not supported under any name. */
#ifndef __cplusplus
#undef inline
#endif
-/* Define to `long' if <sys/types.h> does not define. */
-#undef off_t
-
/* Define as the type of the result of subtracting two pointers, if the system
doesn't define it. */
#undef ptrdiff_t
/* Define to empty if the C compiler doesn't support this keyword. */
#undef signed
-/* Define to `unsigned' if <sys/types.h> does not define. */
+/* Define to `unsigned int' if <sys/types.h> does not define. */
#undef size_t
/* Define as a signed type of the same size as size_t. */
#define __libc_lock_init gl_lock_init
#define __libc_lock_lock gl_lock_lock
#define __libc_lock_unlock gl_lock_unlock
-#define __libc_rwlock_t gl_rwlock_t
-#define __libc_rwlock_define gl_rwlock_define
-#define __libc_rwlock_define_initialized gl_rwlock_define_initialized
-#define __libc_rwlock_init gl_rwlock_init
-#define __libc_rwlock_rdlock gl_rwlock_rdlock
-#define __libc_rwlock_wrlock gl_rwlock_wrlock
-#define __libc_rwlock_unlock gl_rwlock_unlock
#define __libc_lock_recursive_t gl_recursive_lock_t
#define __libc_lock_define_recursive gl_recursive_lock_define
#define __libc_lock_define_initialized_recursive gl_recursive_lock_define_initialized
/* On Windows, variables that may be in a DLL must be marked specially. */
-#if (defined _MSC_VER && defined _DLL) || (defined __MINGW32__ && defined DLL_EXPORT)
+#if (defined _MSC_VER && defined _DLL)
# define DLL_VARIABLE __declspec (dllimport)
#else
# define DLL_VARIABLE
#line 1 "plural.y"
/* Expression parsing for plural form selection.
- Copyright (C) 2000-2001, 2003 Free Software Foundation, Inc.
+ Copyright (C) 2000-2001, 2003, 2005 Free Software Foundation, Inc.
Written by Ulrich Drepper <drepper@cygnus.com>, 2000.
This program is free software; you can redistribute it and/or modify it
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
USA. */
-/* The bison generated parser uses alloca. AIX 3 forces us to put this
- declaration at the beginning of the file. The declaration in bison's
- skeleton file comes too late. This must come before <config.h>
- because <config.h> may include arbitrary system headers. */
+/* For bison < 2.0, the bison generated parser uses alloca. AIX 3 forces us
+ to put this declaration at the beginning of the file. The declaration in
+ bison's skeleton file comes too late. This must come before <config.h>
+ because <config.h> may include arbitrary system headers.
+ This can go away once the AM_INTL_SUBDIR macro requires bison >= 2.0. */
#if defined _AIX && !defined __GNUC__
#pragma alloca
#endif
#include <stddef.h>
#include <stdlib.h>
+#include <string.h>
#include "plural-exp.h"
/* The main function generated by the parser is called __gettextparse,
#define YYLEX_PARAM &((struct parse_args *) arg)->cp
#define YYPARSE_PARAM arg
-#line 49 "plural.y"
+#line 51 "plural.y"
#ifndef YYSTYPE
typedef union {
unsigned long int num;
# define YYSTYPE yystype
# define YYSTYPE_IS_TRIVIAL 1
#endif
-#line 55 "plural.y"
+#line 57 "plural.y"
/* Prototypes for local functions. */
static int yylex (YYSTYPE *lval, const char **pexp);
/* YYRLINE[YYN] -- source line where rule number YYN was defined. */
static const short yyrline[] =
{
- 0, 150, 158, 162, 166, 170, 174, 178, 182, 186,
- 190, 194, 199
+ 0, 152, 160, 164, 168, 172, 176, 180, 184, 188,
+ 192, 196, 201
};
#endif
#define YYPURE 1
/* -*-C-*- Note some compilers choke on comments on `#line' lines. */
-#line 3 "/usr/local/share/bison/bison.simple"
+#line 3 "bison.simple"
/* Skeleton output parser for bison,
# endif
#endif
\f
-#line 315 "/usr/local/share/bison/bison.simple"
+#line 315 "bison.simple"
/* The user can define YYPARSE_PARAM as the name of an argument to be passed
switch (yyn) {
case 1:
-#line 151 "plural.y"
+#line 153 "plural.y"
{
if (yyvsp[0].exp == NULL)
YYABORT;
}
break;
case 2:
-#line 159 "plural.y"
+#line 161 "plural.y"
{
yyval.exp = new_exp_3 (qmop, yyvsp[-4].exp, yyvsp[-2].exp, yyvsp[0].exp);
}
break;
case 3:
-#line 163 "plural.y"
+#line 165 "plural.y"
{
yyval.exp = new_exp_2 (lor, yyvsp[-2].exp, yyvsp[0].exp);
}
break;
case 4:
-#line 167 "plural.y"
+#line 169 "plural.y"
{
yyval.exp = new_exp_2 (land, yyvsp[-2].exp, yyvsp[0].exp);
}
break;
case 5:
-#line 171 "plural.y"
+#line 173 "plural.y"
{
yyval.exp = new_exp_2 (yyvsp[-1].op, yyvsp[-2].exp, yyvsp[0].exp);
}
break;
case 6:
-#line 175 "plural.y"
+#line 177 "plural.y"
{
yyval.exp = new_exp_2 (yyvsp[-1].op, yyvsp[-2].exp, yyvsp[0].exp);
}
break;
case 7:
-#line 179 "plural.y"
+#line 181 "plural.y"
{
yyval.exp = new_exp_2 (yyvsp[-1].op, yyvsp[-2].exp, yyvsp[0].exp);
}
break;
case 8:
-#line 183 "plural.y"
+#line 185 "plural.y"
{
yyval.exp = new_exp_2 (yyvsp[-1].op, yyvsp[-2].exp, yyvsp[0].exp);
}
break;
case 9:
-#line 187 "plural.y"
+#line 189 "plural.y"
{
yyval.exp = new_exp_1 (lnot, yyvsp[0].exp);
}
break;
case 10:
-#line 191 "plural.y"
+#line 193 "plural.y"
{
yyval.exp = new_exp_0 (var);
}
break;
case 11:
-#line 195 "plural.y"
+#line 197 "plural.y"
{
if ((yyval.exp = new_exp_0 (num)) != NULL)
yyval.exp->val.num = yyvsp[0].num;
}
break;
case 12:
-#line 200 "plural.y"
+#line 202 "plural.y"
{
yyval.exp = yyvsp[-1].exp;
}
break;
}
-#line 705 "/usr/local/share/bison/bison.simple"
+#line 705 "bison.simple"
\f
yyvsp -= yylen;
#endif
return yyresult;
}
-#line 205 "plural.y"
+#line 207 "plural.y"
void
-This is autosprintf.info, produced by makeinfo version 4.6 from
+This is autosprintf.info, produced by makeinfo version 4.8 from
autosprintf.texi.
INFO-DIR-SECTION C++ libraries
This file provides documentation for GNU `autosprintf' library.
- Copyright (C) 2002 Free Software Foundation, Inc.
+ Copyright (C) 2002-2003 Free Software Foundation, Inc.
- Permission is granted to make and distribute verbatim copies of this
-manual provided the copyright notice and this permission notice are
-preserved on all copies.
+ This manual is free documentation. It is dually licensed under the
+GNU FDL and the GNU GPL. This means that you can redistribute this
+manual under either of these two licenses, at your choice.
- Permission is granted to copy and distribute modified versions of
-this manual under the conditions for verbatim copying, provided that
-the entire resulting derived work is distributed under the terms of a
-permission notice identical to this one.
+ This manual is covered by the GNU FDL. Permission is granted to
+copy, distribute and/or modify this document under the terms of the GNU
+Free Documentation License (FDL), either version 1.2 of the License, or
+(at your option) any later version published by the Free Software
+Foundation (FSF); with no Invariant Sections, with no Front-Cover Text,
+and with no Back-Cover Texts. A copy of the license is at
+`http://www.gnu.org/licenses/fdl.html'.
- Permission is granted to copy and distribute translations of this
-manual into another language, under the above conditions for modified
-versions, except that this permission notice may be stated in a
-translation approved by the Foundation.
+ This manual is covered by the GNU GPL. You can redistribute it
+and/or modify it under the terms of the GNU General Public License
+(GPL), either version 2 of the License, or (at your option) any later
+version published by the Free Software Foundation (FSF). A copy of the
+license is at `http://www.gnu.org/licenses/gpl.html'.
\1f
File: autosprintf.info, Node: Top, Next: Introduction, Prev: (dir), Up: (dir)
\1f
File: autosprintf.info, Node: Introduction, Next: Class autosprintf, Prev: Top, Up: Top
-Introduction
-************
+1 Introduction
+**************
This package makes the C formatted output routines (`fprintf' et al.)
usable in C++ programs, for use with the `<string>' strings and the
\1f
File: autosprintf.info, Node: Class autosprintf, Next: Using autosprintf, Prev: Introduction, Up: Top
-The `autosprintf' class
-***********************
+2 The `autosprintf' class
+*************************
An instance of class `autosprintf' just contains a string with the
formatted output result. Such an instance is usually allocated as an
\1f
File: autosprintf.info, Node: Using autosprintf, Prev: Class autosprintf, Up: Top
-Using `autosprintf' in own programs
-***********************************
+3 Using `autosprintf' in own programs
+*************************************
To use the `autosprintf' class in your programs, you need to add
\1f
Tag Table:
-Node: Top\7f1011
-Node: Introduction\7f1371
-Node: Class autosprintf\7f2518
-Node: Using autosprintf\7f3286
+Node: Top\7f1336
+Node: Introduction\7f1696
+Node: Class autosprintf\7f2847
+Node: Using autosprintf\7f3619
\1f
End Tag Table
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from autosprintf.texi on 18 January 2004 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from autosprintf.texi on 20 April 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU autosprintf</TITLE>
</HEAD>
<BODY>
<P>
to your source code.
The include file defines the class <CODE>autosprintf</CODE>, in a namespace called
-<CODE>gnu</CODE>. The <SAMP>`using´</SAMP> statement makes it possible to use the class
+<CODE>gnu</CODE>. The <SAMP>‘using’</SAMP> statement makes it possible to use the class
without the (otherwise natural) <CODE>gnu::</CODE> prefix.
</P>
<P>
When linking your program, you need to link with <CODE>libasprintf</CODE>, because
that's where the class is defined. In projects using GNU <CODE>autoconf</CODE>,
-this means adding <SAMP>`AC_LIB_LINKFLAGS([asprintf])´</SAMP> to <CODE>configure.in</CODE>
+this means adding <SAMP>‘AC_LIB_LINKFLAGS([asprintf])’</SAMP> to <CODE>configure.in</CODE>
or <CODE>configure.ac</CODE>, and using the @LIBASPRINTF@ Makefile variable that
it provides.
</P>
<P><HR><P>
-This document was generated on 18 January 2004 using the
+This document was generated on 20 April 2006 using the
<A HREF="http://wwwinfo.cern.ch/dis/texi2html/">texi2html</A>
-translator version 1.52a.</P>
+translator version 1.52b.</P>
</BODY>
</HTML>
/* If using the C implementation of alloca, define if you know the
direction of stack growth for your system; otherwise it will be
- automatically deduced at run-time.
+ automatically deduced at runtime.
STACK_DIRECTION > 0 => grows toward higher addresses
STACK_DIRECTION < 0 => grows toward lower addresses
STACK_DIRECTION = 0 => direction of growth unknown */
/* Version number of package */
#undef VERSION
-/* Define to empty if `const' does not conform to ANSI C. */
-#undef const
-
/* Define to `__inline__' or `__inline' if that's what the C compiler
calls it, or to nothing if 'inline' is not supported under any name. */
#ifndef __cplusplus
/* Define to empty if the C compiler doesn't support this keyword. */
#undef signed
-/* Define to `unsigned' if <sys/types.h> does not define. */
+/* Define to `unsigned int' if <sys/types.h> does not define. */
#undef size_t
.\" GNU gettext source code and manual
.\" LI18NUX 2000 Globalization Specification
.\"
-.TH BIND_TEXTDOMAIN_CODESET 3 "May 2001" "GNU gettext 0.14.4"
+.TH BIND_TEXTDOMAIN_CODESET 3 "May 2001" "GNU gettext 0.15"
.SH NAME
bind_textdomain_codeset \- set encoding of message translations
.SH SYNOPSIS
.\" GNU gettext source code and manual
.\" LI18NUX 2000 Globalization Specification
.\"
-.TH BINDTEXTDOMAIN 3 "May 2001" "GNU gettext 0.14.4"
+.TH BINDTEXTDOMAIN 3 "May 2001" "GNU gettext 0.15"
.SH NAME
bindtextdomain \- set directory containing message catalogs
.SH SYNOPSIS
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH ENVSUBST "1" "April 2005" "GNU gettext-runtime 0.14.3" GNU
+.TH ENVSUBST "1" "July 2006" "GNU gettext-runtime 0.15" GNU
.SH NAME
envsubst \- substitutes environment variables in shell format strings
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 2003-2005 Free Software Foundation, Inc.
+Copyright \(co 2003-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 2003-2005 Free Software Foundation, Inc.<br>
+Copyright 2003-2006 Free Software Foundation, Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
MERCHANTABILITY or FITNESS FOR A PARTICULAR
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 1995-1997, 2000-2005 Free Software Foundation,
+Copyright 1995-1997, 2000-2006 Free Software Foundation,
Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH GETTEXT "1" "April 2005" "GNU gettext-runtime 0.14.3" GNU
+.TH GETTEXT "1" "July 2006" "GNU gettext-runtime 0.15" GNU
.SH NAME
gettext \- translate message
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 1995-1997, 2000-2005 Free Software Foundation, Inc.
+Copyright \(co 1995-1997, 2000-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
.\" GNU gettext source code and manual
.\" LI18NUX 2000 Globalization Specification
.\"
-.TH GETTEXT 3 "May 2001" "GNU gettext 0.14.4"
+.TH GETTEXT 3 "May 2001" "GNU gettext 0.15"
.SH NAME
gettext, dgettext, dcgettext \- translate message
.SH SYNOPSIS
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 1995-1997, 2000-2005 Free Software Foundation,
+Copyright 1995-1997, 2000-2006 Free Software Foundation,
Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH NGETTEXT "1" "April 2005" "GNU gettext-runtime 0.14.3" GNU
+.TH NGETTEXT "1" "July 2006" "GNU gettext-runtime 0.15" GNU
.SH NAME
ngettext \- translate message and choose plural form
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 1995-1997, 2000-2005 Free Software Foundation, Inc.
+Copyright \(co 1995-1997, 2000-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
.\" GNU gettext source code and manual
.\" LI18NUX 2000 Globalization Specification
.\"
-.TH NGETTEXT 3 "May 2001" "GNU gettext 0.14.4"
+.TH NGETTEXT 3 "May 2001" "GNU gettext 0.15"
.SH NAME
ngettext, dngettext, dcngettext \- translate message and choose plural form
.SH SYNOPSIS
.\" GNU gettext source code and manual
.\" LI18NUX 2000 Globalization Specification
.\"
-.TH TEXTDOMAIN 3 "May 2001" "GNU gettext 0.14.4"
+.TH TEXTDOMAIN 3 "May 2001" "GNU gettext 0.15"
.SH NAME
textdomain \- set domain for future gettext() calls
.SH SYNOPSIS
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2005-01-14 13:07+0100\n"
+"POT-Creation-Date: 2006-04-20 15:54+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgid "memory exhausted"
msgstr ""
-#: src/envsubst.c:113 src/gettext.c:135 src/ngettext.c:125
+#: src/envsubst.c:114 src/gettext.c:135 src/ngettext.c:125
#, c-format, no-wrap
msgid ""
"Copyright (C) %s Free Software Foundation, Inc.\n"
"warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n"
msgstr ""
-#: src/envsubst.c:118 src/gettext.c:140 src/ngettext.c:130
+#: src/envsubst.c:119 src/gettext.c:140 src/ngettext.c:130
#, c-format
msgid "Written by %s.\n"
msgstr ""
-#: src/envsubst.c:127 src/gettext.c:158 src/ngettext.c:142
+#. This is a proper name. See the gettext manual, section Names.
+#: src/envsubst.c:119
+msgid "Bruno Haible"
+msgstr ""
+
+#: src/envsubst.c:128 src/gettext.c:158 src/ngettext.c:142
#, c-format
msgid "too many arguments"
msgstr ""
-#: src/envsubst.c:138 src/gettext.c:168 src/ngettext.c:154
+#: src/envsubst.c:139 src/gettext.c:168 src/ngettext.c:154
#, c-format
msgid "missing arguments"
msgstr ""
-#: src/envsubst.c:171 src/gettext.c:239 src/ngettext.c:208
+#: src/envsubst.c:172 src/gettext.c:239 src/ngettext.c:208
#, c-format
msgid "Try `%s --help' for more information.\n"
msgstr ""
-#: src/envsubst.c:176
+#: src/envsubst.c:177
#, c-format, no-wrap
msgid "Usage: %s [OPTION] [SHELL-FORMAT]\n"
msgstr ""
-#: src/envsubst.c:181
+#: src/envsubst.c:182
#, c-format, no-wrap
msgid "Substitutes the values of environment variables.\n"
msgstr ""
-#: src/envsubst.c:185
+#: src/envsubst.c:186
#, c-format, no-wrap
msgid "Operation mode:\n"
msgstr ""
-#: src/envsubst.c:188
+#: src/envsubst.c:189
#, c-format, no-wrap
msgid " -v, --variables output the variables occurring in SHELL-FORMAT\n"
msgstr ""
-#: src/envsubst.c:192
+#: src/envsubst.c:193
#, c-format, no-wrap
msgid "Informative output:\n"
msgstr ""
-#: src/envsubst.c:195
+#: src/envsubst.c:196
#, c-format, no-wrap
msgid " -h, --help display this help and exit\n"
msgstr ""
-#: src/envsubst.c:198
+#: src/envsubst.c:199
#, c-format, no-wrap
msgid " -V, --version output version information and exit\n"
msgstr ""
-#: src/envsubst.c:202
+#: src/envsubst.c:203
#, c-format, no-wrap
msgid ""
"In normal operation mode, standard input is copied to standard output,\n"
"standard input are substituted.\n"
msgstr ""
-#: src/envsubst.c:211
+#: src/envsubst.c:212
#, c-format, no-wrap
msgid ""
"When --variables is used, standard input is ignored, and the output consists\n"
"of the environment variables that are referenced in SHELL-FORMAT, one per line.\n"
msgstr ""
-#: src/envsubst.c:215 src/gettext.c:276 src/ngettext.c:242
+#: src/envsubst.c:216 src/gettext.c:276 src/ngettext.c:242
msgid "Report bugs to <bug-gnu-gettext@gnu.org>.\n"
msgstr ""
-#: src/envsubst.c:438
+#: src/envsubst.c:439
#, c-format
msgid "error while reading \"%s\""
msgstr ""
-#: src/envsubst.c:439
+#: src/envsubst.c:440
msgid "standard input"
msgstr ""
+#. This is a proper name. See the gettext manual, section Names.
+#: src/gettext.c:140 src/ngettext.c:130
+msgid "Ulrich Drepper"
+msgstr ""
+
#: src/gettext.c:244
#, c-format, no-wrap
msgid ""
#define DEFAULT_OUTPUT_ALIGNMENT 1
-/* Define to 1 if the `closedir' function returns void instead of `int'. */
-#undef CLOSEDIR_VOID
-
/* Define to one of `_getb67', `GETB67', `getb67' for Cray-2 and Cray-YMP
systems. This function is required for `alloca.c' support on those systems.
*/
*/
#undef HAVE_ALLOCA_H
+/* Define to 1 if you have the `argz_count' function. */
+#undef HAVE_ARGZ_COUNT
+
/* Define to 1 if you have the <argz.h> header file. */
#undef HAVE_ARGZ_H
+/* Define to 1 if you have the `argz_next' function. */
+#undef HAVE_ARGZ_NEXT
+
+/* Define to 1 if you have the `argz_stringify' function. */
+#undef HAVE_ARGZ_STRINGIFY
+
/* Define to 1 if you have the <arpa/inet.h> header file. */
#undef HAVE_ARPA_INET_H
/* Define to 1 if you have the `btowc' function. */
#undef HAVE_BTOWC
+/* Define to 1 if the compiler understands __builtin_expect. */
+#undef HAVE_BUILTIN_EXPECT
+
/* Define to 1 if you have the <byteswap.h> header file. */
#undef HAVE_BYTESWAP_H
don't. */
#undef HAVE_DECL__SNWPRINTF
-/* Define to 1 if you have the <dirent.h> header file, and it defines `DIR'.
- */
+/* Define to 1 if you have the <dirent.h> header file. */
#undef HAVE_DIRENT_H
/* Define to 1 if you have the <dlfcn.h> header file. */
#undef HAVE_DLFCN_H
-/* Define to 1 if you don't have `vprintf' but do have `_doprnt.' */
-#undef HAVE_DOPRNT
-
/* Define if you have the declaration of environ. */
#undef HAVE_ENVIRON_DECL
-/* Define if you have the declaration of errno. */
-#undef HAVE_ERRNO_DECL
-
/* Define to 1 if you have the `fork' function. */
#undef HAVE_FORK
/* Define to 1 if you have the <limits.h> header file. */
#undef HAVE_LIMITS_H
-/* Define to 1 if you have the <locale.h> header file. */
-#undef HAVE_LOCALE_H
-
/* Define if you have the 'long double' type. */
#undef HAVE_LONG_DOUBLE
/* Define if you have the 'long long' type. */
#undef HAVE_LONG_LONG
+/* Define to 1 if you have the <mach-o/dyld.h> header file. */
+#undef HAVE_MACH_O_DYLD_H
+
/* Define to 1 if you have the <malloc.h> header file. */
#undef HAVE_MALLOC_H
/* Define to 1 if you have the `munmap' function. */
#undef HAVE_MUNMAP
-/* Define to 1 if you have the <ndir.h> header file, and it defines `DIR'. */
-#undef HAVE_NDIR_H
-
/* Define if you have <langinfo.h> and it defines the NL_LOCALE_NAME macro if
_GNU_SOURCE is defined. */
#undef HAVE_NL_LOCALE_NAME
-/* Define to 1 if you have the <nl_types.h> header file. */
-#undef HAVE_NL_TYPES_H
-
/* Define to 1 if you have the `pathconf' function. */
#undef HAVE_PATHCONF
/* Define to 1 if `__names' is member of `struct __locale_struct'. */
#undef HAVE_STRUCT___LOCALE_STRUCT___NAMES
-/* Define to 1 if you have the <sys/dir.h> header file, and it defines `DIR'.
- */
-#undef HAVE_SYS_DIR_H
-
-/* Define to 1 if you have the <sys/ndir.h> header file, and it defines `DIR'.
- */
-#undef HAVE_SYS_NDIR_H
-
/* Define to 1 if you have the <sys/param.h> header file. */
#undef HAVE_SYS_PARAM_H
declarations. */
#undef HAVE_VISIBILITY
-/* Define to 1 if you have the `vprintf' function. */
-#undef HAVE_VPRINTF
-
/* Define to 1 if you have the `waitid' function. */
#undef HAVE_WAITID
/* Define to 1 if the system has the type `_Bool'. */
#undef HAVE__BOOL
-/* Define to 1 if you have the `__argz_count' function. */
-#undef HAVE___ARGZ_COUNT
-
-/* Define to 1 if you have the `__argz_next' function. */
-#undef HAVE___ARGZ_NEXT
-
-/* Define to 1 if you have the `__argz_stringify' function. */
-#undef HAVE___ARGZ_STRINGIFY
+/* Define to 1 if you have the `_NSGetExecutablePath' function. */
+#undef HAVE__NSGETEXECUTABLEPATH
/* Define to 1 if you have the `__fsetlocking' function. */
#undef HAVE___FSETLOCKING
/* If using the C implementation of alloca, define if you know the
direction of stack growth for your system; otherwise it will be
- automatically deduced at run-time.
+ automatically deduced at runtime.
STACK_DIRECTION > 0 => grows toward higher addresses
STACK_DIRECTION < 0 => grows toward lower addresses
STACK_DIRECTION = 0 => direction of growth unknown */
/* Define if unsetenv() returns void, not int. */
#undef VOID_UNSETENV
+/* Define when --enable-shared is used on mingw or Cygwin. */
+#undef WOE32DLL
+
+/* Define to 1 to internationalize bison runtime messages. */
+#undef YYENABLE_NLS
+
/* Define to 1 if on AIX 3.
System headers sometimes define this.
We just want to avoid a redefinition error message. */
used. */
#undef __GETOPT_PREFIX
-/* Define to empty if `const' does not conform to ANSI C. */
-#undef const
-
/* Define as 'access' if you don't have the eaccess() function. */
#undef eaccess
/* Define to a replacement function name for getline(). */
#undef getline
+/* A replacement for va_copy, if needed. */
+#define gl_va_copy(a,b) ((a) = (b))
+
/* Define to `__inline__' or `__inline' if that's what the C compiler
calls it, or to nothing if 'inline' is not supported under any name. */
#ifndef __cplusplus
/* Define to `int' if <sys/types.h> does not define. */
#undef mode_t
-/* Define to `long' if <sys/types.h> does not define. */
-#undef off_t
-
/* Define to `int' if <sys/types.h> does not define. */
#undef pid_t
/* Define to empty if the C compiler doesn't support this keyword. */
#undef signed
-/* Define to `unsigned' if <sys/types.h> does not define. */
+/* Define to `unsigned int' if <sys/types.h> does not define. */
#undef size_t
/* Define as a signed type of the same size as size_t. */
<inttypes.h> don't define. */
#undef uintmax_t
+/* Define as a macro for copying va_list variables. */
+#undef va_copy
+
/* Define as `fork' if `vfork' does not work. */
#undef vfork
#define __libc_lock_init gl_lock_init
#define __libc_lock_lock gl_lock_lock
#define __libc_lock_unlock gl_lock_unlock
-#define __libc_rwlock_t gl_rwlock_t
-#define __libc_rwlock_define gl_rwlock_define
-#define __libc_rwlock_define_initialized gl_rwlock_define_initialized
-#define __libc_rwlock_init gl_rwlock_init
-#define __libc_rwlock_rdlock gl_rwlock_rdlock
-#define __libc_rwlock_wrlock gl_rwlock_wrlock
-#define __libc_rwlock_unlock gl_rwlock_unlock
#define __libc_lock_recursive_t gl_recursive_lock_t
#define __libc_lock_define_recursive gl_recursive_lock_define
#define __libc_lock_define_initialized_recursive gl_recursive_lock_define_initialized
#define PAGE_WIDTH 79
/* On Windows, variables that may be in a DLL must be marked specially. */
-#if (defined _MSC_VER && defined _DLL) || (defined __MINGW32__ && defined DLL_EXPORT)
+#if (defined _MSC_VER && defined _DLL) || defined WOE32DLL
# define DLL_VARIABLE __declspec (dllimport)
#else
# define DLL_VARIABLE
This file provides documentation for GNU `gettext' utilities. It
also serves as a reference for the free Translation Project.
- Copyright (C) 1995-1998, 2001-2005 Free Software Foundation, Inc.
-
- Permission is granted to make and distribute verbatim copies of this
-manual provided the copyright notice and this permission notice are
-preserved on all copies.
-
- Permission is granted to copy and distribute modified versions of
-this manual under the conditions for verbatim copying, provided that
-the entire resulting derived work is distributed under the terms of a
-permission notice identical to this one.
-
- Permission is granted to copy and distribute translations of this
-manual into another language, under the above conditions for modified
-versions, except that this permission notice may be stated in a
-translation approved by the Foundation.
+ Copyright (C) 1995-1998, 2001-2006 Free Software Foundation, Inc.
+
+ This manual is free documentation. It is dually licensed under the
+GNU FDL and the GNU GPL. This means that you can redistribute this
+manual under either of these two licenses, at your choice.
+
+ This manual is covered by the GNU FDL. Permission is granted to
+copy, distribute and/or modify this document under the terms of the GNU
+Free Documentation License (FDL), either version 1.2 of the License, or
+(at your option) any later version published by the Free Software
+Foundation (FSF); with no Invariant Sections, with no Front-Cover Text,
+and with no Back-Cover Texts. A copy of the license is included in
+*Note GNU FDL::.
+
+ This manual is covered by the GNU GPL. You can redistribute it
+and/or modify it under the terms of the GNU General Public License
+(GPL), either version 2 of the License, or (at your option) any later
+version published by the Free Software Foundation (FSF). A copy of the
+license is included in *Note GNU GPL::.
\1f
File: gettext.info, Node: Top, Next: Introduction, Prev: (dir), Up: (dir)
***********************
This manual documents the GNU gettext tools and the GNU libintl library,
-version 0.14.4.
+version 0.15.
* Menu:
* Introduction:: Introduction
-* Basics:: PO Files and PO Mode Basics
+* Users:: The User's View
+* PO Files:: The Format of PO Files
* Sources:: Preparing Program Sources
* Template:: Making the PO Template File
* Creating:: Creating a New PO File
* Updating:: Updating Existing PO Files
+* Editing:: Editing PO Files
* Manipulating:: Manipulating PO Files
* Binaries:: Producing Binary MO Files
-* Users:: The User's View
* Programmers:: The Programmer's View
* Translators:: The Translator's View
* Maintainers:: The Maintainer's View
+* Installers:: The Installer's and Distributor's View
* Programming Languages:: Other Programming Languages
* Conclusion:: Concluding Remarks
* Language Codes:: ISO 639 language codes
* Country Codes:: ISO 3166 country codes
+* Licenses:: Licenses
* Program Index:: Index of Programs
* Option Index:: Index of Command-Line Options
* Files:: Files Conveying Translations
* Overview:: Overview of GNU `gettext'
-PO Files and PO Mode Basics
+The User's View
-* Installation:: Completing GNU `gettext' Installation
-* PO Files:: The Format of PO Files
-* Main PO Commands:: Main Commands
-* Entry Positioning:: Entry Positioning
-* Normalizing:: Normalizing Strings in Entries
+* Matrix:: The Current `ABOUT-NLS' Matrix
+* End Users:: Magic for End Users
Preparing Program Sources
+* Importing:: Importing the `gettext' declaration
* Triggering:: Triggering `gettext' Operations
* Preparing Strings:: Preparing Translatable Strings
* Mark Keywords:: How Marks Appear in Sources
Updating Existing PO Files
* msgmerge Invocation:: Invoking the `msgmerge' Program
+
+Editing PO Files
+
+* KBabel:: KDE's PO File Editor
+* Gtranslator:: GNOME's PO File Editor
+* PO Mode:: Emacs's PO File Editor
+
+Emacs's PO File Editor
+
+* Installation:: Completing GNU `gettext' Installation
+* Main PO Commands:: Main Commands
+* Entry Positioning:: Entry Positioning
+* Normalizing:: Normalizing Strings in Entries
* Translated Entries:: Translated Entries
* Fuzzy Entries:: Fuzzy Entries
* Untranslated Entries:: Untranslated Entries
* msgunfmt Invocation:: Invoking the `msgunfmt' Program
* MO Files:: The Format of GNU MO Files
-The User's View
-
-* Matrix:: The Current `ABOUT-NLS' Matrix
-* Installers:: Magic for Installers
-* End Users:: Magic for End Users
-
The Programmer's View
* catgets:: About `catgets'
* Ambiguities:: Solving ambiguities
* Locating Catalogs:: Locating message catalog files
* Charset conversion:: How to request conversion to Unicode
+* Contexts:: Solving ambiguities in GUI programs
* Plural forms:: Additional functions for handling plurals
-* GUI program problems:: Another technique for solving ambiguities
* Optimized gettext:: Optimization of the *gettext functions
Temporary Notes for the Programmers Chapter
* po/POTFILES.in:: `POTFILES.in' in `po/'
* po/LINGUAS:: `LINGUAS' in `po/'
* po/Makevars:: `Makevars' in `po/'
+* po/Rules-*:: Extending `Makefile' in `po/'
* configure.in:: `configure.in' at top level
* config.guess:: `config.guess', `config.sub' at top level
* mkinstalldirs:: `mkinstalldirs' at top level
* php-format:: PHP Format Strings
* gcc-internal-format:: GCC internal Format Strings
* qt-format:: Qt Format Strings
+* boost-format:: Boost Format Strings
Individual Programming Languages
* C#:: C#
* gawk:: GNU awk
* Pascal:: Pascal - Free Pascal Compiler
-* wxWindows:: wxWindows library
+* wxWidgets:: wxWidgets library
* YCP:: YCP - YaST2 scripting language
* Tcl:: Tcl - Tk's scripting language
* Perl:: Perl
* History:: History of GNU `gettext'
* References:: Related Readings
+Licenses
+
+* GNU GPL:: GNU General Public License
+* GNU LGPL:: GNU Lesser General Public License
+* GNU FDL:: GNU Free Documentation License
+
\1f
-File: gettext.info, Node: Introduction, Next: Basics, Prev: Top, Up: Top
+File: gettext.info, Node: Introduction, Next: Users, Prev: Top, Up: Top
1 Introduction
**************
- This manual is still in _DRAFT_ state. Some sections are still
- empty, or almost. We keep merging material from other sources
- (essentially e-mail folders) while the proper integration of this
- material is delayed.
+This chapter explains the goals sought in the creation of GNU `gettext'
+and the free Translation Project. Then, it explains a few broad
+concepts around Native Language Support, and positions message
+translation with regard to other aspects of national and cultural
+variance, as they apply to programs. It also surveys those files used
+to convey the translations. It explains how the various tools interact
+in the initial generation of these files, and later, how the maintenance
+cycle should usually operate.
In this manual, we use _he_ when speaking of the programmer or
maintainer, _she_ when speaking of the translator, and _they_ when
to be useful for people using computers, whatever their sex, race,
religion or nationality!
- This chapter explains the goals sought in the creation of GNU
-`gettext' and the free Translation Project. Then, it explains a few
-broad concepts around Native Language Support, and positions message
-translation with regard to other aspects of national and cultural
-variance, as they apply to to programs. It also surveys those files
-used to convey the translations. It explains how the various tools
-interact in the initial generation of these files, and later, how the
-maintenance cycle should usually operate.
-
Please send suggestions and corrections to:
Internet address:
* A few stand-alone programs to massage in various ways the sets of
translatable strings, or already translated strings.
+ * A library supporting the parsing and creation of files containing
+ translated messages.
+
* A special mode for Emacs(1) which helps preparing these sets and
bringing them up to date.
interrelations will surely help programmers, translators and
maintainers.
- Original C Sources ---> PO mode ---> Marked C Sources ---.
- |
- .---------<--- GNU gettext Library |
- .--- make <---+ |
- | `---------<--------------------+-----------'
+ Original C Sources ---> Preparation ---> Marked C Sources ---.
+ |
+ .---------<--- GNU gettext Library |
+ .--- make <---+ |
+ | `---------<--------------------+---------------'
| |
| .-----<--- PACKAGE.pot <--- xgettext <---' .---<--- PO Compendium
- | | | ^
- | | `---. |
- | `---. +---> PO mode ---.
- | +----> msgmerge ------> LANG.po ---->--------' |
- | .---' |
- | | |
- | `-------------<---------------. |
- | +--- New LANG.po <------------------'
+ | | | ^
+ | | `---. |
+ | `---. +---> PO editor ---.
+ | +----> msgmerge ------> LANG.po ---->--------' |
+ | .---' |
+ | | |
+ | `-------------<---------------. |
+ | +--- New LANG.po <--------------------'
| .--- LANG.gmo <--- msgfmt <---'
| |
| `---> install ---> /.../LANG/PACKAGE.mo ---.
| +---> "Hello world!"
`-------> install ---> /.../bin/PROGRAM -------'
- The indication `PO mode' appears in two places in this picture, and
-you may safely read it as merely meaning "hand editing", using any
-editor of your choice, really. However, for those of you being the
-lucky users of Emacs, PO mode has been specifically created for
-providing a cozy environment for editing or modifying PO files. While
-editing a PO file, PO mode allows for the easy browsing of auxiliary
-and compendium PO files, as well as for following references into the
-set of C program sources from which PO files have been derived. It has
-a few special features, among which are the interactive marking of
-program strings as translatable, and the validation of PO files with
-easy repositioning to PO file lines showing errors.
-
As a programmer, the first step to bringing GNU `gettext' into your
package is identifying, right in the C sources, those strings which are
meant to be translatable, and those which are untranslatable. This
translating concerns with others who target the same native language.
While adding the translated messages into the `LANG.po' PO file, if
-you do not have Emacs handy, you are on your own for ensuring that your
-efforts fully respect the PO file format, and quoting conventions
-(*note PO Files::). This is surely not an impossible task, as this is
-the way many people have handled PO files already for Uniforum or
-Solaris. On the other hand, by using PO mode in Emacs, most details 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 (*note
-Main PO Commands::), you should know how to move between entries (*note
-Entry Positioning::), and how to handle untranslated entries (*note
-Untranslated Entries::).
+you are not using one of the dedicated PO file editors (*note
+Editing::), you are on your own for ensuring that your efforts fully
+respect the PO file format, and quoting conventions (*note PO Files::).
+This is surely not an impossible task, as this is the way many people
+have handled PO files around 1995. On the other hand, by using a PO
+file editor, most details of PO file format are taken care of for you,
+but you have to acquire some familiarity with PO file editor itself.
If some common translations have already been saved into a compendium
PO file, translators may use PO mode for initializing untranslated
the various steps outlined above.
\1f
-File: gettext.info, Node: Basics, Next: Sources, Prev: Introduction, Up: Top
+File: gettext.info, Node: Users, Next: PO Files, Prev: Introduction, Up: Top
-2 PO Files and PO Mode Basics
-*****************************
+2 The User's View
+*****************
-The GNU `gettext' toolset helps programmers and translators at
-producing, updating and using translation files, mainly those PO files
-which are textual, editable files. This chapter stresses the format of
-PO files, and contains a PO mode starter. PO mode description is
-spread throughout this manual instead of being concentrated in one
-place. Here we present only the basics of PO mode.
+When GNU `gettext' will truly have reached its goal, average users
+should feel some kind of astonished pleasure, seeing the effect of that
+strange kind of magic that just makes their own native language appear
+everywhere on their screens. As for naive users, they would ideally
+have no special pleasure about it, merely taking their own language for
+_granted_, and becoming rather unhappy otherwise.
-* Menu:
+ So, let's try to describe here how we would like the magic to
+operate, as we want the users' view to be the simplest, among all ways
+one could look at GNU `gettext'. All other software engineers:
+programmers, translators, maintainers, should work together in such a
+way that the magic becomes possible. This is a long and progressive
+undertaking, and information is available about the progress of the
+Translation Project.
-* Installation:: Completing GNU `gettext' Installation
-* PO Files:: The Format of PO Files
-* Main PO Commands:: Main Commands
-* Entry Positioning:: Entry Positioning
-* Normalizing:: Normalizing Strings in Entries
+ When a package is distributed, there are two kinds of users:
+"installers" who fetch the distribution, unpack it, configure it,
+compile it and install it for themselves or others to use; and "end
+users" that call programs of the package, once these have been
+installed at their site. GNU `gettext' is offering magic for both
+installers and end users.
-\1f
-File: gettext.info, Node: Installation, Next: PO Files, Prev: Basics, Up: Basics
+* Menu:
-2.1 Completing GNU `gettext' Installation
-=========================================
+* Matrix:: The Current `ABOUT-NLS' Matrix
+* End Users:: Magic for End Users
-Once you have received, unpacked, configured and compiled the GNU
-`gettext' distribution, the `make install' command puts in place the
-programs `xgettext', `msgfmt', `gettext', and `msgmerge', as well as
-their available message catalogs. To top off a comfortable
-installation, you might also want to make the PO mode available to your
-Emacs users.
+\1f
+File: gettext.info, Node: Matrix, Next: End Users, Prev: Users, Up: Users
- During the installation of the PO mode, you might want to modify your
-file `.emacs', once and for all, so it contains a few lines looking
-like:
+2.1 The Current `ABOUT-NLS' Matrix
+==================================
- (setq auto-mode-alist
- (cons '("\\.po\\'\\|\\.po\\." . po-mode) auto-mode-alist))
- (autoload 'po-mode "po-mode" "Major mode for translators to edit PO files" t)
+Languages are not equally supported in all packages using GNU
+`gettext'. To know if some package uses GNU `gettext', one may check
+the distribution for the `ABOUT-NLS' information file, for 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. *Note End Users:: for a complete
+description of the format for LL.
- Later, whenever you edit some `.po' file, or any file having the
-string `.po.' within its name, Emacs loads `po-mode.elc' (or
-`po-mode.el') as needed, and automatically activates PO mode commands
-for the associated buffer. The string _PO_ appears in the mode line
-for any buffer for which PO mode is active. Many PO files may be
-active at once in a single Emacs session.
+ More generally, a matrix is available for showing the current state
+of the Translation Project, listing which packages are prepared for
+multi-lingual messages, and which languages are supported by each.
+Because this information changes often, this matrix is not kept within
+this GNU `gettext' manual. This information is often found in file
+`ABOUT-NLS' from various distributions, but is also as old as the
+distribution itself. A recent copy of this `ABOUT-NLS' file,
+containing up-to-date information, should generally be found on the
+Translation Project sites, and also on most GNU archive sites.
- If you are using Emacs version 20 or newer, and have already
-installed the appropriate international fonts on your system, you may
-also tell Emacs how to determine automatically the coding system of
-every PO file. This will often (but not always) cause the necessary
-fonts to be loaded and used for displaying the translations on your
-Emacs screen. For this to happen, add the lines:
+\1f
+File: gettext.info, Node: End Users, Prev: Matrix, Up: Users
- (modify-coding-system-alist 'file "\\.po\\'\\|\\.po\\."
- 'po-find-file-coding-system)
- (autoload 'po-find-file-coding-system "po-mode")
+2.2 Magic for End Users
+=======================
-to your `.emacs' file. If, with this, you still see boxes instead of
-international characters, try a different font set (via Shift Mouse
-button 1).
+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. *Note 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
+this from their `.login' or `.profile' file.
\1f
-File: gettext.info, Node: PO Files, Next: Main PO Commands, Prev: Installation, Up: Basics
+File: gettext.info, Node: PO Files, Next: Sources, Prev: Users, Up: Top
-2.2 The Format of PO Files
-==========================
+3 The Format of PO Files
+************************
+
+The GNU `gettext' toolset helps programmers and translators at
+producing, updating and using translation files, mainly those PO files
+which are textual, editable files. This chapter explains the format of
+PO files.
-A PO file is made up of many entries, each entry holding the relation
+ A PO file is made up of many entries, each entry holding the relation
between an original untranslated string and its corresponding
translation. All entries in a given PO file usually pertain to a
single project, and all translations are expressed in a single target
WHITE-SPACE
# TRANSLATOR-COMMENTS
- #. AUTOMATIC-COMMENTS
+ #. EXTRACTED-COMMENTS
#: REFERENCE...
#, FLAG...
msgid UNTRANSLATED-STRING
generated through GNU `gettext' tools, there is exactly one blank line
between entries. Then comments follow, on lines all starting with the
character `#'. There are two kinds of comments: those which have some
-white space immediately following the `#', which comments are created
-and maintained exclusively by the translator, and those which have some
-non-white character just after the `#', which comments are created and
-maintained automatically by GNU `gettext' tools. All comments, of
-either kind, are optional.
+white space immediately following the `#' - the TRANSLATOR COMMENTS -,
+which comments are created and maintained exclusively by the
+translator, and those which have some non-white character just after the
+`#' - the AUTOMATIC COMMENTS -, which comments are created and
+maintained automatically by GNU `gettext' tools. Comment lines
+starting with `#.' contain comments given by the programmer, directed
+at the translator; these comments are called EXTRACTED COMMENTS because
+the `xgettext' program extracts them from the program's source code.
+Comment lines starting with `#:' contain references to the program's
+source code. Comment lines starting with `#,' contain flags; more
+about these below. All comments, of either kind, are optional.
After white space and comments, entries show two strings, namely
first the untranslated string as it appears in the original program
`no-qt-format'
Likewise for Qt, see *Note qt-format::.
+`boost-format'
+`no-boost-format'
+ Likewise for Boost, see *Note boost-format::.
+
+
+ It is also possible to have entries with a context specifier. They
+look like this:
+
+ WHITE-SPACE
+ # TRANSLATOR-COMMENTS
+ #. EXTRACTED-COMMENTS
+ #: REFERENCE...
+ #, FLAG...
+ msgctxt CONTEXT
+ msgid UNTRANSLATED-STRING
+ msgstr TRANSLATED-STRING
+
+ The context serves to disambiguate messages with the same
+UNTRANSLATED-STRING. It is possible to have several entries with the
+same UNTRANSLATED-STRING in a PO file, provided that they each have a
+different CONTEXT. Note that an empty CONTEXT string and an absent
+`msgctxt' line do not mean the same thing.
A different kind of entries is used for translations which involve
plural forms.
WHITE-SPACE
# TRANSLATOR-COMMENTS
- #. AUTOMATIC-COMMENTS
+ #. EXTRACTED-COMMENTS
#: REFERENCE...
#, FLAG...
msgid UNTRANSLATED-STRING-SINGULAR
msgstr[0] "s'ha trobat %d error fatal"
msgstr[1] "s'han trobat %d errors fatals"
+ Here also, a `msgctxt' context can be specified before `msgid', like
+above.
+
It happens that some lines, usually whitespace or comments, follow
the very last entry of a PO file. Such lines are not part of any entry,
-and PO mode is unable to take action on those lines. By using the PO
-mode function `M-x po-normalize', the translator may get rid of those
-spurious lines. *Note Normalizing::.
+and will be dropped when the PO file is processed by the tools, or may
+disturb some PO file editors.
- The remainder of this section may be safely skipped by those using
-PO mode, yet it may be interesting for everybody to have a better idea
-of the precise format of a PO file. On the other hand, those not
-having Emacs handy should carefully continue reading on.
+ The remainder of this section may be safely skipped by those using a
+PO file editor, yet it may be interesting for everybody to have a better
+idea of the precise format of a PO file. On the other hand, those
+wishing to modify PO files by hand should carefully continue reading on.
Each of UNTRANSLATED-STRING and TRANSLATED-STRING respects the C
syntax for a character string, including the surrounding quotes and
compatibility with the `msgfmt' implementation on Solaris.
\1f
-File: gettext.info, Node: Main PO Commands, Next: Entry Positioning, Prev: PO Files, Up: Basics
+File: gettext.info, Node: Sources, Next: Template, Prev: PO Files, Up: Top
-2.3 Main PO mode Commands
-=========================
+4 Preparing Program Sources
+***************************
-After setting up Emacs with something similar to the lines in *Note
-Installation::, PO mode is activated for a window when Emacs finds a PO
-file in that window. This puts the window read-only and establishes a
-po-mode-map, which is a genuine Emacs mode, in a way that is not derived
-from text mode in any way. Functions found on `po-mode-hook', if any,
-will be executed.
+For the programmer, changes to the C source code fall into three
+categories. First, you have to make the localization functions known
+to all modules needing message translation. Second, you should
+properly trigger the operation of GNU `gettext' when the program
+initializes, usually from the `main' function. Last, you should
+identify, adjust and mark all constant strings in your program needing
+translation.
- 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 (*note Translated Entries::, 3 fuzzy entries
-(*note Fuzzy Entries::), 10 untranslated entries (*note Untranslated
-Entries::) and 2 obsolete entries (*note 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.
+* Menu:
- The main PO commands are those which do not fit into the other
-categories of subsequent sections. These allow for quitting PO mode or
-for managing windows in special ways.
+* Importing:: Importing the `gettext' declaration
+* Triggering:: Triggering `gettext' Operations
+* Preparing Strings:: Preparing Translatable Strings
+* Mark Keywords:: How Marks Appear in Sources
+* Marking:: Marking Translatable Strings
+* c-format Flag:: Telling something about the following string
+* Special cases:: Special Cases of Translatable Strings
+* Names:: Marking Proper Names for Translation
+* Libraries:: Preparing Library Sources
-`_'
- Undo last modification to the PO file (`po-undo').
+\1f
+File: gettext.info, Node: Importing, Next: Triggering, Prev: Sources, Up: Sources
-`Q'
- Quit processing and save the PO file (`po-quit').
+4.1 Importing the `gettext' declaration
+=======================================
-`q'
- Quit processing, possibly after confirmation
- (`po-confirm-and-quit').
+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 (*note Maintainers::), each C module having translated C
+strings should contain the line:
-`0'
- Temporary leave the PO file window (`po-other-window').
+ #include <libintl.h>
-`?'
-`h'
- Show help about PO mode (`po-help').
+ Similarly, each C module containing `printf()'/`fprintf()'/...
+calls with a format string that could be a translated C string (even if
+the C string comes from a different C module) should contain the line:
-`='
- Give some PO file statistics (`po-statistics').
+ #include <libintl.h>
-`V'
- Batch validate the format of the whole PO file (`po-validate').
+\1f
+File: gettext.info, Node: Triggering, Next: Preparing Strings, Prev: Importing, Up: Sources
+4.2 Triggering `gettext' Operations
+===================================
- The command `_' (`po-undo') interfaces to the Emacs _undo_ facility.
-*Note Undoing Changes: (emacs)Undo. Each time `U' is typed,
-modifications which the translator did to the PO file are undone a
-little more. For the purpose of undoing, each PO mode command is
-atomic. This is especially true for the `<RET>' command: the whole
-edition made by using a single use of this command is undone at once,
-even if the edition itself implied several actions. However, while in
-the editing window, one can undo the edition work quite parsimoniously.
+The initialization of locale data should be done with more or less the
+same code in every program, as demonstrated below:
- The commands `Q' (`po-quit') and `q' (`po-confirm-and-quit') are
-used when the translator is done with the PO file. The former is a bit
-less verbose than the latter. If the file has been modified, it is
-saved to disk first. In both cases, and prior to all this, the
-commands check if any untranslated messages remain in the PO file and,
-if so, the translator is asked if she really wants to leave off working
-with this PO file. This is the preferred way of getting rid of an
-Emacs PO file buffer. Merely killing it through the usual command
-`C-x k' (`kill-buffer') is not the tidiest way to proceed.
+ int
+ main (int argc, char *argv[])
+ {
+ ...
+ setlocale (LC_ALL, "");
+ bindtextdomain (PACKAGE, LOCALEDIR);
+ textdomain (PACKAGE);
+ ...
+ }
- The command `0' (`po-other-window') is another, softer way, to leave
-PO mode, temporarily. It just moves the cursor to some other Emacs
-window, and pops one if necessary. For example, if the translator just
-got PO mode to show some source context in some other, she might
-discover some apparent bug in the program source that needs correction.
-This command allows the translator to change sex, become a programmer,
-and have the cursor right into the window containing the program she
-(or rather _he_) wants to modify. By later getting the cursor back in
-the PO file window, or by asking Emacs to edit this file once again, PO
-mode is then recovered.
+ PACKAGE and LOCALEDIR should be provided either by `config.h' or by
+the Makefile. For now consult the `gettext' or `hello' sources for
+more information.
- The command `h' (`po-help') displays a summary of all available PO
-mode commands. The translator should then type any character to resume
-normal PO mode operations. The command `?' has the same effect as `h'.
-
- The command `=' (`po-statistics') computes the total number of
-entries in the PO file, the ordinal of the current entry (counted from
-1), the number of untranslated entries, the number of obsolete entries,
-and displays all these numbers.
-
- The command `V' (`po-validate') launches `msgfmt' in checking and
-verbose mode over the current PO file. This command first offers to
-save the current PO file on disk. The `msgfmt' tool, from GNU
-`gettext', has the purpose of creating a MO file out of a PO file, and
-PO mode uses the features of this program for checking the overall
-format of a PO file, as well as all individual entries.
-
- The program `msgfmt' runs asynchronously with Emacs, so the
-translator regains control immediately while her PO file is being
-studied. Error output is collected in the Emacs `*compilation*' buffer,
-displayed in another window. The regular Emacs command `C-x`'
-(`next-error'), as well as other usual compile commands, allow the
-translator to reposition quickly to the offending parts of the PO file.
-Once the cursor is on the line in error, the translator may decide on
-any PO mode action which would help correcting the error.
-
-\1f
-File: gettext.info, Node: Entry Positioning, Next: Normalizing, Prev: Main PO Commands, Up: Basics
-
-2.4 Entry Positioning
-=====================
-
-The cursor in a PO file window is almost always part of an entry. The
-only exceptions are the special case when the cursor is after the last
-entry in the file, or when the PO file is empty. The entry where the
-cursor is found to be is said to be the current entry. Many PO mode
-commands operate on the current entry, so moving the cursor does more
-than allowing the translator to browse the PO file, this also selects
-on which entry commands operate.
-
- Some PO mode commands alter the position of the cursor in a
-specialized way. A few of those special purpose positioning are
-described here, the others are described in following sections (for a
-complete list try `C-h m'):
-
-`.'
- Redisplay the current entry (`po-current-entry').
-
-`n'
- Select the entry after the current one (`po-next-entry').
-
-`p'
- Select the entry before the current one (`po-previous-entry').
-
-`<'
- Select the first entry in the PO file (`po-first-entry').
-
-`>'
- Select the last entry in the PO file (`po-last-entry').
-
-`m'
- Record the location of the current entry for later use
- (`po-push-location').
-
-`r'
- Return to a previously saved entry location (`po-pop-location').
-
-`x'
- Exchange the current entry location with the previously saved one
- (`po-exchange-location').
-
-
- Any Emacs command able to reposition the cursor may be used to
-select the current entry in PO mode, including commands which move by
-characters, lines, paragraphs, screens or pages, and search commands.
-However, there is a kind of standard way to display the current entry
-in PO mode, which usual Emacs commands moving the cursor do not
-especially try to enforce. The command `.' (`po-current-entry') has
-the sole purpose of redisplaying the current entry properly, after the
-current entry has been changed by means external to PO mode, or the
-Emacs screen otherwise altered.
-
- It is yet to be decided if PO mode helps the translator, or otherwise
-irritates her, by forcing a rigid window disposition while she is doing
-her work. We originally had quite precise ideas about how windows
-should behave, but on the other hand, anyone used to Emacs is often
-happy to keep full control. Maybe a fixed window disposition might be
-offered as a PO mode option that the translator might activate or
-deactivate at will, so it could be offered on an experimental basis.
-If nobody feels a real need for using it, or a compulsion for writing
-it, we should drop this whole idea. The incentive for doing it should
-come from translators rather than programmers, as opinions from an
-experienced translator are surely more worth to me than opinions from
-programmers _thinking_ about how _others_ should do translation.
-
- The commands `n' (`po-next-entry') and `p' (`po-previous-entry')
-move the cursor the entry following, or preceding, the current one. If
-`n' is given while the cursor is on the last entry of the PO file, or
-if `p' is given while the cursor is on the first entry, no move is done.
-
- The commands `<' (`po-first-entry') and `>' (`po-last-entry') move
-the cursor to the first entry, or last entry, of the PO file. When the
-cursor is located past the last entry in a PO file, most PO mode
-commands will return an error saying `After last entry'. Moreover, the
-commands `<' and `>' 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.
-*Note Marking::.
-
- The translator may decide, before working at the translation of a
-particular entry, that she needs to browse the remainder of the PO
-file, maybe for finding the terminology or phraseology used in related
-entries. She can of course use the standard Emacs idioms for saving
-the current cursor location in some register, and use that register for
-getting back, or else, use the location ring.
-
- PO mode offers another approach, by which cursor locations may be
-saved onto a special stack. The command `m' (`po-push-location')
-merely adds the location of current entry to the stack, pushing the
-already saved locations under the new one. The command `r'
-(`po-pop-location') consumes the top stack element and repositions the
-cursor to the entry associated with that top element. This position is
-then lost, for the next `r' will move the cursor to the previously
-saved location, and so on until no locations remain on the stack.
-
- If the translator wants the position to be kept on the location
-stack, maybe for taking a look at the entry associated with the top
-element, then go elsewhere with the intent of getting back later, she
-ought to use `m' immediately after `r'.
-
- The command `x' (`po-exchange-location') simultaneously repositions
-the cursor to the entry associated with the top element of the stack of
-saved locations, and replaces that top element with the location of the
-current entry before the move. Consequently, repeating the `x' command
-toggles alternatively between two entries. For achieving this, the
-translator will position the cursor on the first entry, use `m', then
-position to the second entry, and merely use `x' for making the switch.
-
-\1f
-File: gettext.info, Node: Normalizing, Prev: Entry Positioning, Up: Basics
-
-2.5 Normalizing Strings in Entries
-==================================
-
-There are many different ways for encoding a particular string into a
-PO file entry, because there are so many different ways to split and
-quote multi-line strings, and even, to represent special characters by
-backslashed escaped sequences. Some features of PO mode rely on the
-ability for PO mode to scan an already existing PO file for a
-particular string encoded into the `msgid' field of some entry. Even
-if PO mode has internally all the built-in machinery for implementing
-this recognition easily, doing it fast is technically difficult. To
-facilitate a solution to this efficiency problem, we decided on a
-canonical representation for strings.
-
- A conventional representation of strings in a PO file is currently
-under discussion, and PO mode experiments with a canonical
-representation. Having both `xgettext' and PO mode converging towards
-a uniform way of representing equivalent strings would be useful, as
-the internal normalization needed by PO mode could be automatically
-satisfied when using `xgettext' from GNU `gettext'. An explicit PO
-mode normalization should then be only necessary for PO files imported
-from elsewhere, or for when the convention itself evolves.
-
- So, for achieving normalization of at least the strings of a given
-PO file needing a canonical representation, the following PO mode
-command is available:
-
-`M-x po-normalize'
- Tidy the whole PO file by making entries more uniform.
-
-
- The special command `M-x po-normalize', which has no associated
-keys, revises all entries, ensuring that strings of both original and
-translated entries use uniform internal quoting in the PO file. It
-also removes any crumb after the last entry. This command may be
-useful for PO files freshly imported from elsewhere, or if we ever
-improve on the canonical quoting format we use. This canonical format
-is not only meant for getting cleaner PO files, but also for greatly
-speeding up `msgid' string lookup for some other PO mode commands.
-
- `M-x po-normalize' presently makes three passes over the entries.
-The first implements heuristics for converting PO files for GNU
-`gettext' 0.6 and earlier, in which `msgid' and `msgstr' fields were
-using K&R style C string syntax for multi-line strings. These
-heuristics may fail for comments not related to obsolete entries and
-ending with a backslash; they also depend on subsequent passes for
-finalizing the proper commenting of continued lines for obsolete
-entries. This first pass might disappear once all oldish PO files
-would have been adjusted. The second and third pass normalize all
-`msgid' and `msgstr' strings respectively. They also clean out those
-trailing backslashes used by XView's `msgfmt' for continued lines.
-
- Having such an explicit normalizing command allows for importing PO
-files from other sources, but also eases the evolution of the current
-convention, evolution driven mostly by aesthetic concerns, as of now.
-It is easy to make suggested adjustments at a later time, as the
-normalizing command and eventually, other GNU `gettext' tools should
-greatly automate conformance. A description of the canonical string
-format is given below, for the particular benefit of those not having
-Emacs handy, and who would nevertheless want to handcraft their PO
-files in nice ways.
-
- Right now, in PO mode, strings are single line or multi-line. A
-string goes multi-line if and only if it has _embedded_ newlines, that
-is, if it matches `[^\n]\n+[^\n]'. So, we would have:
-
- msgstr "\n\nHello, world!\n\n\n"
-
- but, replacing the space by a newline, this becomes:
-
- msgstr ""
- "\n"
- "\n"
- "Hello,\n"
- "world!\n"
- "\n"
- "\n"
-
- We are deliberately using a caricatural example, here, to make the
-point clearer. Usually, multi-lines are not that bad looking. It is
-probable that we will implement the following suggestion. We might
-lump together all initial newlines into the empty string, and also all
-newlines introducing empty lines (that is, for N > 1, the N-1'th last
-newlines would go together on a separate string), so making the
-previous example appear:
-
- msgstr "\n\n"
- "Hello,\n"
- "world!\n"
- "\n\n"
-
- There are a few yet undecided little points about string
-normalization, to be documented in this manual, once these questions
-settle.
-
-\1f
-File: gettext.info, Node: Sources, Next: Template, Prev: Basics, Up: Top
-
-3 Preparing Program Sources
-***************************
-
-For the programmer, changes to the C source code fall into three
-categories. First, you have to make the localization functions known
-to all modules needing message translation. Second, you should
-properly trigger the operation of GNU `gettext' when the program
-initializes, usually from the `main' function. Last, you should
-identify and especially mark all constant strings in your program
-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 (*note Maintainers::), each C module having
-translated C strings should contain the line:
-
- #include <libintl.h>
-
- Similarly, each C module containing `printf()'/`fprintf()'/...
-calls with a format string that could be a translated C string (even if
-the C string comes from a different C module) should contain the line:
-
- #include <libintl.h>
-
- The remaining changes to your C sources are discussed in the further
-sections of this chapter.
-
-* Menu:
-
-* Triggering:: Triggering `gettext' Operations
-* Preparing Strings:: Preparing Translatable Strings
-* Mark Keywords:: How Marks Appear in Sources
-* Marking:: Marking Translatable Strings
-* c-format Flag:: Telling something about the following string
-* Special cases:: Special Cases of Translatable Strings
-* Names:: Marking Proper Names for Translation
-* Libraries:: Preparing Library Sources
-
-\1f
-File: gettext.info, Node: Triggering, Next: Preparing Strings, Prev: Sources, Up: Sources
-
-3.1 Triggering `gettext' Operations
-===================================
-
-The initialization of locale data should be done with more or less the
-same code in every program, as demonstrated below:
-
- int
- main (int argc, char *argv[])
- {
- ...
- setlocale (LC_ALL, "");
- bindtextdomain (PACKAGE, LOCALEDIR);
- textdomain (PACKAGE);
- ...
- }
-
- PACKAGE and LOCALEDIR should be provided either by `config.h' or by
-the Makefile. For now consult the `gettext' or `hello' sources for
-more information.
-
- The use of `LC_ALL' might not be appropriate for you. `LC_ALL'
-includes all locale categories and especially `LC_CTYPE'. This later
-category is responsible for determining character classes with the
-`isalnum' etc. functions from `ctype.h' which could especially for
-programs, which process some kind of input language, be wrong. For
-example this would mean that a source code using the c, (c-cedilla
-character) is runnable in France but not in the U.S.
+ The use of `LC_ALL' might not be appropriate for you. `LC_ALL'
+includes all locale categories and especially `LC_CTYPE'. This later
+category is responsible for determining character classes with the
+`isalnum' etc. functions from `ctype.h' which could especially for
+programs, which process some kind of input language, be wrong. For
+example this would mean that a source code using the c, (c-cedilla
+character) is runnable in France but not in the U.S.
Some systems also have problems with parsing numbers using the
`scanf' functions if an other but the `LC_ALL' locale is used. The
\1f
File: gettext.info, Node: Preparing Strings, Next: Mark Keywords, Prev: Triggering, Up: Sources
-3.2 Preparing Translatable Strings
+4.3 Preparing Translatable Strings
==================================
Before strings can be marked for translations, they sometimes need to
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".
+also be able to find the appropriate grammatical construction. A French
+translator for example translates "write protected" like "protected
+against writing".
Entire sentences are also important because in many languages, the
declination of some word in a sentence depends on the gender or the
\1f
File: gettext.info, Node: Mark Keywords, Next: Marking, Prev: Preparing Strings, Up: Sources
-3.3 How Marks Appear in Sources
+4.4 How Marks Appear in Sources
===============================
All strings requiring translation should be marked in the C sources.
\1f
File: gettext.info, Node: Marking, Next: c-format Flag, Prev: Mark Keywords, Up: Sources
-3.4 Marking Translatable Strings
+4.5 Marking Translatable Strings
================================
In PO mode, one set of features is meant more for the programmer than
\1f
File: gettext.info, Node: c-format Flag, Next: Special cases, Prev: Marking, Up: Sources
-3.5 Special Comments preceding Keywords
+4.6 Special Comments preceding Keywords
=======================================
In C programs strings are often used within calls of functions from the
\1f
File: gettext.info, Node: Special cases, Next: Names, Prev: c-format Flag, Up: Sources
-3.6 Special Cases of Translatable Strings
+4.7 Special Cases of Translatable Strings
=========================================
The attentive reader might now point out that it is not always possible
\1f
File: gettext.info, Node: Names, Next: Libraries, Prev: Special cases, Up: Sources
-3.7 Marking Proper Names for Translation
+4.8 Marking Proper Names for Translation
========================================
Should names of persons, cities, locations etc. be marked for
\1f
File: gettext.info, Node: Libraries, Prev: Names, Up: Sources
-3.8 Preparing Library Sources
+4.9 Preparing Library Sources
=============================
When you are preparing a library, not a program, for the use of
\1f
File: gettext.info, Node: Template, Next: Creating, Prev: Sources, Up: Top
-4 Making the PO Template File
+5 Making the PO Template File
*****************************
After preparing the sources, the programmer creates a PO template file.
\1f
File: gettext.info, Node: xgettext Invocation, Prev: Template, Up: Template
-4.1 Invoking the `xgettext' Program
+5.1 Invoking the `xgettext' Program
===================================
xgettext [OPTION] [INPUTFILE] ...
The `xgettext' program extracts translatable strings from given
input files.
-4.1.1 Input file location
+5.1.1 Input file location
-------------------------
`INPUTFILE ...'
If INPUTFILE is `-', standard input is read.
-4.1.2 Output file location
+5.1.2 Output file location
--------------------------
`-d NAME'
If the output FILE is `-' or `/dev/stdout', the output is written to
standard output.
-4.1.3 Choice of input file language
+5.1.3 Choice of input file language
-----------------------------------
`-L NAME'
By default the language is guessed depending on the input file name
extension.
-4.1.4 Input file interpretation
+5.1.4 Input file interpretation
-------------------------------
`--from-code=NAME'
Specifies the encoding of the input files. This option is needed
only if some untranslated message strings or their corresponding
- comments contain non-ASCII characters. Note that Python, Tcl, and
- Glade input files are always assumed to be in UTF-8, regardless of
- this option.
+ comments contain non-ASCII characters. Note that Tcl and Glade
+ input files are always assumed to be in UTF-8, regardless of this
+ option.
By default the input files are assumed to be in ASCII.
-4.1.5 Operation mode
+5.1.5 Operation mode
--------------------
`-j'
output file.
-4.1.6 Language specific options
+5.1.6 Language specific options
-------------------------------
`-a'
of the form `ID:ARGNUM1,ARGNUM2', `xgettext' looks for strings in
the ARGNUM1st argument and in the ARGNUM2nd argument of the call,
and treats them as singular/plural variants for a message with
- plural handling.
- The default keyword specifications, which are always looked for if
- not explicitly disabled, are `gettext', `dgettext:2',
- `dcgettext:2', `ngettext:1,2', `dngettext:2,3', `dcngettext:2,3',
- and `gettext_noop'.
+ plural handling. Also, if KEYWORDSPEC is of the form
+ `ID:CONTEXTARGNUMc,ARGNUM' or `ID:ARGNUM,CONTEXTARGNUMc',
+ `xgettext' treats strings in the CONTEXTARGNUMth argument as a
+ context specifier. And, as a special-purpose support for GNOME,
+ if KEYWORDSPEC is of the form `ID:ARGNUMg', `xgettext' recognizes
+ the ARGNUMth argument as a string with context, using the GNOME
+ `glib' syntax `"msgctxt|msgid"'.
+ Furthermore, if KEYWORDSPEC is of the form `ID:...,TOTALNUMARGSt',
+ `xgettext' recognizes this argument specification only if the
+ number of actual arguments is equal to TOTALNUMARGS. This is
+ useful for disambiguating overloaded function calls in C++.
+ Finally, if KEYWORDSPEC is of the form `ID:ARGNUM...,"XCOMMENT"',
+ `xgettext', when extracting a message from the specified argument
+ strings, adds an extracted comment XCOMMENT to the message. Note
+ that when used through a normal shell command line, the
+ double-quotes around the XCOMMENT need to be escaped.
+
This option has an effect with most languages, namely C, C++,
ObjectiveC, Shell, Python, Lisp, EmacsLisp, librep, Java, C#, awk,
Tcl, Perl, PHP, GCC-source, Glade.
+ The default keyword specifications, which are always looked for if
+ not explicitly disabled, are language dependent. They are:
+
+ * For C, C++, and GCC-source: `gettext', `dgettext:2',
+ `dcgettext:2', `ngettext:1,2', `dngettext:2,3',
+ `dcngettext:2,3', `gettext_noop', and `pgettext:1c,2',
+ `dpgettext:2c,3', `dcpgettext:2c,3', `npgettext:1c,2,3',
+ `dnpgettext:2c,3,4', `dcnpgettext:2c,3,4'.
+
+ * For Objective C: Like for C, and also `NSLocalizedString',
+ `_', `NSLocalizedStaticString', `__'.
+
+ * For Shell scripts: `gettext', `ngettext:1,2', `eval_gettext',
+ `eval_ngettext:1,2'.
+
+ * For Python: `gettext', `ugettext', `dgettext:2',
+ `ngettext:1,2', `ungettext:1,2', `dngettext:2,3', `_'.
+
+ * For Lisp: `gettext', `ngettext:1,2', `gettext-noop'.
+
+ * For EmacsLisp: `_'.
+
+ * For librep: `_'.
+
+ * For Scheme: `gettext', `ngettext:1,2', `gettext-noop'.
+
+ * For Java: `GettextResource.gettext:2',
+ `GettextResource.ngettext:2,3', `gettext', `ngettext:1,2',
+ `getString'.
+
+ * For C#: `GetString', `GetPluralString:1,2'.
+
+ * For awk: `dcgettext', `dcngettext:1,2'.
+
+ * For Tcl: `::msgcat::mc'.
+
+ * For Perl: `gettext', `%gettext', `$gettext', `dgettext:2',
+ `dcgettext:2', `ngettext:1,2', `dngettext:2,3',
+ `dcngettext:2,3', `gettext_noop'.
+
+ * For PHP: `_', `gettext', `dgettext:2', `dcgettext:2',
+ `ngettext:1,2', `dngettext:2,3', `dcngettext:2,3'.
+
+ * For Glade 1: `label', `title', `text', `format', `copyright',
+ `comments', `preview_text', `tooltip'.
+
+ To disable the default keyword specifications, the option `-k' or
+ `--keyword' or `--keyword=', without a KEYWORDSPEC, can be used.
+
`--flag=WORD:ARG:FLAG'
Specifies additional flags for strings occurring as part of the
ARGth argument of the function WORD. The possible flags are the
Recognize Qt format strings.
This option has an effect only with the language C++.
+`--boost'
+ Recognize Boost format strings.
+ This option has an effect only with the language C++.
+
`--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
cases, like strings in preprocessor macros, ANSI concatenation of
adjacent strings, and escaped end of lines for continued strings.
-4.1.7 Output details
+5.1.7 Output details
--------------------
`--force-po'
Use STRING (or "" if not specified) as suffix for msgstr entries.
-4.1.8 Informative output
+5.1.8 Informative output
------------------------
`-h'
\1f
File: gettext.info, Node: Creating, Next: Updating, Prev: Template, Up: Top
-5 Creating a New PO File
+6 Creating a New PO File
************************
When starting a new translation, the translator creates a file called
\1f
File: gettext.info, Node: msginit Invocation, Next: Header Entry, Prev: Creating, Up: Creating
-5.1 Invoking the `msginit' Program
+6.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
+6.1.1 Input file location
-------------------------
`-i INPUTFILE'
If no INPUTFILE is given, the current directory is searched for the
POT file. If it is `-', standard input is read.
-5.1.2 Output file location
+6.1.2 Output file location
--------------------------
`-o FILE'
the user's locale setting. If it is `-', the results are written to
standard output.
-5.1.3 Input file syntax
+6.1.3 Input file syntax
-----------------------
`-P'
file in `.strings' syntax, not in PO file syntax.
-5.1.4 Output details
+6.1.4 Output details
--------------------
`-l LL_CC'
page width will be split.
-5.1.5 Informative output
+6.1.5 Informative output
------------------------
`-h'
\1f
File: gettext.info, Node: Header Entry, Prev: msginit Invocation, Up: Creating
-5.2 Filling in the Header Entry
+6.2 Filling in the Header Entry
===============================
The initial comments "SOME DESCRIPTIVE TITLE", "YEAR" and "FIRST AUTHOR
This has already been filled in by `xgettext'.
PO-Revision-Date
- You don't need to fill this in. It will be filled by the Emacs PO
- mode when you save the file.
+ You don't need to fill this in. It will be filled by the PO file
+ editor when you save the file.
Last-Translator
Fill in your name and email address (without double quotes).
as for users whose locale's character encoding differs from yours
(see *Note Charset conversion::).
- 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 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.
+ 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 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 `libiconv'. These are: `ASCII', `ISO-8859-1',
+ `ISO-8859-2', `ISO-8859-3', `ISO-8859-4', `ISO-8859-5',
+ `ISO-8859-6', `ISO-8859-7', `ISO-8859-8', `ISO-8859-9',
+ `ISO-8859-13', `ISO-8859-14', `ISO-8859-15', `KOI8-R', `KOI8-U',
+ `KOI8-T', `CP850', `CP866', `CP874', `CP932', `CP949', `CP950',
+ `CP1250', `CP1251', `CP1252', `CP1253', `CP1254', `CP1255',
+ `CP1256', `CP1257', `GB2312', `EUC-JP', `EUC-KR', `EUC-TW',
+ `BIG5', `BIG5-HKSCS', `GBK', `GB18030', `SHIFT_JIS', `JOHAB',
+ `TIS-620', `VISCII', `GEORGIAN-PS', `UTF-8'.
+
+ In the GNU system, the following encodings are frequently used for
+ the corresponding languages.
+
+ * `ISO-8859-1' for Afrikaans, Albanian, Basque, Breton,
+ Catalan, Cornish, Danish, Dutch, English, Estonian, Faroese,
+ Finnish, French, Galician, German, Greenlandic, Icelandic,
+ Indonesian, Irish, Italian, Malay, Manx, Norwegian, Occitan,
+ Portuguese, Spanish, Swedish, Tagalog, Uzbek, Walloon,
+
+ * `ISO-8859-2' for Bosnian, Croatian, Czech, Hungarian, Polish,
+ Romanian, Serbian, Slovak, Slovenian,
+
+ * `ISO-8859-3' for Maltese,
+
+ * `ISO-8859-5' for Macedonian, Serbian,
+
+ * `ISO-8859-6' for Arabic,
+
+ * `ISO-8859-7' for Greek,
+
+ * `ISO-8859-8' for Hebrew,
+
+ * `ISO-8859-9' for Turkish,
+
+ * `ISO-8859-13' for Latvian, Lithuanian, Maori,
+
+ * `ISO-8859-14' for Welsh,
+
+ * `ISO-8859-15' for Basque, Catalan, Dutch, English, Finnish,
+ French, Galician, German, Irish, Italian, Portuguese,
+ Spanish, Swedish, Walloon,
+
+ * `KOI8-R' for Russian,
+
+ * `KOI8-U' for Ukrainian,
+
+ * `KOI8-T' for Tajik,
+
+ * `CP1251' for Bulgarian, Byelorussian,
+
+ * `GB2312', `GBK', `GB18030' for simplified writing of Chinese,
+
+ * `BIG5', `BIG5-HKSCS' for traditional writing of Chinese,
+
+ * `EUC-JP' for Japanese,
+
+ * `EUC-KR' for Korean,
+
+ * `TIS-620' for Thai,
+
+ * `GEORGIAN-PS' for Georgian,
+
+ * `UTF-8' for any language, including those listed above.
+
+ 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 encoding, instead of your locale's encoding. This is
+ because in UTF-8 the real quote characters can be represented
+ (single quote characters: U+2018, U+2019, double quote characters:
+ U+201C, U+201D), whereas none of ISO-8859-* charsets has them all.
+ Users in UTF-8 locales will see the 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", "leftdoublequotemark",
+ "rightdoublequotemark", "singlelowquotemark", "doublelowquotemark".
+
+ Note that only recent versions of GNU Emacs support the UTF-8
+ encoding: Emacs 20 with Mule-UCS, and Emacs 21. As of January
+ 2001, XEmacs doesn't support the UTF-8 encoding.
+
+ The character encoding name can be written in either upper or
+ lower case. Usually upper case is preferred.
+
+Content-Transfer-Encoding
+ Set this to `8bit'.
+
+Plural-Forms
+ 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 *Note Plural forms::.
+
+\1f
+File: gettext.info, Node: Updating, Next: Editing, Prev: Creating, Up: Top
+
+7 Updating Existing PO Files
+****************************
+
+* Menu:
+
+* msgmerge Invocation:: Invoking the `msgmerge' Program
+
+\1f
+File: gettext.info, Node: msgmerge Invocation, Prev: Updating, Up: Updating
+
+7.1 Invoking the `msgmerge' Program
+===================================
+
+ msgmerge [OPTION] DEF.po REF.pot
+
+ The `msgmerge' program merges two Uniforum style .po files together.
+The DEF.po file is an existing PO file with translations which will be
+taken over to the newly created file as long as they still match;
+comments will be preserved, but extracted comments and file positions
+will be discarded. The REF.pot file is the last created PO file with
+up-to-date source references but old translations, or a PO Template file
+(generally created by `xgettext'); any translations or comments in the
+file will be discarded, however dot comments and file positions will be
+preserved. Where an exact match cannot be found, fuzzy matching is
+used to produce better results.
+
+7.1.1 Input file location
+-------------------------
+
+`DEF.po'
+ Translations referring to old sources.
+
+`REF.pot'
+ References to the new sources.
+
+`-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.
+
+`-C FILE'
+`--compendium=FILE'
+ Specify an additional library of message translations. *Note
+ Compendium::. This option may be specified more than once.
+
+
+7.1.2 Operation mode
+--------------------
+
+`-U'
+`--update'
+ Update DEF.po. Do nothing if DEF.po is already up to date.
+
+
+7.1.3 Output file location
+--------------------------
+
+`-o FILE'
+`--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.4 Output file location in update mode
+-----------------------------------------
+
+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:
+
+`none'
+`off'
+ Never make backups (even if `--backup' is given).
+
+`numbered'
+`t'
+ Make numbered backups.
+
+`existing'
+`nil'
+ Make numbered backups if numbered backups for this file already
+ exist, otherwise make simple backups.
+
+`simple'
+`never'
+ Always make simple backups.
+
+
+ The backup suffix is `~', unless set with `--suffix' or the
+`SIMPLE_BACKUP_SUFFIX' environment variable.
+
+7.1.5 Operation modifiers
+-------------------------
+
+`-m'
+`--multi-domain'
+ Apply REF.pot to each of the domains in DEF.po.
+
+`-N'
+`--no-fuzzy-matching'
+ Do not use fuzzy matching when an exact match is not found. This
+ may speed up the operation considerably.
- 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 `libiconv'. These are: `ASCII', `ISO-8859-1',
- `ISO-8859-2', `ISO-8859-3', `ISO-8859-4', `ISO-8859-5',
- `ISO-8859-6', `ISO-8859-7', `ISO-8859-8', `ISO-8859-9',
- `ISO-8859-13', `ISO-8859-14', `ISO-8859-15', `KOI8-R', `KOI8-U',
- `KOI8-T', `CP850', `CP866', `CP874', `CP932', `CP949', `CP950',
- `CP1250', `CP1251', `CP1252', `CP1253', `CP1254', `CP1255',
- `CP1256', `CP1257', `GB2312', `EUC-JP', `EUC-KR', `EUC-TW',
- `BIG5', `BIG5-HKSCS', `GBK', `GB18030', `SHIFT_JIS', `JOHAB',
- `TIS-620', `VISCII', `GEORGIAN-PS', `UTF-8'.
+7.1.6 Input file syntax
+-----------------------
- In the GNU system, the following encodings are frequently used for
- the corresponding languages.
+`-P'
+`--properties-input'
+ Assume the input files are Java ResourceBundles in Java
+ `.properties' syntax, not in PO file syntax.
- * `ISO-8859-1' for Afrikaans, Albanian, Basque, Breton,
- Catalan, Cornish, Danish, Dutch, English, Estonian, Faroese,
- Finnish, French, Galician, German, Greenlandic, Icelandic,
- Indonesian, Irish, Italian, Malay, Manx, Norwegian, Occitan,
- Portuguese, Spanish, Swedish, Tagalog, Uzbek, Walloon,
+`--stringtable-input'
+ Assume the input files are NeXTstep/GNUstep localized resource
+ files in `.strings' syntax, not in PO file syntax.
- * `ISO-8859-2' for Bosnian, Croatian, Czech, Hungarian, Polish,
- Romanian, Serbian, Slovak, Slovenian,
- * `ISO-8859-3' for Maltese,
+7.1.7 Output details
+--------------------
- * `ISO-8859-5' for Macedonian, Serbian,
+`--force-po'
+ Always write an output file even if it contains no message.
- * `ISO-8859-6' for Arabic,
+`-i'
+`--indent'
+ Write the .po file using indented style.
- * `ISO-8859-7' for Greek,
+`--no-location'
+ Do not write `#: FILENAME:LINE' lines.
- * `ISO-8859-8' for Hebrew,
+`--add-location'
+ Generate `#: FILENAME:LINE' lines (default).
- * `ISO-8859-9' for Turkish,
+`--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.
- * `ISO-8859-13' for Latvian, Lithuanian, Maori,
+`-p'
+`--properties-output'
+ Write out a Java ResourceBundle in Java `.properties' syntax. Note
+ that this file format doesn't support plural forms and silently
+ drops obsolete messages.
- * `ISO-8859-14' for Welsh,
+`--stringtable-output'
+ Write out a NeXTstep/GNUstep localized resource file in `.strings'
+ syntax. Note that this file format doesn't support plural forms.
- * `ISO-8859-15' for Basque, Catalan, Dutch, English, Finnish,
- French, Galician, German, Irish, Italian, Portuguese,
- Spanish, Swedish, Walloon,
+`-w NUMBER'
+`--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.
- * `KOI8-R' for Russian,
+`--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.
- * `KOI8-U' for Ukrainian,
+`-s'
+`--sort-output'
+ Generate sorted output. Note that using this option makes it much
+ harder for the translator to understand each message's context.
- * `KOI8-T' for Tajik,
+`-F'
+`--sort-by-file'
+ Sort output by file location.
- * `CP1251' for Bulgarian, Byelorussian,
- * `GB2312', `GBK', `GB18030' for simplified writing of Chinese,
+7.1.8 Informative output
+------------------------
- * `BIG5', `BIG5-HKSCS' for traditional writing of Chinese,
+`-h'
+`--help'
+ Display this help and exit.
- * `EUC-JP' for Japanese,
+`-V'
+`--version'
+ Output version information and exit.
- * `EUC-KR' for Korean,
+`-v'
+`--verbose'
+ Increase verbosity level.
- * `TIS-620' for Thai,
+`-q'
+`--quiet'
+`--silent'
+ Suppress progress indicators.
- * `GEORGIAN-PS' for Georgian,
- * `UTF-8' for any language, including those listed above.
+\1f
+File: gettext.info, Node: Editing, Next: Manipulating, Prev: Updating, Up: Top
- 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 encoding, instead of your locale's encoding. This is
- because in UTF-8 the real quote characters can be represented
- (single quote characters: U+2018, U+2019, double quote characters:
- U+201C, U+201D), whereas none of ISO-8859-* charsets has them all.
- Users in UTF-8 locales will see the 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).
+8 Editing PO Files
+******************
- 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", "leftdoublequotemark",
- "rightdoublequotemark", "singlelowquotemark", "doublelowquotemark".
+* Menu:
- Note that only recent versions of GNU Emacs support the UTF-8
- encoding: Emacs 20 with Mule-UCS, and Emacs 21. As of January
- 2001, XEmacs doesn't support the UTF-8 encoding.
+* KBabel:: KDE's PO File Editor
+* Gtranslator:: GNOME's PO File Editor
+* PO Mode:: Emacs's PO File Editor
- The character encoding name can be written in either upper or
- lower case. Usually upper case is preferred.
+\1f
+File: gettext.info, Node: KBabel, Next: Gtranslator, Prev: Editing, Up: Editing
-Content-Transfer-Encoding
- Set this to `8bit'.
+8.1 KDE's PO File Editor
+========================
-Plural-Forms
- 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 *Note Plural forms::.
+\1f
+File: gettext.info, Node: Gtranslator, Next: PO Mode, Prev: KBabel, Up: Editing
+
+8.2 GNOME's PO File Editor
+==========================
\1f
-File: gettext.info, Node: Updating, Next: Manipulating, Prev: Creating, Up: Top
+File: gettext.info, Node: PO Mode, Prev: Gtranslator, Up: Editing
-6 Updating Existing PO Files
-****************************
+8.3 Emacs's PO File Editor
+==========================
+
+For those of you being the lucky users of Emacs, PO mode has been
+specifically created for providing a cozy environment for editing or
+modifying PO files. While editing a PO file, PO mode allows for the
+easy browsing of auxiliary and compendium PO files, as well as for
+following references into the set of C program sources from which PO
+files have been derived. It has a few special features, among which
+are the interactive marking of program strings as translatable, and the
+validation of PO files with easy repositioning to PO file lines showing
+errors.
+
+ For the beginning, besides main PO mode commands (*note Main PO
+Commands::), you should know how to move between entries (*note Entry
+Positioning::), and how to handle untranslated entries (*note
+Untranslated Entries::).
* Menu:
-* msgmerge Invocation:: Invoking the `msgmerge' Program
+* Installation:: Completing GNU `gettext' Installation
+* Main PO Commands:: Main Commands
+* Entry Positioning:: Entry Positioning
+* Normalizing:: Normalizing Strings in Entries
* Translated Entries:: Translated Entries
* Fuzzy Entries:: Fuzzy Entries
* Untranslated Entries:: Untranslated Entries
* Compendium:: Using Translation Compendia
\1f
-File: gettext.info, Node: msgmerge Invocation, Next: Translated Entries, Prev: Updating, Up: Updating
+File: gettext.info, Node: Installation, Next: Main PO Commands, Prev: PO Mode, Up: PO Mode
-6.1 Invoking the `msgmerge' Program
-===================================
+8.3.1 Completing GNU `gettext' Installation
+-------------------------------------------
- msgmerge [OPTION] DEF.po REF.pot
+Once you have received, unpacked, configured and compiled the GNU
+`gettext' distribution, the `make install' command puts in place the
+programs `xgettext', `msgfmt', `gettext', and `msgmerge', as well as
+their available message catalogs. To top off a comfortable
+installation, you might also want to make the PO mode available to your
+Emacs users.
- The `msgmerge' program merges two Uniforum style .po files together.
-The DEF.po file is an existing PO file with translations which will be
-taken over to the newly created file as long as they still match;
-comments will be preserved, but extracted comments and file positions
-will be discarded. The REF.pot file is the last created PO file with
-up-to-date source references but old translations, or a PO Template file
-(generally created by `xgettext'); any translations or comments in the
-file will be discarded, however dot comments and file positions will be
-preserved. Where an exact match cannot be found, fuzzy matching is
-used to produce better results.
+ During the installation of the PO mode, you might want to modify your
+file `.emacs', once and for all, so it contains a few lines looking
+like:
-6.1.1 Input file location
--------------------------
+ (setq auto-mode-alist
+ (cons '("\\.po\\'\\|\\.po\\." . po-mode) auto-mode-alist))
+ (autoload 'po-mode "po-mode" "Major mode for translators to edit PO files" t)
-`DEF.po'
- Translations referring to old sources.
+ Later, whenever you edit some `.po' file, or any file having the
+string `.po.' within its name, Emacs loads `po-mode.elc' (or
+`po-mode.el') as needed, and automatically activates PO mode commands
+for the associated buffer. The string _PO_ appears in the mode line
+for any buffer for which PO mode is active. Many PO files may be
+active at once in a single Emacs session.
-`REF.pot'
- References to the new sources.
+ If you are using Emacs version 20 or newer, and have already
+installed the appropriate international fonts on your system, you may
+also tell Emacs how to determine automatically the coding system of
+every PO file. This will often (but not always) cause the necessary
+fonts to be loaded and used for displaying the translations on your
+Emacs screen. For this to happen, add the lines:
+
+ (modify-coding-system-alist 'file "\\.po\\'\\|\\.po\\."
+ 'po-find-file-coding-system)
+ (autoload 'po-find-file-coding-system "po-mode")
+
+to your `.emacs' file. If, with this, you still see boxes instead of
+international characters, try a different font set (via Shift Mouse
+button 1).
+
+\1f
+File: gettext.info, Node: Main PO Commands, Next: Entry Positioning, Prev: Installation, Up: PO Mode
+
+8.3.2 Main PO mode Commands
+---------------------------
+
+After setting up Emacs with something similar to the lines in *Note
+Installation::, PO mode is activated for a window when Emacs finds a PO
+file in that window. This puts the window read-only and establishes a
+po-mode-map, which is a genuine Emacs mode, in a way that is not derived
+from text mode in any way. Functions found on `po-mode-hook', if any,
+will be executed.
+
+ 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 (*note Translated Entries::, 3 fuzzy entries
+(*note Fuzzy Entries::), 10 untranslated entries (*note Untranslated
+Entries::) and 2 obsolete entries (*note 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.
+
+ The main PO commands are those which do not fit into the other
+categories of subsequent sections. These allow for quitting PO mode or
+for managing windows in special ways.
+
+`_'
+ Undo last modification to the PO file (`po-undo').
+
+`Q'
+ Quit processing and save the PO file (`po-quit').
+
+`q'
+ Quit processing, possibly after confirmation
+ (`po-confirm-and-quit').
+
+`0'
+ Temporary leave the PO file window (`po-other-window').
+
+`?'
+`h'
+ Show help about PO mode (`po-help').
-`-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.
+`='
+ Give some PO file statistics (`po-statistics').
-`-C FILE'
-`--compendium=FILE'
- Specify an additional library of message translations. *Note
- Compendium::. This option may be specified more than once.
+`V'
+ Batch validate the format of the whole PO file (`po-validate').
-6.1.2 Operation mode
---------------------
+ The command `_' (`po-undo') interfaces to the Emacs _undo_ facility.
+*Note Undoing Changes: (emacs)Undo. Each time `U' is typed,
+modifications which the translator did to the PO file are undone a
+little more. For the purpose of undoing, each PO mode command is
+atomic. This is especially true for the `<RET>' command: the whole
+edition made by using a single use of this command is undone at once,
+even if the edition itself implied several actions. However, while in
+the editing window, one can undo the edition work quite parsimoniously.
-`-U'
-`--update'
- Update DEF.po. Do nothing if DEF.po is already up to date.
+ The commands `Q' (`po-quit') and `q' (`po-confirm-and-quit') are
+used when the translator is done with the PO file. The former is a bit
+less verbose than the latter. If the file has been modified, it is
+saved to disk first. In both cases, and prior to all this, the
+commands check if any untranslated messages remain in the PO file and,
+if so, the translator is asked if she really wants to leave off working
+with this PO file. This is the preferred way of getting rid of an
+Emacs PO file buffer. Merely killing it through the usual command
+`C-x k' (`kill-buffer') is not the tidiest way to proceed.
+ The command `0' (`po-other-window') is another, softer way, to leave
+PO mode, temporarily. It just moves the cursor to some other Emacs
+window, and pops one if necessary. For example, if the translator just
+got PO mode to show some source context in some other, she might
+discover some apparent bug in the program source that needs correction.
+This command allows the translator to change sex, become a programmer,
+and have the cursor right into the window containing the program she
+(or rather _he_) wants to modify. By later getting the cursor back in
+the PO file window, or by asking Emacs to edit this file once again, PO
+mode is then recovered.
-6.1.3 Output file location
---------------------------
+ The command `h' (`po-help') displays a summary of all available PO
+mode commands. The translator should then type any character to resume
+normal PO mode operations. The command `?' has the same effect as `h'.
-`-o FILE'
-`--output-file=FILE'
- Write output to specified file.
+ The command `=' (`po-statistics') computes the total number of
+entries in the PO file, the ordinal of the current entry (counted from
+1), the number of untranslated entries, the number of obsolete entries,
+and displays all these numbers.
+ The command `V' (`po-validate') launches `msgfmt' in checking and
+verbose mode over the current PO file. This command first offers to
+save the current PO file on disk. The `msgfmt' tool, from GNU
+`gettext', has the purpose of creating a MO file out of a PO file, and
+PO mode uses the features of this program for checking the overall
+format of a PO file, as well as all individual entries.
- The results are written to standard output if no output file is
-specified or if it is `-'.
+ The program `msgfmt' runs asynchronously with Emacs, so the
+translator regains control immediately while her PO file is being
+studied. Error output is collected in the Emacs `*compilation*' buffer,
+displayed in another window. The regular Emacs command `C-x`'
+(`next-error'), as well as other usual compile commands, allow the
+translator to reposition quickly to the offending parts of the PO file.
+Once the cursor is on the line in error, the translator may decide on
+any PO mode action which would help correcting the error.
-6.1.4 Output file location in update mode
------------------------------------------
+\1f
+File: gettext.info, Node: Entry Positioning, Next: Normalizing, Prev: Main PO Commands, Up: PO Mode
-The result is written back to DEF.po.
+8.3.3 Entry Positioning
+-----------------------
-`--backup=CONTROL'
- Make a backup of DEF.po
+The cursor in a PO file window is almost always part of an entry. The
+only exceptions are the special case when the cursor is after the last
+entry in the file, or when the PO file is empty. The entry where the
+cursor is found to be is said to be the current entry. Many PO mode
+commands operate on the current entry, so moving the cursor does more
+than allowing the translator to browse the PO file, this also selects
+on which entry commands operate.
-`--suffix=SUFFIX'
- Override the usual backup suffix.
+ Some PO mode commands alter the position of the cursor in a
+specialized way. A few of those special purpose positioning are
+described here, the others are described in following sections (for a
+complete list try `C-h m'):
+`.'
+ Redisplay the current entry (`po-current-entry').
- The version control method may be selected via the `--backup' option
-or through the `VERSION_CONTROL' environment variable. Here are the
-values:
+`n'
+ Select the entry after the current one (`po-next-entry').
-`none'
-`off'
- Never make backups (even if `--backup' is given).
+`p'
+ Select the entry before the current one (`po-previous-entry').
-`numbered'
-`t'
- Make numbered backups.
+`<'
+ Select the first entry in the PO file (`po-first-entry').
-`existing'
-`nil'
- Make numbered backups if numbered backups for this file already
- exist, otherwise make simple backups.
+`>'
+ Select the last entry in the PO file (`po-last-entry').
-`simple'
-`never'
- Always make simple backups.
+`m'
+ Record the location of the current entry for later use
+ (`po-push-location').
+`r'
+ Return to a previously saved entry location (`po-pop-location').
- The backup suffix is `~', unless set with `--suffix' or the
-`SIMPLE_BACKUP_SUFFIX' environment variable.
+`x'
+ Exchange the current entry location with the previously saved one
+ (`po-exchange-location').
-6.1.5 Operation modifiers
--------------------------
-`-m'
-`--multi-domain'
- Apply REF.pot to each of the domains in DEF.po.
+ Any Emacs command able to reposition the cursor may be used to
+select the current entry in PO mode, including commands which move by
+characters, lines, paragraphs, screens or pages, and search commands.
+However, there is a kind of standard way to display the current entry
+in PO mode, which usual Emacs commands moving the cursor do not
+especially try to enforce. The command `.' (`po-current-entry') has
+the sole purpose of redisplaying the current entry properly, after the
+current entry has been changed by means external to PO mode, or the
+Emacs screen otherwise altered.
-`-N'
-`--no-fuzzy-matching'
- Do not use fuzzy matching when an exact match is not found. This
- may speed up the operation considerably.
+ It is yet to be decided if PO mode helps the translator, or otherwise
+irritates her, by forcing a rigid window disposition while she is doing
+her work. We originally had quite precise ideas about how windows
+should behave, but on the other hand, anyone used to Emacs is often
+happy to keep full control. Maybe a fixed window disposition might be
+offered as a PO mode option that the translator might activate or
+deactivate at will, so it could be offered on an experimental basis.
+If nobody feels a real need for using it, or a compulsion for writing
+it, we should drop this whole idea. The incentive for doing it should
+come from translators rather than programmers, as opinions from an
+experienced translator are surely more worth to me than opinions from
+programmers _thinking_ about how _others_ should do translation.
-6.1.6 Input file syntax
------------------------
+ The commands `n' (`po-next-entry') and `p' (`po-previous-entry')
+move the cursor the entry following, or preceding, the current one. If
+`n' is given while the cursor is on the last entry of the PO file, or
+if `p' is given while the cursor is on the first entry, no move is done.
-`-P'
-`--properties-input'
- Assume the input files are Java ResourceBundles in Java
- `.properties' syntax, not in PO file syntax.
+ The commands `<' (`po-first-entry') and `>' (`po-last-entry') move
+the cursor to the first entry, or last entry, of the PO file. When the
+cursor is located past the last entry in a PO file, most PO mode
+commands will return an error saying `After last entry'. Moreover, the
+commands `<' and `>' 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.
+*Note Marking::.
-`--stringtable-input'
- Assume the input files are NeXTstep/GNUstep localized resource
- files in `.strings' syntax, not in PO file syntax.
+ The translator may decide, before working at the translation of a
+particular entry, that she needs to browse the remainder of the PO
+file, maybe for finding the terminology or phraseology used in related
+entries. She can of course use the standard Emacs idioms for saving
+the current cursor location in some register, and use that register for
+getting back, or else, use the location ring.
+ PO mode offers another approach, by which cursor locations may be
+saved onto a special stack. The command `m' (`po-push-location')
+merely adds the location of current entry to the stack, pushing the
+already saved locations under the new one. The command `r'
+(`po-pop-location') consumes the top stack element and repositions the
+cursor to the entry associated with that top element. This position is
+then lost, for the next `r' will move the cursor to the previously
+saved location, and so on until no locations remain on the stack.
-6.1.7 Output details
---------------------
+ If the translator wants the position to be kept on the location
+stack, maybe for taking a look at the entry associated with the top
+element, then go elsewhere with the intent of getting back later, she
+ought to use `m' immediately after `r'.
-`--force-po'
- Always write an output file even if it contains no message.
+ The command `x' (`po-exchange-location') simultaneously repositions
+the cursor to the entry associated with the top element of the stack of
+saved locations, and replaces that top element with the location of the
+current entry before the move. Consequently, repeating the `x' command
+toggles alternatively between two entries. For achieving this, the
+translator will position the cursor on the first entry, use `m', then
+position to the second entry, and merely use `x' for making the switch.
-`-i'
-`--indent'
- Write the .po file using indented style.
+\1f
+File: gettext.info, Node: Normalizing, Next: Translated Entries, Prev: Entry Positioning, Up: PO Mode
-`--no-location'
- Do not write `#: FILENAME:LINE' lines.
+8.3.4 Normalizing Strings in Entries
+------------------------------------
-`--add-location'
- Generate `#: FILENAME:LINE' lines (default).
+There are many different ways for encoding a particular string into a
+PO file entry, because there are so many different ways to split and
+quote multi-line strings, and even, to represent special characters by
+backslashed escaped sequences. Some features of PO mode rely on the
+ability for PO mode to scan an already existing PO file for a
+particular string encoded into the `msgid' field of some entry. Even
+if PO mode has internally all the built-in machinery for implementing
+this recognition easily, doing it fast is technically difficult. To
+facilitate a solution to this efficiency problem, we decided on a
+canonical representation for strings.
-`--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.
+ A conventional representation of strings in a PO file is currently
+under discussion, and PO mode experiments with a canonical
+representation. Having both `xgettext' and PO mode converging towards
+a uniform way of representing equivalent strings would be useful, as
+the internal normalization needed by PO mode could be automatically
+satisfied when using `xgettext' from GNU `gettext'. An explicit PO
+mode normalization should then be only necessary for PO files imported
+from elsewhere, or for when the convention itself evolves.
-`-p'
-`--properties-output'
- Write out a Java ResourceBundle in Java `.properties' syntax. Note
- that this file format doesn't support plural forms and silently
- drops obsolete messages.
+ So, for achieving normalization of at least the strings of a given
+PO file needing a canonical representation, the following PO mode
+command is available:
-`--stringtable-output'
- Write out a NeXTstep/GNUstep localized resource file in `.strings'
- syntax. Note that this file format doesn't support plural forms.
+`M-x po-normalize'
+ Tidy the whole PO file by making entries more uniform.
-`-w NUMBER'
-`--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.
+ The special command `M-x po-normalize', which has no associated
+keys, revises all entries, ensuring that strings of both original and
+translated entries use uniform internal quoting in the PO file. It
+also removes any crumb after the last entry. This command may be
+useful for PO files freshly imported from elsewhere, or if we ever
+improve on the canonical quoting format we use. This canonical format
+is not only meant for getting cleaner PO files, but also for greatly
+speeding up `msgid' string lookup for some other PO mode commands.
-`-s'
-`--sort-output'
- Generate sorted output. Note that using this option makes it much
- harder for the translator to understand each message's context.
+ `M-x po-normalize' presently makes three passes over the entries.
+The first implements heuristics for converting PO files for GNU
+`gettext' 0.6 and earlier, in which `msgid' and `msgstr' fields were
+using K&R style C string syntax for multi-line strings. These
+heuristics may fail for comments not related to obsolete entries and
+ending with a backslash; they also depend on subsequent passes for
+finalizing the proper commenting of continued lines for obsolete
+entries. This first pass might disappear once all oldish PO files
+would have been adjusted. The second and third pass normalize all
+`msgid' and `msgstr' strings respectively. They also clean out those
+trailing backslashes used by XView's `msgfmt' for continued lines.
-`-F'
-`--sort-by-file'
- Sort output by file location.
+ Having such an explicit normalizing command allows for importing PO
+files from other sources, but also eases the evolution of the current
+convention, evolution driven mostly by aesthetic concerns, as of now.
+It is easy to make suggested adjustments at a later time, as the
+normalizing command and eventually, other GNU `gettext' tools should
+greatly automate conformance. A description of the canonical string
+format is given below, for the particular benefit of those not having
+Emacs handy, and who would nevertheless want to handcraft their PO
+files in nice ways.
+ Right now, in PO mode, strings are single line or multi-line. A
+string goes multi-line if and only if it has _embedded_ newlines, that
+is, if it matches `[^\n]\n+[^\n]'. So, we would have:
-6.1.8 Informative output
-------------------------
+ msgstr "\n\nHello, world!\n\n\n"
-`-h'
-`--help'
- Display this help and exit.
+ but, replacing the space by a newline, this becomes:
-`-V'
-`--version'
- Output version information and exit.
+ msgstr ""
+ "\n"
+ "\n"
+ "Hello,\n"
+ "world!\n"
+ "\n"
+ "\n"
-`-v'
-`--verbose'
- Increase verbosity level.
+ We are deliberately using a caricatural example, here, to make the
+point clearer. Usually, multi-lines are not that bad looking. It is
+probable that we will implement the following suggestion. We might
+lump together all initial newlines into the empty string, and also all
+newlines introducing empty lines (that is, for N > 1, the N-1'th last
+newlines would go together on a separate string), so making the
+previous example appear:
-`-q'
-`--quiet'
-`--silent'
- Suppress progress indicators.
+ msgstr "\n\n"
+ "Hello,\n"
+ "world!\n"
+ "\n\n"
+ There are a few yet undecided little points about string
+normalization, to be documented in this manual, once these questions
+settle.
\1f
-File: gettext.info, Node: Translated Entries, Next: Fuzzy Entries, Prev: msgmerge Invocation, Up: Updating
+File: gettext.info, Node: Translated Entries, Next: Fuzzy Entries, Prev: Normalizing, Up: PO Mode
-6.2 Translated Entries
-======================
+8.3.5 Translated Entries
+------------------------
Each PO file entry for which the `msgstr' field has been filled with a
translation, and which is not marked as fuzzy (*note Fuzzy Entries::),
entry. *Note Fuzzy Entries::.
\1f
-File: gettext.info, Node: Fuzzy Entries, Next: Untranslated Entries, Prev: Translated Entries, Up: Updating
+File: gettext.info, Node: Fuzzy Entries, Next: Untranslated Entries, Prev: Translated Entries, Up: PO Mode
-6.3 Fuzzy Entries
-=================
+8.3.6 Fuzzy Entries
+-------------------
Each PO file entry may have a set of "attributes", which are qualities
given a name and explicitly associated with the translation, using a
still exists.
\1f
-File: gettext.info, Node: Untranslated Entries, Next: Obsolete Entries, Prev: Fuzzy Entries, Up: Updating
+File: gettext.info, Node: Untranslated Entries, Next: Obsolete Entries, Prev: Fuzzy Entries, Up: PO Mode
-6.4 Untranslated Entries
-========================
+8.3.7 Untranslated Entries
+--------------------------
When `xgettext' originally creates a PO file, unless told otherwise, it
initializes the `msgid' field with the untranslated string, and leaves
untranslated string still exists.
\1f
-File: gettext.info, Node: Obsolete Entries, Next: Modifying Translations, Prev: Untranslated Entries, Up: Updating
+File: gettext.info, Node: Obsolete Entries, Next: Modifying Translations, Prev: Untranslated Entries, Up: PO Mode
-6.5 Obsolete Entries
-====================
+8.3.8 Obsolete Entries
+----------------------
By "obsolete" PO file entries, we mean those entries which are
commented out, usually by `msgmerge' when it found that the translation
tries to provide handy tools for helping her to do so.
\1f
-File: gettext.info, Node: Modifying Translations, Next: Modifying Comments, Prev: Obsolete Entries, Up: Updating
+File: gettext.info, Node: Modifying Translations, Next: Modifying Comments, Prev: Obsolete Entries, Up: PO Mode
-6.6 Modifying Translations
-==========================
+8.3.9 Modifying Translations
+----------------------------
PO mode prevents direct modification of the PO file, by the usual means
Emacs gives for altering a buffer's contents. By doing so, it pretends
request. *Note Keyboard Macros: (emacs)Keyboard Macros.
\1f
-File: gettext.info, Node: Modifying Comments, Next: Subedit, Prev: Modifying Translations, Up: Updating
+File: gettext.info, Node: Modifying Comments, Next: Subedit, Prev: Modifying Translations, Up: PO Mode
-6.7 Modifying Comments
-======================
+8.3.10 Modifying Comments
+-------------------------
Any translation work done seriously will raise many linguistic
difficulties, for which decisions have to be made, and the choices
previous translation where she likes.
\1f
-File: gettext.info, Node: Subedit, Next: C Sources Context, Prev: Modifying Comments, Up: Updating
+File: gettext.info, Node: Subedit, Next: C Sources Context, Prev: Modifying Comments, Up: PO Mode
-6.8 Details of Sub Edition
-==========================
+8.3.11 Details of Sub Edition
+-----------------------------
The PO subedit minor mode has a few peculiarities worth being described
in fuller detail. It installs a few commands over the usual editing set
each of them.
\1f
-File: gettext.info, Node: C Sources Context, Next: Auxiliary, Prev: Subedit, Up: Updating
+File: gettext.info, Node: C Sources Context, Next: Auxiliary, Prev: Subedit, Up: PO Mode
-6.9 C Sources Context
-=====================
+8.3.12 C Sources Context
+------------------------
PO mode is particularly powerful when used with PO files created
through GNU `gettext' utilities, as those utilities insert special
the directories she does not want anymore on the search path.
\1f
-File: gettext.info, Node: Auxiliary, Next: Compendium, Prev: C Sources Context, Up: Updating
+File: gettext.info, Node: Auxiliary, Next: Compendium, Prev: C Sources Context, Up: PO Mode
-6.10 Consulting Auxiliary PO Files
-==================================
+8.3.13 Consulting Auxiliary PO Files
+------------------------------------
PO mode is able to help the knowledgeable translator, being fluent in
many languages, at taking advantage of translations already achieved in
resolved, the translator should stay aware of normalisation issues.
\1f
-File: gettext.info, Node: Compendium, Prev: Auxiliary, Up: Updating
+File: gettext.info, Node: Compendium, Prev: Auxiliary, Up: PO Mode
-6.11 Using Translation Compendia
-================================
+8.3.14 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
\1f
File: gettext.info, Node: Creating Compendia, Next: Using Compendia, Prev: Compendium, Up: Compendium
-6.11.1 Creating Compendia
--------------------------
+8.3.14.1 Creating Compendia
+...........................
Basically every PO file consisting of translated entries only can be
declared as a valid compendium. Often the translator wants to have
special compendia; let's consider two cases: `concatenating PO files'
and `extracting a message subset from a PO file'.
-6.11.1.1 Concatenate PO Files
+8.3.14.2 Concatenate PO Files
.............................
To concatenate several valid PO files into one compendium file you can
files or postprocess the result using `msgattrib --translated
--no-fuzzy'.
-6.11.1.2 Extract a Message Subset from a PO File
+8.3.14.3 Extract a Message Subset from a PO File
................................................
Nobody wants to translate the same messages again and again; thus you
\1f
File: gettext.info, Node: Using Compendia, Prev: Creating Compendia, Up: Compendium
-6.11.2 Using Compendia
-----------------------
+8.3.14.4 Using Compendia
+........................
You can use a compendium file to initialize a translation from scratch
or to update an already existing translation.
-6.11.2.1 Initialize a New Translation File
+8.3.14.5 Initialize a New Translation File
..........................................
Since a PO file with translations does not exist the translator can
msgmerge --compendium compendium.po -o file.po /dev/null file.pot
-6.11.2.2 Update an Existing Translation File
+8.3.14.6 Update an Existing Translation File
............................................
Concatenate the compendium file(s) and the existing PO, merge the
msgmerge update.po file.pot | sed -e '/^#~/d' > file.po
\1f
-File: gettext.info, Node: Manipulating, Next: Binaries, Prev: Updating, Up: Top
+File: gettext.info, Node: Manipulating, Next: Binaries, Prev: Editing, Up: Top
-7 Manipulating PO Files
+9 Manipulating PO Files
***********************
Sometimes it is necessary to manipulate PO files in a way that is better
\1f
File: gettext.info, Node: msgcat Invocation, Next: msgconv Invocation, Prev: Manipulating, Up: Manipulating
-7.1 Invoking the `msgcat' Program
+9.1 Invoking the `msgcat' Program
=================================
msgcat [OPTION] [INPUTFILE]...
PO file to define them. File positions from all PO files will be
cumulated.
-7.1.1 Input file location
+9.1.1 Input file location
-------------------------
`INPUTFILE ...'
If INPUTFILE is `-', standard input is read.
-7.1.2 Output file location
+9.1.2 Output file location
--------------------------
`-o FILE'
The results are written to standard output if no output file is
specified or if it is `-'.
-7.1.3 Message selection
+9.1.3 Message selection
-----------------------
`-< NUMBER'
be printed.
-7.1.4 Input file syntax
+9.1.4 Input file syntax
-----------------------
`-P'
files in `.strings' syntax, not in PO file syntax.
-7.1.5 Output details
+9.1.5 Output details
--------------------
`-t'
Sort output by file location.
-7.1.6 Informative output
+9.1.6 Informative output
------------------------
`-h'
\1f
File: gettext.info, Node: msgconv Invocation, Next: msggrep Invocation, Prev: msgcat Invocation, Up: Manipulating
-7.2 Invoking the `msgconv' Program
+9.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
+9.2.1 Input file location
-------------------------
`INPUTFILE'
If no INPUTFILE is given or if it is `-', standard input is read.
-7.2.2 Output file location
+9.2.2 Output file location
--------------------------
`-o FILE'
The results are written to standard output if no output file is
specified or if it is `-'.
-7.2.3 Conversion target
+9.2.3 Conversion target
-----------------------
`-t'
The default encoding is the current locale's encoding.
-7.2.4 Input file syntax
+9.2.4 Input file syntax
-----------------------
`-P'
file in `.strings' syntax, not in PO file syntax.
-7.2.5 Output details
+9.2.5 Output details
--------------------
`--force-po'
Sort output by file location.
-7.2.6 Informative output
+9.2.6 Informative output
------------------------
`-h'
\1f
File: gettext.info, Node: msggrep Invocation, Next: msgfilter Invocation, Prev: msgconv Invocation, Up: Manipulating
-7.3 Invoking the `msggrep' Program
+9.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
+9.3.1 Input file location
-------------------------
`INPUTFILE'
If no INPUTFILE is given or if it is `-', standard input is read.
-7.3.2 Output file location
+9.3.2 Output file location
--------------------------
`-o FILE'
The results are written to standard output if no output file is
specified or if it is `-'.
-7.3.3 Message selection
+9.3.3 Message selection
-----------------------
[-N SOURCEFILE]... [-M DOMAINNAME]...
- [-K MSGID-PATTERN] [-T MSGSTR-PATTERN] [-C COMMENT-PATTERN]
+ [-J MSGCTXT-PATTERN [-K MSGID-PATTERN] [-T MSGSTR-PATTERN]
+ [-C COMMENT-PATTERN]
A message is selected if
* it comes from one of the specified source files,
* or if it comes from one of the specified domains,
+ * or if `-J' is given and its context (msgctxt) matches
+ MSGCTXT-PATTERN,
+
* or if `-K' is given and its key (msgid or msgid_plural) matches
MSGID-PATTERN,
`--domain=DOMAINNAME'
Select messages belonging to domain DOMAINNAME.
+`-J'
+`--msgctxt'
+ Start of patterns for the msgctxt.
+
`-K'
`--msgid'
Start of patterns for the msgid.
`--comment'
Start of patterns for the translator's comment.
+`-X'
+`--extracted-comment'
+ Start of patterns for the extracted comments.
+
`-E'
`--extended-regexp'
Specify that PATTERN is an extended regular expression.
`--ignore-case'
Ignore case distinctions.
+`-v'
+`--invert-match'
+ Output only the messages that do not match any selection
+ criterion, instead of the messages that match a selection
+ criterion.
+
-7.3.4 Input file syntax
+9.3.4 Input file syntax
-----------------------
`-P'
file in `.strings' syntax, not in PO file syntax.
-7.3.5 Output details
+9.3.5 Output details
--------------------
`--force-po'
Sort output by file location.
-7.3.6 Informative output
+9.3.6 Informative output
------------------------
`-h'
\1f
File: gettext.info, Node: msgfilter Invocation, Next: msguniq Invocation, Prev: msggrep Invocation, Up: Manipulating
-7.4 Invoking the `msgfilter' Program
+9.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
+9.4.1 Input file location
-------------------------
`-i INPUTFILE'
If no INPUTFILE is given or if it is `-', standard input is read.
-7.4.2 Output file location
+9.4.2 Output file location
--------------------------
`-o FILE'
The results are written to standard output if no output file is
specified or if it is `-'.
-7.4.3 The filter
+9.4.3 The filter
----------------
The FILTER can be any program that reads a translation from standard
input and writes a modified translation to standard output. A
-frequently used filter is `sed'.
+frequently used filter is `sed'. A few particular built-in filters are
+also recognized.
- Note: It is your responsibility to ensure that the FILTER can cope
+ Note: If the filter is not a built-in filter, you have to care about
+encodings: 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
convert the translation catalog to that encoding using the `msgconv'
it is not terminated with a newline. You can use GNU `sed' instead; it
does not have this limitation.
-7.4.4 Useful FILTER-OPTIONs when the FILTER is `sed'
+9.4.4 Useful FILTER-OPTIONs when the FILTER is `sed'
----------------------------------------------------
`-e SCRIPT'
Suppress automatic printing of pattern space.
-7.4.5 Input file syntax
+9.4.5 Built-in FILTERs
+----------------------
+
+The filter `recode-sr-latin' is recognized as a built-in filter. The
+command `recode-sr-latin' converts Serbian text, written in the
+Cyrillic script, to the Latin script. The command `msgfilter
+recode-sr-latin' applies this conversion to the translations of a PO
+file. Thus, it can be used to convert an `sr.po' file to an
+`sr@latin.po' file.
+
+ The use of built-in filters is not sensitive to the current locale's
+encoding. Moreover, when used with a built-in filter, `msgfilter' can
+automatically convert the message catalog to the UTF-8 encoding when
+needed.
+
+9.4.6 Input file syntax
-----------------------
`-P'
file in `.strings' syntax, not in PO file syntax.
-7.4.6 Output details
+9.4.7 Output details
--------------------
`--force-po'
Sort output by file location.
-7.4.7 Informative output
+9.4.8 Informative output
------------------------
`-h'
\1f
File: gettext.info, Node: msguniq Invocation, Next: msgcomm Invocation, Prev: msgfilter Invocation, Up: Manipulating
-7.5 Invoking the `msguniq' Program
+9.5 Invoking the `msguniq' Program
==================================
msguniq [OPTION] [INPUTFILE]
taken from the first translation. File positions will be cumulated.
When using the `--unique' option, duplicates are discarded.
-7.5.1 Input file location
+9.5.1 Input file location
-------------------------
`INPUTFILE'
If no INPUTFILE is given or if it is `-', standard input is read.
-7.5.2 Output file location
+9.5.2 Output file location
--------------------------
`-o FILE'
The results are written to standard output if no output file is
specified or if it is `-'.
-7.5.3 Message selection
+9.5.3 Message selection
-----------------------
`-d'
Print only unique messages, discard duplicates.
-7.5.4 Input file syntax
+9.5.4 Input file syntax
-----------------------
`-P'
file in `.strings' syntax, not in PO file syntax.
-7.5.5 Output details
+9.5.5 Output details
--------------------
`-t'
Sort output by file location.
-7.5.6 Informative output
+9.5.6 Informative output
------------------------
`-h'
\1f
File: gettext.info, Node: msgcomm Invocation, Next: msgcmp Invocation, Prev: msguniq Invocation, Up: Manipulating
-7.6 Invoking the `msgcomm' Program
+9.6 Invoking the `msgcomm' Program
==================================
msgcomm [OPTION] [INPUTFILE]...
preserved, but only from the first PO file to define them. File
positions from all PO files will be cumulated.
-7.6.1 Input file location
+9.6.1 Input file location
-------------------------
`INPUTFILE ...'
If INPUTFILE is `-', standard input is read.
-7.6.2 Output file location
+9.6.2 Output file location
--------------------------
`-o FILE'
The results are written to standard output if no output file is
specified or if it is `-'.
-7.6.3 Message selection
+9.6.3 Message selection
-----------------------
`-< NUMBER'
be printed.
-7.6.4 Input file syntax
+9.6.4 Input file syntax
-----------------------
`-P'
files in `.strings' syntax, not in PO file syntax.
-7.6.5 Output details
+9.6.5 Output details
--------------------
`--force-po'
Don't write header with `msgid ""' entry.
-7.6.6 Informative output
+9.6.6 Informative output
------------------------
`-h'
\1f
File: gettext.info, Node: msgcmp Invocation, Next: msgattrib Invocation, Prev: msgcomm Invocation, Up: Manipulating
-7.7 Invoking the `msgcmp' Program
+9.7 Invoking the `msgcmp' Program
=================================
msgcmp [OPTION] DEF.po REF.pot
and every message in your program. Where an exact match cannot be
found, fuzzy matching is used to produce better diagnostics.
-7.7.1 Input file location
+9.7.1 Input file location
-------------------------
`DEF.po'
searched relative to this list of directories.
-7.7.2 Operation modifiers
+9.7.2 Operation modifiers
-------------------------
`-m'
Apply REF.pot to each of the domains in DEF.po.
-7.7.3 Input file syntax
+9.7.3 Input file syntax
-----------------------
`-P'
files in `.strings' syntax, not in PO file syntax.
-7.7.4 Informative output
+9.7.4 Informative output
------------------------
`-h'
\1f
File: gettext.info, Node: msgattrib Invocation, Next: msgen Invocation, Prev: msgcmp Invocation, Up: Manipulating
-7.8 Invoking the `msgattrib' Program
+9.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
+9.8.1 Input file location
-------------------------
`INPUTFILE'
If no INPUTFILE is given or if it is `-', standard input is read.
-7.8.2 Output file location
+9.8.2 Output file location
--------------------------
`-o FILE'
The results are written to standard output if no output file is
specified or if it is `-'.
-7.8.3 Message selection
+9.8.3 Message selection
-----------------------
`--translated'
Keep obsolete #~ messages, remove all other messages.
-7.8.4 Attribute manipulation
+9.8.4 Attribute manipulation
----------------------------
Attributes are modified after the message selection/removal has been
obsolete messages and makes them non-obsolete.
-7.8.5 Input file syntax
+9.8.5 Input file syntax
-----------------------
`-P'
file in `.strings' syntax, not in PO file syntax.
-7.8.6 Output details
+9.8.6 Output details
--------------------
`--force-po'
Sort output by file location.
-7.8.7 Informative output
+9.8.7 Informative output
------------------------
`-h'
\1f
File: gettext.info, Node: msgen Invocation, Next: msgexec Invocation, Prev: msgattrib Invocation, Up: Manipulating
-7.9 Invoking the `msgen' Program
+9.9 Invoking the `msgen' Program
================================
msgen [OPTION] INPUTFILE
task. The main difference is that `msginit' cares specially about the
header entry, whereas `msgen' doesn't.
-7.9.1 Input file location
+9.9.1 Input file location
-------------------------
`INPUTFILE'
If INPUTFILE is `-', standard input is read.
-7.9.2 Output file location
+9.9.2 Output file location
--------------------------
`-o FILE'
The results are written to standard output if no output file is
specified or if it is `-'.
-7.9.3 Input file syntax
+9.9.3 Input file syntax
-----------------------
`-P'
file in `.strings' syntax, not in PO file syntax.
-7.9.4 Output details
+9.9.4 Output details
--------------------
`--force-po'
Sort output by file location.
-7.9.5 Informative output
+9.9.5 Informative output
------------------------
`-h'
\1f
File: gettext.info, Node: msgexec Invocation, Next: libgettextpo, Prev: msgen Invocation, Up: Manipulating
-7.10 Invoking the `msgexec' Program
+9.10 Invoking the `msgexec' Program
===================================
msgexec [OPTION] COMMAND [COMMAND-OPTION]
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 of
-the message.
+the message. If the message has a context, the environment variable
+`MSGEXEC_MSGCTXT' is bound to the message's msgctxt, otherwise it is
+unbound.
Note: It is your responsibility to ensure that the COMMAND can cope
with input encoded in the translation catalog's encoding. If the
`msgconv' program and then make `msgexec' work in an UTF-8 locale, by
using the `LC_ALL' environment variable.
-7.10.1 Input file location
+9.10.1 Input file location
--------------------------
`-i INPUTFILE'
If no INPUTFILE is given or if it is `-', standard input is read.
-7.10.2 Input file syntax
+9.10.2 Input file syntax
------------------------
`-P'
file in `.strings' syntax, not in PO file syntax.
-7.10.3 Informative output
+9.10.3 Informative output
-------------------------
`-h'
\1f
File: gettext.info, Node: libgettextpo, Prev: msgexec Invocation, Up: Manipulating
-7.11 Writing your own programs that process PO files
+9.11 Writing your own programs that process PO files
====================================================
For the tasks for which a combination of `msgattrib', `msgcat' etc. is
po_file_free (file);
\1f
-File: gettext.info, Node: Binaries, Next: Users, Prev: Manipulating, Up: Top
+File: gettext.info, Node: Binaries, Next: Programmers, Prev: Manipulating, Up: Top
-8 Producing Binary MO Files
-***************************
+10 Producing Binary MO Files
+****************************
* Menu:
\1f
File: gettext.info, Node: msgfmt Invocation, Next: msgunfmt Invocation, Prev: Binaries, Up: Binaries
-8.1 Invoking the `msgfmt' Program
-=================================
+10.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
--------------------------
+10.1.1 Input file location
+--------------------------
`FILENAME.po ...'
If an input file is `-', standard input is read.
-8.1.2 Operation mode
---------------------
+10.1.2 Operation mode
+---------------------
`-j'
`--java'
Qt mode: generate a Qt `.qm' file.
-8.1.3 Output file location
---------------------------
+10.1.3 Output file location
+---------------------------
`-o FILE'
`--output-file=FILE'
If the output FILE is `-', output is written to standard output.
-8.1.4 Output file location in Java mode
----------------------------------------
+10.1.4 Output file location in Java mode
+----------------------------------------
`-r RESOURCE'
`--resource=RESOURCE'
resource name, separated with an underscore. The `-d' option is
mandatory. The class is written under the specified directory.
-8.1.5 Output file location in C# mode
--------------------------------------
+10.1.5 Output file location in C# mode
+--------------------------------------
`-r RESOURCE'
`--resource=RESOURCE'
in a subdirectory of the specified directory whose name depends on the
locale.
-8.1.6 Output file location in Tcl mode
---------------------------------------
+10.1.6 Output file location in Tcl mode
+---------------------------------------
`-l LOCALE'
`--locale=LOCALE'
The `-l' and `-d' options are mandatory. The `.msg' file is written
in the specified directory.
-8.1.7 Input file syntax
------------------------
+10.1.7 Input file syntax
+------------------------
`-P'
`--properties-input'
files in `.strings' syntax, not in PO file syntax.
-8.1.8 Input file interpretation
--------------------------------
+10.1.8 Input file interpretation
+--------------------------------
`-c'
`--check'
not been validated by a human translator.
-8.1.9 Output details
---------------------
+10.1.9 Output details
+---------------------
`-a NUMBER'
`--alignment=NUMBER'
lookup).
-8.1.10 Informative output
--------------------------
+10.1.10 Informative output
+--------------------------
`-h'
`--help'
\1f
File: gettext.info, Node: msgunfmt Invocation, Next: MO Files, Prev: msgfmt Invocation, Up: Binaries
-8.2 Invoking the `msgunfmt' Program
-===================================
+10.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
---------------------
+10.2.1 Operation mode
+---------------------
`-j'
`--java'
Tcl mode: input is a tcl/msgcat `.msg' file.
-8.2.2 Input file location
--------------------------
+10.2.2 Input file location
+--------------------------
`FILE ...'
Input .mo files.
If no input FILE is given or if it is `-', standard input is read.
-8.2.3 Input file location in Java mode
---------------------------------------
+10.2.3 Input file location in Java mode
+---------------------------------------
`-r RESOURCE'
`--resource=RESOURCE'
resource name, separated with an underscore. The class is located
using the `CLASSPATH'.
-8.2.4 Input file location in C# mode
-------------------------------------
+10.2.4 Input file location in C# mode
+-------------------------------------
`-r RESOURCE'
`--resource=RESOURCE'
in a subdirectory of the specified directory whose name depends on the
locale.
-8.2.5 Input file location in Tcl mode
--------------------------------------
+10.2.5 Input file location in Tcl mode
+--------------------------------------
`-l LOCALE'
`--locale=LOCALE'
The `-l' and `-d' options are mandatory. The `.msg' file is located
in the specified directory.
-8.2.6 Output file location
---------------------------
+10.2.6 Output file location
+---------------------------
`-o FILE'
`--output-file=FILE'
The results are written to standard output if no output file is
specified or if it is `-'.
-8.2.7 Output details
---------------------
+10.2.7 Output details
+---------------------
`--force-po'
Always write an output file even if it contains no message.
harder for the translator to understand each message's context.
-8.2.8 Informative output
-------------------------
+10.2.8 Informative output
+-------------------------
`-h'
`--help'
\1f
File: gettext.info, Node: MO Files, Prev: msgunfmt Invocation, Up: Binaries
-8.3 The Format of GNU MO Files
-==============================
+10.3 The Format of GNU MO Files
+===============================
The format of the generated MO files is best described by a picture,
which appears below.
multiple of the alignment value. On some RISC machines, a correct
alignment will speed things up.
+ Contexts are stored by storing the concatenation of the context, a
+<EOT> byte, and the original string, instead of the original string.
+
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 includes both.
H | start hash table | | | | |
... ... | | | |
H + S * 4 | end hash table | | | | |
- | | | | | |
- | NUL terminated 0th string <----------------' | | |
- | | | | |
- | NUL terminated 1st string <------------------' | |
- | | | |
- ... ... | |
- | | | |
- | NUL terminated 0th translation <---------------' |
- | | |
- | NUL terminated 1st translation <-----------------'
- | |
- ... ...
- | |
- +------------------------------------------+
-
-\1f
-File: gettext.info, Node: Users, Next: Programmers, Prev: Binaries, Up: Top
-
-9 The User's View
-*****************
-
-When GNU `gettext' will truly have reached its goal, average users
-should feel some kind of astonished pleasure, seeing the effect of that
-strange kind of magic that just makes their own native language appear
-everywhere on their screens. As for naive users, they would ideally
-have no special pleasure about it, merely taking their own language for
-_granted_, and becoming rather unhappy otherwise.
-
- So, let's try to describe here how we would like the magic to
-operate, as we want the users' view to be the simplest, among all ways
-one could look at GNU `gettext'. All other software engineers:
-programmers, translators, maintainers, should work together in such a
-way that the magic becomes possible. This is a long and progressive
-undertaking, and information is available about the progress of the
-Translation Project.
-
- When a package is distributed, there are two kinds of users:
-"installers" who fetch the distribution, unpack it, configure it,
-compile it and install it for themselves or others to use; and "end
-users" that call programs of the package, once these have been
-installed at their site. GNU `gettext' is offering magic for both
-installers and end users.
-
-* Menu:
-
-* Matrix:: The Current `ABOUT-NLS' Matrix
-* Installers:: Magic for Installers
-* End Users:: Magic for End Users
-
-\1f
-File: gettext.info, Node: Matrix, Next: Installers, Prev: Users, Up: Users
-
-9.1 The Current `ABOUT-NLS' Matrix
-==================================
-
-Languages are not equally supported in all packages using GNU
-`gettext'. To know if some package uses GNU `gettext', one may check
-the distribution for the `ABOUT-NLS' information file, for 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. *Note End Users:: for a complete
-description of the format for LL.
-
- More generally, a matrix is available for showing the current state
-of the Translation Project, listing which packages are prepared for
-multi-lingual messages, and which languages are supported by each.
-Because this information changes often, this matrix is not kept within
-this GNU `gettext' manual. This information is often found in file
-`ABOUT-NLS' from various distributions, but is also as old as the
-distribution itself. A recent copy of this `ABOUT-NLS' file,
-containing up-to-date information, should generally be found on the
-Translation Project sites, and also on most GNU archive sites.
-
-\1f
-File: gettext.info, Node: Installers, Next: End Users, Prev: Matrix, Up: Users
-
-9.2 Magic for Installers
-========================
-
-By default, packages fully using GNU `gettext', internally, are
-installed in such a way that they to allow translation of messages. At
-_configuration_ time, those packages should automatically detect
-whether the underlying host system already provides the GNU `gettext'
-functions. If not, the GNU `gettext' library should be automatically
-prepared and used. Installers may use special options at configuration
-time for changing this behavior. The command `./configure
---with-included-gettext' bypasses system `gettext' to use the included
-GNU `gettext' instead, while `./configure --disable-nls' 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
-with the package. However, the environment variable `LINGUAS' may be
-set, prior to configuration, to limit the installed set. `LINGUAS'
-should then contain a space separated list of two-letter codes, stating
-which languages are allowed.
-
-\1f
-File: gettext.info, Node: End Users, Prev: Installers, Up: 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. *Note 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
-this from their `.login' or `.profile' file.
+ | | | | | |
+ | NUL terminated 0th string <----------------' | | |
+ | | | | |
+ | NUL terminated 1st string <------------------' | |
+ | | | |
+ ... ... | |
+ | | | |
+ | NUL terminated 0th translation <---------------' |
+ | | |
+ | NUL terminated 1st translation <-----------------'
+ | |
+ ... ...
+ | |
+ +------------------------------------------+
\1f
-File: gettext.info, Node: Programmers, Next: Translators, Prev: Users, Up: Top
+File: gettext.info, Node: Programmers, Next: Translators, Prev: Binaries, Up: Top
-10 The Programmer's View
+11 The Programmer's View
************************
One aim of the current message catalog implementation provided by GNU
\1f
File: gettext.info, Node: catgets, Next: gettext, Prev: Programmers, Up: Programmers
-10.1 About `catgets'
+11.1 About `catgets'
====================
The `catgets' implementation is defined in the X/Open Portability
\1f
File: gettext.info, Node: Interface to catgets, Next: Problems with catgets, Prev: catgets, Up: catgets
-10.1.1 The Interface
+11.1.1 The Interface
--------------------
The interface to the `catgets' implementation consists of three
\1f
File: gettext.info, Node: Problems with catgets, Prev: Interface to catgets, Up: catgets
-10.1.2 Problems with the `catgets' Interface?!
+11.1.2 Problems with the `catgets' Interface?!
----------------------------------------------
Now that this description seemed to be really easy -- where are the
\1f
File: gettext.info, Node: gettext, Next: Comparison, Prev: catgets, Up: Programmers
-10.2 About `gettext'
+11.2 About `gettext'
====================
The definition of the `gettext' interface comes from a Uniforum
* Ambiguities:: Solving ambiguities
* Locating Catalogs:: Locating message catalog files
* Charset conversion:: How to request conversion to Unicode
+* Contexts:: Solving ambiguities in GUI programs
* Plural forms:: Additional functions for handling plurals
-* GUI program problems:: Another technique for solving ambiguities
* Optimized gettext:: Optimization of the *gettext functions
\1f
File: gettext.info, Node: Interface to gettext, Next: Ambiguities, Prev: gettext, Up: gettext
-10.2.1 The Interface
+11.2.1 The Interface
--------------------
The minimal functionality an interface must have is a) to select a
\1f
File: gettext.info, Node: Ambiguities, Next: Locating Catalogs, Prev: Interface to gettext, Up: gettext
-10.2.2 Solving Ambiguities
+11.2.2 Solving Ambiguities
--------------------------
While this single name domain works well for most applications there
\1f
File: gettext.info, Node: Locating Catalogs, Next: Charset conversion, Prev: Ambiguities, Up: gettext
-10.2.3 Locating Message Catalog Files
+11.2.3 Locating Message Catalog Files
-------------------------------------
Because many different languages for many different packages have to be
variables.
\1f
-File: gettext.info, Node: Charset conversion, Next: Plural forms, Prev: Locating Catalogs, Up: gettext
+File: gettext.info, Node: Charset conversion, Next: Contexts, Prev: Locating Catalogs, Up: gettext
-10.2.4 How to specify the output character set `gettext' uses
+11.2.4 How to specify the output character set `gettext' uses
-------------------------------------------------------------
`gettext' not only looks up a translation in a message catalog. It
global variable ERRNO is set accordingly.
\1f
-File: gettext.info, Node: Plural forms, Next: GUI program problems, Prev: Charset conversion, Up: gettext
+File: gettext.info, Node: Contexts, Next: Plural forms, Prev: Charset conversion, Up: gettext
+
+11.2.5 Using contexts for solving ambiguities
+---------------------------------------------
+
+One place where the `gettext' functions, if used normally, have big
+problems is within programs with graphical user interfaces (GUIs). The
+problem is that many of the strings which have to be translated are very
+short. They have to appear in pull-down menus which restricts the
+length. But strings which are not containing entire sentences or at
+least large fragments of a sentence may appear in more than one
+situation in the program but might have different translations. This is
+especially true for the one-word strings which are frequently used in
+GUI programs.
+
+ As a consequence many people say that the `gettext' approach is
+wrong and instead `catgets' should be used which indeed does not have
+this problem. But there is a very simple and powerful method to handle
+this kind of problems with the `gettext' functions.
+
+ Contexts can be added to strings to be translated. A context
+dependent translation lookup is when a translation for a given string
+is searched, that is limited to a given context. The translation for
+the same string in a different context can be different. The different
+translations of the same string in different contexts can be stored in
+the in the same MO file, and can be edited by the translator in the
+same PO file.
+
+ The `gettext.h' include file contains the lookup macros for strings
+with contexts. They are implemented as thin macros and inline functions
+over the functions from `<libintl.h>'.
+
+ const char *pgettext (const char *msgctxt, const char *msgid);
+
+ In a call of this macro, MSGCTXT and MSGID must be string literals.
+The macro returns the translation of MSGID, restricted to the context
+given by MSGCTXT.
+
+ The MSGCTXT string is visible in the PO file to the translator. You
+should try to make it somehow canonical and never changing. Because
+every time you change an MSGCTXT, the translator will have to review
+the translation of MSGID.
+
+ Finding a canonical MSGCTXT string that doesn't change over time can
+be hard. But you shouldn't use the file name or class name containing
+the `pgettext' call - because it is a common development task to rename
+a file or a class, and it shouldn't cause translator work. Also you
+shouldn't use a comment in the form of a complete English sentence as
+MSGCTXT - because orthography or grammar changes are often applied to
+such sentences, and again, it shouldn't force the translator to do a
+review.
+
+ The `p' in `pgettext' stands for "particular": `pgettext' fetches a
+particular translation of the MSGID.
+
+ const char *dpgettext (const char *domain_name,
+ const char *msgctxt, const char *msgid);
+ const char *dcpgettext (const char *domain_name,
+ const char *msgctxt, const char *msgid,
+ int category);
+
+ These are generalizations of `pgettext'. They behave similarly to
+`dgettext' and `dcgettext', respectively. The DOMAIN_NAME argument
+defines the translation domain. The CATEGORY argument allows to use
+another locale facet than `LC_MESSAGES'.
+
+ As as example consider the following fictional situation. A GUI
+program has a menu bar with the following entries:
+
+ +------------+------------+--------------------------------------+
+ | File | Printer | |
+ +------------+------------+--------------------------------------+
+ | Open | | Select |
+ | New | | Open |
+ +----------+ | Connect |
+ +----------+
+
+ To have the strings `File', `Printer', `Open', `New', `Select', and
+`Connect' translated there has to be at some point in the code a call
+to a function of the `gettext' family. But in two places the string
+passed into the function would be `Open'. The translations might not
+be the same and therefore we are in the dilemma described above.
+
+ What distinguishes the two places is the menu path from the menu
+root to the particular menu entries:
+
+ Menu|File
+ Menu|Printer
+ Menu|File|Open
+ Menu|File|New
+ Menu|Printer|Select
+ Menu|Printer|Open
+ Menu|Printer|Connect
+
+ The context is thus the menu path without its last part. So, the
+calls look like this:
+
+ pgettext ("Menu|", "File")
+ pgettext ("Menu|", "Printer")
+ pgettext ("Menu|File|", "Open")
+ pgettext ("Menu|File|", "New")
+ pgettext ("Menu|Printer|", "Select")
+ pgettext ("Menu|Printer|", "Open")
+ pgettext ("Menu|Printer|", "Connect")
+
+ Whether or not to use the `|' character at the end of the context is
+a matter of style.
+
+ For more complex cases, where the MSGCTXT or MSGID are not string
+literals, more general macros are available:
+
+ const char *pgettext_expr (const char *msgctxt, const char *msgid);
+ const char *dpgettext_expr (const char *domain_name,
+ const char *msgctxt, const char *msgid);
+ const char *dcpgettext_expr (const char *domain_name,
+ const char *msgctxt, const char *msgid,
+ int category);
+
+ Here MSGCTXT and MSGID can be arbitrary string-valued expressions.
+These macros are more general. But in the case that both argument
+expressions are string literals, the macros without the `_expr' suffix
+are more efficient.
+
+\1f
+File: gettext.info, Node: Plural forms, Next: Optimized gettext, Prev: Contexts, Up: gettext
-10.2.5 Additional functions for plural forms
+11.2.6 Additional functions for plural forms
--------------------------------------------
The functions of the `gettext' family described so far (and all the
many different plural forms exist for this language. The string
following `plural' is an expression which is using the C language
syntax. Exceptions are that no negative numbers are allowed, numbers
-must be decimal, and the only variable allowed is `n'. This expression
-will be evaluated whenever one of the functions `ngettext',
-`dngettext', or `dcngettext' is called. The numeric value passed to
-these functions is then substituted for all uses of the variable `n' in
-the expression. The resulting value then must be greater or equal to
-zero and smaller than the value given as the value of `nplurals'.
+must be decimal, and the only variable allowed is `n'. Spaces are
+allowed in the expression, but backslash-newlines are not; in the
+examples below the backslash-newlines are present for formatting
+purposes only. This expression will be evaluated whenever one of the
+functions `ngettext', `dngettext', or `dcngettext' is called. The
+numeric value passed to these functions is then substituted for all uses
+of the variable `n' in the expression. The resulting value then must
+be greater or equal to zero and smaller than the value given as the
+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
Celtic
Gaeilge (Irish)
+Three forms, special case for numbers ending in 00 or [2-9][0-9]
+ The header entry would be:
+
+ Plural-Forms: nplurals=3; \
+ plural=n==1 ? 0 : (n==0 || (n%100 > 0 && n%100 < 20)) ? 1 : 2;
+
+ Languages with this property include:
+
+ Romanic family
+ Romanian
+
Three forms, special case for numbers ending in 1[2-9]
The header entry would look like this:
<bug-glibc-manual@gnu.org>.
\1f
-File: gettext.info, Node: GUI program problems, Next: Optimized gettext, Prev: Plural forms, Up: gettext
-
-10.2.6 How to use `gettext' in GUI programs
--------------------------------------------
-
-One place where the `gettext' functions, if used normally, have big
-problems is within programs with graphical user interfaces (GUIs). The
-problem is that many of the strings which have to be translated are very
-short. They have to appear in pull-down menus which restricts the
-length. But strings which are not containing entire sentences or at
-least large fragments of a sentence may appear in more than one
-situation in the program but might have different translations. This is
-especially true for the one-word strings which are frequently used in
-GUI programs.
-
- As a consequence many people say that the `gettext' approach is
-wrong and instead `catgets' should be used which indeed does not have
-this problem. But there is a very simple and powerful method to handle
-these kind of problems with the `gettext' functions.
-
-As as example consider the following fictional situation. A GUI program
-has a menu bar with the following entries:
-
- +------------+------------+--------------------------------------+
- | File | Printer | |
- +------------+------------+--------------------------------------+
- | Open | | Select |
- | New | | Open |
- +----------+ | Connect |
- +----------+
-
- To have the strings `File', `Printer', `Open', `New', `Select', and
-`Connect' translated there has to be at some point in the code a call
-to a function of the `gettext' family. But in two places the string
-passed into the function would be `Open'. The translations might not
-be the same and therefore we are in the dilemma described above.
-
- One solution to this problem is to artificially enlengthen the
-strings to make them unambiguous. But what would the program do if no
-translation is available? The enlengthened string is not what should be
-printed. So we should use a little bit modified version of the
-functions.
-
- To enlengthen the strings a uniform method should be used. E.g., in
-the example above the strings could be chosen as
-
- Menu|File
- Menu|Printer
- Menu|File|Open
- Menu|File|New
- Menu|Printer|Select
- Menu|Printer|Open
- Menu|Printer|Connect
+File: gettext.info, Node: Optimized gettext, Prev: Plural forms, Up: gettext
- Now all the strings are different and if now instead of `gettext'
-the following little wrapper function is used, everything works just
-fine:
-
- char *
- sgettext (const char *msgid)
- {
- char *msgval = gettext (msgid);
- if (msgval == msgid)
- msgval = strrchr (msgid, '|') + 1;
- return msgval;
- }
-
- What this little function does is to recognize the case when no
-translation is available. This can be done very efficiently by a
-pointer comparison since the return value is the input value. If there
-is no translation we know that the input string is in the format we used
-for the Menu entries and therefore contains a `|' character. We simply
-search for the last occurrence of this character and return a pointer
-to the character following it. That's it!
-
- If one now consistently uses the enlengthened string form and
-replaces the `gettext' calls with calls to `sgettext' (this is normally
-limited to very few places in the GUI implementation) then it is
-possible to produce a program which can be internationalized.
-
- The other `gettext' functions (`dgettext', `dcgettext' and the
-`ngettext' equivalents) can and should have corresponding functions as
-well which look almost identical, except for the parameters and the
-call to the underlying function.
-
- Now there is of course the question why such functions do not exist
-in the GNU gettext package? There are two parts of the answer to this
-question.
-
- * They are easy to write and therefore can be provided by the
- project they are used in. This is not an answer by itself and
- must be seen together with the second part which is:
-
- * There is no way the gettext package can contain a version which
- can work everywhere. The problem is the selection of the
- character to separate the prefix from the actual string in the
- enlenghtened string. The examples above used `|' which is a quite
- good choice because it resembles a notation frequently used in
- this context and it also is a character not often used in message
- strings.
-
- But what if the character is used in message strings? Or if the
- chose character is not available in the character set on the
- machine one compiles (e.g., `|' is not required to exist for
- ISO C; this is why the `iso646.h' file exists in ISO C programming
- environments).
-
- There is only one more comment to be said. The wrapper function
-above requires that the translations strings are not enlengthened
-themselves. This is only logical. There is no need to disambiguate
-the strings (since they are never used as keys for a search) and one
-also saves quite some memory and disk space by doing this.
-
-\1f
-File: gettext.info, Node: Optimized gettext, Prev: GUI program problems, Up: gettext
-
-10.2.7 Optimization of the *gettext functions
+11.2.7 Optimization of the *gettext functions
---------------------------------------------
At this point of the discussion we should talk about an advantage of the
\1f
File: gettext.info, Node: Comparison, Next: Using libintl.a, Prev: gettext, Up: Programmers
-10.3 Comparing the Two Interfaces
+11.3 Comparing the Two Interfaces
=================================
The following discussion is perhaps a little bit colored. As said
\1f
File: gettext.info, Node: Using libintl.a, Next: gettext grok, Prev: Comparison, Up: Programmers
-10.4 Using libintl.a in own programs
+11.4 Using libintl.a in own programs
====================================
Starting with version 0.9.4 the library `libintl.h' should be
\1f
File: gettext.info, Node: gettext grok, Next: Temp Programmers, Prev: Using libintl.a, Up: Programmers
-10.5 Being a `gettext' grok
+11.5 Being a `gettext' grok
===========================
-To fully exploit the functionality of the GNU `gettext' library it is
-surely helpful to read the source code. But for those who don't want
+* NOTE: * This documentation section is outdated and needs to be
+revised.
+
+ To fully exploit the functionality of the GNU `gettext' library it
+is surely helpful to read the source code. But for those who don't want
to spend that much time in reading the (sometimes complicated) code here
is a list comments:
\1f
File: gettext.info, Node: Temp Programmers, Prev: gettext grok, Up: Programmers
-10.6 Temporary Notes for the Programmers Chapter
+11.6 Temporary Notes for the Programmers Chapter
================================================
+* NOTE: * This documentation section is outdated and needs to be
+revised.
+
* Menu:
* Temp Implementations:: Temporary - Two Possible Implementations
\1f
File: gettext.info, Node: Temp Implementations, Next: Temp catgets, Prev: Temp Programmers, Up: Temp Programmers
-10.6.1 Temporary - Two Possible Implementations
+11.6.1 Temporary - Two Possible Implementations
-----------------------------------------------
There are two competing methods for language independent messages: the
\1f
File: gettext.info, Node: Temp catgets, Next: Temp WSI, Prev: Temp Implementations, Up: Temp Programmers
-10.6.2 Temporary - About `catgets'
+11.6.2 Temporary - About `catgets'
----------------------------------
There have been a few discussions of late on the use of `catgets' as a
\1f
File: gettext.info, Node: Temp WSI, Next: Temp Notes, Prev: Temp catgets, Up: Temp Programmers
-10.6.3 Temporary - Why a single implementation
+11.6.3 Temporary - Why a single implementation
----------------------------------------------
Now it seems kind of wasteful to me to have two different systems
\1f
File: gettext.info, Node: Temp Notes, Prev: Temp WSI, Up: Temp Programmers
-10.6.4 Temporary - Notes
+11.6.4 Temporary - Notes
------------------------
X/Open agreed very late on the standard form so that many
\1f
File: gettext.info, Node: Translators, Next: Maintainers, Prev: Programmers, Up: Top
-11 The Translator's View
+12 The Translator's View
************************
* Menu:
\1f
File: gettext.info, Node: Trans Intro 0, Next: Trans Intro 1, Prev: Translators, Up: Translators
-11.1 Introduction 0
+12.1 Introduction 0
===================
-Free software is going international! The Translation Project is a way
-to get maintainers, translators and users all together, so free software
-will gradually become able to speak many native languages.
+* NOTE: * This documentation section is outdated and needs to be
+revised.
+
+ Free software is going international! The Translation Project is a
+way to get maintainers, translators and users all together, so free
+software will gradually become able to speak many native languages.
The GNU `gettext' tool set contains _everything_ maintainers need
for internationalizing their packages for messages. It also contains
\1f
File: gettext.info, Node: Trans Intro 1, Next: Discussions, Prev: Trans Intro 0, Up: Translators
-11.2 Introduction 1
+12.2 Introduction 1
===================
-This is now official, GNU is going international! Here is the
+* NOTE: * This documentation section is outdated and needs to be
+revised.
+
+ This is now official, GNU is going international! Here is the
announcement submitted for the January 1995 GNU Bulletin:
A handful of GNU packages have already been adapted and provided
\1f
File: gettext.info, Node: Discussions, Next: Organization, Prev: Trans Intro 1, Up: Translators
-11.3 Discussions
+12.3 Discussions
================
-Facing this internationalization effort, a few users expressed their
+* NOTE: * This documentation section is outdated and needs to be
+revised.
+
+ Facing this internationalization effort, a few users expressed their
concerns. Some of these doubts are presented and discussed, here.
* Smaller groups
\1f
File: gettext.info, Node: Organization, Next: Information Flow, Prev: Discussions, Up: Translators
-11.4 Organization
+12.4 Organization
=================
-On a larger scale, the true solution would be to organize some kind of
-fairly precise set up in which volunteers could participate. I gave
+* NOTE: * This documentation section is outdated and needs to be
+revised.
+
+ On a larger scale, the true solution would be to organize some kind
+of fairly precise set up in which volunteers could participate. I gave
some thought to this idea lately, and realize there will be some touchy
points. I thought of writing to Richard Stallman to launch such a
project, but feel it might be good to shake out the ideas between
\1f
File: gettext.info, Node: Central Coordination, Next: National Teams, Prev: Organization, Up: Organization
-11.4.1 Central Coordination
+12.4.1 Central Coordination
---------------------------
I also think GNU will need sooner than it thinks, that someone setup a
\1f
File: gettext.info, Node: National Teams, Next: Mailing Lists, Prev: Central Coordination, Up: Organization
-11.4.2 National Teams
+12.4.2 National Teams
---------------------
I suggest we look for volunteer coordinators/editors for individual
\1f
File: gettext.info, Node: Sub-Cultures, Next: Organizational Ideas, Prev: National Teams, Up: National Teams
-11.4.2.1 Sub-Cultures
+12.4.2.1 Sub-Cultures
.....................
Taking French for example, there are a few sub-cultures around computers
\1f
File: gettext.info, Node: Organizational Ideas, Prev: Sub-Cultures, Up: National Teams
-11.4.2.2 Organizational Ideas
+12.4.2.2 Organizational Ideas
.............................
I expect the next big changes after the official release. Please note
\1f
File: gettext.info, Node: Mailing Lists, Prev: National Teams, Up: Organization
-11.4.3 Mailing Lists
+12.4.3 Mailing Lists
--------------------
If we get any inquiries about GNU `gettext', send them on to:
\1f
File: gettext.info, Node: Information Flow, Next: Prioritizing messages, Prev: Organization, Up: Translators
-11.5 Information Flow
+12.5 Information Flow
=====================
-There will surely be some discussion about this messages after the
+* NOTE: * This documentation section is outdated and needs to be
+revised.
+
+ There will surely be some discussion about this messages after the
packages are finally released. If people now send you some proposals
for better messages, how do you proceed? Jim, please note that right
now, as I put forward nearly a dozen of localizable programs, I receive
\1f
File: gettext.info, Node: Prioritizing messages, Prev: Information Flow, Up: Translators
-11.6 Prioritizing messages: How to determine which messages to translate first
+12.6 Prioritizing messages: How to determine which messages to translate first
==============================================================================
A translator sometimes has only a limited amount of time per week to
$ msguniq $HOME/gettextlogused > missing.po
- The result is a PO file, but needs some preprocessing before the
-Emacs PO mode can be used with it. First, it is a multi-domain PO
-file, containing messages from many translation domains. Second, it
-lacks all translator comments and source references. Here is how to
-get a list of the affected translation domains:
+ The result is a PO file, but needs some preprocessing before a PO
+file editor can be used with it. First, it is a multi-domain PO file,
+containing messages from many translation domains. Second, it lacks
+all translator comments and source references. Here is how to get a
+list of the affected translation domains:
$ sed -n -e 's,^domain "\(.*\)"$,\1,p' < missing.po | sort | uniq
a fresh one if she's the first translator (see *Note Creating::). She
then uses the following commands to mark the not urgent messages as
"obsolete". (This doesn't mean that these messages - translated and
-untranslated ones - will go away. It simply means that Emacs PO mode
-will ignore them in the following editing session.)
+untranslated ones - will go away. It simply means that the PO file
+editor will ignore them in the following editing session.)
$ msggrep --domain=$domain missing.po | grep -v '^domain' \
> $domain-missing.po
$ msgattrib --set-obsolete --ignore-file $domain-missing.po $domain.$lang.po \
> $domain.$lang-urgent.po
- The she translates `$domain.$lang-urgent.po' by use of Emacs PO mode.
-(FIXME: I don't know whether `KBabel' and `gtranslator' also preserve
-obsolete messages, as they should.) Finally she restores the not
-urgent messages (with their earlier translations, for those which were
-already translated) through this command:
+ The she translates `$domain.$lang-urgent.po' by use of a PO file
+editor (*note Editing::). (FIXME: I don't know whether `KBabel' and
+`gtranslator' also preserve obsolete messages, as they should.)
+Finally she restores the not urgent messages (with their earlier
+translations, for those which were already translated) through this
+command:
$ msgmerge --no-fuzzy-matching $domain.$lang-urgent.po $package/po/$domain.pot \
> $domain.$lang.po
domain.
\1f
-File: gettext.info, Node: Maintainers, Next: Programming Languages, Prev: Translators, Up: Top
+File: gettext.info, Node: Maintainers, Next: Installers, Prev: Translators, Up: Top
-12 The Maintainer's View
+13 The Maintainer's View
************************
The maintainer of a package has many responsibilities. One of them is
\1f
File: gettext.info, Node: Flat and Non-Flat, Next: Prerequisites, Prev: Maintainers, Up: Maintainers
-12.1 Flat or Non-Flat Directory Structures
+13.1 Flat or Non-Flat Directory Structures
==========================================
Some free software packages are distributed as `tar' files which unpack
\1f
File: gettext.info, Node: Prerequisites, Next: gettextize Invocation, Prev: Flat and Non-Flat, Up: Maintainers
-12.2 Prerequisite Works
+13.2 Prerequisite Works
=======================
There are some works which are required for using GNU `gettext' in one
\1f
File: gettext.info, Node: gettextize Invocation, Next: Adjusting Files, Prev: Prerequisites, Up: Maintainers
-12.3 Invoking the `gettextize' Program
+13.3 Invoking the `gettextize' Program
======================================
The `gettextize' program is an interactive tool that helps the
option `--force' (`-f') is given, the `intl/' directory is emptied
first.
- 4. The files `config.rpath' and `mkinstalldirs' are copied into the
- directory containing configuration support files. It is needed by
- the `AM_GNU_GETTEXT' autoconf macro.
+ 4. The file `config.rpath' is copied into the directory containing
+ configuration support files. It is needed by the `AM_GNU_GETTEXT'
+ autoconf macro.
5. Only if the project is using GNU `automake': A set of `autoconf'
macro files is copied into the package's `autoconf' macro
not. But in any case, the maintainer should still read the section
*Note Adjusting Files:: after invoking `gettextize'.
+ In particular, if after using `gettexize', you get an error
+`AC_COMPILE_IFELSE was called before AC_GNU_SOURCE' or `AC_RUN_IFELSE
+was called before AC_GNU_SOURCE', you can fix it by modifying
+`configure.ac', as described in *Note configure.in::.
+
It is also important to understand that `gettextize' is not part of
the GNU build system, in the sense that it should not be invoked
automatically, and not be invoked by someone who doesn't assume the
\1f
File: gettext.info, Node: Adjusting Files, Next: autoconf macros, Prev: gettextize Invocation, Up: Maintainers
-12.4 Files You Must Create or Alter
+13.4 Files You Must Create or Alter
===================================
Besides files which are automatically added through `gettextize', there
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.14.4 distribution itself, or from the GNU `hello'
+`gettext' 0.15 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' packages, as they are
* po/POTFILES.in:: `POTFILES.in' in `po/'
* po/LINGUAS:: `LINGUAS' in `po/'
* po/Makevars:: `Makevars' in `po/'
+* po/Rules-*:: Extending `Makefile' in `po/'
* configure.in:: `configure.in' at top level
* config.guess:: `config.guess', `config.sub' at top level
* mkinstalldirs:: `mkinstalldirs' at top level
\1f
File: gettext.info, Node: po/POTFILES.in, Next: po/LINGUAS, Prev: Adjusting Files, Up: Adjusting Files
-12.4.1 `POTFILES.in' in `po/'
+13.4.1 `POTFILES.in' in `po/'
-----------------------------
The `po/' directory should receive a file named `POTFILES.in'. This
\1f
File: gettext.info, Node: po/LINGUAS, Next: po/Makevars, Prev: po/POTFILES.in, Up: Adjusting Files
-12.4.2 `LINGUAS' in `po/'
+13.4.2 `LINGUAS' in `po/'
-------------------------
The `po/' directory should also receive a file named `LINGUAS'. This
they are also installed by running `gettextize'.
\1f
-File: gettext.info, Node: po/Makevars, Next: configure.in, Prev: po/LINGUAS, Up: Adjusting Files
+File: gettext.info, Node: po/Makevars, Next: po/Rules-*, Prev: po/LINGUAS, Up: Adjusting Files
-12.4.3 `Makevars' in `po/'
+13.4.3 `Makevars' in `po/'
--------------------------
-The `po/' directory also has a file named `Makevars'. It can be left
-unmodified if your package has a single message domain and,
-accordingly, a single `po/' directory. Only packages which have
-multiple `po/' directories at different locations need to adjust the
-three variables defined in `Makevars'.
+The `po/' directory also has a file named `Makevars'. It contains
+variables that are specific to your project. `po/Makevars' gets
+inserted into the `po/Makefile' when the latter is created. The
+variables thus take effect when the POT file is created or updated, and
+when the message catalogs get installed.
+
+ The first three variables can be left unmodified if your package has
+a single message domain and, accordingly, a single `po/' directory.
+Only packages which have multiple `po/' directories at different
+locations need to adjust the three first variables defined in
+`Makevars'.
+
+\1f
+File: gettext.info, Node: po/Rules-*, Next: configure.in, Prev: po/Makevars, Up: Adjusting Files
+
+13.4.4 Extending `Makefile' in `po/'
+------------------------------------
- `po/Makevars' gets inserted into the `po/Makefile' when the latter
-is created. At the same time, all files called `Rules-*' in the `po/'
-directory get appended to the `po/Makefile'. They present an
-opportunity to add rules for special PO files to the Makefile, without
-needing to mess with `po/Makefile.in.in'.
+All files called `Rules-*' in the `po/' directory get appended to the
+`po/Makefile' when it is created. They present an opportunity to add
+rules for special PO files to the Makefile, without 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
useful only for command-line programs, not GUI programs. To enable it,
similarly add `en@boldquot' to the `po/LINGUAS' file.
+ Similarly, you can create rules for building message catalogs for the
+`sr@latin' locale - Serbian written with the Latin alphabet - from
+those for the `sr' locale - Serbian written with Cyrillic letters. See
+*Note msgfilter Invocation::.
+
\1f
-File: gettext.info, Node: configure.in, Next: config.guess, Prev: po/Makevars, Up: Adjusting Files
+File: gettext.info, Node: configure.in, Next: config.guess, Prev: po/Rules-*, Up: Adjusting Files
-12.4.4 `configure.in' at top level
+13.4.5 `configure.in' at top level
----------------------------------
`configure.in' or `configure.ac' - this is the source from which
This is done by a set of lines like these:
PACKAGE=gettext
- VERSION=0.14.4
+ VERSION=0.15
AC_DEFINE_UNQUOTED(PACKAGE, "$PACKAGE")
AC_DEFINE_UNQUOTED(VERSION, "$VERSION")
AC_SUBST(PACKAGE)
or, if you are using GNU `automake', by a line like this:
- AM_INIT_AUTOMAKE(gettext, 0.14.4)
+ AM_INIT_AUTOMAKE(gettext, 0.15)
Of course, you replace `gettext' with the name of your package,
- and `0.14.4' by its version numbers, exactly as they should appear
+ and `0.15' by its version numbers, exactly as they should appear
in the packaged `tar' file name of your distribution
- (`gettext-0.14.4.tar.gz', here).
+ (`gettext-0.15.tar.gz', here).
2. Check for internationalization support.
`intl/Makefile' to the `AC_OUTPUT' line.
+ If, after doing the recommended modifications, a command like
+`aclocal -I m4' or `autoconf' or `autoreconf' fails with a trace
+similar to this:
+
+ configure.ac:44: warning: AC_COMPILE_IFELSE was called before AC_GNU_SOURCE
+ ../../lib/autoconf/specific.m4:335: AC_GNU_SOURCE is expanded from...
+ m4/lock.m4:224: gl_LOCK is expanded from...
+ m4/gettext.m4:571: gt_INTL_SUBDIR_CORE is expanded from...
+ m4/gettext.m4:472: AM_INTL_SUBDIR is expanded from...
+ m4/gettext.m4:347: AM_GNU_GETTEXT is expanded from...
+ configure.ac:44: the top level
+ configure.ac:44: warning: AC_RUN_IFELSE was called before AC_GNU_SOURCE
+
+you need to add an explicit invocation of `AC_GNU_SOURCE' in the
+`configure.ac' file - after `AC_PROG_CC' but before `AM_GNU_GETTEXT',
+most likely very close to the `AC_PROG_CC' invocation. This is
+necessary because of ordering restrictions imposed by GNU autoconf.
+
\1f
File: gettext.info, Node: config.guess, Next: mkinstalldirs, Prev: configure.in, Up: Adjusting Files
-12.4.5 `config.guess', `config.sub' at top level
+13.4.6 `config.guess', `config.sub' at top level
------------------------------------------------
If you haven't suppressed the `intl/' subdirectory, you need to add the
Normally, `config.guess' and `config.sub' are put at the top level
of a distribution. But it is also possible to put them in a
subdirectory, altogether with other configuration support files like
-`install-sh', `ltconfig', `ltmain.sh', `mkinstalldirs' or `missing'.
-All you need to do, other than moving the files, is to add the
-following line to your `configure.in'.
+`install-sh', `ltconfig', `ltmain.sh' or `missing'. All you need to
+do, other than moving the files, is to add the following line to your
+`configure.in'.
AC_CONFIG_AUX_DIR([SUBDIR])
\1f
File: gettext.info, Node: mkinstalldirs, Next: aclocal, Prev: config.guess, Up: Adjusting Files
-12.4.6 `mkinstalldirs' at top level
+13.4.7 `mkinstalldirs' at top level
-----------------------------------
-If `gettextize' has not already done it, you need to add the GNU
-`mkinstalldirs' script to your distribution. It is needed because
-`mkdir -p' is not portable enough. You find this script in the GNU
-`automake' distribution.
-
- Normally, `mkinstalldirs' is put at the top level of a distribution.
-But it is also possible to put it in a subdirectory, altogether with
-other configuration support files like `install-sh', `ltconfig',
-`ltmain.sh' or `missing'. All you need to do, other than moving the
-files, is to add the following line to your `configure.in'.
-
- AC_CONFIG_AUX_DIR([SUBDIR])
+With earlier versions of GNU gettext, you needed to add the GNU
+`mkinstalldirs' script to your distribution. This is not needed any
+more. You can remove it if you not also using an automake version
+older than automake 1.9.
\1f
File: gettext.info, Node: aclocal, Next: acconfig, Prev: mkinstalldirs, Up: Adjusting Files
-12.4.7 `aclocal.m4' at top level
+13.4.8 `aclocal.m4' at top level
--------------------------------
If you do not have an `aclocal.m4' file in your distribution, the
simplest is to concatenate the files `codeset.m4', `gettext.m4',
`glibc2.m4', `glibc21.m4', `iconv.m4', `intdiv0.m4', `intmax.m4',
-`inttypes.m4', `inttypes_h.m4', `inttypes-pri.m4', `isc-posix.m4',
-`lcmessage.m4', `lib-ld.m4', `lib-link.m4', `lib-prefix.m4',
+`inttypes_h.m4', `inttypes-h.m4', `inttypes-pri.m4', `lcmessage.m4',
+`lib-ld.m4', `lib-link.m4', `lib-prefix.m4', `lock.m4',
`longdouble.m4', `longlong.m4', `printf-posix.m4', `progtest.m4',
`signed.m4', `size_max.m4', `stdint_h.m4', `uintmax_t.m4',
-`ulonglong.m4', `wchar_t.m4', `wint_t.m4', `xsize.m4' from GNU
-`gettext''s `m4/' directory into a single file. If you have suppressed
-the `intl/' directory, only `gettext.m4', `iconv.m4', `lib-ld.m4',
-`lib-link.m4', `lib-prefix.m4', `progtest.m4' need to be concatenated.
+`ulonglong.m4', `visibility.m4', `wchar_t.m4', `wint_t.m4', `xsize.m4'
+from GNU `gettext''s `m4/' directory into a single file. If you have
+suppressed the `intl/' directory, only `gettext.m4', `iconv.m4',
+`lib-ld.m4', `lib-link.m4', `lib-prefix.m4', `progtest.m4' need to be
+concatenated.
If you already have an `aclocal.m4' file, then you will have to
merge the said macro files into your `aclocal.m4'. Note that if you
\1f
File: gettext.info, Node: acconfig, Next: config.h.in, Prev: aclocal, Up: Adjusting Files
-12.4.8 `acconfig.h' at top level
+13.4.9 `acconfig.h' at top level
--------------------------------
Earlier GNU `gettext' releases required to put definitions for
\1f
File: gettext.info, Node: config.h.in, Next: Makefile, Prev: acconfig, Up: Adjusting Files
-12.4.9 `config.h.in' at top level
----------------------------------
+13.4.10 `config.h.in' at top level
+----------------------------------
The include file template that holds the C macros to be defined by
`configure' is usually called `config.h.in' and may be maintained
\1f
File: gettext.info, Node: Makefile, Next: src/Makefile, Prev: config.h.in, Up: Adjusting Files
-12.4.10 `Makefile.in' at top level
+13.4.11 `Makefile.in' at top level
----------------------------------
Here are a few modifications you need to make to your main, top-level
\1f
File: gettext.info, Node: src/Makefile, Next: lib/gettext.h, Prev: Makefile, Up: Adjusting Files
-12.4.11 `Makefile.in' in `src/'
+13.4.12 `Makefile.in' in `src/'
-------------------------------
Some of the modifications made in the main `Makefile.in' will also be
\1f
File: gettext.info, Node: lib/gettext.h, Prev: src/Makefile, Up: Adjusting Files
-12.4.12 `gettext.h' in `lib/'
+13.4.13 `gettext.h' in `lib/'
-----------------------------
Internationalization of packages, as provided by GNU `gettext', is
\1f
File: gettext.info, Node: autoconf macros, Next: CVS Issues, Prev: Adjusting Files, Up: Maintainers
-12.5 Autoconf macros for use in `configure.in'
+13.5 Autoconf macros for use in `configure.in'
==============================================
GNU `gettext' installs macros for use in a package's `configure.in' or
\1f
File: gettext.info, Node: AM_GNU_GETTEXT, Next: AM_GNU_GETTEXT_VERSION, Prev: autoconf macros, Up: autoconf macros
-12.5.1 AM_GNU_GETTEXT in `gettext.m4'
+13.5.1 AM_GNU_GETTEXT in `gettext.m4'
-------------------------------------
The `AM_GNU_GETTEXT' macro tests for the presence of the GNU gettext
\1f
File: gettext.info, Node: AM_GNU_GETTEXT_VERSION, Next: AM_PO_SUBDIRS, Prev: AM_GNU_GETTEXT, Up: autoconf macros
-12.5.2 AM_GNU_GETTEXT_VERSION in `gettext.m4'
+13.5.2 AM_GNU_GETTEXT_VERSION in `gettext.m4'
---------------------------------------------
The `AM_GNU_GETTEXT_VERSION' macro declares the version number of the
\1f
File: gettext.info, Node: AM_PO_SUBDIRS, Next: AM_ICONV, Prev: AM_GNU_GETTEXT_VERSION, Up: autoconf macros
-12.5.3 AM_PO_SUBDIRS in `po.m4'
+13.5.3 AM_PO_SUBDIRS in `po.m4'
-------------------------------
The `AM_PO_SUBDIRS' macro prepares the `po/' directories of the package
\1f
File: gettext.info, Node: AM_ICONV, Prev: AM_PO_SUBDIRS, Up: autoconf macros
-12.5.4 AM_ICONV in `iconv.m4'
+13.5.4 AM_ICONV in `iconv.m4'
-----------------------------
The `AM_ICONV' macro tests for the presence of the POSIX/XSI `iconv'
\1f
File: gettext.info, Node: CVS Issues, Next: Release Management, Prev: autoconf macros, Up: Maintainers
-12.6 Integrating with CVS
+13.6 Integrating with CVS
=========================
Many projects use CVS for distributed development, version control and
\1f
File: gettext.info, Node: Distributed CVS, Next: Files under CVS, Prev: CVS Issues, Up: CVS Issues
-12.6.1 Avoiding version mismatch in distributed development
+13.6.1 Avoiding version mismatch in distributed development
-----------------------------------------------------------
In a project development with multiple developers, using CVS, there
\1f
File: gettext.info, Node: Files under CVS, Next: autopoint Invocation, Prev: Distributed CVS, Up: CVS Issues
-12.6.2 Files to put under CVS version control
+13.6.2 Files to put under CVS version control
---------------------------------------------
There are basically three ways to deal with generated files in the
Instead, he adds to the `configure.in' or `configure.ac' a line of the
form
- AM_GNU_GETTEXT_VERSION(0.14.4)
+ AM_GNU_GETTEXT_VERSION(0.15)
and adds to the package's pre-build script an invocation of
`autopoint'. For everyone who checks out the CVS, this `autopoint'
\1f
File: gettext.info, Node: autopoint Invocation, Prev: Files under CVS, Up: CVS Issues
-12.6.3 Invoking the `autopoint' Program
+13.6.3 Invoking the `autopoint' Program
---------------------------------------
autopoint [OPTION]...
package, and copies the infrastructure files belonging to this version
into the package.
-12.6.3.1 Options
+13.6.3.1 Options
................
`-f'
instead only listed on standard output.
-12.6.3.2 Informative output
+13.6.3.2 Informative output
...........................
`--help'
`autopoint' supports the GNU `gettext' versions from 0.10.35 to the
-current one, 0.14.4. In order to apply `autopoint' to a package using
-a `gettext' version newer than 0.14.4, you need to install this same
+current one, 0.15. In order to apply `autopoint' to a package using a
+`gettext' version newer than 0.15, you need to install this same
version of GNU `gettext' at least.
In packages using GNU `automake', an invocation of `autopoint'
\1f
File: gettext.info, Node: Release Management, Prev: CVS Issues, Up: Maintainers
-12.7 Creating a Distribution Tarball
+13.7 Creating a Distribution Tarball
====================================
In projects that use GNU `automake', the usual commands for creating a
$ make distclean
\1f
-File: gettext.info, Node: Programming Languages, Next: Conclusion, Prev: Maintainers, Up: Top
+File: gettext.info, Node: Installers, Next: Programming Languages, Prev: Maintainers, Up: Top
+
+14 The Installer's and Distributor's View
+*****************************************
+
+By default, packages fully using GNU `gettext', internally, are
+installed in such a way that they to allow translation of messages. At
+_configuration_ time, those packages should automatically detect
+whether the underlying host system already provides the GNU `gettext'
+functions. If not, the GNU `gettext' library should be automatically
+prepared and used. Installers may use special options at configuration
+time for changing this behavior. The command `./configure
+--with-included-gettext' bypasses system `gettext' to use the included
+GNU `gettext' instead, while `./configure --disable-nls' 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
+with the package. However, the environment variable `LINGUAS' may be
+set, prior to configuration, to limit the installed set. `LINGUAS'
+should then contain a space separated list of two-letter codes, stating
+which languages are allowed.
+
+\1f
+File: gettext.info, Node: Programming Languages, Next: Conclusion, Prev: Installers, Up: Top
-13 Other Programming Languages
+15 Other Programming Languages
******************************
While the presentation of `gettext' focuses mostly on C and implicitly
\1f
File: gettext.info, Node: Language Implementors, Next: Programmers for other Languages, Prev: Programming Languages, Up: Programming Languages
-13.1 The Language Implementor's View
+15.1 The Language Implementor's View
====================================
All programming and scripting languages that have the notion of strings
written for yours, without actually translating the strings.
9. To help the programmer in the task of marking translatable strings,
- which is usually performed using the Emacs PO mode, you are
- welcome to contact the GNU `gettext' maintainers, so they can add
- support for your language to `po-mode.el'.
+ which is sometimes performed using the Emacs PO mode (*note
+ Marking::), you are welcome to contact the GNU `gettext'
+ maintainers, so they can add support for your language to
+ `po-mode.el'.
On the implementation side, three approaches are possible, with
different effects on portability and copyright:
\1f
File: gettext.info, Node: Programmers for other Languages, Next: Translators for other Languages, Prev: Language Implementors, Up: Programming Languages
-13.2 The Programmer's View
+15.2 The Programmer's View
==========================
For the programmer, the general procedure is the same as for the C
-language. The Emacs PO mode supports other languages, and the GNU
-`xgettext' string extractor recognizes other languages based on the
+language. The Emacs PO mode marking supports other languages, and the
+GNU `xgettext' string extractor recognizes other languages based on the
file extension or a command-line option. In some languages,
`setlocale' is not needed because it is already performed by the
underlying language runtime.
\1f
File: gettext.info, Node: Translators for other Languages, Next: Maintainers for other Languages, Prev: Programmers for other Languages, Up: Programming Languages
-13.3 The Translator's View
+15.3 The Translator's View
==========================
The translator works exactly as in the C language case. The only
* php-format:: PHP Format Strings
* gcc-internal-format:: GCC internal Format Strings
* qt-format:: Qt Format Strings
+* boost-format:: Boost Format Strings
\1f
File: gettext.info, Node: c-format, Next: objc-format, Prev: Translators for other Languages, Up: Translators for other Languages
-13.3.1 C Format Strings
+15.3.1 C Format Strings
-----------------------
C format strings are described in POSIX (IEEE P1003.1 2001), section
XSH 3 fprintf(),
`http://www.opengroup.org/onlinepubs/007904975/functions/fprintf.html'.
-See also the fprintf(3) manual page,
+See also the fprintf() manual page,
`http://www.linuxvalley.it/encyclopedia/ldp/manpage/man3/printf.3.php',
`http://informatik.fh-wuerzburg.de/student/i510/man/printf.html'.
\1f
File: gettext.info, Node: objc-format, Next: sh-format, Prev: c-format, Up: Translators for other Languages
-13.3.2 Objective C Format Strings
+15.3.2 Objective C Format Strings
---------------------------------
Objective C format strings are like C format strings. They support an
\1f
File: gettext.info, Node: sh-format, Next: python-format, Prev: objc-format, Up: Translators for other Languages
-13.3.3 Shell Format Strings
+15.3.3 Shell Format Strings
---------------------------
Shell format strings, as supported by GNU gettext and the `envsubst'
\1f
File: gettext.info, Node: python-format, Next: lisp-format, Prev: sh-format, Up: Translators for other Languages
-13.3.4 Python Format Strings
+15.3.4 Python Format Strings
----------------------------
Python format strings are described in Python Library reference /
\1f
File: gettext.info, Node: lisp-format, Next: elisp-format, Prev: python-format, Up: Translators for other Languages
-13.3.5 Lisp Format Strings
+15.3.5 Lisp Format Strings
--------------------------
Lisp format strings are described in the Common Lisp HyperSpec, chapter
\1f
File: gettext.info, Node: elisp-format, Next: librep-format, Prev: lisp-format, Up: Translators for other Languages
-13.3.6 Emacs Lisp Format Strings
+15.3.6 Emacs Lisp Format Strings
--------------------------------
Emacs Lisp format strings are documented in the Emacs Lisp reference,
\1f
File: gettext.info, Node: librep-format, Next: scheme-format, Prev: elisp-format, Up: Translators for other Languages
-13.3.7 librep Format Strings
+15.3.7 librep Format Strings
----------------------------
librep format strings are documented in the librep manual, section
\1f
File: gettext.info, Node: scheme-format, Next: smalltalk-format, Prev: librep-format, Up: Translators for other Languages
-13.3.8 Scheme Format Strings
+15.3.8 Scheme Format Strings
----------------------------
Scheme format strings are documented in the SLIB manual, section
\1f
File: gettext.info, Node: smalltalk-format, Next: java-format, Prev: scheme-format, Up: Translators for other Languages
-13.3.9 Smalltalk Format Strings
+15.3.9 Smalltalk Format Strings
-------------------------------
Smalltalk format strings are described in the GNU Smalltalk
\1f
File: gettext.info, Node: java-format, Next: csharp-format, Prev: smalltalk-format, Up: Translators for other Languages
-13.3.10 Java Format Strings
+15.3.10 Java Format Strings
---------------------------
Java format strings are described in the JDK documentation for class
\1f
File: gettext.info, Node: csharp-format, Next: awk-format, Prev: java-format, Up: Translators for other Languages
-13.3.11 C# Format Strings
+15.3.11 C# Format Strings
-------------------------
C# format strings are described in the .NET documentation for class
\1f
File: gettext.info, Node: awk-format, Next: object-pascal-format, Prev: csharp-format, Up: Translators for other Languages
-13.3.12 awk Format Strings
+15.3.12 awk Format Strings
--------------------------
awk format strings are described in the gawk documentation, section
\1f
File: gettext.info, Node: object-pascal-format, Next: ycp-format, Prev: awk-format, Up: Translators for other Languages
-13.3.13 Object Pascal Format Strings
+15.3.13 Object Pascal Format Strings
------------------------------------
Where is this documented?
\1f
File: gettext.info, Node: ycp-format, Next: tcl-format, Prev: object-pascal-format, Up: Translators for other Languages
-13.3.14 YCP Format Strings
+15.3.14 YCP Format Strings
--------------------------
YCP sformat strings are described in the libycp documentation
\1f
File: gettext.info, Node: tcl-format, Next: perl-format, Prev: ycp-format, Up: Translators for other Languages
-13.3.15 Tcl Format Strings
+15.3.15 Tcl Format Strings
--------------------------
Tcl format strings are described in the `format.n' manual page,
\1f
File: gettext.info, Node: perl-format, Next: php-format, Prev: tcl-format, Up: Translators for other Languages
-13.3.16 Perl Format Strings
+15.3.16 Perl Format Strings
---------------------------
There are two kinds format strings in Perl: those acceptable to the
\1f
File: gettext.info, Node: php-format, Next: gcc-internal-format, Prev: perl-format, Up: Translators for other Languages
-13.3.17 PHP Format Strings
+15.3.17 PHP Format Strings
--------------------------
PHP format strings are described in the documentation of the PHP
\1f
File: gettext.info, Node: gcc-internal-format, Next: qt-format, Prev: php-format, Up: Translators for other Languages
-13.3.18 GCC internal Format Strings
+15.3.18 GCC internal Format Strings
-----------------------------------
These format strings are used inside the GCC sources. In such a format
const/volatile qualifier.
\1f
-File: gettext.info, Node: qt-format, Prev: gcc-internal-format, Up: Translators for other Languages
+File: gettext.info, Node: qt-format, Next: boost-format, Prev: gcc-internal-format, Up: Translators for other Languages
-13.3.19 Qt Format Strings
+15.3.19 Qt Format Strings
-------------------------
Qt format strings are described in the documentation of the QString
directive consists of a `%' followed by a digit. The same directive
cannot occur more than once in a format string.
+\1f
+File: gettext.info, Node: boost-format, Prev: qt-format, Up: Translators for other Languages
+
+15.3.20 Boost Format Strings
+----------------------------
+
+Boost format strings are described in the documentation of the
+`boost::format' class, at
+`http://www.boost.org/libs/format/doc/format.html'. In summary, a
+directive has either the same syntax as in a C format string, such as
+`%1$+5d', or may be surrounded by vertical bars, such as `%|1$+5d|' or
+`%|1$+5|', or consists of just an argument number between percent
+signs, such as `%1%'.
+
\1f
File: gettext.info, Node: Maintainers for other Languages, Next: List of Programming Languages, Prev: Translators for other Languages, Up: Programming Languages
-13.4 The Maintainer's View
+15.4 The Maintainer's View
==========================
For the maintainer, the general procedure differs from the C language
\1f
File: gettext.info, Node: List of Programming Languages, Next: List of Data Formats, Prev: Maintainers for other Languages, Up: Programming Languages
-13.5 Individual Programming Languages
+15.5 Individual Programming Languages
=====================================
* Menu:
* C#:: C#
* gawk:: GNU awk
* Pascal:: Pascal - Free Pascal Compiler
-* wxWindows:: wxWindows library
+* wxWidgets:: wxWidgets library
* YCP:: YCP - YaST2 scripting language
* Tcl:: Tcl - Tk's scripting language
* Perl:: Perl
\1f
File: gettext.info, Node: C, Next: sh, Prev: List of Programming Languages, Up: List of Programming Languages
-13.5.1 C, C++, Objective C
+15.5.1 C, C++, Objective C
--------------------------
RPMs
The following examples are available in the `examples' directory:
`hello-c', `hello-c-gnome', `hello-c++', `hello-c++-qt',
-`hello-c++-kde', `hello-c++-gnome', `hello-objc', `hello-objc-gnustep',
-`hello-objc-gnome'.
+`hello-c++-kde', `hello-c++-gnome', `hello-c++-wxwidgets',
+`hello-objc', `hello-objc-gnustep', `hello-objc-gnome'.
\1f
File: gettext.info, Node: sh, Next: bash, Prev: C, Up: List of Programming Languages
-13.5.2 sh - Shell Script
+15.5.2 sh - Shell Script
------------------------
RPMs
\1f
File: gettext.info, Node: Preparing Shell Scripts, Next: gettext.sh, Prev: sh, Up: sh
-13.5.2.1 Preparing Shell Scripts for Internationalization
+15.5.2.1 Preparing Shell Scripts for Internationalization
.........................................................
Preparing a shell script for internationalization is conceptually
\1f
File: gettext.info, Node: gettext.sh, Next: gettext Invocation, Prev: Preparing Shell Scripts, Up: sh
-13.5.2.2 Contents of `gettext.sh'
+15.5.2.2 Contents of `gettext.sh'
.................................
`gettext.sh', contained in the run-time package of GNU gettext, provides
\1f
File: gettext.info, Node: gettext Invocation, Next: ngettext Invocation, Prev: gettext.sh, Up: sh
-13.5.2.3 Invoking the `gettext' program
+15.5.2.3 Invoking the `gettext' program
.......................................
gettext [OPTION] [[TEXTDOMAIN] MSGID]
\1f
File: gettext.info, Node: ngettext Invocation, Next: envsubst Invocation, Prev: gettext Invocation, Up: sh
-13.5.2.4 Invoking the `ngettext' program
+15.5.2.4 Invoking the `ngettext' program
........................................
ngettext [OPTION] [TEXTDOMAIN] MSGID MSGID-PLURAL COUNT
\1f
File: gettext.info, Node: envsubst Invocation, Next: eval_gettext Invocation, Prev: ngettext Invocation, Up: sh
-13.5.2.5 Invoking the `envsubst' program
+15.5.2.5 Invoking the `envsubst' program
........................................
envsubst [OPTION] [SHELL-FORMAT]
\1f
File: gettext.info, Node: eval_gettext Invocation, Next: eval_ngettext Invocation, Prev: envsubst Invocation, Up: sh
-13.5.2.6 Invoking the `eval_gettext' function
+15.5.2.6 Invoking the `eval_gettext' function
.............................................
eval_gettext MSGID
\1f
File: gettext.info, Node: eval_ngettext Invocation, Prev: eval_gettext Invocation, Up: sh
-13.5.2.7 Invoking the `eval_ngettext' function
+15.5.2.7 Invoking the `eval_ngettext' function
..............................................
eval_ngettext MSGID MSGID-PLURAL COUNT
\1f
File: gettext.info, Node: bash, Next: Python, Prev: sh, Up: List of Programming Languages
-13.5.3 bash - Bourne-Again Shell Script
+15.5.3 bash - Bourne-Again Shell Script
---------------------------------------
GNU `bash' 2.0 or newer has a special shorthand for translating a
\1f
File: gettext.info, Node: Python, Next: Common Lisp, Prev: bash, Up: List of Programming Languages
-13.5.4 Python
+15.5.4 Python
-------------
RPMs
\1f
File: gettext.info, Node: Common Lisp, Next: clisp C, Prev: Python, Up: List of Programming Languages
-13.5.5 GNU clisp - Common Lisp
+15.5.5 GNU clisp - Common Lisp
------------------------------
RPMs
\1f
File: gettext.info, Node: clisp C, Next: Emacs Lisp, Prev: Common Lisp, Up: List of Programming Languages
-13.5.6 GNU clisp C sources
+15.5.6 GNU clisp C sources
--------------------------
RPMs
\1f
File: gettext.info, Node: Emacs Lisp, Next: librep, Prev: clisp C, Up: List of Programming Languages
-13.5.7 Emacs Lisp
+15.5.7 Emacs Lisp
-----------------
RPMs
\1f
File: gettext.info, Node: librep, Next: Scheme, Prev: Emacs Lisp, Up: List of Programming Languages
-13.5.8 librep
+15.5.8 librep
-------------
RPMs
\1f
File: gettext.info, Node: Scheme, Next: Smalltalk, Prev: librep, Up: List of Programming Languages
-13.5.9 GNU guile - Scheme
+15.5.9 GNU guile - Scheme
-------------------------
RPMs
\1f
File: gettext.info, Node: Smalltalk, Next: Java, Prev: Scheme, Up: List of Programming Languages
-13.5.10 GNU Smalltalk
+15.5.10 GNU Smalltalk
---------------------
RPMs
\1f
File: gettext.info, Node: Java, Next: C#, Prev: Smalltalk, Up: List of Programming Languages
-13.5.11 Java
+15.5.11 Java
------------
RPMs
directory: `hello-java', `hello-java-awt', `hello-java-swing'.
Now, to make use of the API and define a shorthand for `getString',
-there are two idioms that you can choose from:
+there are three idioms that you can choose from:
+
+ * (This one assumes Java 1.5 or newer.) In a unique class of your
+ project, say `Util', define a static variable holding the
+ `ResourceBundle' instance and the shorthand:
+
+ private static ResourceBundle myResources =
+ ResourceBundle.getBundle("domain-name");
+ public static String _(String s) {
+ return myResources.getString(s);
+ }
+
+ All classes containing internationalized strings then contain
+
+ import static Util._;
+
+ and the shorthand is used like this:
+
+ System.out.println(_("Operation completed."));
* In a unique class of your project, say `Util', define a static
variable holding the `ResourceBundle' instance:
System.out.println(S._("Operation completed."));
- Which of the two idioms you choose, will depend on whether copying
-two lines of codes into every class is more acceptable in your project
-than a class with a single-letter name.
+ Which of the three idioms you choose, will depend on whether your
+project requires portability to Java versions prior to Java 1.5 and, if
+so, whether copying two lines of codes into every class is more
+acceptable in your project than a class with a single-letter name.
\1f
File: gettext.info, Node: C#, Next: gawk, Prev: Java, Up: List of Programming Languages
-13.5.12 C#
+15.5.12 C#
----------
RPMs
\1f
File: gettext.info, Node: gawk, Next: Pascal, Prev: C#, Up: List of Programming Languages
-13.5.13 GNU awk
+15.5.13 GNU awk
---------------
RPMs
An example is available in the `examples' directory: `hello-gawk'.
\1f
-File: gettext.info, Node: Pascal, Next: wxWindows, Prev: gawk, Up: List of Programming Languages
+File: gettext.info, Node: Pascal, Next: wxWidgets, Prev: gawk, Up: List of Programming Languages
-13.5.14 Pascal - Free Pascal Compiler
+15.5.14 Pascal - Free Pascal Compiler
-------------------------------------
RPMs
An example is available in the `examples' directory: `hello-pascal'.
\1f
-File: gettext.info, Node: wxWindows, Next: YCP, Prev: Pascal, Up: List of Programming Languages
+File: gettext.info, Node: wxWidgets, Next: YCP, Prev: Pascal, Up: List of Programming Languages
-13.5.15 wxWindows library
+15.5.15 wxWidgets library
-------------------------
RPMs
`xgettext'
Formatting with positions
- --
+ wxString::Format supports positions if and only if the system has
+ `wprintf()', `vswprintf()' functions and they support positions
+ according to POSIX.
Portability
fully portable
yes
\1f
-File: gettext.info, Node: YCP, Next: Tcl, Prev: wxWindows, Up: List of Programming Languages
+File: gettext.info, Node: YCP, Next: Tcl, Prev: wxWidgets, Up: List of Programming Languages
-13.5.16 YCP - YaST2 scripting language
+15.5.16 YCP - YaST2 scripting language
--------------------------------------
RPMs
\1f
File: gettext.info, Node: Tcl, Next: Perl, Prev: YCP, Up: List of Programming Languages
-13.5.17 Tcl - Tk's scripting language
+15.5.17 Tcl - Tk's scripting language
-------------------------------------
RPMs
\1f
File: gettext.info, Node: Perl, Next: PHP, Prev: Tcl, Up: List of Programming Languages
-13.5.18 Perl
+15.5.18 Perl
------------
RPMs
\1f
File: gettext.info, Node: General Problems, Next: Default Keywords, Up: Perl
-13.5.18.1 General Problems Parsing Perl Code
+15.5.18.1 General Problems Parsing Perl Code
............................................
It is often heard that only Perl can parse Perl. This is not true.
\1f
File: gettext.info, Node: Default Keywords, Next: Special Keywords, Prev: General Problems, Up: Perl
-13.5.18.2 Which keywords will xgettext look for?
+15.5.18.2 Which keywords will xgettext look for?
................................................
Unless you instruct `xgettext' otherwise by invoking it with one of the
\1f
File: gettext.info, Node: Special Keywords, Next: Quote-like Expressions, Prev: Default Keywords, Up: Perl
-13.5.18.3 How to Extract Hash Keys
+15.5.18.3 How to Extract Hash Keys
..................................
Translating messages at runtime is normally performed by looking up the
\1f
File: gettext.info, Node: Quote-like Expressions, Next: Interpolation I, Prev: Special Keywords, Up: Perl
-13.5.18.4 What are Strings And Quote-like Expressions?
+15.5.18.4 What are Strings And Quote-like Expressions?
......................................................
Perl offers a plethora of different string constructs. Those that can
\1f
File: gettext.info, Node: Interpolation I, Next: Interpolation II, Prev: Quote-like Expressions, Up: Perl
-13.5.18.5 Invalid Uses Of String Interpolation
+15.5.18.5 Invalid Uses Of String Interpolation
..............................................
Perl is capable of interpolating variables into strings. This offers
\1f
File: gettext.info, Node: Interpolation II, Next: Parentheses, Prev: Interpolation I, Up: Perl
-13.5.18.6 Valid Uses Of String Interpolation
+15.5.18.6 Valid Uses Of String Interpolation
............................................
Perl is often used to generate sources for other programming languages
\1f
File: gettext.info, Node: Parentheses, Next: Long Lines, Prev: Interpolation II, Up: Perl
-13.5.18.7 When To Use Parentheses
+15.5.18.7 When To Use Parentheses
.................................
In Perl, parentheses around function arguments are mostly optional.
\1f
File: gettext.info, Node: Long Lines, Next: Perl Pitfalls, Prev: Parentheses, Up: Perl
-13.5.18.8 How To Grok with Long Lines
+15.5.18.8 How To Grok with Long Lines
.....................................
The necessity of long messages can often lead to a cumbersome or
\1f
File: gettext.info, Node: Perl Pitfalls, Prev: Long Lines, Up: Perl
-13.5.18.9 Bugs, Pitfalls, And Things That Do Not Work
+15.5.18.9 Bugs, Pitfalls, And Things That Do Not Work
.....................................................
The foregoing sections should have proven that `xgettext' is quite
\1f
File: gettext.info, Node: PHP, Next: Pike, Prev: Perl, Up: List of Programming Languages
-13.5.19 PHP Hypertext Preprocessor
+15.5.19 PHP Hypertext Preprocessor
----------------------------------
RPMs
\1f
File: gettext.info, Node: Pike, Next: GCC-source, Prev: PHP, Up: List of Programming Languages
-13.5.20 Pike
+15.5.20 Pike
------------
RPMs
\1f
File: gettext.info, Node: GCC-source, Prev: Pike, Up: List of Programming Languages
-13.5.21 GNU Compiler Collection sources
+15.5.21 GNU Compiler Collection sources
---------------------------------------
RPMs
\1f
File: gettext.info, Node: List of Data Formats, Prev: List of Programming Languages, Up: Programming Languages
-13.6 Internationalizable Data
+15.6 Internationalizable Data
=============================
Here is a list of other data formats which can be internationalized
\1f
File: gettext.info, Node: POT, Next: RST, Prev: List of Data Formats, Up: List of Data Formats
-13.6.1 POT - Portable Object Template
+15.6.1 POT - Portable Object Template
-------------------------------------
RPMs
\1f
File: gettext.info, Node: RST, Next: Glade, Prev: POT, Up: List of Data Formats
-13.6.2 Resource String Table
+15.6.2 Resource String Table
----------------------------
RPMs
\1f
File: gettext.info, Node: Glade, Prev: RST, Up: List of Data Formats
-13.6.3 Glade - GNOME user interface description
+15.6.3 Glade - GNOME user interface description
-----------------------------------------------
RPMs
\1f
File: gettext.info, Node: Conclusion, Next: Language Codes, Prev: Programming Languages, Up: Top
-14 Concluding Remarks
+16 Concluding Remarks
*********************
We would like to conclude this GNU `gettext' manual by presenting an
\1f
File: gettext.info, Node: History, Next: References, Prev: Conclusion, Up: Conclusion
-14.1 History of GNU `gettext'
+16.1 History of GNU `gettext'
=============================
Internationalization concerns and algorithms have been informally and
\1f
File: gettext.info, Node: References, Prev: History, Up: Conclusion
-14.2 Related Readings
+16.2 Related Readings
=====================
-Eugene H. Dorr (`dorre@well.com') maintains an interesting bibliography
-on internationalization matters, called `Internationalization Reference
-List', which is available as:
+* NOTE: * This documentation section is outdated and needs to be
+revised.
+
+ Eugene H. Dorr (`dorre@well.com') maintains an interesting
+bibliography on internationalization matters, called
+`Internationalization Reference List', which is available as:
ftp://ftp.ora.com/pub/examples/nutshell/ujip/doc/i18n-books.txt
Michael Gschwind (`mike@vlsivie.tuwien.ac.at') maintains a
Zulu.
\1f
-File: gettext.info, Node: Country Codes, Next: Program Index, Prev: Language Codes, Up: Top
+File: gettext.info, Node: Country Codes, Next: Licenses, Prev: Language Codes, Up: Top
Appendix B Country Codes
************************
Zimbabwe.
\1f
-File: gettext.info, Node: Program Index, Next: Option Index, Prev: Country Codes, Up: Top
+File: gettext.info, Node: Licenses, Next: Program Index, Prev: Country Codes, Up: Top
+
+Appendix C Licenses
+*******************
+
+The files of this package are covered by the licenses indicated in each
+particular file or directory. Here is a summary:
+
+ * The `libintl' and `libasprintf' libraries are covered by the GNU
+ Library General Public License (LGPL). A copy of the license is
+ included in *Note GNU LGPL::.
+
+ * The executable programs of this package and the `libgettextpo'
+ library are covered by the GNU General Public License (GPL). A
+ copy of the license is included in *Note GNU GPL::.
+
+ * This manual is free documentation. It is dually licensed under the
+ GNU FDL and the GNU GPL. This means that you can redistribute this
+ manual under either of these two licenses, at your choice.
+ This manual is covered by the GNU FDL. Permission is granted to
+ copy, distribute and/or modify this document under the terms of the
+ GNU Free Documentation License (FDL), either version 1.2 of the
+ License, or (at your option) any later version published by the
+ Free Software Foundation (FSF); with no Invariant Sections, with no
+ Front-Cover Text, and with no Back-Cover Texts. A copy of the
+ license is included in *Note GNU FDL::.
+ This manual is covered by the GNU GPL. You can redistribute it
+ and/or modify it under the terms of the GNU General Public License
+ (GPL), either version 2 of the License, or (at your option) any
+ later version published by the Free Software Foundation (FSF). A
+ copy of the license is included in *Note GNU GPL::.
+
+* Menu:
+
+* GNU GPL:: GNU General Public License
+* GNU LGPL:: GNU Lesser General Public License
+* GNU FDL:: GNU Free Documentation License
+
+\1f
+File: gettext.info, Node: GNU GPL, Next: GNU LGPL, Up: Licenses
+
+C.1 GNU GENERAL PUBLIC LICENSE
+==============================
+
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+Preamble
+--------
+
+The licenses for most software are designed to take away your freedom
+to share and change it. By contrast, the GNU General Public License is
+intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it in
+new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software,
+and (2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains a
+ notice placed by the copyright holder saying it may be distributed
+ under the terms of this General Public License. The "Program",
+ below, refers to any such program or work, and a "work based on
+ the Program" means either the Program or any derivative work under
+ copyright law: that is to say, a work containing the Program or a
+ portion of it, either verbatim or with modifications and/or
+ translated into another language. (Hereinafter, translation is
+ included without limitation in the term "modification".) Each
+ licensee is addressed as "you".
+
+ Activities other than copying, distribution and modification are
+ not covered by this License; they are outside its scope. The act
+ of running the Program is not restricted, and the output from the
+ Program is covered only if its contents constitute a work based on
+ the Program (independent of having been made by running the
+ Program). Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+ source code as you receive it, in any medium, provided that you
+ conspicuously and appropriately publish on each copy an appropriate
+ copyright notice and disclaimer of warranty; keep intact all the
+ notices that refer to this License and to the absence of any
+ warranty; and give any other recipients of the Program a copy of
+ this License along with the Program.
+
+ You may charge a fee for the physical act of transferring a copy,
+ and you may at your option offer warranty protection in exchange
+ for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+ of it, thus forming a work based on the Program, and copy and
+ distribute such modifications or work under the terms of Section 1
+ above, provided that you also meet all of these conditions:
+
+ a. You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b. You must cause any work that you distribute or publish, that
+ in whole or in part contains or is derived from the Program
+ or any part thereof, to be licensed as a whole at no charge
+ to all third parties under the terms of this License.
+
+ c. If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display
+ an announcement including an appropriate copyright notice and
+ a notice that there is no warranty (or else, saying that you
+ provide a warranty) and that users may redistribute the
+ program under these conditions, and telling the user how to
+ view a copy of this License. (Exception: if the Program
+ itself is interactive but does not normally print such an
+ announcement, your work based on the Program is not required
+ to print an announcement.)
+
+ These requirements apply to the modified work as a whole. If
+ identifiable sections of that work are not derived from the
+ Program, and can be reasonably considered independent and separate
+ works in themselves, then this License, and its terms, do not
+ apply to those sections when you distribute them as separate
+ works. But when you distribute the same sections as part of a
+ whole which is a work based on the Program, the distribution of
+ the whole must be on the terms of this License, whose permissions
+ for other licensees extend to the entire whole, and thus to each
+ and every part regardless of who wrote it.
+
+ Thus, it is not the intent of this section to claim rights or
+ contest your rights to work written entirely by you; rather, the
+ intent is to exercise the right to control the distribution of
+ derivative or collective works based on the Program.
+
+ In addition, mere aggregation of another work not based on the
+ Program with the Program (or with a work based on the Program) on
+ a volume of a storage or distribution medium does not bring the
+ other work under the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+ under Section 2) in object code or executable form under the terms
+ of Sections 1 and 2 above provided that you also do one of the
+ following:
+
+ a. Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of
+ Sections 1 and 2 above on a medium customarily used for
+ software interchange; or,
+
+ b. Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a
+ medium customarily used for software interchange; or,
+
+ c. Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with
+ such an offer, in accord with Subsection b above.)
+
+ The source code for a work means the preferred form of the work for
+ making modifications to it. For an executable work, complete
+ source code means all the source code for all modules it contains,
+ plus any associated interface definition files, plus the scripts
+ used to control compilation and installation of the executable.
+ However, as a special exception, the source code distributed need
+ not include anything that is normally distributed (in either
+ source or binary form) with the major components (compiler,
+ kernel, and so on) of the operating system on which the executable
+ runs, unless that component itself accompanies the executable.
+
+ If distribution of executable or object code is made by offering
+ access to copy from a designated place, then offering equivalent
+ access to copy the source code from the same place counts as
+ distribution of the source code, even though third parties are not
+ compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+ except as expressly provided under this License. Any attempt
+ otherwise to copy, modify, sublicense or distribute the Program is
+ void, and will automatically terminate your rights under this
+ License. However, parties who have received copies, or rights,
+ from you under this License will not have their licenses
+ terminated so long as such parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+ signed it. However, nothing else grants you permission to modify
+ or distribute the Program or its derivative works. These actions
+ are prohibited by law if you do not accept this License.
+ Therefore, by modifying or distributing the Program (or any work
+ based on the Program), you indicate your acceptance of this
+ License to do so, and all its terms and conditions for copying,
+ distributing or modifying the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+ Program), the recipient automatically receives a license from the
+ original licensor to copy, distribute or modify the Program
+ subject to these terms and conditions. You may not impose any
+ further restrictions on the recipients' exercise of the rights
+ granted herein. You are not responsible for enforcing compliance
+ by third parties to this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+ infringement or for any other reason (not limited to patent
+ issues), conditions are imposed on you (whether by court order,
+ agreement or otherwise) that contradict the conditions of this
+ License, they do not excuse you from the conditions of this
+ License. If you cannot distribute so as to satisfy simultaneously
+ your obligations under this License and any other pertinent
+ obligations, then as a consequence you may not distribute the
+ Program at all. For example, if a patent license would not permit
+ royalty-free redistribution of the Program by all those who
+ receive copies directly or indirectly through you, then the only
+ way you could satisfy both it and this License would be to refrain
+ entirely from distribution of the Program.
+
+ If any portion of this section is held invalid or unenforceable
+ under any particular circumstance, the balance of the section is
+ intended to apply and the section as a whole is intended to apply
+ in other circumstances.
+
+ It is not the purpose of this section to induce you to infringe any
+ patents or other property right claims or to contest validity of
+ any such claims; this section has the sole purpose of protecting
+ the integrity of the free software distribution system, which is
+ implemented by public license practices. Many people have made
+ generous contributions to the wide range of software distributed
+ through that system in reliance on consistent application of that
+ system; it is up to the author/donor to decide if he or she is
+ willing to distribute software through any other system and a
+ licensee cannot impose that choice.
+
+ This section is intended to make thoroughly clear what is believed
+ to be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+ certain countries either by patents or by copyrighted interfaces,
+ the original copyright holder who places the Program under this
+ License may add an explicit geographical distribution limitation
+ excluding those countries, so that distribution is permitted only
+ in or among countries not thus excluded. In such case, this
+ License incorporates the limitation as if written in the body of
+ this License.
+
+ 9. The Free Software Foundation may publish revised and/or new
+ versions of the General Public License from time to time. Such
+ new versions will be similar in spirit to the present version, but
+ may differ in detail to address new problems or concerns.
+
+ Each version is given a distinguishing version number. If the
+ Program specifies a version number of this License which applies
+ to it and "any later version", you have the option of following
+ the terms and conditions either of that version or of any later
+ version published by the Free Software Foundation. If the Program
+ does not specify a version number of this License, you may choose
+ any version ever published by the Free Software Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+ programs whose distribution conditions are different, write to the
+ author to ask for permission. For software which is copyrighted
+ by the Free Software Foundation, write to the Free Software
+ Foundation; we sometimes make exceptions for this. Our decision
+ will be guided by the two goals of preserving the free status of
+ all derivatives of our free software and of promoting the sharing
+ and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO
+ WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
+ LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+ HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
+ WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT
+ NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
+ FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
+ QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+ PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY
+ SERVICING, REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+ WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY
+ MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE
+ LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
+ INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR
+ INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+ DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU
+ OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY
+ OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
+ ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+Appendix: How to Apply These Terms to Your New Programs
+-------------------------------------------------------
+
+If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these
+terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+ ONE LINE TO GIVE THE PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES.
+ Copyright (C) YYYY NAME OF AUTHOR
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+
+ Also add information on how to contact you by electronic and paper
+mail.
+
+ If the program is interactive, make it output a short notice like
+this when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) 19YY NAME OF AUTHOR
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+ The hypothetical commands `show w' and `show c' should show the
+appropriate parts of the General Public License. Of course, the
+commands you use may be called something other than `show w' and `show
+c'; they could even be mouse-clicks or menu items--whatever suits your
+program.
+
+ You should also get your employer (if you work as a programmer) or
+your school, if any, to sign a "copyright disclaimer" for the program,
+if necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ SIGNATURE OF TY COON, 1 April 1989
+ Ty Coon, President of Vice
+
+ This General Public License does not permit incorporating your
+program into proprietary programs. If your program is a subroutine
+library, you may consider it more useful to permit linking proprietary
+applications with the library. If this is what you want to do, use the
+GNU Library General Public License instead of this License.
+
+\1f
+File: gettext.info, Node: GNU LGPL, Next: GNU FDL, Prev: GNU GPL, Up: Licenses
+
+C.2 GNU LESSER GENERAL PUBLIC LICENSE
+=====================================
+
+ Version 2.1, February 1999
+
+ Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+ 51 Franklin St - Fifth Floor, Boston, MA 02110-1301, USA
+
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ [This is the first released version of the Lesser GPL. It also counts
+ as the successor of the GNU Library Public License, version 2, hence the
+ version number 2.1.]
+
+Preamble
+--------
+
+The licenses for most software are designed to take away your freedom
+to share and change it. By contrast, the GNU General Public Licenses
+are intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.
+
+ This license, the Lesser General Public License, applies to some
+specially designated software--typically libraries--of the Free
+Software Foundation and other authors who decide to use it. You can use
+it too, but we suggest you first think carefully about whether this
+license or the ordinary General Public License is the better strategy to
+use in any particular case, based on the explanations below.
+
+ When we speak of free software, we are referring to freedom of use,
+not price. Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of it
+in new free programs; and that you are informed that you can do these
+things.
+
+ To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights. These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+
+ For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it. And you must show them these terms so they know their rights.
+
+ We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+
+ To protect each distributor, we want to make it very clear that
+there is no warranty for the free library. Also, if the library is
+modified by someone else and passed on, the recipients should know that
+what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
+
+ Finally, software patents pose a constant threat to the existence of
+any free program. We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder. Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+
+ Most GNU software, including some libraries, is covered by the
+ordinary GNU General Public License. This license, the GNU Lesser
+General Public License, applies to certain designated libraries, and is
+quite different from the ordinary General Public License. We use this
+license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+ When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library. The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom. The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+
+ We call this license the "Lesser" General Public License because it
+does _Less_ to protect the user's freedom than the ordinary General
+Public License. It also provides other free software developers Less
+of an advantage over competing non-free programs. These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries. However, the Lesser license provides advantages in certain
+special circumstances.
+
+ For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it
+becomes a de-facto standard. To achieve this, non-free programs must be
+allowed to use the library. A more frequent case is that a free
+library does the same job as widely used non-free libraries. In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+
+ In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of free
+software. For example, permission to use the GNU C Library in non-free
+programs enables many more people to use the whole GNU operating
+system, as well as its variant, the GNU/Linux operating system.
+
+ Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run that
+program using a modified version of the Library.
+
+ The precise terms and conditions for copying, distribution and
+modification follow. Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library". The
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
+
+ GNU LESSER GENERAL PUBLIC LICENSE
+
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any software library or other
+ program which contains a notice placed by the copyright holder or
+ other authorized party saying it may be distributed under the
+ terms of this Lesser General Public License (also called "this
+ License"). Each licensee is addressed as "you".
+
+ A "library" means a collection of software functions and/or data
+ prepared so as to be conveniently linked with application programs
+ (which use some of those functions and data) to form executables.
+
+ The "Library", below, refers to any such software library or work
+ which has been distributed under these terms. A "work based on the
+ Library" means either the Library or any derivative work under
+ copyright law: that is to say, a work containing the Library or a
+ portion of it, either verbatim or with modifications and/or
+ translated straightforwardly into another language. (Hereinafter,
+ translation is included without limitation in the term
+ "modification".)
+
+ "Source code" for a work means the preferred form of the work for
+ making modifications to it. For a library, complete source code
+ means all the source code for all modules it contains, plus any
+ associated interface definition files, plus the scripts used to
+ control compilation and installation of the library.
+
+ Activities other than copying, distribution and modification are
+ not covered by this License; they are outside its scope. The act
+ of running a program using the Library is not restricted, and
+ output from such a program is covered only if its contents
+ constitute a work based on the Library (independent of the use of
+ the Library in a tool for writing it). Whether that is true
+ depends on what the Library does and what the program that uses
+ the Library does.
+
+ 1. You may copy and distribute verbatim copies of the Library's
+ complete source code as you receive it, in any medium, provided
+ that you conspicuously and appropriately publish on each copy an
+ appropriate copyright notice and disclaimer of warranty; keep
+ intact all the notices that refer to this License and to the
+ absence of any warranty; and distribute a copy of this License
+ along with the Library.
+
+ You may charge a fee for the physical act of transferring a copy,
+ and you may at your option offer warranty protection in exchange
+ for a fee.
+
+ 2. You may modify your copy or copies of the Library or any portion
+ of it, thus forming a work based on the Library, and copy and
+ distribute such modifications or work under the terms of Section 1
+ above, provided that you also meet all of these conditions:
+
+ a. The modified work must itself be a software library.
+
+ b. You must cause the files modified to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ c. You must cause the whole of the work to be licensed at no
+ charge to all third parties under the terms of this License.
+
+ d. If a facility in the modified Library refers to a function or
+ a table of data to be supplied by an application program that
+ uses the facility, other than as an argument passed when the
+ facility is invoked, then you must make a good faith effort
+ to ensure that, in the event an application does not supply
+ such function or table, the facility still operates, and
+ performs whatever part of its purpose remains meaningful.
+
+ (For example, a function in a library to compute square roots
+ has a purpose that is entirely well-defined independent of the
+ application. Therefore, Subsection 2d requires that any
+ application-supplied function or table used by this function
+ must be optional: if the application does not supply it, the
+ square root function must still compute square roots.)
+
+ These requirements apply to the modified work as a whole. If
+ identifiable sections of that work are not derived from the
+ Library, and can be reasonably considered independent and separate
+ works in themselves, then this License, and its terms, do not
+ apply to those sections when you distribute them as separate
+ works. But when you distribute the same sections as part of a
+ whole which is a work based on the Library, the distribution of
+ the whole must be on the terms of this License, whose permissions
+ for other licensees extend to the entire whole, and thus to each
+ and every part regardless of who wrote it.
+
+ Thus, it is not the intent of this section to claim rights or
+ contest your rights to work written entirely by you; rather, the
+ intent is to exercise the right to control the distribution of
+ derivative or collective works based on the Library.
+
+ In addition, mere aggregation of another work not based on the
+ Library with the Library (or with a work based on the Library) on
+ a volume of a storage or distribution medium does not bring the
+ other work under the scope of this License.
+
+ 3. You may opt to apply the terms of the ordinary GNU General Public
+ License instead of this License to a given copy of the Library.
+ To do this, you must alter all the notices that refer to this
+ License, so that they refer to the ordinary GNU General Public
+ License, version 2, instead of to this License. (If a newer
+ version than version 2 of the ordinary GNU General Public License
+ has appeared, then you can specify that version instead if you
+ wish.) Do not make any other change in these notices.
+
+ Once this change is made in a given copy, it is irreversible for
+ that copy, so the ordinary GNU General Public License applies to
+ all subsequent copies and derivative works made from that copy.
+
+ This option is useful when you wish to copy part of the code of
+ the Library into a program that is not a library.
+
+ 4. You may copy and distribute the Library (or a portion or
+ derivative of it, under Section 2) in object code or executable
+ form under the terms of Sections 1 and 2 above provided that you
+ accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software
+ interchange.
+
+ If distribution of object code is made by offering access to copy
+ from a designated place, then offering equivalent access to copy
+ the source code from the same place satisfies the requirement to
+ distribute the source code, even though third parties are not
+ compelled to copy the source along with the object code.
+
+ 5. A program that contains no derivative of any portion of the
+ Library, but is designed to work with the Library by being
+ compiled or linked with it, is called a "work that uses the
+ Library". Such a work, in isolation, is not a derivative work of
+ the Library, and therefore falls outside the scope of this License.
+
+ However, linking a "work that uses the Library" with the Library
+ creates an executable that is a derivative of the Library (because
+ it contains portions of the Library), rather than a "work that
+ uses the library". The executable is therefore covered by this
+ License. Section 6 states terms for distribution of such
+ executables.
+
+ When a "work that uses the Library" uses material from a header
+ file that is part of the Library, the object code for the work may
+ be a derivative work of the Library even though the source code is
+ not. Whether this is true is especially significant if the work
+ can be linked without the Library, or if the work is itself a
+ library. The threshold for this to be true is not precisely
+ defined by law.
+
+ If such an object file uses only numerical parameters, data
+ structure layouts and accessors, and small macros and small inline
+ functions (ten lines or less in length), then the use of the object
+ file is unrestricted, regardless of whether it is legally a
+ derivative work. (Executables containing this object code plus
+ portions of the Library will still fall under Section 6.)
+
+ Otherwise, if the work is a derivative of the Library, you may
+ distribute the object code for the work under the terms of Section
+ 6. Any executables containing that work also fall under Section 6,
+ whether or not they are linked directly with the Library itself.
+
+ 6. As an exception to the Sections above, you may also combine or
+ link a "work that uses the Library" with the Library to produce a
+ work containing portions of the Library, and distribute that work
+ under terms of your choice, provided that the terms permit
+ modification of the work for the customer's own use and reverse
+ engineering for debugging such modifications.
+
+ You must give prominent notice with each copy of the work that the
+ Library is used in it and that the Library and its use are covered
+ by this License. You must supply a copy of this License. If the
+ work during execution displays copyright notices, you must include
+ the copyright notice for the Library among them, as well as a
+ reference directing the user to the copy of this License. Also,
+ you must do one of these things:
+
+ a. Accompany the work with the complete corresponding
+ machine-readable source code for the Library including
+ whatever changes were used in the work (which must be
+ distributed under Sections 1 and 2 above); and, if the work
+ is an executable linked with the Library, with the complete
+ machine-readable "work that uses the Library", as object code
+ and/or source code, so that the user can modify the Library
+ and then relink to produce a modified executable containing
+ the modified Library. (It is understood that the user who
+ changes the contents of definitions files in the Library will
+ not necessarily be able to recompile the application to use
+ the modified definitions.)
+
+ b. Use a suitable shared library mechanism for linking with the
+ Library. A suitable mechanism is one that (1) uses at run
+ time a copy of the library already present on the user's
+ computer system, rather than copying library functions into
+ the executable, and (2) will operate properly with a modified
+ version of the library, if the user installs one, as long as
+ the modified version is interface-compatible with the version
+ that the work was made with.
+
+ c. Accompany the work with a written offer, valid for at least
+ three years, to give the same user the materials specified in
+ Subsection 6a, above, for a charge no more than the cost of
+ performing this distribution.
+
+ d. If distribution of the work is made by offering access to copy
+ from a designated place, offer equivalent access to copy the
+ above specified materials from the same place.
+
+ e. Verify that the user has already received a copy of these
+ materials or that you have already sent this user a copy.
+
+ For an executable, the required form of the "work that uses the
+ Library" must include any data and utility programs needed for
+ reproducing the executable from it. However, as a special
+ exception, the materials to be distributed need not include
+ anything that is normally distributed (in either source or binary
+ form) with the major components (compiler, kernel, and so on) of
+ the operating system on which the executable runs, unless that
+ component itself accompanies the executable.
+
+ It may happen that this requirement contradicts the license
+ restrictions of other proprietary libraries that do not normally
+ accompany the operating system. Such a contradiction means you
+ cannot use both them and the Library together in an executable
+ that you distribute.
+
+ 7. You may place library facilities that are a work based on the
+ Library side-by-side in a single library together with other
+ library facilities not covered by this License, and distribute
+ such a combined library, provided that the separate distribution
+ of the work based on the Library and of the other library
+ facilities is otherwise permitted, and provided that you do these
+ two things:
+
+ a. Accompany the combined library with a copy of the same work
+ based on the Library, uncombined with any other library
+ facilities. This must be distributed under the terms of the
+ Sections above.
+
+ b. Give prominent notice with the combined library of the fact
+ that part of it is a work based on the Library, and explaining
+ where to find the accompanying uncombined form of the same
+ work.
+
+ 8. You may not copy, modify, sublicense, link with, or distribute the
+ Library except as expressly provided under this License. Any
+ attempt otherwise to copy, modify, sublicense, link with, or
+ distribute the Library is void, and will automatically terminate
+ your rights under this License. However, parties who have
+ received copies, or rights, from you under this License will not
+ have their licenses terminated so long as such parties remain in
+ full compliance.
+
+ 9. You are not required to accept this License, since you have not
+ signed it. However, nothing else grants you permission to modify
+ or distribute the Library or its derivative works. These actions
+ are prohibited by law if you do not accept this License.
+ Therefore, by modifying or distributing the Library (or any work
+ based on the Library), you indicate your acceptance of this
+ License to do so, and all its terms and conditions for copying,
+ distributing or modifying the Library or works based on it.
+
+ 10. Each time you redistribute the Library (or any work based on the
+ Library), the recipient automatically receives a license from the
+ original licensor to copy, distribute, link with or modify the
+ Library subject to these terms and conditions. You may not impose
+ any further restrictions on the recipients' exercise of the rights
+ granted herein. You are not responsible for enforcing compliance
+ by third parties with this License.
+
+ 11. If, as a consequence of a court judgment or allegation of patent
+ infringement or for any other reason (not limited to patent
+ issues), conditions are imposed on you (whether by court order,
+ agreement or otherwise) that contradict the conditions of this
+ License, they do not excuse you from the conditions of this
+ License. If you cannot distribute so as to satisfy simultaneously
+ your obligations under this License and any other pertinent
+ obligations, then as a consequence you may not distribute the
+ Library at all. For example, if a patent license would not permit
+ royalty-free redistribution of the Library by all those who
+ receive copies directly or indirectly through you, then the only
+ way you could satisfy both it and this License would be to refrain
+ entirely from distribution of the Library.
+
+ If any portion of this section is held invalid or unenforceable
+ under any particular circumstance, the balance of the section is
+ intended to apply, and the section as a whole is intended to apply
+ in other circumstances.
+
+ It is not the purpose of this section to induce you to infringe any
+ patents or other property right claims or to contest validity of
+ any such claims; this section has the sole purpose of protecting
+ the integrity of the free software distribution system which is
+ implemented by public license practices. Many people have made
+ generous contributions to the wide range of software distributed
+ through that system in reliance on consistent application of that
+ system; it is up to the author/donor to decide if he or she is
+ willing to distribute software through any other system and a
+ licensee cannot impose that choice.
+
+ This section is intended to make thoroughly clear what is believed
+ to be a consequence of the rest of this License.
+
+ 12. If the distribution and/or use of the Library is restricted in
+ certain countries either by patents or by copyrighted interfaces,
+ the original copyright holder who places the Library under this
+ License may add an explicit geographical distribution limitation
+ excluding those countries, so that distribution is permitted only
+ in or among countries not thus excluded. In such case, this
+ License incorporates the limitation as if written in the body of
+ this License.
+
+ 13. The Free Software Foundation may publish revised and/or new
+ versions of the Lesser General Public License from time to time.
+ Such new versions will be similar in spirit to the present version,
+ but may differ in detail to address new problems or concerns.
+
+ Each version is given a distinguishing version number. If the
+ Library specifies a version number of this License which applies
+ to it and "any later version", you have the option of following
+ the terms and conditions either of that version or of any later
+ version published by the Free Software Foundation. If the Library
+ does not specify a license version number, you may choose any
+ version ever published by the Free Software Foundation.
+
+ 14. If you wish to incorporate parts of the Library into other free
+ programs whose distribution conditions are incompatible with these,
+ write to the author to ask for permission. For software which is
+ copyrighted by the Free Software Foundation, write to the Free
+ Software Foundation; we sometimes make exceptions for this. Our
+ decision will be guided by the two goals of preserving the free
+ status of all derivatives of our free software and of promoting
+ the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+ WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE
+ LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+ HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT
+ WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT
+ NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
+ FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
+ QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE
+ LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY
+ SERVICING, REPAIR OR CORRECTION.
+
+ 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+ WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY
+ MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE
+ LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
+ INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR
+ INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF
+ DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU
+ OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY
+ OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
+ ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+How to Apply These Terms to Your New Libraries
+----------------------------------------------
+
+If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change. You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of
+the ordinary General Public License).
+
+ To apply these terms, attach the following notices to the library.
+It is safest to attach them to the start of each source file to most
+effectively convey the exclusion of warranty; and each file should have
+at least the "copyright" line and a pointer to where the full notice is
+found.
+
+ ONE LINE TO GIVE THE LIBRARY'S NAME AND AN IDEA OF WHAT IT DOES.
+ Copyright (C) YEAR NAME OF AUTHOR
+
+ This library is free software; you can redistribute it and/or modify it
+ under the terms of the GNU Lesser General Public License as published by
+ the Free Software Foundation; either version 2.1 of the License, or (at
+ your option) any later version.
+
+ This library is distributed in the hope that it will be useful, but
+ WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Lesser General Public License for more details.
+
+ You should have received a copy of the GNU Lesser General Public
+ License along with this library; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
+ USA.
+
+ Also add information on how to contact you by electronic and paper
+mail.
+
+ You should also get your employer (if you work as a programmer) or
+your school, if any, to sign a "copyright disclaimer" for the library,
+if necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the library
+ `Frob' (a library for tweaking knobs) written by James Random Hacker.
+
+ SIGNATURE OF TY COON, 1 April 1990
+ Ty Coon, President of Vice
+
+ That's all there is to it!
+
+\1f
+File: gettext.info, Node: GNU FDL, Prev: GNU LGPL, Up: Licenses
+
+C.3 GNU Free Documentation License
+==================================
+
+ Version 1.2, November 2002
+
+ Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ 0. PREAMBLE
+
+ The purpose of this License is to make a manual, textbook, or other
+ functional and useful document "free" in the sense of freedom: to
+ assure everyone the effective freedom to copy and redistribute it,
+ with or without modifying it, either commercially or
+ noncommercially. Secondarily, this License preserves for the
+ author and publisher a way to get credit for their work, while not
+ being considered responsible for modifications made by others.
+
+ This License is a kind of "copyleft", which means that derivative
+ works of the document must themselves be free in the same sense.
+ It complements the GNU General Public License, which is a copyleft
+ license designed for free software.
+
+ We have designed this License in order to use it for manuals for
+ free software, because free software needs free documentation: a
+ free program should come with manuals providing the same freedoms
+ that the software does. But this License is not limited to
+ software manuals; it can be used for any textual work, regardless
+ of subject matter or whether it is published as a printed book.
+ We recommend this License principally for works whose purpose is
+ instruction or reference.
+
+ 1. APPLICABILITY AND DEFINITIONS
+
+ This License applies to any manual or other work, in any medium,
+ that contains a notice placed by the copyright holder saying it
+ can be distributed under the terms of this License. Such a notice
+ grants a world-wide, royalty-free license, unlimited in duration,
+ to use that work under the conditions stated herein. The
+ "Document", below, refers to any such manual or work. Any member
+ of the public is a licensee, and is addressed as "you". You
+ accept the license if you copy, modify or distribute the work in a
+ way requiring permission under copyright law.
+
+ A "Modified Version" of the Document means any work containing the
+ Document or a portion of it, either copied verbatim, or with
+ modifications and/or translated into another language.
+
+ A "Secondary Section" is a named appendix or a front-matter section
+ of the Document that deals exclusively with the relationship of the
+ publishers or authors of the Document to the Document's overall
+ subject (or to related matters) and contains nothing that could
+ fall directly within that overall subject. (Thus, if the Document
+ is in part a textbook of mathematics, a Secondary Section may not
+ explain any mathematics.) The relationship could be a matter of
+ historical connection with the subject or with related matters, or
+ of legal, commercial, philosophical, ethical or political position
+ regarding them.
+
+ The "Invariant Sections" are certain Secondary Sections whose
+ titles are designated, as being those of Invariant Sections, in
+ the notice that says that the Document is released under this
+ License. If a section does not fit the above definition of
+ Secondary then it is not allowed to be designated as Invariant.
+ The Document may contain zero Invariant Sections. If the Document
+ does not identify any Invariant Sections then there are none.
+
+ The "Cover Texts" are certain short passages of text that are
+ listed, as Front-Cover Texts or Back-Cover Texts, in the notice
+ that says that the Document is released under this License. A
+ Front-Cover Text may be at most 5 words, and a Back-Cover Text may
+ be at most 25 words.
+
+ A "Transparent" copy of the Document means a machine-readable copy,
+ represented in a format whose specification is available to the
+ general public, that is suitable for revising the document
+ straightforwardly with generic text editors or (for images
+ composed of pixels) generic paint programs or (for drawings) some
+ widely available drawing editor, and that is suitable for input to
+ text formatters or for automatic translation to a variety of
+ formats suitable for input to text formatters. A copy made in an
+ otherwise Transparent file format whose markup, or absence of
+ markup, has been arranged to thwart or discourage subsequent
+ modification by readers is not Transparent. An image format is
+ not Transparent if used for any substantial amount of text. A
+ copy that is not "Transparent" is called "Opaque".
+
+ Examples of suitable formats for Transparent copies include plain
+ ASCII without markup, Texinfo input format, LaTeX input format,
+ SGML or XML using a publicly available DTD, and
+ standard-conforming simple HTML, PostScript or PDF designed for
+ human modification. Examples of transparent image formats include
+ PNG, XCF and JPG. Opaque formats include proprietary formats that
+ can be read and edited only by proprietary word processors, SGML or
+ XML for which the DTD and/or processing tools are not generally
+ available, and the machine-generated HTML, PostScript or PDF
+ produced by some word processors for output purposes only.
+
+ The "Title Page" means, for a printed book, the title page itself,
+ plus such following pages as are needed to hold, legibly, the
+ material this License requires to appear in the title page. For
+ works in formats which do not have any title page as such, "Title
+ Page" means the text near the most prominent appearance of the
+ work's title, preceding the beginning of the body of the text.
+
+ A section "Entitled XYZ" means a named subunit of the Document
+ whose title either is precisely XYZ or contains XYZ in parentheses
+ following text that translates XYZ in another language. (Here XYZ
+ stands for a specific section name mentioned below, such as
+ "Acknowledgements", "Dedications", "Endorsements", or "History".)
+ To "Preserve the Title" of such a section when you modify the
+ Document means that it remains a section "Entitled XYZ" according
+ to this definition.
+
+ The Document may include Warranty Disclaimers next to the notice
+ which states that this License applies to the Document. These
+ Warranty Disclaimers are considered to be included by reference in
+ this License, but only as regards disclaiming warranties: any other
+ implication that these Warranty Disclaimers may have is void and
+ has no effect on the meaning of this License.
+
+ 2. VERBATIM COPYING
+
+ You may copy and distribute the Document in any medium, either
+ commercially or noncommercially, provided that this License, the
+ copyright notices, and the license notice saying this License
+ applies to the Document are reproduced in all copies, and that you
+ add no other conditions whatsoever to those of this License. You
+ may not use technical measures to obstruct or control the reading
+ or further copying of the copies you make or distribute. However,
+ you may accept compensation in exchange for copies. If you
+ distribute a large enough number of copies you must also follow
+ the conditions in section 3.
+
+ You may also lend copies, under the same conditions stated above,
+ and you may publicly display copies.
+
+ 3. COPYING IN QUANTITY
+
+ If you publish printed copies (or copies in media that commonly
+ have printed covers) of the Document, numbering more than 100, and
+ the Document's license notice requires Cover Texts, you must
+ enclose the copies in covers that carry, clearly and legibly, all
+ these Cover Texts: Front-Cover Texts on the front cover, and
+ Back-Cover Texts on the back cover. Both covers must also clearly
+ and legibly identify you as the publisher of these copies. The
+ front cover must present the full title with all words of the
+ title equally prominent and visible. You may add other material
+ on the covers in addition. Copying with changes limited to the
+ covers, as long as they preserve the title of the Document and
+ satisfy these conditions, can be treated as verbatim copying in
+ other respects.
+
+ If the required texts for either cover are too voluminous to fit
+ legibly, you should put the first ones listed (as many as fit
+ reasonably) on the actual cover, and continue the rest onto
+ adjacent pages.
+
+ If you publish or distribute Opaque copies of the Document
+ numbering more than 100, you must either include a
+ machine-readable Transparent copy along with each Opaque copy, or
+ state in or with each Opaque copy a computer-network location from
+ which the general network-using public has access to download
+ using public-standard network protocols a complete Transparent
+ copy of the Document, free of added material. If you use the
+ latter option, you must take reasonably prudent steps, when you
+ begin distribution of Opaque copies in quantity, to ensure that
+ this Transparent copy will remain thus accessible at the stated
+ location until at least one year after the last time you
+ distribute an Opaque copy (directly or through your agents or
+ retailers) of that edition to the public.
+
+ It is requested, but not required, that you contact the authors of
+ the Document well before redistributing any large number of
+ copies, to give them a chance to provide you with an updated
+ version of the Document.
+
+ 4. MODIFICATIONS
+
+ You may copy and distribute a Modified Version of the Document
+ under the conditions of sections 2 and 3 above, provided that you
+ release the Modified Version under precisely this License, with
+ the Modified Version filling the role of the Document, thus
+ licensing distribution and modification of the Modified Version to
+ whoever possesses a copy of it. In addition, you must do these
+ things in the Modified Version:
+
+ A. Use in the Title Page (and on the covers, if any) a title
+ distinct from that of the Document, and from those of
+ previous versions (which should, if there were any, be listed
+ in the History section of the Document). You may use the
+ same title as a previous version if the original publisher of
+ that version gives permission.
+
+ B. List on the Title Page, as authors, one or more persons or
+ entities responsible for authorship of the modifications in
+ the Modified Version, together with at least five of the
+ principal authors of the Document (all of its principal
+ authors, if it has fewer than five), unless they release you
+ from this requirement.
+
+ C. State on the Title page the name of the publisher of the
+ Modified Version, as the publisher.
+
+ D. Preserve all the copyright notices of the Document.
+
+ E. Add an appropriate copyright notice for your modifications
+ adjacent to the other copyright notices.
+
+ F. Include, immediately after the copyright notices, a license
+ notice giving the public permission to use the Modified
+ Version under the terms of this License, in the form shown in
+ the Addendum below.
+
+ G. Preserve in that license notice the full lists of Invariant
+ Sections and required Cover Texts given in the Document's
+ license notice.
+
+ H. Include an unaltered copy of this License.
+
+ I. Preserve the section Entitled "History", Preserve its Title,
+ and add to it an item stating at least the title, year, new
+ authors, and publisher of the Modified Version as given on
+ the Title Page. If there is no section Entitled "History" in
+ the Document, create one stating the title, year, authors,
+ and publisher of the Document as given on its Title Page,
+ then add an item describing the Modified Version as stated in
+ the previous sentence.
+
+ J. Preserve the network location, if any, given in the Document
+ for public access to a Transparent copy of the Document, and
+ likewise the network locations given in the Document for
+ previous versions it was based on. These may be placed in
+ the "History" section. You may omit a network location for a
+ work that was published at least four years before the
+ Document itself, or if the original publisher of the version
+ it refers to gives permission.
+
+ K. For any section Entitled "Acknowledgements" or "Dedications",
+ Preserve the Title of the section, and preserve in the
+ section all the substance and tone of each of the contributor
+ acknowledgements and/or dedications given therein.
+
+ L. Preserve all the Invariant Sections of the Document,
+ unaltered in their text and in their titles. Section numbers
+ or the equivalent are not considered part of the section
+ titles.
+
+ M. Delete any section Entitled "Endorsements". Such a section
+ may not be included in the Modified Version.
+
+ N. Do not retitle any existing section to be Entitled
+ "Endorsements" or to conflict in title with any Invariant
+ Section.
+
+ O. Preserve any Warranty Disclaimers.
+
+ If the Modified Version includes new front-matter sections or
+ appendices that qualify as Secondary Sections and contain no
+ material copied from the Document, you may at your option
+ designate some or all of these sections as invariant. To do this,
+ add their titles to the list of Invariant Sections in the Modified
+ Version's license notice. These titles must be distinct from any
+ other section titles.
+
+ You may add a section Entitled "Endorsements", provided it contains
+ nothing but endorsements of your Modified Version by various
+ parties--for example, statements of peer review or that the text
+ has been approved by an organization as the authoritative
+ definition of a standard.
+
+ You may add a passage of up to five words as a Front-Cover Text,
+ and a passage of up to 25 words as a Back-Cover Text, to the end
+ of the list of Cover Texts in the Modified Version. Only one
+ passage of Front-Cover Text and one of Back-Cover Text may be
+ added by (or through arrangements made by) any one entity. If the
+ Document already includes a cover text for the same cover,
+ previously added by you or by arrangement made by the same entity
+ you are acting on behalf of, you may not add another; but you may
+ replace the old one, on explicit permission from the previous
+ publisher that added the old one.
+
+ The author(s) and publisher(s) of the Document do not by this
+ License give permission to use their names for publicity for or to
+ assert or imply endorsement of any Modified Version.
+
+ 5. COMBINING DOCUMENTS
+
+ You may combine the Document with other documents released under
+ this License, under the terms defined in section 4 above for
+ modified versions, provided that you include in the combination
+ all of the Invariant Sections of all of the original documents,
+ unmodified, and list them all as Invariant Sections of your
+ combined work in its license notice, and that you preserve all
+ their Warranty Disclaimers.
+
+ The combined work need only contain one copy of this License, and
+ multiple identical Invariant Sections may be replaced with a single
+ copy. If there are multiple Invariant Sections with the same name
+ but different contents, make the title of each such section unique
+ by adding at the end of it, in parentheses, the name of the
+ original author or publisher of that section if known, or else a
+ unique number. Make the same adjustment to the section titles in
+ the list of Invariant Sections in the license notice of the
+ combined work.
+
+ In the combination, you must combine any sections Entitled
+ "History" in the various original documents, forming one section
+ Entitled "History"; likewise combine any sections Entitled
+ "Acknowledgements", and any sections Entitled "Dedications". You
+ must delete all sections Entitled "Endorsements."
+
+ 6. COLLECTIONS OF DOCUMENTS
+
+ You may make a collection consisting of the Document and other
+ documents released under this License, and replace the individual
+ copies of this License in the various documents with a single copy
+ that is included in the collection, provided that you follow the
+ rules of this License for verbatim copying of each of the
+ documents in all other respects.
+
+ You may extract a single document from such a collection, and
+ distribute it individually under this License, provided you insert
+ a copy of this License into the extracted document, and follow
+ this License in all other respects regarding verbatim copying of
+ that document.
+
+ 7. AGGREGATION WITH INDEPENDENT WORKS
+
+ A compilation of the Document or its derivatives with other
+ separate and independent documents or works, in or on a volume of
+ a storage or distribution medium, is called an "aggregate" if the
+ copyright resulting from the compilation is not used to limit the
+ legal rights of the compilation's users beyond what the individual
+ works permit. When the Document is included in an aggregate, this
+ License does not apply to the other works in the aggregate which
+ are not themselves derivative works of the Document.
+
+ If the Cover Text requirement of section 3 is applicable to these
+ copies of the Document, then if the Document is less than one half
+ of the entire aggregate, the Document's Cover Texts may be placed
+ on covers that bracket the Document within the aggregate, or the
+ electronic equivalent of covers if the Document is in electronic
+ form. Otherwise they must appear on printed covers that bracket
+ the whole aggregate.
+
+ 8. TRANSLATION
+
+ Translation is considered a kind of modification, so you may
+ distribute translations of the Document under the terms of section
+ 4. Replacing Invariant Sections with translations requires special
+ permission from their copyright holders, but you may include
+ translations of some or all Invariant Sections in addition to the
+ original versions of these Invariant Sections. You may include a
+ translation of this License, and all the license notices in the
+ Document, and any Warranty Disclaimers, provided that you also
+ include the original English version of this License and the
+ original versions of those notices and disclaimers. In case of a
+ disagreement between the translation and the original version of
+ this License or a notice or disclaimer, the original version will
+ prevail.
+
+ If a section in the Document is Entitled "Acknowledgements",
+ "Dedications", or "History", the requirement (section 4) to
+ Preserve its Title (section 1) will typically require changing the
+ actual title.
+
+ 9. TERMINATION
+
+ You may not copy, modify, sublicense, or distribute the Document
+ except as expressly provided for under this License. Any other
+ attempt to copy, modify, sublicense or distribute the Document is
+ void, and will automatically terminate your rights under this
+ License. However, parties who have received copies, or rights,
+ from you under this License will not have their licenses
+ terminated so long as such parties remain in full compliance.
+
+ 10. FUTURE REVISIONS OF THIS LICENSE
+
+ The Free Software Foundation may publish new, revised versions of
+ the GNU Free Documentation License from time to time. Such new
+ versions will be similar in spirit to the present version, but may
+ differ in detail to address new problems or concerns. See
+ `http://www.gnu.org/copyleft/'.
+
+ Each version of the License is given a distinguishing version
+ number. If the Document specifies that a particular numbered
+ version of this License "or any later version" applies to it, you
+ have the option of following the terms and conditions either of
+ that specified version or of any later version that has been
+ published (not as a draft) by the Free Software Foundation. If
+ the Document does not specify a version number of this License,
+ you may choose any version ever published (not as a draft) by the
+ Free Software Foundation.
+
+ADDENDUM: How to use this License for your documents
+----------------------------------------------------
+
+To use this License in a document you have written, include a copy of
+the License in the document and put the following copyright and license
+notices just after the title page:
+
+ Copyright (C) YEAR YOUR NAME.
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the GNU Free Documentation License, Version 1.2
+ or any later version published by the Free Software Foundation;
+ with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
+ Texts. A copy of the license is included in the section entitled ``GNU
+ Free Documentation License''.
+
+ If you have Invariant Sections, Front-Cover Texts and Back-Cover
+Texts, replace the "with...Texts." line with this:
+
+ with the Invariant Sections being LIST THEIR TITLES, with
+ the Front-Cover Texts being LIST, and with the Back-Cover Texts
+ being LIST.
+
+ If you have Invariant Sections without Cover Texts, or some other
+combination of the three, merge those two alternatives to suit the
+situation.
+
+ If your document contains nontrivial examples of program code, we
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License, to
+permit their use in free software.
+
+\1f
+File: gettext.info, Node: Program Index, Next: Option Index, Prev: Licenses, Up: Top
Program Index
*************
* msguniq: msguniq Invocation. (line 6)
* ngettext <1>: ngettext Invocation. (line 6)
* ngettext: sh. (line 19)
+* recode-sr-latin: msgfilter Invocation. (line 85)
* xgettext: xgettext Invocation. (line 6)
\1f
* --add-location, msgconv option: msgconv Invocation. (line 74)
* --add-location, msgen option: msgen Invocation. (line 70)
* --add-location, msgfilter option: msgfilter Invocation.
- (line 111)
-* --add-location, msggrep option: msggrep Invocation. (line 134)
+ (line 128)
+* --add-location, msggrep option: msggrep Invocation. (line 152)
* --add-location, msgmerge option: msgmerge Invocation. (line 135)
* --add-location, msguniq option: msguniq Invocation. (line 92)
-* --add-location, xgettext option: xgettext Invocation. (line 211)
+* --add-location, xgettext option: xgettext Invocation. (line 276)
* --alignment, msgfmt option: msgfmt Invocation. (line 209)
* --backup, msgmerge option: msgmerge Invocation. (line 65)
+* --boost, xgettext option: xgettext Invocation. (line 244)
* --c++, xgettext option: xgettext Invocation. (line 64)
* --check, msgfmt option: msgfmt Invocation. (line 146)
* --check-accelerators, msgfmt option: msgfmt Invocation. (line 187)
(line 71)
* --clear-obsolete, msgattrib option: msgattrib Invocation.
(line 77)
-* --comment, msggrep option: msggrep Invocation. (line 85)
+* --comment, msggrep option: msggrep Invocation. (line 93)
* --compendium, msgmerge option: msgmerge Invocation. (line 36)
* --copy, gettextize option: gettextize Invocation.
(line 40)
-* --copyright-holder, xgettext option: xgettext Invocation. (line 258)
+* --copyright-holder, xgettext option: xgettext Invocation. (line 323)
* --csharp, msgfmt option: msgfmt Invocation. (line 36)
* --csharp, msgunfmt option: msgunfmt Invocation. (line 19)
* --csharp-resources, msgfmt option: msgfmt Invocation. (line 40)
* --csharp-resources, msgunfmt option: msgunfmt Invocation. (line 23)
-* --debug, xgettext option: xgettext Invocation. (line 183)
+* --debug, xgettext option: xgettext Invocation. (line 248)
* --default-domain, xgettext option: xgettext Invocation. (line 36)
* --directory, msgattrib option: msgattrib Invocation.
(line 19)
* --directory, msgcomm option: msgcomm Invocation. (line 30)
* --directory, msgconv option: msgconv Invocation. (line 19)
* --directory, msgen option: msgen Invocation. (line 25)
-* --directory, msgexec option: msgexec Invocation. (line 42)
+* --directory, msgexec option: msgexec Invocation. (line 44)
* --directory, msgfilter option: msgfilter Invocation.
(line 20)
* --directory, msgfmt option: msgfmt Invocation. (line 18)
* --directory, msguniq option: msguniq Invocation. (line 26)
* --directory, xgettext option: xgettext Invocation. (line 24)
* --domain, gettext option: gettext Invocation. (line 16)
-* --domain, msggrep option: msggrep Invocation. (line 73)
+* --domain, msggrep option: msggrep Invocation. (line 77)
* --domain, ngettext option: ngettext Invocation. (line 15)
* --dry-run, autopoint option: autopoint Invocation.
(line 24)
(line 65)
* --exclude-file, xgettext option: xgettext Invocation. (line 92)
* --expression, msgfilter option: msgfilter Invocation.
- (line 68)
-* --extended-regexp, msggrep option: msggrep Invocation. (line 89)
+ (line 70)
+* --extended-regexp, msggrep option: msggrep Invocation. (line 101)
* --extract-all, xgettext option: xgettext Invocation. (line 106)
+* --extracted-comment, msggrep option: msggrep Invocation. (line 97)
* --file, msgfilter option: msgfilter Invocation.
- (line 72)
-* --file, msggrep option: msggrep Invocation. (line 101)
+ (line 74)
+* --file, msggrep option: msggrep Invocation. (line 113)
* --files-from, msgcat option: msgcat Invocation. (line 27)
* --files-from, msgcomm option: msgcomm Invocation. (line 25)
* --files-from, xgettext option: xgettext Invocation. (line 19)
-* --fixed-strings, msggrep option: msggrep Invocation. (line 93)
-* --flag, xgettext option: xgettext Invocation. (line 134)
+* --fixed-strings, msggrep option: msggrep Invocation. (line 105)
+* --flag, xgettext option: xgettext Invocation. (line 195)
* --force, autopoint option: autopoint Invocation.
(line 20)
* --force, gettextize option: gettextize Invocation.
* --force-po, msgconv option: msgconv Invocation. (line 64)
* --force-po, msgen option: msgen Invocation. (line 60)
* --force-po, msgfilter option: msgfilter Invocation.
- (line 97)
-* --force-po, msggrep option: msggrep Invocation. (line 125)
+ (line 114)
+* --force-po, msggrep option: msggrep Invocation. (line 143)
* --force-po, msgmerge option: msgmerge Invocation. (line 125)
* --force-po, msgunfmt option: msgunfmt Invocation. (line 108)
* --force-po, msguniq option: msguniq Invocation. (line 81)
-* --force-po, xgettext option: xgettext Invocation. (line 200)
-* --foreign-user, xgettext option: xgettext Invocation. (line 273)
+* --force-po, xgettext option: xgettext Invocation. (line 265)
+* --foreign-user, xgettext option: xgettext Invocation. (line 338)
* --from-code, xgettext option: xgettext Invocation. (line 74)
* --fuzzy, msgattrib option: msgattrib Invocation.
(line 88)
* --help, msgcomm option: msgcomm Invocation. (line 143)
* --help, msgconv option: msgconv Invocation. (line 119)
* --help, msgen option: msgen Invocation. (line 115)
-* --help, msgexec option: msgexec Invocation. (line 67)
+* --help, msgexec option: msgexec Invocation. (line 69)
* --help, msgfilter option: msgfilter Invocation.
- (line 156)
+ (line 173)
* --help, msgfmt option: msgfmt Invocation. (line 222)
-* --help, msggrep option: msggrep Invocation. (line 177)
+* --help, msggrep option: msggrep Invocation. (line 195)
* --help, msginit option: msginit Invocation. (line 90)
* --help, msgmerge option: msgmerge Invocation. (line 180)
* --help, msgunfmt option: msgunfmt Invocation. (line 153)
* --help, msguniq option: msguniq Invocation. (line 137)
* --help, ngettext option: ngettext Invocation. (line 31)
-* --help, xgettext option: xgettext Invocation. (line 319)
-* --ignore-case, msggrep option: msggrep Invocation. (line 105)
+* --help, xgettext option: xgettext Invocation. (line 384)
+* --ignore-case, msggrep option: msggrep Invocation. (line 117)
* --ignore-file, msgattrib option: msgattrib Invocation.
(line 84)
* --indent, msgattrib option: msgattrib Invocation.
* --indent, msgconv option: msgconv Invocation. (line 68)
* --indent, msgen option: msgen Invocation. (line 64)
* --indent, msgfilter option: msgfilter Invocation.
- (line 100)
-* --indent, msggrep option: msggrep Invocation. (line 128)
+ (line 117)
+* --indent, msggrep option: msggrep Invocation. (line 146)
* --indent, msgmerge option: msgmerge Invocation. (line 129)
* --indent, msgunfmt option: msgunfmt Invocation. (line 112)
* --indent, msguniq option: msguniq Invocation. (line 85)
-* --indent, xgettext option: xgettext Invocation. (line 204)
-* --input, msgexec option: msgexec Invocation. (line 38)
+* --indent, xgettext option: xgettext Invocation. (line 269)
+* --input, msgexec option: msgexec Invocation. (line 40)
* --input, msgfilter option: msgfilter Invocation.
(line 16)
* --input, msginit option: msginit Invocation. (line 16)
* --intl, gettextize option: gettextize Invocation.
(line 51)
+* --invert-match, msggrep option: msggrep Invocation. (line 121)
* --java, msgfmt option: msgfmt Invocation. (line 30)
* --java, msgunfmt option: msgunfmt Invocation. (line 16)
* --java2, msgfmt option: msgfmt Invocation. (line 33)
* --join-existing, xgettext option: xgettext Invocation. (line 88)
* --keep-header, msgfilter option: msgfilter Invocation.
- (line 103)
+ (line 120)
* --keyword, xgettext option: xgettext Invocation. (line 114)
* --language, xgettext option: xgettext Invocation. (line 56)
* --less-than, msgcat option: msgcat Invocation. (line 55)
* --locale, msgfmt option: msgfmt Invocation. (line 79)
* --locale, msginit option: msginit Invocation. (line 52)
* --locale, msgunfmt option: msgunfmt Invocation. (line 47)
-* --location, msggrep option: msggrep Invocation. (line 68)
+* --location, msggrep option: msggrep Invocation. (line 72)
* --more-than, msgcat option: msgcat Invocation. (line 60)
* --more-than, msgcomm option: msgcomm Invocation. (line 58)
-* --msgid, msggrep option: msggrep Invocation. (line 77)
-* --msgid-bugs-address, xgettext option: xgettext Invocation. (line 279)
-* --msgstr, msggrep option: msggrep Invocation. (line 81)
-* --msgstr-prefix, xgettext option: xgettext Invocation. (line 307)
-* --msgstr-suffix, xgettext option: xgettext Invocation. (line 311)
+* --msgctxt, msggrep option: msggrep Invocation. (line 81)
+* --msgid, msggrep option: msggrep Invocation. (line 85)
+* --msgid-bugs-address, xgettext option: xgettext Invocation. (line 344)
+* --msgstr, msggrep option: msggrep Invocation. (line 89)
+* --msgstr-prefix, xgettext option: xgettext Invocation. (line 372)
+* --msgstr-suffix, xgettext option: xgettext Invocation. (line 376)
* --multi-domain, msgcmp option: msgcmp Invocation. (line 36)
* --multi-domain, msgmerge option: msgmerge Invocation. (line 101)
* --no-changelog, gettextize option: gettextize Invocation.
* --no-location, msgconv option: msgconv Invocation. (line 71)
* --no-location, msgen option: msgen Invocation. (line 67)
* --no-location, msgfilter option: msgfilter Invocation.
- (line 108)
-* --no-location, msggrep option: msggrep Invocation. (line 131)
+ (line 125)
+* --no-location, msggrep option: msggrep Invocation. (line 149)
* --no-location, msgmerge option: msgmerge Invocation. (line 132)
* --no-location, msguniq option: msguniq Invocation. (line 88)
-* --no-location, xgettext option: xgettext Invocation. (line 207)
+* --no-location, xgettext option: xgettext Invocation. (line 272)
* --no-obsolete, msgattrib option: msgattrib Invocation.
(line 53)
* --no-translator, msginit option: msginit Invocation. (line 58)
* --no-wrap, msgconv option: msgconv Invocation. (line 99)
* --no-wrap, msgen option: msgen Invocation. (line 95)
* --no-wrap, msgfilter option: msgfilter Invocation.
- (line 136)
-* --no-wrap, msggrep option: msggrep Invocation. (line 159)
+ (line 153)
+* --no-wrap, msggrep option: msggrep Invocation. (line 177)
* --no-wrap, msginit option: msginit Invocation. (line 79)
* --no-wrap, msgmerge option: msgmerge Invocation. (line 160)
* --no-wrap, msgunfmt option: msgunfmt Invocation. (line 137)
* --no-wrap, msguniq option: msguniq Invocation. (line 117)
-* --no-wrap, xgettext option: xgettext Invocation. (line 235)
+* --no-wrap, xgettext option: xgettext Invocation. (line 300)
* --obsolete, msgattrib option: msgattrib Invocation.
(line 92)
* --omit-header, msgcomm option: msgcomm Invocation. (line 135)
-* --omit-header, xgettext option: xgettext Invocation. (line 250)
+* --omit-header, xgettext option: xgettext Invocation. (line 315)
* --only-file, msgattrib option: msgattrib Invocation.
(line 80)
* --only-fuzzy, msgattrib option: msgattrib Invocation.
* --properties-input, msgcomm option: msgcomm Invocation. (line 72)
* --properties-input, msgconv option: msgconv Invocation. (line 52)
* --properties-input, msgen option: msgen Invocation. (line 48)
-* --properties-input, msgexec option: msgexec Invocation. (line 54)
+* --properties-input, msgexec option: msgexec Invocation. (line 56)
* --properties-input, msgfilter option: msgfilter Invocation.
- (line 85)
+ (line 102)
* --properties-input, msgfmt option: msgfmt Invocation. (line 133)
-* --properties-input, msggrep option: msggrep Invocation. (line 113)
+* --properties-input, msggrep option: msggrep Invocation. (line 131)
* --properties-input, msginit option: msginit Invocation. (line 39)
* --properties-input, msgmerge option: msgmerge Invocation. (line 113)
* --properties-input, msguniq option: msguniq Invocation. (line 61)
* --properties-output, msgconv option: msgconv Invocation. (line 83)
* --properties-output, msgen option: msgen Invocation. (line 79)
* --properties-output, msgfilter option: msgfilter Invocation.
- (line 120)
-* --properties-output, msggrep option: msggrep Invocation. (line 143)
+ (line 137)
+* --properties-output, msggrep option: msggrep Invocation. (line 161)
* --properties-output, msginit option: msginit Invocation. (line 63)
* --properties-output, msgmerge option: msgmerge Invocation. (line 144)
* --properties-output, msgunfmt option: msgunfmt Invocation. (line 121)
* --properties-output, msguniq option: msguniq Invocation. (line 101)
-* --properties-output, xgettext option: xgettext Invocation. (line 219)
+* --properties-output, xgettext option: xgettext Invocation. (line 284)
* --qt, msgfmt option: msgfmt Invocation. (line 46)
-* --qt, xgettext option: xgettext Invocation. (line 179)
+* --qt, xgettext option: xgettext Invocation. (line 240)
* --quiet, msgfilter option: msgfilter Invocation.
- (line 77)
+ (line 79)
* --quiet, msgmerge option: msgmerge Invocation. (line 193)
-* --regexp=, msggrep option: msggrep Invocation. (line 97)
+* --regexp=, msggrep option: msggrep Invocation. (line 109)
* --repeated, msguniq option: msguniq Invocation. (line 49)
* --resource, msgfmt option: msgfmt Invocation. (line 75)
* --resource, msgunfmt option: msgunfmt Invocation. (line 43)
* --set-obsolete, msgattrib option: msgattrib Invocation.
(line 74)
* --silent, msgfilter option: msgfilter Invocation.
- (line 77)
+ (line 79)
* --silent, msgmerge option: msgmerge Invocation. (line 193)
* --sort-by-file, msgattrib option: msgattrib Invocation.
(line 161)
* --sort-by-file, msgconv option: msgconv Invocation. (line 111)
* --sort-by-file, msgen option: msgen Invocation. (line 107)
* --sort-by-file, msgfilter option: msgfilter Invocation.
- (line 148)
-* --sort-by-file, msggrep option: msggrep Invocation. (line 169)
+ (line 165)
+* --sort-by-file, msggrep option: msggrep Invocation. (line 187)
* --sort-by-file, msgmerge option: msgmerge Invocation. (line 172)
* --sort-by-file, msguniq option: msguniq Invocation. (line 129)
-* --sort-by-file, xgettext option: xgettext Invocation. (line 247)
+* --sort-by-file, xgettext option: xgettext Invocation. (line 312)
* --sort-output, msgattrib option: msgattrib Invocation.
(line 156)
* --sort-output, msgcat option: msgcat Invocation. (line 137)
* --sort-output, msgconv option: msgconv Invocation. (line 106)
* --sort-output, msgen option: msgen Invocation. (line 102)
* --sort-output, msgfilter option: msgfilter Invocation.
- (line 143)
-* --sort-output, msggrep option: msggrep Invocation. (line 165)
+ (line 160)
+* --sort-output, msggrep option: msggrep Invocation. (line 183)
* --sort-output, msgmerge option: msgmerge Invocation. (line 167)
* --sort-output, msgunfmt option: msgunfmt Invocation. (line 144)
* --sort-output, msguniq option: msguniq Invocation. (line 124)
-* --sort-output, xgettext option: xgettext Invocation. (line 242)
+* --sort-output, xgettext option: xgettext Invocation. (line 307)
* --statistics, msgfmt option: msgfmt Invocation. (line 229)
* --strict, msgattrib option: msgattrib Invocation.
(line 127)
* --strict, msgconv option: msgconv Invocation. (line 77)
* --strict, msgen option: msgen Invocation. (line 73)
* --strict, msgfilter option: msgfilter Invocation.
- (line 114)
+ (line 131)
* --strict, msgfmt option: msgfmt Invocation. (line 57)
-* --strict, msggrep option: msggrep Invocation. (line 137)
+* --strict, msggrep option: msggrep Invocation. (line 155)
* --strict, msgmerge option: msgmerge Invocation. (line 138)
* --strict, msgunfmt option: msgunfmt Invocation. (line 115)
* --strict, msguniq option: msguniq Invocation. (line 95)
-* --strict, xgettext option: xgettext Invocation. (line 214)
+* --strict, xgettext option: xgettext Invocation. (line 279)
* --stringtable-input, msgattrib option: msgattrib Invocation.
(line 105)
* --stringtable-input, msgcat option: msgcat Invocation. (line 78)
* --stringtable-input, msgcmp option: msgcmp Invocation. (line 48)
* --stringtable-input, msgcomm option: msgcomm Invocation. (line 76)
* --stringtable-input, msgen option: msgen Invocation. (line 52)
-* --stringtable-input, msgexec option: msgexec Invocation. (line 58)
+* --stringtable-input, msgexec option: msgexec Invocation. (line 60)
* --stringtable-input, msgfilter option: msgfilter Invocation.
- (line 89)
+ (line 106)
* --stringtable-input, msgfmt option: msgfmt Invocation. (line 137)
-* --stringtable-input, msggrep option: msggrep Invocation. (line 117)
+* --stringtable-input, msggrep option: msggrep Invocation. (line 135)
* --stringtable-input, msginit option: msginit Invocation. (line 43)
* --stringtable-input, msgmerge option: msgmerge Invocation. (line 117)
* --stringtable-input, msgonv option: msgconv Invocation. (line 56)
* --stringtable-output, msgconv option: msgconv Invocation. (line 88)
* --stringtable-output, msgen option: msgen Invocation. (line 84)
* --stringtable-output, msgfilter option: msgfilter Invocation.
- (line 125)
-* --stringtable-output, msggrep option: msggrep Invocation. (line 148)
+ (line 142)
+* --stringtable-output, msggrep option: msggrep Invocation. (line 166)
* --stringtable-output, msginit option: msginit Invocation. (line 68)
* --stringtable-output, msgmerge option: msgmerge Invocation. (line 149)
* --stringtable-output, msgunfmt option: msgunfmt Invocation. (line 126)
* --stringtable-output, msguniq option: msguniq Invocation. (line 106)
-* --stringtable-output, xgettext option: xgettext Invocation. (line 224)
+* --stringtable-output, xgettext option: xgettext Invocation. (line 289)
* --suffix, msgmerge option: msgmerge Invocation. (line 68)
* --tcl, msgfmt option: msgfmt Invocation. (line 43)
* --tcl, msgunfmt option: msgunfmt Invocation. (line 26)
* --to-code, msguniq option: msguniq Invocation. (line 74)
* --translated, msgattrib option: msgattrib Invocation.
(line 41)
-* --trigraphs, xgettext option: xgettext Invocation. (line 174)
+* --trigraphs, xgettext option: xgettext Invocation. (line 235)
* --unique, msgcat option: msgcat Invocation. (line 65)
* --unique, msgcomm option: msgcomm Invocation. (line 63)
* --unique, msguniq option: msguniq Invocation. (line 53)
* --version, msgcomm option: msgcomm Invocation. (line 147)
* --version, msgconv option: msgconv Invocation. (line 123)
* --version, msgen option: msgen Invocation. (line 119)
-* --version, msgexec option: msgexec Invocation. (line 71)
+* --version, msgexec option: msgexec Invocation. (line 73)
* --version, msgfilter option: msgfilter Invocation.
- (line 160)
+ (line 177)
* --version, msgfmt option: msgfmt Invocation. (line 226)
-* --version, msggrep option: msggrep Invocation. (line 181)
+* --version, msggrep option: msggrep Invocation. (line 199)
* --version, msginit option: msginit Invocation. (line 94)
* --version, msgmerge option: msgmerge Invocation. (line 184)
* --version, msgunfmt option: msgunfmt Invocation. (line 157)
* --version, msguniq option: msguniq Invocation. (line 141)
* --version, ngettext option: ngettext Invocation. (line 35)
-* --version, xgettext option: xgettext Invocation. (line 323)
+* --version, xgettext option: xgettext Invocation. (line 388)
* --width, msgattrib option: msgattrib Invocation.
(line 143)
* --width, msgcat option: msgcat Invocation. (line 124)
* --width, msgconv option: msgconv Invocation. (line 93)
* --width, msgen option: msgen Invocation. (line 89)
* --width, msgfilter option: msgfilter Invocation.
- (line 130)
-* --width, msggrep option: msggrep Invocation. (line 153)
+ (line 147)
+* --width, msggrep option: msggrep Invocation. (line 171)
* --width, msginit option: msginit Invocation. (line 73)
* --width, msgmerge option: msgmerge Invocation. (line 154)
* --width, msgunfmt option: msgunfmt Invocation. (line 131)
* --width, msguniq option: msguniq Invocation. (line 111)
-* --width, xgettext option: xgettext Invocation. (line 229)
+* --width, xgettext option: xgettext Invocation. (line 294)
* -<, msgcat option: msgcat Invocation. (line 55)
* -<, msgcomm option: msgcomm Invocation. (line 53)
* ->, msgcat option: msgcat Invocation. (line 60)
(line 40)
* -C, msgfmt option: msgfmt Invocation. (line 183)
* -c, msgfmt option: msgfmt Invocation. (line 146)
-* -C, msggrep option: msggrep Invocation. (line 85)
+* -C, msggrep option: msggrep Invocation. (line 93)
* -C, msgmerge option: msgmerge Invocation. (line 36)
* -c, xgettext option: xgettext Invocation. (line 97)
* -C, xgettext option: xgettext Invocation. (line 64)
* -D, msgcomm option: msgcomm Invocation. (line 30)
* -D, msgconv option: msgconv Invocation. (line 19)
* -D, msgen option: msgen Invocation. (line 25)
-* -D, msgexec option: msgexec Invocation. (line 42)
+* -D, msgexec option: msgexec Invocation. (line 44)
* -D, msgfilter option: msgfilter Invocation.
(line 20)
* -d, msgfmt option: msgfmt Invocation. (line 84)
* -E, gettext option: gettext Invocation. (line 27)
* -e, gettext option: gettext Invocation. (line 20)
* -e, msgfilter option: msgfilter Invocation.
- (line 68)
-* -e, msggrep option: msggrep Invocation. (line 97)
-* -E, msggrep option: msggrep Invocation. (line 89)
+ (line 70)
+* -e, msggrep option: msggrep Invocation. (line 109)
+* -E, msggrep option: msggrep Invocation. (line 101)
* -E, ngettext option: ngettext Invocation. (line 26)
* -e, ngettext option: ngettext Invocation. (line 19)
* -f, autopoint option: autopoint Invocation.
* -F, msgconv option: msgconv Invocation. (line 111)
* -F, msgen option: msgen Invocation. (line 107)
* -F, msgfilter option: msgfilter Invocation.
- (line 148)
+ (line 165)
* -f, msgfilter option: msgfilter Invocation.
- (line 72)
+ (line 74)
* -f, msgfmt option: msgfmt Invocation. (line 199)
-* -f, msggrep option: msggrep Invocation. (line 101)
-* -F, msggrep option: msggrep Invocation. (line 93)
+* -f, msggrep option: msggrep Invocation. (line 113)
+* -F, msggrep option: msggrep Invocation. (line 105)
* -F, msgmerge option: msgmerge Invocation. (line 172)
* -F, msguniq option: msguniq Invocation. (line 129)
-* -F, xgettext option: xgettext Invocation. (line 247)
+* -F, xgettext option: xgettext Invocation. (line 312)
* -f, xgettext option: xgettext Invocation. (line 19)
* -h, envsubst option: envsubst Invocation. (line 22)
* -h, gettext option: gettext Invocation. (line 32)
* -h, msgcomm option: msgcomm Invocation. (line 143)
* -h, msgconv option: msgconv Invocation. (line 119)
* -h, msgen option: msgen Invocation. (line 115)
-* -h, msgexec option: msgexec Invocation. (line 67)
+* -h, msgexec option: msgexec Invocation. (line 69)
* -h, msgfilter option: msgfilter Invocation.
- (line 156)
+ (line 173)
* -h, msgfmt option: msgfmt Invocation. (line 222)
-* -h, msggrep option: msggrep Invocation. (line 177)
+* -h, msggrep option: msggrep Invocation. (line 195)
* -h, msginit option: msginit Invocation. (line 90)
* -h, msgmerge option: msgmerge Invocation. (line 180)
* -h, msgunfmt option: msgunfmt Invocation. (line 153)
* -h, msguniq option: msguniq Invocation. (line 137)
* -h, ngettext option: ngettext Invocation. (line 31)
-* -h, xgettext option: xgettext Invocation. (line 319)
+* -h, xgettext option: xgettext Invocation. (line 384)
* -i, msgattrib option: msgattrib Invocation.
(line 117)
* -i, msgcat option: msgcat Invocation. (line 98)
* -i, msgcomm option: msgcomm Invocation. (line 88)
* -i, msgconv option: msgconv Invocation. (line 68)
* -i, msgen option: msgen Invocation. (line 64)
-* -i, msgexec option: msgexec Invocation. (line 38)
+* -i, msgexec option: msgexec Invocation. (line 40)
* -i, msgfilter option: msgfilter Invocation.
(line 16)
-* -i, msggrep option: msggrep Invocation. (line 105)
+* -i, msggrep option: msggrep Invocation. (line 117)
* -i, msginit option: msginit Invocation. (line 16)
* -i, msgmerge option: msgmerge Invocation. (line 129)
* -i, msgunfmt option: msgunfmt Invocation. (line 112)
* -i, msguniq option: msguniq Invocation. (line 85)
-* -i, xgettext option: xgettext Invocation. (line 204)
+* -i, xgettext option: xgettext Invocation. (line 269)
* -j, msgfmt option: msgfmt Invocation. (line 30)
+* -J, msggrep option: msggrep Invocation. (line 81)
* -j, msgunfmt option: msgunfmt Invocation. (line 16)
* -j, xgettext option: xgettext Invocation. (line 88)
-* -K, msggrep option: msggrep Invocation. (line 77)
+* -K, msggrep option: msggrep Invocation. (line 85)
* -k, xgettext option: xgettext Invocation. (line 114)
* -l, msgfmt option: msgfmt Invocation. (line 79)
* -l, msginit option: msginit Invocation. (line 52)
* -l, msgunfmt option: msgunfmt Invocation. (line 47)
* -L, xgettext option: xgettext Invocation. (line 56)
* -m, msgcmp option: msgcmp Invocation. (line 36)
-* -M, msggrep option: msggrep Invocation. (line 73)
+* -M, msggrep option: msggrep Invocation. (line 77)
* -m, msgmerge option: msgmerge Invocation. (line 101)
-* -M, xgettext option: xgettext Invocation. (line 311)
-* -m, xgettext option: xgettext Invocation. (line 307)
+* -M, xgettext option: xgettext Invocation. (line 376)
+* -m, xgettext option: xgettext Invocation. (line 372)
* -n, gettext option: gettext Invocation. (line 35)
* -n, msgattrib option: msgattrib Invocation.
(line 124)
* -n, msgcat option: msgcat Invocation. (line 105)
* -n, msgcomm option: msgcomm Invocation. (line 95)
* -n, msgfilter option: msgfilter Invocation.
- (line 77)
-* -N, msggrep option: msggrep Invocation. (line 68)
+ (line 79)
+* -N, msggrep option: msggrep Invocation. (line 72)
* -N, msgmerge option: msgmerge Invocation. (line 105)
* -n, msguniq option: msguniq Invocation. (line 92)
-* -n, xgettext option: xgettext Invocation. (line 211)
+* -n, xgettext option: xgettext Invocation. (line 276)
* -o, msgattrib option: msgattrib Invocation.
(line 31)
* -o, msgcat option: msgcat Invocation. (line 44)
* -P, msgconv option: msgconv Invocation. (line 52)
* -p, msgen option: msgen Invocation. (line 79)
* -P, msgen option: msgen Invocation. (line 48)
-* -P, msgexec option: msgexec Invocation. (line 54)
+* -P, msgexec option: msgexec Invocation. (line 56)
* -p, msgfilter option: msgfilter Invocation.
- (line 120)
+ (line 137)
* -P, msgfilter option: msgfilter Invocation.
- (line 85)
+ (line 102)
* -P, msgfmt option: msgfmt Invocation. (line 133)
-* -p, msggrep option: msggrep Invocation. (line 143)
-* -P, msggrep option: msggrep Invocation. (line 113)
+* -p, msggrep option: msggrep Invocation. (line 161)
+* -P, msggrep option: msggrep Invocation. (line 131)
* -p, msginit option: msginit Invocation. (line 63)
* -P, msginit option: msginit Invocation. (line 39)
* -p, msgmerge option: msgmerge Invocation. (line 144)
* -s, msgconv option: msgconv Invocation. (line 106)
* -s, msgen option: msgen Invocation. (line 102)
* -s, msgfilter option: msgfilter Invocation.
- (line 143)
+ (line 160)
* -s, msgmerge option: msgmerge Invocation. (line 167)
* -s, msgunfmt option: msgunfmt Invocation. (line 144)
* -s, msguniq option: msguniq Invocation. (line 124)
-* -s, xgettext option: xgettext Invocation. (line 242)
+* -s, xgettext option: xgettext Invocation. (line 307)
* -t, msgcat option: msgcat Invocation. (line 87)
* -t, msgconv option: msgconv Invocation. (line 42)
-* -T, msggrep option: msggrep Invocation. (line 81)
+* -T, msggrep option: msggrep Invocation. (line 89)
* -t, msguniq option: msguniq Invocation. (line 74)
-* -T, xgettext option: xgettext Invocation. (line 174)
+* -T, xgettext option: xgettext Invocation. (line 235)
* -u, msgcat option: msgcat Invocation. (line 65)
* -u, msgcomm option: msgcomm Invocation. (line 63)
* -U, msgmerge option: msgmerge Invocation. (line 45)
* -V, msgcomm option: msgcomm Invocation. (line 147)
* -V, msgconv option: msgconv Invocation. (line 123)
* -V, msgen option: msgen Invocation. (line 119)
-* -V, msgexec option: msgexec Invocation. (line 71)
+* -V, msgexec option: msgexec Invocation. (line 73)
* -V, msgfilter option: msgfilter Invocation.
- (line 160)
+ (line 177)
* -v, msgfmt option: msgfmt Invocation. (line 233)
* -V, msgfmt option: msgfmt Invocation. (line 226)
-* -V, msggrep option: msggrep Invocation. (line 181)
+* -V, msggrep option: msggrep Invocation. (line 199)
+* -v, msggrep option: msggrep Invocation. (line 121)
* -V, msginit option: msginit Invocation. (line 94)
* -v, msgmerge option: msgmerge Invocation. (line 188)
* -V, msgmerge option: msgmerge Invocation. (line 184)
* -V, msgunfmt option: msgunfmt Invocation. (line 157)
* -V, msguniq option: msguniq Invocation. (line 141)
* -V, ngettext option: ngettext Invocation. (line 35)
-* -V, xgettext option: xgettext Invocation. (line 323)
+* -V, xgettext option: xgettext Invocation. (line 388)
* -w, msgattrib option: msgattrib Invocation.
(line 143)
* -w, msgcat option: msgcat Invocation. (line 124)
* -w, msgconv option: msgconv Invocation. (line 93)
* -w, msgen option: msgen Invocation. (line 89)
* -w, msgfilter option: msgfilter Invocation.
- (line 130)
-* -w, msggrep option: msggrep Invocation. (line 153)
+ (line 147)
+* -w, msggrep option: msggrep Invocation. (line 171)
* -w, msginit option: msginit Invocation. (line 73)
* -w, msgmerge option: msgmerge Invocation. (line 154)
* -w, msgunfmt option: msgunfmt Invocation. (line 131)
* -w, msguniq option: msguniq Invocation. (line 111)
-* -w, xgettext option: xgettext Invocation. (line 229)
+* -w, xgettext option: xgettext Invocation. (line 294)
+* -X, msggrep option: msggrep Invocation. (line 97)
* -x, xgettext option: xgettext Invocation. (line 92)
\1f
* GETTEXT_LOG_UNTRANSLATED, environment variable: Prioritizing messages.
(line 23)
-* LANG, environment variable <1>: gettext grok. (line 29)
+* LANG, environment variable <1>: gettext grok. (line 32)
* LANG, environment variable: End Users. (line 6)
-* LANGUAGE, environment variable <1>: po/Makevars. (line 18)
-* LANGUAGE, environment variable: gettext grok. (line 25)
-* LC_ALL, environment variable: gettext grok. (line 25)
-* LC_COLLATE, environment variable: gettext grok. (line 27)
-* LC_CTYPE, environment variable: gettext grok. (line 27)
-* LC_MESSAGES, environment variable: gettext grok. (line 27)
-* LC_MONETARY, environment variable: gettext grok. (line 27)
-* LC_NUMERIC, environment variable: gettext grok. (line 27)
-* LC_TIME, environment variable: gettext grok. (line 27)
+* LANGUAGE, environment variable <1>: po/Rules-*. (line 11)
+* LANGUAGE, environment variable: gettext grok. (line 28)
+* LC_ALL, environment variable: gettext grok. (line 28)
+* LC_COLLATE, environment variable: gettext grok. (line 30)
+* LC_CTYPE, environment variable: gettext grok. (line 30)
+* LC_MESSAGES, environment variable: gettext grok. (line 30)
+* LC_MONETARY, environment variable: gettext grok. (line 30)
+* LC_NUMERIC, environment variable: gettext grok. (line 30)
+* LC_TIME, environment variable: gettext grok. (line 30)
* LINGUAS, environment variable: Installers. (line 17)
* MSGEXEC_LOCATION, environment variable: msgexec Invocation. (line 18)
+* MSGEXEC_MSGCTXT, environment variable: msgexec Invocation. (line 18)
* MSGEXEC_MSGID, environment variable: msgexec Invocation. (line 18)
* TEXTDOMAIN, environment variable: sh. (line 23)
* TEXTDOMAINDIR, environment variable: sh. (line 26)
(line 23)
* po-next-untranslated-entry, PO Mode command: Untranslated Entries.
(line 35)
-* po-normalize, PO Mode command <1>: Normalizing. (line 31)
-* po-normalize, PO Mode command: PO Files. (line 192)
+* po-normalize, PO Mode command: Normalizing. (line 31)
* po-other-window, PO Mode command: Main PO Commands. (line 72)
* po-pop-location, PO Mode command: Entry Positioning. (line 92)
* po-previous-entry, PO Mode command: Entry Positioning. (line 69)
* Menu:
* _, a macro to mark strings for translation: Mark Keywords. (line 45)
-* _nl_msg_cat_cntr: gettext grok. (line 59)
+* _nl_msg_cat_cntr: gettext grok. (line 62)
* ABOUT-NLS file: Matrix. (line 6)
* acconfig.h file: acconfig. (line 6)
* accumulating translations: Creating Compendia. (line 14)
* auxiliary PO file: Auxiliary. (line 13)
* available translations: Matrix. (line 6)
* awk: gawk. (line 6)
-* awk-format flag: PO Files. (line 133)
+* awk-format flag: PO Files. (line 144)
* backup old file, and msgmerge program: msgmerge Invocation. (line 65)
* bash: bash. (line 6)
* bibliography: References. (line 6)
* big picture: Overview. (line 6)
* bind_textdomain_codeset: Charset conversion. (line 28)
-* bug report address: Introduction. (line 29)
+* Boost format strings: xgettext Invocation. (line 244)
+* boost-format flag: PO Files. (line 180)
+* bug report address: Introduction. (line 24)
* C and C-like languages: C. (line 6)
-* C trigraphs: xgettext Invocation. (line 174)
+* C trigraphs: xgettext Invocation. (line 235)
* C#: C#. (line 6)
* C# mode, and msgfmt program: msgfmt Invocation. (line 36)
* C# mode, and msgunfmt program: msgunfmt Invocation. (line 19)
* C# resources mode, and msgunfmt program: msgunfmt Invocation.
(line 23)
* C#, string concatenation: Preparing Strings. (line 166)
-* c-format flag: PO Files. (line 74)
+* c-format flag: PO Files. (line 85)
* c-format, and xgettext: c-format Flag. (line 48)
-* catalog encoding and msgexec output: msgexec Invocation. (line 23)
+* catalog encoding and msgexec output: msgexec Invocation. (line 25)
* catclose, a catgets function: Interface to catgets.
(line 44)
* catgets, a catgets function: Interface to catgets.
* clisp: Common Lisp. (line 6)
* clisp C sources: clisp C. (line 6)
* codeset: Aspects. (line 67)
-* comments in PO files: PO Files. (line 235)
+* comments in PO files: PO Files. (line 270)
+* comments, automatic: PO Files. (line 35)
+* comments, extracted: PO Files. (line 35)
+* comments, translator: PO Files. (line 35)
* Common Lisp: Common Lisp. (line 6)
* compare PO files: msgcmp Invocation. (line 8)
* comparison of interfaces: Comparison. (line 6)
(line 14)
* concatenation of strings: Preparing Strings. (line 115)
* config.h.in file: config.h.in. (line 6)
+* context: Contexts. (line 6)
+* context, argument specification in xgettext: xgettext Invocation.
+ (line 117)
+* context, in MO files: MO Files. (line 63)
+* context, in PO files: PO Files. (line 184)
* convert binary message catalog into PO file: msgunfmt Invocation.
(line 8)
* convert translations to a different encoding: msgconv Invocation.
* create new PO file: msginit Invocation. (line 8)
* creating a new PO file: Creating. (line 6)
* creating compendia: Creating Compendia. (line 6)
-* csharp-format flag: PO Files. (line 129)
+* csharp-format flag: PO Files. (line 140)
* currency symbols: Aspects. (line 79)
* date format: Aspects. (line 84)
* dcngettext: Plural forms. (line 111)
+* dcpgettext: Contexts. (line 56)
+* dcpgettext_expr: Contexts. (line 112)
* debugging messages marked as format strings: xgettext Invocation.
- (line 183)
+ (line 248)
* dialect: Manipulating. (line 28)
* disabling NLS: lib/gettext.h. (line 6)
* distribution tarball: Release Management. (line 6)
* dngettext: Plural forms. (line 103)
* dollar substitution: envsubst Invocation. (line 8)
* domain ambiguities: Ambiguities. (line 6)
+* dpgettext: Contexts. (line 56)
+* dpgettext_expr: Contexts. (line 112)
* duplicate elimination: Manipulating. (line 45)
* duplicate removal: msguniq Invocation. (line 8)
* editing comments in PO files: Modifying Comments. (line 6)
+* Editing PO Files: Editing. (line 6)
* editing translations: Modifying Translations.
(line 6)
-* elisp-format flag: PO Files. (line 109)
+* elisp-format flag: PO Files. (line 120)
* Emacs Lisp: Emacs Lisp. (line 6)
+* Emacs PO Mode: PO Mode. (line 6)
* encoding: Aspects. (line 67)
* encoding conversion: Manipulating. (line 17)
* encoding conversion at runtime: Charset conversion. (line 6)
(line 6)
* eval_ngettext function, usage: eval_ngettext Invocation.
(line 6)
-* evolution of packages: Overview. (line 142)
+* evolution of packages: Overview. (line 127)
* extracting parts of a PO file into a compendium: Creating Compendia.
(line 65)
+* FDL, GNU Free Documentation License: GNU FDL. (line 6)
* file format, .mo: MO Files. (line 6)
* file format, .po: PO Files. (line 6)
* files, .po and .mo: Files. (line 6)
-* files, .pot: Overview. (line 79)
+* files, .pot: Overview. (line 67)
* filter messages according to attributes: msgattrib Invocation.
(line 8)
* find common messages: msgcomm Invocation. (line 8)
* force use of fuzzy entries: msgfmt Invocation. (line 199)
* format strings: c-format Flag. (line 6)
* Free Pascal: Pascal. (line 6)
-* function attribute, __format__: xgettext Invocation. (line 138)
-* function attribute, __format_arg__: xgettext Invocation. (line 152)
+* function attribute, __format__: xgettext Invocation. (line 199)
+* function attribute, __format_arg__: xgettext Invocation. (line 213)
* fuzzy entries: Fuzzy Entries. (line 6)
-* fuzzy flag: PO Files. (line 64)
+* fuzzy flag: PO Files. (line 75)
* gawk: gawk. (line 6)
-* gcc-internal-format flag: PO Files. (line 161)
+* gcc-internal-format flag: PO Files. (line 172)
* GCC-source: GCC-source. (line 6)
* generate binary message catalog from PO file: msgfmt Invocation.
(line 8)
* gettext.h file: lib/gettext.h. (line 6)
* gettextize program, usage: gettextize Invocation.
(line 34)
-* GUI programs: GUI program problems.
- (line 6)
+* GNOME PO file editor: Gtranslator. (line 6)
+* GPL, GNU General Public License: GNU GPL. (line 6)
+* GUI programs: Contexts. (line 6)
* guile: Scheme. (line 6)
* hash table, inside MO files: MO Files. (line 47)
-* he, she, and they: Introduction. (line 11)
+* he, she, and they: Introduction. (line 15)
* header entry of a PO file: Header Entry. (line 6)
* help option: Preparing Strings. (line 107)
* history of GNU gettext: History. (line 6)
* importing PO files: Normalizing. (line 55)
* include file libintl.h <1>: lib/gettext.h. (line 29)
* include file libintl.h <2>: Comparison. (line 33)
-* include file libintl.h <3>: Sources. (line 19)
-* include file libintl.h: Overview. (line 69)
+* include file libintl.h <3>: Importing. (line 11)
+* include file libintl.h: Overview. (line 57)
* initialization: Triggering. (line 6)
* initialize new PO file: msginit Invocation. (line 8)
* initialize translations from a compendium: Using Compendia. (line 12)
* Java mode, and msgfmt program: msgfmt Invocation. (line 30)
* Java mode, and msgunfmt program: msgunfmt Invocation. (line 16)
* Java, string concatenation: Preparing Strings. (line 166)
-* java-format flag: PO Files. (line 125)
+* java-format flag: PO Files. (line 136)
+* KDE PO file editor: KBabel. (line 6)
* keyboard accelerator checking: msgfmt Invocation. (line 187)
* l10n: Concepts. (line 6)
* language codes: Language Codes. (line 6)
* language selection: End Users. (line 6)
-* language selection at runtime: gettext grok. (line 11)
+* language selection at runtime: gettext grok. (line 14)
* large package: Ambiguities. (line 6)
+* LGPL, GNU Lesser General Public License: GNU LGPL. (line 6)
* libiconv library: AM_ICONV. (line 21)
* libintl for C#: C#. (line 161)
* libintl for Java: Java. (line 104)
* libintl library: AM_GNU_GETTEXT. (line 48)
* librep Lisp: librep. (line 6)
-* librep-format flag: PO Files. (line 113)
+* librep-format flag: PO Files. (line 124)
+* License, GNU FDL: GNU FDL. (line 6)
+* License, GNU GPL: GNU GPL. (line 6)
+* License, GNU LGPL: GNU LGPL. (line 6)
+* Licenses: Licenses. (line 6)
* LINGUAS file: po/LINGUAS. (line 6)
-* link with libintl: Overview. (line 74)
+* link with libintl: Overview. (line 62)
* Linux <1>: Header Entry. (line 91)
-* Linux <2>: Overview. (line 74)
+* Linux <2>: Overview. (line 62)
* Linux: Aspects. (line 114)
* Lisp: Common Lisp. (line 6)
-* lisp-format flag: PO Files. (line 105)
+* lisp-format flag: PO Files. (line 116)
* list of translation teams, where to find: Header Entry. (line 58)
* locale facet, LC_ALL: Triggering. (line 23)
* locale facet, LC_COLLATE: Triggering. (line 52)
(line 8)
* lookup plural message translation: ngettext Invocation. (line 8)
* magic signature of MO files: MO Files. (line 9)
+* Makefile.in.in extensions: po/Rules-*. (line 6)
* Makevars file: po/Makevars. (line 6)
* manipulating PO files: Manipulating. (line 6)
* marking Perl sources: Perl. (line 93)
* marking string initializers: Special cases. (line 6)
* marking strings that require translation: Mark Keywords. (line 6)
* marking strings, preparations: Preparing Strings. (line 6)
-* marking translatable strings: Overview. (line 46)
-* menu entries: GUI program problems.
- (line 6)
+* marking translatable strings: Overview. (line 34)
+* menu entries: Contexts. (line 6)
* menu, keyboard accelerator support: msgfmt Invocation. (line 187)
* merge PO files: msgcat Invocation. (line 8)
* merging two PO files: Manipulating. (line 10)
* msgcmp program, usage: msgcmp Invocation. (line 6)
* msgcomm program, usage: msgcomm Invocation. (line 6)
* msgconv program, usage: msgconv Invocation. (line 6)
+* msgctxt: PO Files. (line 184)
* msgen program, usage: msgen Invocation. (line 6)
* msgexec program, usage: msgexec Invocation. (line 6)
* msgfilter filter and catalog encoding: msgfilter Invocation.
- (line 45)
+ (line 46)
* msgfilter program, usage: msgfilter Invocation.
(line 6)
* msgfmt program, usage: msgfmt Invocation. (line 6)
* msggrep program, usage: msggrep Invocation. (line 6)
-* msgid: PO Files. (line 40)
-* msgid_plural: PO Files. (line 169)
+* msgid: PO Files. (line 51)
+* msgid_plural: PO Files. (line 202)
* msginit program, usage: msginit Invocation. (line 6)
* msgmerge program, usage: msgmerge Invocation. (line 6)
-* msgstr: PO Files. (line 40)
+* msgstr: PO Files. (line 51)
* msgunfmt program, usage: msgunfmt Invocation. (line 6)
* msguniq program, usage: msguniq Invocation. (line 6)
* multi-line strings: Normalizing. (line 65)
* N_, a convenience macro: Comparison. (line 41)
* Native Language Support: Concepts. (line 51)
* Natural Language Support: Concepts. (line 51)
-* newlines in PO files: PO Files. (line 230)
+* newlines in PO files: PO Files. (line 265)
* ngettext: Plural forms. (line 84)
* ngettext program, usage: ngettext Invocation. (line 6)
* NLS: Concepts. (line 51)
-* no-awk-format flag: PO Files. (line 134)
-* no-c-format flag: PO Files. (line 75)
+* no-awk-format flag: PO Files. (line 145)
+* no-boost-format flag: PO Files. (line 181)
+* no-c-format flag: PO Files. (line 86)
* no-c-format, and xgettext: c-format Flag. (line 48)
-* no-csharp-format flag: PO Files. (line 130)
-* no-elisp-format flag: PO Files. (line 110)
-* no-gcc-internal-format flag: PO Files. (line 162)
-* no-java-format flag: PO Files. (line 126)
-* no-librep-format flag: PO Files. (line 114)
-* no-lisp-format flag: PO Files. (line 106)
-* no-objc-format flag: PO Files. (line 94)
-* no-object-pascal-format flag: PO Files. (line 138)
-* no-perl-brace-format flag: PO Files. (line 154)
-* no-perl-format flag: PO Files. (line 150)
-* no-php-format flag: PO Files. (line 158)
-* no-python-format flag: PO Files. (line 102)
-* no-qt-format flag: PO Files. (line 166)
-* no-scheme-format flag: PO Files. (line 118)
-* no-sh-format flag: PO Files. (line 98)
-* no-smalltalk-format flag: PO Files. (line 122)
-* no-tcl-format flag: PO Files. (line 146)
-* no-ycp-format flag: PO Files. (line 142)
+* no-csharp-format flag: PO Files. (line 141)
+* no-elisp-format flag: PO Files. (line 121)
+* no-gcc-internal-format flag: PO Files. (line 173)
+* no-java-format flag: PO Files. (line 137)
+* no-librep-format flag: PO Files. (line 125)
+* no-lisp-format flag: PO Files. (line 117)
+* no-objc-format flag: PO Files. (line 105)
+* no-object-pascal-format flag: PO Files. (line 149)
+* no-perl-brace-format flag: PO Files. (line 165)
+* no-perl-format flag: PO Files. (line 161)
+* no-php-format flag: PO Files. (line 169)
+* no-python-format flag: PO Files. (line 113)
+* no-qt-format flag: PO Files. (line 177)
+* no-scheme-format flag: PO Files. (line 129)
+* no-sh-format flag: PO Files. (line 109)
+* no-smalltalk-format flag: PO Files. (line 133)
+* no-tcl-format flag: PO Files. (line 157)
+* no-ycp-format flag: PO Files. (line 153)
* nplurals, in a PO file header: Plural forms. (line 128)
* number format: Aspects. (line 94)
-* objc-format flag: PO Files. (line 93)
+* objc-format flag: PO Files. (line 104)
* Object Pascal: Pascal. (line 6)
-* object-pascal-format flag: PO Files. (line 137)
+* object-pascal-format flag: PO Files. (line 148)
* obsolete entries: Obsolete Entries. (line 6)
* optimization of gettext functions: Optimized gettext. (line 6)
* orthography: Manipulating. (line 28)
* package and version declaration in configure.in: configure.in.
(line 9)
* package build and installation options: Installers. (line 6)
+* package distributor's view of gettext: Installers. (line 6)
+* package installer's view of gettext: Installers. (line 6)
* package maintainer's view of gettext: Maintainers. (line 6)
* paragraphs: Preparing Strings. (line 99)
* Pascal: Pascal. (line 6)
(line 6)
* Perl special keywords for hash-lookups: Special Keywords. (line 6)
* Perl valid string interpolation: Interpolation II. (line 6)
-* perl-brace-format flag: PO Files. (line 153)
-* perl-format flag: PO Files. (line 149)
+* perl-brace-format flag: PO Files. (line 164)
+* perl-format flag: PO Files. (line 160)
+* pgettext: Contexts. (line 33)
+* pgettext_expr: Contexts. (line 112)
* PHP: PHP. (line 6)
-* php-format flag: PO Files. (line 157)
+* php-format flag: PO Files. (line 168)
* Pike: Pike. (line 6)
-* plural form formulas: Plural forms. (line 145)
+* plural form formulas: Plural forms. (line 148)
* plural forms: Plural forms. (line 6)
-* plural forms, in MO files: MO Files. (line 63)
-* plural forms, in PO files: PO Files. (line 169)
+* plural forms, in MO files: MO Files. (line 66)
+* plural forms, in PO files: PO Files. (line 202)
* plural, in a PO file header: Plural forms. (line 128)
* PO files' format: PO Files. (line 6)
* PO mode (Emacs) commands: Main PO Commands. (line 6)
* po_message_msgstr_plural: libgettextpo. (line 86)
* po_next_message: libgettextpo. (line 62)
* portability problems with sed: msgfilter Invocation.
- (line 55)
+ (line 57)
* POTFILES.in file: po/POTFILES.in. (line 6)
* preparing programs for translation: Sources. (line 6)
* preparing shell scripts for translation: Preparing Shell Scripts.
* programming languages: Language Implementors.
(line 6)
* Python: Python. (line 6)
-* python-format flag: PO Files. (line 101)
-* Qt format strings: xgettext Invocation. (line 179)
+* python-format flag: PO Files. (line 112)
+* Qt format strings: xgettext Invocation. (line 240)
* Qt mode, and msgfmt program: msgfmt Invocation. (line 46)
-* qt-format flag: PO Files. (line 165)
-* quotation marks <1>: po/Makevars. (line 18)
+* qt-format flag: PO Files. (line 176)
+* quotation marks <1>: po/Rules-*. (line 11)
* quotation marks: Header Entry. (line 145)
* quote characters, use in PO files: Header Entry. (line 145)
+* recode-sr-latin program: msgfilter Invocation.
+ (line 85)
* related reading: References. (line 6)
* release: Release Management. (line 6)
* RST: RST. (line 6)
* Scheme: Scheme. (line 6)
-* scheme-format flag: PO Files. (line 117)
+* scheme-format flag: PO Files. (line 128)
* scripting languages: Language Implementors.
(line 6)
* search messages in a catalog: msggrep Invocation. (line 8)
* setting up gettext at build time: Installers. (line 6)
* setting up gettext at run time: End Users. (line 6)
* several domains: Ambiguities. (line 6)
-* sex: Introduction. (line 11)
-* sgettext: GUI program problems.
- (line 59)
-* sh-format flag: PO Files. (line 97)
-* she, he, and they: Introduction. (line 11)
+* sex: Introduction. (line 15)
+* sh-format flag: PO Files. (line 108)
+* she, he, and they: Introduction. (line 15)
* shell format string: envsubst Invocation. (line 8)
* shell scripts: sh. (line 6)
* Smalltalk: Smalltalk. (line 6)
-* smalltalk-format flag: PO Files. (line 121)
+* smalltalk-format flag: PO Files. (line 132)
* sorting msgcat output: msgcat Invocation. (line 137)
* sorting msgmerge output: msgmerge Invocation. (line 167)
* sorting msgunfmt output: msgunfmt Invocation. (line 144)
-* sorting output of xgettext: xgettext Invocation. (line 242)
+* sorting output of xgettext: xgettext Invocation. (line 307)
* specifying plural form in a PO file: Plural forms. (line 128)
* standard output, and msgcat: msgcat Invocation. (line 47)
* standard output, and msgmerge program: msgmerge Invocation. (line 56)
* Tcl: Tcl. (line 6)
* Tcl mode, and msgfmt program: msgfmt Invocation. (line 43)
* Tcl mode, and msgunfmt program: msgunfmt Invocation. (line 26)
-* tcl-format flag: PO Files. (line 145)
-* template PO file: Overview. (line 79)
-* testing .po files for equivalence: xgettext Invocation. (line 252)
+* tcl-format flag: PO Files. (line 156)
+* template PO file: Overview. (line 67)
+* testing .po files for equivalence: xgettext Invocation. (line 317)
* Tk's scripting language: Tcl. (line 6)
* translated entries: Translated Entries. (line 6)
-* translating menu entries: GUI program problems.
- (line 6)
+* translating menu entries: Contexts. (line 6)
* translation aspects: Aspects. (line 6)
* Translation Matrix: Matrix. (line 6)
* Translation Project: Why. (line 17)
* upgrading to new versions of gettext: Prerequisites. (line 6)
* version control for backup files, msgmerge: msgmerge Invocation.
(line 71)
-* wxWindows library: wxWindows. (line 6)
+* wxWidgets library: wxWidgets. (line 6)
* xargs, and output from msgexec: msgexec Invocation. (line 14)
* xgettext program, usage: xgettext Invocation. (line 6)
* xmodmap program, and typing quotation marks: Header Entry. (line 157)
* YaST2 scripting language: YCP. (line 6)
* YCP: YCP. (line 6)
-* ycp-format flag: PO Files. (line 141)
+* ycp-format flag: PO Files. (line 152)
\1f
Tag Table:
-Node: Top\7f2663
-Node: Introduction\7f15060
-Node: Why\7f16922
-Ref: Why-Footnote-1\7f20034
-Node: Concepts\7f20190
-Node: Aspects\7f23608
-Node: Files\7f29466
-Node: Overview\7f31372
-Node: Basics\7f42169
-Node: Installation\7f43000
-Node: PO Files\7f44947
-Ref: PO Files-Footnote-1\7f54373
-Node: Main PO Commands\7f54500
-Node: Entry Positioning\7f59576
-Node: Normalizing\7f65037
-Node: Sources\7f69496
-Node: Triggering\7f71194
-Node: Preparing Strings\7f74229
-Node: Mark Keywords\7f81934
-Node: Marking\7f85494
-Node: c-format Flag\7f93221
-Node: Special cases\7f97137
-Node: Names\7f99863
-Node: Libraries\7f103464
-Node: Template\7f106495
-Node: xgettext Invocation\7f107216
-Node: Creating\7f118812
-Node: msginit Invocation\7f119694
-Node: Header Entry\7f122320
-Node: Updating\7f129325
-Node: msgmerge Invocation\7f130084
-Node: Translated Entries\7f135125
-Node: Fuzzy Entries\7f136485
-Node: Untranslated Entries\7f139659
-Node: Obsolete Entries\7f141585
-Node: Modifying Translations\7f144804
-Node: Modifying Comments\7f152767
-Node: Subedit\7f157186
-Node: C Sources Context\7f161074
-Node: Auxiliary\7f166190
-Node: Compendium\7f169423
-Node: Creating Compendia\7f170040
-Node: Using Compendia\7f172520
-Node: Manipulating\7f173449
-Node: msgcat Invocation\7f177212
-Node: msgconv Invocation\7f181462
-Node: msggrep Invocation\7f184641
-Node: msgfilter Invocation\7f189412
-Node: msguniq Invocation\7f194291
-Node: msgcomm Invocation\7f198180
-Node: msgcmp Invocation\7f202225
-Node: msgattrib Invocation\7f203837
-Node: msgen Invocation\7f208432
-Node: msgexec Invocation\7f211767
-Node: libgettextpo\7f214214
-Node: Binaries\7f219336
-Node: msgfmt Invocation\7f219672
-Node: msgunfmt Invocation\7f226655
-Node: MO Files\7f230799
-Node: Users\7f238895
-Node: Matrix\7f240379
-Node: Installers\7f241588
-Node: End Users\7f242763
-Node: Programmers\7f243416
-Node: catgets\7f244592
-Node: Interface to catgets\7f246002
-Node: Problems with catgets\7f248008
-Node: gettext\7f248920
-Node: Interface to gettext\7f250426
-Node: Ambiguities\7f252783
-Node: Locating Catalogs\7f255487
-Ref: Locating Catalogs-Footnote-1\7f256645
-Ref: Locating Catalogs-Footnote-2\7f256870
-Node: Charset conversion\7f257019
-Node: Plural forms\7f259474
-Ref: Plural forms-Footnote-1\7f270380
-Node: GUI program problems\7f270472
-Node: Optimized gettext\7f275587
-Node: Comparison\7f276931
-Node: Using libintl.a\7f281198
-Node: gettext grok\7f281638
-Node: Temp Programmers\7f284189
-Node: Temp Implementations\7f284639
-Node: Temp catgets\7f286016
-Node: Temp WSI\7f287714
-Node: Temp Notes\7f289713
-Node: Translators\7f290213
-Node: Trans Intro 0\7f290676
-Node: Trans Intro 1\7f293332
-Node: Discussions\7f295203
-Node: Organization\7f298780
-Node: Central Coordination\7f300768
-Node: National Teams\7f301907
-Node: Sub-Cultures\7f304431
-Node: Organizational Ideas\7f305365
-Node: Mailing Lists\7f306383
-Node: Information Flow\7f308197
-Node: Prioritizing messages\7f310367
-Node: Maintainers\7f314638
-Node: Flat and Non-Flat\7f316602
-Node: Prerequisites\7f318092
-Node: gettextize Invocation\7f322239
-Node: Adjusting Files\7f328953
-Node: po/POTFILES.in\7f330677
-Node: po/LINGUAS\7f331923
-Node: po/Makevars\7f333612
-Node: configure.in\7f335203
-Node: config.guess\7f337306
-Node: mkinstalldirs\7f338675
-Node: aclocal\7f339447
-Node: acconfig\7f341240
-Node: config.h.in\7f341737
-Node: Makefile\7f343200
-Node: src/Makefile\7f345794
-Node: lib/gettext.h\7f350181
-Node: autoconf macros\7f352427
-Node: AM_GNU_GETTEXT\7f353061
-Node: AM_GNU_GETTEXT_VERSION\7f356655
-Node: AM_PO_SUBDIRS\7f357101
-Node: AM_ICONV\7f357879
-Node: CVS Issues\7f360086
-Node: Distributed CVS\7f360674
-Node: Files under CVS\7f362599
-Node: autopoint Invocation\7f365872
-Node: Release Management\7f367716
-Node: Programming Languages\7f368226
-Node: Language Implementors\7f369050
-Node: Programmers for other Languages\7f373839
-Node: Translators for other Languages\7f374412
-Node: c-format\7f375885
-Node: objc-format\7f377599
-Node: sh-format\7f377951
-Node: python-format\7f378753
-Node: lisp-format\7f379191
-Node: elisp-format\7f379517
-Node: librep-format\7f380007
-Node: scheme-format\7f380407
-Node: smalltalk-format\7f380683
-Node: java-format\7f381183
-Node: csharp-format\7f381631
-Node: awk-format\7f382006
-Node: object-pascal-format\7f382331
-Node: ycp-format\7f382560
-Node: tcl-format\7f382959
-Node: perl-format\7f383254
-Node: php-format\7f383999
-Node: gcc-internal-format\7f384364
-Node: qt-format\7f385406
-Node: Maintainers for other Languages\7f385819
-Node: List of Programming Languages\7f387054
-Node: C\7f388337
-Node: sh\7f389614
-Node: Preparing Shell Scripts\7f390888
-Node: gettext.sh\7f394277
-Node: gettext Invocation\7f394824
-Node: ngettext Invocation\7f396579
-Node: envsubst Invocation\7f398167
-Node: eval_gettext Invocation\7f399588
-Node: eval_ngettext Invocation\7f400049
-Node: bash\7f400563
-Node: Python\7f402539
-Node: Common Lisp\7f403689
-Node: clisp C\7f404489
-Node: Emacs Lisp\7f405204
-Node: librep\7f405930
-Node: Scheme\7f406665
-Node: Smalltalk\7f407449
-Node: Java\7f408483
-Node: C#\7f413502
-Node: gawk\7f421919
-Node: Pascal\7f422831
-Node: wxWindows\7f424139
-Node: YCP\7f424889
-Node: Tcl\7f425628
-Node: Perl\7f427038
-Node: General Problems\7f430046
-Node: Default Keywords\7f433704
-Node: Special Keywords\7f434656
-Node: Quote-like Expressions\7f436170
-Node: Interpolation I\7f438445
-Node: Interpolation II\7f442235
-Node: Parentheses\7f444600
-Node: Long Lines\7f446117
-Node: Perl Pitfalls\7f447964
-Node: PHP\7f452206
-Node: Pike\7f453137
-Node: GCC-source\7f453798
-Node: List of Data Formats\7f454545
-Node: POT\7f455011
-Node: RST\7f455269
-Node: Glade\7f455495
-Node: Conclusion\7f455855
-Node: History\7f456358
-Node: References\7f460624
-Node: Language Codes\7f462190
-Node: Country Codes\7f466536
-Node: Program Index\7f472293
-Node: Option Index\7f474111
-Node: Variable Index\7f519612
-Node: PO Mode Index\7f521077
-Node: Autoconf Macro Index\7f534986
-Node: Index\7f535505
+Node: Top\7f2955
+Node: Introduction\7f15951
+Node: Why\7f17571
+Ref: Why-Footnote-1\7f20781
+Node: Concepts\7f20937
+Node: Aspects\7f24355
+Node: Files\7f30213
+Node: Overview\7f32119
+Node: Users\7f42037
+Node: Matrix\7f43469
+Node: End Users\7f44677
+Node: PO Files\7f45326
+Ref: PO Files-Footnote-1\7f56086
+Node: Sources\7f56213
+Node: Importing\7f57366
+Node: Triggering\7f58046
+Node: Preparing Strings\7f61083
+Node: Mark Keywords\7f68786
+Node: Marking\7f72346
+Node: c-format Flag\7f80073
+Node: Special cases\7f83989
+Node: Names\7f86715
+Node: Libraries\7f90316
+Node: Template\7f93347
+Node: xgettext Invocation\7f94068
+Node: Creating\7f108383
+Node: msginit Invocation\7f109265
+Node: Header Entry\7f111891
+Node: Updating\7f118897
+Node: msgmerge Invocation\7f119112
+Node: Editing\7f124126
+Node: KBabel\7f124424
+Node: Gtranslator\7f124562
+Node: PO Mode\7f124704
+Node: Installation\7f126396
+Node: Main PO Commands\7f128357
+Node: Entry Positioning\7f133442
+Node: Normalizing\7f138908
+Node: Translated Entries\7f143399
+Node: Fuzzy Entries\7f144754
+Node: Untranslated Entries\7f147931
+Node: Obsolete Entries\7f149860
+Node: Modifying Translations\7f153082
+Node: Modifying Comments\7f161048
+Node: Subedit\7f165472
+Node: C Sources Context\7f169365
+Node: Auxiliary\7f174486
+Node: Compendium\7f177722
+Node: Creating Compendia\7f178342
+Node: Using Compendia\7f180826
+Node: Manipulating\7f181759
+Node: msgcat Invocation\7f185521
+Node: msgconv Invocation\7f189771
+Node: msggrep Invocation\7f192950
+Node: msgfilter Invocation\7f198131
+Node: msguniq Invocation\7f203755
+Node: msgcomm Invocation\7f207644
+Node: msgcmp Invocation\7f211689
+Node: msgattrib Invocation\7f213301
+Node: msgen Invocation\7f217896
+Node: msgexec Invocation\7f221231
+Node: libgettextpo\7f223812
+Node: Binaries\7f228934
+Node: msgfmt Invocation\7f229278
+Node: msgunfmt Invocation\7f236283
+Node: MO Files\7f240445
+Node: Programmers\7f248683
+Node: catgets\7f249862
+Node: Interface to catgets\7f251272
+Node: Problems with catgets\7f253278
+Node: gettext\7f254190
+Node: Interface to gettext\7f255690
+Node: Ambiguities\7f258047
+Node: Locating Catalogs\7f260751
+Ref: Locating Catalogs-Footnote-1\7f261909
+Ref: Locating Catalogs-Footnote-2\7f262134
+Node: Charset conversion\7f262283
+Node: Contexts\7f264734
+Node: Plural forms\7f270234
+Ref: Plural forms-Footnote-1\7f281582
+Node: Optimized gettext\7f281674
+Node: Comparison\7f283010
+Node: Using libintl.a\7f287277
+Node: gettext grok\7f287717
+Node: Temp Programmers\7f290346
+Node: Temp Implementations\7f290871
+Node: Temp catgets\7f292248
+Node: Temp WSI\7f293946
+Node: Temp Notes\7f295945
+Node: Translators\7f296445
+Node: Trans Intro 0\7f296908
+Node: Trans Intro 1\7f299642
+Node: Discussions\7f301591
+Node: Organization\7f305246
+Node: Central Coordination\7f307312
+Node: National Teams\7f308451
+Node: Sub-Cultures\7f310975
+Node: Organizational Ideas\7f311909
+Node: Mailing Lists\7f312927
+Node: Information Flow\7f314741
+Node: Prioritizing messages\7f316989
+Node: Maintainers\7f321285
+Node: Flat and Non-Flat\7f323238
+Node: Prerequisites\7f324728
+Node: gettextize Invocation\7f328875
+Node: Adjusting Files\7f335817
+Node: po/POTFILES.in\7f337601
+Node: po/LINGUAS\7f338847
+Node: po/Makevars\7f340536
+Node: po/Rules-*\7f341284
+Node: configure.in\7f342752
+Node: config.guess\7f345763
+Node: mkinstalldirs\7f347116
+Node: aclocal\7f347518
+Node: acconfig\7f349325
+Node: config.h.in\7f349822
+Node: Makefile\7f351287
+Node: src/Makefile\7f353881
+Node: lib/gettext.h\7f358268
+Node: autoconf macros\7f360514
+Node: AM_GNU_GETTEXT\7f361148
+Node: AM_GNU_GETTEXT_VERSION\7f364742
+Node: AM_PO_SUBDIRS\7f365188
+Node: AM_ICONV\7f365966
+Node: CVS Issues\7f368173
+Node: Distributed CVS\7f368761
+Node: Files under CVS\7f370686
+Node: autopoint Invocation\7f373957
+Node: Release Management\7f375797
+Node: Installers\7f376307
+Node: Programming Languages\7f377531
+Node: Language Implementors\7f378354
+Node: Programmers for other Languages\7f383168
+Node: Translators for other Languages\7f383749
+Node: c-format\7f385275
+Node: objc-format\7f386988
+Node: sh-format\7f387340
+Node: python-format\7f388142
+Node: lisp-format\7f388580
+Node: elisp-format\7f388906
+Node: librep-format\7f389396
+Node: scheme-format\7f389796
+Node: smalltalk-format\7f390072
+Node: java-format\7f390572
+Node: csharp-format\7f391020
+Node: awk-format\7f391395
+Node: object-pascal-format\7f391720
+Node: ycp-format\7f391949
+Node: tcl-format\7f392348
+Node: perl-format\7f392643
+Node: php-format\7f393388
+Node: gcc-internal-format\7f393753
+Node: qt-format\7f394795
+Node: boost-format\7f395229
+Node: Maintainers for other Languages\7f395773
+Node: List of Programming Languages\7f397008
+Node: C\7f398291
+Node: sh\7f399591
+Node: Preparing Shell Scripts\7f400865
+Node: gettext.sh\7f404254
+Node: gettext Invocation\7f404801
+Node: ngettext Invocation\7f406556
+Node: envsubst Invocation\7f408144
+Node: eval_gettext Invocation\7f409565
+Node: eval_ngettext Invocation\7f410026
+Node: bash\7f410540
+Node: Python\7f412516
+Node: Common Lisp\7f413666
+Node: clisp C\7f414466
+Node: Emacs Lisp\7f415181
+Node: librep\7f415907
+Node: Scheme\7f416642
+Node: Smalltalk\7f417426
+Node: Java\7f418460
+Node: C#\7f424168
+Node: gawk\7f432585
+Node: Pascal\7f433497
+Node: wxWidgets\7f434805
+Node: YCP\7f435712
+Node: Tcl\7f436451
+Node: Perl\7f437861
+Node: General Problems\7f440869
+Node: Default Keywords\7f444527
+Node: Special Keywords\7f445479
+Node: Quote-like Expressions\7f446993
+Node: Interpolation I\7f449268
+Node: Interpolation II\7f453058
+Node: Parentheses\7f455423
+Node: Long Lines\7f456940
+Node: Perl Pitfalls\7f458787
+Node: PHP\7f463029
+Node: Pike\7f463960
+Node: GCC-source\7f464621
+Node: List of Data Formats\7f465368
+Node: POT\7f465834
+Node: RST\7f466092
+Node: Glade\7f466318
+Node: Conclusion\7f466678
+Node: History\7f467181
+Node: References\7f471447
+Node: Language Codes\7f473091
+Node: Country Codes\7f477437
+Node: Licenses\7f483189
+Node: GNU GPL\7f485031
+Node: GNU LGPL\7f504208
+Node: GNU FDL\7f532341
+Node: Program Index\7f554727
+Node: Option Index\7f556613
+Node: Variable Index\7f602625
+Node: PO Mode Index\7f604163
+Node: Autoconf Macro Index\7f617999
+Node: Index\7f618518
\1f
End Tag Table
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 1 Introduction</TITLE>
</HEAD>
<BODY>
-Go to the first, previous, <A HREF="gettext_2.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the first, previous, <A HREF="gettext_2.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC1" HREF="gettext_toc.html#TOC1">1 Introduction</A></H1>
+<H1><A NAME="SEC1" HREF="gettext_toc.html#TOC1">1 Introduction</A></H1>
-<BLOCKQUOTE>
<P>
-This manual is still in <EM>DRAFT</EM> state. Some sections are still
-empty, or almost. We keep merging material from other sources
-(essentially e-mail folders) while the proper integration of this
-material is delayed.
-</BLOCKQUOTE>
+This chapter explains the goals sought in the creation
+of GNU <CODE>gettext</CODE> and the free Translation Project.
+Then, it explains a few broad concepts around
+Native Language Support, and positions message translation with regard
+to other aspects of national and cultural variance, as they apply
+to programs. It also surveys those files used to convey the
+translations. It explains how the various tools interact in the
+initial generation of these files, and later, how the maintenance
+cycle should usually operate.
+</P>
<P>
<A NAME="IDX1"></A>
<A NAME="IDX2"></A>
is meant to be useful for people using computers, whatever their sex,
race, religion or nationality!
-</P>
-<P>
-This chapter explains the goals sought in the creation
-of GNU <CODE>gettext</CODE> and the free Translation Project.
-Then, it explains a few broad concepts around
-Native Language Support, and positions message translation with regard
-to other aspects of national and cultural variance, as they apply to
-to programs. It also surveys those files used to convey the
-translations. It explains how the various tools interact in the
-initial generation of these files, and later, how the maintenance
-cycle should usually operate.
-
</P>
<P>
<A NAME="IDX4"></A>
<LI>
+A library supporting the parsing and creation of files containing
+translated messages.
+
+<LI>
+
A special mode for Emacs<A NAME="DOCF1" HREF="gettext_foot.html#FOOT1">(1)</A> which helps preparing these sets
and bringing them up to date.
</UL>
other English specific habits, and connected to generic ways of doing
the same, instead. Program developers may use various techniques to
internationalize their programs. Some of these have been standardized.
-GNU <CODE>gettext</CODE> offers one of these standards. See section <A HREF="gettext_11.html#SEC162">11 The Programmer's View</A>.
+GNU <CODE>gettext</CODE> offers one of these standards. See section <A HREF="gettext_11.html#SEC164">11 The Programmer's View</A>.
</P>
<P>
stored in a particular locale. When someone presently refers to a
particular locale, they are obviously referring to the data stored
within that particular locale. Similarly, if a programmer is referring
-to "accessing the locale routines", they are referring to the
+to “accessing the locale routines”, they are referring to the
complete suite of routines that access all of the locale's information.
</P>
input files which are texts containing keywords, identifiers, or
replies which are inherently translatable. For example, one may want
<CODE>gcc</CODE> to allow diacriticized characters in identifiers or use
-translated keywords; <SAMP>`rm -i´</SAMP> might accept something else than
-<SAMP>`y´</SAMP> or <SAMP>`n´</SAMP> for replies, etc. Even if the program will
+translated keywords; <SAMP>‘rm -i’</SAMP> might accept something else than
+<SAMP>‘y’</SAMP> or <SAMP>‘n’</SAMP> for replies, etc. Even if the program will
eventually make most of its output in the foreign languages, one has
to decide whether the input syntax, option values, etc., are to be
localized or not.
<P>
<A NAME="IDX28"></A>
-The letters PO in <TT>`.po´</TT> files means Portable Object, to
-distinguish it from <TT>`.mo´</TT> files, where MO stands for Machine
+The letters PO in <TT>‘.po’</TT> files means Portable Object, to
+distinguish it from <TT>‘.mo’</TT> files, where MO stands for Machine
Object. This paradigm, as well as the PO file format, is inspired
by the NLS standard developed by Uniforum, and first implemented by
Sun in their Solaris system.
empty translations. Program <CODE>msgmerge</CODE> takes care of adjusting
PO files between releases of the corresponding sources, commenting
obsolete entries, initializing new ones, and updating all source
-line references. Files ending with <TT>`.pot´</TT> are kind of base
+line references. Files ending with <TT>‘.pot’</TT> are kind of base
translation files found in distributions, in PO file format.
</P>
and non-portable. The tools already provided with these systems don't
support all the features of GNU <CODE>gettext</CODE>. Therefore GNU
<CODE>gettext</CODE> uses its own format for MO files. Files ending with
-<TT>`.gmo´</TT> are really MO files, when it is known that these files use
+<TT>‘.gmo’</TT> are really MO files, when it is known that these files use
the GNU format.
</P>
</P>
<PRE>
-Original C Sources ---> PO mode ---> Marked C Sources ---.
- |
- .---------<--- GNU gettext Library |
-.--- make <---+ |
-| `---------<--------------------+-----------'
-| |
-| .-----<--- PACKAGE.pot <--- xgettext <---' .---<--- PO Compendium
-| | | ^
-| | `---. |
-| `---. +---> PO mode ---.
-| +----> msgmerge ------> LANG.po ---->--------' |
-| .---' |
-| | |
-| `-------------<---------------. |
-| +--- New LANG.po <------------------'
-| .--- LANG.gmo <--- msgfmt <---'
-| |
-| `---> install ---> /.../LANG/PACKAGE.mo ---.
-| +---> "Hello world!"
-`-------> install ---> /.../bin/PROGRAM -------'
+@group
+Original C Sources ───> Preparation ───> Marked C Sources ───╮
+ │
+ ╭─────────<─── GNU gettext Library │
+╭─── make <───┤ │
+│ ╰─────────<────────────────────┬───────────────╯
+│ │
+│ ╭─────<─── PACKAGE.pot <─── xgettext <───╯ ╭───<─── PO Compendium
+│ │ │ ↑
+│ │ ╰───╮ │
+│ ╰───╮ ├───> PO editor ───╮
+│ ├────> msgmerge ──────> LANG.po ────>────────╯ │
+│ ╭───╯ │
+│ │ │
+│ ╰─────────────<───────────────╮ │
+│ ├─── New LANG.po <────────────────────╯
+│ ╭─── LANG.gmo <─── msgfmt <───╯
+│ │
+│ ╰───> install ───> /.../LANG/PACKAGE.mo ───╮
+│ ├───> "Hello world!"
+╰───────> install ───> /.../bin/PROGRAM ───────╯
+@end group
</PRE>
-<P>
-The indication <SAMP>`PO mode´</SAMP> appears in two places in this picture,
-and you may safely read it as merely meaning "hand editing", using
-any editor of your choice, really. However, for those of you being
-the lucky users of Emacs, PO mode has been specifically created
-for providing a cozy environment for editing or modifying PO files.
-While editing a PO file, PO mode allows for the easy browsing of
-auxiliary and compendium PO files, as well as for following references into
-the set of C program sources from which PO files have been derived.
-It has a few special features, among which are the interactive marking
-of program strings as translatable, and the validation of PO files
-with easy repositioning to PO file lines showing errors.
-
-</P>
<P>
<A NAME="IDX32"></A>
As a programmer, the first step to bringing GNU <CODE>gettext</CODE>
<P>
<A NAME="IDX34"></A>
<A NAME="IDX35"></A>
-and link against <TT>`libintl.a´</TT> or <TT>`libintl.so´</TT>. Note that on
+and link against <TT>‘libintl.a’</TT> or <TT>‘libintl.so’</TT>. Note that on
GNU systems, you don't need to link with <CODE>libintl</CODE> because the
<CODE>gettext</CODE> library functions are already contained in GNU libc.
That is all you have to change.
<A NAME="IDX37"></A>
Once the C sources have been modified, the <CODE>xgettext</CODE> program
is used to find and extract all translatable strings, and create a
-PO template file out of all these. This <TT>`<VAR>package</VAR>.pot´</TT> file
+PO template file out of all these. This <TT>‘<VAR>package</VAR>.pot’</TT> file
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 <CODE>t</CODE> in <TT>`.pot´</TT> marks this as
+are set to empty. The letter <CODE>t</CODE> in <TT>‘.pot’</TT> marks this as
a Template PO file, not yet oriented towards any particular language.
-See section <A HREF="gettext_5.html#SEC21">5.1 Invoking the <CODE>xgettext</CODE> Program</A>, for more details about how one calls the
+See section <A HREF="gettext_5.html#SEC22">5.1 Invoking the <CODE>xgettext</CODE> Program</A>, for more details about how one calls the
<CODE>xgettext</CODE> program. If you are <EM>really</EM> lazy, you might
be interested at working a lot more right away, and preparing the
-whole distribution setup (see section <A HREF="gettext_13.html#SEC194">13 The Maintainer's View</A>). By doing so, you
+whole distribution setup (see section <A HREF="gettext_13.html#SEC196">13 The Maintainer's View</A>). By doing so, you
spare yourself typing the <CODE>xgettext</CODE> command, as <CODE>make</CODE>
should now generate the proper things automatically for you!
</P>
<P>
-The first time through, there is no <TT>`<VAR>lang</VAR>.po´</TT> yet, so the
+The first time through, there is no <TT>‘<VAR>lang</VAR>.po’</TT> yet, so the
<CODE>msgmerge</CODE> step may be skipped and replaced by a mere copy of
-<TT>`<VAR>package</VAR>.pot´</TT> to <TT>`<VAR>lang</VAR>.po´</TT>, where <VAR>lang</VAR>
-represents the target language. See section <A HREF="gettext_6.html#SEC30">6 Creating a New PO File</A> for details.
+<TT>‘<VAR>package</VAR>.pot’</TT> to <TT>‘<VAR>lang</VAR>.po’</TT>, where <VAR>lang</VAR>
+represents the target language. See section <A HREF="gettext_6.html#SEC31">6 Creating a New PO File</A> for details.
</P>
<P>
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 <A HREF="gettext_12.html#SEC182">12 The Translator's View</A>). You will also find there indications
+manual (see section <A HREF="gettext_12.html#SEC184">12 The Translator's View</A>). 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.
</P>
<P>
-While adding the translated messages into the <TT>`<VAR>lang</VAR>.po´</TT>
-PO file, if you do not have Emacs handy, you are on your own
+While adding the translated messages into the <TT>‘<VAR>lang</VAR>.po’</TT>
+PO file, if you are not using one of the dedicated PO file editors
+(see section <A HREF="gettext_8.html#SEC49">8 Editing PO Files</A>), you are on your own
for ensuring that your efforts fully respect the PO file format, and quoting
conventions (see section <A HREF="gettext_3.html#SEC10">3 The Format of PO Files</A>). This is surely not an impossible task,
-as this is the way many people have handled PO files already for Uniforum or
-Solaris. On the other hand, by using PO mode in Emacs, most details
+as this is the way many people have handled PO files around 1995.
+On the other hand, by using a PO file editor, most details
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 <A HREF="gettext_8.html#SEC53">8.3.2 Main PO mode Commands</A>), you should know how to move between entries
-(see section <A HREF="gettext_8.html#SEC54">8.3.3 Entry Positioning</A>), and how to handle untranslated entries
-(see section <A HREF="gettext_8.html#SEC58">8.3.7 Untranslated Entries</A>).
+some familiarity with PO file editor itself.
</P>
<P>
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 <A HREF="gettext_8.html#SEC65">8.3.14 Using Translation Compendia</A>). Compendium files
+the compendium, updating it (see section <A HREF="gettext_8.html#SEC66">8.3.14 Using Translation Compendia</A>). Compendium files
are meant to be exchanged between members of a given translation team.
</P>
worry about them being translated, as this will come in proper time.
Consequently, when programs and their strings are adjusted in various
ways by maintainers, and for matters usually unrelated to translation,
-<CODE>xgettext</CODE> would construct <TT>`<VAR>package</VAR>.pot´</TT> files which are
-evolving over time, so the translations carried by <TT>`<VAR>lang</VAR>.po´</TT>
+<CODE>xgettext</CODE> would construct <TT>‘<VAR>package</VAR>.pot’</TT> files which are
+evolving over time, so the translations carried by <TT>‘<VAR>lang</VAR>.po’</TT>
are slowly fading out of date.
</P>
</P>
<P>
The <CODE>msgmerge</CODE> program has the purpose of refreshing an already
-existing <TT>`<VAR>lang</VAR>.po´</TT> file, by comparing it with a newer
-<TT>`<VAR>package</VAR>.pot´</TT> template file, extracted by <CODE>xgettext</CODE>
+existing <TT>‘<VAR>lang</VAR>.po’</TT> file, by comparing it with a newer
+<TT>‘<VAR>package</VAR>.pot’</TT> template file, extracted by <CODE>xgettext</CODE>
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, <CODE>msgmerge</CODE> comments out as
-obsolete, in <TT>`<VAR>lang</VAR>.po´</TT>, those already translated entries
-which are no longer used in the program sources (see section <A HREF="gettext_8.html#SEC59">8.3.8 Obsolete Entries</A>). It finally discovers new strings and inserts them in
-the resulting PO file as untranslated entries (see section <A HREF="gettext_8.html#SEC58">8.3.7 Untranslated Entries</A>). See section <A HREF="gettext_7.html#SEC39">7.1 Invoking the <CODE>msgmerge</CODE> Program</A>, for more information about what
+obsolete, in <TT>‘<VAR>lang</VAR>.po’</TT>, those already translated entries
+which are no longer used in the program sources (see section <A HREF="gettext_8.html#SEC60">8.3.8 Obsolete Entries</A>). It finally discovers new strings and inserts them in
+the resulting PO file as untranslated entries (see section <A HREF="gettext_8.html#SEC59">8.3.7 Untranslated Entries</A>). See section <A HREF="gettext_7.html#SEC40">7.1 Invoking the <CODE>msgmerge</CODE> Program</A>, for more information about what
<CODE>msgmerge</CODE> really does.
</P>
<P>
Whatever route or means taken, the goal is to obtain an updated
-<TT>`<VAR>lang</VAR>.po´</TT> file offering translations for all strings.
+<TT>‘<VAR>lang</VAR>.po’</TT> file offering translations for all strings.
</P>
<P>
Once the PO file is complete and dependable, the <CODE>msgfmt</CODE> 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 <A HREF="gettext_10.html#SEC161">10.3 The Format of GNU MO Files</A>). See section <A HREF="gettext_10.html#SEC141">10.1 Invoking the <CODE>msgfmt</CODE> Program</A>, for more information about all modes of execution
+package, whenever needed at runtime (see section <A HREF="gettext_10.html#SEC163">10.3 The Format of GNU MO Files</A>). See section <A HREF="gettext_10.html#SEC143">10.1 Invoking the <CODE>msgfmt</CODE> Program</A>, for more information about all modes of execution
for the <CODE>msgfmt</CODE> program.
</P>
<P>
Finally, the modified and marked C sources are compiled and linked
with the GNU <CODE>gettext</CODE> library, usually through the operation of
-<CODE>make</CODE>, given a suitable <TT>`Makefile´</TT> exists for the project,
+<CODE>make</CODE>, given a suitable <TT>‘Makefile’</TT> 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 <A HREF="gettext_2.html#SEC9">2.2 Magic for End Users</A>), the
</P>
<P><HR><P>
-Go to the first, previous, <A HREF="gettext_2.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the first, previous, <A HREF="gettext_2.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 10 Producing Binary MO Files</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_9.html">previous</A>, <A HREF="gettext_11.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_9.html">previous</A>, <A HREF="gettext_11.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC140" HREF="gettext_toc.html#TOC140">10 Producing Binary MO Files</A></H1>
+<H1><A NAME="SEC142" HREF="gettext_toc.html#TOC142">10 Producing Binary MO Files</A></H1>
-<H2><A NAME="SEC141" HREF="gettext_toc.html#TOC141">10.1 Invoking the <CODE>msgfmt</CODE> Program</A></H2>
+<H2><A NAME="SEC143" HREF="gettext_toc.html#TOC143">10.1 Invoking the <CODE>msgfmt</CODE> Program</A></H2>
<P>
-<A NAME="IDX869"></A>
-<A NAME="IDX870"></A>
+<A NAME="IDX887"></A>
+<A NAME="IDX888"></A>
<PRE>
msgfmt [<VAR>option</VAR>] <VAR>filename</VAR>.po ...
</PRE>
<P>
-<A NAME="IDX871"></A>
+<A NAME="IDX889"></A>
The <CODE>msgfmt</CODE> programs generates a binary message catalog from a textual
translation description.
</P>
-<H3><A NAME="SEC142" HREF="gettext_toc.html#TOC142">10.1.1 Input file location</A></H3>
+<H3><A NAME="SEC144" HREF="gettext_toc.html#TOC144">10.1.1 Input file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`<VAR>filename</VAR>.po ...´</SAMP>
+<DT><SAMP>‘<VAR>filename</VAR>.po ...’</SAMP>
<DD>
-<DT><SAMP>`-D <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-D <VAR>directory</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--directory=<VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘--directory=<VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX872"></A>
-<A NAME="IDX873"></A>
+<A NAME="IDX890"></A>
+<A NAME="IDX891"></A>
Add <VAR>directory</VAR> to the list of directories. Source files are
-searched relative to this list of directories. The resulting <TT>`.po´</TT>
+searched relative to this list of directories. The resulting <TT>‘.po’</TT>
file will be written relative to the current directory, though.
</DL>
<P>
-If an input file is <SAMP>`-´</SAMP>, standard input is read.
+If an input file is <SAMP>‘-’</SAMP>, standard input is read.
</P>
-<H3><A NAME="SEC143" HREF="gettext_toc.html#TOC143">10.1.2 Operation mode</A></H3>
+<H3><A NAME="SEC145" HREF="gettext_toc.html#TOC145">10.1.2 Operation mode</A></H3>
<DL COMPACT>
-<DT><SAMP>`-j´</SAMP>
+<DT><SAMP>‘-j’</SAMP>
<DD>
-<DT><SAMP>`--java´</SAMP>
+<DT><SAMP>‘--java’</SAMP>
<DD>
-<A NAME="IDX874"></A>
-<A NAME="IDX875"></A>
-<A NAME="IDX876"></A>
+<A NAME="IDX892"></A>
+<A NAME="IDX893"></A>
+<A NAME="IDX894"></A>
Java mode: generate a Java <CODE>ResourceBundle</CODE> class.
-<DT><SAMP>`--java2´</SAMP>
+<DT><SAMP>‘--java2’</SAMP>
<DD>
-<A NAME="IDX877"></A>
+<A NAME="IDX895"></A>
Like --java, and assume Java2 (JDK 1.2 or higher).
-<DT><SAMP>`--csharp´</SAMP>
+<DT><SAMP>‘--csharp’</SAMP>
<DD>
-<A NAME="IDX878"></A>
-<A NAME="IDX879"></A>
+<A NAME="IDX896"></A>
+<A NAME="IDX897"></A>
C# mode: generate a .NET .dll file containing a subclass of
<CODE>GettextResourceSet</CODE>.
-<DT><SAMP>`--csharp-resources´</SAMP>
+<DT><SAMP>‘--csharp-resources’</SAMP>
<DD>
-<A NAME="IDX880"></A>
-<A NAME="IDX881"></A>
-C# resources mode: generate a .NET <TT>`.resources´</TT> file.
+<A NAME="IDX898"></A>
+<A NAME="IDX899"></A>
+C# resources mode: generate a .NET <TT>‘.resources’</TT> file.
-<DT><SAMP>`--tcl´</SAMP>
+<DT><SAMP>‘--tcl’</SAMP>
<DD>
-<A NAME="IDX882"></A>
-<A NAME="IDX883"></A>
-Tcl mode: generate a tcl/msgcat <TT>`.msg´</TT> file.
+<A NAME="IDX900"></A>
+<A NAME="IDX901"></A>
+Tcl mode: generate a tcl/msgcat <TT>‘.msg’</TT> file.
-<DT><SAMP>`--qt´</SAMP>
+<DT><SAMP>‘--qt’</SAMP>
<DD>
-<A NAME="IDX884"></A>
-<A NAME="IDX885"></A>
-Qt mode: generate a Qt <TT>`.qm´</TT> file.
+<A NAME="IDX902"></A>
+<A NAME="IDX903"></A>
+Qt mode: generate a Qt <TT>‘.qm’</TT> file.
</DL>
-<H3><A NAME="SEC144" HREF="gettext_toc.html#TOC144">10.1.3 Output file location</A></H3>
+<H3><A NAME="SEC146" HREF="gettext_toc.html#TOC146">10.1.3 Output file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`-o <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-o <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--output-file=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--output-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX886"></A>
-<A NAME="IDX887"></A>
+<A NAME="IDX904"></A>
+<A NAME="IDX905"></A>
Write output to specified file.
-<DT><SAMP>`--strict´</SAMP>
+<DT><SAMP>‘--strict’</SAMP>
<DD>
-<A NAME="IDX888"></A>
+<A NAME="IDX906"></A>
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
same as the domain name. If the strict Uniforum mode is enabled the
-suffix <TT>`.mo´</TT> is added to the file name if it is not already
+suffix <TT>‘.mo’</TT> is added to the file name if it is not already
present.
We find this behaviour of Sun's implementation rather silly and so by
</DL>
<P>
-If the output <VAR>file</VAR> is <SAMP>`-´</SAMP>, output is written to standard output.
+If the output <VAR>file</VAR> is <SAMP>‘-’</SAMP>, output is written to standard output.
</P>
-<H3><A NAME="SEC145" HREF="gettext_toc.html#TOC145">10.1.4 Output file location in Java mode</A></H3>
+<H3><A NAME="SEC147" HREF="gettext_toc.html#TOC147">10.1.4 Output file location in Java mode</A></H3>
<DL COMPACT>
-<DT><SAMP>`-r <VAR>resource</VAR>´</SAMP>
+<DT><SAMP>‘-r <VAR>resource</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--resource=<VAR>resource</VAR>´</SAMP>
+<DT><SAMP>‘--resource=<VAR>resource</VAR>’</SAMP>
<DD>
-<A NAME="IDX889"></A>
-<A NAME="IDX890"></A>
+<A NAME="IDX907"></A>
+<A NAME="IDX908"></A>
Specify the resource name.
-<DT><SAMP>`-l <VAR>locale</VAR>´</SAMP>
+<DT><SAMP>‘-l <VAR>locale</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--locale=<VAR>locale</VAR>´</SAMP>
+<DT><SAMP>‘--locale=<VAR>locale</VAR>’</SAMP>
<DD>
-<A NAME="IDX891"></A>
-<A NAME="IDX892"></A>
+<A NAME="IDX909"></A>
+<A NAME="IDX910"></A>
Specify the locale name, either a language specification of the form <VAR>ll</VAR>
or a combined language and country specification of the form <VAR>ll_CC</VAR>.
-<DT><SAMP>`-d <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-d <VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX893"></A>
+<A NAME="IDX911"></A>
Specify the base directory of classes directory hierarchy.
</DL>
<P>
The class name is determined by appending the locale name to the resource name,
-separated with an underscore. The <SAMP>`-d´</SAMP> option is mandatory. The class
+separated with an underscore. The <SAMP>‘-d’</SAMP> option is mandatory. The class
is written under the specified directory.
</P>
-<H3><A NAME="SEC146" HREF="gettext_toc.html#TOC146">10.1.5 Output file location in C# mode</A></H3>
+<H3><A NAME="SEC148" HREF="gettext_toc.html#TOC148">10.1.5 Output file location in C# mode</A></H3>
<DL COMPACT>
-<DT><SAMP>`-r <VAR>resource</VAR>´</SAMP>
+<DT><SAMP>‘-r <VAR>resource</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--resource=<VAR>resource</VAR>´</SAMP>
+<DT><SAMP>‘--resource=<VAR>resource</VAR>’</SAMP>
<DD>
-<A NAME="IDX894"></A>
-<A NAME="IDX895"></A>
+<A NAME="IDX912"></A>
+<A NAME="IDX913"></A>
Specify the resource name.
-<DT><SAMP>`-l <VAR>locale</VAR>´</SAMP>
+<DT><SAMP>‘-l <VAR>locale</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--locale=<VAR>locale</VAR>´</SAMP>
+<DT><SAMP>‘--locale=<VAR>locale</VAR>’</SAMP>
<DD>
-<A NAME="IDX896"></A>
-<A NAME="IDX897"></A>
+<A NAME="IDX914"></A>
+<A NAME="IDX915"></A>
Specify the locale name, either a language specification of the form <VAR>ll</VAR>
or a combined language and country specification of the form <VAR>ll_CC</VAR>.
-<DT><SAMP>`-d <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-d <VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX898"></A>
-Specify the base directory for locale dependent <TT>`.dll´</TT> files.
+<A NAME="IDX916"></A>
+Specify the base directory for locale dependent <TT>‘.dll’</TT> files.
</DL>
<P>
-The <SAMP>`-l´</SAMP> and <SAMP>`-d´</SAMP> options are mandatory. The <TT>`.dll´</TT> file is
+The <SAMP>‘-l’</SAMP> and <SAMP>‘-d’</SAMP> options are mandatory. The <TT>‘.dll’</TT> file is
written in a subdirectory of the specified directory whose name depends on the
locale.
</P>
-<H3><A NAME="SEC147" HREF="gettext_toc.html#TOC147">10.1.6 Output file location in Tcl mode</A></H3>
+<H3><A NAME="SEC149" HREF="gettext_toc.html#TOC149">10.1.6 Output file location in Tcl mode</A></H3>
<DL COMPACT>
-<DT><SAMP>`-l <VAR>locale</VAR>´</SAMP>
+<DT><SAMP>‘-l <VAR>locale</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--locale=<VAR>locale</VAR>´</SAMP>
+<DT><SAMP>‘--locale=<VAR>locale</VAR>’</SAMP>
<DD>
-<A NAME="IDX899"></A>
-<A NAME="IDX900"></A>
+<A NAME="IDX917"></A>
+<A NAME="IDX918"></A>
Specify the locale name, either a language specification of the form <VAR>ll</VAR>
or a combined language and country specification of the form <VAR>ll_CC</VAR>.
-<DT><SAMP>`-d <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-d <VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX901"></A>
-Specify the base directory of <TT>`.msg´</TT> message catalogs.
+<A NAME="IDX919"></A>
+Specify the base directory of <TT>‘.msg’</TT> message catalogs.
</DL>
<P>
-The <SAMP>`-l´</SAMP> and <SAMP>`-d´</SAMP> options are mandatory. The <TT>`.msg´</TT> file is
+The <SAMP>‘-l’</SAMP> and <SAMP>‘-d’</SAMP> options are mandatory. The <TT>‘.msg’</TT> file is
written in the specified directory.
</P>
-<H3><A NAME="SEC148" HREF="gettext_toc.html#TOC148">10.1.7 Input file syntax</A></H3>
+<H3><A NAME="SEC150" HREF="gettext_toc.html#TOC150">10.1.7 Input file syntax</A></H3>
<DL COMPACT>
-<DT><SAMP>`-P´</SAMP>
+<DT><SAMP>‘-P’</SAMP>
<DD>
-<DT><SAMP>`--properties-input´</SAMP>
+<DT><SAMP>‘--properties-input’</SAMP>
<DD>
-<A NAME="IDX902"></A>
-<A NAME="IDX903"></A>
+<A NAME="IDX920"></A>
+<A NAME="IDX921"></A>
Assume the input files are Java ResourceBundles in Java <CODE>.properties</CODE>
syntax, not in PO file syntax.
-<DT><SAMP>`--stringtable-input´</SAMP>
+<DT><SAMP>‘--stringtable-input’</SAMP>
<DD>
-<A NAME="IDX904"></A>
+<A NAME="IDX922"></A>
Assume the input files are NeXTstep/GNUstep localized resource files in
<CODE>.strings</CODE> syntax, not in PO file syntax.
-<H3><A NAME="SEC149" HREF="gettext_toc.html#TOC149">10.1.8 Input file interpretation</A></H3>
+<H3><A NAME="SEC151" HREF="gettext_toc.html#TOC151">10.1.8 Input file interpretation</A></H3>
<DL COMPACT>
-<DT><SAMP>`-c´</SAMP>
+<DT><SAMP>‘-c’</SAMP>
<DD>
-<DT><SAMP>`--check´</SAMP>
+<DT><SAMP>‘--check’</SAMP>
<DD>
-<A NAME="IDX905"></A>
-<A NAME="IDX906"></A>
+<A NAME="IDX923"></A>
+<A NAME="IDX924"></A>
Perform all the checks implied by <CODE>--check-format</CODE>, <CODE>--check-header</CODE>,
<CODE>--check-domain</CODE>.
-<DT><SAMP>`--check-format´</SAMP>
+<DT><SAMP>‘--check-format’</SAMP>
<DD>
-<A NAME="IDX907"></A>
-<A NAME="IDX908"></A>
+<A NAME="IDX925"></A>
+<A NAME="IDX926"></A>
Check language dependent format strings.
If the string represents a format string used in a
<CODE>printf</CODE>-like function both strings should have the same number of
-<SAMP>`%´</SAMP> format specifiers, with matching types. If the flag
+<SAMP>‘%’</SAMP> format specifiers, with matching types. If the flag
<CODE>c-format</CODE> or <CODE>possible-c-format</CODE> appears in the special
comment <KBD>#,</KBD> for this entry a check is performed. For example, the
-check will diagnose using <SAMP>`%.*s´</SAMP> against <SAMP>`%s´</SAMP>, or <SAMP>`%d´</SAMP>
-against <SAMP>`%s´</SAMP>, or <SAMP>`%d´</SAMP> against <SAMP>`%x´</SAMP>. It can even handle
+check will diagnose using <SAMP>‘%.*s’</SAMP> against <SAMP>‘%s’</SAMP>, or <SAMP>‘%d’</SAMP>
+against <SAMP>‘%s’</SAMP>, or <SAMP>‘%d’</SAMP> against <SAMP>‘%x’</SAMP>. It can even handle
positional parameters.
Normally the <CODE>xgettext</CODE> program automatically decides whether a
errors where there are none.
To solve this problem the programmer can dictate the decision to the
-<CODE>xgettext</CODE> program (see section <A HREF="gettext_15.html#SEC228">15.3.1 C Format Strings</A>). The translator should not
+<CODE>xgettext</CODE> program (see section <A HREF="gettext_15.html#SEC231">15.3.1 C Format Strings</A>). The translator should not
consider removing the flag from the <KBD>#,</KBD> line. This "fix" would be
reversed again as soon as <CODE>msgmerge</CODE> is called the next time.
-<DT><SAMP>`--check-header´</SAMP>
+<DT><SAMP>‘--check-header’</SAMP>
<DD>
-<A NAME="IDX909"></A>
-Verify presence and contents of the header entry. See section <A HREF="gettext_6.html#SEC37">6.2 Filling in the Header Entry</A>,
+<A NAME="IDX927"></A>
+Verify presence and contents of the header entry. See section <A HREF="gettext_6.html#SEC38">6.2 Filling in the Header Entry</A>,
for a description of the various fields in the header entry.
-<DT><SAMP>`--check-domain´</SAMP>
+<DT><SAMP>‘--check-domain’</SAMP>
<DD>
-<A NAME="IDX910"></A>
+<A NAME="IDX928"></A>
Check for conflicts between domain directives and the <CODE>--output-file</CODE>
option
-<DT><SAMP>`-C´</SAMP>
+<DT><SAMP>‘-C’</SAMP>
<DD>
-<DT><SAMP>`--check-compatibility´</SAMP>
+<DT><SAMP>‘--check-compatibility’</SAMP>
<DD>
-<A NAME="IDX911"></A>
-<A NAME="IDX912"></A>
-<A NAME="IDX913"></A>
+<A NAME="IDX929"></A>
+<A NAME="IDX930"></A>
+<A NAME="IDX931"></A>
Check that GNU msgfmt behaves like X/Open msgfmt. This will give an error
when attempting to use the GNU extensions.
-<DT><SAMP>`--check-accelerators[=<VAR>char</VAR>]´</SAMP>
+<DT><SAMP>‘--check-accelerators[=<VAR>char</VAR>]’</SAMP>
<DD>
-<A NAME="IDX914"></A>
-<A NAME="IDX915"></A>
-<A NAME="IDX916"></A>
-<A NAME="IDX917"></A>
+<A NAME="IDX932"></A>
+<A NAME="IDX933"></A>
+<A NAME="IDX934"></A>
+<A NAME="IDX935"></A>
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 <SAMP>`&´</SAMP> character.
+item string is designated by an immediately preceding <SAMP>‘&’</SAMP> character.
Sometimes a keyboard accelerator is also called "keyboard mnemonic".
This check verifies that if the untranslated string has exactly one
-<SAMP>`&´</SAMP> character, the translated string has exactly one <SAMP>`&´</SAMP> as well.
+<SAMP>‘&’</SAMP> character, the translated string has exactly one <SAMP>‘&’</SAMP> as well.
If this option is given with a <VAR>char</VAR> argument, this <VAR>char</VAR> should
be a non-alphanumeric character and is used as keyboard accelerator mark
-instead of <SAMP>`&´</SAMP>.
+instead of <SAMP>‘&’</SAMP>.
-<DT><SAMP>`-f´</SAMP>
+<DT><SAMP>‘-f’</SAMP>
<DD>
-<DT><SAMP>`--use-fuzzy´</SAMP>
+<DT><SAMP>‘--use-fuzzy’</SAMP>
<DD>
-<A NAME="IDX918"></A>
-<A NAME="IDX919"></A>
-<A NAME="IDX920"></A>
+<A NAME="IDX936"></A>
+<A NAME="IDX937"></A>
+<A NAME="IDX938"></A>
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.
-<H3><A NAME="SEC150" HREF="gettext_toc.html#TOC150">10.1.9 Output details</A></H3>
+<H3><A NAME="SEC152" HREF="gettext_toc.html#TOC152">10.1.9 Output details</A></H3>
<DL COMPACT>
-<DT><SAMP>`-a <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-a <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--alignment=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--alignment=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX921"></A>
-<A NAME="IDX922"></A>
+<A NAME="IDX939"></A>
+<A NAME="IDX940"></A>
Align strings to <VAR>number</VAR> bytes (default: 1).
-<DT><SAMP>`--no-hash´</SAMP>
+<DT><SAMP>‘--no-hash’</SAMP>
<DD>
-<A NAME="IDX923"></A>
+<A NAME="IDX941"></A>
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).
-<H3><A NAME="SEC151" HREF="gettext_toc.html#TOC151">10.1.10 Informative output</A></H3>
+<H3><A NAME="SEC153" HREF="gettext_toc.html#TOC153">10.1.10 Informative output</A></H3>
<DL COMPACT>
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX924"></A>
-<A NAME="IDX925"></A>
+<A NAME="IDX942"></A>
+<A NAME="IDX943"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX926"></A>
-<A NAME="IDX927"></A>
+<A NAME="IDX944"></A>
+<A NAME="IDX945"></A>
Output version information and exit.
-<DT><SAMP>`--statistics´</SAMP>
+<DT><SAMP>‘--statistics’</SAMP>
<DD>
-<A NAME="IDX928"></A>
+<A NAME="IDX946"></A>
Print statistics about translations.
-<DT><SAMP>`-v´</SAMP>
+<DT><SAMP>‘-v’</SAMP>
<DD>
-<DT><SAMP>`--verbose´</SAMP>
+<DT><SAMP>‘--verbose’</SAMP>
<DD>
-<A NAME="IDX929"></A>
-<A NAME="IDX930"></A>
+<A NAME="IDX947"></A>
+<A NAME="IDX948"></A>
Increase verbosity level.
</DL>
-<H2><A NAME="SEC152" HREF="gettext_toc.html#TOC152">10.2 Invoking the <CODE>msgunfmt</CODE> Program</A></H2>
+<H2><A NAME="SEC154" HREF="gettext_toc.html#TOC154">10.2 Invoking the <CODE>msgunfmt</CODE> Program</A></H2>
<P>
-<A NAME="IDX931"></A>
-<A NAME="IDX932"></A>
+<A NAME="IDX949"></A>
+<A NAME="IDX950"></A>
<PRE>
msgunfmt [<VAR>option</VAR>] [<VAR>file</VAR>]...
</PRE>
<P>
-<A NAME="IDX933"></A>
+<A NAME="IDX951"></A>
The <CODE>msgunfmt</CODE> program converts a binary message catalog to a
Uniforum style .po file.
</P>
-<H3><A NAME="SEC153" HREF="gettext_toc.html#TOC153">10.2.1 Operation mode</A></H3>
+<H3><A NAME="SEC155" HREF="gettext_toc.html#TOC155">10.2.1 Operation mode</A></H3>
<DL COMPACT>
-<DT><SAMP>`-j´</SAMP>
+<DT><SAMP>‘-j’</SAMP>
<DD>
-<DT><SAMP>`--java´</SAMP>
+<DT><SAMP>‘--java’</SAMP>
<DD>
-<A NAME="IDX934"></A>
-<A NAME="IDX935"></A>
-<A NAME="IDX936"></A>
+<A NAME="IDX952"></A>
+<A NAME="IDX953"></A>
+<A NAME="IDX954"></A>
Java mode: input is a Java <CODE>ResourceBundle</CODE> class.
-<DT><SAMP>`--csharp´</SAMP>
+<DT><SAMP>‘--csharp’</SAMP>
<DD>
-<A NAME="IDX937"></A>
-<A NAME="IDX938"></A>
+<A NAME="IDX955"></A>
+<A NAME="IDX956"></A>
C# mode: input is a .NET .dll file containing a subclass of
<CODE>GettextResourceSet</CODE>.
-<DT><SAMP>`--csharp-resources´</SAMP>
+<DT><SAMP>‘--csharp-resources’</SAMP>
<DD>
-<A NAME="IDX939"></A>
-<A NAME="IDX940"></A>
-C# resources mode: input is a .NET <TT>`.resources´</TT> file.
+<A NAME="IDX957"></A>
+<A NAME="IDX958"></A>
+C# resources mode: input is a .NET <TT>‘.resources’</TT> file.
-<DT><SAMP>`--tcl´</SAMP>
+<DT><SAMP>‘--tcl’</SAMP>
<DD>
-<A NAME="IDX941"></A>
-<A NAME="IDX942"></A>
-Tcl mode: input is a tcl/msgcat <TT>`.msg´</TT> file.
+<A NAME="IDX959"></A>
+<A NAME="IDX960"></A>
+Tcl mode: input is a tcl/msgcat <TT>‘.msg’</TT> file.
</DL>
-<H3><A NAME="SEC154" HREF="gettext_toc.html#TOC154">10.2.2 Input file location</A></H3>
+<H3><A NAME="SEC156" HREF="gettext_toc.html#TOC156">10.2.2 Input file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`<VAR>file</VAR> ...´</SAMP>
+<DT><SAMP>‘<VAR>file</VAR> ...’</SAMP>
<DD>
Input .mo files.
</DL>
<P>
-If no input <VAR>file</VAR> is given or if it is <SAMP>`-´</SAMP>, standard input is read.
+If no input <VAR>file</VAR> is given or if it is <SAMP>‘-’</SAMP>, standard input is read.
</P>
-<H3><A NAME="SEC155" HREF="gettext_toc.html#TOC155">10.2.3 Input file location in Java mode</A></H3>
+<H3><A NAME="SEC157" HREF="gettext_toc.html#TOC157">10.2.3 Input file location in Java mode</A></H3>
<DL COMPACT>
-<DT><SAMP>`-r <VAR>resource</VAR>´</SAMP>
+<DT><SAMP>‘-r <VAR>resource</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--resource=<VAR>resource</VAR>´</SAMP>
+<DT><SAMP>‘--resource=<VAR>resource</VAR>’</SAMP>
<DD>
-<A NAME="IDX943"></A>
-<A NAME="IDX944"></A>
+<A NAME="IDX961"></A>
+<A NAME="IDX962"></A>
Specify the resource name.
-<DT><SAMP>`-l <VAR>locale</VAR>´</SAMP>
+<DT><SAMP>‘-l <VAR>locale</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--locale=<VAR>locale</VAR>´</SAMP>
+<DT><SAMP>‘--locale=<VAR>locale</VAR>’</SAMP>
<DD>
-<A NAME="IDX945"></A>
-<A NAME="IDX946"></A>
+<A NAME="IDX963"></A>
+<A NAME="IDX964"></A>
Specify the locale name, either a language specification of the form <VAR>ll</VAR>
or a combined language and country specification of the form <VAR>ll_CC</VAR>.
</P>
-<H3><A NAME="SEC156" HREF="gettext_toc.html#TOC156">10.2.4 Input file location in C# mode</A></H3>
+<H3><A NAME="SEC158" HREF="gettext_toc.html#TOC158">10.2.4 Input file location in C# mode</A></H3>
<DL COMPACT>
-<DT><SAMP>`-r <VAR>resource</VAR>´</SAMP>
+<DT><SAMP>‘-r <VAR>resource</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--resource=<VAR>resource</VAR>´</SAMP>
+<DT><SAMP>‘--resource=<VAR>resource</VAR>’</SAMP>
<DD>
-<A NAME="IDX947"></A>
-<A NAME="IDX948"></A>
+<A NAME="IDX965"></A>
+<A NAME="IDX966"></A>
Specify the resource name.
-<DT><SAMP>`-l <VAR>locale</VAR>´</SAMP>
+<DT><SAMP>‘-l <VAR>locale</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--locale=<VAR>locale</VAR>´</SAMP>
+<DT><SAMP>‘--locale=<VAR>locale</VAR>’</SAMP>
<DD>
-<A NAME="IDX949"></A>
-<A NAME="IDX950"></A>
+<A NAME="IDX967"></A>
+<A NAME="IDX968"></A>
Specify the locale name, either a language specification of the form <VAR>ll</VAR>
or a combined language and country specification of the form <VAR>ll_CC</VAR>.
-<DT><SAMP>`-d <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-d <VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX951"></A>
-Specify the base directory for locale dependent <TT>`.dll´</TT> files.
+<A NAME="IDX969"></A>
+Specify the base directory for locale dependent <TT>‘.dll’</TT> files.
</DL>
<P>
-The <SAMP>`-l´</SAMP> and <SAMP>`-d´</SAMP> options are mandatory. The <TT>`.msg´</TT> file is
+The <SAMP>‘-l’</SAMP> and <SAMP>‘-d’</SAMP> options are mandatory. The <TT>‘.msg’</TT> file is
located in a subdirectory of the specified directory whose name depends on the
locale.
</P>
-<H3><A NAME="SEC157" HREF="gettext_toc.html#TOC157">10.2.5 Input file location in Tcl mode</A></H3>
+<H3><A NAME="SEC159" HREF="gettext_toc.html#TOC159">10.2.5 Input file location in Tcl mode</A></H3>
<DL COMPACT>
-<DT><SAMP>`-l <VAR>locale</VAR>´</SAMP>
+<DT><SAMP>‘-l <VAR>locale</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--locale=<VAR>locale</VAR>´</SAMP>
+<DT><SAMP>‘--locale=<VAR>locale</VAR>’</SAMP>
<DD>
-<A NAME="IDX952"></A>
-<A NAME="IDX953"></A>
+<A NAME="IDX970"></A>
+<A NAME="IDX971"></A>
Specify the locale name, either a language specification of the form <VAR>ll</VAR>
or a combined language and country specification of the form <VAR>ll_CC</VAR>.
-<DT><SAMP>`-d <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-d <VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX954"></A>
-Specify the base directory of <TT>`.msg´</TT> message catalogs.
+<A NAME="IDX972"></A>
+Specify the base directory of <TT>‘.msg’</TT> message catalogs.
</DL>
<P>
-The <SAMP>`-l´</SAMP> and <SAMP>`-d´</SAMP> options are mandatory. The <TT>`.msg´</TT> file is
+The <SAMP>‘-l’</SAMP> and <SAMP>‘-d’</SAMP> options are mandatory. The <TT>‘.msg’</TT> file is
located in the specified directory.
</P>
-<H3><A NAME="SEC158" HREF="gettext_toc.html#TOC158">10.2.6 Output file location</A></H3>
+<H3><A NAME="SEC160" HREF="gettext_toc.html#TOC160">10.2.6 Output file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`-o <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-o <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--output-file=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--output-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX955"></A>
-<A NAME="IDX956"></A>
+<A NAME="IDX973"></A>
+<A NAME="IDX974"></A>
Write output to specified file.
</DL>
<P>
The results are written to standard output if no output file is specified
-or if it is <SAMP>`-´</SAMP>.
+or if it is <SAMP>‘-’</SAMP>.
</P>
-<H3><A NAME="SEC159" HREF="gettext_toc.html#TOC159">10.2.7 Output details</A></H3>
+<H3><A NAME="SEC161" HREF="gettext_toc.html#TOC161">10.2.7 Output details</A></H3>
<DL COMPACT>
-<DT><SAMP>`--force-po´</SAMP>
+<DT><SAMP>‘--force-po’</SAMP>
<DD>
-<A NAME="IDX957"></A>
+<A NAME="IDX975"></A>
Always write an output file even if it contains no message.
-<DT><SAMP>`-i´</SAMP>
+<DT><SAMP>‘-i’</SAMP>
<DD>
-<DT><SAMP>`--indent´</SAMP>
+<DT><SAMP>‘--indent’</SAMP>
<DD>
-<A NAME="IDX958"></A>
-<A NAME="IDX959"></A>
+<A NAME="IDX976"></A>
+<A NAME="IDX977"></A>
Write the .po file using indented style.
-<DT><SAMP>`--strict´</SAMP>
+<DT><SAMP>‘--strict’</SAMP>
<DD>
-<A NAME="IDX960"></A>
+<A NAME="IDX978"></A>
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
-<DT><SAMP>`-p´</SAMP>
+<DT><SAMP>‘-p’</SAMP>
<DD>
-<DT><SAMP>`--properties-output´</SAMP>
+<DT><SAMP>‘--properties-output’</SAMP>
<DD>
-<A NAME="IDX961"></A>
-<A NAME="IDX962"></A>
+<A NAME="IDX979"></A>
+<A NAME="IDX980"></A>
Write out a Java ResourceBundle in Java <CODE>.properties</CODE> syntax. Note
that this file format doesn't support plural forms and silently drops
obsolete messages.
-<DT><SAMP>`--stringtable-output´</SAMP>
+<DT><SAMP>‘--stringtable-output’</SAMP>
<DD>
-<A NAME="IDX963"></A>
+<A NAME="IDX981"></A>
Write out a NeXTstep/GNUstep localized resource file in <CODE>.strings</CODE> syntax.
Note that this file format doesn't support plural forms.
-<DT><SAMP>`-w <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-w <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--width=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--width=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX964"></A>
-<A NAME="IDX965"></A>
+<A NAME="IDX982"></A>
+<A NAME="IDX983"></A>
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 <VAR>number</VAR>.
-<DT><SAMP>`--no-wrap´</SAMP>
+<DT><SAMP>‘--no-wrap’</SAMP>
<DD>
-<A NAME="IDX966"></A>
+<A NAME="IDX984"></A>
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.
-<DT><SAMP>`-s´</SAMP>
+<DT><SAMP>‘-s’</SAMP>
<DD>
-<DT><SAMP>`--sort-output´</SAMP>
+<DT><SAMP>‘--sort-output’</SAMP>
<DD>
-<A NAME="IDX967"></A>
-<A NAME="IDX968"></A>
-<A NAME="IDX969"></A>
+<A NAME="IDX985"></A>
+<A NAME="IDX986"></A>
+<A NAME="IDX987"></A>
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
-<H3><A NAME="SEC160" HREF="gettext_toc.html#TOC160">10.2.8 Informative output</A></H3>
+<H3><A NAME="SEC162" HREF="gettext_toc.html#TOC162">10.2.8 Informative output</A></H3>
<DL COMPACT>
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX970"></A>
-<A NAME="IDX971"></A>
+<A NAME="IDX988"></A>
+<A NAME="IDX989"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX972"></A>
-<A NAME="IDX973"></A>
+<A NAME="IDX990"></A>
+<A NAME="IDX991"></A>
Output version information and exit.
-<DT><SAMP>`-v´</SAMP>
+<DT><SAMP>‘-v’</SAMP>
<DD>
-<DT><SAMP>`--verbose´</SAMP>
+<DT><SAMP>‘--verbose’</SAMP>
<DD>
-<A NAME="IDX974"></A>
-<A NAME="IDX975"></A>
+<A NAME="IDX992"></A>
+<A NAME="IDX993"></A>
Increase verbosity level.
</DL>
-<H2><A NAME="SEC161" HREF="gettext_toc.html#TOC161">10.3 The Format of GNU MO Files</A></H2>
+<H2><A NAME="SEC163" HREF="gettext_toc.html#TOC163">10.3 The Format of GNU MO Files</A></H2>
<P>
-<A NAME="IDX976"></A>
-<A NAME="IDX977"></A>
+<A NAME="IDX994"></A>
+<A NAME="IDX995"></A>
</P>
<P>
</P>
<P>
-<A NAME="IDX978"></A>
+<A NAME="IDX996"></A>
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
that the readers of MO files can distinguish new formats from old
ones, so that both can be handled correctly. The version is kept
separate from the magic number, instead of using different magic
-numbers for different formats, mainly because <TT>`/etc/magic´</TT> is
+numbers for different formats, mainly because <TT>‘/etc/magic’</TT> is
not updated often. It might be better to have magic separated from
internal format version identification.
</P>
<P>
-<A NAME="IDX979"></A>
+<A NAME="IDX997"></A>
The size <VAR>S</VAR> 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
</P>
<P>
-<A NAME="IDX980"></A>
+<A NAME="IDX998"></A>
+Contexts are stored by storing the concatenation of the context, a
+<KBD>EOT</KBD> byte, and the original string, instead of the original string.
+
+</P>
+<P>
+<A NAME="IDX999"></A>
Plural forms are stored by letting the plural of the original string
follow the singular of the original string, separated through a
<KBD>NUL</KBD> byte. The length which appears in the string descriptor
implement wide characters right in MO files, where <KBD>NUL</KBD> bytes may
accidently appear. (No, we don't want to have wide characters in MO
files. They would make the file unnecessarily large, and the
-<SAMP>`wchar_t´</SAMP> type being platform dependent, MO files would be
+<SAMP>‘wchar_t’</SAMP> type being platform dependent, MO files would be
platform dependent as well.)
</P>
</PRE>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_9.html">previous</A>, <A HREF="gettext_11.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_9.html">previous</A>, <A HREF="gettext_11.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 11 The Programmer's View</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_10.html">previous</A>, <A HREF="gettext_12.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_10.html">previous</A>, <A HREF="gettext_12.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC162" HREF="gettext_toc.html#TOC162">11 The Programmer's View</A></H1>
+<H1><A NAME="SEC164" HREF="gettext_toc.html#TOC164">11 The Programmer's View</A></H1>
<P>
One aim of the current message catalog implementation provided by
-<H2><A NAME="SEC163" HREF="gettext_toc.html#TOC163">11.1 About <CODE>catgets</CODE></A></H2>
+<H2><A NAME="SEC165" HREF="gettext_toc.html#TOC165">11.1 About <CODE>catgets</CODE></A></H2>
<P>
-<A NAME="IDX981"></A>
+<A NAME="IDX1000"></A>
</P>
<P>
-<H3><A NAME="SEC164" HREF="gettext_toc.html#TOC164">11.1.1 The Interface</A></H3>
+<H3><A NAME="SEC166" HREF="gettext_toc.html#TOC166">11.1.1 The Interface</A></H3>
<P>
-<A NAME="IDX982"></A>
+<A NAME="IDX1001"></A>
</P>
<P>
</P>
<P>
-<A NAME="IDX983"></A>
+<A NAME="IDX1002"></A>
<CODE>catopen</CODE> is used like in this:
</P>
</P>
<P>
-<A NAME="IDX984"></A>
+<A NAME="IDX1003"></A>
This handle is of course used in the <CODE>catgets</CODE> function which can
be used like this:
</P>
<P>
-<A NAME="IDX985"></A>
+<A NAME="IDX1004"></A>
The last of these functions is used and behaves as expected:
</P>
</P>
-<H3><A NAME="SEC165" HREF="gettext_toc.html#TOC165">11.1.2 Problems with the <CODE>catgets</CODE> Interface?!</A></H3>
+<H3><A NAME="SEC167" HREF="gettext_toc.html#TOC167">11.1.2 Problems with the <CODE>catgets</CODE> Interface?!</A></H3>
<P>
-<A NAME="IDX986"></A>
+<A NAME="IDX1005"></A>
</P>
<P>
</P>
-<H2><A NAME="SEC166" HREF="gettext_toc.html#TOC166">11.2 About <CODE>gettext</CODE></A></H2>
+<H2><A NAME="SEC168" HREF="gettext_toc.html#TOC168">11.2 About <CODE>gettext</CODE></A></H2>
<P>
-<A NAME="IDX987"></A>
+<A NAME="IDX1006"></A>
</P>
<P>
method of normal file handling (open-use-close) and that it does not
burden the programmer with so many tasks, 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 <A HREF="gettext_11.html#SEC174">11.3 Comparing the Two Interfaces</A> for a more
+itself (how long or short it is). See section <A HREF="gettext_11.html#SEC176">11.3 Comparing the Two Interfaces</A> for a more
detailed comparison of the two methods.
</P>
-<H3><A NAME="SEC167" HREF="gettext_toc.html#TOC167">11.2.1 The Interface</A></H3>
+<H3><A NAME="SEC169" HREF="gettext_toc.html#TOC169">11.2.1 The Interface</A></H3>
<P>
-<A NAME="IDX988"></A>
+<A NAME="IDX1007"></A>
</P>
<P>
</P>
-<H3><A NAME="SEC168" HREF="gettext_toc.html#TOC168">11.2.2 Solving Ambiguities</A></H3>
+<H3><A NAME="SEC170" HREF="gettext_toc.html#TOC170">11.2.2 Solving Ambiguities</A></H3>
<P>
-<A NAME="IDX989"></A>
-<A NAME="IDX990"></A>
-<A NAME="IDX991"></A>
+<A NAME="IDX1008"></A>
+<A NAME="IDX1009"></A>
+<A NAME="IDX1010"></A>
</P>
<P>
</P>
-<H3><A NAME="SEC169" HREF="gettext_toc.html#TOC169">11.2.3 Locating Message Catalog Files</A></H3>
+<H3><A NAME="SEC171" HREF="gettext_toc.html#TOC171">11.2.3 Locating Message Catalog Files</A></H3>
<P>
-<A NAME="IDX992"></A>
+<A NAME="IDX1011"></A>
</P>
<P>
</P>
-<H3><A NAME="SEC170" HREF="gettext_toc.html#TOC170">11.2.4 How to specify the output character set <CODE>gettext</CODE> uses</A></H3>
+<H3><A NAME="SEC172" HREF="gettext_toc.html#TOC172">11.2.4 How to specify the output character set <CODE>gettext</CODE> uses</A></H3>
<P>
-<A NAME="IDX993"></A>
-<A NAME="IDX994"></A>
+<A NAME="IDX1012"></A>
+<A NAME="IDX1013"></A>
</P>
<P>
<P>
<DL>
<DT><U>Function:</U> char * <B>bind_textdomain_codeset</B> <I>(const char *<VAR>domainname</VAR>, const char *<VAR>codeset</VAR>)</I>
-<DD><A NAME="IDX995"></A>
+<DD><A NAME="IDX1014"></A>
The <CODE>bind_textdomain_codeset</CODE> function can be used to specify the
output character set for message catalogs for domain <VAR>domainname</VAR>.
The <VAR>codeset</VAR> argument must be a valid codeset name which can be used
</P>
-<H3><A NAME="SEC171" HREF="gettext_toc.html#TOC171">11.2.5 Additional functions for plural forms</A></H3>
+<H3><A NAME="SEC173" HREF="gettext_toc.html#TOC173">11.2.5 Using contexts for solving ambiguities</A></H3>
+<P>
+<A NAME="IDX1015"></A>
+<A NAME="IDX1016"></A>
+<A NAME="IDX1017"></A>
+<A NAME="IDX1018"></A>
+
+</P>
+<P>
+One place where the <CODE>gettext</CODE> functions, if used normally, have big
+problems is within programs with graphical user interfaces (GUIs). The
+problem is that many of the strings which have to be translated are very
+short. They have to appear in pull-down menus which restricts the
+length. But strings which are not containing entire sentences or at
+least large fragments of a sentence may appear in more than one
+situation in the program but might have different translations. This is
+especially true for the one-word strings which are frequently used in
+GUI programs.
+
+</P>
<P>
-<A NAME="IDX996"></A>
+As a consequence many people say that the <CODE>gettext</CODE> approach is
+wrong and instead <CODE>catgets</CODE> should be used which indeed does not
+have this problem. But there is a very simple and powerful method to
+handle this kind of problems with the <CODE>gettext</CODE> functions.
+
+</P>
+<P>
+Contexts can be added to strings to be translated. A context dependent
+translation lookup is when a translation for a given string is searched,
+that is limited to a given context. The translation for the same string
+in a different context can be different. The different translations of
+the same string in different contexts can be stored in the in the same
+MO file, and can be edited by the translator in the same PO file.
+
+</P>
+<P>
+The <TT>‘gettext.h’</TT> include file contains the lookup macros for strings
+with contexts. They are implemented as thin macros and inline functions
+over the functions from <CODE><libintl.h></CODE>.
+
+</P>
+<P>
+<A NAME="IDX1019"></A>
+
+<PRE>
+const char *pgettext (const char *msgctxt, const char *msgid);
+</PRE>
+
+<P>
+In a call of this macro, <VAR>msgctxt</VAR> and <VAR>msgid</VAR> must be string
+literals. The macro returns the translation of <VAR>msgid</VAR>, restricted
+to the context given by <VAR>msgctxt</VAR>.
+
+</P>
+<P>
+The <VAR>msgctxt</VAR> string is visible in the PO file to the translator.
+You should try to make it somehow canonical and never changing. Because
+every time you change an <VAR>msgctxt</VAR>, the translator will have to review
+the translation of <VAR>msgid</VAR>.
+
+</P>
+<P>
+Finding a canonical <VAR>msgctxt</VAR> string that doesn't change over time can
+be hard. But you shouldn't use the file name or class name containing the
+<CODE>pgettext</CODE> call -- because it is a common development task to rename
+a file or a class, and it shouldn't cause translator work. Also you shouldn't
+use a comment in the form of a complete English sentence as <VAR>msgctxt</VAR> --
+because orthography or grammar changes are often applied to such sentences,
+and again, it shouldn't force the translator to do a review.
+
+</P>
+<P>
+The <SAMP>‘p’</SAMP> in <SAMP>‘pgettext’</SAMP> stands for “particular”: <CODE>pgettext</CODE>
+fetches a particular translation of the <VAR>msgid</VAR>.
+
+</P>
+<P>
+<A NAME="IDX1020"></A>
+<A NAME="IDX1021"></A>
+
+<PRE>
+const char *dpgettext (const char *domain_name,
+ const char *msgctxt, const char *msgid);
+const char *dcpgettext (const char *domain_name,
+ const char *msgctxt, const char *msgid,
+ int category);
+</PRE>
+
+<P>
+These are generalizations of <CODE>pgettext</CODE>. They behave similarly to
+<CODE>dgettext</CODE> and <CODE>dcgettext</CODE>, respectively. The <VAR>domain_name</VAR>
+argument defines the translation domain. The <VAR>category</VAR> argument
+allows to use another locale facet than <CODE>LC_MESSAGES</CODE>.
+
+</P>
+<P>
+As as example consider the following fictional situation. A GUI program
+has a menu bar with the following entries:
+
+</P>
+
+<PRE>
++------------+------------+--------------------------------------+
+| File | Printer | |
++------------+------------+--------------------------------------+
+| Open | | Select |
+| New | | Open |
++----------+ | Connect |
+ +----------+
+</PRE>
+
+<P>
+To have the strings <CODE>File</CODE>, <CODE>Printer</CODE>, <CODE>Open</CODE>,
+<CODE>New</CODE>, <CODE>Select</CODE>, and <CODE>Connect</CODE> translated there has to be
+at some point in the code a call to a function of the <CODE>gettext</CODE>
+family. But in two places the string passed into the function would be
+<CODE>Open</CODE>. The translations might not be the same and therefore we
+are in the dilemma described above.
+
+</P>
+<P>
+What distinguishes the two places is the menu path from the menu root to
+the particular menu entries:
+
+</P>
+
+<PRE>
+Menu|File
+Menu|Printer
+Menu|File|Open
+Menu|File|New
+Menu|Printer|Select
+Menu|Printer|Open
+Menu|Printer|Connect
+</PRE>
+
+<P>
+The context is thus the menu path without its last part. So, the calls
+look like this:
+
+</P>
+
+<PRE>
+pgettext ("Menu|", "File")
+pgettext ("Menu|", "Printer")
+pgettext ("Menu|File|", "Open")
+pgettext ("Menu|File|", "New")
+pgettext ("Menu|Printer|", "Select")
+pgettext ("Menu|Printer|", "Open")
+pgettext ("Menu|Printer|", "Connect")
+</PRE>
+
+<P>
+Whether or not to use the <SAMP>‘|’</SAMP> character at the end of the context is a
+matter of style.
+
+</P>
+<P>
+For more complex cases, where the <VAR>msgctxt</VAR> or <VAR>msgid</VAR> are not
+string literals, more general macros are available:
+
+</P>
+<P>
+<A NAME="IDX1022"></A>
+<A NAME="IDX1023"></A>
+<A NAME="IDX1024"></A>
+
+<PRE>
+const char *pgettext_expr (const char *msgctxt, const char *msgid);
+const char *dpgettext_expr (const char *domain_name,
+ const char *msgctxt, const char *msgid);
+const char *dcpgettext_expr (const char *domain_name,
+ const char *msgctxt, const char *msgid,
+ int category);
+</PRE>
+
+<P>
+Here <VAR>msgctxt</VAR> and <VAR>msgid</VAR> can be arbitrary string-valued expressions.
+These macros are more general. But in the case that both argument expressions
+are string literals, the macros without the <SAMP>‘_expr’</SAMP> suffix are more
+efficient.
+
+</P>
+
+
+<H3><A NAME="SEC174" HREF="gettext_toc.html#TOC174">11.2.6 Additional functions for plural forms</A></H3>
+<P>
+<A NAME="IDX1025"></A>
</P>
<P>
<P>
But this does not solve the problem. It helps languages where the
-plural form of a noun is not simply constructed by adding an `s' but
-that is all. Once again people fell into the trap of believing the
+plural form of a noun is not simply constructed by adding an
+‘s’
+but that is all. Once again people fell into the trap of believing the
rules their language is using are universal. But the handling of plural
forms differs widely between the language families. For example,
Rafal Maszkowski <CODE><rzm@mat.uni.torun.pl></CODE> reports:
languages which have many irregularities. German, for instance, is a
drastic case. Though English and German are part of the same language
family (Germanic), the almost regular forming of plural noun forms
-(appending an `s') is hardly found in German.
+(appending an
+‘s’)
+is hardly found in German.
<LI>
<P>
<DL>
<DT><U>Function:</U> char * <B>ngettext</B> <I>(const char *<VAR>msgid1</VAR>, const char *<VAR>msgid2</VAR>, unsigned long int <VAR>n</VAR>)</I>
-<DD><A NAME="IDX997"></A>
+<DD><A NAME="IDX1026"></A>
The <CODE>ngettext</CODE> function is similar to the <CODE>gettext</CODE> function
as it finds the message catalogs in the same way. But it takes two
extra arguments. The <VAR>msgid1</VAR> parameter must contain the singular
<P>
<DL>
<DT><U>Function:</U> char * <B>dngettext</B> <I>(const char *<VAR>domain</VAR>, const char *<VAR>msgid1</VAR>, const char *<VAR>msgid2</VAR>, unsigned long int <VAR>n</VAR>)</I>
-<DD><A NAME="IDX998"></A>
+<DD><A NAME="IDX1027"></A>
The <CODE>dngettext</CODE> is similar to the <CODE>dgettext</CODE> 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
<P>
<DL>
<DT><U>Function:</U> char * <B>dcngettext</B> <I>(const char *<VAR>domain</VAR>, const char *<VAR>msgid1</VAR>, const char *<VAR>msgid2</VAR>, unsigned long int <VAR>n</VAR>, int <VAR>category</VAR>)</I>
-<DD><A NAME="IDX999"></A>
+<DD><A NAME="IDX1028"></A>
The <CODE>dcngettext</CODE> is similar to the <CODE>dcgettext</CODE> 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
</P>
<P>
-<A NAME="IDX1000"></A>
-<A NAME="IDX1001"></A>
-<A NAME="IDX1002"></A>
+<A NAME="IDX1029"></A>
+<A NAME="IDX1030"></A>
+<A NAME="IDX1031"></A>
The information about the plural form selection has to be stored in the
header entry of the PO file (the one with the empty <CODE>msgid</CODE> string).
The plural form information looks like this:
many different plural forms exist for this language. The string
following <CODE>plural</CODE> is an expression which is using the C language
syntax. Exceptions are that no negative numbers are allowed, numbers
-must be decimal, and the only variable allowed is <CODE>n</CODE>. This
-expression will be evaluated whenever one of the functions
+must be decimal, and the only variable allowed is <CODE>n</CODE>. Spaces are
+allowed in the expression, but backslash-newlines are not; in the
+examples below the backslash-newlines are present for formatting purposes
+only. This expression will be evaluated whenever one of the functions
<CODE>ngettext</CODE>, <CODE>dngettext</CODE>, or <CODE>dcngettext</CODE> is called. The
numeric value passed to these functions is then substituted for all uses
of the variable <CODE>n</CODE> in the expression. The resulting value then
</P>
<P>
-<A NAME="IDX1003"></A>
+<A NAME="IDX1032"></A>
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
Gaeilge (Irish)
</DL>
+<DT>Three forms, special case for numbers ending in 00 or [2-9][0-9]
+<DD>
+The header entry would be:
+
+
+<PRE>
+Plural-Forms: nplurals=3; \
+ plural=n==1 ? 0 : (n==0 || (n%100 > 0 && n%100 < 20)) ? 1 : 2;
+</PRE>
+
+Languages with this property include:
+
+<DL COMPACT>
+
+<DT>Romanic family
+<DD>
+Romanian
+</DL>
+
<DT>Three forms, special case for numbers ending in 1[2-9]
<DD>
The header entry would look like this:
-<H3><A NAME="SEC172" HREF="gettext_toc.html#TOC172">11.2.6 How to use <CODE>gettext</CODE> in GUI programs</A></H3>
-<P>
-<A NAME="IDX1004"></A>
-<A NAME="IDX1005"></A>
-<A NAME="IDX1006"></A>
-
-</P>
+<H3><A NAME="SEC175" HREF="gettext_toc.html#TOC175">11.2.7 Optimization of the *gettext functions</A></H3>
<P>
-One place where the <CODE>gettext</CODE> functions, if used normally, have big
-problems is within programs with graphical user interfaces (GUIs). The
-problem is that many of the strings which have to be translated are very
-short. They have to appear in pull-down menus which restricts the
-length. But strings which are not containing entire sentences or at
-least large fragments of a sentence may appear in more than one
-situation in the program but might have different translations. This is
-especially true for the one-word strings which are frequently used in
-GUI programs.
-
-</P>
-<P>
-As a consequence many people say that the <CODE>gettext</CODE> approach is
-wrong and instead <CODE>catgets</CODE> should be used which indeed does not
-have this problem. But there is a very simple and powerful method to
-handle these kind of problems with the <CODE>gettext</CODE> functions.
-
-</P>
-<P>
-As as example consider the following fictional situation. A GUI program
-has a menu bar with the following entries:
-
-</P>
-
-<PRE>
-+------------+------------+--------------------------------------+
-| File | Printer | |
-+------------+------------+--------------------------------------+
-| Open | | Select |
-| New | | Open |
-+----------+ | Connect |
- +----------+
-</PRE>
-
-<P>
-To have the strings <CODE>File</CODE>, <CODE>Printer</CODE>, <CODE>Open</CODE>,
-<CODE>New</CODE>, <CODE>Select</CODE>, and <CODE>Connect</CODE> translated there has to be
-at some point in the code a call to a function of the <CODE>gettext</CODE>
-family. But in two places the string passed into the function would be
-<CODE>Open</CODE>. The translations might not be the same and therefore we
-are in the dilemma described above.
-
-</P>
-<P>
-One solution to this problem is to artificially enlengthen the strings
-to make them unambiguous. But what would the program do if no
-translation is available? The enlengthened string is not what should be
-printed. So we should use a little bit modified version of the functions.
-
-</P>
-<P>
-To enlengthen the strings a uniform method should be used. E.g., in the
-example above the strings could be chosen as
-
-</P>
-
-<PRE>
-Menu|File
-Menu|Printer
-Menu|File|Open
-Menu|File|New
-Menu|Printer|Select
-Menu|Printer|Open
-Menu|Printer|Connect
-</PRE>
-
-<P>
-Now all the strings are different and if now instead of <CODE>gettext</CODE>
-the following little wrapper function is used, everything works just
-fine:
-
-</P>
-<P>
-<A NAME="IDX1007"></A>
-
-<PRE>
- char *
- sgettext (const char *msgid)
- {
- char *msgval = gettext (msgid);
- if (msgval == msgid)
- msgval = strrchr (msgid, '|') + 1;
- return msgval;
- }
-</PRE>
-
-<P>
-What this little function does is to recognize the case when no
-translation is available. This can be done very efficiently by a
-pointer comparison since the return value is the input value. If there
-is no translation we know that the input string is in the format we used
-for the Menu entries and therefore contains a <CODE>|</CODE> character. We
-simply search for the last occurrence of this character and return a
-pointer to the character following it. That's it!
-
-</P>
-<P>
-If one now consistently uses the enlengthened string form and replaces
-the <CODE>gettext</CODE> calls with calls to <CODE>sgettext</CODE> (this is normally
-limited to very few places in the GUI implementation) then it is
-possible to produce a program which can be internationalized.
-
-</P>
-<P>
-The other <CODE>gettext</CODE> functions (<CODE>dgettext</CODE>, <CODE>dcgettext</CODE>
-and the <CODE>ngettext</CODE> equivalents) can and should have corresponding
-functions as well which look almost identical, except for the parameters
-and the call to the underlying function.
-
-</P>
-<P>
-Now there is of course the question why such functions do not exist in
-the GNU gettext package? There are two parts of the answer to this question.
-
-</P>
-
-<UL>
-<LI>
-
-They are easy to write and therefore can be provided by the project they
-are used in. This is not an answer by itself and must be seen together
-with the second part which is:
-
-<LI>
-
-There is no way the gettext package can contain a version which can work
-everywhere. The problem is the selection of the character to separate
-the prefix from the actual string in the enlenghtened string. The
-examples above used <CODE>|</CODE> which is a quite good choice because it
-resembles a notation frequently used in this context and it also is a
-character not often used in message strings.
-
-But what if the character is used in message strings? Or if the chose
-character is not available in the character set on the machine one
-compiles (e.g., <CODE>|</CODE> is not required to exist for ISO C; this is
-why the <TT>`iso646.h´</TT> file exists in ISO C programming environments).
-</UL>
-
-<P>
-There is only one more comment to be said. The wrapper function above
-requires that the translations strings are not enlengthened themselves.
-This is only logical. There is no need to disambiguate the strings
-(since they are never used as keys for a search) and one also saves
-quite some memory and disk space by doing this.
-
-</P>
-
-
-<H3><A NAME="SEC173" HREF="gettext_toc.html#TOC173">11.2.7 Optimization of the *gettext functions</A></H3>
-<P>
-<A NAME="IDX1008"></A>
+<A NAME="IDX1033"></A>
</P>
<P>
</P>
-<H2><A NAME="SEC174" HREF="gettext_toc.html#TOC174">11.3 Comparing the Two Interfaces</A></H2>
+<H2><A NAME="SEC176" HREF="gettext_toc.html#TOC176">11.3 Comparing the Two Interfaces</A></H2>
<P>
-<A NAME="IDX1009"></A>
-<A NAME="IDX1010"></A>
+<A NAME="IDX1034"></A>
+<A NAME="IDX1035"></A>
</P>
</P>
<P>
-<A NAME="IDX1011"></A>
+<A NAME="IDX1036"></A>
<PRE>
#include <libintl.h>
</PRE>
<P>
-Additionally we run the program <TT>`xgettext´</TT> on all source code file
+Additionally we run the program <TT>‘xgettext’</TT> on all source code file
which contain translatable strings and that's it: we have a running
program which does not depend on translations to be available, but which
can use any that becomes available.
</P>
<P>
-<A NAME="IDX1012"></A>
+<A NAME="IDX1037"></A>
The same procedure can be done for the <CODE>gettext_noop</CODE> invocations
-(see section <A HREF="gettext_4.html#SEC17">4.6 Special Cases of Translatable Strings</A>). One usually defines <CODE>gettext_noop</CODE> as a
+(see section <A HREF="gettext_4.html#SEC18">4.7 Special Cases of Translatable Strings</A>). One usually defines <CODE>gettext_noop</CODE> as a
no-op macro. So you should consider the following code for your project:
</P>
</PRE>
<P>
-<CODE>N_</CODE> is a short form similar to <CODE>_</CODE>. The <TT>`Makefile´</TT> in
-the <TT>`po/´</TT> directory of GNU <CODE>gettext</CODE> knows by default both of the
+<CODE>N_</CODE> is a short form similar to <CODE>_</CODE>. The <TT>‘Makefile’</TT> in
+the <TT>‘po/’</TT> directory of GNU <CODE>gettext</CODE> knows by default both of the
mentioned short forms so you are invited to follow this proposal for
your own ease.
<P>
<CODE>catgets</CODE> allows same original entry to have different translations,
but <CODE>gettext</CODE> has another, scalable approach for solving ambiguities
-of this kind: See section <A HREF="gettext_11.html#SEC168">11.2.2 Solving Ambiguities</A>.
+of this kind: See section <A HREF="gettext_11.html#SEC170">11.2.2 Solving Ambiguities</A>.
</P>
-<H2><A NAME="SEC175" HREF="gettext_toc.html#TOC175">11.4 Using libintl.a in own programs</A></H2>
+<H2><A NAME="SEC177" HREF="gettext_toc.html#TOC177">11.4 Using libintl.a in own programs</A></H2>
<P>
Starting with version 0.9.4 the library <CODE>libintl.h</CODE> should be
self-contained. I.e., you can use it in your own programs without
-providing additional functions. The <TT>`Makefile´</TT> will put the header
+providing additional functions. The <TT>‘Makefile’</TT> will put the header
and the library in directories selected using the <CODE>$(prefix)</CODE>.
</P>
-<H2><A NAME="SEC176" HREF="gettext_toc.html#TOC176">11.5 Being a <CODE>gettext</CODE> grok</A></H2>
+<H2><A NAME="SEC178" HREF="gettext_toc.html#TOC178">11.5 Being a <CODE>gettext</CODE> grok</A></H2>
+<P>
+<STRONG> NOTE: </STRONG> This documentation section is outdated and needs to be
+revised.
+
+</P>
<P>
To fully exploit the functionality of the GNU <CODE>gettext</CODE> library it
is surely helpful to read the source code. But for those who don't want
<UL>
<LI>Changing the language at runtime
-<A NAME="IDX1013"></A>
+<A NAME="IDX1038"></A>
For interactive programs it might be useful to offer a selection of the
used language at runtime. To understand how to do this one need to know
<OL>
<LI><CODE>LANGUAGE</CODE>
-<A NAME="IDX1014"></A>
+<A NAME="IDX1039"></A>
-<A NAME="IDX1015"></A>
+<A NAME="IDX1040"></A>
<LI><CODE>LC_ALL</CODE>
-<A NAME="IDX1016"></A>
-<A NAME="IDX1017"></A>
-<A NAME="IDX1018"></A>
-<A NAME="IDX1019"></A>
-<A NAME="IDX1020"></A>
-<A NAME="IDX1021"></A>
+<A NAME="IDX1041"></A>
+<A NAME="IDX1042"></A>
+<A NAME="IDX1043"></A>
+<A NAME="IDX1044"></A>
+<A NAME="IDX1045"></A>
+<A NAME="IDX1046"></A>
<LI><CODE>LC_xxx</CODE>, according to selected locale
-<A NAME="IDX1022"></A>
+<A NAME="IDX1047"></A>
<LI><CODE>LANG</CODE>
</OL>
some optimization. This optimization normally prevents the calling of
the <CODE>dcgettext</CODE> function as long as no new catalog is loaded. But
if <CODE>dcgettext</CODE> is not called the program also cannot find the
-<CODE>LANGUAGE</CODE> variable be changed (see section <A HREF="gettext_11.html#SEC173">11.2.7 Optimization of the *gettext functions</A>). A
+<CODE>LANGUAGE</CODE> variable be changed (see section <A HREF="gettext_11.html#SEC175">11.2.7 Optimization of the *gettext functions</A>). A
solution for this is very easy. Include the following code in the
language switching function.
}
</PRE>
-<A NAME="IDX1023"></A>
-The variable <CODE>_nl_msg_cat_cntr</CODE> is defined in <TT>`loadmsgcat.c´</TT>.
+<A NAME="IDX1048"></A>
+The variable <CODE>_nl_msg_cat_cntr</CODE> is defined in <TT>‘loadmsgcat.c’</TT>.
You don't need to know what this is for. But it can be used to detect
whether a <CODE>gettext</CODE> implementation is GNU gettext and not non-GNU
system's native gettext implementation.
-<H2><A NAME="SEC177" HREF="gettext_toc.html#TOC177">11.6 Temporary Notes for the Programmers Chapter</A></H2>
+<H2><A NAME="SEC179" HREF="gettext_toc.html#TOC179">11.6 Temporary Notes for the Programmers Chapter</A></H2>
+
+<P>
+<STRONG> NOTE: </STRONG> This documentation section is outdated and needs to be
+revised.
+
+</P>
-<H3><A NAME="SEC178" HREF="gettext_toc.html#TOC178">11.6.1 Temporary - Two Possible Implementations</A></H3>
+<H3><A NAME="SEC180" HREF="gettext_toc.html#TOC180">11.6.1 Temporary - Two Possible Implementations</A></H3>
<P>
There are two competing methods for language independent messages:
vs. <CODE>catgets</CODE> (XPG). In the end the committee couldn't
agree on anything, so no messaging system was included as part
of the standard. I believe the informative annex of the standard
-includes the XPG3 messaging interfaces, "...as an example of
-a messaging system that has been implemented..."
+includes the XPG3 messaging interfaces, “...as an example of
+a messaging system that has been implemented...”
</P>
<P>
</P>
-<H3><A NAME="SEC179" HREF="gettext_toc.html#TOC179">11.6.2 Temporary - About <CODE>catgets</CODE></A></H3>
+<H3><A NAME="SEC181" HREF="gettext_toc.html#TOC181">11.6.2 Temporary - About <CODE>catgets</CODE></A></H3>
<P>
There have been a few discussions of late on the use of
</P>
-<H3><A NAME="SEC180" HREF="gettext_toc.html#TOC180">11.6.3 Temporary - Why a single implementation</A></H3>
+<H3><A NAME="SEC182" HREF="gettext_toc.html#TOC182">11.6.3 Temporary - Why a single implementation</A></H3>
<P>
Now it seems kind of wasteful to me to have two different systems
</P>
-<H3><A NAME="SEC181" HREF="gettext_toc.html#TOC181">11.6.4 Temporary - Notes</A></H3>
+<H3><A NAME="SEC183" HREF="gettext_toc.html#TOC183">11.6.4 Temporary - Notes</A></H3>
<P>
X/Open agreed very late on the standard form so that many
</P>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_10.html">previous</A>, <A HREF="gettext_12.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_10.html">previous</A>, <A HREF="gettext_12.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 12 The Translator's View</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_11.html">previous</A>, <A HREF="gettext_13.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_11.html">previous</A>, <A HREF="gettext_13.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC182" HREF="gettext_toc.html#TOC182">12 The Translator's View</A></H1>
+<H1><A NAME="SEC184" HREF="gettext_toc.html#TOC184">12 The Translator's View</A></H1>
-<H2><A NAME="SEC183" HREF="gettext_toc.html#TOC183">12.1 Introduction 0</A></H2>
+<H2><A NAME="SEC185" HREF="gettext_toc.html#TOC185">12.1 Introduction 0</A></H2>
+<P>
+<STRONG> NOTE: </STRONG> This documentation section is outdated and needs to be
+revised.
+
+</P>
<P>
Free software is going international! The Translation Project is a way
to get maintainers, translators and users all together, so free software
<P>
Each team has its own mailing list, courtesy of Linux
International. You may reach your translating team at the address
-<TT>`<VAR>ll</VAR>@li.org´</TT>, replacing <VAR>ll</VAR> by the two-letter ISO 639
+<TT>‘<VAR>ll</VAR>@li.org’</TT>, replacing <VAR>ll</VAR> by the two-letter ISO 639
code for your language. Language codes are <EM>not</EM> the same as
country codes given in ISO 3166. The following translating teams
exist:
<P>
For example, you may reach the Chinese translating team by writing to
-<TT>`zh@li.org´</TT>. When you become a member of the translating team
+<TT>‘zh@li.org’</TT>. When you become a member of the translating team
for your own language, you may subscribe to its list. For example,
-Swedish people can send a message to <TT>`sv-request@li.org´</TT>,
+Swedish people can send a message to <TT>‘sv-request@li.org’</TT>,
having this message body:
</P>
Keep in mind that team members should be interested in <EM>working</EM>
at translations, or at solving translational difficulties, rather than
merely lurking around. If your team does not exist yet and you want to
-start one, please write to <TT>`translation@iro.umontreal.ca´</TT>;
+start one, please write to <TT>‘translation@iro.umontreal.ca’</TT>;
you will then reach the coordinator for all translator teams.
</P>
point. But there are many more packages and many languages for
which we have no volunteer translators. If you would like to
volunteer to work at translating messages, please send mail to
-<TT>`translation@iro.umontreal.ca´</TT> indicating what language(s)
+<TT>‘translation@iro.umontreal.ca’</TT> indicating what language(s)
you can work on.
</P>
-<H2><A NAME="SEC184" HREF="gettext_toc.html#TOC184">12.2 Introduction 1</A></H2>
+<H2><A NAME="SEC186" HREF="gettext_toc.html#TOC186">12.2 Introduction 1</A></H2>
+
+<P>
+<STRONG> NOTE: </STRONG> This documentation section is outdated and needs to be
+revised.
+</P>
<P>
This is now official, GNU is going international! Here is the
announcement submitted for the January 1995 GNU Bulletin:
point. But there are many more packages and many languages
for which we have no volunteer translators. If you'd like to
volunteer to work at translating messages, please send mail to
-<SAMP>`translation@iro.umontreal.ca´</SAMP> indicating what language(s)
+<SAMP>‘translation@iro.umontreal.ca’</SAMP> indicating what language(s)
you can work on.
</BLOCKQUOTE>
</P>
<P>
For suggestion clarifications, additions or corrections to this
-document, please e-mail to <TT>`translation@iro.umontreal.ca´</TT>.
+document, please e-mail to <TT>‘translation@iro.umontreal.ca’</TT>.
</P>
-<H2><A NAME="SEC185" HREF="gettext_toc.html#TOC185">12.3 Discussions</A></H2>
+<H2><A NAME="SEC187" HREF="gettext_toc.html#TOC187">12.3 Discussions</A></H2>
+<P>
+<STRONG> NOTE: </STRONG> This documentation section is outdated and needs to be
+revised.
+
+</P>
<P>
Facing this internationalization effort, a few users expressed their
concerns. Some of these doubts are presented and discussed, here.
The biggest problem is to find the right translations so that
everybody can understand the messages. Translations are usually a
little odd. Some people get used to English, to the extent they may
-find translations into their own language "rather pushy, obnoxious
-and sometimes even hilarious." As a French speaking man, I have
+find translations into their own language “rather pushy, obnoxious
+and sometimes even hilarious.” As a French speaking man, I have
the experience of those instruction manuals for goods, so poorly
translated in French in Korea or Taiwan...
package under the protective wing of the GNU General Public License or
the GNU Library General Public License, when they do not want to make
their program free, or want other kinds of freedom. The simplest
-answer is "normally not".
+answer is “normally not”.
The <CODE>gettext-runtime</CODE> part of GNU <CODE>gettext</CODE>, i.e. the
contents of <CODE>libintl</CODE>, is covered by the GNU Library General Public
-<H2><A NAME="SEC186" HREF="gettext_toc.html#TOC186">12.4 Organization</A></H2>
+<H2><A NAME="SEC188" HREF="gettext_toc.html#TOC188">12.4 Organization</A></H2>
+
+<P>
+<STRONG> NOTE: </STRONG> This documentation section is outdated and needs to be
+revised.
+</P>
<P>
On a larger scale, the true solution would be to organize some kind of
fairly precise set up in which volunteers could participate. I gave
once well started.
The setup should be minimally completed and tested before GNU
<CODE>gettext</CODE> becomes an official reality. The e-mail address
-<TT>`translation@iro.umontreal.ca´</TT> has been setup for receiving
+<TT>‘translation@iro.umontreal.ca’</TT> has been setup for receiving
offers from volunteers and general e-mail on these topics. This address
reaches the Translation Project coordinator.
-<H3><A NAME="SEC187" HREF="gettext_toc.html#TOC187">12.4.1 Central Coordination</A></H3>
+<H3><A NAME="SEC189" HREF="gettext_toc.html#TOC189">12.4.1 Central Coordination</A></H3>
<P>
I also think GNU will need sooner than it thinks, that someone setup
a way to organize and coordinate these groups. Some kind of group
of groups. My opinion is that it would be good that GNU delegates
this task to a small group of collaborating volunteers, shortly.
-Perhaps in <TT>`gnu.announce´</TT> a list of this national committee's
+Perhaps in <TT>‘gnu.announce’</TT> a list of this national committee's
can be published.
</P>
</P>
-<H3><A NAME="SEC188" HREF="gettext_toc.html#TOC188">12.4.2 National Teams</A></H3>
+<H3><A NAME="SEC190" HREF="gettext_toc.html#TOC190">12.4.2 National Teams</A></H3>
<P>
I suggest we look for volunteer coordinators/editors for individual
-<H4><A NAME="SEC189" HREF="gettext_toc.html#TOC189">12.4.2.1 Sub-Cultures</A></H4>
+<H4><A NAME="SEC191" HREF="gettext_toc.html#TOC191">12.4.2.1 Sub-Cultures</A></H4>
<P>
Taking French for example, there are a few sub-cultures around computers
</P>
-<H4><A NAME="SEC190" HREF="gettext_toc.html#TOC190">12.4.2.2 Organizational Ideas</A></H4>
+<H4><A NAME="SEC192" HREF="gettext_toc.html#TOC192">12.4.2.2 Organizational Ideas</A></H4>
<P>
I expect the next big changes after the official release. Please note
-<H3><A NAME="SEC191" HREF="gettext_toc.html#TOC191">12.4.3 Mailing Lists</A></H3>
+<H3><A NAME="SEC193" HREF="gettext_toc.html#TOC193">12.4.3 Mailing Lists</A></H3>
<P>
If we get any inquiries about GNU <CODE>gettext</CODE>, send them on to:
</P>
<PRE>
-<TT>`translation@iro.umontreal.ca´</TT>
+<TT>‘translation@iro.umontreal.ca’</TT>
</PRE>
<P>
-The <TT>`*-pretest´</TT> lists are quite useful to me, maybe the idea could
+The <TT>‘*-pretest’</TT> lists are quite useful to me, maybe the idea could
be generalized to many GNU, and non-GNU packages. But each maintainer
his/her way!
</P>
<P>
François, we have a mechanism in place here at
-<TT>`gnu.ai.mit.edu´</TT> to track teams, support mailing lists for
+<TT>‘gnu.ai.mit.edu’</TT> to track teams, support mailing lists for
them and log members. We have a slight preference that you use it.
If this is OK with you, I can get you clued in.
</P>
-<H2><A NAME="SEC192" HREF="gettext_toc.html#TOC192">12.5 Information Flow</A></H2>
+<H2><A NAME="SEC194" HREF="gettext_toc.html#TOC194">12.5 Information Flow</A></H2>
+<P>
+<STRONG> NOTE: </STRONG> This documentation section is outdated and needs to be
+revised.
+
+</P>
<P>
There will surely be some discussion about this messages after the
packages are finally released. If people now send you some proposals
</P>
-<H2><A NAME="SEC193" HREF="gettext_toc.html#TOC193">12.6 Prioritizing messages: How to determine which messages to translate first</A></H2>
+<H2><A NAME="SEC195" HREF="gettext_toc.html#TOC195">12.6 Prioritizing messages: How to determine which messages to translate first</A></H2>
<P>
A translator sometimes has only a limited amount of time per week to
</P>
<P>
-<A NAME="IDX1024"></A>
+<A NAME="IDX1049"></A>
Here a more details. The GNU <CODE>libintl</CODE> library (but not the
corresponding functions in GNU <CODE>libc</CODE>) supports an environment variable
<CODE>GETTEXT_LOG_UNTRANSLATED</CODE>. The GNU <CODE>libintl</CODE> library will
log into this file the messages for which <CODE>gettext()</CODE> and related
functions couldn't find the translation. If the file doesn't exist, it
will be created as needed. On systems with GNU <CODE>libc</CODE> a shared library
-<SAMP>`preloadable_libintl.so´</SAMP> is provided that can be used with the ELF
-<SAMP>`LD_PRELOAD´</SAMP> mechanism.
+<SAMP>‘preloadable_libintl.so’</SAMP> is provided that can be used with the ELF
+<SAMP>‘LD_PRELOAD’</SAMP> mechanism.
</P>
<P>
</PRE>
<P>
-The result is a PO file, but needs some preprocessing before the Emacs PO
-mode can be used with it. First, it is a multi-domain PO file, containing
+The result is a PO file, but needs some preprocessing before a PO file editor
+can be used with it. First, it is a multi-domain PO file, containing
messages from many translation domains. Second, it lacks all translator
comments and source references. Here is how to get a list of the affected
translation domains:
</PRE>
<P>
-She takes the latest copy of <TT>`$lang.po´</TT> from the Translation Project,
-or from the package (in most cases, <TT>`$package/po/$lang.po´</TT>), or
-creates a fresh one if she's the first translator (see section <A HREF="gettext_6.html#SEC30">6 Creating a New PO File</A>).
+She takes the latest copy of <TT>‘$lang.po’</TT> from the Translation Project,
+or from the package (in most cases, <TT>‘$package/po/$lang.po’</TT>), or
+creates a fresh one if she's the first translator (see section <A HREF="gettext_6.html#SEC31">6 Creating a New PO File</A>).
She then uses the following commands to mark the not urgent messages as
"obsolete". (This doesn't mean that these messages - translated and
-untranslated ones - will go away. It simply means that Emacs PO mode
+untranslated ones - will go away. It simply means that the PO file editor
will ignore them in the following editing session.)
</P>
</PRE>
<P>
-The she translates <TT>`$domain.$lang-urgent.po´</TT> by use of Emacs PO mode.
+The she translates <TT>‘$domain.$lang-urgent.po’</TT> by use of a PO file editor
+(see section <A HREF="gettext_8.html#SEC49">8 Editing PO Files</A>).
(FIXME: I don't know whether <CODE>KBabel</CODE> and <CODE>gtranslator</CODE> also
preserve obsolete messages, as they should.)
Finally she restores the not urgent messages (with their earlier
</PRE>
<P>
-Then she can submit <TT>`$domain.$lang.po´</TT> and proceed to the next domain.
+Then she can submit <TT>‘$domain.$lang.po’</TT> and proceed to the next domain.
</P>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_11.html">previous</A>, <A HREF="gettext_13.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_11.html">previous</A>, <A HREF="gettext_13.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 13 The Maintainer's View</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_12.html">previous</A>, <A HREF="gettext_14.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_12.html">previous</A>, <A HREF="gettext_14.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC194" HREF="gettext_toc.html#TOC194">13 The Maintainer's View</A></H1>
+<H1><A NAME="SEC196" HREF="gettext_toc.html#TOC196">13 The Maintainer's View</A></H1>
<P>
-<A NAME="IDX1025"></A>
+<A NAME="IDX1050"></A>
</P>
<P>
is purposely for helping the internationalization of the whole GNU
project, and as many other good free packages as possible. So, the
maintainer's view presented here presumes that the package already has
-a <TT>`configure.in´</TT> file and uses GNU Autoconf.
+a <TT>‘configure.in’</TT> file and uses GNU Autoconf.
</P>
<P>
-<H2><A NAME="SEC195" HREF="gettext_toc.html#TOC195">13.1 Flat or Non-Flat Directory Structures</A></H2>
+<H2><A NAME="SEC197" HREF="gettext_toc.html#TOC197">13.1 Flat or Non-Flat Directory Structures</A></H2>
<P>
Some free software packages are distributed as <CODE>tar</CODE> files which unpack
in a single directory, these are said to be <EM>flat</EM> distributions.
Other free software packages have a one level hierarchy of subdirectories, using
-for example a subdirectory named <TT>`doc/´</TT> for the Texinfo manual and
-man pages, another called <TT>`lib/´</TT> for holding functions meant to
-replace or complement C libraries, and a subdirectory <TT>`src/´</TT> for
+for example a subdirectory named <TT>‘doc/’</TT> for the Texinfo manual and
+man pages, another called <TT>‘lib/’</TT> for holding functions meant to
+replace or complement C libraries, and a subdirectory <TT>‘src/’</TT> for
holding the proper sources for the package. These other distributions
are said to be <EM>non-flat</EM>.
</P>
-<H2><A NAME="SEC196" HREF="gettext_toc.html#TOC196">13.2 Prerequisite Works</A></H2>
+<H2><A NAME="SEC198" HREF="gettext_toc.html#TOC198">13.2 Prerequisite Works</A></H2>
<P>
-<A NAME="IDX1026"></A>
-<A NAME="IDX1027"></A>
-<A NAME="IDX1028"></A>
+<A NAME="IDX1051"></A>
+<A NAME="IDX1052"></A>
+<A NAME="IDX1053"></A>
</P>
<P>
To further ease the task of a package maintainer the <CODE>automake</CODE>
package was designed and implemented. GNU <CODE>gettext</CODE> now uses this
-tool and the <TT>`Makefile´</TT>s in the <TT>`intl/´</TT> and <TT>`po/´</TT>
+tool and the <TT>‘Makefile’</TT>s in the <TT>‘intl/’</TT> and <TT>‘po/’</TT>
therefore know about all the goals necessary for using <CODE>automake</CODE>
-and <TT>`libintl´</TT> in one project.
+and <TT>‘libintl’</TT> in one project.
Those four packages are only needed by you, as a maintainer; the
installers of your own package and end users do not really need any of
<LI>
-Your package should use Autoconf and have a <TT>`configure.in´</TT> or
-<TT>`configure.ac´</TT> file.
+Your package should use Autoconf and have a <TT>‘configure.in’</TT> or
+<TT>‘configure.ac’</TT> file.
If it does not, you have to learn how. The Autoconf documentation
is quite well written, it is a good idea that you print it and get
familiar with it.
<LI>
-Your <TT>`po/´</TT> directory should receive all PO files submitted to you
-by the translator teams, each having <TT>`<VAR>ll</VAR>.po´</TT> as a name.
+Your <TT>‘po/’</TT> directory should receive all PO files submitted to you
+by the translator teams, each having <TT>‘<VAR>ll</VAR>.po’</TT> as a name.
This is not usually easy to get translation
work done before your package gets internationalized and available!
Since the cycle has to start somewhere, the easiest for the maintainer
ideally behave with PO files submissions. As a maintainer, your role is
to authenticate the origin of the submission as being the representative
of the appropriate translating teams of the Translation Project (forward
-the submission to <TT>`translation@iro.umontreal.ca´</TT> in case of doubt),
+the submission to <TT>‘translation@iro.umontreal.ca’</TT> in case of doubt),
to ensure that the PO file format is not severely broken and does not
prevent successful installation, and for the rest, to merely put these
-PO files in <TT>`po/´</TT> for distribution.
+PO files in <TT>‘po/’</TT> for distribution.
</P>
<P>
driven by maintainers. You can help by carefully redirecting all
communications and reports from users about linguistic matters to the
appropriate translation team, or explain users how to reach or join
-their team. The simplest might be to send them the <TT>`ABOUT-NLS´</TT> file.
+their team. The simplest might be to send them the <TT>‘ABOUT-NLS’</TT> file.
</P>
<P>
</P>
-<H2><A NAME="SEC197" HREF="gettext_toc.html#TOC197">13.3 Invoking the <CODE>gettextize</CODE> Program</A></H2>
+<H2><A NAME="SEC199" HREF="gettext_toc.html#TOC199">13.3 Invoking the <CODE>gettextize</CODE> Program</A></H2>
<P>
The <CODE>gettextize</CODE> program is an interactive tool that helps the
<LI>It performs as many of the tasks mentioned in the next section
-section <A HREF="gettext_13.html#SEC198">13.4 Files You Must Create or Alter</A> as can be performed automatically.
+section <A HREF="gettext_13.html#SEC200">13.4 Files You Must Create or Alter</A> as can be performed automatically.
<LI>It removes obsolete files and idioms used for previous GNU
</P>
<P>
-<A NAME="IDX1029"></A>
-<A NAME="IDX1030"></A>
+<A NAME="IDX1054"></A>
+<A NAME="IDX1055"></A>
<PRE>
gettextize [ <VAR>option</VAR>... ] [ <VAR>directory</VAR> ]
</P>
<DL COMPACT>
-<DT><SAMP>`-c´</SAMP>
+<DT><SAMP>‘-c’</SAMP>
<DD>
-<DT><SAMP>`--copy´</SAMP>
+<DT><SAMP>‘--copy’</SAMP>
<DD>
-<A NAME="IDX1031"></A>
-<A NAME="IDX1032"></A>
+<A NAME="IDX1056"></A>
+<A NAME="IDX1057"></A>
Copy the needed files instead of making symbolic links. Using links
would allow the package to always use the latest <CODE>gettext</CODE> code
available on the system, but it might disturb some mechanism the
maintainer is used to apply to the sources. Because running
<CODE>gettextize</CODE> is easy there shouldn't be problems with using copies.
-<DT><SAMP>`-f´</SAMP>
+<DT><SAMP>‘-f’</SAMP>
<DD>
-<DT><SAMP>`--force´</SAMP>
+<DT><SAMP>‘--force’</SAMP>
<DD>
-<A NAME="IDX1033"></A>
-<A NAME="IDX1034"></A>
+<A NAME="IDX1058"></A>
+<A NAME="IDX1059"></A>
Force replacement of files which already exist.
-<DT><SAMP>`--intl´</SAMP>
+<DT><SAMP>‘--intl’</SAMP>
<DD>
-<A NAME="IDX1035"></A>
-Install the libintl sources in a subdirectory named <TT>`intl/´</TT>.
+<A NAME="IDX1060"></A>
+Install the libintl sources in a subdirectory named <TT>‘intl/’</TT>.
This libintl will be used to provide internationalization on systems
that don't have GNU libintl installed. If this option is omitted,
-the call to <CODE>AM_GNU_GETTEXT</CODE> in <TT>`configure.in´</TT> should read:
-<SAMP>`AM_GNU_GETTEXT([external])´</SAMP>, and internationalization will not
+the call to <CODE>AM_GNU_GETTEXT</CODE> in <TT>‘configure.in’</TT> should read:
+<SAMP>‘AM_GNU_GETTEXT([external])’</SAMP>, and internationalization will not
be enabled on systems lacking GNU gettext.
-<DT><SAMP>`--no-changelog´</SAMP>
+<DT><SAMP>‘--no-changelog’</SAMP>
<DD>
-<A NAME="IDX1036"></A>
+<A NAME="IDX1061"></A>
Don't update or create ChangeLog files. By default, <CODE>gettextize</CODE>
logs all changes (file additions, modifications and removals) in a
-file called <SAMP>`ChangeLog´</SAMP> in each affected directory.
+file called <SAMP>‘ChangeLog’</SAMP> in each affected directory.
-<DT><SAMP>`-n´</SAMP>
+<DT><SAMP>‘-n’</SAMP>
<DD>
-<DT><SAMP>`--dry-run´</SAMP>
+<DT><SAMP>‘--dry-run’</SAMP>
<DD>
-<A NAME="IDX1037"></A>
-<A NAME="IDX1038"></A>
+<A NAME="IDX1062"></A>
+<A NAME="IDX1063"></A>
Print modifications but don't perform them. All actions that
<CODE>gettextize</CODE> would normally execute are inhibited and instead only
listed on standard output.
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX1039"></A>
+<A NAME="IDX1064"></A>
Display this help and exit.
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX1040"></A>
+<A NAME="IDX1065"></A>
Output version information and exit.
</DL>
<OL>
<LI>
-The <TT>`ABOUT-NLS´</TT> file is copied in the main directory of your package,
+The <TT>‘ABOUT-NLS’</TT> file is copied in the main directory of your package,
the one being at the top level. This file gives the main indications
about how to install and use the Native Language Support features
of your program. You might elect to use a more recent copy of this
-<TT>`ABOUT-NLS´</TT> file than the one provided through <CODE>gettextize</CODE>,
+<TT>‘ABOUT-NLS’</TT> file than the one provided through <CODE>gettextize</CODE>,
if you have one handy. You may also fetch a more recent copy of file
-<TT>`ABOUT-NLS´</TT> from Translation Project sites, and from most GNU
+<TT>‘ABOUT-NLS’</TT> from Translation Project sites, and from most GNU
archive sites.
<LI>
-A <TT>`po/´</TT> directory is created for eventually holding
+A <TT>‘po/’</TT> directory is created for eventually holding
all translation files, but initially only containing the file
-<TT>`po/Makefile.in.in´</TT> from the GNU <CODE>gettext</CODE> distribution
-(beware the double <SAMP>`.in´</SAMP> in the file name) and a few auxiliary
-files. If the <TT>`po/´</TT> directory already exists, it will be preserved
-along with the files it contains, and only <TT>`Makefile.in.in´</TT> and
+<TT>‘po/Makefile.in.in’</TT> from the GNU <CODE>gettext</CODE> distribution
+(beware the double <SAMP>‘.in’</SAMP> in the file name) and a few auxiliary
+files. If the <TT>‘po/’</TT> directory already exists, it will be preserved
+along with the files it contains, and only <TT>‘Makefile.in.in’</TT> and
the auxiliary files will be overwritten.
<LI>
-Only if <SAMP>`--intl´</SAMP> has been specified:
-A <TT>`intl/´</TT> directory is created and filled with most of the files
-originally in the <TT>`intl/´</TT> directory of the GNU <CODE>gettext</CODE>
+Only if <SAMP>‘--intl’</SAMP> has been specified:
+A <TT>‘intl/’</TT> directory is created and filled with most of the files
+originally in the <TT>‘intl/’</TT> directory of the GNU <CODE>gettext</CODE>
distribution. Also, if option <CODE>--force</CODE> (<CODE>-f</CODE>) is given,
-the <TT>`intl/´</TT> directory is emptied first.
+the <TT>‘intl/’</TT> directory is emptied first.
<LI>
-The files <TT>`config.rpath´</TT> and <TT>`mkinstalldirs´</TT> are copied into
-the directory containing configuration support files. It is needed by
-the <CODE>AM_GNU_GETTEXT</CODE> autoconf macro.
+The file <TT>‘config.rpath’</TT> is copied into the directory containing
+configuration support files. It is needed by the <CODE>AM_GNU_GETTEXT</CODE>
+autoconf macro.
<LI>
Only if the project is using GNU <CODE>automake</CODE>:
A set of <CODE>autoconf</CODE> macro files is copied into the package's
-<CODE>autoconf</CODE> macro repository, usually in a directory called <TT>`m4/´</TT>.
+<CODE>autoconf</CODE> macro repository, usually in a directory called <TT>‘m4/’</TT>.
</OL>
<P>
If your site support symbolic links, <CODE>gettextize</CODE> will not
actually copy the files into your package, but establish symbolic
links instead. This avoids duplicating the disk space needed in
-all packages. Merely using the <SAMP>`-h´</SAMP> option while creating the
+all packages. Merely using the <SAMP>‘-h’</SAMP> option while creating the
<CODE>tar</CODE> archive of your distribution will resolve each link by an
actual copy in the distribution archive. So, to insist, you really
-should use <SAMP>`-h´</SAMP> option with <CODE>tar</CODE> within your <CODE>dist</CODE>
-goal of your main <TT>`Makefile.in´</TT>.
+should use <SAMP>‘-h’</SAMP> option with <CODE>tar</CODE> within your <CODE>dist</CODE>
+goal of your main <TT>‘Makefile.in’</TT>.
</P>
<P>
-Furthermore, <CODE>gettextize</CODE> will update all <TT>`Makefile.am´</TT> files
-in each affected directory, as well as the top level <TT>`configure.in´</TT>
-or <TT>`configure.ac´</TT> file.
+Furthermore, <CODE>gettextize</CODE> will update all <TT>‘Makefile.am’</TT> files
+in each affected directory, as well as the top level <TT>‘configure.in’</TT>
+or <TT>‘configure.ac’</TT> file.
</P>
<P>
It is interesting to understand that most new files for supporting
-GNU <CODE>gettext</CODE> facilities in one package go in <TT>`intl/´</TT>,
-<TT>`po/´</TT> and <TT>`m4/´</TT> subdirectories. One distinction between
-<TT>`intl/´</TT> and the two other directories is that <TT>`intl/´</TT> is
+GNU <CODE>gettext</CODE> facilities in one package go in <TT>‘intl/’</TT>,
+<TT>‘po/’</TT> and <TT>‘m4/’</TT> subdirectories. One distinction between
+<TT>‘intl/’</TT> and the two other directories is that <TT>‘intl/’</TT> is
meant to be completely identical in all packages using GNU <CODE>gettext</CODE>,
while the other directories will mostly contain package dependent
files.
replaces or changes, and also write ChangeLog entries about these
changes. This way, the careful maintainer can check after running
<CODE>gettextize</CODE> whether its changes are acceptable to him, and
-possibly adjust them. An exception to this rule is the <TT>`intl/´</TT>
+possibly adjust them. An exception to this rule is the <TT>‘intl/’</TT>
directory, which is added or replaced or removed as a whole.
</P>
entire job of adapting a package for using GNU <CODE>gettext</CODE>. The
amount of remaining work depends on whether the package uses GNU
<CODE>automake</CODE> or not. But in any case, the maintainer should still
-read the section section <A HREF="gettext_13.html#SEC198">13.4 Files You Must Create or Alter</A> after invoking <CODE>gettextize</CODE>.
+read the section section <A HREF="gettext_13.html#SEC200">13.4 Files You Must Create or Alter</A> after invoking <CODE>gettextize</CODE>.
+
+</P>
+<P>
+In particular, if after using <SAMP>‘gettexize’</SAMP>, you get an error
+<SAMP>‘AC_COMPILE_IFELSE was called before AC_GNU_SOURCE’</SAMP> or
+<SAMP>‘AC_RUN_IFELSE was called before AC_GNU_SOURCE’</SAMP>, you can fix it
+by modifying <TT>‘configure.ac’</TT>, as described in section <A HREF="gettext_13.html#SEC205">13.4.5 <TT>‘configure.in’</TT> at top level</A>.
</P>
<P>
of the GNU build system, in the sense that it should not be invoked
automatically, and not be invoked by someone who doesn't assume the
responsibilities of a package maintainer. For the latter purpose, a
-separate tool is provided, see section <A HREF="gettext_13.html#SEC219">13.6.3 Invoking the <CODE>autopoint</CODE> Program</A>.
+separate tool is provided, see section <A HREF="gettext_13.html#SEC222">13.6.3 Invoking the <CODE>autopoint</CODE> Program</A>.
</P>
-<H2><A NAME="SEC198" HREF="gettext_toc.html#TOC198">13.4 Files You Must Create or Alter</A></H2>
+<H2><A NAME="SEC200" HREF="gettext_toc.html#TOC200">13.4 Files You Must Create or Alter</A></H2>
<P>
-<A NAME="IDX1041"></A>
+<A NAME="IDX1066"></A>
</P>
<P>
<P>
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
-<CODE>gettext</CODE> 0.15-pre0 distribution itself, or from the GNU
+<CODE>gettext</CODE> 0.15 distribution itself, or from the GNU
<CODE>hello</CODE> distribution (<A HREF="http://www.franken.de/users/gnu/ke/hello">http://www.franken.de/users/gnu/ke/hello</A>
or <A HREF="http://www.gnu.franken.de/ke/hello/">http://www.gnu.franken.de/ke/hello/</A>) You may indeed
refer to the source code of the GNU <CODE>gettext</CODE> and GNU <CODE>hello</CODE>
-<H3><A NAME="SEC199" HREF="gettext_toc.html#TOC199">13.4.1 <TT>`POTFILES.in´</TT> in <TT>`po/´</TT></A></H3>
+<H3><A NAME="SEC201" HREF="gettext_toc.html#TOC201">13.4.1 <TT>‘POTFILES.in’</TT> in <TT>‘po/’</TT></A></H3>
<P>
-<A NAME="IDX1042"></A>
+<A NAME="IDX1067"></A>
</P>
<P>
-The <TT>`po/´</TT> directory should receive a file named
-<TT>`POTFILES.in´</TT>. This file tells which files, among all program
+The <TT>‘po/’</TT> directory should receive a file named
+<TT>‘POTFILES.in’</TT>. This file tells which files, among all program
sources, have marked strings needing translation. Here is an example
of such a file:
<P>
Hash-marked comments and white lines are ignored. All other lines
list those source files containing strings marked for translation
-(see section <A HREF="gettext_4.html#SEC14">4.3 How Marks Appear in Sources</A>), in a notation relative to the top level
+(see section <A HREF="gettext_4.html#SEC15">4.4 How Marks Appear in Sources</A>), in a notation relative to the top level
of your whole distribution, rather than the location of the
-<TT>`POTFILES.in´</TT> file itself.
+<TT>‘POTFILES.in’</TT> file itself.
</P>
<P>
When a C file is automatically generated by a tool, like <CODE>flex</CODE> or
<CODE>bison</CODE>, that doesn't introduce translatable strings by itself,
-it is recommended to list in <TT>`po/POTFILES.in´</TT> the real source file
-(ending in <TT>`.l´</TT> in the case of <CODE>flex</CODE>, or in <TT>`.y´</TT> in the
+it is recommended to list in <TT>‘po/POTFILES.in’</TT> the real source file
+(ending in <TT>‘.l’</TT> in the case of <CODE>flex</CODE>, or in <TT>‘.y’</TT> in the
case of <CODE>bison</CODE>), not the generated C file.
</P>
-<H3><A NAME="SEC200" HREF="gettext_toc.html#TOC200">13.4.2 <TT>`LINGUAS´</TT> in <TT>`po/´</TT></A></H3>
+<H3><A NAME="SEC202" HREF="gettext_toc.html#TOC202">13.4.2 <TT>‘LINGUAS’</TT> in <TT>‘po/’</TT></A></H3>
<P>
-<A NAME="IDX1043"></A>
+<A NAME="IDX1068"></A>
</P>
<P>
-The <TT>`po/´</TT> directory should also receive a file named
-<TT>`LINGUAS´</TT>. This file contains the list of available translations.
+The <TT>‘po/’</TT> directory should also receive a file named
+<TT>‘LINGUAS’</TT>. This file contains the list of available translations.
It is a whitespace separated list. Hash-marked comments and white lines
are ignored. Here is an example file:
This example means that German and French PO files are available, so
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 <TT>`LINGUAS´</TT> file,
+languages, this should not be done by modifying the <TT>‘LINGUAS’</TT> file,
but rather by using the <CODE>LINGUAS</CODE> environment variable
-(see section <A HREF="gettext_14.html#SEC223">14 The Installer's and Distributor's View</A>).
+(see section <A HREF="gettext_14.html#SEC226">14 The Installer's and Distributor's View</A>).
</P>
<P>
-It is recommended that you add the "languages" <SAMP>`en@quot´</SAMP> and
-<SAMP>`en@boldquot´</SAMP> to the <CODE>LINGUAS</CODE> file. <CODE>en@quot</CODE> is a
+It is recommended that you add the "languages" <SAMP>‘en@quot’</SAMP> and
+<SAMP>‘en@boldquot’</SAMP> to the <CODE>LINGUAS</CODE> file. <CODE>en@quot</CODE> is a
variant of English message catalogs (<CODE>en</CODE>) which uses real quotation
-marks instead of the ugly looking asymmetric ASCII substitutes <SAMP>``´</SAMP>
-and <SAMP>`'´</SAMP>. <CODE>en@boldquot</CODE> is a variant of <CODE>en@quot</CODE> that
+marks instead of the ugly looking asymmetric ASCII substitutes <SAMP>‘`’</SAMP>
+and <SAMP>‘'’</SAMP>. <CODE>en@boldquot</CODE> is a variant of <CODE>en@quot</CODE> that
additionally outputs quoted pieces of text in a bold font, when used in
a terminal emulator which supports the VT100 escape sequences (such as
<CODE>xterm</CODE> or the Linux console, but not Emacs in <KBD>M-x shell</KBD> mode).
</P>
<P>
-These extra message catalogs <SAMP>`en@quot´</SAMP> and <SAMP>`en@boldquot´</SAMP>
+These extra message catalogs <SAMP>‘en@quot’</SAMP> and <SAMP>‘en@boldquot’</SAMP>
are constructed automatically, not by translators; to support them, you
-need the files <TT>`Rules-quot´</TT>, <TT>`quot.sed´</TT>, <TT>`boldquot.sed´</TT>,
-<TT>`en@quot.header´</TT>, <TT>`en@boldquot.header´</TT>, <TT>`insert-header.sin´</TT>
-in the <TT>`po/´</TT> directory. You can copy them from GNU gettext's <TT>`po/´</TT>
+need the files <TT>‘Rules-quot’</TT>, <TT>‘quot.sed’</TT>, <TT>‘boldquot.sed’</TT>,
+<TT>‘en@quot.header’</TT>, <TT>‘en@boldquot.header’</TT>, <TT>‘insert-header.sin’</TT>
+in the <TT>‘po/’</TT> directory. You can copy them from GNU gettext's <TT>‘po/’</TT>
directory; they are also installed by running <CODE>gettextize</CODE>.
</P>
-<H3><A NAME="SEC201" HREF="gettext_toc.html#TOC201">13.4.3 <TT>`Makevars´</TT> in <TT>`po/´</TT></A></H3>
+<H3><A NAME="SEC203" HREF="gettext_toc.html#TOC203">13.4.3 <TT>‘Makevars’</TT> in <TT>‘po/’</TT></A></H3>
+<P>
+<A NAME="IDX1069"></A>
+
+</P>
<P>
-<A NAME="IDX1044"></A>
+The <TT>‘po/’</TT> directory also has a file named <TT>‘Makevars’</TT>. It
+contains variables that are specific to your project. <TT>‘po/Makevars’</TT>
+gets inserted into the <TT>‘po/Makefile’</TT> when the latter is created.
+The variables thus take effect when the POT file is created or updated,
+and when the message catalogs get installed.
</P>
<P>
-The <TT>`po/´</TT> directory also has a file named <TT>`Makevars´</TT>.
-It can be left unmodified if your package has a single message domain
-and, accordingly, a single <TT>`po/´</TT> directory. Only packages which
-have multiple <TT>`po/´</TT> directories at different locations need to
-adjust the three variables defined in <TT>`Makevars´</TT>.
+The first three variables can be left unmodified if your package has a
+single message domain and, accordingly, a single <TT>‘po/’</TT> directory.
+Only packages which have multiple <TT>‘po/’</TT> directories at different
+locations need to adjust the three first variables defined in
+<TT>‘Makevars’</TT>.
</P>
+
+
+<H3><A NAME="SEC204" HREF="gettext_toc.html#TOC204">13.4.4 Extending <TT>‘Makefile’</TT> in <TT>‘po/’</TT></A></H3>
<P>
-<TT>`po/Makevars´</TT> gets inserted into the <TT>`po/Makefile´</TT> when the
-latter is created. At the same time, all files called <TT>`Rules-*´</TT> in the
-<TT>`po/´</TT> directory get appended to the <TT>`po/Makefile´</TT>. They present
-an opportunity to add rules for special PO files to the Makefile, without
-needing to mess with <TT>`po/Makefile.in.in´</TT>.
+<A NAME="IDX1070"></A>
</P>
<P>
-<A NAME="IDX1045"></A>
-<A NAME="IDX1046"></A>
-GNU gettext comes with a <TT>`Rules-quot´</TT> file, containing rules for
-building catalogs <TT>`en@quot.po´</TT> and <TT>`en@boldquot.po´</TT>. The
-effect of <TT>`en@quot.po´</TT> is that people who set their <CODE>LANGUAGE</CODE>
-environment variable to <SAMP>`en@quot´</SAMP> will get messages with proper
+All files called <TT>‘Rules-*’</TT> in the <TT>‘po/’</TT> directory get appended to
+the <TT>‘po/Makefile’</TT> when it is created. They present an opportunity to
+add rules for special PO files to the Makefile, without needing to mess
+with <TT>‘po/Makefile.in.in’</TT>.
+
+</P>
+<P>
+<A NAME="IDX1071"></A>
+<A NAME="IDX1072"></A>
+GNU gettext comes with a <TT>‘Rules-quot’</TT> file, containing rules for
+building catalogs <TT>‘en@quot.po’</TT> and <TT>‘en@boldquot.po’</TT>. The
+effect of <TT>‘en@quot.po’</TT> is that people who set their <CODE>LANGUAGE</CODE>
+environment variable to <SAMP>‘en@quot’</SAMP> will get messages with proper
looking symmetric Unicode quotation marks instead of abusing the ASCII
grave accent and the ASCII apostrophe for indicating quotations. To
-enable this catalog, simply add <CODE>en@quot</CODE> to the <TT>`po/LINGUAS´</TT>
-file. The effect of <TT>`en@boldquot.po´</TT> is that people who set
-<CODE>LANGUAGE</CODE> to <SAMP>`en@boldquot´</SAMP> will get not only proper quotation
+enable this catalog, simply add <CODE>en@quot</CODE> to the <TT>‘po/LINGUAS’</TT>
+file. The effect of <TT>‘en@boldquot.po’</TT> is that people who set
+<CODE>LANGUAGE</CODE> to <SAMP>‘en@boldquot’</SAMP> will get not only proper quotation
marks, but also the quoted text will be shown in a bold font on terminals
and consoles. This catalog is useful only for command-line programs, not
GUI programs. To enable it, similarly add <CODE>en@boldquot</CODE> to the
-<TT>`po/LINGUAS´</TT> file.
+<TT>‘po/LINGUAS’</TT> file.
+
+</P>
+<P>
+Similarly, you can create rules for building message catalogs for the
+<TT>‘sr@latin’</TT> locale -- Serbian written with the Latin alphabet --
+from those for the <TT>‘sr’</TT> locale -- Serbian written with Cyrillic
+letters. See section <A HREF="gettext_9.html#SEC95">9.4 Invoking the <CODE>msgfilter</CODE> Program</A>.
</P>
-<H3><A NAME="SEC202" HREF="gettext_toc.html#TOC202">13.4.4 <TT>`configure.in´</TT> at top level</A></H3>
+<H3><A NAME="SEC205" HREF="gettext_toc.html#TOC205">13.4.5 <TT>‘configure.in’</TT> at top level</A></H3>
<P>
-<TT>`configure.in´</TT> or <TT>`configure.ac´</TT> - this is the source from which
-<CODE>autoconf</CODE> generates the <TT>`configure´</TT> script.
+<TT>‘configure.in’</TT> or <TT>‘configure.ac’</TT> - this is the source from which
+<CODE>autoconf</CODE> generates the <TT>‘configure’</TT> script.
</P>
<OL>
<LI>Declare the package and version.
-<A NAME="IDX1047"></A>
+<A NAME="IDX1073"></A>
This is done by a set of lines like these:
<PRE>
PACKAGE=gettext
-VERSION=0.15-pre0
+VERSION=0.15
AC_DEFINE_UNQUOTED(PACKAGE, "$PACKAGE")
AC_DEFINE_UNQUOTED(VERSION, "$VERSION")
AC_SUBST(PACKAGE)
<PRE>
-AM_INIT_AUTOMAKE(gettext, 0.15-pre0)
+AM_INIT_AUTOMAKE(gettext, 0.15)
</PRE>
-Of course, you replace <SAMP>`gettext´</SAMP> with the name of your package,
-and <SAMP>`0.15-pre0´</SAMP> by its version numbers, exactly as they
+Of course, you replace <SAMP>‘gettext’</SAMP> with the name of your package,
+and <SAMP>‘0.15’</SAMP> by its version numbers, exactly as they
should appear in the packaged <CODE>tar</CODE> file name of your distribution
-(<TT>`gettext-0.15-pre0.tar.gz´</TT>, here).
+(<TT>‘gettext-0.15.tar.gz’</TT>, here).
<LI>Check for internationalization support.
Here is the main <CODE>m4</CODE> macro for triggering internationalization
-support. Just add this line to <TT>`configure.in´</TT>:
+support. Just add this line to <TT>‘configure.in’</TT>:
<PRE>
This call is purposely simple, even if it generates a lot of configure
time checking and actions.
-If you have suppressed the <TT>`intl/´</TT> subdirectory by calling
-<CODE>gettextize</CODE> without <SAMP>`--intl´</SAMP> option, this call should read
+If you have suppressed the <TT>‘intl/’</TT> subdirectory by calling
+<CODE>gettextize</CODE> without <SAMP>‘--intl’</SAMP> option, this call should read
<PRE>
<LI>Have output files created.
-The <CODE>AC_OUTPUT</CODE> directive, at the end of your <TT>`configure.in´</TT>
+The <CODE>AC_OUTPUT</CODE> directive, at the end of your <TT>‘configure.in’</TT>
file, needs to be modified in two ways:
</PRE>
The modification to the first argument to <CODE>AC_OUTPUT</CODE> asks
-for substitution in the <TT>`intl/´</TT> and <TT>`po/´</TT> directories.
-Note the <SAMP>`.in´</SAMP> suffix used for <TT>`po/´</TT> only. This is because
-the distributed file is really <TT>`po/Makefile.in.in´</TT>.
+for substitution in the <TT>‘intl/’</TT> and <TT>‘po/’</TT> directories.
+Note the <SAMP>‘.in’</SAMP> suffix used for <TT>‘po/’</TT> only. This is because
+the distributed file is really <TT>‘po/Makefile.in.in’</TT>.
-If you have suppressed the <TT>`intl/´</TT> subdirectory by calling
-<CODE>gettextize</CODE> without <SAMP>`--intl´</SAMP> option, then you don't need to
+If you have suppressed the <TT>‘intl/’</TT> subdirectory by calling
+<CODE>gettextize</CODE> without <SAMP>‘--intl’</SAMP> option, then you don't need to
add <CODE>intl/Makefile</CODE> to the <CODE>AC_OUTPUT</CODE> line.
</OL>
+<P>
+If, after doing the recommended modifications, a command like
+<SAMP>‘aclocal -I m4’</SAMP> or <SAMP>‘autoconf’</SAMP> or <SAMP>‘autoreconf’</SAMP> fails with
+a trace similar to this:
+
+</P>
+
+<PRE>
+configure.ac:44: warning: AC_COMPILE_IFELSE was called before AC_GNU_SOURCE
+../../lib/autoconf/specific.m4:335: AC_GNU_SOURCE is expanded from...
+m4/lock.m4:224: gl_LOCK is expanded from...
+m4/gettext.m4:571: gt_INTL_SUBDIR_CORE is expanded from...
+m4/gettext.m4:472: AM_INTL_SUBDIR is expanded from...
+m4/gettext.m4:347: AM_GNU_GETTEXT is expanded from...
+configure.ac:44: the top level
+configure.ac:44: warning: AC_RUN_IFELSE was called before AC_GNU_SOURCE
+</PRE>
+
+<P>
+you need to add an explicit invocation of <SAMP>‘AC_GNU_SOURCE’</SAMP> in the
+<TT>‘configure.ac’</TT> file - after <SAMP>‘AC_PROG_CC’</SAMP> but before
+<SAMP>‘AM_GNU_GETTEXT’</SAMP>, most likely very close to the <SAMP>‘AC_PROG_CC’</SAMP>
+invocation. This is necessary because of ordering restrictions imposed
+by GNU autoconf.
+
+</P>
-<H3><A NAME="SEC203" HREF="gettext_toc.html#TOC203">13.4.5 <TT>`config.guess´</TT>, <TT>`config.sub´</TT> at top level</A></H3>
+<H3><A NAME="SEC206" HREF="gettext_toc.html#TOC206">13.4.6 <TT>‘config.guess’</TT>, <TT>‘config.sub’</TT> at top level</A></H3>
<P>
-If you haven't suppressed the <TT>`intl/´</TT> subdirectory,
-you need to add the GNU <TT>`config.guess´</TT> and <TT>`config.sub´</TT> files
-to your distribution. They are needed because the <TT>`intl/´</TT> directory
+If you haven't suppressed the <TT>‘intl/’</TT> subdirectory,
+you need to add the GNU <TT>‘config.guess’</TT> and <TT>‘config.sub’</TT> files
+to your distribution. They are needed because the <TT>‘intl/’</TT> directory
has platform dependent support for determining the locale's character
encoding and therefore needs to identify the platform.
</P>
<P>
-You can obtain the newest version of <TT>`config.guess´</TT> and
-<TT>`config.sub´</TT> from the CVS of the <SAMP>`config´</SAMP> project at
-<TT>`http://savannah.gnu.org/´</TT>. The commands to fetch them are
+You can obtain the newest version of <TT>‘config.guess’</TT> and
+<TT>‘config.sub’</TT> from the CVS of the <SAMP>‘config’</SAMP> project at
+<TT>‘http://savannah.gnu.org/’</TT>. The commands to fetch them are
<PRE>
$ wget 'http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.guess'
</P>
<P>
-Normally, <TT>`config.guess´</TT> and <TT>`config.sub´</TT> are put at the
+Normally, <TT>‘config.guess’</TT> and <TT>‘config.sub’</TT> are put at the
top level of a distribution. But it is also possible to put them in a
subdirectory, altogether with other configuration support files like
-<TT>`install-sh´</TT>, <TT>`ltconfig´</TT>, <TT>`ltmain.sh´</TT>,
-<TT>`mkinstalldirs´</TT> or <TT>`missing´</TT>. All you need to do, other than
-moving the files, is to add the following line to your
-<TT>`configure.in´</TT>.
+<TT>‘install-sh’</TT>, <TT>‘ltconfig’</TT>, <TT>‘ltmain.sh’</TT> or <TT>‘missing’</TT>.
+All you need to do, other than moving the files, is to add the following line
+to your <TT>‘configure.in’</TT>.
</P>
-<H3><A NAME="SEC204" HREF="gettext_toc.html#TOC204">13.4.6 <TT>`mkinstalldirs´</TT> at top level</A></H3>
-<P>
-<A NAME="IDX1048"></A>
-
-</P>
+<H3><A NAME="SEC207" HREF="gettext_toc.html#TOC207">13.4.7 <TT>‘mkinstalldirs’</TT> at top level</A></H3>
<P>
-If <CODE>gettextize</CODE> has not already done it, you need to add the GNU
-<TT>`mkinstalldirs´</TT> script to your distribution. It is needed because
-<SAMP>`mkdir -p´</SAMP> is not portable enough. You find this script in the
-GNU <CODE>automake</CODE> distribution.
+<A NAME="IDX1074"></A>
</P>
<P>
-Normally, <TT>`mkinstalldirs´</TT> is put at the top level of a distribution.
-But it is also possible to put it in a subdirectory, altogether with other
-configuration support files like <TT>`install-sh´</TT>, <TT>`ltconfig´</TT>,
-<TT>`ltmain.sh´</TT> or <TT>`missing´</TT>. All you need to do, other than
-moving the files, is to add the following line to your <TT>`configure.in´</TT>.
+With earlier versions of GNU gettext, you needed to add the GNU
+<TT>‘mkinstalldirs’</TT> script to your distribution. This is not needed any
+more. You can remove it if you not also using an automake version older than
+automake 1.9.
</P>
-<PRE>
-AC_CONFIG_AUX_DIR([<VAR>subdir</VAR>])
-</PRE>
-
-
-<H3><A NAME="SEC205" HREF="gettext_toc.html#TOC205">13.4.7 <TT>`aclocal.m4´</TT> at top level</A></H3>
+<H3><A NAME="SEC208" HREF="gettext_toc.html#TOC208">13.4.8 <TT>‘aclocal.m4’</TT> at top level</A></H3>
<P>
-<A NAME="IDX1049"></A>
+<A NAME="IDX1075"></A>
</P>
<P>
-If you do not have an <TT>`aclocal.m4´</TT> file in your distribution,
-the simplest is to concatenate the files <TT>`codeset.m4´</TT>,
-<TT>`gettext.m4´</TT>, <TT>`glibc2.m4´</TT>, <TT>`glibc21.m4´</TT>, <TT>`iconv.m4´</TT>,
-<TT>`intdiv0.m4´</TT>, <TT>`intmax.m4´</TT>, <TT>`inttypes.m4´</TT>, <TT>`inttypes_h.m4´</TT>,
-<TT>`inttypes-pri.m4´</TT>, <TT>`isc-posix.m4´</TT>, <TT>`lcmessage.m4´</TT>,
-<TT>`lib-ld.m4´</TT>, <TT>`lib-link.m4´</TT>, <TT>`lib-prefix.m4´</TT>, <TT>`lock.m4´</TT>,
-<TT>`longdouble.m4´</TT>, <TT>`longlong.m4´</TT>, <TT>`printf-posix.m4´</TT>,
-<TT>`progtest.m4´</TT>, <TT>`signed.m4´</TT>, <TT>`size_max.m4´</TT>,
-<TT>`stdint_h.m4´</TT>, <TT>`uintmax_t.m4´</TT>, <TT>`ulonglong.m4´</TT>,
-<TT>`wchar_t.m4´</TT>, <TT>`wint_t.m4´</TT>, <TT>`xsize.m4´</TT>
+If you do not have an <TT>‘aclocal.m4’</TT> file in your distribution,
+the simplest is to concatenate the files <TT>‘codeset.m4’</TT>,
+<TT>‘gettext.m4’</TT>, <TT>‘glibc2.m4’</TT>, <TT>‘glibc21.m4’</TT>, <TT>‘iconv.m4’</TT>,
+<TT>‘intdiv0.m4’</TT>, <TT>‘intmax.m4’</TT>, <TT>‘inttypes_h.m4’</TT>, <TT>‘inttypes-h.m4’</TT>,
+<TT>‘inttypes-pri.m4’</TT>, <TT>‘lcmessage.m4’</TT>,
+<TT>‘lib-ld.m4’</TT>, <TT>‘lib-link.m4’</TT>, <TT>‘lib-prefix.m4’</TT>, <TT>‘lock.m4’</TT>,
+<TT>‘longdouble.m4’</TT>, <TT>‘longlong.m4’</TT>, <TT>‘printf-posix.m4’</TT>,
+<TT>‘progtest.m4’</TT>, <TT>‘signed.m4’</TT>, <TT>‘size_max.m4’</TT>,
+<TT>‘stdint_h.m4’</TT>, <TT>‘uintmax_t.m4’</TT>, <TT>‘ulonglong.m4’</TT>,
+<TT>‘visibility.m4’</TT>, <TT>‘wchar_t.m4’</TT>, <TT>‘wint_t.m4’</TT>, <TT>‘xsize.m4’</TT>
from GNU <CODE>gettext</CODE>'s
-<TT>`m4/´</TT> directory into a single file. If you have suppressed the
-<TT>`intl/´</TT> directory, only <TT>`gettext.m4´</TT>, <TT>`iconv.m4´</TT>,
-<TT>`lib-ld.m4´</TT>, <TT>`lib-link.m4´</TT>, <TT>`lib-prefix.m4´</TT>,
-<TT>`progtest.m4´</TT> need to be concatenated.
+<TT>‘m4/’</TT> directory into a single file. If you have suppressed the
+<TT>‘intl/’</TT> directory, only <TT>‘gettext.m4’</TT>, <TT>‘iconv.m4’</TT>,
+<TT>‘lib-ld.m4’</TT>, <TT>‘lib-link.m4’</TT>, <TT>‘lib-prefix.m4’</TT>,
+<TT>‘progtest.m4’</TT> need to be concatenated.
</P>
<P>
-If you already have an <TT>`aclocal.m4´</TT> file, then you will have
-to merge the said macro files into your <TT>`aclocal.m4´</TT>. Note that if
+If you already have an <TT>‘aclocal.m4’</TT> file, then you will have
+to merge the said macro files into your <TT>‘aclocal.m4’</TT>. Note that if
you are upgrading from a previous release of GNU <CODE>gettext</CODE>, you
should most probably <EM>replace</EM> the macros (<CODE>AM_GNU_GETTEXT</CODE>,
etc.), as they usually
</P>
<P>
If you are using GNU <CODE>automake</CODE> 1.5 or newer, it is enough to put
-these macro files into a subdirectory named <TT>`m4/´</TT> and add the line
+these macro files into a subdirectory named <TT>‘m4/’</TT> and add the line
</P>
</PRE>
<P>
-to your top level <TT>`Makefile.am´</TT>.
+to your top level <TT>‘Makefile.am’</TT>.
</P>
<P>
</P>
-<H3><A NAME="SEC206" HREF="gettext_toc.html#TOC206">13.4.8 <TT>`acconfig.h´</TT> at top level</A></H3>
+<H3><A NAME="SEC209" HREF="gettext_toc.html#TOC209">13.4.9 <TT>‘acconfig.h’</TT> at top level</A></H3>
<P>
-<A NAME="IDX1050"></A>
+<A NAME="IDX1076"></A>
</P>
<P>
Earlier GNU <CODE>gettext</CODE> releases required to put definitions for
<CODE>ENABLE_NLS</CODE>, <CODE>HAVE_GETTEXT</CODE> and <CODE>HAVE_LC_MESSAGES</CODE>,
<CODE>HAVE_STPCPY</CODE>, <CODE>PACKAGE</CODE> and <CODE>VERSION</CODE> into an
-<TT>`acconfig.h´</TT> file. This is not needed any more; you can remove
-them from your <TT>`acconfig.h´</TT> file unless your package uses them
-independently from the <TT>`intl/´</TT> directory.
+<TT>‘acconfig.h’</TT> file. This is not needed any more; you can remove
+them from your <TT>‘acconfig.h’</TT> file unless your package uses them
+independently from the <TT>‘intl/’</TT> directory.
</P>
-<H3><A NAME="SEC207" HREF="gettext_toc.html#TOC207">13.4.9 <TT>`config.h.in´</TT> at top level</A></H3>
+<H3><A NAME="SEC210" HREF="gettext_toc.html#TOC210">13.4.10 <TT>‘config.h.in’</TT> at top level</A></H3>
<P>
-<A NAME="IDX1051"></A>
+<A NAME="IDX1077"></A>
</P>
<P>
The include file template that holds the C macros to be defined by
-<CODE>configure</CODE> is usually called <TT>`config.h.in´</TT> and may be
+<CODE>configure</CODE> is usually called <TT>‘config.h.in’</TT> and may be
maintained either manually or automatically.
</P>
<P>
-If <CODE>gettextize</CODE> has created an <TT>`intl/´</TT> directory, this file
-must be called <TT>`config.h.in´</TT> and must be at the top level. If,
-however, you have suppressed the <TT>`intl/´</TT> directory by calling
-<CODE>gettextize</CODE> without <SAMP>`--intl´</SAMP> option, then you can choose the
+If <CODE>gettextize</CODE> has created an <TT>‘intl/’</TT> directory, this file
+must be called <TT>‘config.h.in’</TT> and must be at the top level. If,
+however, you have suppressed the <TT>‘intl/’</TT> directory by calling
+<CODE>gettextize</CODE> without <SAMP>‘--intl’</SAMP> option, then you can choose the
name of this file and its location freely.
</P>
<P>
-If it is maintained automatically, by use of the <SAMP>`autoheader´</SAMP>
+If it is maintained automatically, by use of the <SAMP>‘autoheader’</SAMP>
program, you need to do nothing about it. This is the case in particular
if you are using GNU <CODE>automake</CODE>.
</P>
<P>
If it is maintained manually, and if <CODE>gettextize</CODE> has created an
-<TT>`intl/´</TT> directory, you should switch to using <SAMP>`autoheader´</SAMP>.
-The list of C macros to be added for the sake of the <TT>`intl/´</TT>
+<TT>‘intl/’</TT> directory, you should switch to using <SAMP>‘autoheader’</SAMP>.
+The list of C macros to be added for the sake of the <TT>‘intl/’</TT>
directory is just too long to be maintained manually; it also changes
between different versions of GNU <CODE>gettext</CODE>.
</P>
<P>
If it is maintained manually, and if on the other hand you have
-suppressed the <TT>`intl/´</TT> directory by calling <CODE>gettextize</CODE>
-without <SAMP>`--intl´</SAMP> option, then you can get away by adding the
-following lines to <TT>`config.h.in´</TT>:
+suppressed the <TT>‘intl/’</TT> directory by calling <CODE>gettextize</CODE>
+without <SAMP>‘--intl’</SAMP> option, then you can get away by adding the
+following lines to <TT>‘config.h.in’</TT>:
</P>
-<H3><A NAME="SEC208" HREF="gettext_toc.html#TOC208">13.4.10 <TT>`Makefile.in´</TT> at top level</A></H3>
+<H3><A NAME="SEC211" HREF="gettext_toc.html#TOC211">13.4.11 <TT>‘Makefile.in’</TT> at top level</A></H3>
<P>
Here are a few modifications you need to make to your main, top-level
-<TT>`Makefile.in´</TT> file.
+<TT>‘Makefile.in’</TT> file.
</P>
<OL>
<LI>
-Add the following lines near the beginning of your <TT>`Makefile.in´</TT>,
-so the <SAMP>`dist:´</SAMP> goal will work properly (as explained further down):
+Add the following lines near the beginning of your <TT>‘Makefile.in’</TT>,
+so the <SAMP>‘dist:’</SAMP> goal will work properly (as explained further down):
<PRE>
<LI>
-Add file <TT>`ABOUT-NLS´</TT> to the <CODE>DISTFILES</CODE> definition, so the file gets
+Add file <TT>‘ABOUT-NLS’</TT> to the <CODE>DISTFILES</CODE> definition, so the file gets
distributed.
<LI>
-Wherever you process subdirectories in your <TT>`Makefile.in´</TT>, be sure
-you also process the subdirectories <SAMP>`intl´</SAMP> and <SAMP>`po´</SAMP>. Special
-rules in the <TT>`Makefiles´</TT> take care for the case where no
+Wherever you process subdirectories in your <TT>‘Makefile.in’</TT>, be sure
+you also process the subdirectories <SAMP>‘intl’</SAMP> and <SAMP>‘po’</SAMP>. Special
+rules in the <TT>‘Makefiles’</TT> take care for the case where no
internationalization is wanted.
If you are using Makefiles, either generated by automake, or hand-written
so they carefully follow the GNU coding standards, the effected goals for
-which the new subdirectories must be handled include <SAMP>`installdirs´</SAMP>,
-<SAMP>`install´</SAMP>, <SAMP>`uninstall´</SAMP>, <SAMP>`clean´</SAMP>, <SAMP>`distclean´</SAMP>.
+which the new subdirectories must be handled include <SAMP>‘installdirs’</SAMP>,
+<SAMP>‘install’</SAMP>, <SAMP>‘uninstall’</SAMP>, <SAMP>‘clean’</SAMP>, <SAMP>‘distclean’</SAMP>.
Here is an example of a canonical order of processing. In this
example, we also define <CODE>SUBDIRS</CODE> in <CODE>Makefile.in</CODE> for it
-to be further used in the <SAMP>`dist:´</SAMP> goal.
+to be further used in the <SAMP>‘dist:’</SAMP> goal.
<PRE>
SUBDIRS = doc intl lib src po
</PRE>
-Note that you must arrange for <SAMP>`make´</SAMP> to descend into the
+Note that you must arrange for <SAMP>‘make’</SAMP> to descend into the
<CODE>intl</CODE> directory before descending into other directories containing
code which make use of the <CODE>libintl.h</CODE> header file. For this
reason, here we mention <CODE>intl</CODE> before <CODE>lib</CODE> and <CODE>src</CODE>.
<LI>
-A delicate point is the <SAMP>`dist:´</SAMP> goal, as both
-<TT>`intl/Makefile´</TT> and <TT>`po/Makefile´</TT> will later assume that the
-proper directory has been set up from the main <TT>`Makefile´</TT>. Here is
-an example at what the <SAMP>`dist:´</SAMP> goal might look like:
+A delicate point is the <SAMP>‘dist:’</SAMP> goal, as both
+<TT>‘intl/Makefile’</TT> and <TT>‘po/Makefile’</TT> will later assume that the
+proper directory has been set up from the main <TT>‘Makefile’</TT>. Here is
+an example at what the <SAMP>‘dist:’</SAMP> goal might look like:
<PRE>
</OL>
<P>
-Note that if you are using GNU <CODE>automake</CODE>, <TT>`Makefile.in´</TT> is
-automatically generated from <TT>`Makefile.am´</TT>, and all needed changes
-to <TT>`Makefile.am´</TT> are already made by running <SAMP>`gettextize´</SAMP>.
+Note that if you are using GNU <CODE>automake</CODE>, <TT>‘Makefile.in’</TT> is
+automatically generated from <TT>‘Makefile.am’</TT>, and all needed changes
+to <TT>‘Makefile.am’</TT> are already made by running <SAMP>‘gettextize’</SAMP>.
</P>
-<H3><A NAME="SEC209" HREF="gettext_toc.html#TOC209">13.4.11 <TT>`Makefile.in´</TT> in <TT>`src/´</TT></A></H3>
+<H3><A NAME="SEC212" HREF="gettext_toc.html#TOC212">13.4.12 <TT>‘Makefile.in’</TT> in <TT>‘src/’</TT></A></H3>
<P>
-Some of the modifications made in the main <TT>`Makefile.in´</TT> will
-also be needed in the <TT>`Makefile.in´</TT> from your package sources,
-which we assume here to be in the <TT>`src/´</TT> subdirectory. Here are
-all the modifications needed in <TT>`src/Makefile.in´</TT>:
+Some of the modifications made in the main <TT>‘Makefile.in’</TT> will
+also be needed in the <TT>‘Makefile.in’</TT> from your package sources,
+which we assume here to be in the <TT>‘src/’</TT> subdirectory. Here are
+all the modifications needed in <TT>‘src/Makefile.in’</TT>:
</P>
<OL>
<LI>
-In view of the <SAMP>`dist:´</SAMP> goal, you should have these lines near the
-beginning of <TT>`src/Makefile.in´</TT>:
+In view of the <SAMP>‘dist:’</SAMP> goal, you should have these lines near the
+beginning of <TT>‘src/Makefile.in’</TT>:
<PRE>
<LI>
-You might also want to define <CODE>subdir</CODE> as <SAMP>`src´</SAMP>, later
-allowing for almost uniform <SAMP>`dist:´</SAMP> goals in all your
-<TT>`Makefile.in´</TT>. At list, the <SAMP>`dist:´</SAMP> goal below assume that
+You might also want to define <CODE>subdir</CODE> as <SAMP>‘src’</SAMP>, later
+allowing for almost uniform <SAMP>‘dist:’</SAMP> goals in all your
+<TT>‘Makefile.in’</TT>. At list, the <SAMP>‘dist:’</SAMP> goal below assume that
you used:
<LI>
The <CODE>main</CODE> function of your program will normally call
-<CODE>bindtextdomain</CODE> (see see section <A HREF="gettext_4.html#SEC12">4.1 Triggering <CODE>gettext</CODE> Operations</A>), like this:
+<CODE>bindtextdomain</CODE> (see see section <A HREF="gettext_4.html#SEC13">4.2 Triggering <CODE>gettext</CODE> Operations</A>), like this:
<PRE>
</PRE>
To make LOCALEDIR known to the program, add the following lines to
-<TT>`Makefile.in´</TT>:
+<TT>‘Makefile.in’</TT>:
<PRE>
DEFS = -DLOCALEDIR=\"$(localedir)\" @DEFS@
</PRE>
-Note that <CODE>@datadir@</CODE> defaults to <SAMP>`$(prefix)/share´</SAMP>, thus
-<CODE>$(localedir)</CODE> defaults to <SAMP>`$(prefix)/share/locale´</SAMP>.
+Note that <CODE>@datadir@</CODE> defaults to <SAMP>‘$(prefix)/share’</SAMP>, thus
+<CODE>$(localedir)</CODE> defaults to <SAMP>‘$(prefix)/share/locale’</SAMP>.
<LI>
</PRE>
In most packages internationalized with GNU <CODE>gettext</CODE>, one will
-find a directory <TT>`lib/´</TT> in which a library containing some helper
+find a directory <TT>‘lib/’</TT> in which a library containing some helper
functions will be build. (You need at least the few functions which the
GNU <CODE>gettext</CODE> Library itself needs.) However some of the functions
-in the <TT>`lib/´</TT> also give messages to the user which of course should be
+in the <TT>‘lib/’</TT> also give messages to the user which of course should be
translated, too. Taking care of this, the support library (say
-<TT>`libsupport.a´</TT>) should be placed before <CODE>@LIBINTL@</CODE> and
+<TT>‘libsupport.a’</TT>) should be placed before <CODE>@LIBINTL@</CODE> and
<CODE>@LIBS@</CODE> in the above example. So one has to write this:
<LI>
-You should also ensure that directory <TT>`intl/´</TT> will be searched for
+You should also ensure that directory <TT>‘intl/’</TT> will be searched for
C preprocessor include files in all circumstances. So, you have to
-manage so both <SAMP>`-I../intl´</SAMP> and <SAMP>`-I$(top_srcdir)/intl´</SAMP> will
+manage so both <SAMP>‘-I../intl’</SAMP> and <SAMP>‘-I$(top_srcdir)/intl’</SAMP> will
be given to the C compiler.
<LI>
-Your <SAMP>`dist:´</SAMP> goal has to conform with others. Here is a
+Your <SAMP>‘dist:’</SAMP> goal has to conform with others. Here is a
reasonable definition for it:
</OL>
<P>
-Note that if you are using GNU <CODE>automake</CODE>, <TT>`Makefile.in´</TT> is
-automatically generated from <TT>`Makefile.am´</TT>, and the first three
+Note that if you are using GNU <CODE>automake</CODE>, <TT>‘Makefile.in’</TT> is
+automatically generated from <TT>‘Makefile.am’</TT>, and the first three
changes and the last change are not necessary. The remaining needed
-<TT>`Makefile.am´</TT> modifications are the following:
+<TT>‘Makefile.am’</TT> modifications are the following:
</P>
<LI>
To make LOCALEDIR known to the program, add the following to
-<TT>`Makefile.am´</TT>:
+<TT>‘Makefile.am’</TT>:
<PRE>
</PRE>
for all modules and compilation units together. Furthermore, add this
-line to define <SAMP>`localedir´</SAMP>:
+line to define <SAMP>‘localedir’</SAMP>:
<PRE>
To ensure that the final linking will use <CODE>@LIBINTL@</CODE> or
<CODE>@LTLIBINTL@</CODE> as a library, add the following to
-<TT>`Makefile.am´</TT>:
+<TT>‘Makefile.am’</TT>:
<PRE>
<LI>
-If you have an <TT>`intl/´</TT> directory, whose contents is created by
+If you have an <TT>‘intl/’</TT> directory, whose contents is created by
<CODE>gettextize</CODE>, then to ensure that it will be searched for
C preprocessor include files in all circumstances, add something like
-this to <TT>`Makefile.am´</TT>:
+this to <TT>‘Makefile.am’</TT>:
<PRE>
-<H3><A NAME="SEC210" HREF="gettext_toc.html#TOC210">13.4.12 <TT>`gettext.h´</TT> in <TT>`lib/´</TT></A></H3>
+<H3><A NAME="SEC213" HREF="gettext_toc.html#TOC213">13.4.13 <TT>‘gettext.h’</TT> in <TT>‘lib/’</TT></A></H3>
<P>
-<A NAME="IDX1052"></A>
-<A NAME="IDX1053"></A>
-<A NAME="IDX1054"></A>
+<A NAME="IDX1078"></A>
+<A NAME="IDX1079"></A>
+<A NAME="IDX1080"></A>
</P>
<P>
<UL>
<LI>
-When the installer has specified <SAMP>`./configure --disable-nls´</SAMP>. This
+When the installer has specified <SAMP>‘./configure --disable-nls’</SAMP>. This
can be useful when small binaries are more important than features, for
example when building utilities for boot diskettes. It can also be useful
in order to get some specific C compiler warnings about code quality with
A C preprocessor macro can be used to detect these two cases. Usually,
when <CODE>libintl.h</CODE> was found and not explicitly disabled, the
<CODE>ENABLE_NLS</CODE> macro will be defined to 1 in the autoconf generated
-configuration file (usually called <TT>`config.h´</TT>). In the two negative
+configuration file (usually called <TT>‘config.h’</TT>). In the two negative
situations, however, this macro will not be defined, thus it will evaluate
to 0 in C preprocessor expressions.
</P>
<P>
-<A NAME="IDX1055"></A>
-<TT>`gettext.h´</TT> is a convenience header file for conditional use of
-<TT>`<libintl.h>´</TT>, depending on the <CODE>ENABLE_NLS</CODE> macro. If
-<CODE>ENABLE_NLS</CODE> is set, it includes <TT>`<libintl.h>´</TT>; otherwise it
+<A NAME="IDX1081"></A>
+<TT>‘gettext.h’</TT> is a convenience header file for conditional use of
+<TT>‘<libintl.h>’</TT>, depending on the <CODE>ENABLE_NLS</CODE> macro. If
+<CODE>ENABLE_NLS</CODE> is set, it includes <TT>‘<libintl.h>’</TT>; otherwise it
defines no-op substitutes for the libintl.h functions. We recommend
-the use of <CODE>"gettext.h"</CODE> over direct use of <TT>`<libintl.h>´</TT>,
+the use of <CODE>"gettext.h"</CODE> over direct use of <TT>‘<libintl.h>’</TT>,
so that portability to older systems is guaranteed and installers can
turn off internationalization if they want to. In the C code, you will
then write
<P>
The location of <CODE>gettext.h</CODE> is usually in a directory containing
auxiliary include files. In many GNU packages, there is a directory
-<TT>`lib/´</TT> containing helper functions; <TT>`gettext.h´</TT> fits there.
-In other packages, it can go into the <TT>`src´</TT> directory.
+<TT>‘lib/’</TT> containing helper functions; <TT>‘gettext.h’</TT> fits there.
+In other packages, it can go into the <TT>‘src’</TT> directory.
</P>
<P>
</P>
-<H2><A NAME="SEC211" HREF="gettext_toc.html#TOC211">13.5 Autoconf macros for use in <TT>`configure.in´</TT></A></H2>
+<H2><A NAME="SEC214" HREF="gettext_toc.html#TOC214">13.5 Autoconf macros for use in <TT>‘configure.in’</TT></A></H2>
<P>
-<A NAME="IDX1056"></A>
+<A NAME="IDX1082"></A>
</P>
<P>
GNU <CODE>gettext</CODE> installs macros for use in a package's
-<TT>`configure.in´</TT> or <TT>`configure.ac´</TT>.
-See section `Introduction' in <CITE>The Autoconf Manual</CITE>.
+<TT>‘configure.in’</TT> or <TT>‘configure.ac’</TT>.
+See section ‘Introduction’ in <CITE>The Autoconf Manual</CITE>.
The primary macro is, of course, <CODE>AM_GNU_GETTEXT</CODE>.
</P>
-<H3><A NAME="SEC212" HREF="gettext_toc.html#TOC212">13.5.1 AM_GNU_GETTEXT in <TT>`gettext.m4´</TT></A></H3>
+<H3><A NAME="SEC215" HREF="gettext_toc.html#TOC215">13.5.1 AM_GNU_GETTEXT in <TT>‘gettext.m4’</TT></A></H3>
<P>
-<A NAME="IDX1057"></A>
+<A NAME="IDX1083"></A>
The <CODE>AM_GNU_GETTEXT</CODE> macro tests for the presence of the GNU gettext
function family in either the C library or a separate <CODE>libintl</CODE>
library (shared or static libraries are both supported) or in the package's
-<TT>`intl/´</TT> directory. It also invokes <CODE>AM_PO_SUBDIRS</CODE>, thus preparing
-the <TT>`po/´</TT> directories of the package for building.
+<TT>‘intl/’</TT> directory. It also invokes <CODE>AM_PO_SUBDIRS</CODE>, thus preparing
+the <TT>‘po/’</TT> directories of the package for building.
</P>
<P>
</PRE>
<P>
-<VAR>intlsymbol</VAR> can be <SAMP>`external´</SAMP> or <SAMP>`no-libtool´</SAMP>. The default
-(if it is not specified or empty) is <SAMP>`no-libtool´</SAMP>. <VAR>intlsymbol</VAR>
-should be <SAMP>`external´</SAMP> for packages with no <TT>`intl/´</TT> directory,
-and <SAMP>`no-libtool´</SAMP> for packages with an <TT>`intl/´</TT> directory. In
+<VAR>intlsymbol</VAR> can be <SAMP>‘external’</SAMP> or <SAMP>‘no-libtool’</SAMP>. The default
+(if it is not specified or empty) is <SAMP>‘no-libtool’</SAMP>. <VAR>intlsymbol</VAR>
+should be <SAMP>‘external’</SAMP> for packages with no <TT>‘intl/’</TT> directory,
+and <SAMP>‘no-libtool’</SAMP> for packages with an <TT>‘intl/’</TT> directory. In
the latter case, a static library <CODE>$(top_builddir)/intl/libintl.a</CODE>
will be created.
</P>
<P>
-If <VAR>needsymbol</VAR> is specified and is <SAMP>`need-ngettext´</SAMP>, then GNU
+If <VAR>needsymbol</VAR> is specified and is <SAMP>‘need-ngettext’</SAMP>, then GNU
gettext implementations (in libc or libintl) without the <CODE>ngettext()</CODE>
function will be ignored. If <VAR>needsymbol</VAR> is specified and is
-<SAMP>`need-formatstring-macros´</SAMP>, then GNU gettext implementations that don't
-support the ISO C 99 <TT>`<inttypes.h>´</TT> formatstring macros will be ignored.
+<SAMP>‘need-formatstring-macros’</SAMP>, then GNU gettext implementations that don't
+support the ISO C 99 <TT>‘<inttypes.h>’</TT> formatstring macros will be ignored.
Only one <VAR>needsymbol</VAR> can be specified. To specify more than one
requirement, just specify the strongest one among them. The hierarchy among
-the various alternatives is as follows: <SAMP>`need-formatstring-macros´</SAMP>
-implies <SAMP>`need-ngettext´</SAMP>.
+the various alternatives is as follows: <SAMP>‘need-formatstring-macros’</SAMP>
+implies <SAMP>‘need-ngettext’</SAMP>.
</P>
<P>
<VAR>intldir</VAR> is used to find the intl libraries. If empty, the value
-<SAMP>`$(top_builddir)/intl/´</SAMP> is used.
+<SAMP>‘$(top_builddir)/intl/’</SAMP> is used.
</P>
<P>
The <CODE>AM_GNU_GETTEXT</CODE> macro determines whether GNU gettext is
available and should be used. If so, it sets the <CODE>USE_NLS</CODE> variable
-to <SAMP>`yes´</SAMP>; it defines <CODE>ENABLE_NLS</CODE> to 1 in the autoconf
-generated configuration file (usually called <TT>`config.h´</TT>); it sets
+to <SAMP>‘yes’</SAMP>; it defines <CODE>ENABLE_NLS</CODE> to 1 in the autoconf
+generated configuration file (usually called <TT>‘config.h’</TT>); it sets
the variables <CODE>LIBINTL</CODE> and <CODE>LTLIBINTL</CODE> to the linker options
for use in a Makefile (<CODE>LIBINTL</CODE> for use without libtool,
-<CODE>LTLIBINTL</CODE> for use with libtool); it adds an <SAMP>`-I´</SAMP> option to
+<CODE>LTLIBINTL</CODE> for use with libtool); it adds an <SAMP>‘-I’</SAMP> option to
<CODE>CPPFLAGS</CODE> if necessary. In the negative case, it sets
-<CODE>USE_NLS</CODE> to <SAMP>`no´</SAMP>; it sets <CODE>LIBINTL</CODE> and <CODE>LTLIBINTL</CODE>
+<CODE>USE_NLS</CODE> to <SAMP>‘no’</SAMP>; it sets <CODE>LIBINTL</CODE> and <CODE>LTLIBINTL</CODE>
to empty and doesn't change <CODE>CPPFLAGS</CODE>.
</P>
<UL>
<LI>
-<A NAME="IDX1058"></A>
+<A NAME="IDX1084"></A>
Some operating systems have <CODE>gettext</CODE> in the C library, for example
glibc. Some have it in a separate library <CODE>libintl</CODE>. GNU <CODE>libintl</CODE>
might have been installed as part of the GNU <CODE>gettext</CODE> package.
-<H3><A NAME="SEC213" HREF="gettext_toc.html#TOC213">13.5.2 AM_GNU_GETTEXT_VERSION in <TT>`gettext.m4´</TT></A></H3>
+<H3><A NAME="SEC216" HREF="gettext_toc.html#TOC216">13.5.2 AM_GNU_GETTEXT_VERSION in <TT>‘gettext.m4’</TT></A></H3>
<P>
-<A NAME="IDX1059"></A>
+<A NAME="IDX1085"></A>
The <CODE>AM_GNU_GETTEXT_VERSION</CODE> macro declares the version number of
the GNU gettext infrastructure that is used by the package.
</P>
<P>
The use of this macro is optional; only the <CODE>autopoint</CODE> program makes
-use of it (see section <A HREF="gettext_13.html#SEC216">13.6 Integrating with CVS</A>).
+use of it (see section <A HREF="gettext_13.html#SEC219">13.6 Integrating with CVS</A>).
</P>
-<H3><A NAME="SEC214" HREF="gettext_toc.html#TOC214">13.5.3 AM_PO_SUBDIRS in <TT>`po.m4´</TT></A></H3>
+<H3><A NAME="SEC217" HREF="gettext_toc.html#TOC217">13.5.3 AM_PO_SUBDIRS in <TT>‘po.m4’</TT></A></H3>
<P>
-<A NAME="IDX1060"></A>
-The <CODE>AM_PO_SUBDIRS</CODE> macro prepares the <TT>`po/´</TT> directories of the
+<A NAME="IDX1086"></A>
+The <CODE>AM_PO_SUBDIRS</CODE> macro prepares the <TT>‘po/’</TT> directories of the
package for building. This macro should be used in internationalized
programs written in other programming languages than C, C++, Objective C,
-for example <CODE>sh</CODE>, <CODE>Python</CODE>, <CODE>Lisp</CODE>. See section <A HREF="gettext_15.html#SEC224">15 Other Programming Languages</A> for a list of programming languages that support localization
+for example <CODE>sh</CODE>, <CODE>Python</CODE>, <CODE>Lisp</CODE>. See section <A HREF="gettext_15.html#SEC227">15 Other Programming Languages</A> for a list of programming languages that support localization
through PO files.
</P>
<P>
The <CODE>AM_PO_SUBDIRS</CODE> macro determines whether internationalization
-should be used. If so, it sets the <CODE>USE_NLS</CODE> variable to <SAMP>`yes´</SAMP>,
-otherwise to <SAMP>`no´</SAMP>. It also determines the right values for Makefile
-variables in each <TT>`po/´</TT> directory.
+should be used. If so, it sets the <CODE>USE_NLS</CODE> variable to <SAMP>‘yes’</SAMP>,
+otherwise to <SAMP>‘no’</SAMP>. It also determines the right values for Makefile
+variables in each <TT>‘po/’</TT> directory.
</P>
-<H3><A NAME="SEC215" HREF="gettext_toc.html#TOC215">13.5.4 AM_ICONV in <TT>`iconv.m4´</TT></A></H3>
+<H3><A NAME="SEC218" HREF="gettext_toc.html#TOC218">13.5.4 AM_ICONV in <TT>‘iconv.m4’</TT></A></H3>
<P>
-<A NAME="IDX1061"></A>
+<A NAME="IDX1087"></A>
The <CODE>AM_ICONV</CODE> macro tests for the presence of the POSIX/XSI
<CODE>iconv</CODE> function family in either the C library or a separate
<CODE>libiconv</CODE> library. If found, it sets the <CODE>am_cv_func_iconv</CODE>
-variable to <SAMP>`yes´</SAMP>; it defines <CODE>HAVE_ICONV</CODE> to 1 in the autoconf
-generated configuration file (usually called <TT>`config.h´</TT>); it defines
-<CODE>ICONV_CONST</CODE> to <SAMP>`const´</SAMP> or to empty, depending on whether the
-second argument of <CODE>iconv()</CODE> is of type <SAMP>`const char **´</SAMP> or
-<SAMP>`char **´</SAMP>; it sets the variables <CODE>LIBICONV</CODE> and
+variable to <SAMP>‘yes’</SAMP>; it defines <CODE>HAVE_ICONV</CODE> to 1 in the autoconf
+generated configuration file (usually called <TT>‘config.h’</TT>); it defines
+<CODE>ICONV_CONST</CODE> to <SAMP>‘const’</SAMP> or to empty, depending on whether the
+second argument of <CODE>iconv()</CODE> is of type <SAMP>‘const char **’</SAMP> or
+<SAMP>‘char **’</SAMP>; it sets the variables <CODE>LIBICONV</CODE> and
<CODE>LTLIBICONV</CODE> to the linker options for use in a Makefile
(<CODE>LIBICONV</CODE> for use without libtool, <CODE>LTLIBICONV</CODE> for use with
-libtool); it adds an <SAMP>`-I´</SAMP> option to <CODE>CPPFLAGS</CODE> if
+libtool); it adds an <SAMP>‘-I’</SAMP> option to <CODE>CPPFLAGS</CODE> if
necessary. If not found, it sets <CODE>LIBICONV</CODE> and <CODE>LTLIBICONV</CODE> to
empty and doesn't change <CODE>CPPFLAGS</CODE>.
<UL>
<LI>
-<A NAME="IDX1062"></A>
+<A NAME="IDX1088"></A>
Some operating systems have <CODE>iconv</CODE> in the C library, for example
glibc. Some have it in a separate library <CODE>libiconv</CODE>, for example
OSF/1 or FreeBSD. Regardless of the operating system, GNU <CODE>libiconv</CODE>
<LI>
GNU <CODE>libiconv</CODE> is binary incompatible with some operating system's
-native <CODE>iconv</CODE>, for example on FreeBSD. Use of an <TT>`iconv.h´</TT>
-and <TT>`libiconv.so´</TT> that don't fit together would produce program
+native <CODE>iconv</CODE>, for example on FreeBSD. Use of an <TT>‘iconv.h’</TT>
+and <TT>‘libiconv.so’</TT> that don't fit together would produce program
crashes.
<LI>
</UL>
<P>
-<TT>`iconv.m4´</TT> is distributed with the GNU gettext package because
-<TT>`gettext.m4´</TT> relies on it.
+<TT>‘iconv.m4’</TT> is distributed with the GNU gettext package because
+<TT>‘gettext.m4’</TT> relies on it.
</P>
-<H2><A NAME="SEC216" HREF="gettext_toc.html#TOC216">13.6 Integrating with CVS</A></H2>
+<H2><A NAME="SEC219" HREF="gettext_toc.html#TOC219">13.6 Integrating with CVS</A></H2>
<P>
Many projects use CVS for distributed development, version control and
-<H3><A NAME="SEC217" HREF="gettext_toc.html#TOC217">13.6.1 Avoiding version mismatch in distributed development</A></H3>
+<H3><A NAME="SEC220" HREF="gettext_toc.html#TOC220">13.6.1 Avoiding version mismatch in distributed development</A></H3>
<P>
In a project development with multiple developers, using CVS, there
should be a single developer who occasionally - when there is desire to
upgrade to a new <CODE>gettext</CODE> version - runs <CODE>gettextize</CODE> and
-performs the changes listed in section <A HREF="gettext_13.html#SEC198">13.4 Files You Must Create or Alter</A>, and then commits
+performs the changes listed in section <A HREF="gettext_13.html#SEC200">13.4 Files You Must Create or Alter</A>, and then commits
his changes to the CVS.
</P>
<LI>
Apparent version mismatch between developers. Since some <CODE>gettext</CODE>
-specific portions in <TT>`configure.in´</TT>, <TT>`configure.ac´</TT> and
+specific portions in <TT>‘configure.in’</TT>, <TT>‘configure.ac’</TT> and
<CODE>Makefile.am</CODE>, <CODE>Makefile.in</CODE> files depend on the <CODE>gettext</CODE>
version, the use of infrastructure files belonging to different
<CODE>gettext</CODE> versions can easily lead to build errors.
-<H3><A NAME="SEC218" HREF="gettext_toc.html#TOC218">13.6.2 Files to put under CVS version control</A></H3>
+<H3><A NAME="SEC221" HREF="gettext_toc.html#TOC221">13.6.2 Files to put under CVS version control</A></H3>
<P>
There are basically three ways to deal with generated files in the
-context of a CVS repository, such as <TT>`configure´</TT> generated from
-<TT>`configure.in´</TT>, <CODE><VAR>parser</VAR>.c</CODE> generated from
+context of a CVS repository, such as <TT>‘configure’</TT> generated from
+<TT>‘configure.in’</TT>, <CODE><VAR>parser</VAR>.c</CODE> generated from
<CODE><VAR>parser</VAR>.y</CODE>, or <CODE>po/Makefile.in.in</CODE> autoinstalled by
<CODE>gettextize</CODE> or <CODE>autopoint</CODE>.
<P>
For the third approach, the maintainer can omit from the CVS repository
all the files that <CODE>gettextize</CODE> mentions as "copy". Instead, he
-adds to the <TT>`configure.in´</TT> or <TT>`configure.ac´</TT> a line of the
+adds to the <TT>‘configure.in’</TT> or <TT>‘configure.ac’</TT> a line of the
form
</P>
<PRE>
-AM_GNU_GETTEXT_VERSION(0.15-pre0)
+AM_GNU_GETTEXT_VERSION(0.15)
</PRE>
<P>
and adds to the package's pre-build script an invocation of
-<SAMP>`autopoint´</SAMP>. For everyone who checks out the CVS, this
+<SAMP>‘autopoint’</SAMP>. For everyone who checks out the CVS, this
<CODE>autopoint</CODE> invocation will copy into the right place the
<CODE>gettext</CODE> infrastructure files that have been omitted from the CVS.
<P>
The version number used as argument to <CODE>AM_GNU_GETTEXT_VERSION</CODE> is
the version of the <CODE>gettext</CODE> infrastructure that the package wants
-to use. It is also the minimum version number of the <SAMP>`autopoint´</SAMP>
+to use. It is also the minimum version number of the <SAMP>‘autopoint’</SAMP>
program. So, if you write <CODE>AM_GNU_GETTEXT_VERSION(0.11.5)</CODE> then the
developers can have any version >= 0.11.5 installed; the package will work
with the 0.11.5 infrastructure in all developers' builds. When the
</P>
-<H3><A NAME="SEC219" HREF="gettext_toc.html#TOC219">13.6.3 Invoking the <CODE>autopoint</CODE> Program</A></H3>
+<H3><A NAME="SEC222" HREF="gettext_toc.html#TOC222">13.6.3 Invoking the <CODE>autopoint</CODE> Program</A></H3>
<P>
-<A NAME="IDX1063"></A>
-<A NAME="IDX1064"></A>
+<A NAME="IDX1089"></A>
+<A NAME="IDX1090"></A>
<PRE>
autopoint [<VAR>option</VAR>]...
The <CODE>autopoint</CODE> program copies standard gettext infrastructure files
into a source package. It extracts from a macro call of the form
<CODE>AM_GNU_GETTEXT_VERSION(<VAR>version</VAR>)</CODE>, found in the package's
-<TT>`configure.in´</TT> or <TT>`configure.ac´</TT> file, the gettext version
+<TT>‘configure.in’</TT> or <TT>‘configure.ac’</TT> file, the gettext version
used by the package, and copies the infrastructure files belonging to
this version into the package.
</P>
-<H4><A NAME="SEC220" HREF="gettext_toc.html#TOC220">13.6.3.1 Options</A></H4>
+<H4><A NAME="SEC223" HREF="gettext_toc.html#TOC223">13.6.3.1 Options</A></H4>
<DL COMPACT>
-<DT><SAMP>`-f´</SAMP>
+<DT><SAMP>‘-f’</SAMP>
<DD>
-<DT><SAMP>`--force´</SAMP>
+<DT><SAMP>‘--force’</SAMP>
<DD>
-<A NAME="IDX1065"></A>
-<A NAME="IDX1066"></A>
+<A NAME="IDX1091"></A>
+<A NAME="IDX1092"></A>
Force overwriting of files that already exist.
-<DT><SAMP>`-n´</SAMP>
+<DT><SAMP>‘-n’</SAMP>
<DD>
-<DT><SAMP>`--dry-run´</SAMP>
+<DT><SAMP>‘--dry-run’</SAMP>
<DD>
-<A NAME="IDX1067"></A>
-<A NAME="IDX1068"></A>
+<A NAME="IDX1093"></A>
+<A NAME="IDX1094"></A>
Print modifications but don't perform them. All file copying actions that
<CODE>autopoint</CODE> would normally execute are inhibited and instead only
listed on standard output.
-<H4><A NAME="SEC221" HREF="gettext_toc.html#TOC221">13.6.3.2 Informative output</A></H4>
+<H4><A NAME="SEC224" HREF="gettext_toc.html#TOC224">13.6.3.2 Informative output</A></H4>
<DL COMPACT>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX1069"></A>
+<A NAME="IDX1095"></A>
Display this help and exit.
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX1070"></A>
+<A NAME="IDX1096"></A>
Output version information and exit.
</DL>
<P>
<CODE>autopoint</CODE> supports the GNU <CODE>gettext</CODE> versions from 0.10.35 to
-the current one, 0.15-pre0. In order to apply <CODE>autopoint</CODE> to
-a package using a <CODE>gettext</CODE> version newer than 0.15-pre0, you
+the current one, 0.15. In order to apply <CODE>autopoint</CODE> to
+a package using a <CODE>gettext</CODE> version newer than 0.15, you
need to install this same version of GNU <CODE>gettext</CODE> at least.
</P>
should be followed by invocations of <CODE>aclocal</CODE> and then <CODE>autoconf</CODE>
and <CODE>autoheader</CODE>. The reason is that <CODE>autopoint</CODE> installs some
autoconf macro files, which are used by <CODE>aclocal</CODE> to create
-<TT>`aclocal.m4´</TT>, and the latter is used by <CODE>autoconf</CODE> to create the
-package's <TT>`configure´</TT> script and by <CODE>autoheader</CODE> to create the
-package's <TT>`config.h.in´</TT> include file template.
+<TT>‘aclocal.m4’</TT>, and the latter is used by <CODE>autoconf</CODE> to create the
+package's <TT>‘configure’</TT> script and by <CODE>autoheader</CODE> to create the
+package's <TT>‘config.h.in’</TT> include file template.
</P>
<P>
-The name <SAMP>`autopoint´</SAMP> is an abbreviation of <SAMP>`auto-po-intl-m4´</SAMP>;
-the tool copies or updates mostly files in the <TT>`po´</TT>, <TT>`intl´</TT>,
-<TT>`m4´</TT> directories.
+The name <SAMP>‘autopoint’</SAMP> is an abbreviation of <SAMP>‘auto-po-intl-m4’</SAMP>;
+the tool copies or updates mostly files in the <TT>‘po’</TT>, <TT>‘intl’</TT>,
+<TT>‘m4’</TT> directories.
</P>
-<H2><A NAME="SEC222" HREF="gettext_toc.html#TOC222">13.7 Creating a Distribution Tarball</A></H2>
+<H2><A NAME="SEC225" HREF="gettext_toc.html#TOC225">13.7 Creating a Distribution Tarball</A></H2>
<P>
-<A NAME="IDX1071"></A>
-<A NAME="IDX1072"></A>
+<A NAME="IDX1097"></A>
+<A NAME="IDX1098"></A>
In projects that use GNU <CODE>automake</CODE>, the usual commands for creating
-a distribution tarball, <SAMP>`make dist´</SAMP> or <SAMP>`make distcheck´</SAMP>,
+a distribution tarball, <SAMP>‘make dist’</SAMP> or <SAMP>‘make distcheck’</SAMP>,
automatically update the PO files as needed.
</P>
</PRE>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_12.html">previous</A>, <A HREF="gettext_14.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_12.html">previous</A>, <A HREF="gettext_14.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 14 The Installer's and Distributor's View</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_13.html">previous</A>, <A HREF="gettext_15.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_13.html">previous</A>, <A HREF="gettext_15.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC223" HREF="gettext_toc.html#TOC223">14 The Installer's and Distributor's View</A></H1>
+<H1><A NAME="SEC226" HREF="gettext_toc.html#TOC226">14 The Installer's and Distributor's View</A></H1>
<P>
-<A NAME="IDX1073"></A>
-<A NAME="IDX1074"></A>
-<A NAME="IDX1075"></A>
-<A NAME="IDX1076"></A>
+<A NAME="IDX1099"></A>
+<A NAME="IDX1100"></A>
+<A NAME="IDX1101"></A>
+<A NAME="IDX1102"></A>
</P>
<P>
the GNU <CODE>gettext</CODE> functions. If not,
the GNU <CODE>gettext</CODE> library should be automatically prepared
and used. Installers may use special options at configuration
-time for changing this behavior. The command <SAMP>`./configure
---with-included-gettext´</SAMP> bypasses system <CODE>gettext</CODE> to
+time for changing this behavior. The command <SAMP>‘./configure
+--with-included-gettext’</SAMP> bypasses system <CODE>gettext</CODE> to
use the included GNU <CODE>gettext</CODE> instead,
-while <SAMP>`./configure --disable-nls´</SAMP>
+while <SAMP>‘./configure --disable-nls’</SAMP>
produces programs totally unable to translate messages.
</P>
<P>
-<A NAME="IDX1077"></A>
-Internationalized packages have usually many <TT>`<VAR>ll</VAR>.po´</TT>
+<A NAME="IDX1103"></A>
+Internationalized packages have usually many <TT>‘<VAR>ll</VAR>.po’</TT>
files. Unless
translations are disabled, all those available are installed together
with the package. However, the environment variable <CODE>LINGUAS</CODE>
</P>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_13.html">previous</A>, <A HREF="gettext_15.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_13.html">previous</A>, <A HREF="gettext_15.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 15 Other Programming Languages</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_14.html">previous</A>, <A HREF="gettext_16.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_14.html">previous</A>, <A HREF="gettext_16.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC224" HREF="gettext_toc.html#TOC224">15 Other Programming Languages</A></H1>
+<H1><A NAME="SEC227" HREF="gettext_toc.html#TOC227">15 Other Programming Languages</A></H1>
<P>
While the presentation of <CODE>gettext</CODE> focuses mostly on C and
-<H2><A NAME="SEC225" HREF="gettext_toc.html#TOC225">15.1 The Language Implementor's View</A></H2>
+<H2><A NAME="SEC228" HREF="gettext_toc.html#TOC228">15.1 The Language Implementor's View</A></H2>
<P>
-<A NAME="IDX1078"></A>
-<A NAME="IDX1079"></A>
+<A NAME="IDX1104"></A>
+<A NAME="IDX1105"></A>
</P>
<P>
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 <A HREF="gettext_4.html#SEC16">4.5 Special Comments preceding Keywords</A>.
+output the substituted arguments in different order. See section <A HREF="gettext_4.html#SEC17">4.6 Special Comments preceding Keywords</A>.
<LI>
<LI>
To help the programmer in the task of marking translatable strings,
-which is usually performed using the Emacs PO mode, you are welcome to
+which is sometimes performed using the Emacs PO mode (see section <A HREF="gettext_4.html#SEC16">4.5 Marking Translatable Strings</A>),
+you are welcome to
contact the GNU <CODE>gettext</CODE> maintainers, so they can add support for
-your language to <TT>`po-mode.el´</TT>.
+your language to <TT>‘po-mode.el’</TT>.
</OL>
<P>
<UL>
<LI>
-You may integrate the GNU <CODE>gettext</CODE>'s <TT>`intl/´</TT> directory in
-your package, as described in section <A HREF="gettext_13.html#SEC194">13 The Maintainer's View</A>. This allows you to
+You may integrate the GNU <CODE>gettext</CODE>'s <TT>‘intl/’</TT> directory in
+your package, as described in section <A HREF="gettext_13.html#SEC196">13 The Maintainer's View</A>. 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
-<H2><A NAME="SEC226" HREF="gettext_toc.html#TOC226">15.2 The Programmer's View</A></H2>
+<H2><A NAME="SEC229" HREF="gettext_toc.html#TOC229">15.2 The Programmer's View</A></H2>
<P>
For the programmer, the general procedure is the same as for the C
-language. The Emacs PO mode supports other languages, and the GNU
+language. The Emacs PO mode marking supports other languages, and the GNU
<CODE>xgettext</CODE> string extractor recognizes other languages based on the
file extension or a command-line option. In some languages,
<CODE>setlocale</CODE> is not needed because it is already performed by the
</P>
-<H2><A NAME="SEC227" HREF="gettext_toc.html#TOC227">15.3 The Translator's View</A></H2>
+<H2><A NAME="SEC230" HREF="gettext_toc.html#TOC230">15.3 The Translator's View</A></H2>
<P>
The translator works exactly as in the C language case. The only
-<H3><A NAME="SEC228" HREF="gettext_toc.html#TOC228">15.3.1 C Format Strings</A></H3>
+<H3><A NAME="SEC231" HREF="gettext_toc.html#TOC231">15.3.1 C Format Strings</A></H3>
<P>
C format strings are described in POSIX (IEEE P1003.1 2001), section
<P>
are a POSIX/XSI feature and not specified by ISO C 99, translators can rely
on this reordering ability: On the few platforms where <CODE>printf()</CODE>,
-<CODE>fprintf()</CODE> etc. don't support this feature natively, <TT>`libintl.a´</TT>
-or <TT>`libintl.so´</TT> provides replacement functions, and GNU <CODE><libintl.h></CODE>
+<CODE>fprintf()</CODE> etc. don't support this feature natively, <TT>‘libintl.a’</TT>
+or <TT>‘libintl.so’</TT> provides replacement functions, and GNU <CODE><libintl.h></CODE>
activates these replacement functions automatically.
</P>
<P>
-<A NAME="IDX1080"></A>
-<A NAME="IDX1081"></A>
+<A NAME="IDX1106"></A>
+<A NAME="IDX1107"></A>
As a special feature for Farsi (Persian) and maybe Arabic, translators can
-insert an <SAMP>`I´</SAMP> flag into numeric format directives. For example, the
+insert an <SAMP>‘I’</SAMP> flag into numeric format directives. For example, the
translation of <CODE>"%d"</CODE> can be <CODE>"%Id"</CODE>. The effect of this flag,
on systems with GNU <CODE>libc</CODE>, is that in the output, the ASCII digits are
-replaced with the <SAMP>`outdigits´</SAMP> defined in the <CODE>LC_CTYPE</CODE> locale
+replaced with the <SAMP>‘outdigits’</SAMP> defined in the <CODE>LC_CTYPE</CODE> locale
facet. On other systems, the <CODE>gettext</CODE> function removes this flag,
so that it has no effect.
</P>
<P>
Note that the programmer should <EM>not</EM> put this flag into the
-untranslated string. (Putting the <SAMP>`I´</SAMP> format directive flag into an
+untranslated string. (Putting the <SAMP>‘I’</SAMP> format directive flag into an
<VAR>msgid</VAR> string would lead to undefined behaviour on platforms without
glibc when NLS is disabled.)
</P>
-<H3><A NAME="SEC229" HREF="gettext_toc.html#TOC229">15.3.2 Objective C Format Strings</A></H3>
+<H3><A NAME="SEC232" HREF="gettext_toc.html#TOC232">15.3.2 Objective C Format Strings</A></H3>
<P>
Objective C format strings are like C format strings. They support an
</P>
-<H3><A NAME="SEC230" HREF="gettext_toc.html#TOC230">15.3.3 Shell Format Strings</A></H3>
+<H3><A NAME="SEC233" HREF="gettext_toc.html#TOC233">15.3.3 Shell Format Strings</A></H3>
<P>
-Shell format strings, as supported by GNU gettext and the <SAMP>`envsubst´</SAMP>
+Shell format strings, as supported by GNU gettext and the <SAMP>‘envsubst’</SAMP>
program, are strings with references to shell variables in the form
<CODE>$<VAR>variable</VAR></CODE> or <CODE>${<VAR>variable</VAR>}</CODE>. References of the form
<CODE>${<VAR>variable</VAR>-<VAR>default</VAR>}</CODE>,
</P>
-<H3><A NAME="SEC231" HREF="gettext_toc.html#TOC231">15.3.4 Python Format Strings</A></H3>
+<H3><A NAME="SEC234" HREF="gettext_toc.html#TOC234">15.3.4 Python Format Strings</A></H3>
<P>
Python format strings are described in
</P>
-<H3><A NAME="SEC232" HREF="gettext_toc.html#TOC232">15.3.5 Lisp Format Strings</A></H3>
+<H3><A NAME="SEC235" HREF="gettext_toc.html#TOC235">15.3.5 Lisp Format Strings</A></H3>
<P>
Lisp format strings are described in the Common Lisp HyperSpec,
</P>
-<H3><A NAME="SEC233" HREF="gettext_toc.html#TOC233">15.3.6 Emacs Lisp Format Strings</A></H3>
+<H3><A NAME="SEC236" HREF="gettext_toc.html#TOC236">15.3.6 Emacs Lisp Format Strings</A></H3>
<P>
Emacs Lisp format strings are documented in the Emacs Lisp reference,
</P>
-<H3><A NAME="SEC234" HREF="gettext_toc.html#TOC234">15.3.7 librep Format Strings</A></H3>
+<H3><A NAME="SEC237" HREF="gettext_toc.html#TOC237">15.3.7 librep Format Strings</A></H3>
<P>
librep format strings are documented in the librep manual, section
</P>
-<H3><A NAME="SEC235" HREF="gettext_toc.html#TOC235">15.3.8 Scheme Format Strings</A></H3>
+<H3><A NAME="SEC238" HREF="gettext_toc.html#TOC238">15.3.8 Scheme Format Strings</A></H3>
<P>
Scheme format strings are documented in the SLIB manual, section
</P>
-<H3><A NAME="SEC236" HREF="gettext_toc.html#TOC236">15.3.9 Smalltalk Format Strings</A></H3>
+<H3><A NAME="SEC239" HREF="gettext_toc.html#TOC239">15.3.9 Smalltalk Format Strings</A></H3>
<P>
Smalltalk format strings are described in the GNU Smalltalk documentation,
-class <CODE>CharArray</CODE>, methods <SAMP>`bindWith:´</SAMP> and
-<SAMP>`bindWithArguments:´</SAMP>.
+class <CODE>CharArray</CODE>, methods <SAMP>‘bindWith:’</SAMP> and
+<SAMP>‘bindWithArguments:’</SAMP>.
<A HREF="http://www.gnu.org/software/smalltalk/gst-manual/gst_68.html#SEC238">http://www.gnu.org/software/smalltalk/gst-manual/gst_68.html#SEC238</A>.
-In summary, a directive starts with <SAMP>`%´</SAMP> and is followed by <SAMP>`%´</SAMP>
-or a nonzero digit (<SAMP>`1´</SAMP> to <SAMP>`9´</SAMP>).
+In summary, a directive starts with <SAMP>‘%’</SAMP> and is followed by <SAMP>‘%’</SAMP>
+or a nonzero digit (<SAMP>‘1’</SAMP> to <SAMP>‘9’</SAMP>).
</P>
-<H3><A NAME="SEC237" HREF="gettext_toc.html#TOC237">15.3.10 Java Format Strings</A></H3>
+<H3><A NAME="SEC240" HREF="gettext_toc.html#TOC240">15.3.10 Java Format Strings</A></H3>
<P>
Java format strings are described in the JDK documentation for class
</P>
-<H3><A NAME="SEC238" HREF="gettext_toc.html#TOC238">15.3.11 C# Format Strings</A></H3>
+<H3><A NAME="SEC241" HREF="gettext_toc.html#TOC241">15.3.11 C# Format Strings</A></H3>
<P>
C# format strings are described in the .NET documentation for class
</P>
-<H3><A NAME="SEC239" HREF="gettext_toc.html#TOC239">15.3.12 awk Format Strings</A></H3>
+<H3><A NAME="SEC242" HREF="gettext_toc.html#TOC242">15.3.12 awk Format Strings</A></H3>
<P>
awk format strings are described in the gawk documentation, section
</P>
-<H3><A NAME="SEC240" HREF="gettext_toc.html#TOC240">15.3.13 Object Pascal Format Strings</A></H3>
+<H3><A NAME="SEC243" HREF="gettext_toc.html#TOC243">15.3.13 Object Pascal Format Strings</A></H3>
<P>
Where is this documented?
</P>
-<H3><A NAME="SEC241" HREF="gettext_toc.html#TOC241">15.3.14 YCP Format Strings</A></H3>
+<H3><A NAME="SEC244" HREF="gettext_toc.html#TOC244">15.3.14 YCP Format Strings</A></H3>
<P>
YCP sformat strings are described in the libycp documentation
<A HREF="file:/usr/share/doc/packages/libycp/YCP-builtins.html">file:/usr/share/doc/packages/libycp/YCP-builtins.html</A>.
-In summary, a directive starts with <SAMP>`%´</SAMP> and is followed by <SAMP>`%´</SAMP>
-or a nonzero digit (<SAMP>`1´</SAMP> to <SAMP>`9´</SAMP>).
+In summary, a directive starts with <SAMP>‘%’</SAMP> and is followed by <SAMP>‘%’</SAMP>
+or a nonzero digit (<SAMP>‘1’</SAMP> to <SAMP>‘9’</SAMP>).
</P>
-<H3><A NAME="SEC242" HREF="gettext_toc.html#TOC242">15.3.15 Tcl Format Strings</A></H3>
+<H3><A NAME="SEC245" HREF="gettext_toc.html#TOC245">15.3.15 Tcl Format Strings</A></H3>
<P>
-Tcl format strings are described in the <TT>`format.n´</TT> manual page,
+Tcl format strings are described in the <TT>‘format.n’</TT> manual page,
<A HREF="http://www.scriptics.com/man/tcl8.3/TclCmd/format.htm">http://www.scriptics.com/man/tcl8.3/TclCmd/format.htm</A>.
</P>
-<H3><A NAME="SEC243" HREF="gettext_toc.html#TOC243">15.3.16 Perl Format Strings</A></H3>
+<H3><A NAME="SEC246" HREF="gettext_toc.html#TOC246">15.3.16 Perl Format Strings</A></H3>
<P>
There are two kinds format strings in Perl: those acceptable to the
-Perl built-in function <CODE>printf</CODE>, labelled as <SAMP>`perl-format´</SAMP>,
+Perl built-in function <CODE>printf</CODE>, labelled as <SAMP>‘perl-format’</SAMP>,
and those acceptable to the <CODE>libintl-perl</CODE> function <CODE>__x</CODE>,
-labelled as <SAMP>`perl-brace-format´</SAMP>.
+labelled as <SAMP>‘perl-brace-format’</SAMP>.
</P>
<P>
Perl <CODE>printf</CODE> format strings are described in the <CODE>sprintf</CODE>
-section of <SAMP>`man perlfunc´</SAMP>.
+section of <SAMP>‘man perlfunc’</SAMP>.
</P>
<P>
Perl brace format strings are described in the
-<TT>`Locale::TextDomain(3pm)´</TT> manual page of the CPAN package
+<TT>‘Locale::TextDomain(3pm)’</TT> manual page of the CPAN package
libintl-perl. In brief, Perl format uses placeholders put between
-braces (<SAMP>`{´</SAMP> and <SAMP>`}´</SAMP>). The placeholder must have the syntax
+braces (<SAMP>‘{’</SAMP> and <SAMP>‘}’</SAMP>). The placeholder must have the syntax
of simple identifiers.
</P>
-<H3><A NAME="SEC244" HREF="gettext_toc.html#TOC244">15.3.17 PHP Format Strings</A></H3>
+<H3><A NAME="SEC247" HREF="gettext_toc.html#TOC247">15.3.17 PHP Format Strings</A></H3>
<P>
PHP format strings are described in the documentation of the PHP function
-<CODE>sprintf</CODE>, in <TT>`phpdoc/manual/function.sprintf.html´</TT> or
+<CODE>sprintf</CODE>, in <TT>‘phpdoc/manual/function.sprintf.html’</TT> or
<A HREF="http://www.php.net/manual/en/function.sprintf.php">http://www.php.net/manual/en/function.sprintf.php</A>.
</P>
-<H3><A NAME="SEC245" HREF="gettext_toc.html#TOC245">15.3.18 GCC internal Format Strings</A></H3>
+<H3><A NAME="SEC248" HREF="gettext_toc.html#TOC248">15.3.18 GCC internal Format Strings</A></H3>
<P>
These format strings are used inside the GCC sources. In such a format
-string, a directive starts with <SAMP>`%´</SAMP>, is optionally followed by a
-size specifier <SAMP>`l´</SAMP>, an optional flag <SAMP>`+´</SAMP>, another optional flag
-<SAMP>`#´</SAMP>, and is finished by a specifier: <SAMP>`%´</SAMP> denotes a literal
-percent sign, <SAMP>`c´</SAMP> denotes a character, <SAMP>`s´</SAMP> denotes a string,
-<SAMP>`i´</SAMP> and <SAMP>`d´</SAMP> denote an integer, <SAMP>`o´</SAMP>, <SAMP>`u´</SAMP>, <SAMP>`x´</SAMP>
-denote an unsigned integer, <SAMP>`.*s´</SAMP> denotes a string preceded by a
-width specification, <SAMP>`H´</SAMP> denotes a <SAMP>`location_t *´</SAMP> pointer,
-<SAMP>`D´</SAMP> denotes a general declaration, <SAMP>`F´</SAMP> denotes a function
-declaration, <SAMP>`T´</SAMP> denotes a type, <SAMP>`A´</SAMP> denotes a function argument,
-<SAMP>`C´</SAMP> denotes a tree code, <SAMP>`E´</SAMP> denotes an expression, <SAMP>`L´</SAMP>
-denotes a programming language, <SAMP>`O´</SAMP> denotes a binary operator,
-<SAMP>`P´</SAMP> denotes a function parameter, <SAMP>`Q´</SAMP> denotes an assignment
-operator, <SAMP>`V´</SAMP> denotes a const/volatile qualifier.
+string, a directive starts with <SAMP>‘%’</SAMP>, is optionally followed by a
+size specifier <SAMP>‘l’</SAMP>, an optional flag <SAMP>‘+’</SAMP>, another optional flag
+<SAMP>‘#’</SAMP>, and is finished by a specifier: <SAMP>‘%’</SAMP> denotes a literal
+percent sign, <SAMP>‘c’</SAMP> denotes a character, <SAMP>‘s’</SAMP> denotes a string,
+<SAMP>‘i’</SAMP> and <SAMP>‘d’</SAMP> denote an integer, <SAMP>‘o’</SAMP>, <SAMP>‘u’</SAMP>, <SAMP>‘x’</SAMP>
+denote an unsigned integer, <SAMP>‘.*s’</SAMP> denotes a string preceded by a
+width specification, <SAMP>‘H’</SAMP> denotes a <SAMP>‘location_t *’</SAMP> pointer,
+<SAMP>‘D’</SAMP> denotes a general declaration, <SAMP>‘F’</SAMP> denotes a function
+declaration, <SAMP>‘T’</SAMP> denotes a type, <SAMP>‘A’</SAMP> denotes a function argument,
+<SAMP>‘C’</SAMP> denotes a tree code, <SAMP>‘E’</SAMP> denotes an expression, <SAMP>‘L’</SAMP>
+denotes a programming language, <SAMP>‘O’</SAMP> denotes a binary operator,
+<SAMP>‘P’</SAMP> denotes a function parameter, <SAMP>‘Q’</SAMP> denotes an assignment
+operator, <SAMP>‘V’</SAMP> denotes a const/volatile qualifier.
</P>
-<H3><A NAME="SEC246" HREF="gettext_toc.html#TOC246">15.3.19 Qt Format Strings</A></H3>
+<H3><A NAME="SEC249" HREF="gettext_toc.html#TOC249">15.3.19 Qt Format Strings</A></H3>
<P>
Qt format strings are described in the documentation of the QString class
<A HREF="file:/usr/lib/qt-3.0.5/doc/html/qstring.html">file:/usr/lib/qt-3.0.5/doc/html/qstring.html</A>.
-In summary, a directive consists of a <SAMP>`%´</SAMP> followed by a digit. The same
+In summary, a directive consists of a <SAMP>‘%’</SAMP> followed by a digit. The same
directive cannot occur more than once in a format string.
</P>
-<H2><A NAME="SEC247" HREF="gettext_toc.html#TOC247">15.4 The Maintainer's View</A></H2>
+<H3><A NAME="SEC250" HREF="gettext_toc.html#TOC250">15.3.20 Boost Format Strings</A></H3>
+
+<P>
+Boost format strings are described in the documentation of the
+<CODE>boost::format</CODE> class, at
+<A HREF="http://www.boost.org/libs/format/doc/format.html">http://www.boost.org/libs/format/doc/format.html</A>.
+In summary, a directive has either the same syntax as in a C format string,
+such as <SAMP>‘%1$+5d’</SAMP>, or may be surrounded by vertical bars, such as
+<SAMP>‘%|1$+5d|’</SAMP> or <SAMP>‘%|1$+5|’</SAMP>, or consists of just an argument number
+between percent signs, such as <SAMP>‘%1%’</SAMP>.
+
+</P>
+
+
+<H2><A NAME="SEC251" HREF="gettext_toc.html#TOC251">15.4 The Maintainer's View</A></H2>
<P>
For the maintainer, the general procedure differs from the C language
<UL>
<LI>
-For those languages that don't use GNU gettext, the <TT>`intl/´</TT> directory
+For those languages that don't use GNU gettext, the <TT>‘intl/’</TT> directory
is not needed and can be omitted. This means that the maintainer calls the
-<CODE>gettextize</CODE> program without the <SAMP>`--intl´</SAMP> option, and that he
+<CODE>gettextize</CODE> program without the <SAMP>‘--intl’</SAMP> option, and that he
invokes the <CODE>AM_GNU_GETTEXT</CODE> autoconf macro via
-<SAMP>`AM_GNU_GETTEXT([external])´</SAMP>.
+<SAMP>‘AM_GNU_GETTEXT([external])’</SAMP>.
<LI>
If only a single programming language is used, the <CODE>XGETTEXT_OPTIONS</CODE>
-variable in <TT>`po/Makevars´</TT> (see section <A HREF="gettext_13.html#SEC201">13.4.3 <TT>`Makevars´</TT> in <TT>`po/´</TT></A>) should be adjusted to
+variable in <TT>‘po/Makevars’</TT> (see section <A HREF="gettext_13.html#SEC203">13.4.3 <TT>‘Makevars’</TT> in <TT>‘po/’</TT></A>) should be adjusted to
match the <CODE>xgettext</CODE> options for that particular programming language.
If the package uses more than one programming language with <CODE>gettext</CODE>
support, it becomes necessary to change the POT file construction rule
-in <TT>`po/Makefile.in.in´</TT>. It is recommended to make one <CODE>xgettext</CODE>
+in <TT>‘po/Makefile.in.in’</TT>. It is recommended to make one <CODE>xgettext</CODE>
invocation per programming language, each with the options appropriate for
that language, and to combine the resulting files using <CODE>msgcat</CODE>.
</UL>
-<H2><A NAME="SEC248" HREF="gettext_toc.html#TOC248">15.5 Individual Programming Languages</A></H2>
+<H2><A NAME="SEC252" HREF="gettext_toc.html#TOC252">15.5 Individual Programming Languages</A></H2>
-<H3><A NAME="SEC249" HREF="gettext_toc.html#TOC249">15.5.1 C, C++, Objective C</A></H3>
+<H3><A NAME="SEC253" HREF="gettext_toc.html#TOC253">15.5.1 C, C++, Objective C</A></H3>
<P>
-<A NAME="IDX1082"></A>
+<A NAME="IDX1108"></A>
</P>
<DL COMPACT>
<DD>
<CODE>fprintf "%2$d %1$d"</CODE>
<BR>In C++: <CODE>autosprintf "%2$d %1$d"</CODE>
-(see section `Introduction' in <CITE>GNU autosprintf</CITE>)
+(see section ‘Introduction’ in <CITE>GNU autosprintf</CITE>)
<DT>Portability
<DD>
</DL>
<P>
-The following examples are available in the <TT>`examples´</TT> directory:
+The following examples are available in the <TT>‘examples’</TT> directory:
<CODE>hello-c</CODE>, <CODE>hello-c-gnome</CODE>, <CODE>hello-c++</CODE>, <CODE>hello-c++-qt</CODE>,
-<CODE>hello-c++-kde</CODE>, <CODE>hello-c++-gnome</CODE>, <CODE>hello-objc</CODE>,
-<CODE>hello-objc-gnustep</CODE>, <CODE>hello-objc-gnome</CODE>.
+<CODE>hello-c++-kde</CODE>, <CODE>hello-c++-gnome</CODE>, <CODE>hello-c++-wxwidgets</CODE>,
+<CODE>hello-objc</CODE>, <CODE>hello-objc-gnustep</CODE>, <CODE>hello-objc-gnome</CODE>.
</P>
-<H3><A NAME="SEC250" HREF="gettext_toc.html#TOC250">15.5.2 sh - Shell Script</A></H3>
+<H3><A NAME="SEC254" HREF="gettext_toc.html#TOC254">15.5.2 sh - Shell Script</A></H3>
<P>
-<A NAME="IDX1083"></A>
+<A NAME="IDX1109"></A>
</P>
<DL COMPACT>
<DT>gettext/ngettext functions
<DD>
-<A NAME="IDX1084"></A>
-<A NAME="IDX1085"></A>
+<A NAME="IDX1110"></A>
+<A NAME="IDX1111"></A>
<CODE>gettext</CODE>, <CODE>ngettext</CODE> programs
<BR><CODE>eval_gettext</CODE>, <CODE>eval_ngettext</CODE> shell functions
<DT>textdomain
<DD>
-<A NAME="IDX1086"></A>
+<A NAME="IDX1112"></A>
environment variable <CODE>TEXTDOMAIN</CODE>
<DT>bindtextdomain
<DD>
-<A NAME="IDX1087"></A>
+<A NAME="IDX1113"></A>
environment variable <CODE>TEXTDOMAINDIR</CODE>
<DT>setlocale
</DL>
<P>
-An example is available in the <TT>`examples´</TT> directory: <CODE>hello-sh</CODE>.
+An example is available in the <TT>‘examples’</TT> directory: <CODE>hello-sh</CODE>.
</P>
-<H4><A NAME="SEC251" HREF="gettext_toc.html#TOC251">15.5.2.1 Preparing Shell Scripts for Internationalization</A></H4>
+<H4><A NAME="SEC255" HREF="gettext_toc.html#TOC255">15.5.2.1 Preparing Shell Scripts for Internationalization</A></H4>
<P>
-<A NAME="IDX1088"></A>
+<A NAME="IDX1114"></A>
</P>
<P>
near the top of the script. <CODE>gettext.sh</CODE> is a shell function library
that provides the functions
-<CODE>eval_gettext</CODE> (see section <A HREF="gettext_15.html#SEC256">15.5.2.6 Invoking the <CODE>eval_gettext</CODE> function</A>) and
-<CODE>eval_ngettext</CODE> (see section <A HREF="gettext_15.html#SEC257">15.5.2.7 Invoking the <CODE>eval_ngettext</CODE> function</A>).
+<CODE>eval_gettext</CODE> (see section <A HREF="gettext_15.html#SEC260">15.5.2.6 Invoking the <CODE>eval_gettext</CODE> function</A>) and
+<CODE>eval_ngettext</CODE> (see section <A HREF="gettext_15.html#SEC261">15.5.2.7 Invoking the <CODE>eval_ngettext</CODE> function</A>).
You have to ensure that <CODE>gettext.sh</CODE> can be found in the <CODE>PATH</CODE>.
<LI>
<LI>
-Prepare the strings for translation, as described in section <A HREF="gettext_4.html#SEC13">4.2 Preparing Translatable Strings</A>.
+Prepare the strings for translation, as described in section <A HREF="gettext_4.html#SEC14">4.3 Preparing Translatable Strings</A>.
<LI>
<LI>
-For each translatable string, change the output command <SAMP>`echo´</SAMP> or
-<SAMP>`$echo´</SAMP> to <SAMP>`gettext´</SAMP> (if the string contains no references to
-shell variables) or to <SAMP>`eval_gettext´</SAMP> (if it refers to shell variables),
-followed by a no-argument <SAMP>`echo´</SAMP> command (to account for the terminating
+For each translatable string, change the output command <SAMP>‘echo’</SAMP> or
+<SAMP>‘$echo’</SAMP> to <SAMP>‘gettext’</SAMP> (if the string contains no references to
+shell variables) or to <SAMP>‘eval_gettext’</SAMP> (if it refers to shell variables),
+followed by a no-argument <SAMP>‘echo’</SAMP> command (to account for the terminating
newline). Similarly, for cases with plural handling, replace a conditional
-<SAMP>`echo´</SAMP> command with an invocation of <SAMP>`ngettext´</SAMP> or
-<SAMP>`eval_ngettext´</SAMP>, followed by a no-argument <SAMP>`echo´</SAMP> command.
+<SAMP>‘echo’</SAMP> command with an invocation of <SAMP>‘ngettext’</SAMP> or
+<SAMP>‘eval_ngettext’</SAMP>, followed by a no-argument <SAMP>‘echo’</SAMP> command.
When doing this, you also need to add an extra backslash before the dollar
-sign in references to shell variables, so that the <SAMP>`eval_gettext´</SAMP>
+sign in references to shell variables, so that the <SAMP>‘eval_gettext’</SAMP>
function receives the translatable string before the variable values are
substituted into it. For example,
eval_gettext "Remaining files: \$filecount"; echo
</PRE>
-If the output command is not <SAMP>`echo´</SAMP>, you can make it use <SAMP>`echo´</SAMP>
+If the output command is not <SAMP>‘echo’</SAMP>, you can make it use <SAMP>‘echo’</SAMP>
nevertheless, through the use of backquotes. However, note that inside
backquotes, backslashes must be doubled to be effective (because the
backquoting eats one level of backslashes). For example, assuming that
-<SAMP>`error´</SAMP> is a shell function that signals an error,
+<SAMP>‘error’</SAMP> is a shell function that signals an error,
<PRE>
-<H4><A NAME="SEC252" HREF="gettext_toc.html#TOC252">15.5.2.2 Contents of <CODE>gettext.sh</CODE></A></H4>
+<H4><A NAME="SEC256" HREF="gettext_toc.html#TOC256">15.5.2.2 Contents of <CODE>gettext.sh</CODE></A></H4>
<P>
<CODE>gettext.sh</CODE>, contained in the run-time package of GNU gettext, provides
<LI>eval_gettext
-See section <A HREF="gettext_15.html#SEC256">15.5.2.6 Invoking the <CODE>eval_gettext</CODE> function</A>.
+See section <A HREF="gettext_15.html#SEC260">15.5.2.6 Invoking the <CODE>eval_gettext</CODE> function</A>.
<LI>eval_ngettext
-See section <A HREF="gettext_15.html#SEC257">15.5.2.7 Invoking the <CODE>eval_ngettext</CODE> function</A>.
+See section <A HREF="gettext_15.html#SEC261">15.5.2.7 Invoking the <CODE>eval_ngettext</CODE> function</A>.
</UL>
-<H4><A NAME="SEC253" HREF="gettext_toc.html#TOC253">15.5.2.3 Invoking the <CODE>gettext</CODE> program</A></H4>
+<H4><A NAME="SEC257" HREF="gettext_toc.html#TOC257">15.5.2.3 Invoking the <CODE>gettext</CODE> program</A></H4>
<P>
-<A NAME="IDX1089"></A>
-<A NAME="IDX1090"></A>
+<A NAME="IDX1115"></A>
+<A NAME="IDX1116"></A>
<PRE>
gettext [<VAR>option</VAR>] [[<VAR>textdomain</VAR>] <VAR>msgid</VAR>]
</PRE>
<P>
-<A NAME="IDX1091"></A>
+<A NAME="IDX1117"></A>
The <CODE>gettext</CODE> program displays the native language translation of a
textual message.
</P>
<DL COMPACT>
-<DT><SAMP>`-d <VAR>textdomain</VAR>´</SAMP>
+<DT><SAMP>‘-d <VAR>textdomain</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--domain=<VAR>textdomain</VAR>´</SAMP>
+<DT><SAMP>‘--domain=<VAR>textdomain</VAR>’</SAMP>
<DD>
-<A NAME="IDX1092"></A>
-<A NAME="IDX1093"></A>
+<A NAME="IDX1118"></A>
+<A NAME="IDX1119"></A>
Retrieve translated messages from <VAR>textdomain</VAR>. Usually a <VAR>textdomain</VAR>
corresponds to a package, a program, or a module of a program.
-<DT><SAMP>`-e´</SAMP>
+<DT><SAMP>‘-e’</SAMP>
<DD>
-<A NAME="IDX1094"></A>
+<A NAME="IDX1120"></A>
Enable expansion of some escape sequences. This option is for compatibility
-with the <SAMP>`echo´</SAMP> program or shell built-in. The escape sequences
-<SAMP>`\a´</SAMP>, <SAMP>`\b´</SAMP>, <SAMP>`\c´</SAMP>, <SAMP>`\f´</SAMP>, <SAMP>`\n´</SAMP>, <SAMP>`\r´</SAMP>, <SAMP>`\t´</SAMP>,
-<SAMP>`\v´</SAMP>, <SAMP>`\\´</SAMP>, and <SAMP>`\´</SAMP> followed by one to three octal digits, are
-interpreted like the SystemV <SAMP>`echo´</SAMP> program does.
+with the <SAMP>‘echo’</SAMP> program or shell built-in. The escape sequences
+<SAMP>‘\a’</SAMP>, <SAMP>‘\b’</SAMP>, <SAMP>‘\c’</SAMP>, <SAMP>‘\f’</SAMP>, <SAMP>‘\n’</SAMP>, <SAMP>‘\r’</SAMP>, <SAMP>‘\t’</SAMP>,
+<SAMP>‘\v’</SAMP>, <SAMP>‘\\’</SAMP>, and <SAMP>‘\’</SAMP> followed by one to three octal digits, are
+interpreted like the SystemV <SAMP>‘echo’</SAMP> program does.
-<DT><SAMP>`-E´</SAMP>
+<DT><SAMP>‘-E’</SAMP>
<DD>
-<A NAME="IDX1095"></A>
-This option is only for compatibility with the <SAMP>`echo´</SAMP> program or shell
+<A NAME="IDX1121"></A>
+This option is only for compatibility with the <SAMP>‘echo’</SAMP> program or shell
built-in. It has no effect.
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX1096"></A>
-<A NAME="IDX1097"></A>
+<A NAME="IDX1122"></A>
+<A NAME="IDX1123"></A>
Display this help and exit.
-<DT><SAMP>`-n´</SAMP>
+<DT><SAMP>‘-n’</SAMP>
<DD>
-<A NAME="IDX1098"></A>
+<A NAME="IDX1124"></A>
Suppress trailing newline. By default, <CODE>gettext</CODE> adds a newline to
the output.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX1099"></A>
-<A NAME="IDX1100"></A>
+<A NAME="IDX1125"></A>
+<A NAME="IDX1126"></A>
Output version information and exit.
-<DT><SAMP>`[<VAR>textdomain</VAR>] <VAR>msgid</VAR>´</SAMP>
+<DT><SAMP>‘[<VAR>textdomain</VAR>] <VAR>msgid</VAR>’</SAMP>
<DD>
Retrieve translated message corresponding to <VAR>msgid</VAR> from <VAR>textdomain</VAR>.
</P>
<P>
-When used with the <CODE>-s</CODE> option the program behaves like the <SAMP>`echo´</SAMP>
+When used with the <CODE>-s</CODE> option the program behaves like the <SAMP>‘echo’</SAMP>
command. But it does not simply copy its arguments to stdout. Instead those
messages found in the selected catalog are translated.
</P>
-<H4><A NAME="SEC254" HREF="gettext_toc.html#TOC254">15.5.2.4 Invoking the <CODE>ngettext</CODE> program</A></H4>
+<H4><A NAME="SEC258" HREF="gettext_toc.html#TOC258">15.5.2.4 Invoking the <CODE>ngettext</CODE> program</A></H4>
<P>
-<A NAME="IDX1101"></A>
-<A NAME="IDX1102"></A>
+<A NAME="IDX1127"></A>
+<A NAME="IDX1128"></A>
<PRE>
ngettext [<VAR>option</VAR>] [<VAR>textdomain</VAR>] <VAR>msgid</VAR> <VAR>msgid-plural</VAR> <VAR>count</VAR>
</PRE>
<P>
-<A NAME="IDX1103"></A>
+<A NAME="IDX1129"></A>
The <CODE>ngettext</CODE> program displays the native language translation of a
textual message whose grammatical form depends on a number.
</P>
<DL COMPACT>
-<DT><SAMP>`-d <VAR>textdomain</VAR>´</SAMP>
+<DT><SAMP>‘-d <VAR>textdomain</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--domain=<VAR>textdomain</VAR>´</SAMP>
+<DT><SAMP>‘--domain=<VAR>textdomain</VAR>’</SAMP>
<DD>
-<A NAME="IDX1104"></A>
-<A NAME="IDX1105"></A>
+<A NAME="IDX1130"></A>
+<A NAME="IDX1131"></A>
Retrieve translated messages from <VAR>textdomain</VAR>. Usually a <VAR>textdomain</VAR>
corresponds to a package, a program, or a module of a program.
-<DT><SAMP>`-e´</SAMP>
+<DT><SAMP>‘-e’</SAMP>
<DD>
-<A NAME="IDX1106"></A>
+<A NAME="IDX1132"></A>
Enable expansion of some escape sequences. This option is for compatibility
-with the <SAMP>`gettext´</SAMP> program. The escape sequences
-<SAMP>`\a´</SAMP>, <SAMP>`\b´</SAMP>, <SAMP>`\c´</SAMP>, <SAMP>`\f´</SAMP>, <SAMP>`\n´</SAMP>, <SAMP>`\r´</SAMP>, <SAMP>`\t´</SAMP>,
-<SAMP>`\v´</SAMP>, <SAMP>`\\´</SAMP>, and <SAMP>`\´</SAMP> followed by one to three octal digits, are
-interpreted like the SystemV <SAMP>`echo´</SAMP> program does.
+with the <SAMP>‘gettext’</SAMP> program. The escape sequences
+<SAMP>‘\a’</SAMP>, <SAMP>‘\b’</SAMP>, <SAMP>‘\c’</SAMP>, <SAMP>‘\f’</SAMP>, <SAMP>‘\n’</SAMP>, <SAMP>‘\r’</SAMP>, <SAMP>‘\t’</SAMP>,
+<SAMP>‘\v’</SAMP>, <SAMP>‘\\’</SAMP>, and <SAMP>‘\’</SAMP> followed by one to three octal digits, are
+interpreted like the SystemV <SAMP>‘echo’</SAMP> program does.
-<DT><SAMP>`-E´</SAMP>
+<DT><SAMP>‘-E’</SAMP>
<DD>
-<A NAME="IDX1107"></A>
-This option is only for compatibility with the <SAMP>`gettext´</SAMP> program. It has
+<A NAME="IDX1133"></A>
+This option is only for compatibility with the <SAMP>‘gettext’</SAMP> program. It has
no effect.
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX1108"></A>
-<A NAME="IDX1109"></A>
+<A NAME="IDX1134"></A>
+<A NAME="IDX1135"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX1110"></A>
-<A NAME="IDX1111"></A>
+<A NAME="IDX1136"></A>
+<A NAME="IDX1137"></A>
Output version information and exit.
-<DT><SAMP>`<VAR>textdomain</VAR>´</SAMP>
+<DT><SAMP>‘<VAR>textdomain</VAR>’</SAMP>
<DD>
Retrieve translated message from <VAR>textdomain</VAR>.
-<DT><SAMP>`<VAR>msgid</VAR> <VAR>msgid-plural</VAR>´</SAMP>
+<DT><SAMP>‘<VAR>msgid</VAR> <VAR>msgid-plural</VAR>’</SAMP>
<DD>
Translate <VAR>msgid</VAR> (English singular) / <VAR>msgid-plural</VAR> (English plural).
-<DT><SAMP>`<VAR>count</VAR>´</SAMP>
+<DT><SAMP>‘<VAR>count</VAR>’</SAMP>
<DD>
Choose singular/plural form based on this value.
</P>
-<H4><A NAME="SEC255" HREF="gettext_toc.html#TOC255">15.5.2.5 Invoking the <CODE>envsubst</CODE> program</A></H4>
+<H4><A NAME="SEC259" HREF="gettext_toc.html#TOC259">15.5.2.5 Invoking the <CODE>envsubst</CODE> program</A></H4>
<P>
-<A NAME="IDX1112"></A>
-<A NAME="IDX1113"></A>
+<A NAME="IDX1138"></A>
+<A NAME="IDX1139"></A>
<PRE>
envsubst [<VAR>option</VAR>] [<VAR>shell-format</VAR>]
</PRE>
<P>
-<A NAME="IDX1114"></A>
-<A NAME="IDX1115"></A>
-<A NAME="IDX1116"></A>
+<A NAME="IDX1140"></A>
+<A NAME="IDX1141"></A>
+<A NAME="IDX1142"></A>
The <CODE>envsubst</CODE> program substitutes the values of environment variables.
</P>
</P>
<DL COMPACT>
-<DT><SAMP>`-v´</SAMP>
+<DT><SAMP>‘-v’</SAMP>
<DD>
-<DT><SAMP>`--variables´</SAMP>
+<DT><SAMP>‘--variables’</SAMP>
<DD>
-<A NAME="IDX1117"></A>
-<A NAME="IDX1118"></A>
+<A NAME="IDX1143"></A>
+<A NAME="IDX1144"></A>
Output the variables occurring in <VAR>shell-format</VAR>.
</DL>
</P>
<DL COMPACT>
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX1119"></A>
-<A NAME="IDX1120"></A>
+<A NAME="IDX1145"></A>
+<A NAME="IDX1146"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX1121"></A>
-<A NAME="IDX1122"></A>
+<A NAME="IDX1147"></A>
+<A NAME="IDX1148"></A>
Output version information and exit.
</DL>
</P>
-<H4><A NAME="SEC256" HREF="gettext_toc.html#TOC256">15.5.2.6 Invoking the <CODE>eval_gettext</CODE> function</A></H4>
+<H4><A NAME="SEC260" HREF="gettext_toc.html#TOC260">15.5.2.6 Invoking the <CODE>eval_gettext</CODE> function</A></H4>
<P>
-<A NAME="IDX1123"></A>
+<A NAME="IDX1149"></A>
<PRE>
eval_gettext <VAR>msgid</VAR>
</PRE>
<P>
-<A NAME="IDX1124"></A>
+<A NAME="IDX1150"></A>
This function outputs the native language translation of a textual message,
performing dollar-substitution on the result. Note that only shell variables
mentioned in <VAR>msgid</VAR> will be dollar-substituted in the result.
</P>
-<H4><A NAME="SEC257" HREF="gettext_toc.html#TOC257">15.5.2.7 Invoking the <CODE>eval_ngettext</CODE> function</A></H4>
+<H4><A NAME="SEC261" HREF="gettext_toc.html#TOC261">15.5.2.7 Invoking the <CODE>eval_ngettext</CODE> function</A></H4>
<P>
-<A NAME="IDX1125"></A>
+<A NAME="IDX1151"></A>
<PRE>
eval_ngettext <VAR>msgid</VAR> <VAR>msgid-plural</VAR> <VAR>count</VAR>
</PRE>
<P>
-<A NAME="IDX1126"></A>
+<A NAME="IDX1152"></A>
This function outputs the native language translation of a textual message
whose grammatical form depends on a number, performing dollar-substitution
on the result. Note that only shell variables mentioned in <VAR>msgid</VAR> or
</P>
-<H3><A NAME="SEC258" HREF="gettext_toc.html#TOC258">15.5.3 bash - Bourne-Again Shell Script</A></H3>
+<H3><A NAME="SEC262" HREF="gettext_toc.html#TOC262">15.5.3 bash - Bourne-Again Shell Script</A></H3>
<P>
-<A NAME="IDX1127"></A>
+<A NAME="IDX1153"></A>
</P>
<P>
<P>
The security holes of <CODE>$"..."</CODE> come from the fact that after looking up
the translation of the string, <CODE>bash</CODE> processes it like it processes
-any double-quoted string: dollar and backquote processing, like <SAMP>`eval´</SAMP>
+any double-quoted string: dollar and backquote processing, like <SAMP>‘eval’</SAMP>
does.
</P>
</P>
-<H3><A NAME="SEC259" HREF="gettext_toc.html#TOC259">15.5.4 Python</A></H3>
+<H3><A NAME="SEC263" HREF="gettext_toc.html#TOC263">15.5.4 Python</A></H3>
<P>
-<A NAME="IDX1128"></A>
+<A NAME="IDX1154"></A>
</P>
<DL COMPACT>
<DD>
<CODE>'abc'</CODE>, <CODE>u'abc'</CODE>, <CODE>r'abc'</CODE>, <CODE>ur'abc'</CODE>,
<BR><CODE>"abc"</CODE>, <CODE>u"abc"</CODE>, <CODE>r"abc"</CODE>, <CODE>ur"abc"</CODE>,
-<BR><CODE>"'abc"'</CODE>, <CODE>u"'abc"'</CODE>, <CODE>r"'abc"'</CODE>, <CODE>ur"'abc"'</CODE>,
+<BR><CODE>”'abc”'</CODE>, <CODE>u”'abc”'</CODE>, <CODE>r”'abc”'</CODE>, <CODE>ur”'abc”'</CODE>,
<BR><CODE>"""abc"""</CODE>, <CODE>u"""abc"""</CODE>, <CODE>r"""abc"""</CODE>, <CODE>ur"""abc"""</CODE>
<DT>gettext shorthand
</DL>
<P>
-An example is available in the <TT>`examples´</TT> directory: <CODE>hello-python</CODE>.
+An example is available in the <TT>‘examples’</TT> directory: <CODE>hello-python</CODE>.
</P>
-<H3><A NAME="SEC260" HREF="gettext_toc.html#TOC260">15.5.5 GNU clisp - Common Lisp</A></H3>
+<H3><A NAME="SEC264" HREF="gettext_toc.html#TOC264">15.5.5 GNU clisp - Common Lisp</A></H3>
<P>
-<A NAME="IDX1129"></A>
-<A NAME="IDX1130"></A>
-<A NAME="IDX1131"></A>
+<A NAME="IDX1155"></A>
+<A NAME="IDX1156"></A>
+<A NAME="IDX1157"></A>
</P>
<DL COMPACT>
</DL>
<P>
-An example is available in the <TT>`examples´</TT> directory: <CODE>hello-clisp</CODE>.
+An example is available in the <TT>‘examples’</TT> directory: <CODE>hello-clisp</CODE>.
</P>
-<H3><A NAME="SEC261" HREF="gettext_toc.html#TOC261">15.5.6 GNU clisp C sources</A></H3>
+<H3><A NAME="SEC265" HREF="gettext_toc.html#TOC265">15.5.6 GNU clisp C sources</A></H3>
<P>
-<A NAME="IDX1132"></A>
+<A NAME="IDX1158"></A>
</P>
<DL COMPACT>
-<H3><A NAME="SEC262" HREF="gettext_toc.html#TOC262">15.5.7 Emacs Lisp</A></H3>
+<H3><A NAME="SEC266" HREF="gettext_toc.html#TOC266">15.5.7 Emacs Lisp</A></H3>
<P>
-<A NAME="IDX1133"></A>
+<A NAME="IDX1159"></A>
</P>
<DL COMPACT>
-<H3><A NAME="SEC263" HREF="gettext_toc.html#TOC263">15.5.8 librep</A></H3>
+<H3><A NAME="SEC267" HREF="gettext_toc.html#TOC267">15.5.8 librep</A></H3>
<P>
-<A NAME="IDX1134"></A>
+<A NAME="IDX1160"></A>
</P>
<DL COMPACT>
</DL>
<P>
-An example is available in the <TT>`examples´</TT> directory: <CODE>hello-librep</CODE>.
+An example is available in the <TT>‘examples’</TT> directory: <CODE>hello-librep</CODE>.
</P>
-<H3><A NAME="SEC264" HREF="gettext_toc.html#TOC264">15.5.9 GNU guile - Scheme</A></H3>
+<H3><A NAME="SEC268" HREF="gettext_toc.html#TOC268">15.5.9 GNU guile - Scheme</A></H3>
<P>
-<A NAME="IDX1135"></A>
-<A NAME="IDX1136"></A>
+<A NAME="IDX1161"></A>
+<A NAME="IDX1162"></A>
</P>
<DL COMPACT>
</DL>
<P>
-An example is available in the <TT>`examples´</TT> directory: <CODE>hello-guile</CODE>.
+An example is available in the <TT>‘examples’</TT> directory: <CODE>hello-guile</CODE>.
</P>
-<H3><A NAME="SEC265" HREF="gettext_toc.html#TOC265">15.5.10 GNU Smalltalk</A></H3>
+<H3><A NAME="SEC269" HREF="gettext_toc.html#TOC269">15.5.10 GNU Smalltalk</A></H3>
<P>
-<A NAME="IDX1137"></A>
+<A NAME="IDX1163"></A>
</P>
<DL COMPACT>
</DL>
<P>
-An example is available in the <TT>`examples´</TT> directory:
+An example is available in the <TT>‘examples’</TT> directory:
<CODE>hello-smalltalk</CODE>.
</P>
-<H3><A NAME="SEC266" HREF="gettext_toc.html#TOC266">15.5.11 Java</A></H3>
+<H3><A NAME="SEC270" HREF="gettext_toc.html#TOC270">15.5.11 Java</A></H3>
<P>
-<A NAME="IDX1138"></A>
+<A NAME="IDX1164"></A>
</P>
<DL COMPACT>
This has the advantage of having the <CODE>ngettext</CODE> function for plural
handling.
-<A NAME="IDX1139"></A>
+<A NAME="IDX1165"></A>
To use this API, one needs the <CODE>libintl.jar</CODE> file which is part of
the GNU gettext package and distributed under the LGPL.
</OL>
<P>
-Three examples, using the second API, are available in the <TT>`examples´</TT>
+Three examples, using the second API, are available in the <TT>‘examples’</TT>
directory: <CODE>hello-java</CODE>, <CODE>hello-java-awt</CODE>, <CODE>hello-java-swing</CODE>.
</P>
<P>
-Now, to make use of the API and define a shorthand for <SAMP>`getString´</SAMP>,
-there are two idioms that you can choose from:
+Now, to make use of the API and define a shorthand for <SAMP>‘getString’</SAMP>,
+there are three idioms that you can choose from:
</P>
<UL>
<LI>
-In a unique class of your project, say <SAMP>`Util´</SAMP>, define a static variable
+(This one assumes Java 1.5 or newer.)
+In a unique class of your project, say <SAMP>‘Util’</SAMP>, define a static variable
+holding the <CODE>ResourceBundle</CODE> instance and the shorthand:
+
+
+<PRE>
+private static ResourceBundle myResources =
+ ResourceBundle.getBundle("domain-name");
+public static String _(String s) {
+ return myResources.getString(s);
+}
+</PRE>
+
+All classes containing internationalized strings then contain
+
+
+<PRE>
+import static Util._;
+</PRE>
+
+and the shorthand is used like this:
+
+
+<PRE>
+System.out.println(_("Operation completed."));
+</PRE>
+
+<LI>
+
+In a unique class of your project, say <SAMP>‘Util’</SAMP>, define a static variable
holding the <CODE>ResourceBundle</CODE> instance:
<LI>
-You add a class with a very short name, say <SAMP>`S´</SAMP>, containing just the
+You add a class with a very short name, say <SAMP>‘S’</SAMP>, containing just the
definition of the resource bundle and of the shorthand:
</UL>
<P>
-Which of the two idioms you choose, will depend on whether copying two lines
-of codes into every class is more acceptable in your project than a class
-with a single-letter name.
+Which of the three idioms you choose, will depend on whether your project
+requires portability to Java versions prior to Java 1.5 and, if so, whether
+copying two lines of codes into every class is more acceptable in your project
+than a class with a single-letter name.
</P>
-<H3><A NAME="SEC267" HREF="gettext_toc.html#TOC267">15.5.12 C#</A></H3>
+<H3><A NAME="SEC271" HREF="gettext_toc.html#TOC271">15.5.12 C#</A></H3>
<P>
-<A NAME="IDX1140"></A>
+<A NAME="IDX1166"></A>
</P>
<DL COMPACT>
</P>
<P>
To convert a PO file to a <CODE>.resources</CODE> file, the <CODE>msgfmt</CODE> program
-can be used with the option <SAMP>`--csharp-resources´</SAMP>. To convert a
+can be used with the option <SAMP>‘--csharp-resources’</SAMP>. To convert a
<CODE>.resources</CODE> file back to a PO file, the <CODE>msgunfmt</CODE> program can be
-used with the option <SAMP>`--csharp-resources´</SAMP>. You can also, in some cases,
+used with the option <SAMP>‘--csharp-resources’</SAMP>. You can also, in some cases,
use the <CODE>resgen</CODE> program (from the <CODE>pnet</CODE> package) or the
<CODE>monoresgen</CODE> program (from the <CODE>mono</CODE>/<CODE>mcs</CODE> package). These
programs can also convert a <CODE>.resources</CODE> file back to a PO file. But
The <CODE>GetPluralString</CODE> function returns a string translation with plural
handling, like the <CODE>ngettext</CODE> function in C.
-<A NAME="IDX1141"></A>
+<A NAME="IDX1167"></A>
To use this API, one needs the <CODE>GNU.Gettext.dll</CODE> file which is part of
the GNU gettext package and distributed under the LGPL.
</OL>
</P>
<P>
-Two examples, using the second API, are available in the <TT>`examples´</TT>
+Two examples, using the second API, are available in the <TT>‘examples’</TT>
directory: <CODE>hello-csharp</CODE>, <CODE>hello-csharp-forms</CODE>.
</P>
<P>
-Now, to make use of the API and define a shorthand for <SAMP>`GetString´</SAMP>,
+Now, to make use of the API and define a shorthand for <SAMP>‘GetString’</SAMP>,
there are two idioms that you can choose from:
</P>
<UL>
<LI>
-In a unique class of your project, say <SAMP>`Util´</SAMP>, define a static variable
+In a unique class of your project, say <SAMP>‘Util’</SAMP>, define a static variable
holding the <CODE>ResourceManager</CODE> instance:
<LI>
-You add a class with a very short name, say <SAMP>`S´</SAMP>, containing just the
+You add a class with a very short name, say <SAMP>‘S’</SAMP>, containing just the
definition of the resource manager and of the shorthand:
</P>
-<H3><A NAME="SEC268" HREF="gettext_toc.html#TOC268">15.5.13 GNU awk</A></H3>
+<H3><A NAME="SEC272" HREF="gettext_toc.html#TOC272">15.5.13 GNU awk</A></H3>
<P>
-<A NAME="IDX1142"></A>
-<A NAME="IDX1143"></A>
+<A NAME="IDX1168"></A>
+<A NAME="IDX1169"></A>
</P>
<DL COMPACT>
</DL>
<P>
-An example is available in the <TT>`examples´</TT> directory: <CODE>hello-gawk</CODE>.
+An example is available in the <TT>‘examples’</TT> directory: <CODE>hello-gawk</CODE>.
</P>
-<H3><A NAME="SEC269" HREF="gettext_toc.html#TOC269">15.5.14 Pascal - Free Pascal Compiler</A></H3>
+<H3><A NAME="SEC273" HREF="gettext_toc.html#TOC273">15.5.14 Pascal - Free Pascal Compiler</A></H3>
<P>
-<A NAME="IDX1144"></A>
-<A NAME="IDX1145"></A>
-<A NAME="IDX1146"></A>
+<A NAME="IDX1170"></A>
+<A NAME="IDX1171"></A>
+<A NAME="IDX1172"></A>
</P>
<DL COMPACT>
</P>
<P>
-An example is available in the <TT>`examples´</TT> directory: <CODE>hello-pascal</CODE>.
+An example is available in the <TT>‘examples’</TT> directory: <CODE>hello-pascal</CODE>.
</P>
-<H3><A NAME="SEC270" HREF="gettext_toc.html#TOC270">15.5.15 wxWindows library</A></H3>
+<H3><A NAME="SEC274" HREF="gettext_toc.html#TOC274">15.5.15 wxWidgets library</A></H3>
<P>
-<A NAME="IDX1147"></A>
+<A NAME="IDX1173"></A>
</P>
<DL COMPACT>
<DT>Formatting with positions
<DD>
----
+wxString::Format supports positions if and only if the system has
+<CODE>wprintf()</CODE>, <CODE>vswprintf()</CODE> functions and they support positions
+according to POSIX.
<DT>Portability
<DD>
-<H3><A NAME="SEC271" HREF="gettext_toc.html#TOC271">15.5.16 YCP - YaST2 scripting language</A></H3>
+<H3><A NAME="SEC275" HREF="gettext_toc.html#TOC275">15.5.16 YCP - YaST2 scripting language</A></H3>
<P>
-<A NAME="IDX1148"></A>
-<A NAME="IDX1149"></A>
+<A NAME="IDX1174"></A>
+<A NAME="IDX1175"></A>
</P>
<DL COMPACT>
</DL>
<P>
-An example is available in the <TT>`examples´</TT> directory: <CODE>hello-ycp</CODE>.
+An example is available in the <TT>‘examples’</TT> directory: <CODE>hello-ycp</CODE>.
</P>
-<H3><A NAME="SEC272" HREF="gettext_toc.html#TOC272">15.5.17 Tcl - Tk's scripting language</A></H3>
+<H3><A NAME="SEC276" HREF="gettext_toc.html#TOC276">15.5.17 Tcl - Tk's scripting language</A></H3>
<P>
-<A NAME="IDX1150"></A>
-<A NAME="IDX1151"></A>
+<A NAME="IDX1176"></A>
+<A NAME="IDX1177"></A>
</P>
<DL COMPACT>
</DL>
<P>
-Two examples are available in the <TT>`examples´</TT> directory:
+Two examples are available in the <TT>‘examples’</TT> directory:
<CODE>hello-tcl</CODE>, <CODE>hello-tcl-tk</CODE>.
</P>
</P>
-<H3><A NAME="SEC273" HREF="gettext_toc.html#TOC273">15.5.18 Perl</A></H3>
+<H3><A NAME="SEC277" HREF="gettext_toc.html#TOC277">15.5.18 Perl</A></H3>
<P>
-<A NAME="IDX1152"></A>
+<A NAME="IDX1178"></A>
</P>
<DL COMPACT>
<LI><CODE>$tied_hash_reference->{"message"}</CODE>
-<LI>etc., issue the command <SAMP>`man perlsyn´</SAMP> for details
+<LI>etc., issue the command <SAMP>‘man perlsyn’</SAMP> for details
</UL>
</DL>
<P>
-An example is available in the <TT>`examples´</TT> directory: <CODE>hello-perl</CODE>.
+An example is available in the <TT>‘examples’</TT> directory: <CODE>hello-perl</CODE>.
</P>
<P>
-<A NAME="IDX1153"></A>
+<A NAME="IDX1179"></A>
</P>
<P>
-<H4><A NAME="SEC274" HREF="gettext_toc.html#TOC274">15.5.18.1 General Problems Parsing Perl Code</A></H4>
+<H4><A NAME="SEC278" HREF="gettext_toc.html#TOC278">15.5.18.1 General Problems Parsing Perl Code</A></H4>
<P>
It is often heard that only Perl can parse Perl. This is not true.
<P>
In this case, the string <CODE>gettext</CODE> will be interpreted as a file
-handle again, and the above example will create a file <TT>`testfile´</TT>
-and write the string "Hello world!" into it. Even advanced
+handle again, and the above example will create a file <TT>‘testfile’</TT>
+and write the string “Hello world!” into it. Even advanced
control flow analysis will not really help:
</P>
</P>
-<H4><A NAME="SEC275" HREF="gettext_toc.html#TOC275">15.5.18.2 Which keywords will xgettext look for?</A></H4>
+<H4><A NAME="SEC279" HREF="gettext_toc.html#TOC279">15.5.18.2 Which keywords will xgettext look for?</A></H4>
<P>
-<A NAME="IDX1154"></A>
+<A NAME="IDX1180"></A>
</P>
<P>
-<H4><A NAME="SEC276" HREF="gettext_toc.html#TOC276">15.5.18.3 How to Extract Hash Keys</A></H4>
+<H4><A NAME="SEC280" HREF="gettext_toc.html#TOC280">15.5.18.3 How to Extract Hash Keys</A></H4>
<P>
-<A NAME="IDX1155"></A>
+<A NAME="IDX1181"></A>
</P>
<P>
Translating messages at runtime is normally performed by looking up the
original string in the translation database and returning the
-translated version. The "natural" Perl implementation is a hash
+translated version. The “natural” Perl implementation is a hash
lookup, and, of course, <CODE>xgettext</CODE> supports such practice.
</P>
</P>
-<H4><A NAME="SEC277" HREF="gettext_toc.html#TOC277">15.5.18.4 What are Strings And Quote-like Expressions?</A></H4>
+<H4><A NAME="SEC281" HREF="gettext_toc.html#TOC281">15.5.18.4 What are Strings And Quote-like Expressions?</A></H4>
<P>
-<A NAME="IDX1156"></A>
+<A NAME="IDX1182"></A>
</P>
<P>
-<H4><A NAME="SEC278" HREF="gettext_toc.html#TOC278">15.5.18.5 Invalid Uses Of String Interpolation</A></H4>
+<H4><A NAME="SEC282" HREF="gettext_toc.html#TOC282">15.5.18.5 Invalid Uses Of String Interpolation</A></H4>
<P>
-<A NAME="IDX1157"></A>
+<A NAME="IDX1183"></A>
</P>
<P>
</P>
<P>
-Please see the manual page <SAMP>`man perlop´</SAMP> for details of strings and
+Please see the manual page <SAMP>‘man perlop’</SAMP> for details of strings and
quote-like expressions that are subject to interpolation and those
that are not. Safe interpolations (that will not lead to a fatal
error) are:
</P>
-<H4><A NAME="SEC279" HREF="gettext_toc.html#TOC279">15.5.18.6 Valid Uses Of String Interpolation</A></H4>
+<H4><A NAME="SEC283" HREF="gettext_toc.html#TOC283">15.5.18.6 Valid Uses Of String Interpolation</A></H4>
<P>
-<A NAME="IDX1158"></A>
+<A NAME="IDX1184"></A>
</P>
<P>
<P>
You can interpolate hash lookups in all strings or quote-like
expressions that are subject to interpolation (see the manual page
-<SAMP>`man perlop´</SAMP> for details). Double interpolation is invalid, however:
+<SAMP>‘man perlop’</SAMP> for details). Double interpolation is invalid, however:
</P>
The <CODE>qq</CODE>-quoted string is recognized as an argument to <CODE>xgettext</CODE> in
the first place, and checked for invalid variable interpolation. The
dollar sign of hash-dereferencing will therefore terminate the parser
-with an "invalid interpolation" error.
+with an “invalid interpolation” error.
</P>
<P>
-<H4><A NAME="SEC280" HREF="gettext_toc.html#TOC280">15.5.18.7 When To Use Parentheses</A></H4>
+<H4><A NAME="SEC284" HREF="gettext_toc.html#TOC284">15.5.18.7 When To Use Parentheses</A></H4>
<P>
-<A NAME="IDX1159"></A>
+<A NAME="IDX1185"></A>
</P>
<P>
-<H4><A NAME="SEC281" HREF="gettext_toc.html#TOC281">15.5.18.8 How To Grok with Long Lines</A></H4>
+<H4><A NAME="SEC285" HREF="gettext_toc.html#TOC285">15.5.18.8 How To Grok with Long Lines</A></H4>
<P>
-<A NAME="IDX1160"></A>
+<A NAME="IDX1186"></A>
</P>
<P>
</P>
<P>
Note that the future Perl 6 will probably use the underscore
-(<SAMP>`_´</SAMP>) as the string concatenation operator, and the dot
-(<SAMP>`.´</SAMP>) for dereferencing. This new syntax is not yet supported by
+(<SAMP>‘_’</SAMP>) as the string concatenation operator, and the dot
+(<SAMP>‘.’</SAMP>) for dereferencing. This new syntax is not yet supported by
<CODE>xgettext</CODE>.
</P>
</P>
-<H4><A NAME="SEC282" HREF="gettext_toc.html#TOC282">15.5.18.9 Bugs, Pitfalls, And Things That Do Not Work</A></H4>
+<H4><A NAME="SEC286" HREF="gettext_toc.html#TOC286">15.5.18.9 Bugs, Pitfalls, And Things That Do Not Work</A></H4>
<P>
-<A NAME="IDX1161"></A>
+<A NAME="IDX1187"></A>
</P>
<P>
The modifier <CODE>e</CODE> will cause the substitution to be interpreted as
an evaluable statement. Consequently, at runtime the function
<CODE>gettext()</CODE> is called, but again, the parser fails to extract the
-string "Sunday". Use a temporary variable as a simple workaround if
+string “Sunday”. Use a temporary variable as a simple workaround if
you really happen to need this feature:
</P>
</PRE>
<P>
-Whereas <SAMP>`{program}´</SAMP> is a placeholder, <SAMP>`{OPTIONS}´</SAMP>
+Whereas <SAMP>‘{program}’</SAMP> is a placeholder, <SAMP>‘{OPTIONS}’</SAMP>
is not and should probably be translated. Yet, there is no way to teach
the Perl parser in <CODE>xgettext</CODE> to recognize the first one, and leave
the other one alone.
</P>
-<H3><A NAME="SEC283" HREF="gettext_toc.html#TOC283">15.5.19 PHP Hypertext Preprocessor</A></H3>
+<H3><A NAME="SEC287" HREF="gettext_toc.html#TOC287">15.5.19 PHP Hypertext Preprocessor</A></H3>
<P>
-<A NAME="IDX1162"></A>
+<A NAME="IDX1188"></A>
</P>
<DL COMPACT>
</DL>
<P>
-An example is available in the <TT>`examples´</TT> directory: <CODE>hello-php</CODE>.
+An example is available in the <TT>‘examples’</TT> directory: <CODE>hello-php</CODE>.
</P>
-<H3><A NAME="SEC284" HREF="gettext_toc.html#TOC284">15.5.20 Pike</A></H3>
+<H3><A NAME="SEC288" HREF="gettext_toc.html#TOC288">15.5.20 Pike</A></H3>
<P>
-<A NAME="IDX1163"></A>
+<A NAME="IDX1189"></A>
</P>
<DL COMPACT>
-<H3><A NAME="SEC285" HREF="gettext_toc.html#TOC285">15.5.21 GNU Compiler Collection sources</A></H3>
+<H3><A NAME="SEC289" HREF="gettext_toc.html#TOC289">15.5.21 GNU Compiler Collection sources</A></H3>
<P>
-<A NAME="IDX1164"></A>
+<A NAME="IDX1190"></A>
</P>
<DL COMPACT>
-<H2><A NAME="SEC286" HREF="gettext_toc.html#TOC286">15.6 Internationalizable Data</A></H2>
+<H2><A NAME="SEC290" HREF="gettext_toc.html#TOC290">15.6 Internationalizable Data</A></H2>
<P>
Here is a list of other data formats which can be internationalized
-<H3><A NAME="SEC287" HREF="gettext_toc.html#TOC287">15.6.1 POT - Portable Object Template</A></H3>
+<H3><A NAME="SEC291" HREF="gettext_toc.html#TOC291">15.6.1 POT - Portable Object Template</A></H3>
<DL COMPACT>
-<H3><A NAME="SEC288" HREF="gettext_toc.html#TOC288">15.6.2 Resource String Table</A></H3>
+<H3><A NAME="SEC292" HREF="gettext_toc.html#TOC292">15.6.2 Resource String Table</A></H3>
<P>
-<A NAME="IDX1165"></A>
+<A NAME="IDX1191"></A>
</P>
<DL COMPACT>
-<H3><A NAME="SEC289" HREF="gettext_toc.html#TOC289">15.6.3 Glade - GNOME user interface description</A></H3>
+<H3><A NAME="SEC293" HREF="gettext_toc.html#TOC293">15.6.3 Glade - GNOME user interface description</A></H3>
<DL COMPACT>
</DL>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_14.html">previous</A>, <A HREF="gettext_16.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_14.html">previous</A>, <A HREF="gettext_16.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 16 Concluding Remarks</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_15.html">previous</A>, <A HREF="gettext_17.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_15.html">previous</A>, <A HREF="gettext_17.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC290" HREF="gettext_toc.html#TOC290">16 Concluding Remarks</A></H1>
+<H1><A NAME="SEC294" HREF="gettext_toc.html#TOC294">16 Concluding Remarks</A></H1>
<P>
We would like to conclude this GNU <CODE>gettext</CODE> manual by presenting
-<H2><A NAME="SEC291" HREF="gettext_toc.html#TOC291">16.1 History of GNU <CODE>gettext</CODE></A></H2>
+<H2><A NAME="SEC295" HREF="gettext_toc.html#TOC295">16.1 History of GNU <CODE>gettext</CODE></A></H2>
<P>
-<A NAME="IDX1166"></A>
+<A NAME="IDX1192"></A>
</P>
<P>
</P>
-<H2><A NAME="SEC292" HREF="gettext_toc.html#TOC292">16.2 Related Readings</A></H2>
+<H2><A NAME="SEC296" HREF="gettext_toc.html#TOC296">16.2 Related Readings</A></H2>
<P>
-<A NAME="IDX1167"></A>
-<A NAME="IDX1168"></A>
+<A NAME="IDX1193"></A>
+<A NAME="IDX1194"></A>
</P>
<P>
-Eugene H. Dorr (<TT>`dorre@well.com´</TT>) maintains an interesting
+<STRONG> NOTE: </STRONG> This documentation section is outdated and needs to be
+revised.
+
+</P>
+<P>
+Eugene H. Dorr (<TT>‘dorre@well.com’</TT>) maintains an interesting
bibliography on internationalization matters, called
<CITE>Internationalization Reference List</CITE>, which is available as:
</PRE>
<P>
-Michael Gschwind (<TT>`mike@vlsivie.tuwien.ac.at´</TT>) maintains a
+Michael Gschwind (<TT>‘mike@vlsivie.tuwien.ac.at’</TT>) maintains a
Frequently Asked Questions (FAQ) list, entitled <CITE>Programming for
Internationalisation</CITE>. This FAQ discusses writing programs which
can handle different language conventions, character sets, etc.;
and is applicable to all character set encodings, with particular
emphasis on ISO 8859-1. It is regularly published in Usenet
-groups <TT>`comp.unix.questions´</TT>, <TT>`comp.std.internat´</TT>,
-<TT>`comp.software.international´</TT>, <TT>`comp.lang.c´</TT>,
-<TT>`comp.windows.x´</TT>, <TT>`comp.std.c´</TT>, <TT>`comp.answers´</TT>
-and <TT>`news.answers´</TT>. The home location of this document is:
+groups <TT>‘comp.unix.questions’</TT>, <TT>‘comp.std.internat’</TT>,
+<TT>‘comp.software.international’</TT>, <TT>‘comp.lang.c’</TT>,
+<TT>‘comp.windows.x’</TT>, <TT>‘comp.std.c’</TT>, <TT>‘comp.answers’</TT>
+and <TT>‘news.answers’</TT>. The home location of this document is:
<PRE>
ftp://ftp.vlsivie.tuwien.ac.at/pub/8bit/ISO-programming
</PRE>
<P>
-Patrick D'Cruze (<TT>`pdcruze@li.org´</TT>) wrote a tutorial about NLS
-matters, and Jochen Hein (<TT>`Hein@student.tu-clausthal.de´</TT>) took
+Patrick D'Cruze (<TT>‘pdcruze@li.org’</TT>) wrote a tutorial about NLS
+matters, and Jochen Hein (<TT>‘Hein@student.tu-clausthal.de’</TT>) took
over the responsibility of maintaining it. It may be found as:
<PRE>
</P>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_15.html">previous</A>, <A HREF="gettext_17.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_15.html">previous</A>, <A HREF="gettext_17.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - A Language Codes</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_16.html">previous</A>, <A HREF="gettext_18.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_16.html">previous</A>, <A HREF="gettext_18.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC293" HREF="gettext_toc.html#TOC293">A Language Codes</A></H1>
+<H1><A NAME="SEC297" HREF="gettext_toc.html#TOC297">A Language Codes</A></H1>
<P>
-<A NAME="IDX1169"></A>
-<A NAME="IDX1170"></A>
+<A NAME="IDX1195"></A>
+<A NAME="IDX1196"></A>
</P>
<P>
</P>
<DL COMPACT>
-<DT><SAMP>`aa´</SAMP>
+<DT><SAMP>‘aa’</SAMP>
<DD>
Afar.
-<DT><SAMP>`ab´</SAMP>
+<DT><SAMP>‘ab’</SAMP>
<DD>
Abkhazian.
-<DT><SAMP>`ae´</SAMP>
+<DT><SAMP>‘ae’</SAMP>
<DD>
Avestan.
-<DT><SAMP>`af´</SAMP>
+<DT><SAMP>‘af’</SAMP>
<DD>
Afrikaans.
-<DT><SAMP>`ak´</SAMP>
+<DT><SAMP>‘ak’</SAMP>
<DD>
Akan.
-<DT><SAMP>`am´</SAMP>
+<DT><SAMP>‘am’</SAMP>
<DD>
Amharic.
-<DT><SAMP>`an´</SAMP>
+<DT><SAMP>‘an’</SAMP>
<DD>
Aragonese.
-<DT><SAMP>`ar´</SAMP>
+<DT><SAMP>‘ar’</SAMP>
<DD>
Arabic.
-<DT><SAMP>`as´</SAMP>
+<DT><SAMP>‘as’</SAMP>
<DD>
Assamese.
-<DT><SAMP>`av´</SAMP>
+<DT><SAMP>‘av’</SAMP>
<DD>
Avaric.
-<DT><SAMP>`ay´</SAMP>
+<DT><SAMP>‘ay’</SAMP>
<DD>
Aymara.
-<DT><SAMP>`az´</SAMP>
+<DT><SAMP>‘az’</SAMP>
<DD>
Azerbaijani.
-<DT><SAMP>`ba´</SAMP>
+<DT><SAMP>‘ba’</SAMP>
<DD>
Bashkir.
-<DT><SAMP>`be´</SAMP>
+<DT><SAMP>‘be’</SAMP>
<DD>
Byelorussian; Belarusian.
-<DT><SAMP>`bg´</SAMP>
+<DT><SAMP>‘bg’</SAMP>
<DD>
Bulgarian.
-<DT><SAMP>`bh´</SAMP>
+<DT><SAMP>‘bh’</SAMP>
<DD>
Bihari.
-<DT><SAMP>`bi´</SAMP>
+<DT><SAMP>‘bi’</SAMP>
<DD>
Bislama.
-<DT><SAMP>`bm´</SAMP>
+<DT><SAMP>‘bm’</SAMP>
<DD>
Bambara.
-<DT><SAMP>`bn´</SAMP>
+<DT><SAMP>‘bn’</SAMP>
<DD>
Bengali; Bangla.
-<DT><SAMP>`bo´</SAMP>
+<DT><SAMP>‘bo’</SAMP>
<DD>
Tibetan.
-<DT><SAMP>`br´</SAMP>
+<DT><SAMP>‘br’</SAMP>
<DD>
Breton.
-<DT><SAMP>`bs´</SAMP>
+<DT><SAMP>‘bs’</SAMP>
<DD>
Bosnian.
-<DT><SAMP>`ca´</SAMP>
+<DT><SAMP>‘ca’</SAMP>
<DD>
Catalan.
-<DT><SAMP>`ce´</SAMP>
+<DT><SAMP>‘ce’</SAMP>
<DD>
Chechen.
-<DT><SAMP>`ch´</SAMP>
+<DT><SAMP>‘ch’</SAMP>
<DD>
Chamorro.
-<DT><SAMP>`co´</SAMP>
+<DT><SAMP>‘co’</SAMP>
<DD>
Corsican.
-<DT><SAMP>`cr´</SAMP>
+<DT><SAMP>‘cr’</SAMP>
<DD>
Cree.
-<DT><SAMP>`cs´</SAMP>
+<DT><SAMP>‘cs’</SAMP>
<DD>
Czech.
-<DT><SAMP>`cu´</SAMP>
+<DT><SAMP>‘cu’</SAMP>
<DD>
Church Slavic.
-<DT><SAMP>`cv´</SAMP>
+<DT><SAMP>‘cv’</SAMP>
<DD>
Chuvash.
-<DT><SAMP>`cy´</SAMP>
+<DT><SAMP>‘cy’</SAMP>
<DD>
Welsh.
-<DT><SAMP>`da´</SAMP>
+<DT><SAMP>‘da’</SAMP>
<DD>
Danish.
-<DT><SAMP>`de´</SAMP>
+<DT><SAMP>‘de’</SAMP>
<DD>
German.
-<DT><SAMP>`dv´</SAMP>
+<DT><SAMP>‘dv’</SAMP>
<DD>
Divehi.
-<DT><SAMP>`dz´</SAMP>
+<DT><SAMP>‘dz’</SAMP>
<DD>
Dzongkha; Bhutani.
-<DT><SAMP>`ee´</SAMP>
+<DT><SAMP>‘ee’</SAMP>
<DD>
'Ew'e.
-<DT><SAMP>`el´</SAMP>
+<DT><SAMP>‘el’</SAMP>
<DD>
Greek.
-<DT><SAMP>`en´</SAMP>
+<DT><SAMP>‘en’</SAMP>
<DD>
English.
-<DT><SAMP>`eo´</SAMP>
+<DT><SAMP>‘eo’</SAMP>
<DD>
Esperanto.
-<DT><SAMP>`es´</SAMP>
+<DT><SAMP>‘es’</SAMP>
<DD>
Spanish.
-<DT><SAMP>`et´</SAMP>
+<DT><SAMP>‘et’</SAMP>
<DD>
Estonian.
-<DT><SAMP>`eu´</SAMP>
+<DT><SAMP>‘eu’</SAMP>
<DD>
Basque.
-<DT><SAMP>`fa´</SAMP>
+<DT><SAMP>‘fa’</SAMP>
<DD>
Persian.
-<DT><SAMP>`ff´</SAMP>
+<DT><SAMP>‘ff’</SAMP>
<DD>
Fulah.
-<DT><SAMP>`fi´</SAMP>
+<DT><SAMP>‘fi’</SAMP>
<DD>
Finnish.
-<DT><SAMP>`fj´</SAMP>
+<DT><SAMP>‘fj’</SAMP>
<DD>
Fijian; Fiji.
-<DT><SAMP>`fo´</SAMP>
+<DT><SAMP>‘fo’</SAMP>
<DD>
Faroese.
-<DT><SAMP>`fr´</SAMP>
+<DT><SAMP>‘fr’</SAMP>
<DD>
French.
-<DT><SAMP>`fy´</SAMP>
+<DT><SAMP>‘fy’</SAMP>
<DD>
Frisian.
-<DT><SAMP>`ga´</SAMP>
+<DT><SAMP>‘ga’</SAMP>
<DD>
Irish.
-<DT><SAMP>`gd´</SAMP>
+<DT><SAMP>‘gd’</SAMP>
<DD>
Scots; Gaelic.
-<DT><SAMP>`gl´</SAMP>
+<DT><SAMP>‘gl’</SAMP>
<DD>
Gallegan; Galician.
-<DT><SAMP>`gn´</SAMP>
+<DT><SAMP>‘gn’</SAMP>
<DD>
Guarani.
-<DT><SAMP>`gu´</SAMP>
+<DT><SAMP>‘gu’</SAMP>
<DD>
Gujarati.
-<DT><SAMP>`gv´</SAMP>
+<DT><SAMP>‘gv’</SAMP>
<DD>
Manx.
-<DT><SAMP>`ha´</SAMP>
+<DT><SAMP>‘ha’</SAMP>
<DD>
Hausa (?).
-<DT><SAMP>`he´</SAMP>
+<DT><SAMP>‘he’</SAMP>
<DD>
Hebrew (formerly iw).
-<DT><SAMP>`hi´</SAMP>
+<DT><SAMP>‘hi’</SAMP>
<DD>
Hindi.
-<DT><SAMP>`ho´</SAMP>
+<DT><SAMP>‘ho’</SAMP>
<DD>
Hiri Motu.
-<DT><SAMP>`hr´</SAMP>
+<DT><SAMP>‘hr’</SAMP>
<DD>
Croatian.
-<DT><SAMP>`ht´</SAMP>
+<DT><SAMP>‘ht’</SAMP>
<DD>
Haitian; Haitian Creole.
-<DT><SAMP>`hu´</SAMP>
+<DT><SAMP>‘hu’</SAMP>
<DD>
Hungarian.
-<DT><SAMP>`hy´</SAMP>
+<DT><SAMP>‘hy’</SAMP>
<DD>
Armenian.
-<DT><SAMP>`hz´</SAMP>
+<DT><SAMP>‘hz’</SAMP>
<DD>
Herero.
-<DT><SAMP>`ia´</SAMP>
+<DT><SAMP>‘ia’</SAMP>
<DD>
Interlingua.
-<DT><SAMP>`id´</SAMP>
+<DT><SAMP>‘id’</SAMP>
<DD>
Indonesian (formerly in).
-<DT><SAMP>`ie´</SAMP>
+<DT><SAMP>‘ie’</SAMP>
<DD>
Interlingue.
-<DT><SAMP>`ig´</SAMP>
+<DT><SAMP>‘ig’</SAMP>
<DD>
Igbo.
-<DT><SAMP>`ii´</SAMP>
+<DT><SAMP>‘ii’</SAMP>
<DD>
Sichuan Yi.
-<DT><SAMP>`ik´</SAMP>
+<DT><SAMP>‘ik’</SAMP>
<DD>
Inupiak.
-<DT><SAMP>`io´</SAMP>
+<DT><SAMP>‘io’</SAMP>
<DD>
Ido.
-<DT><SAMP>`is´</SAMP>
+<DT><SAMP>‘is’</SAMP>
<DD>
Icelandic.
-<DT><SAMP>`it´</SAMP>
+<DT><SAMP>‘it’</SAMP>
<DD>
Italian.
-<DT><SAMP>`iu´</SAMP>
+<DT><SAMP>‘iu’</SAMP>
<DD>
Inuktitut.
-<DT><SAMP>`ja´</SAMP>
+<DT><SAMP>‘ja’</SAMP>
<DD>
Japanese.
-<DT><SAMP>`jv´</SAMP>
+<DT><SAMP>‘jv’</SAMP>
<DD>
Javanese.
-<DT><SAMP>`ka´</SAMP>
+<DT><SAMP>‘ka’</SAMP>
<DD>
Georgian.
-<DT><SAMP>`kg´</SAMP>
+<DT><SAMP>‘kg’</SAMP>
<DD>
Kongo.
-<DT><SAMP>`ki´</SAMP>
+<DT><SAMP>‘ki’</SAMP>
<DD>
Kikuyu.
-<DT><SAMP>`kj´</SAMP>
+<DT><SAMP>‘kj’</SAMP>
<DD>
Kuanyama.
-<DT><SAMP>`kk´</SAMP>
+<DT><SAMP>‘kk’</SAMP>
<DD>
Kazakh.
-<DT><SAMP>`kl´</SAMP>
+<DT><SAMP>‘kl’</SAMP>
<DD>
Kalaallisut; Greenlandic.
-<DT><SAMP>`km´</SAMP>
+<DT><SAMP>‘km’</SAMP>
<DD>
Khmer; Cambodian.
-<DT><SAMP>`kn´</SAMP>
+<DT><SAMP>‘kn’</SAMP>
<DD>
Kannada.
-<DT><SAMP>`ko´</SAMP>
+<DT><SAMP>‘ko’</SAMP>
<DD>
Korean.
-<DT><SAMP>`kr´</SAMP>
+<DT><SAMP>‘kr’</SAMP>
<DD>
Kanuri.
-<DT><SAMP>`ks´</SAMP>
+<DT><SAMP>‘ks’</SAMP>
<DD>
Kashmiri.
-<DT><SAMP>`ku´</SAMP>
+<DT><SAMP>‘ku’</SAMP>
<DD>
Kurdish.
-<DT><SAMP>`kv´</SAMP>
+<DT><SAMP>‘kv’</SAMP>
<DD>
Komi.
-<DT><SAMP>`kw´</SAMP>
+<DT><SAMP>‘kw’</SAMP>
<DD>
Cornish.
-<DT><SAMP>`ky´</SAMP>
+<DT><SAMP>‘ky’</SAMP>
<DD>
Kirghiz.
-<DT><SAMP>`la´</SAMP>
+<DT><SAMP>‘la’</SAMP>
<DD>
Latin.
-<DT><SAMP>`lb´</SAMP>
+<DT><SAMP>‘lb’</SAMP>
<DD>
Letzeburgesch.
-<DT><SAMP>`lg´</SAMP>
+<DT><SAMP>‘lg’</SAMP>
<DD>
Ganda.
-<DT><SAMP>`li´</SAMP>
+<DT><SAMP>‘li’</SAMP>
<DD>
Limburgish; Limburger; Limburgan.
-<DT><SAMP>`ln´</SAMP>
+<DT><SAMP>‘ln’</SAMP>
<DD>
Lingala.
-<DT><SAMP>`lo´</SAMP>
+<DT><SAMP>‘lo’</SAMP>
<DD>
Lao; Laotian.
-<DT><SAMP>`lt´</SAMP>
+<DT><SAMP>‘lt’</SAMP>
<DD>
Lithuanian.
-<DT><SAMP>`lu´</SAMP>
+<DT><SAMP>‘lu’</SAMP>
<DD>
Luba-Katanga.
-<DT><SAMP>`lv´</SAMP>
+<DT><SAMP>‘lv’</SAMP>
<DD>
Latvian; Lettish.
-<DT><SAMP>`mg´</SAMP>
+<DT><SAMP>‘mg’</SAMP>
<DD>
Malagasy.
-<DT><SAMP>`mh´</SAMP>
+<DT><SAMP>‘mh’</SAMP>
<DD>
Marshall.
-<DT><SAMP>`mi´</SAMP>
+<DT><SAMP>‘mi’</SAMP>
<DD>
Maori.
-<DT><SAMP>`mk´</SAMP>
+<DT><SAMP>‘mk’</SAMP>
<DD>
Macedonian.
-<DT><SAMP>`ml´</SAMP>
+<DT><SAMP>‘ml’</SAMP>
<DD>
Malayalam.
-<DT><SAMP>`mn´</SAMP>
+<DT><SAMP>‘mn’</SAMP>
<DD>
Mongolian.
-<DT><SAMP>`mo´</SAMP>
+<DT><SAMP>‘mo’</SAMP>
<DD>
Moldavian.
-<DT><SAMP>`mr´</SAMP>
+<DT><SAMP>‘mr’</SAMP>
<DD>
Marathi.
-<DT><SAMP>`ms´</SAMP>
+<DT><SAMP>‘ms’</SAMP>
<DD>
Malay.
-<DT><SAMP>`mt´</SAMP>
+<DT><SAMP>‘mt’</SAMP>
<DD>
Maltese.
-<DT><SAMP>`my´</SAMP>
+<DT><SAMP>‘my’</SAMP>
<DD>
Burmese.
-<DT><SAMP>`na´</SAMP>
+<DT><SAMP>‘na’</SAMP>
<DD>
Nauru.
-<DT><SAMP>`nb´</SAMP>
+<DT><SAMP>‘nb’</SAMP>
<DD>
Norwegian Bokmål.
-<DT><SAMP>`nd´</SAMP>
+<DT><SAMP>‘nd’</SAMP>
<DD>
Ndebele, North.
-<DT><SAMP>`ne´</SAMP>
+<DT><SAMP>‘ne’</SAMP>
<DD>
Nepali.
-<DT><SAMP>`ng´</SAMP>
+<DT><SAMP>‘ng’</SAMP>
<DD>
Ndonga.
-<DT><SAMP>`nl´</SAMP>
+<DT><SAMP>‘nl’</SAMP>
<DD>
Dutch.
-<DT><SAMP>`nn´</SAMP>
+<DT><SAMP>‘nn’</SAMP>
<DD>
Norwegian Nynorsk.
-<DT><SAMP>`no´</SAMP>
+<DT><SAMP>‘no’</SAMP>
<DD>
Norwegian.
-<DT><SAMP>`nr´</SAMP>
+<DT><SAMP>‘nr’</SAMP>
<DD>
Ndebele, South.
-<DT><SAMP>`nv´</SAMP>
+<DT><SAMP>‘nv’</SAMP>
<DD>
Navajo.
-<DT><SAMP>`ny´</SAMP>
+<DT><SAMP>‘ny’</SAMP>
<DD>
Chichewa; Nyanja.
-<DT><SAMP>`oc´</SAMP>
+<DT><SAMP>‘oc’</SAMP>
<DD>
Occitan; Provençal.
-<DT><SAMP>`oj´</SAMP>
+<DT><SAMP>‘oj’</SAMP>
<DD>
Ojibwa.
-<DT><SAMP>`om´</SAMP>
+<DT><SAMP>‘om’</SAMP>
<DD>
(Afan) Oromo.
-<DT><SAMP>`or´</SAMP>
+<DT><SAMP>‘or’</SAMP>
<DD>
Oriya.
-<DT><SAMP>`os´</SAMP>
+<DT><SAMP>‘os’</SAMP>
<DD>
Ossetian; Ossetic.
-<DT><SAMP>`pa´</SAMP>
+<DT><SAMP>‘pa’</SAMP>
<DD>
Panjabi; Punjabi.
-<DT><SAMP>`pi´</SAMP>
+<DT><SAMP>‘pi’</SAMP>
<DD>
Pali.
-<DT><SAMP>`pl´</SAMP>
+<DT><SAMP>‘pl’</SAMP>
<DD>
Polish.
-<DT><SAMP>`ps´</SAMP>
+<DT><SAMP>‘ps’</SAMP>
<DD>
Pashto, Pushto.
-<DT><SAMP>`pt´</SAMP>
+<DT><SAMP>‘pt’</SAMP>
<DD>
Portuguese.
-<DT><SAMP>`qu´</SAMP>
+<DT><SAMP>‘qu’</SAMP>
<DD>
Quechua.
-<DT><SAMP>`rm´</SAMP>
+<DT><SAMP>‘rm’</SAMP>
<DD>
Rhaeto-Romance.
-<DT><SAMP>`rn´</SAMP>
+<DT><SAMP>‘rn’</SAMP>
<DD>
Rundi; Kirundi.
-<DT><SAMP>`ro´</SAMP>
+<DT><SAMP>‘ro’</SAMP>
<DD>
Romanian.
-<DT><SAMP>`ru´</SAMP>
+<DT><SAMP>‘ru’</SAMP>
<DD>
Russian.
-<DT><SAMP>`rw´</SAMP>
+<DT><SAMP>‘rw’</SAMP>
<DD>
Kinyarwanda.
-<DT><SAMP>`sa´</SAMP>
+<DT><SAMP>‘sa’</SAMP>
<DD>
Sanskrit.
-<DT><SAMP>`sc´</SAMP>
+<DT><SAMP>‘sc’</SAMP>
<DD>
Sardinian.
-<DT><SAMP>`sd´</SAMP>
+<DT><SAMP>‘sd’</SAMP>
<DD>
Sindhi.
-<DT><SAMP>`se´</SAMP>
+<DT><SAMP>‘se’</SAMP>
<DD>
Northern Sami.
-<DT><SAMP>`sg´</SAMP>
+<DT><SAMP>‘sg’</SAMP>
<DD>
Sango; Sangro.
-<DT><SAMP>`si´</SAMP>
+<DT><SAMP>‘si’</SAMP>
<DD>
Sinhalese.
-<DT><SAMP>`sk´</SAMP>
+<DT><SAMP>‘sk’</SAMP>
<DD>
Slovak.
-<DT><SAMP>`sl´</SAMP>
+<DT><SAMP>‘sl’</SAMP>
<DD>
Slovenian.
-<DT><SAMP>`sm´</SAMP>
+<DT><SAMP>‘sm’</SAMP>
<DD>
Samoan.
-<DT><SAMP>`sn´</SAMP>
+<DT><SAMP>‘sn’</SAMP>
<DD>
Shona.
-<DT><SAMP>`so´</SAMP>
+<DT><SAMP>‘so’</SAMP>
<DD>
Somali.
-<DT><SAMP>`sq´</SAMP>
+<DT><SAMP>‘sq’</SAMP>
<DD>
Albanian.
-<DT><SAMP>`sr´</SAMP>
+<DT><SAMP>‘sr’</SAMP>
<DD>
Serbian.
-<DT><SAMP>`ss´</SAMP>
+<DT><SAMP>‘ss’</SAMP>
<DD>
Swati; Siswati.
-<DT><SAMP>`st´</SAMP>
+<DT><SAMP>‘st’</SAMP>
<DD>
Sesotho; Sotho, Southern.
-<DT><SAMP>`su´</SAMP>
+<DT><SAMP>‘su’</SAMP>
<DD>
Sundanese.
-<DT><SAMP>`sv´</SAMP>
+<DT><SAMP>‘sv’</SAMP>
<DD>
Swedish.
-<DT><SAMP>`sw´</SAMP>
+<DT><SAMP>‘sw’</SAMP>
<DD>
Swahili.
-<DT><SAMP>`ta´</SAMP>
+<DT><SAMP>‘ta’</SAMP>
<DD>
Tamil.
-<DT><SAMP>`te´</SAMP>
+<DT><SAMP>‘te’</SAMP>
<DD>
Telugu.
-<DT><SAMP>`tg´</SAMP>
+<DT><SAMP>‘tg’</SAMP>
<DD>
Tajik.
-<DT><SAMP>`th´</SAMP>
+<DT><SAMP>‘th’</SAMP>
<DD>
Thai.
-<DT><SAMP>`ti´</SAMP>
+<DT><SAMP>‘ti’</SAMP>
<DD>
Tigrinya.
-<DT><SAMP>`tk´</SAMP>
+<DT><SAMP>‘tk’</SAMP>
<DD>
Turkmen.
-<DT><SAMP>`tl´</SAMP>
+<DT><SAMP>‘tl’</SAMP>
<DD>
Tagalog.
-<DT><SAMP>`tn´</SAMP>
+<DT><SAMP>‘tn’</SAMP>
<DD>
Tswana; Setswana.
-<DT><SAMP>`to´</SAMP>
+<DT><SAMP>‘to’</SAMP>
<DD>
Tonga (?).
-<DT><SAMP>`tr´</SAMP>
+<DT><SAMP>‘tr’</SAMP>
<DD>
Turkish.
-<DT><SAMP>`ts´</SAMP>
+<DT><SAMP>‘ts’</SAMP>
<DD>
Tsonga.
-<DT><SAMP>`tt´</SAMP>
+<DT><SAMP>‘tt’</SAMP>
<DD>
Tatar.
-<DT><SAMP>`tw´</SAMP>
+<DT><SAMP>‘tw’</SAMP>
<DD>
Twi.
-<DT><SAMP>`ty´</SAMP>
+<DT><SAMP>‘ty’</SAMP>
<DD>
Tahitian.
-<DT><SAMP>`ug´</SAMP>
+<DT><SAMP>‘ug’</SAMP>
<DD>
Uighur.
-<DT><SAMP>`uk´</SAMP>
+<DT><SAMP>‘uk’</SAMP>
<DD>
Ukrainian.
-<DT><SAMP>`ur´</SAMP>
+<DT><SAMP>‘ur’</SAMP>
<DD>
Urdu.
-<DT><SAMP>`uz´</SAMP>
+<DT><SAMP>‘uz’</SAMP>
<DD>
Uzbek.
-<DT><SAMP>`ve´</SAMP>
+<DT><SAMP>‘ve’</SAMP>
<DD>
Venda.
-<DT><SAMP>`vi´</SAMP>
+<DT><SAMP>‘vi’</SAMP>
<DD>
Vietnamese.
-<DT><SAMP>`vo´</SAMP>
+<DT><SAMP>‘vo’</SAMP>
<DD>
Volapük; Volapuk.
-<DT><SAMP>`wa´</SAMP>
+<DT><SAMP>‘wa’</SAMP>
<DD>
Walloon.
-<DT><SAMP>`wo´</SAMP>
+<DT><SAMP>‘wo’</SAMP>
<DD>
Wolof.
-<DT><SAMP>`xh´</SAMP>
+<DT><SAMP>‘xh’</SAMP>
<DD>
Xhosa.
-<DT><SAMP>`yi´</SAMP>
+<DT><SAMP>‘yi’</SAMP>
<DD>
Yiddish (formerly ji).
-<DT><SAMP>`yo´</SAMP>
+<DT><SAMP>‘yo’</SAMP>
<DD>
Yoruba.
-<DT><SAMP>`za´</SAMP>
+<DT><SAMP>‘za’</SAMP>
<DD>
Zhuang.
-<DT><SAMP>`zh´</SAMP>
+<DT><SAMP>‘zh’</SAMP>
<DD>
Chinese.
-<DT><SAMP>`zu´</SAMP>
+<DT><SAMP>‘zu’</SAMP>
<DD>
Zulu.
</DL>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_16.html">previous</A>, <A HREF="gettext_18.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_16.html">previous</A>, <A HREF="gettext_18.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - B Country Codes</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_17.html">previous</A>, <A HREF="gettext_19.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_17.html">previous</A>, <A HREF="gettext_19.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC294" HREF="gettext_toc.html#TOC294">B Country Codes</A></H1>
+<H1><A NAME="SEC298" HREF="gettext_toc.html#TOC298">B Country Codes</A></H1>
<P>
-<A NAME="IDX1171"></A>
-<A NAME="IDX1172"></A>
+<A NAME="IDX1197"></A>
+<A NAME="IDX1198"></A>
</P>
<P>
</P>
<DL COMPACT>
-<DT><SAMP>`AD´</SAMP>
+<DT><SAMP>‘AD’</SAMP>
<DD>
Andorra.
-<DT><SAMP>`AE´</SAMP>
+<DT><SAMP>‘AE’</SAMP>
<DD>
United Arab Emirates.
-<DT><SAMP>`AF´</SAMP>
+<DT><SAMP>‘AF’</SAMP>
<DD>
Afghanistan.
-<DT><SAMP>`AG´</SAMP>
+<DT><SAMP>‘AG’</SAMP>
<DD>
Antigua and Barbuda.
-<DT><SAMP>`AI´</SAMP>
+<DT><SAMP>‘AI’</SAMP>
<DD>
Anguilla.
-<DT><SAMP>`AL´</SAMP>
+<DT><SAMP>‘AL’</SAMP>
<DD>
Albania.
-<DT><SAMP>`AM´</SAMP>
+<DT><SAMP>‘AM’</SAMP>
<DD>
Armenia.
-<DT><SAMP>`AN´</SAMP>
+<DT><SAMP>‘AN’</SAMP>
<DD>
Netherlands Antilles.
-<DT><SAMP>`AO´</SAMP>
+<DT><SAMP>‘AO’</SAMP>
<DD>
Angola.
-<DT><SAMP>`AQ´</SAMP>
+<DT><SAMP>‘AQ’</SAMP>
<DD>
Antarctica.
-<DT><SAMP>`AR´</SAMP>
+<DT><SAMP>‘AR’</SAMP>
<DD>
Argentina.
-<DT><SAMP>`AS´</SAMP>
+<DT><SAMP>‘AS’</SAMP>
<DD>
Samoa (American).
-<DT><SAMP>`AT´</SAMP>
+<DT><SAMP>‘AT’</SAMP>
<DD>
Austria.
-<DT><SAMP>`AU´</SAMP>
+<DT><SAMP>‘AU’</SAMP>
<DD>
Australia.
-<DT><SAMP>`AW´</SAMP>
+<DT><SAMP>‘AW’</SAMP>
<DD>
Aruba.
-<DT><SAMP>`AZ´</SAMP>
+<DT><SAMP>‘AZ’</SAMP>
<DD>
Azerbaijan.
-<DT><SAMP>`BA´</SAMP>
+<DT><SAMP>‘BA’</SAMP>
<DD>
Bosnia and Herzegovina.
-<DT><SAMP>`BB´</SAMP>
+<DT><SAMP>‘BB’</SAMP>
<DD>
Barbados.
-<DT><SAMP>`BD´</SAMP>
+<DT><SAMP>‘BD’</SAMP>
<DD>
Bangladesh.
-<DT><SAMP>`BE´</SAMP>
+<DT><SAMP>‘BE’</SAMP>
<DD>
Belgium.
-<DT><SAMP>`BF´</SAMP>
+<DT><SAMP>‘BF’</SAMP>
<DD>
Burkina Faso.
-<DT><SAMP>`BG´</SAMP>
+<DT><SAMP>‘BG’</SAMP>
<DD>
Bulgaria.
-<DT><SAMP>`BH´</SAMP>
+<DT><SAMP>‘BH’</SAMP>
<DD>
Bahrain.
-<DT><SAMP>`BI´</SAMP>
+<DT><SAMP>‘BI’</SAMP>
<DD>
Burundi.
-<DT><SAMP>`BJ´</SAMP>
+<DT><SAMP>‘BJ’</SAMP>
<DD>
Benin.
-<DT><SAMP>`BM´</SAMP>
+<DT><SAMP>‘BM’</SAMP>
<DD>
Bermuda.
-<DT><SAMP>`BN´</SAMP>
+<DT><SAMP>‘BN’</SAMP>
<DD>
Brunei.
-<DT><SAMP>`BO´</SAMP>
+<DT><SAMP>‘BO’</SAMP>
<DD>
Bolivia.
-<DT><SAMP>`BR´</SAMP>
+<DT><SAMP>‘BR’</SAMP>
<DD>
Brazil.
-<DT><SAMP>`BS´</SAMP>
+<DT><SAMP>‘BS’</SAMP>
<DD>
Bahamas.
-<DT><SAMP>`BT´</SAMP>
+<DT><SAMP>‘BT’</SAMP>
<DD>
Bhutan.
-<DT><SAMP>`BV´</SAMP>
+<DT><SAMP>‘BV’</SAMP>
<DD>
Bouvet Island.
-<DT><SAMP>`BW´</SAMP>
+<DT><SAMP>‘BW’</SAMP>
<DD>
Botswana.
-<DT><SAMP>`BY´</SAMP>
+<DT><SAMP>‘BY’</SAMP>
<DD>
Belarus.
-<DT><SAMP>`BZ´</SAMP>
+<DT><SAMP>‘BZ’</SAMP>
<DD>
Belize.
-<DT><SAMP>`CA´</SAMP>
+<DT><SAMP>‘CA’</SAMP>
<DD>
Canada.
-<DT><SAMP>`CC´</SAMP>
+<DT><SAMP>‘CC’</SAMP>
<DD>
Cocos (Keeling) Islands.
-<DT><SAMP>`CD´</SAMP>
+<DT><SAMP>‘CD’</SAMP>
<DD>
Congo (Dem. Rep.).
-<DT><SAMP>`CF´</SAMP>
+<DT><SAMP>‘CF’</SAMP>
<DD>
Central African Rep..
-<DT><SAMP>`CG´</SAMP>
+<DT><SAMP>‘CG’</SAMP>
<DD>
Congo (Rep.).
-<DT><SAMP>`CH´</SAMP>
+<DT><SAMP>‘CH’</SAMP>
<DD>
Switzerland.
-<DT><SAMP>`CI´</SAMP>
+<DT><SAMP>‘CI’</SAMP>
<DD>
Côte d'Ivoire.
-<DT><SAMP>`CK´</SAMP>
+<DT><SAMP>‘CK’</SAMP>
<DD>
Cook Islands.
-<DT><SAMP>`CL´</SAMP>
+<DT><SAMP>‘CL’</SAMP>
<DD>
Chile.
-<DT><SAMP>`CM´</SAMP>
+<DT><SAMP>‘CM’</SAMP>
<DD>
Cameroon.
-<DT><SAMP>`CN´</SAMP>
+<DT><SAMP>‘CN’</SAMP>
<DD>
China.
-<DT><SAMP>`CO´</SAMP>
+<DT><SAMP>‘CO’</SAMP>
<DD>
Colombia.
-<DT><SAMP>`CR´</SAMP>
+<DT><SAMP>‘CR’</SAMP>
<DD>
Costa Rica.
-<DT><SAMP>`CS´</SAMP>
+<DT><SAMP>‘CS’</SAMP>
<DD>
Serbia and Montenegro.
-<DT><SAMP>`CU´</SAMP>
+<DT><SAMP>‘CU’</SAMP>
<DD>
Cuba.
-<DT><SAMP>`CV´</SAMP>
+<DT><SAMP>‘CV’</SAMP>
<DD>
Cape Verde.
-<DT><SAMP>`CX´</SAMP>
+<DT><SAMP>‘CX’</SAMP>
<DD>
Christmas Island.
-<DT><SAMP>`CY´</SAMP>
+<DT><SAMP>‘CY’</SAMP>
<DD>
Cyprus.
-<DT><SAMP>`CZ´</SAMP>
+<DT><SAMP>‘CZ’</SAMP>
<DD>
Czech Republic.
-<DT><SAMP>`DE´</SAMP>
+<DT><SAMP>‘DE’</SAMP>
<DD>
Germany.
-<DT><SAMP>`DJ´</SAMP>
+<DT><SAMP>‘DJ’</SAMP>
<DD>
Djibouti.
-<DT><SAMP>`DK´</SAMP>
+<DT><SAMP>‘DK’</SAMP>
<DD>
Denmark.
-<DT><SAMP>`DM´</SAMP>
+<DT><SAMP>‘DM’</SAMP>
<DD>
Dominica.
-<DT><SAMP>`DO´</SAMP>
+<DT><SAMP>‘DO’</SAMP>
<DD>
Dominican Republic.
-<DT><SAMP>`DZ´</SAMP>
+<DT><SAMP>‘DZ’</SAMP>
<DD>
Algeria.
-<DT><SAMP>`EC´</SAMP>
+<DT><SAMP>‘EC’</SAMP>
<DD>
Ecuador.
-<DT><SAMP>`EE´</SAMP>
+<DT><SAMP>‘EE’</SAMP>
<DD>
Estonia.
-<DT><SAMP>`EG´</SAMP>
+<DT><SAMP>‘EG’</SAMP>
<DD>
Egypt.
-<DT><SAMP>`EH´</SAMP>
+<DT><SAMP>‘EH’</SAMP>
<DD>
Western Sahara.
-<DT><SAMP>`ER´</SAMP>
+<DT><SAMP>‘ER’</SAMP>
<DD>
Eritrea.
-<DT><SAMP>`ES´</SAMP>
+<DT><SAMP>‘ES’</SAMP>
<DD>
Spain.
-<DT><SAMP>`ET´</SAMP>
+<DT><SAMP>‘ET’</SAMP>
<DD>
Ethiopia.
-<DT><SAMP>`FI´</SAMP>
+<DT><SAMP>‘FI’</SAMP>
<DD>
Finland.
-<DT><SAMP>`FJ´</SAMP>
+<DT><SAMP>‘FJ’</SAMP>
<DD>
Fiji.
-<DT><SAMP>`FK´</SAMP>
+<DT><SAMP>‘FK’</SAMP>
<DD>
Falkland Islands.
-<DT><SAMP>`FM´</SAMP>
+<DT><SAMP>‘FM’</SAMP>
<DD>
Micronesia.
-<DT><SAMP>`FO´</SAMP>
+<DT><SAMP>‘FO’</SAMP>
<DD>
Faeroe Islands.
-<DT><SAMP>`FR´</SAMP>
+<DT><SAMP>‘FR’</SAMP>
<DD>
France.
-<DT><SAMP>`GA´</SAMP>
+<DT><SAMP>‘GA’</SAMP>
<DD>
Gabon.
-<DT><SAMP>`GB´</SAMP>
+<DT><SAMP>‘GB’</SAMP>
<DD>
Britain (UK).
-<DT><SAMP>`GD´</SAMP>
+<DT><SAMP>‘GD’</SAMP>
<DD>
Grenada.
-<DT><SAMP>`GE´</SAMP>
+<DT><SAMP>‘GE’</SAMP>
<DD>
Georgia.
-<DT><SAMP>`GF´</SAMP>
+<DT><SAMP>‘GF’</SAMP>
<DD>
French Guiana.
-<DT><SAMP>`GH´</SAMP>
+<DT><SAMP>‘GH’</SAMP>
<DD>
Ghana.
-<DT><SAMP>`GI´</SAMP>
+<DT><SAMP>‘GI’</SAMP>
<DD>
Gibraltar.
-<DT><SAMP>`GL´</SAMP>
+<DT><SAMP>‘GL’</SAMP>
<DD>
Greenland.
-<DT><SAMP>`GM´</SAMP>
+<DT><SAMP>‘GM’</SAMP>
<DD>
Gambia.
-<DT><SAMP>`GN´</SAMP>
+<DT><SAMP>‘GN’</SAMP>
<DD>
Guinea.
-<DT><SAMP>`GP´</SAMP>
+<DT><SAMP>‘GP’</SAMP>
<DD>
Guadeloupe.
-<DT><SAMP>`GQ´</SAMP>
+<DT><SAMP>‘GQ’</SAMP>
<DD>
Equatorial Guinea.
-<DT><SAMP>`GR´</SAMP>
+<DT><SAMP>‘GR’</SAMP>
<DD>
Greece.
-<DT><SAMP>`GS´</SAMP>
+<DT><SAMP>‘GS’</SAMP>
<DD>
South Georgia and the South Sandwich Islands.
-<DT><SAMP>`GT´</SAMP>
+<DT><SAMP>‘GT’</SAMP>
<DD>
Guatemala.
-<DT><SAMP>`GU´</SAMP>
+<DT><SAMP>‘GU’</SAMP>
<DD>
Guam.
-<DT><SAMP>`GW´</SAMP>
+<DT><SAMP>‘GW’</SAMP>
<DD>
Guinea-Bissau.
-<DT><SAMP>`GY´</SAMP>
+<DT><SAMP>‘GY’</SAMP>
<DD>
Guyana.
-<DT><SAMP>`HK´</SAMP>
+<DT><SAMP>‘HK’</SAMP>
<DD>
Hong Kong.
-<DT><SAMP>`HM´</SAMP>
+<DT><SAMP>‘HM’</SAMP>
<DD>
Heard Island and McDonald Islands.
-<DT><SAMP>`HN´</SAMP>
+<DT><SAMP>‘HN’</SAMP>
<DD>
Honduras.
-<DT><SAMP>`HR´</SAMP>
+<DT><SAMP>‘HR’</SAMP>
<DD>
Croatia.
-<DT><SAMP>`HT´</SAMP>
+<DT><SAMP>‘HT’</SAMP>
<DD>
Haiti.
-<DT><SAMP>`HU´</SAMP>
+<DT><SAMP>‘HU’</SAMP>
<DD>
Hungary.
-<DT><SAMP>`ID´</SAMP>
+<DT><SAMP>‘ID’</SAMP>
<DD>
Indonesia.
-<DT><SAMP>`IE´</SAMP>
+<DT><SAMP>‘IE’</SAMP>
<DD>
Ireland.
-<DT><SAMP>`IL´</SAMP>
+<DT><SAMP>‘IL’</SAMP>
<DD>
Israel.
-<DT><SAMP>`IN´</SAMP>
+<DT><SAMP>‘IN’</SAMP>
<DD>
India.
-<DT><SAMP>`IO´</SAMP>
+<DT><SAMP>‘IO’</SAMP>
<DD>
British Indian Ocean Territory.
-<DT><SAMP>`IQ´</SAMP>
+<DT><SAMP>‘IQ’</SAMP>
<DD>
Iraq.
-<DT><SAMP>`IR´</SAMP>
+<DT><SAMP>‘IR’</SAMP>
<DD>
Iran.
-<DT><SAMP>`IS´</SAMP>
+<DT><SAMP>‘IS’</SAMP>
<DD>
Iceland.
-<DT><SAMP>`IT´</SAMP>
+<DT><SAMP>‘IT’</SAMP>
<DD>
Italy.
-<DT><SAMP>`JM´</SAMP>
+<DT><SAMP>‘JM’</SAMP>
<DD>
Jamaica.
-<DT><SAMP>`JO´</SAMP>
+<DT><SAMP>‘JO’</SAMP>
<DD>
Jordan.
-<DT><SAMP>`JP´</SAMP>
+<DT><SAMP>‘JP’</SAMP>
<DD>
Japan.
-<DT><SAMP>`KE´</SAMP>
+<DT><SAMP>‘KE’</SAMP>
<DD>
Kenya.
-<DT><SAMP>`KG´</SAMP>
+<DT><SAMP>‘KG’</SAMP>
<DD>
Kyrgyzstan.
-<DT><SAMP>`KH´</SAMP>
+<DT><SAMP>‘KH’</SAMP>
<DD>
Cambodia.
-<DT><SAMP>`KI´</SAMP>
+<DT><SAMP>‘KI’</SAMP>
<DD>
Kiribati.
-<DT><SAMP>`KM´</SAMP>
+<DT><SAMP>‘KM’</SAMP>
<DD>
Comoros.
-<DT><SAMP>`KN´</SAMP>
+<DT><SAMP>‘KN’</SAMP>
<DD>
St Kitts and Nevis.
-<DT><SAMP>`KP´</SAMP>
+<DT><SAMP>‘KP’</SAMP>
<DD>
Korea (North).
-<DT><SAMP>`KR´</SAMP>
+<DT><SAMP>‘KR’</SAMP>
<DD>
Korea (South).
-<DT><SAMP>`KW´</SAMP>
+<DT><SAMP>‘KW’</SAMP>
<DD>
Kuwait.
-<DT><SAMP>`KY´</SAMP>
+<DT><SAMP>‘KY’</SAMP>
<DD>
Cayman Islands.
-<DT><SAMP>`KZ´</SAMP>
+<DT><SAMP>‘KZ’</SAMP>
<DD>
Kazakhstan.
-<DT><SAMP>`LA´</SAMP>
+<DT><SAMP>‘LA’</SAMP>
<DD>
Laos.
-<DT><SAMP>`LB´</SAMP>
+<DT><SAMP>‘LB’</SAMP>
<DD>
Lebanon.
-<DT><SAMP>`LC´</SAMP>
+<DT><SAMP>‘LC’</SAMP>
<DD>
St Lucia.
-<DT><SAMP>`LI´</SAMP>
+<DT><SAMP>‘LI’</SAMP>
<DD>
Liechtenstein.
-<DT><SAMP>`LK´</SAMP>
+<DT><SAMP>‘LK’</SAMP>
<DD>
Sri Lanka.
-<DT><SAMP>`LR´</SAMP>
+<DT><SAMP>‘LR’</SAMP>
<DD>
Liberia.
-<DT><SAMP>`LS´</SAMP>
+<DT><SAMP>‘LS’</SAMP>
<DD>
Lesotho.
-<DT><SAMP>`LT´</SAMP>
+<DT><SAMP>‘LT’</SAMP>
<DD>
Lithuania.
-<DT><SAMP>`LU´</SAMP>
+<DT><SAMP>‘LU’</SAMP>
<DD>
Luxembourg.
-<DT><SAMP>`LV´</SAMP>
+<DT><SAMP>‘LV’</SAMP>
<DD>
Latvia.
-<DT><SAMP>`LY´</SAMP>
+<DT><SAMP>‘LY’</SAMP>
<DD>
Libya.
-<DT><SAMP>`MA´</SAMP>
+<DT><SAMP>‘MA’</SAMP>
<DD>
Morocco.
-<DT><SAMP>`MC´</SAMP>
+<DT><SAMP>‘MC’</SAMP>
<DD>
Monaco.
-<DT><SAMP>`MD´</SAMP>
+<DT><SAMP>‘MD’</SAMP>
<DD>
Moldova.
-<DT><SAMP>`MG´</SAMP>
+<DT><SAMP>‘MG’</SAMP>
<DD>
Madagascar.
-<DT><SAMP>`MH´</SAMP>
+<DT><SAMP>‘MH’</SAMP>
<DD>
Marshall Islands.
-<DT><SAMP>`MK´</SAMP>
+<DT><SAMP>‘MK’</SAMP>
<DD>
Macedonia.
-<DT><SAMP>`ML´</SAMP>
+<DT><SAMP>‘ML’</SAMP>
<DD>
Mali.
-<DT><SAMP>`MM´</SAMP>
+<DT><SAMP>‘MM’</SAMP>
<DD>
Myanmar (Burma).
-<DT><SAMP>`MN´</SAMP>
+<DT><SAMP>‘MN’</SAMP>
<DD>
Mongolia.
-<DT><SAMP>`MO´</SAMP>
+<DT><SAMP>‘MO’</SAMP>
<DD>
Macao.
-<DT><SAMP>`MP´</SAMP>
+<DT><SAMP>‘MP’</SAMP>
<DD>
Northern Mariana Islands.
-<DT><SAMP>`MQ´</SAMP>
+<DT><SAMP>‘MQ’</SAMP>
<DD>
Martinique.
-<DT><SAMP>`MR´</SAMP>
+<DT><SAMP>‘MR’</SAMP>
<DD>
Mauritania.
-<DT><SAMP>`MS´</SAMP>
+<DT><SAMP>‘MS’</SAMP>
<DD>
Montserrat.
-<DT><SAMP>`MT´</SAMP>
+<DT><SAMP>‘MT’</SAMP>
<DD>
Malta.
-<DT><SAMP>`MU´</SAMP>
+<DT><SAMP>‘MU’</SAMP>
<DD>
Mauritius.
-<DT><SAMP>`MV´</SAMP>
+<DT><SAMP>‘MV’</SAMP>
<DD>
Maldives.
-<DT><SAMP>`MW´</SAMP>
+<DT><SAMP>‘MW’</SAMP>
<DD>
Malawi.
-<DT><SAMP>`MX´</SAMP>
+<DT><SAMP>‘MX’</SAMP>
<DD>
Mexico.
-<DT><SAMP>`MY´</SAMP>
+<DT><SAMP>‘MY’</SAMP>
<DD>
Malaysia.
-<DT><SAMP>`MZ´</SAMP>
+<DT><SAMP>‘MZ’</SAMP>
<DD>
Mozambique.
-<DT><SAMP>`NA´</SAMP>
+<DT><SAMP>‘NA’</SAMP>
<DD>
Namibia.
-<DT><SAMP>`NC´</SAMP>
+<DT><SAMP>‘NC’</SAMP>
<DD>
New Caledonia.
-<DT><SAMP>`NE´</SAMP>
+<DT><SAMP>‘NE’</SAMP>
<DD>
Niger.
-<DT><SAMP>`NF´</SAMP>
+<DT><SAMP>‘NF’</SAMP>
<DD>
Norfolk Island.
-<DT><SAMP>`NG´</SAMP>
+<DT><SAMP>‘NG’</SAMP>
<DD>
Nigeria.
-<DT><SAMP>`NI´</SAMP>
+<DT><SAMP>‘NI’</SAMP>
<DD>
Nicaragua.
-<DT><SAMP>`NL´</SAMP>
+<DT><SAMP>‘NL’</SAMP>
<DD>
Netherlands.
-<DT><SAMP>`NO´</SAMP>
+<DT><SAMP>‘NO’</SAMP>
<DD>
Norway.
-<DT><SAMP>`NP´</SAMP>
+<DT><SAMP>‘NP’</SAMP>
<DD>
Nepal.
-<DT><SAMP>`NR´</SAMP>
+<DT><SAMP>‘NR’</SAMP>
<DD>
Nauru.
-<DT><SAMP>`NU´</SAMP>
+<DT><SAMP>‘NU’</SAMP>
<DD>
Niue.
-<DT><SAMP>`NZ´</SAMP>
+<DT><SAMP>‘NZ’</SAMP>
<DD>
New Zealand.
-<DT><SAMP>`OM´</SAMP>
+<DT><SAMP>‘OM’</SAMP>
<DD>
Oman.
-<DT><SAMP>`PA´</SAMP>
+<DT><SAMP>‘PA’</SAMP>
<DD>
Panama.
-<DT><SAMP>`PE´</SAMP>
+<DT><SAMP>‘PE’</SAMP>
<DD>
Peru.
-<DT><SAMP>`PF´</SAMP>
+<DT><SAMP>‘PF’</SAMP>
<DD>
French Polynesia.
-<DT><SAMP>`PG´</SAMP>
+<DT><SAMP>‘PG’</SAMP>
<DD>
Papua New Guinea.
-<DT><SAMP>`PH´</SAMP>
+<DT><SAMP>‘PH’</SAMP>
<DD>
Philippines.
-<DT><SAMP>`PK´</SAMP>
+<DT><SAMP>‘PK’</SAMP>
<DD>
Pakistan.
-<DT><SAMP>`PL´</SAMP>
+<DT><SAMP>‘PL’</SAMP>
<DD>
Poland.
-<DT><SAMP>`PM´</SAMP>
+<DT><SAMP>‘PM’</SAMP>
<DD>
St Pierre and Miquelon.
-<DT><SAMP>`PN´</SAMP>
+<DT><SAMP>‘PN’</SAMP>
<DD>
Pitcairn.
-<DT><SAMP>`PR´</SAMP>
+<DT><SAMP>‘PR’</SAMP>
<DD>
Puerto Rico.
-<DT><SAMP>`PS´</SAMP>
+<DT><SAMP>‘PS’</SAMP>
<DD>
Palestine.
-<DT><SAMP>`PT´</SAMP>
+<DT><SAMP>‘PT’</SAMP>
<DD>
Portugal.
-<DT><SAMP>`PW´</SAMP>
+<DT><SAMP>‘PW’</SAMP>
<DD>
Palau.
-<DT><SAMP>`PY´</SAMP>
+<DT><SAMP>‘PY’</SAMP>
<DD>
Paraguay.
-<DT><SAMP>`QA´</SAMP>
+<DT><SAMP>‘QA’</SAMP>
<DD>
Qatar.
-<DT><SAMP>`RE´</SAMP>
+<DT><SAMP>‘RE’</SAMP>
<DD>
Reunion.
-<DT><SAMP>`RO´</SAMP>
+<DT><SAMP>‘RO’</SAMP>
<DD>
Romania.
-<DT><SAMP>`RU´</SAMP>
+<DT><SAMP>‘RU’</SAMP>
<DD>
Russia.
-<DT><SAMP>`RW´</SAMP>
+<DT><SAMP>‘RW’</SAMP>
<DD>
Rwanda.
-<DT><SAMP>`SA´</SAMP>
+<DT><SAMP>‘SA’</SAMP>
<DD>
Saudi Arabia.
-<DT><SAMP>`SB´</SAMP>
+<DT><SAMP>‘SB’</SAMP>
<DD>
Solomon Islands.
-<DT><SAMP>`SC´</SAMP>
+<DT><SAMP>‘SC’</SAMP>
<DD>
Seychelles.
-<DT><SAMP>`SD´</SAMP>
+<DT><SAMP>‘SD’</SAMP>
<DD>
Sudan.
-<DT><SAMP>`SE´</SAMP>
+<DT><SAMP>‘SE’</SAMP>
<DD>
Sweden.
-<DT><SAMP>`SG´</SAMP>
+<DT><SAMP>‘SG’</SAMP>
<DD>
Singapore.
-<DT><SAMP>`SH´</SAMP>
+<DT><SAMP>‘SH’</SAMP>
<DD>
St Helena.
-<DT><SAMP>`SI´</SAMP>
+<DT><SAMP>‘SI’</SAMP>
<DD>
Slovenia.
-<DT><SAMP>`SJ´</SAMP>
+<DT><SAMP>‘SJ’</SAMP>
<DD>
Svalbard and Jan Mayen.
-<DT><SAMP>`SK´</SAMP>
+<DT><SAMP>‘SK’</SAMP>
<DD>
Slovakia.
-<DT><SAMP>`SL´</SAMP>
+<DT><SAMP>‘SL’</SAMP>
<DD>
Sierra Leone.
-<DT><SAMP>`SM´</SAMP>
+<DT><SAMP>‘SM’</SAMP>
<DD>
San Marino.
-<DT><SAMP>`SN´</SAMP>
+<DT><SAMP>‘SN’</SAMP>
<DD>
Senegal.
-<DT><SAMP>`SO´</SAMP>
+<DT><SAMP>‘SO’</SAMP>
<DD>
Somalia.
-<DT><SAMP>`SR´</SAMP>
+<DT><SAMP>‘SR’</SAMP>
<DD>
Suriname.
-<DT><SAMP>`ST´</SAMP>
+<DT><SAMP>‘ST’</SAMP>
<DD>
Sao Tome and Principe.
-<DT><SAMP>`SV´</SAMP>
+<DT><SAMP>‘SV’</SAMP>
<DD>
El Salvador.
-<DT><SAMP>`SY´</SAMP>
+<DT><SAMP>‘SY’</SAMP>
<DD>
Syria.
-<DT><SAMP>`SZ´</SAMP>
+<DT><SAMP>‘SZ’</SAMP>
<DD>
Swaziland.
-<DT><SAMP>`TC´</SAMP>
+<DT><SAMP>‘TC’</SAMP>
<DD>
Turks and Caicos Islands.
-<DT><SAMP>`TD´</SAMP>
+<DT><SAMP>‘TD’</SAMP>
<DD>
Chad.
-<DT><SAMP>`TF´</SAMP>
+<DT><SAMP>‘TF’</SAMP>
<DD>
French Southern and Antarctic Lands.
-<DT><SAMP>`TG´</SAMP>
+<DT><SAMP>‘TG’</SAMP>
<DD>
Togo.
-<DT><SAMP>`TH´</SAMP>
+<DT><SAMP>‘TH’</SAMP>
<DD>
Thailand.
-<DT><SAMP>`TJ´</SAMP>
+<DT><SAMP>‘TJ’</SAMP>
<DD>
Tajikistan.
-<DT><SAMP>`TK´</SAMP>
+<DT><SAMP>‘TK’</SAMP>
<DD>
Tokelau.
-<DT><SAMP>`TL´</SAMP>
+<DT><SAMP>‘TL’</SAMP>
<DD>
Timor-Leste.
-<DT><SAMP>`TM´</SAMP>
+<DT><SAMP>‘TM’</SAMP>
<DD>
Turkmenistan.
-<DT><SAMP>`TN´</SAMP>
+<DT><SAMP>‘TN’</SAMP>
<DD>
Tunisia.
-<DT><SAMP>`TO´</SAMP>
+<DT><SAMP>‘TO’</SAMP>
<DD>
Tonga.
-<DT><SAMP>`TR´</SAMP>
+<DT><SAMP>‘TR’</SAMP>
<DD>
Turkey.
-<DT><SAMP>`TT´</SAMP>
+<DT><SAMP>‘TT’</SAMP>
<DD>
Trinidad and Tobago.
-<DT><SAMP>`TV´</SAMP>
+<DT><SAMP>‘TV’</SAMP>
<DD>
Tuvalu.
-<DT><SAMP>`TW´</SAMP>
+<DT><SAMP>‘TW’</SAMP>
<DD>
Taiwan.
-<DT><SAMP>`TZ´</SAMP>
+<DT><SAMP>‘TZ’</SAMP>
<DD>
Tanzania.
-<DT><SAMP>`UA´</SAMP>
+<DT><SAMP>‘UA’</SAMP>
<DD>
Ukraine.
-<DT><SAMP>`UG´</SAMP>
+<DT><SAMP>‘UG’</SAMP>
<DD>
Uganda.
-<DT><SAMP>`UM´</SAMP>
+<DT><SAMP>‘UM’</SAMP>
<DD>
US minor outlying islands.
-<DT><SAMP>`US´</SAMP>
+<DT><SAMP>‘US’</SAMP>
<DD>
United States.
-<DT><SAMP>`UY´</SAMP>
+<DT><SAMP>‘UY’</SAMP>
<DD>
Uruguay.
-<DT><SAMP>`UZ´</SAMP>
+<DT><SAMP>‘UZ’</SAMP>
<DD>
Uzbekistan.
-<DT><SAMP>`VA´</SAMP>
+<DT><SAMP>‘VA’</SAMP>
<DD>
Vatican City.
-<DT><SAMP>`VC´</SAMP>
+<DT><SAMP>‘VC’</SAMP>
<DD>
St Vincent.
-<DT><SAMP>`VE´</SAMP>
+<DT><SAMP>‘VE’</SAMP>
<DD>
Venezuela.
-<DT><SAMP>`VG´</SAMP>
+<DT><SAMP>‘VG’</SAMP>
<DD>
Virgin Islands (UK).
-<DT><SAMP>`VI´</SAMP>
+<DT><SAMP>‘VI’</SAMP>
<DD>
Virgin Islands (US).
-<DT><SAMP>`VN´</SAMP>
+<DT><SAMP>‘VN’</SAMP>
<DD>
Vietnam.
-<DT><SAMP>`VU´</SAMP>
+<DT><SAMP>‘VU’</SAMP>
<DD>
Vanuatu.
-<DT><SAMP>`WF´</SAMP>
+<DT><SAMP>‘WF’</SAMP>
<DD>
Wallis and Futuna.
-<DT><SAMP>`WS´</SAMP>
+<DT><SAMP>‘WS’</SAMP>
<DD>
Samoa (Western).
-<DT><SAMP>`YE´</SAMP>
+<DT><SAMP>‘YE’</SAMP>
<DD>
Yemen.
-<DT><SAMP>`YT´</SAMP>
+<DT><SAMP>‘YT’</SAMP>
<DD>
Mayotte.
-<DT><SAMP>`ZA´</SAMP>
+<DT><SAMP>‘ZA’</SAMP>
<DD>
South Africa.
-<DT><SAMP>`ZM´</SAMP>
+<DT><SAMP>‘ZM’</SAMP>
<DD>
Zambia.
-<DT><SAMP>`ZW´</SAMP>
+<DT><SAMP>‘ZW’</SAMP>
<DD>
Zimbabwe.
</DL>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_17.html">previous</A>, <A HREF="gettext_19.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_17.html">previous</A>, <A HREF="gettext_19.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
-<TITLE>GNU gettext utilities - Program Index</TITLE>
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+<TITLE>GNU gettext utilities - C Licenses</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_18.html">previous</A>, <A HREF="gettext_20.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_18.html">previous</A>, <A HREF="gettext_20.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC295" HREF="gettext_toc.html#TOC295">Program Index</A></H1>
-
-<P>
-Jump to:
-<A HREF="#pindex_a">a</A>
--
-<A HREF="#pindex_e">e</A>
--
-<A HREF="#pindex_g">g</A>
--
-<A HREF="#pindex_m">m</A>
--
-<A HREF="#pindex_n">n</A>
--
-<A HREF="#pindex_x">x</A>
-<P>
-<H2><A NAME="pindex_a">a</A></H2>
-<DIR>
-<LI><A HREF="gettext_13.html#IDX1063">autopoint</A>
-</DIR>
-<H2><A NAME="pindex_e">e</A></H2>
-<DIR>
-<LI><A HREF="gettext_15.html#IDX1112">envsubst</A>
-</DIR>
-<H2><A NAME="pindex_g">g</A></H2>
-<DIR>
-<LI><A HREF="gettext_15.html#IDX1084">gettext</A>, <A HREF="gettext_15.html#IDX1089">gettext</A>
-<LI><A HREF="gettext_13.html#IDX1029">gettextize</A>
-</DIR>
-<H2><A NAME="pindex_m">m</A></H2>
-<DIR>
-<LI><A HREF="gettext_9.html#IDX761">msgattrib</A>
-<LI><A HREF="gettext_9.html#IDX503">msgcat</A>
-<LI><A HREF="gettext_9.html#IDX747">msgcmp</A>
-<LI><A HREF="gettext_9.html#IDX707">msgcomm</A>
-<LI><A HREF="gettext_9.html#IDX548">msgconv</A>
-<LI><A HREF="gettext_9.html#IDX808">msgen</A>
-<LI><A HREF="gettext_9.html#IDX838">msgexec</A>
-<LI><A HREF="gettext_9.html#IDX627">msgfilter</A>
-<LI><A HREF="gettext_10.html#IDX869">msgfmt</A>
-<LI><A HREF="gettext_9.html#IDX580">msggrep</A>
-<LI><A HREF="gettext_6.html#IDX206">msginit</A>
-<LI><A HREF="gettext_7.html#IDX241">msgmerge</A>
-<LI><A HREF="gettext_10.html#IDX931">msgunfmt</A>
-<LI><A HREF="gettext_9.html#IDX668">msguniq</A>
-</DIR>
-<H2><A NAME="pindex_n">n</A></H2>
-<DIR>
-<LI><A HREF="gettext_15.html#IDX1085">ngettext</A>, <A HREF="gettext_15.html#IDX1101">ngettext</A>
-</DIR>
-<H2><A NAME="pindex_x">x</A></H2>
-<DIR>
-<LI><A HREF="gettext_5.html#IDX135">xgettext</A>
-</DIR>
+<H1><A NAME="SEC299" HREF="gettext_toc.html#TOC299">C Licenses</A></H1>
+<P>
+<A NAME="IDX1199"></A>
+
+</P>
+<P>
+The files of this package are covered by the licenses indicated in each
+particular file or directory. Here is a summary:
+
+</P>
+
+<UL>
+<LI>
+
+The <CODE>libintl</CODE> and <CODE>libasprintf</CODE> libraries are covered by the
+GNU Library General Public License (LGPL).
+A copy of the license is included in section <A HREF="gettext_19.html#SEC303">C.2 GNU LESSER GENERAL PUBLIC LICENSE</A>.
+
+<LI>
+
+The executable programs of this package and the <CODE>libgettextpo</CODE> library
+are covered by the GNU General Public License (GPL).
+A copy of the license is included in section <A HREF="gettext_19.html#SEC300">C.1 GNU GENERAL PUBLIC LICENSE</A>.
+
+<LI>
+
+This manual is free documentation. It is dually licensed under the
+GNU FDL and the GNU GPL. This means that you can redistribute this
+manual under either of these two licenses, at your choice.
+<BR>
+This manual is covered by the GNU FDL. Permission is granted to copy,
+distribute and/or modify this document under the terms of the
+GNU Free Documentation License (FDL), either version 1.2 of the
+License, or (at your option) any later version published by the
+Free Software Foundation (FSF); with no Invariant Sections, with no
+Front-Cover Text, and with no Back-Cover Texts.
+A copy of the license is included in section <A HREF="gettext_19.html#SEC306">C.3 GNU Free Documentation License</A>.
+<BR>
+This manual is covered by the GNU GPL. You can redistribute it and/or
+modify it under the terms of the GNU General Public License (GPL), either
+version 2 of the License, or (at your option) any later version published
+by the Free Software Foundation (FSF).
+A copy of the license is included in section <A HREF="gettext_19.html#SEC300">C.1 GNU GENERAL PUBLIC LICENSE</A>.
+</UL>
+
+
+
+<H2><A NAME="SEC300" HREF="gettext_toc.html#TOC300">C.1 GNU GENERAL PUBLIC LICENSE</A></H2>
+<P>
+<A NAME="IDX1200"></A>
+<A NAME="IDX1201"></A>
+Version 2, June 1991
+
+</P>
+
+
+<PRE>
+Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+</PRE>
+
+
+
+<H3><A NAME="SEC301" HREF="gettext_toc.html#TOC301">Preamble</A></H3>
+
+<P>
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.) You can apply it to
+your programs, too.
+
+</P>
+<P>
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+</P>
+<P>
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+</P>
+<P>
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+</P>
+<P>
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+</P>
+<P>
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+</P>
+<P>
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+</P>
+<P>
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+</P>
+
+
+<OL>
+<LI>
+
+This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The “Program”, below,
+refers to any such program or work, and a “work based on the Program”
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term “modification”.) Each licensee is addressed as “you”.
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+<LI>
+
+You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+<LI>
+
+You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+
+<OL>
+<LI>
+
+You must cause the modified files to carry prominent notices
+stating that you changed the files and the date of any change.
+
+<LI>
+
+You must cause any work that you distribute or publish, that in
+whole or in part contains or is derived from the Program or any
+part thereof, to be licensed as a whole at no charge to all third
+parties under the terms of this License.
+
+<LI>
+
+If the modified program normally reads commands interactively
+when run, you must cause it, when started running for such
+interactive use in the most ordinary way, to print or display an
+announcement including an appropriate copyright notice and a
+notice that there is no warranty (or else, saying that you provide
+a warranty) and that users may redistribute the program under
+these conditions, and telling the user how to view a copy of this
+License. (Exception: if the Program itself is interactive but
+does not normally print such an announcement, your work based on
+the Program is not required to print an announcement.)
+</OL>
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+<LI>
+
+You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+
+<OL>
+<LI>
+
+Accompany it with the complete corresponding machine-readable
+source code, which must be distributed under the terms of Sections
+1 and 2 above on a medium customarily used for software interchange; or,
+
+<LI>
+
+Accompany it with a written offer, valid for at least three
+years, to give any third party, for a charge no more than your
+cost of physically performing source distribution, a complete
+machine-readable copy of the corresponding source code, to be
+distributed under the terms of Sections 1 and 2 above on a medium
+customarily used for software interchange; or,
+
+<LI>
+
+Accompany it with the information you received as to the offer
+to distribute corresponding source code. (This alternative is
+allowed only for noncommercial distribution and only if you
+received the program in object code or executable form with such
+an offer, in accord with Subsection b above.)
+</OL>
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+<LI>
+
+You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+<LI>
+
+You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+<LI>
+
+Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+<LI>
+
+If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+<LI>
+
+If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+<LI>
+
+The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and “any
+later version”, you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+<LI>
+
+If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+<LI>
+
+BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+<LI>
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+</OL>
+
+
+
+<H3><A NAME="SEC302" HREF="gettext_toc.html#TOC302">Appendix: How to Apply These Terms to Your New Programs</A></H3>
+
+<P>
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+</P>
+<P>
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the “copyright” line and a pointer to where the full notice is found.
+
+</P>
+
+<PRE>
+<VAR>one line to give the program's name and a brief idea of what it does.</VAR>
+Copyright (C) <VAR>yyyy</VAR> <VAR>name of author</VAR>
+
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program; if not, write to the Free Software
+Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+</PRE>
+
+<P>
+Also add information on how to contact you by electronic and paper mail.
+
+</P>
+<P>
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+</P>
+
+<PRE>
+Gnomovision version 69, Copyright (C) 19<VAR>yy</VAR> <VAR>name of author</VAR>
+Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+This is free software, and you are welcome to redistribute it
+under certain conditions; type `show c' for details.
+</PRE>
+
+<P>
+The hypothetical commands <SAMP>‘show w’</SAMP> and <SAMP>‘show c’</SAMP> should show
+the appropriate parts of the General Public License. Of course, the
+commands you use may be called something other than <SAMP>‘show w’</SAMP> and
+<SAMP>‘show c’</SAMP>; they could even be mouse-clicks or menu items--whatever
+suits your program.
+
+</P>
+<P>
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a “copyright disclaimer” for the program, if
+necessary. Here is a sample; alter the names:
+
+</P>
+
+<PRE>
+Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+`Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+<VAR>signature of Ty Coon</VAR>, 1 April 1989
+Ty Coon, President of Vice
+</PRE>
+
+<P>
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Library General
+Public License instead of this License.
+
+
+<H2><A NAME="SEC303" HREF="gettext_toc.html#TOC303">C.2 GNU LESSER GENERAL PUBLIC LICENSE</A></H2>
+<P>
+<A NAME="IDX1202"></A>
+<A NAME="IDX1203"></A>
+Version 2.1, February 1999
+
+</P>
+
+<PRE>
+Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+51 Franklin St -- Fifth Floor, Boston, MA 02110-1301, USA
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL. It also counts
+as the successor of the GNU Library Public License, version 2, hence the
+version number 2.1.]
+</PRE>
+
+
+
+<H3><A NAME="SEC304" HREF="gettext_toc.html#TOC304">Preamble</A></H3>
+
+<P>
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+</P>
+<P>
+ This license, the Lesser General Public License, applies to some
+specially designated software--typically libraries--of the Free
+Software Foundation and other authors who decide to use it. You can use
+it too, but we suggest you first think carefully about whether this
+license or the ordinary General Public License is the better strategy to
+use in any particular case, based on the explanations below.
+
+</P>
+<P>
+ When we speak of free software, we are referring to freedom of use,
+not price. Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of it
+in new free programs; and that you are informed that you can do these
+things.
+
+</P>
+<P>
+ To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights. These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
</P>
+<P>
+ For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it. And you must show them these terms so they know their rights.
+
+</P>
+<P>
+ We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+
+</P>
+<P>
+ To protect each distributor, we want to make it very clear that
+there is no warranty for the free library. Also, if the library is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
+
+</P>
+<P>
+ Finally, software patents pose a constant threat to the existence of
+any free program. We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder. Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+
+</P>
+<P>
+ Most GNU software, including some libraries, is covered by the
+ordinary GNU General Public License. This license, the GNU Lesser
+General Public License, applies to certain designated libraries, and
+is quite different from the ordinary General Public License. We use
+this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+</P>
+<P>
+ When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library. The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom. The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+
+</P>
+<P>
+ We call this license the <EM>Lesser</EM> General Public License because it
+does <EM>Less</EM> to protect the user's freedom than the ordinary General
+Public License. It also provides other free software developers Less
+of an advantage over competing non-free programs. These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries. However, the Lesser license provides advantages in certain
+special circumstances.
+
+</P>
+<P>
+ For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it becomes
+a de-facto standard. To achieve this, non-free programs must be
+allowed to use the library. A more frequent case is that a free
+library does the same job as widely used non-free libraries. In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+
+</P>
+<P>
+ In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of
+free software. For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+
+</P>
+<P>
+ Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+that program using a modified version of the Library.
+
+</P>
+<P>
+ The precise terms and conditions for copying, distribution and
+modification follow. Pay close attention to the difference between a
+“work based on the library” and a “work that uses the library”. The
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
+
+</P>
+
+
+<OL>
+<LI>
+
+This License Agreement applies to any software library or other program
+which contains a notice placed by the copyright holder or other
+authorized party saying it may be distributed under the terms of this
+Lesser General Public License (also called “this License”). Each
+licensee is addressed as “you”.
+
+ A “library” means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+ The “Library”, below, refers to any such software library or work
+which has been distributed under these terms. A “work based on the
+Library” means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is
+included without limitation in the term “modification”.)
+
+ “Source code” for a work means the preferred form of the work for
+making modifications to it. For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+ Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it). Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+
+<LI>
+
+You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+ You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+
+<LI>
+
+You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+
+<OL>
+<LI>
+
+The modified work must itself be a software library.
+
+<LI>
+
+You must cause the files modified to carry prominent notices
+stating that you changed the files and the date of any change.
+
+<LI>
+
+You must cause the whole of the work to be licensed at no
+charge to all third parties under the terms of this License.
+
+<LI>
+
+If a facility in the modified Library refers to a function or a
+table of data to be supplied by an application program that uses
+the facility, other than as an argument passed when the facility
+is invoked, then you must make a good faith effort to ensure that,
+in the event an application does not supply such function or
+table, the facility still operates, and performs whatever part of
+its purpose remains meaningful.
+
+(For example, a function in a library to compute square roots has
+a purpose that is entirely well-defined independent of the
+application. Therefore, Subsection 2d requires that any
+application-supplied function or table used by this function must
+be optional: if the application does not supply it, the square
+root function must still compute square roots.)
+</OL>
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+<LI>
+
+You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library. To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License. (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.) Do not make any other change in
+these notices.
+
+ Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+ This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+<LI>
+
+You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+ If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+<LI>
+
+A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a “work that uses the Library”. Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+ However, linking a “work that uses the Library” with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a “work that uses the
+library”. The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+ When a “work that uses the Library” uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+ If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work. (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+ Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+<LI>
+
+As an exception to the Sections above, you may also combine or
+link a “work that uses the Library” with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+ You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License. You must supply a copy of this License. If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one
+of these things:
+
+
+<OL>
+<LI>
+
+Accompany the work with the complete corresponding
+machine-readable source code for the Library including whatever
+changes were used in the work (which must be distributed under
+Sections 1 and 2 above); and, if the work is an executable linked
+with the Library, with the complete machine-readable “work that
+uses the Library”, as object code and/or source code, so that the
+user can modify the Library and then relink to produce a modified
+executable containing the modified Library. (It is understood
+that the user who changes the contents of definitions files in the
+Library will not necessarily be able to recompile the application
+to use the modified definitions.)
+
+<LI>
+
+Use a suitable shared library mechanism for linking with the Library. A
+suitable mechanism is one that (1) uses at run time a copy of the
+library already present on the user's computer system, rather than
+copying library functions into the executable, and (2) will operate
+properly with a modified version of the library, if the user installs
+one, as long as the modified version is interface-compatible with the
+version that the work was made with.
+
+<LI>
+
+Accompany the work with a written offer, valid for at
+least three years, to give the same user the materials
+specified in Subsection 6a, above, for a charge no more
+than the cost of performing this distribution.
+
+<LI>
+
+If distribution of the work is made by offering access to copy
+from a designated place, offer equivalent access to copy the above
+specified materials from the same place.
+
+<LI>
+
+Verify that the user has already received a copy of these
+materials or that you have already sent this user a copy.
+</OL>
+
+ For an executable, the required form of the “work that uses the
+Library” must include any data and utility programs needed for
+reproducing the executable from it. However, as a special exception,
+the materials to be distributed need not include anything that is
+normally distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies the
+executable.
+
+ It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system. Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+
+<LI>
+
+You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+
+<OL>
+<LI>
+
+Accompany the combined library with a copy of the same work
+based on the Library, uncombined with any other library
+facilities. This must be distributed under the terms of the
+Sections above.
+
+<LI>
+
+Give prominent notice with the combined library of the fact
+that part of it is a work based on the Library, and explaining
+where to find the accompanying uncombined form of the same work.
+</OL>
+
+<LI>
+
+You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License. Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+<LI>
+
+You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+<LI>
+
+Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties with
+this License.
+
+<LI>
+
+If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all. For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+<LI>
+
+If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License may add
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded. In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+<LI>
+
+The Free Software Foundation may publish revised and/or new
+versions of the Lesser General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library
+specifies a version number of this License which applies to it and
+“any later version”, you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation. If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+<LI>
+
+If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission. For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this. Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+<LI>
+
+BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY “AS IS” WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+<LI>
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+</OL>
+
+
+
+<H3><A NAME="SEC305" HREF="gettext_toc.html#TOC305">How to Apply These Terms to Your New Libraries</A></H3>
+
+<P>
+ If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change. You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+
+</P>
+<P>
+ To apply these terms, attach the following notices to the library. It is
+safest to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least the
+“copyright” line and a pointer to where the full notice is found.
+
+</P>
+
+<PRE>
+<VAR>one line to give the library's name and an idea of what it does.</VAR>
+Copyright (C) <VAR>year</VAR> <VAR>name of author</VAR>
+
+This library is free software; you can redistribute it and/or modify it
+under the terms of the GNU Lesser General Public License as published by
+the Free Software Foundation; either version 2.1 of the License, or (at
+your option) any later version.
+
+This library is distributed in the hope that it will be useful, but
+WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+Lesser General Public License for more details.
+
+You should have received a copy of the GNU Lesser General Public
+License along with this library; if not, write to the Free Software
+Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
+USA.
+</PRE>
+
+<P>
+Also add information on how to contact you by electronic and paper mail.
+
+</P>
+<P>
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a “copyright disclaimer” for the library, if
+necessary. Here is a sample; alter the names:
+
+</P>
+
+<PRE>
+Yoyodyne, Inc., hereby disclaims all copyright interest in the library
+`Frob' (a library for tweaking knobs) written by James Random Hacker.
+
+<VAR>signature of Ty Coon</VAR>, 1 April 1990
+Ty Coon, President of Vice
+</PRE>
+
+<P>
+That's all there is to it!
+
+
+<H2><A NAME="SEC306" HREF="gettext_toc.html#TOC306">C.3 GNU Free Documentation License</A></H2>
+<P>
+<A NAME="IDX1204"></A>
+<A NAME="IDX1205"></A>
+Version 1.2, November 2002
+
+</P>
+
+<PRE>
+Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+</PRE>
+
+
+<OL>
+<LI>
+
+PREAMBLE
+
+The purpose of this License is to make a manual, textbook, or other
+functional and useful document <EM>free</EM> in the sense of freedom: to
+assure everyone the effective freedom to copy and redistribute it,
+with or without modifying it, either commercially or noncommercially.
+Secondarily, this License preserves for the author and publisher a way
+to get credit for their work, while not being considered responsible
+for modifications made by others.
+
+This License is a kind of “copyleft”, which means that derivative
+works of the document must themselves be free in the same sense. It
+complements the GNU General Public License, which is a copyleft
+license designed for free software.
+
+We have designed this License in order to use it for manuals for free
+software, because free software needs free documentation: a free
+program should come with manuals providing the same freedoms that the
+software does. But this License is not limited to software manuals;
+it can be used for any textual work, regardless of subject matter or
+whether it is published as a printed book. We recommend this License
+principally for works whose purpose is instruction or reference.
+
+<LI>
+
+APPLICABILITY AND DEFINITIONS
+
+This License applies to any manual or other work, in any medium, that
+contains a notice placed by the copyright holder saying it can be
+distributed under the terms of this License. Such a notice grants a
+world-wide, royalty-free license, unlimited in duration, to use that
+work under the conditions stated herein. The “Document”, below,
+refers to any such manual or work. Any member of the public is a
+licensee, and is addressed as “you”. You accept the license if you
+copy, modify or distribute the work in a way requiring permission
+under copyright law.
+
+A “Modified Version” of the Document means any work containing the
+Document or a portion of it, either copied verbatim, or with
+modifications and/or translated into another language.
+
+A “Secondary Section” is a named appendix or a front-matter section
+of the Document that deals exclusively with the relationship of the
+publishers or authors of the Document to the Document's overall
+subject (or to related matters) and contains nothing that could fall
+directly within that overall subject. (Thus, if the Document is in
+part a textbook of mathematics, a Secondary Section may not explain
+any mathematics.) The relationship could be a matter of historical
+connection with the subject or with related matters, or of legal,
+commercial, philosophical, ethical or political position regarding
+them.
+
+The “Invariant Sections” are certain Secondary Sections whose titles
+are designated, as being those of Invariant Sections, in the notice
+that says that the Document is released under this License. If a
+section does not fit the above definition of Secondary then it is not
+allowed to be designated as Invariant. The Document may contain zero
+Invariant Sections. If the Document does not identify any Invariant
+Sections then there are none.
+
+The “Cover Texts” are certain short passages of text that are listed,
+as Front-Cover Texts or Back-Cover Texts, in the notice that says that
+the Document is released under this License. A Front-Cover Text may
+be at most 5 words, and a Back-Cover Text may be at most 25 words.
+
+A “Transparent” copy of the Document means a machine-readable copy,
+represented in a format whose specification is available to the
+general public, that is suitable for revising the document
+straightforwardly with generic text editors or (for images composed of
+pixels) generic paint programs or (for drawings) some widely available
+drawing editor, and that is suitable for input to text formatters or
+for automatic translation to a variety of formats suitable for input
+to text formatters. A copy made in an otherwise Transparent file
+format whose markup, or absence of markup, has been arranged to thwart
+or discourage subsequent modification by readers is not Transparent.
+An image format is not Transparent if used for any substantial amount
+of text. A copy that is not “Transparent” is called “Opaque”.
+
+Examples of suitable formats for Transparent copies include plain
+ASCII without markup, Texinfo input format, LaTeX input
+format, SGML or XML using a publicly available
+DTD, and standard-conforming simple HTML,
+PostScript or PDF designed for human modification. Examples
+of transparent image formats include PNG, XCF and
+JPG. Opaque formats include proprietary formats that can be
+read and edited only by proprietary word processors, SGML or
+XML for which the DTD and/or processing tools are
+not generally available, and the machine-generated HTML,
+PostScript or PDF produced by some word processors for
+output purposes only.
+
+The “Title Page” means, for a printed book, the title page itself,
+plus such following pages as are needed to hold, legibly, the material
+this License requires to appear in the title page. For works in
+formats which do not have any title page as such, “Title Page” means
+the text near the most prominent appearance of the work's title,
+preceding the beginning of the body of the text.
+
+A section “Entitled XYZ” means a named subunit of the Document whose
+title either is precisely XYZ or contains XYZ in parentheses following
+text that translates XYZ in another language. (Here XYZ stands for a
+specific section name mentioned below, such as “Acknowledgements”,
+“Dedications”, “Endorsements”, or “History”.) To “Preserve the Title”
+of such a section when you modify the Document means that it remains a
+section “Entitled XYZ” according to this definition.
+
+The Document may include Warranty Disclaimers next to the notice which
+states that this License applies to the Document. These Warranty
+Disclaimers are considered to be included by reference in this
+License, but only as regards disclaiming warranties: any other
+implication that these Warranty Disclaimers may have is void and has
+no effect on the meaning of this License.
+
+<LI>
+
+VERBATIM COPYING
+
+You may copy and distribute the Document in any medium, either
+commercially or noncommercially, provided that this License, the
+copyright notices, and the license notice saying this License applies
+to the Document are reproduced in all copies, and that you add no other
+conditions whatsoever to those of this License. You may not use
+technical measures to obstruct or control the reading or further
+copying of the copies you make or distribute. However, you may accept
+compensation in exchange for copies. If you distribute a large enough
+number of copies you must also follow the conditions in section 3.
+
+You may also lend copies, under the same conditions stated above, and
+you may publicly display copies.
+
+<LI>
+
+COPYING IN QUANTITY
+
+If you publish printed copies (or copies in media that commonly have
+printed covers) of the Document, numbering more than 100, and the
+Document's license notice requires Cover Texts, you must enclose the
+copies in covers that carry, clearly and legibly, all these Cover
+Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
+the back cover. Both covers must also clearly and legibly identify
+you as the publisher of these copies. The front cover must present
+the full title with all words of the title equally prominent and
+visible. You may add other material on the covers in addition.
+Copying with changes limited to the covers, as long as they preserve
+the title of the Document and satisfy these conditions, can be treated
+as verbatim copying in other respects.
+
+If the required texts for either cover are too voluminous to fit
+legibly, you should put the first ones listed (as many as fit
+reasonably) on the actual cover, and continue the rest onto adjacent
+pages.
+
+If you publish or distribute Opaque copies of the Document numbering
+more than 100, you must either include a machine-readable Transparent
+copy along with each Opaque copy, or state in or with each Opaque copy
+a computer-network location from which the general network-using
+public has access to download using public-standard network protocols
+a complete Transparent copy of the Document, free of added material.
+If you use the latter option, you must take reasonably prudent steps,
+when you begin distribution of Opaque copies in quantity, to ensure
+that this Transparent copy will remain thus accessible at the stated
+location until at least one year after the last time you distribute an
+Opaque copy (directly or through your agents or retailers) of that
+edition to the public.
+
+It is requested, but not required, that you contact the authors of the
+Document well before redistributing any large number of copies, to give
+them a chance to provide you with an updated version of the Document.
+
+<LI>
+
+MODIFICATIONS
+
+You may copy and distribute a Modified Version of the Document under
+the conditions of sections 2 and 3 above, provided that you release
+the Modified Version under precisely this License, with the Modified
+Version filling the role of the Document, thus licensing distribution
+and modification of the Modified Version to whoever possesses a copy
+of it. In addition, you must do these things in the Modified Version:
+
+
+<OL>
+<LI>
+
+Use in the Title Page (and on the covers, if any) a title distinct
+from that of the Document, and from those of previous versions
+(which should, if there were any, be listed in the History section
+of the Document). You may use the same title as a previous version
+if the original publisher of that version gives permission.
+
+<LI>
+
+List on the Title Page, as authors, one or more persons or entities
+responsible for authorship of the modifications in the Modified
+Version, together with at least five of the principal authors of the
+Document (all of its principal authors, if it has fewer than five),
+unless they release you from this requirement.
+
+<LI>
+
+State on the Title page the name of the publisher of the
+Modified Version, as the publisher.
+
+<LI>
+
+Preserve all the copyright notices of the Document.
+
+<LI>
+
+Add an appropriate copyright notice for your modifications
+adjacent to the other copyright notices.
+
+<LI>
+
+Include, immediately after the copyright notices, a license notice
+giving the public permission to use the Modified Version under the
+terms of this License, in the form shown in the Addendum below.
+
+<LI>
+
+Preserve in that license notice the full lists of Invariant Sections
+and required Cover Texts given in the Document's license notice.
+
+<LI>
+
+Include an unaltered copy of this License.
+
+<LI>
+
+Preserve the section Entitled “History”, Preserve its Title, and add
+to it an item stating at least the title, year, new authors, and
+publisher of the Modified Version as given on the Title Page. If
+there is no section Entitled “History” in the Document, create one
+stating the title, year, authors, and publisher of the Document as
+given on its Title Page, then add an item describing the Modified
+Version as stated in the previous sentence.
+
+<LI>
+
+Preserve the network location, if any, given in the Document for
+public access to a Transparent copy of the Document, and likewise
+the network locations given in the Document for previous versions
+it was based on. These may be placed in the “History” section.
+You may omit a network location for a work that was published at
+least four years before the Document itself, or if the original
+publisher of the version it refers to gives permission.
+
+<LI>
+
+For any section Entitled “Acknowledgements” or “Dedications”, Preserve
+the Title of the section, and preserve in the section all the
+substance and tone of each of the contributor acknowledgements and/or
+dedications given therein.
+
+<LI>
+
+Preserve all the Invariant Sections of the Document,
+unaltered in their text and in their titles. Section numbers
+or the equivalent are not considered part of the section titles.
+
+<LI>
+
+Delete any section Entitled “Endorsements”. Such a section
+may not be included in the Modified Version.
+
+<LI>
+
+Do not retitle any existing section to be Entitled “Endorsements” or
+to conflict in title with any Invariant Section.
+
+<LI>
+
+Preserve any Warranty Disclaimers.
+</OL>
+
+If the Modified Version includes new front-matter sections or
+appendices that qualify as Secondary Sections and contain no material
+copied from the Document, you may at your option designate some or all
+of these sections as invariant. To do this, add their titles to the
+list of Invariant Sections in the Modified Version's license notice.
+These titles must be distinct from any other section titles.
+
+You may add a section Entitled “Endorsements”, provided it contains
+nothing but endorsements of your Modified Version by various
+parties--for example, statements of peer review or that the text has
+been approved by an organization as the authoritative definition of a
+standard.
+
+You may add a passage of up to five words as a Front-Cover Text, and a
+passage of up to 25 words as a Back-Cover Text, to the end of the list
+of Cover Texts in the Modified Version. Only one passage of
+Front-Cover Text and one of Back-Cover Text may be added by (or
+through arrangements made by) any one entity. If the Document already
+includes a cover text for the same cover, previously added by you or
+by arrangement made by the same entity you are acting on behalf of,
+you may not add another; but you may replace the old one, on explicit
+permission from the previous publisher that added the old one.
+
+The author(s) and publisher(s) of the Document do not by this License
+give permission to use their names for publicity for or to assert or
+imply endorsement of any Modified Version.
+
+<LI>
+
+COMBINING DOCUMENTS
+
+You may combine the Document with other documents released under this
+License, under the terms defined in section 4 above for modified
+versions, provided that you include in the combination all of the
+Invariant Sections of all of the original documents, unmodified, and
+list them all as Invariant Sections of your combined work in its
+license notice, and that you preserve all their Warranty Disclaimers.
+
+The combined work need only contain one copy of this License, and
+multiple identical Invariant Sections may be replaced with a single
+copy. If there are multiple Invariant Sections with the same name but
+different contents, make the title of each such section unique by
+adding at the end of it, in parentheses, the name of the original
+author or publisher of that section if known, or else a unique number.
+Make the same adjustment to the section titles in the list of
+Invariant Sections in the license notice of the combined work.
+
+In the combination, you must combine any sections Entitled “History”
+in the various original documents, forming one section Entitled
+“History”; likewise combine any sections Entitled “Acknowledgements”,
+and any sections Entitled “Dedications”. You must delete all
+sections Entitled “Endorsements.”
+
+<LI>
+
+COLLECTIONS OF DOCUMENTS
+
+You may make a collection consisting of the Document and other documents
+released under this License, and replace the individual copies of this
+License in the various documents with a single copy that is included in
+the collection, provided that you follow the rules of this License for
+verbatim copying of each of the documents in all other respects.
+
+You may extract a single document from such a collection, and distribute
+it individually under this License, provided you insert a copy of this
+License into the extracted document, and follow this License in all
+other respects regarding verbatim copying of that document.
+
+<LI>
+
+AGGREGATION WITH INDEPENDENT WORKS
+
+A compilation of the Document or its derivatives with other separate
+and independent documents or works, in or on a volume of a storage or
+distribution medium, is called an “aggregate” if the copyright
+resulting from the compilation is not used to limit the legal rights
+of the compilation's users beyond what the individual works permit.
+When the Document is included in an aggregate, this License does not
+apply to the other works in the aggregate which are not themselves
+derivative works of the Document.
+
+If the Cover Text requirement of section 3 is applicable to these
+copies of the Document, then if the Document is less than one half of
+the entire aggregate, the Document's Cover Texts may be placed on
+covers that bracket the Document within the aggregate, or the
+electronic equivalent of covers if the Document is in electronic form.
+Otherwise they must appear on printed covers that bracket the whole
+aggregate.
+
+<LI>
+
+TRANSLATION
+
+Translation is considered a kind of modification, so you may
+distribute translations of the Document under the terms of section 4.
+Replacing Invariant Sections with translations requires special
+permission from their copyright holders, but you may include
+translations of some or all Invariant Sections in addition to the
+original versions of these Invariant Sections. You may include a
+translation of this License, and all the license notices in the
+Document, and any Warranty Disclaimers, provided that you also include
+the original English version of this License and the original versions
+of those notices and disclaimers. In case of a disagreement between
+the translation and the original version of this License or a notice
+or disclaimer, the original version will prevail.
+
+If a section in the Document is Entitled “Acknowledgements”,
+“Dedications”, or “History”, the requirement (section 4) to Preserve
+its Title (section 1) will typically require changing the actual
+title.
+
+<LI>
+
+TERMINATION
+
+You may not copy, modify, sublicense, or distribute the Document except
+as expressly provided for under this License. Any other attempt to
+copy, modify, sublicense or distribute the Document is void, and will
+automatically terminate your rights under this License. However,
+parties who have received copies, or rights, from you under this
+License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+<LI>
+
+FUTURE REVISIONS OF THIS LICENSE
+
+The Free Software Foundation may publish new, revised versions
+of the GNU Free Documentation License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns. See
+<A HREF="http://www.gnu.org/copyleft/">http://www.gnu.org/copyleft/</A>.
+
+Each version of the License is given a distinguishing version number.
+If the Document specifies that a particular numbered version of this
+License “or any later version” applies to it, you have the option of
+following the terms and conditions either of that specified version or
+of any later version that has been published (not as a draft) by the
+Free Software Foundation. If the Document does not specify a version
+number of this License, you may choose any version ever published (not
+as a draft) by the Free Software Foundation.
+</OL>
+
+
+
+<H3><A NAME="SEC307" HREF="gettext_toc.html#TOC307">ADDENDUM: How to use this License for your documents</A></H3>
+
+<P>
+To use this License in a document you have written, include a copy of
+the License in the document and put the following copyright and
+license notices just after the title page:
+
+</P>
+
+<PRE>
+ Copyright (C) <VAR>year</VAR> <VAR>your name</VAR>.
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the GNU Free Documentation License, Version 1.2
+ or any later version published by the Free Software Foundation;
+ with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
+ Texts. A copy of the license is included in the section entitled ``GNU
+ Free Documentation License''.
+</PRE>
+
+<P>
+If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the “with...Texts.” line with this:
+
+</P>
+
+<PRE>
+ with the Invariant Sections being <VAR>list their titles</VAR>, with
+ the Front-Cover Texts being <VAR>list</VAR>, and with the Back-Cover Texts
+ being <VAR>list</VAR>.
+</PRE>
+
+<P>
+If you have Invariant Sections without Cover Texts, or some other
+combination of the three, merge those two alternatives to suit the
+situation.
+
+</P>
+<P>
+If your document contains nontrivial examples of program code, we
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License,
+to permit their use in free software.
+
+</P>
+
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_18.html">previous</A>, <A HREF="gettext_20.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_18.html">previous</A>, <A HREF="gettext_20.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 2 The User's View</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_1.html">previous</A>, <A HREF="gettext_3.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_1.html">previous</A>, <A HREF="gettext_3.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H2><A NAME="SEC8" HREF="gettext_toc.html#TOC8">2.1 The Current <TT>`ABOUT-NLS´</TT> Matrix</A></H2>
+<H2><A NAME="SEC8" HREF="gettext_toc.html#TOC8">2.1 The Current <TT>‘ABOUT-NLS’</TT> Matrix</A></H2>
<P>
<A NAME="IDX39"></A>
<A NAME="IDX40"></A>
<P>
Languages are not equally supported in all packages using GNU
<CODE>gettext</CODE>. To know if some package uses GNU <CODE>gettext</CODE>, one
-may check the distribution for the <TT>`ABOUT-NLS´</TT> information file, for
-some <TT>`<VAR>ll</VAR>.po´</TT> files, often kept together into some <TT>`po/´</TT>
-directory, or for an <TT>`intl/´</TT> directory. Internationalized packages
-have usually many <TT>`<VAR>ll</VAR>.po´</TT> files, where <VAR>ll</VAR> represents
+may check the distribution for the <TT>‘ABOUT-NLS’</TT> information file, for
+some <TT>‘<VAR>ll</VAR>.po’</TT> files, often kept together into some <TT>‘po/’</TT>
+directory, or for an <TT>‘intl/’</TT> directory. Internationalized packages
+have usually many <TT>‘<VAR>ll</VAR>.po’</TT> files, where <VAR>ll</VAR> represents
the language. section <A HREF="gettext_2.html#SEC9">2.2 Magic for End Users</A> for a complete description of the format
for <VAR>ll</VAR>.
multi-lingual messages, and which languages are supported by each.
Because this information changes often, this matrix is not kept within
this GNU <CODE>gettext</CODE> manual. This information is often found in
-file <TT>`ABOUT-NLS´</TT> from various distributions, but is also as old as
-the distribution itself. A recent copy of this <TT>`ABOUT-NLS´</TT> file,
+file <TT>‘ABOUT-NLS’</TT> from various distributions, but is also as old as
+the distribution itself. A recent copy of this <TT>‘ABOUT-NLS’</TT> file,
containing up-to-date information, should generally be found on the
Translation Project sites, and also on most GNU archive sites.
We consider here those packages using GNU <CODE>gettext</CODE> internally,
and for which the installers did not disable translation at
<EM>configure</EM> time. Then, users only have to set the <CODE>LANG</CODE>
-environment variable to the appropriate <SAMP>`<VAR>ll</VAR>_<VAR>CC</VAR>´</SAMP>
-combination prior to using the programs in the package. See section <A HREF="gettext_2.html#SEC8">2.1 The Current <TT>`ABOUT-NLS´</TT> Matrix</A>.
+environment variable to the appropriate <SAMP>‘<VAR>ll</VAR>_<VAR>CC</VAR>’</SAMP>
+combination prior to using the programs in the package. See section <A HREF="gettext_2.html#SEC8">2.1 The Current <TT>‘ABOUT-NLS’</TT> Matrix</A>.
For example, let's presume a German site. At the shell prompt, users
-merely have to execute <SAMP>`setenv LANG de_DE´</SAMP> (in <CODE>csh</CODE>) or
-<SAMP>`export LANG; LANG=de_DE´</SAMP> (in <CODE>sh</CODE>). They could even do
-this from their <TT>`.login´</TT> or <TT>`.profile´</TT> file.
+merely have to execute <SAMP>‘setenv LANG de_DE’</SAMP> (in <CODE>csh</CODE>) or
+<SAMP>‘export LANG; LANG=de_DE’</SAMP> (in <CODE>sh</CODE>). They could even do
+this from their <TT>‘.login’</TT> or <TT>‘.profile’</TT> file.
</P>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_1.html">previous</A>, <A HREF="gettext_3.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_1.html">previous</A>, <A HREF="gettext_3.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
-<TITLE>GNU gettext utilities - Option Index</TITLE>
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+<TITLE>GNU gettext utilities - Program Index</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_19.html">previous</A>, <A HREF="gettext_21.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_19.html">previous</A>, <A HREF="gettext_21.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC296" HREF="gettext_toc.html#TOC296">Option Index</A></H1>
+<H1><A NAME="SEC308" HREF="gettext_toc.html#TOC308">Program Index</A></H1>
<P>
Jump to:
-<A HREF="#opindex_-">-</A>
+<A HREF="#pindex_a">a</A>
+-
+<A HREF="#pindex_e">e</A>
+-
+<A HREF="#pindex_g">g</A>
+-
+<A HREF="#pindex_m">m</A>
+-
+<A HREF="#pindex_n">n</A>
+-
+<A HREF="#pindex_r">r</A>
+-
+<A HREF="#pindex_x">x</A>
<P>
-<H2><A NAME="opindex_-">-</A></H2>
+<H2><A NAME="pindex_a">a</A></H2>
<DIR>
-<LI><A HREF="gettext_5.html#IDX159">--add-comments, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX792">--add-location, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX531">--add-location, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX730">--add-location, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX564">--add-location, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX822">--add-location, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX652">--add-location, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX613">--add-location, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX267">--add-location, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX691">--add-location, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX180">--add-location, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX922">--alignment, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX252">--backup, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX152">--c++, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX906">--check, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX914">--check-accelerators, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX912">--check-compatibility, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX910">--check-domain, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX907">--check-format, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX909">--check-header, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX777">--clear-fuzzy, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX779">--clear-obsolete, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX596">--comment, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX246">--compendium, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_13.html#IDX1032">--copy, <CODE>gettextize</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX194">--copyright-holder, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX878">--csharp, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX937">--csharp, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX880">--csharp-resources, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX939">--csharp-resources, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX173">--debug, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX142">--default-domain, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX766">--directory, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX510">--directory, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX751">--directory, <CODE>msgcmp</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX713">--directory, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX552">--directory, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX812">--directory, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX848">--directory, <CODE>msgexec</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX633">--directory, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX873">--directory, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX584">--directory, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX244">--directory, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX673">--directory, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX140">--directory, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1093">--domain, <CODE>gettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX590">--domain, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1105">--domain, <CODE>ngettext</CODE> option</A>
-<LI><A HREF="gettext_13.html#IDX1068">--dry-run, <CODE>autopoint</CODE> option</A>
-<LI><A HREF="gettext_13.html#IDX1038">--dry-run, <CODE>gettextize</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX157">--exclude-file, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX639">--expression, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX598">--extended-regexp, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX161">--extract-all, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX641">--file, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX604">--file, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX508">--files-from, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX711">--files-from, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX138">--files-from, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX600">--fixed-strings, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX165">--flag, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_13.html#IDX1066">--force, <CODE>autopoint</CODE> option</A>
-<LI><A HREF="gettext_13.html#IDX1034">--force, <CODE>gettextize</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX787">--force-po, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX526">--force-po, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX725">--force-po, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX560">--force-po, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX818">--force-po, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX648">--force-po, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX610">--force-po, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX263">--force-po, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX957">--force-po, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX686">--force-po, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX175">--force-po, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX195">--foreign-user, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX153">--from-code, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX782">--fuzzy, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_13.html#IDX1069">--help, <CODE>autopoint</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1120">--help, <CODE>envsubst</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1097">--help, <CODE>gettext</CODE> option</A>
-<LI><A HREF="gettext_13.html#IDX1039">--help, <CODE>gettextize</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX805">--help, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX545">--help, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX758">--help, <CODE>msgcmp</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX744">--help, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX577">--help, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX835">--help, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX853">--help, <CODE>msgexec</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX665">--help, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX925">--help, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX624">--help, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX227">--help, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX281">--help, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX971">--help, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX704">--help, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1109">--help, <CODE>ngettext</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX202">--help, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX606">--ignore-case, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX781">--ignore-file, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX789">--indent, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX528">--indent, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX727">--indent, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX562">--indent, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX820">--indent, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX649">--indent, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX611">--indent, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX265">--indent, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX959">--indent, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX688">--indent, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX177">--indent, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX846">--input, <CODE>msgexec</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX631">--input, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX211">--input, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_13.html#IDX1035">--intl, <CODE>gettextize</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX875">--java, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX935">--java, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX877">--java2, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX155">--join-existing, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX650">--keep-header, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX163">--keyword, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX149">--language, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX515">--less-than, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX717">--less-than, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX892">--locale, <CODE>msgfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX897">--locale, <CODE>msgfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX900">--locale, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX218">--locale, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX946">--locale, <CODE>msgunfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX950">--locale, <CODE>msgunfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX953">--locale, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX588">--location, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX517">--more-than, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX719">--more-than, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX592">--msgid, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX196">--msgid-bugs-address, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX594">--msgstr, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX198">--msgstr-prefix, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX200">--msgstr-suffix, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX753">--multi-domain, <CODE>msgcmp</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX257">--multi-domain, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_13.html#IDX1036">--no-changelog, <CODE>gettextize</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX771">--no-fuzzy, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX259">--no-fuzzy-matching, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX923">--no-hash, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX790">--no-location, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX529">--no-location, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX728">--no-location, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX563">--no-location, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX821">--no-location, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX651">--no-location, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX612">--no-location, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX266">--no-location, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX689">--no-location, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX178">--no-location, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX773">--no-obsolete, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX219">--no-translator, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX799">--no-wrap, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX538">--no-wrap, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX737">--no-wrap, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX571">--no-wrap, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX829">--no-wrap, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX659">--no-wrap, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX620">--no-wrap, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX225">--no-wrap, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX274">--no-wrap, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX966">--no-wrap, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX698">--no-wrap, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX186">--no-wrap, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX783">--obsolete, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX742">--omit-header, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX192">--omit-header, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX780">--only-file, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX772">--only-fuzzy, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX774">--only-obsolete, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX144">--output, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX146">--output-dir, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX768">--output-file, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX512">--output-file, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX715">--output-file, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX554">--output-file, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX814">--output-file, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX635">--output-file, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX887">--output-file, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX586">--output-file, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX213">--output-file, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX250">--output-file, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX956">--output-file, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX675">--output-file, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX785">--properties-input, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX521">--properties-input, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX755">--properties-input, <CODE>msgcmp</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX723">--properties-input, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX558">--properties-input, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX816">--properties-input, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX850">--properties-input, <CODE>msgexec</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX646">--properties-input, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX903">--properties-input, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX608">--properties-input, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX215">--properties-input, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX261">--properties-input, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX681">--properties-input, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX795">--properties-output, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX534">--properties-output, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX733">--properties-output, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX567">--properties-output, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX825">--properties-output, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX655">--properties-output, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX616">--properties-output, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX221">--properties-output, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX270">--properties-output, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX962">--properties-output, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX694">--properties-output, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX182">--properties-output, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX884">--qt, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX171">--qt, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX643">--quiet, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX287">--quiet, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX602">--regexp=, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX677">--repeated, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX890">--resource, <CODE>msgfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX895">--resource, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX944">--resource, <CODE>msgunfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX948">--resource, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX776">--set-fuzzy, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX778">--set-obsolete, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX644">--silent, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX288">--silent, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX803">--sort-by-file, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX543">--sort-by-file, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX741">--sort-by-file, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX575">--sort-by-file, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX833">--sort-by-file, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX663">--sort-by-file, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX622">--sort-by-file, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX279">--sort-by-file, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX702">--sort-by-file, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX191">--sort-by-file, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX801">--sort-output, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX540">--sort-output, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX739">--sort-output, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX573">--sort-output, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX831">--sort-output, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX661">--sort-output, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX621">--sort-output, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX276">--sort-output, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX968">--sort-output, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX700">--sort-output, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX188">--sort-output, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX928">--statistics, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX793">--strict, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX532">--strict, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX731">--strict, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX565">--strict, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX823">--strict, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX653">--strict, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX888">--strict, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX614">--strict, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX268">--strict, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX960">--strict, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX692">--strict, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX181">--strict, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX786">--stringtable-input, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX522">--stringtable-input, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX756">--stringtable-input, <CODE>msgcmp</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX724">--stringtable-input, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX817">--stringtable-input, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX851">--stringtable-input, <CODE>msgexec</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX647">--stringtable-input, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX904">--stringtable-input, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX609">--stringtable-input, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX216">--stringtable-input, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX262">--stringtable-input, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX559">--stringtable-input, <CODE>msgonv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX682">--stringtable-input, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX796">--stringtable-output, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX535">--stringtable-output, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX734">--stringtable-output, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX568">--stringtable-output, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX826">--stringtable-output, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX656">--stringtable-output, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX617">--stringtable-output, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX222">--stringtable-output, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX271">--stringtable-output, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX963">--stringtable-output, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX695">--stringtable-output, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX183">--stringtable-output, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX254">--suffix, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX882">--tcl, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX941">--tcl, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX524">--to-code, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX556">--to-code, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX684">--to-code, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX769">--translated, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX169">--trigraphs, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX519">--unique, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX721">--unique, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX679">--unique, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX770">--untranslated, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX248">--update, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX525">--use-first, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX685">--use-first, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX919">--use-fuzzy, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1118">--variables, <CODE>envsubst</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX930">--verbose, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX285">--verbose, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX975">--verbose, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_13.html#IDX1070">--version, <CODE>autopoint</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1122">--version, <CODE>envsubst</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1100">--version, <CODE>gettext</CODE> option</A>
-<LI><A HREF="gettext_13.html#IDX1040">--version, <CODE>gettextize</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX807">--version, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX547">--version, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX760">--version, <CODE>msgcmp</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX746">--version, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX579">--version, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX837">--version, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX855">--version, <CODE>msgexec</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX667">--version, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX927">--version, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX626">--version, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX229">--version, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX283">--version, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX973">--version, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX706">--version, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1111">--version, <CODE>ngettext</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX204">--version, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX798">--width, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX537">--width, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX736">--width, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX570">--width, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX828">--width, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX658">--width, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX619">--width, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX224">--width, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX273">--width, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX965">--width, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX697">--width, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX185">--width, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX514">-<, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX716">-<, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX516">->, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX718">->, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX921">-a, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX160">-a, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_13.html#IDX1031">-c, <CODE>gettextize</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX911">-C, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX905">-c, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX595">-C, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX245">-C, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX151">-C, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX158">-c, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_13.html#IDX1067">-d, <CODE>autopoint</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1092">-d, <CODE>gettext</CODE> option</A>
-<LI><A HREF="gettext_13.html#IDX1037">-d, <CODE>gettextize</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX765">-D, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX509">-D, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX750">-D, <CODE>msgcmp</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX712">-D, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX551">-D, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX811">-D, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX847">-D, <CODE>msgexec</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX632">-D, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX893">-d, <CODE>msgfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX898">-d, <CODE>msgfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX901">-d, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX872">-D, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX583">-D, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX243">-D, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX951">-d, <CODE>msgunfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX954">-d, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX672">-D, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX676">-d, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1104">-d, <CODE>ngettext</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX139">-D, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX141">-d, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1094">-e, <CODE>gettext</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1095">-E, <CODE>gettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX638">-e, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX597">-E, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX601">-e, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1106">-e, <CODE>ngettext</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1107">-E, <CODE>ngettext</CODE> option</A>
-<LI><A HREF="gettext_13.html#IDX1065">-f, <CODE>autopoint</CODE> option</A>
-<LI><A HREF="gettext_13.html#IDX1033">-f, <CODE>gettextize</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX802">-F, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX507">-f, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX542">-F, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX740">-F, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX710">-f, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX574">-F, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX832">-F, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX662">-F, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX640">-f, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX918">-f, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX603">-f, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX599">-F, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX278">-F, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX701">-F, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX190">-F, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX137">-f, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1119">-h, <CODE>envsubst</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1096">-h, <CODE>gettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX804">-h, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX544">-h, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX757">-h, <CODE>msgcmp</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX743">-h, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX576">-h, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX834">-h, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX852">-h, <CODE>msgexec</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX664">-h, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX924">-h, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX623">-h, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX226">-h, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX280">-h, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX970">-h, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX703">-h, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1108">-h, <CODE>ngettext</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX201">-h, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX788">-i, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX527">-i, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX726">-i, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX561">-i, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX819">-i, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX845">-i, <CODE>msgexec</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX630">-i, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX605">-i, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX210">-i, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX264">-i, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX958">-i, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX687">-i, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX176">-i, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX874">-j, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX934">-j, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX154">-j, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX591">-K, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX162">-k, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX891">-l, <CODE>msgfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX896">-l, <CODE>msgfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX899">-l, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX217">-l, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX945">-l, <CODE>msgunfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX949">-l, <CODE>msgunfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX952">-l, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX148">-L, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX752">-m, <CODE>msgcmp</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX589">-M, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX256">-m, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX199">-M, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX197">-m, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1098">-n, <CODE>gettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX791">-n, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX530">-n, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX729">-n, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX642">-n, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX587">-N, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX258">-N, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX690">-n, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX179">-n, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX767">-o, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX511">-o, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX714">-o, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX553">-o, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX813">-o, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX634">-o, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX886">-o, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX585">-o, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX212">-o, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX249">-o, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX955">-o, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX674">-o, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX143">-o, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX784">-P, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX794">-p, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX520">-P, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX533">-p, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX754">-P, <CODE>msgcmp</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX722">-P, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX732">-p, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX557">-P, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX566">-p, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX815">-P, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX824">-p, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX849">-P, <CODE>msgexec</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX645">-P, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX654">-p, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX902">-P, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX615">-p, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX607">-P, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX214">-P, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX220">-p, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX269">-p, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX260">-P, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX961">-p, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX693">-p, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX680">-P, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX145">-p, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX286">-q, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX889">-r, <CODE>msgfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX894">-r, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX943">-r, <CODE>msgunfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX947">-r, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX800">-s, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX539">-s, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX738">-s, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX572">-s, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX830">-s, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX660">-s, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX275">-s, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX967">-s, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX699">-s, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX187">-s, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX523">-t, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX555">-t, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX593">-T, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX683">-t, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX168">-T, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX518">-u, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX720">-u, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX247">-U, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX678">-u, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1117">-v, <CODE>envsubst</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1121">-V, <CODE>envsubst</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1099">-V, <CODE>gettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX806">-V, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX546">-V, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX759">-V, <CODE>msgcmp</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX745">-V, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX578">-V, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX836">-V, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX854">-V, <CODE>msgexec</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX666">-V, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX926">-V, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX929">-v, <CODE>msgfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX625">-V, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX228">-V, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX284">-v, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX282">-V, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX974">-v, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX972">-V, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX705">-V, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_15.html#IDX1110">-V, <CODE>ngettext</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX203">-V, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX797">-w, <CODE>msgattrib</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX536">-w, <CODE>msgcat</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX735">-w, <CODE>msgcomm</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX569">-w, <CODE>msgconv</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX827">-w, <CODE>msgen</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX657">-w, <CODE>msgfilter</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX618">-w, <CODE>msggrep</CODE> option</A>
-<LI><A HREF="gettext_6.html#IDX223">-w, <CODE>msginit</CODE> option</A>
-<LI><A HREF="gettext_7.html#IDX272">-w, <CODE>msgmerge</CODE> option</A>
-<LI><A HREF="gettext_10.html#IDX964">-w, <CODE>msgunfmt</CODE> option</A>
-<LI><A HREF="gettext_9.html#IDX696">-w, <CODE>msguniq</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX184">-w, <CODE>xgettext</CODE> option</A>
-<LI><A HREF="gettext_5.html#IDX156">-x, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1089">autopoint</A>
+</DIR>
+<H2><A NAME="pindex_e">e</A></H2>
+<DIR>
+<LI><A HREF="gettext_15.html#IDX1138">envsubst</A>
+</DIR>
+<H2><A NAME="pindex_g">g</A></H2>
+<DIR>
+<LI><A HREF="gettext_15.html#IDX1110">gettext</A>, <A HREF="gettext_15.html#IDX1115">gettext</A>
+<LI><A HREF="gettext_13.html#IDX1054">gettextize</A>
+</DIR>
+<H2><A NAME="pindex_m">m</A></H2>
+<DIR>
+<LI><A HREF="gettext_9.html#IDX778">msgattrib</A>
+<LI><A HREF="gettext_9.html#IDX512">msgcat</A>
+<LI><A HREF="gettext_9.html#IDX764">msgcmp</A>
+<LI><A HREF="gettext_9.html#IDX724">msgcomm</A>
+<LI><A HREF="gettext_9.html#IDX557">msgconv</A>
+<LI><A HREF="gettext_9.html#IDX825">msgen</A>
+<LI><A HREF="gettext_9.html#IDX855">msgexec</A>
+<LI><A HREF="gettext_9.html#IDX642">msgfilter</A>
+<LI><A HREF="gettext_10.html#IDX887">msgfmt</A>
+<LI><A HREF="gettext_9.html#IDX589">msggrep</A>
+<LI><A HREF="gettext_6.html#IDX215">msginit</A>
+<LI><A HREF="gettext_7.html#IDX250">msgmerge</A>
+<LI><A HREF="gettext_10.html#IDX949">msgunfmt</A>
+<LI><A HREF="gettext_9.html#IDX685">msguniq</A>
+</DIR>
+<H2><A NAME="pindex_n">n</A></H2>
+<DIR>
+<LI><A HREF="gettext_15.html#IDX1111">ngettext</A>, <A HREF="gettext_15.html#IDX1127">ngettext</A>
+</DIR>
+<H2><A NAME="pindex_r">r</A></H2>
+<DIR>
+<LI><A HREF="gettext_9.html#IDX660">recode-sr-latin</A>
+</DIR>
+<H2><A NAME="pindex_x">x</A></H2>
+<DIR>
+<LI><A HREF="gettext_5.html#IDX141">xgettext</A>
</DIR>
</P>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_19.html">previous</A>, <A HREF="gettext_21.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_19.html">previous</A>, <A HREF="gettext_21.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
-<TITLE>GNU gettext utilities - Variable Index</TITLE>
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+<TITLE>GNU gettext utilities - Option Index</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_20.html">previous</A>, <A HREF="gettext_22.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_20.html">previous</A>, <A HREF="gettext_22.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC297" HREF="gettext_toc.html#TOC297">Variable Index</A></H1>
+<H1><A NAME="SEC309" HREF="gettext_toc.html#TOC309">Option Index</A></H1>
<P>
Jump to:
-<A HREF="#vindex_g">g</A>
--
-<A HREF="#vindex_l">l</A>
--
-<A HREF="#vindex_m">m</A>
--
-<A HREF="#vindex_t">t</A>
+<A HREF="#opindex_-">-</A>
<P>
-<H2><A NAME="vindex_g">g</A></H2>
+<H2><A NAME="opindex_-">-</A></H2>
<DIR>
-<LI><A HREF="gettext_12.html#IDX1024">GETTEXT_LOG_UNTRANSLATED, environment variable</A>
-</DIR>
-<H2><A NAME="vindex_l">l</A></H2>
-<DIR>
-<LI><A HREF="gettext_2.html#IDX45">LANG, environment variable</A>, <A HREF="gettext_11.html#IDX1022">LANG, environment variable</A>
-<LI><A HREF="gettext_11.html#IDX1014">LANGUAGE, environment variable</A>, <A HREF="gettext_13.html#IDX1046">LANGUAGE, environment variable</A>
-<LI><A HREF="gettext_11.html#IDX1015">LC_ALL, environment variable</A>
-<LI><A HREF="gettext_11.html#IDX1019">LC_COLLATE, environment variable</A>
-<LI><A HREF="gettext_11.html#IDX1016">LC_CTYPE, environment variable</A>
-<LI><A HREF="gettext_11.html#IDX1021">LC_MESSAGES, environment variable</A>
-<LI><A HREF="gettext_11.html#IDX1020">LC_MONETARY, environment variable</A>
-<LI><A HREF="gettext_11.html#IDX1017">LC_NUMERIC, environment variable</A>
-<LI><A HREF="gettext_11.html#IDX1018">LC_TIME, environment variable</A>
-<LI><A HREF="gettext_14.html#IDX1077">LINGUAS, environment variable</A>
-</DIR>
-<H2><A NAME="vindex_m">m</A></H2>
-<DIR>
-<LI><A HREF="gettext_9.html#IDX843">MSGEXEC_LOCATION, environment variable</A>
-<LI><A HREF="gettext_9.html#IDX842">MSGEXEC_MSGID, environment variable</A>
-</DIR>
-<H2><A NAME="vindex_t">t</A></H2>
-<DIR>
-<LI><A HREF="gettext_15.html#IDX1086">TEXTDOMAIN, environment variable</A>
-<LI><A HREF="gettext_15.html#IDX1087">TEXTDOMAINDIR, environment variable</A>
+<LI><A HREF="gettext_5.html#IDX165">--add-comments, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX809">--add-location, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX540">--add-location, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX747">--add-location, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX573">--add-location, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX839">--add-location, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX669">--add-location, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX628">--add-location, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX276">--add-location, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX708">--add-location, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX189">--add-location, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX940">--alignment, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX261">--backup, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX180">--boost, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX158">--c++, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX924">--check, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX932">--check-accelerators, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX930">--check-compatibility, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX928">--check-domain, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX925">--check-format, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX927">--check-header, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX794">--clear-fuzzy, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX796">--clear-obsolete, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX607">--comment, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX255">--compendium, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1057">--copy, <CODE>gettextize</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX203">--copyright-holder, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX896">--csharp, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX955">--csharp, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX898">--csharp-resources, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX957">--csharp-resources, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX182">--debug, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX148">--default-domain, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX783">--directory, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX519">--directory, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX768">--directory, <CODE>msgcmp</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX730">--directory, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX561">--directory, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX829">--directory, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX866">--directory, <CODE>msgexec</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX648">--directory, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX891">--directory, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX593">--directory, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX253">--directory, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX690">--directory, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX146">--directory, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1119">--domain, <CODE>gettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX599">--domain, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1131">--domain, <CODE>ngettext</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1094">--dry-run, <CODE>autopoint</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1063">--dry-run, <CODE>gettextize</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX163">--exclude-file, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX654">--expression, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX611">--extended-regexp, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX167">--extract-all, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX609">--extracted-comment, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX656">--file, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX617">--file, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX517">--files-from, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX728">--files-from, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX144">--files-from, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX613">--fixed-strings, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX172">--flag, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1092">--force, <CODE>autopoint</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1059">--force, <CODE>gettextize</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX804">--force-po, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX535">--force-po, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX742">--force-po, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX569">--force-po, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX835">--force-po, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX665">--force-po, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX625">--force-po, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX272">--force-po, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX975">--force-po, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX703">--force-po, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX184">--force-po, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX204">--foreign-user, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX159">--from-code, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX799">--fuzzy, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1095">--help, <CODE>autopoint</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1146">--help, <CODE>envsubst</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1123">--help, <CODE>gettext</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1064">--help, <CODE>gettextize</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX822">--help, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX554">--help, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX775">--help, <CODE>msgcmp</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX761">--help, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX586">--help, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX852">--help, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX871">--help, <CODE>msgexec</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX682">--help, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX943">--help, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX639">--help, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX236">--help, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX290">--help, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX989">--help, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX721">--help, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1135">--help, <CODE>ngettext</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX211">--help, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX619">--ignore-case, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX798">--ignore-file, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX806">--indent, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX537">--indent, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX744">--indent, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX571">--indent, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX837">--indent, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX666">--indent, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX626">--indent, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX274">--indent, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX977">--indent, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX705">--indent, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX186">--indent, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX864">--input, <CODE>msgexec</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX646">--input, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX220">--input, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1060">--intl, <CODE>gettextize</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX621">--invert-match, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX893">--java, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX953">--java, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX895">--java2, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX161">--join-existing, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX667">--keep-header, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX169">--keyword, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX155">--language, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX524">--less-than, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX734">--less-than, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX910">--locale, <CODE>msgfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX915">--locale, <CODE>msgfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX918">--locale, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX227">--locale, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX964">--locale, <CODE>msgunfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX968">--locale, <CODE>msgunfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX971">--locale, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX597">--location, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX526">--more-than, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX736">--more-than, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX601">--msgctxt, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX603">--msgid, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX205">--msgid-bugs-address, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX605">--msgstr, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX207">--msgstr-prefix, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX209">--msgstr-suffix, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX770">--multi-domain, <CODE>msgcmp</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX266">--multi-domain, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1061">--no-changelog, <CODE>gettextize</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX788">--no-fuzzy, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX268">--no-fuzzy-matching, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX941">--no-hash, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX807">--no-location, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX538">--no-location, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX745">--no-location, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX572">--no-location, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX838">--no-location, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX668">--no-location, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX627">--no-location, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX275">--no-location, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX706">--no-location, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX187">--no-location, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX790">--no-obsolete, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX228">--no-translator, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX816">--no-wrap, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX547">--no-wrap, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX754">--no-wrap, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX580">--no-wrap, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX846">--no-wrap, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX676">--no-wrap, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX635">--no-wrap, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX234">--no-wrap, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX283">--no-wrap, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX984">--no-wrap, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX715">--no-wrap, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX195">--no-wrap, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX800">--obsolete, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX759">--omit-header, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX201">--omit-header, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX797">--only-file, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX789">--only-fuzzy, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX791">--only-obsolete, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX150">--output, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX152">--output-dir, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX785">--output-file, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX521">--output-file, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX732">--output-file, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX563">--output-file, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX831">--output-file, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX650">--output-file, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX905">--output-file, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX595">--output-file, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX222">--output-file, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX259">--output-file, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX974">--output-file, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX692">--output-file, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX802">--properties-input, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX530">--properties-input, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX772">--properties-input, <CODE>msgcmp</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX740">--properties-input, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX567">--properties-input, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX833">--properties-input, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX868">--properties-input, <CODE>msgexec</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX663">--properties-input, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX921">--properties-input, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX623">--properties-input, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX224">--properties-input, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX270">--properties-input, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX698">--properties-input, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX812">--properties-output, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX543">--properties-output, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX750">--properties-output, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX576">--properties-output, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX842">--properties-output, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX672">--properties-output, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX631">--properties-output, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX230">--properties-output, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX279">--properties-output, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX980">--properties-output, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX711">--properties-output, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX191">--properties-output, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX902">--qt, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX178">--qt, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX658">--quiet, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX296">--quiet, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX615">--regexp=, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX694">--repeated, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX908">--resource, <CODE>msgfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX913">--resource, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX962">--resource, <CODE>msgunfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX966">--resource, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX793">--set-fuzzy, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX795">--set-obsolete, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX659">--silent, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX297">--silent, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX820">--sort-by-file, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX552">--sort-by-file, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX758">--sort-by-file, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX584">--sort-by-file, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX850">--sort-by-file, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX680">--sort-by-file, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX637">--sort-by-file, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX288">--sort-by-file, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX719">--sort-by-file, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX200">--sort-by-file, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX818">--sort-output, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX549">--sort-output, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX756">--sort-output, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX582">--sort-output, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX848">--sort-output, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX678">--sort-output, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX636">--sort-output, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX285">--sort-output, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX986">--sort-output, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX717">--sort-output, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX197">--sort-output, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX946">--statistics, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX810">--strict, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX541">--strict, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX748">--strict, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX574">--strict, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX840">--strict, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX670">--strict, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX906">--strict, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX629">--strict, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX277">--strict, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX978">--strict, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX709">--strict, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX190">--strict, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX803">--stringtable-input, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX531">--stringtable-input, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX773">--stringtable-input, <CODE>msgcmp</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX741">--stringtable-input, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX834">--stringtable-input, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX869">--stringtable-input, <CODE>msgexec</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX664">--stringtable-input, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX922">--stringtable-input, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX624">--stringtable-input, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX225">--stringtable-input, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX271">--stringtable-input, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX568">--stringtable-input, <CODE>msgonv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX699">--stringtable-input, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX813">--stringtable-output, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX544">--stringtable-output, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX751">--stringtable-output, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX577">--stringtable-output, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX843">--stringtable-output, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX673">--stringtable-output, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX632">--stringtable-output, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX231">--stringtable-output, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX280">--stringtable-output, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX981">--stringtable-output, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX712">--stringtable-output, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX192">--stringtable-output, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX263">--suffix, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX900">--tcl, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX959">--tcl, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX533">--to-code, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX565">--to-code, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX701">--to-code, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX786">--translated, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX176">--trigraphs, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX528">--unique, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX738">--unique, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX696">--unique, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX787">--untranslated, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX257">--update, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX534">--use-first, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX702">--use-first, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX937">--use-fuzzy, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1144">--variables, <CODE>envsubst</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX948">--verbose, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX294">--verbose, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX993">--verbose, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1096">--version, <CODE>autopoint</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1148">--version, <CODE>envsubst</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1126">--version, <CODE>gettext</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1065">--version, <CODE>gettextize</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX824">--version, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX556">--version, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX777">--version, <CODE>msgcmp</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX763">--version, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX588">--version, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX854">--version, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX873">--version, <CODE>msgexec</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX684">--version, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX945">--version, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX641">--version, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX238">--version, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX292">--version, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX991">--version, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX723">--version, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1137">--version, <CODE>ngettext</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX213">--version, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX815">--width, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX546">--width, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX753">--width, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX579">--width, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX845">--width, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX675">--width, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX634">--width, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX233">--width, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX282">--width, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX983">--width, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX714">--width, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX194">--width, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX523">-<, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX733">-<, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX525">->, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX735">->, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX939">-a, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX166">-a, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1056">-c, <CODE>gettextize</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX929">-C, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX923">-c, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX606">-C, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX254">-C, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX157">-C, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX164">-c, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1093">-d, <CODE>autopoint</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1118">-d, <CODE>gettext</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1062">-d, <CODE>gettextize</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX782">-D, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX518">-D, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX767">-D, <CODE>msgcmp</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX729">-D, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX560">-D, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX828">-D, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX865">-D, <CODE>msgexec</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX647">-D, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX911">-d, <CODE>msgfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX916">-d, <CODE>msgfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX919">-d, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX890">-D, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX592">-D, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX252">-D, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX969">-d, <CODE>msgunfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX972">-d, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX689">-D, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX693">-d, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1130">-d, <CODE>ngettext</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX145">-D, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX147">-d, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1120">-e, <CODE>gettext</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1121">-E, <CODE>gettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX653">-e, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX610">-E, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX614">-e, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1132">-e, <CODE>ngettext</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1133">-E, <CODE>ngettext</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1091">-f, <CODE>autopoint</CODE> option</A>
+<LI><A HREF="gettext_13.html#IDX1058">-f, <CODE>gettextize</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX819">-F, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX516">-f, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX551">-F, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX757">-F, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX727">-f, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX583">-F, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX849">-F, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX679">-F, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX655">-f, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX936">-f, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX616">-f, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX612">-F, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX287">-F, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX718">-F, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX199">-F, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX143">-f, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1145">-h, <CODE>envsubst</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1122">-h, <CODE>gettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX821">-h, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX553">-h, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX774">-h, <CODE>msgcmp</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX760">-h, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX585">-h, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX851">-h, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX870">-h, <CODE>msgexec</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX681">-h, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX942">-h, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX638">-h, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX235">-h, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX289">-h, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX988">-h, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX720">-h, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1134">-h, <CODE>ngettext</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX210">-h, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX805">-i, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX536">-i, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX743">-i, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX570">-i, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX836">-i, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX863">-i, <CODE>msgexec</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX645">-i, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX618">-i, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX219">-i, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX273">-i, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX976">-i, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX704">-i, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX185">-i, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX892">-j, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX600">-J, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX952">-j, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX160">-j, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX602">-K, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX168">-k, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX909">-l, <CODE>msgfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX914">-l, <CODE>msgfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX917">-l, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX226">-l, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX963">-l, <CODE>msgunfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX967">-l, <CODE>msgunfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX970">-l, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX154">-L, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX769">-m, <CODE>msgcmp</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX598">-M, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX265">-m, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX208">-M, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX206">-m, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1124">-n, <CODE>gettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX808">-n, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX539">-n, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX746">-n, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX657">-n, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX596">-N, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX267">-N, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX707">-n, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX188">-n, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX784">-o, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX520">-o, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX731">-o, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX562">-o, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX830">-o, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX649">-o, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX904">-o, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX594">-o, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX221">-o, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX258">-o, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX973">-o, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX691">-o, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX149">-o, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX801">-P, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX811">-p, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX529">-P, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX542">-p, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX771">-P, <CODE>msgcmp</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX739">-P, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX749">-p, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX566">-P, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX575">-p, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX832">-P, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX841">-p, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX867">-P, <CODE>msgexec</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX662">-P, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX671">-p, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX920">-P, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX630">-p, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX622">-P, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX223">-P, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX229">-p, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX278">-p, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX269">-P, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX979">-p, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX710">-p, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX697">-P, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX151">-p, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX295">-q, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX907">-r, <CODE>msgfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX912">-r, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX961">-r, <CODE>msgunfmt</CODE> option</A>, <A HREF="gettext_10.html#IDX965">-r, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX817">-s, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX548">-s, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX755">-s, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX581">-s, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX847">-s, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX677">-s, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX284">-s, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX985">-s, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX716">-s, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX196">-s, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX532">-t, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX564">-t, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX604">-T, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX700">-t, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX175">-T, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX527">-u, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX737">-u, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX256">-U, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX695">-u, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1143">-v, <CODE>envsubst</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1147">-V, <CODE>envsubst</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1125">-V, <CODE>gettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX823">-V, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX555">-V, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX776">-V, <CODE>msgcmp</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX762">-V, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX587">-V, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX853">-V, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX872">-V, <CODE>msgexec</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX683">-V, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX944">-V, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX947">-v, <CODE>msgfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX640">-V, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX620">-v, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX237">-V, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX293">-v, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX291">-V, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX992">-v, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX990">-V, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX722">-V, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_15.html#IDX1136">-V, <CODE>ngettext</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX212">-V, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX814">-w, <CODE>msgattrib</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX545">-w, <CODE>msgcat</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX752">-w, <CODE>msgcomm</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX578">-w, <CODE>msgconv</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX844">-w, <CODE>msgen</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX674">-w, <CODE>msgfilter</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX633">-w, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_6.html#IDX232">-w, <CODE>msginit</CODE> option</A>
+<LI><A HREF="gettext_7.html#IDX281">-w, <CODE>msgmerge</CODE> option</A>
+<LI><A HREF="gettext_10.html#IDX982">-w, <CODE>msgunfmt</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX713">-w, <CODE>msguniq</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX193">-w, <CODE>xgettext</CODE> option</A>
+<LI><A HREF="gettext_9.html#IDX608">-X, <CODE>msggrep</CODE> option</A>
+<LI><A HREF="gettext_5.html#IDX162">-x, <CODE>xgettext</CODE> option</A>
</DIR>
</P>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_20.html">previous</A>, <A HREF="gettext_22.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_20.html">previous</A>, <A HREF="gettext_22.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
-<TITLE>GNU gettext utilities - PO Mode Index</TITLE>
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+<TITLE>GNU gettext utilities - Variable Index</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_21.html">previous</A>, <A HREF="gettext_23.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_21.html">previous</A>, <A HREF="gettext_23.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC298" HREF="gettext_toc.html#TOC298">PO Mode Index</A></H1>
+<H1><A NAME="SEC310" HREF="gettext_toc.html#TOC310">Variable Index</A></H1>
<P>
Jump to:
-<A HREF="#emindex_.">.</A>
+<A HREF="#vindex_g">g</A>
-
-<A HREF="#emindex_a">a</A>
+<A HREF="#vindex_l">l</A>
-
-<A HREF="#emindex_c">c</A>
+<A HREF="#vindex_m">m</A>
-
-<A HREF="#emindex_e">e</A>
--
-<A HREF="#emindex_f">f</A>
--
-<A HREF="#emindex_i">i</A>
--
-<A HREF="#emindex_l">l</A>
--
-<A HREF="#emindex_m">m</A>
--
-<A HREF="#emindex_o">o</A>
--
-<A HREF="#emindex_p">p</A>
--
-<A HREF="#emindex_s">s</A>
--
-<A HREF="#emindex_t">t</A>
--
-<A HREF="#emindex_u">u</A>
+<A HREF="#vindex_t">t</A>
<P>
-<H2><A NAME="emindex_.">.</A></H2>
-<DIR>
-<LI><A HREF="gettext_8.html#IDX295"><TT>`.emacs´</TT> customizations</A>
-</DIR>
-<H2><A NAME="emindex_a">a</A></H2>
-<DIR>
-<LI><A HREF="gettext_8.html#IDX472">auxiliary PO file</A>
-</DIR>
-<H2><A NAME="emindex_c">c</A></H2>
-<DIR>
-<LI><A HREF="gettext_8.html#IDX298">commands</A>
-<LI><A HREF="gettext_8.html#IDX402">comment out PO file entry</A>
-<LI><A HREF="gettext_8.html#IDX454">consulting program sources</A>
-<LI><A HREF="gettext_8.html#IDX470">consulting translations to other languages</A>
-<LI><A HREF="gettext_8.html#IDX323">current entry of a PO file</A>
-<LI><A HREF="gettext_8.html#IDX418">cut and paste for translated strings</A>
-</DIR>
-<H2><A NAME="emindex_e">e</A></H2>
-<DIR>
-<LI><A HREF="gettext_8.html#IDX427">editing comments</A>
-<LI><A HREF="gettext_8.html#IDX452">editing multiple entries</A>
-<LI><A HREF="gettext_8.html#IDX404">editing translations</A>
-<LI><A HREF="gettext_4.html#IDX122"><CODE>etags</CODE>, using for marking strings</A>
-<LI><A HREF="gettext_8.html#IDX445">exiting PO subedit</A>
-</DIR>
-<H2><A NAME="emindex_f">f</A></H2>
-<DIR>
-<LI><A HREF="gettext_8.html#IDX457">find source fragment for a PO file entry</A>
-</DIR>
-<H2><A NAME="emindex_i">i</A></H2>
-<DIR>
-<LI><A HREF="gettext_8.html#IDX296">installing PO mode</A>
-</DIR>
-<H2><A NAME="emindex_l">l</A></H2>
-<DIR>
-<LI><A HREF="gettext_8.html#IDX455">looking at the source to aid translation</A>
-</DIR>
-<H2><A NAME="emindex_m">m</A></H2>
-<DIR>
-<LI><A HREF="gettext_4.html#IDX121">marking strings for translation</A>
-<LI><A HREF="gettext_8.html#IDX366">moving by fuzzy entries</A>
-<LI><A HREF="gettext_8.html#IDX391">moving by obsolete entries</A>
-<LI><A HREF="gettext_8.html#IDX355">moving by translated entries</A>
-<LI><A HREF="gettext_8.html#IDX380">moving by untranslated entries</A>
-<LI><A HREF="gettext_8.html#IDX324">moving through a PO file</A>
-</DIR>
-<H2><A NAME="emindex_o">o</A></H2>
-<DIR>
-<LI><A HREF="gettext_8.html#IDX401">obsolete active entry</A>
-</DIR>
-<H2><A NAME="emindex_p">p</A></H2>
+<H2><A NAME="vindex_g">g</A></H2>
<DIR>
-<LI><A HREF="gettext_8.html#IDX453">pending subedits</A>
+<LI><A HREF="gettext_12.html#IDX1049">GETTEXT_LOG_UNTRANSLATED, environment variable</A>
</DIR>
-<H2><A NAME="emindex_s">s</A></H2>
+<H2><A NAME="vindex_l">l</A></H2>
<DIR>
-<LI><A HREF="gettext_8.html#IDX417">starting a string translation</A>
-<LI><A HREF="gettext_8.html#IDX350">string normalization in entries</A>
-<LI><A HREF="gettext_8.html#IDX441">subedit minor mode</A>
+<LI><A HREF="gettext_2.html#IDX45">LANG, environment variable</A>, <A HREF="gettext_11.html#IDX1047">LANG, environment variable</A>
+<LI><A HREF="gettext_11.html#IDX1039">LANGUAGE, environment variable</A>, <A HREF="gettext_13.html#IDX1072">LANGUAGE, environment variable</A>
+<LI><A HREF="gettext_11.html#IDX1040">LC_ALL, environment variable</A>
+<LI><A HREF="gettext_11.html#IDX1044">LC_COLLATE, environment variable</A>
+<LI><A HREF="gettext_11.html#IDX1041">LC_CTYPE, environment variable</A>
+<LI><A HREF="gettext_11.html#IDX1046">LC_MESSAGES, environment variable</A>
+<LI><A HREF="gettext_11.html#IDX1045">LC_MONETARY, environment variable</A>
+<LI><A HREF="gettext_11.html#IDX1042">LC_NUMERIC, environment variable</A>
+<LI><A HREF="gettext_11.html#IDX1043">LC_TIME, environment variable</A>
+<LI><A HREF="gettext_14.html#IDX1103">LINGUAS, environment variable</A>
</DIR>
-<H2><A NAME="emindex_t">t</A></H2>
+<H2><A NAME="vindex_m">m</A></H2>
<DIR>
-<LI><A HREF="gettext_4.html#IDX123"><TT>`TAGS´</TT>, and marking translatable strings</A>
+<LI><A HREF="gettext_9.html#IDX861">MSGEXEC_LOCATION, environment variable</A>
+<LI><A HREF="gettext_9.html#IDX859">MSGEXEC_MSGCTXT, environment variable</A>
+<LI><A HREF="gettext_9.html#IDX860">MSGEXEC_MSGID, environment variable</A>
</DIR>
-<H2><A NAME="emindex_u">u</A></H2>
+<H2><A NAME="vindex_t">t</A></H2>
<DIR>
-<LI><A HREF="gettext_8.html#IDX456">use the source, Luke</A>
-<LI><A HREF="gettext_8.html#IDX425">using obsolete translations to make new entries</A>
-<LI><A HREF="gettext_8.html#IDX486">using translation compendia</A>
+<LI><A HREF="gettext_15.html#IDX1112">TEXTDOMAIN, environment variable</A>
+<LI><A HREF="gettext_15.html#IDX1113">TEXTDOMAINDIR, environment variable</A>
</DIR>
</P>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_21.html">previous</A>, <A HREF="gettext_23.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_21.html">previous</A>, <A HREF="gettext_23.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
-<TITLE>GNU gettext utilities - Autoconf Macro Index</TITLE>
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+<TITLE>GNU gettext utilities - PO Mode Index</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_22.html">previous</A>, <A HREF="gettext_24.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_22.html">previous</A>, <A HREF="gettext_24.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC299" HREF="gettext_toc.html#TOC299">Autoconf Macro Index</A></H1>
+<H1><A NAME="SEC311" HREF="gettext_toc.html#TOC311">PO Mode Index</A></H1>
<P>
Jump to:
-<A HREF="#amindex_a">a</A>
+<A HREF="#emindex_&">&</A>
+-
+<A HREF="#emindex_a">a</A>
+-
+<A HREF="#emindex_c">c</A>
+-
+<A HREF="#emindex_e">e</A>
+-
+<A HREF="#emindex_f">f</A>
+-
+<A HREF="#emindex_i">i</A>
+-
+<A HREF="#emindex_l">l</A>
+-
+<A HREF="#emindex_m">m</A>
+-
+<A HREF="#emindex_o">o</A>
+-
+<A HREF="#emindex_p">p</A>
+-
+<A HREF="#emindex_s">s</A>
+-
+<A HREF="#emindex_u">u</A>
<P>
-<H2><A NAME="amindex_a">a</A></H2>
+<H2><A NAME="emindex_&">&</A></H2>
<DIR>
-<LI><A HREF="gettext_13.html#IDX1057">AM_GNU_GETTEXT</A>
-<LI><A HREF="gettext_13.html#IDX1059">AM_GNU_GETTEXT_VERSION</A>
-<LI><A HREF="gettext_13.html#IDX1061">AM_ICONV</A>
-<LI><A HREF="gettext_13.html#IDX1060">AM_PO_SUBDIRS</A>
+<LI><A HREF="gettext_8.html#IDX304"><TT>‘.emacs’</TT> customizations</A>
+<LI><A HREF="gettext_4.html#IDX129"><TT>‘TAGS’</TT>, and marking translatable strings</A>
+</DIR>
+<H2><A NAME="emindex_a">a</A></H2>
+<DIR>
+<LI><A HREF="gettext_8.html#IDX481">auxiliary PO file</A>
+</DIR>
+<H2><A NAME="emindex_c">c</A></H2>
+<DIR>
+<LI><A HREF="gettext_8.html#IDX307">commands</A>
+<LI><A HREF="gettext_8.html#IDX411">comment out PO file entry</A>
+<LI><A HREF="gettext_8.html#IDX463">consulting program sources</A>
+<LI><A HREF="gettext_8.html#IDX479">consulting translations to other languages</A>
+<LI><A HREF="gettext_8.html#IDX332">current entry of a PO file</A>
+<LI><A HREF="gettext_8.html#IDX427">cut and paste for translated strings</A>
+</DIR>
+<H2><A NAME="emindex_e">e</A></H2>
+<DIR>
+<LI><A HREF="gettext_8.html#IDX436">editing comments</A>
+<LI><A HREF="gettext_8.html#IDX461">editing multiple entries</A>
+<LI><A HREF="gettext_8.html#IDX413">editing translations</A>
+<LI><A HREF="gettext_4.html#IDX128"><CODE>etags</CODE>, using for marking strings</A>
+<LI><A HREF="gettext_8.html#IDX454">exiting PO subedit</A>
+</DIR>
+<H2><A NAME="emindex_f">f</A></H2>
+<DIR>
+<LI><A HREF="gettext_8.html#IDX466">find source fragment for a PO file entry</A>
+</DIR>
+<H2><A NAME="emindex_i">i</A></H2>
+<DIR>
+<LI><A HREF="gettext_8.html#IDX305">installing PO mode</A>
+</DIR>
+<H2><A NAME="emindex_l">l</A></H2>
+<DIR>
+<LI><A HREF="gettext_8.html#IDX464">looking at the source to aid translation</A>
+</DIR>
+<H2><A NAME="emindex_m">m</A></H2>
+<DIR>
+<LI><A HREF="gettext_4.html#IDX127">marking strings for translation</A>
+<LI><A HREF="gettext_8.html#IDX375">moving by fuzzy entries</A>
+<LI><A HREF="gettext_8.html#IDX400">moving by obsolete entries</A>
+<LI><A HREF="gettext_8.html#IDX364">moving by translated entries</A>
+<LI><A HREF="gettext_8.html#IDX389">moving by untranslated entries</A>
+<LI><A HREF="gettext_8.html#IDX333">moving through a PO file</A>
+</DIR>
+<H2><A NAME="emindex_o">o</A></H2>
+<DIR>
+<LI><A HREF="gettext_8.html#IDX410">obsolete active entry</A>
+</DIR>
+<H2><A NAME="emindex_p">p</A></H2>
+<DIR>
+<LI><A HREF="gettext_8.html#IDX462">pending subedits</A>
+</DIR>
+<H2><A NAME="emindex_s">s</A></H2>
+<DIR>
+<LI><A HREF="gettext_8.html#IDX426">starting a string translation</A>
+<LI><A HREF="gettext_8.html#IDX359">string normalization in entries</A>
+<LI><A HREF="gettext_8.html#IDX450">subedit minor mode</A>
+</DIR>
+<H2><A NAME="emindex_u">u</A></H2>
+<DIR>
+<LI><A HREF="gettext_8.html#IDX465">use the source, Luke</A>
+<LI><A HREF="gettext_8.html#IDX434">using obsolete translations to make new entries</A>
+<LI><A HREF="gettext_8.html#IDX495">using translation compendia</A>
</DIR>
</P>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_22.html">previous</A>, <A HREF="gettext_24.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_22.html">previous</A>, <A HREF="gettext_24.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
-<TITLE>GNU gettext utilities - General Index</TITLE>
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+<TITLE>GNU gettext utilities - Autoconf Macro Index</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_23.html">previous</A>,
next, last section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_23.html">previous</A>,
<A HREF="gettext_25.html">next</A>, <A HREF="gettext_25.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC300" HREF="gettext_toc.html#TOC300">General Index</A></H1>
+<H1><A NAME="SEC312" HREF="gettext_toc.html#TOC312">Autoconf Macro Index</A></H1>
<P>
Jump to:
-<A HREF="#cindex__">_</A>
--
-<A HREF="#cindex_a">a</A>
--
-<A HREF="#cindex_b">b</A>
--
-<A HREF="#cindex_c">c</A>
--
-<A HREF="#cindex_d">d</A>
--
-<A HREF="#cindex_e">e</A>
--
-<A HREF="#cindex_f">f</A>
--
-<A HREF="#cindex_g">g</A>
--
-<A HREF="#cindex_h">h</A>
--
-<A HREF="#cindex_i">i</A>
--
-<A HREF="#cindex_j">j</A>
--
-<A HREF="#cindex_k">k</A>
--
-<A HREF="#cindex_l">l</A>
--
-<A HREF="#cindex_m">m</A>
--
-<A HREF="#cindex_n">n</A>
--
-<A HREF="#cindex_o">o</A>
--
-<A HREF="#cindex_p">p</A>
--
-<A HREF="#cindex_q">q</A>
--
-<A HREF="#cindex_r">r</A>
--
-<A HREF="#cindex_s">s</A>
--
-<A HREF="#cindex_t">t</A>
--
-<A HREF="#cindex_u">u</A>
--
-<A HREF="#cindex_v">v</A>
--
-<A HREF="#cindex_w">w</A>
--
-<A HREF="#cindex_x">x</A>
--
-<A HREF="#cindex_y">y</A>
+<A HREF="#amindex_a">a</A>
<P>
-<H2><A NAME="cindex__">_</A></H2>
+<H2><A NAME="amindex_a">a</A></H2>
<DIR>
-<LI><A HREF="gettext_4.html#IDX120"><CODE>_</CODE>, a macro to mark strings for translation</A>
-<LI><A HREF="gettext_11.html#IDX1023"><CODE>_nl_msg_cat_cntr</CODE></A>
-</DIR>
-<H2><A NAME="cindex_a">a</A></H2>
-<DIR>
-<LI><A HREF="gettext_2.html#IDX41"><TT>`ABOUT-NLS´</TT> file</A>
-<LI><A HREF="gettext_13.html#IDX1050"><TT>`acconfig.h´</TT> file</A>
-<LI><A HREF="gettext_8.html#IDX491">accumulating translations</A>
-<LI><A HREF="gettext_13.html#IDX1049"><TT>`aclocal.m4´</TT> file</A>
-<LI><A HREF="gettext_5.html#IDX164">adding keywords, <CODE>xgettext</CODE></A>
-<LI><A HREF="gettext_4.html#IDX110">ambiguities</A>
-<LI><A HREF="gettext_9.html#IDX629">apply a filter to translations</A>
-<LI><A HREF="gettext_9.html#IDX840">apply command to all translations in a catalog</A>
-<LI><A HREF="gettext_15.html#IDX1081">Arabic digits</A>
-<LI><A HREF="gettext_9.html#IDX764">attribute manipulation</A>
-<LI><A HREF="gettext_8.html#IDX365">attribute, fuzzy</A>
-<LI><A HREF="gettext_8.html#IDX364">attributes of a PO file entry</A>
-<LI><A HREF="gettext_9.html#IDX502">attributes, manipulating</A>
-<LI><A HREF="gettext_13.html#IDX1056">autoconf macros for <CODE>gettext</CODE></A>
-<LI><A HREF="gettext_13.html#IDX1064"><CODE>autopoint</CODE> program, usage</A>
-<LI><A HREF="gettext_8.html#IDX471">auxiliary PO file</A>
-<LI><A HREF="gettext_2.html#IDX40">available translations</A>
-<LI><A HREF="gettext_15.html#IDX1142">awk</A>
-</DIR>
-<H2><A NAME="cindex_b">b</A></H2>
-<DIR>
-<LI><A HREF="gettext_7.html#IDX253">backup old file, and <CODE>msgmerge</CODE> program</A>
-<LI><A HREF="gettext_15.html#IDX1127">bash</A>
-<LI><A HREF="gettext_16.html#IDX1168">bibliography</A>
-<LI><A HREF="gettext_1.html#IDX30">big picture</A>
-<LI><A HREF="gettext_11.html#IDX995">bind_textdomain_codeset</A>
-<LI><A HREF="gettext_1.html#IDX4">bug report address</A>
-</DIR>
-<H2><A NAME="cindex_c">c</A></H2>
-<DIR>
-<LI><A HREF="gettext_15.html#IDX1082">C and C-like languages</A>
-<LI><A HREF="gettext_5.html#IDX170">C trigraphs</A>
-<LI><A HREF="gettext_15.html#IDX1140">C#</A>
-<LI><A HREF="gettext_10.html#IDX879">C# mode, and <CODE>msgfmt</CODE> program</A>
-<LI><A HREF="gettext_10.html#IDX938">C# mode, and <CODE>msgunfmt</CODE> program</A>
-<LI><A HREF="gettext_10.html#IDX881">C# resources mode, and <CODE>msgfmt</CODE> program</A>
-<LI><A HREF="gettext_10.html#IDX940">C# resources mode, and <CODE>msgunfmt</CODE> program</A>
-<LI><A HREF="gettext_4.html#IDX118">C#, string concatenation</A>
-<LI><A HREF="gettext_9.html#IDX844">catalog encoding and <CODE>msgexec</CODE> output</A>
-<LI><A HREF="gettext_11.html#IDX985"><CODE>catclose</CODE>, a <CODE>catgets</CODE> function</A>
-<LI><A HREF="gettext_11.html#IDX981"><CODE>catgets</CODE>, X/Open specification</A>
-<LI><A HREF="gettext_11.html#IDX984"><CODE>catgets</CODE>, a <CODE>catgets</CODE> function</A>
-<LI><A HREF="gettext_11.html#IDX983"><CODE>catopen</CODE>, a <CODE>catgets</CODE> function</A>
-<LI><A HREF="gettext_1.html#IDX17">character encoding</A>
-<LI><A HREF="gettext_11.html#IDX993">charset conversion at runtime</A>
-<LI><A HREF="gettext_6.html#IDX233">charset of PO files</A>
-<LI><A HREF="gettext_10.html#IDX908">check format strings</A>
-<LI><A HREF="gettext_9.html#IDX500">checking of translations</A>
-<LI><A HREF="gettext_15.html#IDX1131">clisp</A>
-<LI><A HREF="gettext_15.html#IDX1132">clisp C sources</A>
-<LI><A HREF="gettext_1.html#IDX15">codeset</A>
-<LI><A HREF="gettext_3.html#IDX95">comments in PO files</A>
-<LI><A HREF="gettext_15.html#IDX1129">Common Lisp</A>
-<LI><A HREF="gettext_9.html#IDX749">compare PO files</A>
-<LI><A HREF="gettext_11.html#IDX1010">comparison of interfaces</A>
-<LI><A HREF="gettext_10.html#IDX913">compatibility with X/Open <CODE>msgfmt</CODE></A>
-<LI><A HREF="gettext_8.html#IDX487">compendium</A>
-<LI><A HREF="gettext_8.html#IDX489">compendium, creating</A>
-<LI><A HREF="gettext_9.html#IDX505">concatenate PO files</A>
-<LI><A HREF="gettext_8.html#IDX490">concatenating PO files into a compendium</A>
-<LI><A HREF="gettext_4.html#IDX115">concatenation of strings</A>
-<LI><A HREF="gettext_13.html#IDX1051"><TT>`config.h.in´</TT> file</A>
-<LI><A HREF="gettext_10.html#IDX933">convert binary message catalog into PO file</A>
-<LI><A HREF="gettext_9.html#IDX550">convert translations to a different encoding</A>
-<LI><A HREF="gettext_13.html#IDX1026">converting a package to use <CODE>gettext</CODE></A>
-<LI><A HREF="gettext_18.html#IDX1171">country codes</A>
-<LI><A HREF="gettext_6.html#IDX208">create new PO file</A>
-<LI><A HREF="gettext_6.html#IDX205">creating a new PO file</A>
-<LI><A HREF="gettext_8.html#IDX488">creating compendia</A>
-<LI><A HREF="gettext_1.html#IDX19">currency symbols</A>
-</DIR>
-<H2><A NAME="cindex_d">d</A></H2>
-<DIR>
-<LI><A HREF="gettext_1.html#IDX21">date format</A>
-<LI><A HREF="gettext_11.html#IDX999">dcngettext</A>
-<LI><A HREF="gettext_5.html#IDX174">debugging messages marked as format strings</A>
-<LI><A HREF="gettext_9.html#IDX498">dialect</A>
-<LI><A HREF="gettext_13.html#IDX1054">disabling NLS</A>
-<LI><A HREF="gettext_13.html#IDX1072">distribution tarball</A>
-<LI><A HREF="gettext_11.html#IDX998">dngettext</A>
-<LI><A HREF="gettext_15.html#IDX1115">dollar substitution</A>
-<LI><A HREF="gettext_11.html#IDX990">domain ambiguities</A>
-<LI><A HREF="gettext_9.html#IDX501">duplicate elimination</A>
-<LI><A HREF="gettext_9.html#IDX671">duplicate removal</A>
-</DIR>
-<H2><A NAME="cindex_e">e</A></H2>
-<DIR>
-<LI><A HREF="gettext_8.html#IDX426">editing comments in PO files</A>
-<LI><A HREF="gettext_8.html#IDX289">Editing PO Files</A>
-<LI><A HREF="gettext_8.html#IDX403">editing translations</A>
-<LI><A HREF="gettext_15.html#IDX1133">Emacs Lisp</A>
-<LI><A HREF="gettext_8.html#IDX292">Emacs PO Mode</A>
-<LI><A HREF="gettext_1.html#IDX16">encoding</A>
-<LI><A HREF="gettext_9.html#IDX497">encoding conversion</A>
-<LI><A HREF="gettext_11.html#IDX994">encoding conversion at runtime</A>
-<LI><A HREF="gettext_6.html#IDX237">encoding for your language</A>
-<LI><A HREF="gettext_6.html#IDX235">encoding list</A>
-<LI><A HREF="gettext_6.html#IDX232">encoding of PO files</A>
-<LI><A HREF="gettext_15.html#IDX1116">environment variables</A>
-<LI><A HREF="gettext_15.html#IDX1113"><CODE>envsubst</CODE> program, usage</A>
-<LI><A HREF="gettext_15.html#IDX1123"><CODE>eval_gettext</CODE> function, usage</A>
-<LI><A HREF="gettext_15.html#IDX1125"><CODE>eval_ngettext</CODE> function, usage</A>
-<LI><A HREF="gettext_1.html#IDX38">evolution of packages</A>
-<LI><A HREF="gettext_8.html#IDX492">extracting parts of a PO file into a compendium</A>
-</DIR>
-<H2><A NAME="cindex_f">f</A></H2>
-<DIR>
-<LI><A HREF="gettext_10.html#IDX977">file format, <TT>`.mo´</TT></A>
-<LI><A HREF="gettext_3.html#IDX47">file format, <TT>`.po´</TT></A>
-<LI><A HREF="gettext_1.html#IDX28">files, <TT>`.po´</TT> and <TT>`.mo´</TT></A>
-<LI><A HREF="gettext_1.html#IDX37">files, <TT>`.pot´</TT></A>
-<LI><A HREF="gettext_9.html#IDX763">filter messages according to attributes</A>
-<LI><A HREF="gettext_9.html#IDX709">find common messages</A>
-<LI><A HREF="gettext_10.html#IDX920">force use of fuzzy entries</A>
-<LI><A HREF="gettext_4.html#IDX130">format strings</A>
-<LI><A HREF="gettext_15.html#IDX1145">Free Pascal</A>
-<LI><A HREF="gettext_5.html#IDX166">function attribute, __format__</A>
-<LI><A HREF="gettext_5.html#IDX167">function attribute, __format_arg__</A>
-<LI><A HREF="gettext_8.html#IDX363">fuzzy entries</A>
-</DIR>
-<H2><A NAME="cindex_g">g</A></H2>
-<DIR>
-<LI><A HREF="gettext_15.html#IDX1143">gawk</A>
-<LI><A HREF="gettext_15.html#IDX1164">GCC-source</A>
-<LI><A HREF="gettext_10.html#IDX871">generate binary message catalog from PO file</A>
-<LI><A HREF="gettext_9.html#IDX810">generate translation catalog in English</A>
-<LI><A HREF="gettext_13.html#IDX1041"><CODE>gettext</CODE> files</A>
-<LI><A HREF="gettext_8.html#IDX294"><CODE>gettext</CODE> installation</A>
-<LI><A HREF="gettext_11.html#IDX988"><CODE>gettext</CODE> interface</A>
-<LI><A HREF="gettext_15.html#IDX1090"><CODE>gettext</CODE> program, usage</A>
-<LI><A HREF="gettext_11.html#IDX987"><CODE>gettext</CODE>, a programmer's view</A>
-<LI><A HREF="gettext_13.html#IDX1052"><TT>`gettext.h´</TT> file</A>
-<LI><A HREF="gettext_11.html#IDX1009"><CODE>gettext</CODE> vs <CODE>catgets</CODE></A>
-<LI><A HREF="gettext_13.html#IDX1030"><CODE>gettextize</CODE> program, usage</A>
-<LI><A HREF="gettext_8.html#IDX291">GNOME PO file editor</A>
-<LI><A HREF="gettext_11.html#IDX1004">GUI programs</A>
-<LI><A HREF="gettext_15.html#IDX1136">guile</A>
-</DIR>
-<H2><A NAME="cindex_h">h</A></H2>
-<DIR>
-<LI><A HREF="gettext_10.html#IDX979">hash table, inside MO files</A>
-<LI><A HREF="gettext_1.html#IDX2">he, she, and they</A>
-<LI><A HREF="gettext_6.html#IDX230">header entry of a PO file</A>
-<LI><A HREF="gettext_4.html#IDX113">help option</A>
-<LI><A HREF="gettext_16.html#IDX1166">history of GNU <CODE>gettext</CODE></A>
-</DIR>
-<H2><A NAME="cindex_i">i</A></H2>
-<DIR>
-<LI><A HREF="gettext_1.html#IDX6">i18n</A>
-<LI><A HREF="gettext_8.html#IDX352">importing PO files</A>
-<LI><A HREF="gettext_1.html#IDX33">include file <TT>`libintl.h´</TT></A>, <A HREF="gettext_4.html#IDX97">include file <TT>`libintl.h´</TT></A>, <A HREF="gettext_11.html#IDX1011">include file <TT>`libintl.h´</TT></A>, <A HREF="gettext_13.html#IDX1055">include file <TT>`libintl.h´</TT></A>
-<LI><A HREF="gettext_4.html#IDX98">initialization</A>
-<LI><A HREF="gettext_6.html#IDX209">initialize new PO file</A>
-<LI><A HREF="gettext_8.html#IDX493">initialize translations from a compendium</A>
-<LI><A HREF="gettext_8.html#IDX293">installing <CODE>gettext</CODE></A>
-<LI><A HREF="gettext_11.html#IDX982">interface to <CODE>catgets</CODE></A>
-<LI><A HREF="gettext_1.html#IDX8">internationalization</A>
-<LI><A HREF="gettext_4.html#IDX116"><CODE>inttypes.h</CODE></A>
-<LI><A HREF="gettext_18.html#IDX1172">ISO 3166</A>
-<LI><A HREF="gettext_17.html#IDX1170">ISO 639</A>
-</DIR>
-<H2><A NAME="cindex_j">j</A></H2>
-<DIR>
-<LI><A HREF="gettext_15.html#IDX1138">Java</A>
-<LI><A HREF="gettext_10.html#IDX876">Java mode, and <CODE>msgfmt</CODE> program</A>
-<LI><A HREF="gettext_10.html#IDX936">Java mode, and <CODE>msgunfmt</CODE> program</A>
-<LI><A HREF="gettext_4.html#IDX117">Java, string concatenation</A>
-</DIR>
-<H2><A NAME="cindex_k">k</A></H2>
-<DIR>
-<LI><A HREF="gettext_8.html#IDX290">KDE PO file editor</A>
-<LI><A HREF="gettext_10.html#IDX915">keyboard accelerator checking</A>
-</DIR>
-<H2><A NAME="cindex_l">l</A></H2>
-<DIR>
-<LI><A HREF="gettext_1.html#IDX7">l10n</A>
-<LI><A HREF="gettext_17.html#IDX1169">language codes</A>
-<LI><A HREF="gettext_2.html#IDX44">language selection</A>
-<LI><A HREF="gettext_11.html#IDX1013">language selection at runtime</A>
-<LI><A HREF="gettext_11.html#IDX991">large package</A>
-<LI><A HREF="gettext_13.html#IDX1062"><CODE>libiconv</CODE> library</A>
-<LI><A HREF="gettext_15.html#IDX1141"><CODE>libintl</CODE> for C#</A>
-<LI><A HREF="gettext_15.html#IDX1139"><CODE>libintl</CODE> for Java</A>
-<LI><A HREF="gettext_13.html#IDX1058"><CODE>libintl</CODE> library</A>
-<LI><A HREF="gettext_15.html#IDX1134"><CODE>librep</CODE> Lisp</A>
-<LI><A HREF="gettext_13.html#IDX1043"><TT>`LINGUAS´</TT> file</A>
-<LI><A HREF="gettext_1.html#IDX34">link with <TT>`libintl´</TT></A>
-<LI><A HREF="gettext_1.html#IDX27">Linux</A>, <A HREF="gettext_1.html#IDX35">Linux</A>, <A HREF="gettext_6.html#IDX236">Linux</A>
-<LI><A HREF="gettext_15.html#IDX1130">Lisp</A>
-<LI><A HREF="gettext_6.html#IDX231">list of translation teams, where to find</A>
-<LI><A HREF="gettext_4.html#IDX99">locale facet, LC_ALL</A>
-<LI><A HREF="gettext_4.html#IDX102">locale facet, LC_COLLATE</A>
-<LI><A HREF="gettext_1.html#IDX18">locale facet, LC_CTYPE</A>, <A HREF="gettext_4.html#IDX100">locale facet, LC_CTYPE</A>, <A HREF="gettext_4.html#IDX101">locale facet, LC_CTYPE</A>
-<LI><A HREF="gettext_1.html#IDX26">locale facet, LC_MESSAGES</A>, <A HREF="gettext_4.html#IDX106">locale facet, LC_MESSAGES</A>
-<LI><A HREF="gettext_1.html#IDX20">locale facet, LC_MONETARY</A>, <A HREF="gettext_4.html#IDX103">locale facet, LC_MONETARY</A>
-<LI><A HREF="gettext_1.html#IDX24">locale facet, LC_NUMERIC</A>, <A HREF="gettext_4.html#IDX104">locale facet, LC_NUMERIC</A>
-<LI><A HREF="gettext_4.html#IDX107">locale facet, LC_RESPONSES</A>
-<LI><A HREF="gettext_1.html#IDX22">locale facet, LC_TIME</A>, <A HREF="gettext_4.html#IDX105">locale facet, LC_TIME</A>
-<LI><A HREF="gettext_1.html#IDX14">locale facets</A>
-<LI><A HREF="gettext_6.html#IDX234"><CODE>locale</CODE> program</A>
-<LI><A HREF="gettext_1.html#IDX9">localization</A>
-<LI><A HREF="gettext_15.html#IDX1091">lookup message translation</A>, <A HREF="gettext_15.html#IDX1124">lookup message translation</A>
-<LI><A HREF="gettext_15.html#IDX1103">lookup plural message translation</A>, <A HREF="gettext_15.html#IDX1126">lookup plural message translation</A>
-</DIR>
-<H2><A NAME="cindex_m">m</A></H2>
-<DIR>
-<LI><A HREF="gettext_10.html#IDX978">magic signature of MO files</A>
-<LI><A HREF="gettext_13.html#IDX1044"><TT>`Makevars´</TT> file</A>
-<LI><A HREF="gettext_9.html#IDX495">manipulating PO files</A>
-<LI><A HREF="gettext_15.html#IDX1153">marking Perl sources</A>
-<LI><A HREF="gettext_4.html#IDX133">marking string initializers</A>
-<LI><A HREF="gettext_4.html#IDX119">marking strings that require translation</A>
-<LI><A HREF="gettext_4.html#IDX108">marking strings, preparations</A>
-<LI><A HREF="gettext_1.html#IDX32">marking translatable strings</A>
-<LI><A HREF="gettext_11.html#IDX1006">menu entries</A>
-<LI><A HREF="gettext_10.html#IDX916">menu, keyboard accelerator support</A>
-<LI><A HREF="gettext_9.html#IDX506">merge PO files</A>
-<LI><A HREF="gettext_9.html#IDX496">merging two PO files</A>
-<LI><A HREF="gettext_11.html#IDX992">message catalog files location</A>
-<LI><A HREF="gettext_1.html#IDX25">messages</A>
-<LI><A HREF="gettext_13.html#IDX1027">migration from earlier versions of <CODE>gettext</CODE></A>
-<LI><A HREF="gettext_13.html#IDX1048"><TT>`mkinstalldirs´</TT> file</A>
-<LI><A HREF="gettext_10.html#IDX917">mnemonics of menu entries</A>
-<LI><A HREF="gettext_10.html#IDX976">MO file's format</A>
-<LI><A HREF="gettext_9.html#IDX775">modify message attrributes</A>
-<LI><A HREF="gettext_9.html#IDX762"><CODE>msgattrib</CODE> program, usage</A>
-<LI><A HREF="gettext_9.html#IDX504"><CODE>msgcat</CODE> program, usage</A>
-<LI><A HREF="gettext_9.html#IDX748"><CODE>msgcmp</CODE> program, usage</A>
-<LI><A HREF="gettext_9.html#IDX708"><CODE>msgcomm</CODE> program, usage</A>
-<LI><A HREF="gettext_9.html#IDX549"><CODE>msgconv</CODE> program, usage</A>
-<LI><A HREF="gettext_9.html#IDX809"><CODE>msgen</CODE> program, usage</A>
-<LI><A HREF="gettext_9.html#IDX839"><CODE>msgexec</CODE> program, usage</A>
-<LI><A HREF="gettext_9.html#IDX636"><CODE>msgfilter</CODE> filter and catalog encoding</A>
-<LI><A HREF="gettext_9.html#IDX628"><CODE>msgfilter</CODE> program, usage</A>
-<LI><A HREF="gettext_10.html#IDX870"><CODE>msgfmt</CODE> program, usage</A>
-<LI><A HREF="gettext_9.html#IDX581"><CODE>msggrep</CODE> program, usage</A>
-<LI><A HREF="gettext_6.html#IDX207"><CODE>msginit</CODE> program, usage</A>
-<LI><A HREF="gettext_7.html#IDX242"><CODE>msgmerge</CODE> program, usage</A>
-<LI><A HREF="gettext_10.html#IDX932"><CODE>msgunfmt</CODE> program, usage</A>
-<LI><A HREF="gettext_9.html#IDX669"><CODE>msguniq</CODE> program, usage</A>
-<LI><A HREF="gettext_8.html#IDX353">multi-line strings</A>
-</DIR>
-<H2><A NAME="cindex_n">n</A></H2>
-<DIR>
-<LI><A HREF="gettext_11.html#IDX1012"><CODE>N_</CODE>, a convenience macro</A>
-<LI><A HREF="gettext_1.html#IDX11">Native Language Support</A>
-<LI><A HREF="gettext_1.html#IDX12">Natural Language Support</A>
-<LI><A HREF="gettext_3.html#IDX94">newlines in PO files</A>
-<LI><A HREF="gettext_11.html#IDX997">ngettext</A>
-<LI><A HREF="gettext_15.html#IDX1102"><CODE>ngettext</CODE> program, usage</A>
-<LI><A HREF="gettext_1.html#IDX10">NLS</A>
-<LI><A HREF="gettext_1.html#IDX23">number format</A>
-</DIR>
-<H2><A NAME="cindex_o">o</A></H2>
-<DIR>
-<LI><A HREF="gettext_15.html#IDX1146">Object Pascal</A>
-<LI><A HREF="gettext_8.html#IDX390">obsolete entries</A>
-<LI><A HREF="gettext_11.html#IDX1008">optimization of <CODE>gettext</CODE> functions</A>
-<LI><A HREF="gettext_9.html#IDX499">orthography</A>
-<LI><A HREF="gettext_15.html#IDX1080">outdigits</A>
-<LI><A HREF="gettext_5.html#IDX147">output to stdout, <CODE>xgettext</CODE></A>
-<LI><A HREF="gettext_1.html#IDX29">overview of <CODE>gettext</CODE></A>
-</DIR>
-<H2><A NAME="cindex_p">p</A></H2>
-<DIR>
-<LI><A HREF="gettext_13.html#IDX1047">package and version declaration in <TT>`configure.in´</TT></A>
-<LI><A HREF="gettext_14.html#IDX1075">package build and installation options</A>
-<LI><A HREF="gettext_14.html#IDX1074">package distributor's view of <CODE>gettext</CODE></A>
-<LI><A HREF="gettext_14.html#IDX1073">package installer's view of <CODE>gettext</CODE></A>
-<LI><A HREF="gettext_13.html#IDX1025">package maintainer's view of <CODE>gettext</CODE></A>
-<LI><A HREF="gettext_4.html#IDX112">paragraphs</A>
-<LI><A HREF="gettext_15.html#IDX1144">Pascal</A>
-<LI><A HREF="gettext_15.html#IDX1152">Perl</A>
-<LI><A HREF="gettext_15.html#IDX1154">Perl default keywords</A>
-<LI><A HREF="gettext_15.html#IDX1157">Perl invalid string interpolation</A>
-<LI><A HREF="gettext_15.html#IDX1160">Perl long lines</A>
-<LI><A HREF="gettext_15.html#IDX1159">Perl parentheses</A>
-<LI><A HREF="gettext_15.html#IDX1161">Perl pitfalls</A>
-<LI><A HREF="gettext_15.html#IDX1156">Perl quote-like expressions</A>
-<LI><A HREF="gettext_15.html#IDX1155">Perl special keywords for hash-lookups</A>
-<LI><A HREF="gettext_15.html#IDX1158">Perl valid string interpolation</A>
-<LI><A HREF="gettext_15.html#IDX1162">PHP</A>
-<LI><A HREF="gettext_15.html#IDX1163">Pike</A>
-<LI><A HREF="gettext_11.html#IDX1003">plural form formulas</A>
-<LI><A HREF="gettext_11.html#IDX996">plural forms</A>
-<LI><A HREF="gettext_10.html#IDX980">plural forms, in MO files</A>
-<LI><A HREF="gettext_3.html#IDX92">plural forms, in PO files</A>
-<LI><A HREF="gettext_3.html#IDX46">PO files' format</A>
-<LI><A HREF="gettext_8.html#IDX297">PO mode (Emacs) commands</A>
-<LI><A HREF="gettext_5.html#IDX134">PO template file</A>
-<LI><A HREF="gettext_9.html#IDX861">po_file_domains</A>
-<LI><A HREF="gettext_9.html#IDX860">po_file_free</A>
-<LI><A HREF="gettext_9.html#IDX859">po_file_read</A>
-<LI><A HREF="gettext_9.html#IDX862">po_message_iterator</A>
-<LI><A HREF="gettext_9.html#IDX863">po_message_iterator_free</A>
-<LI><A HREF="gettext_9.html#IDX865">po_message_msgid</A>
-<LI><A HREF="gettext_9.html#IDX866">po_message_msgid_plural</A>
-<LI><A HREF="gettext_9.html#IDX867">po_message_msgstr</A>
-<LI><A HREF="gettext_9.html#IDX868">po_message_msgstr_plural</A>
-<LI><A HREF="gettext_9.html#IDX864">po_next_message</A>
-<LI><A HREF="gettext_9.html#IDX637">portability problems with <CODE>sed</CODE></A>
-<LI><A HREF="gettext_13.html#IDX1042"><TT>`POTFILES.in´</TT> file</A>
-<LI><A HREF="gettext_4.html#IDX96">preparing programs for translation</A>
-<LI><A HREF="gettext_15.html#IDX1088">preparing shell scripts for translation</A>
-<LI><A HREF="gettext_11.html#IDX986">problems with <CODE>catgets</CODE> interface</A>
-<LI><A HREF="gettext_15.html#IDX1078">programming languages</A>
-<LI><A HREF="gettext_15.html#IDX1128">Python</A>
-</DIR>
-<H2><A NAME="cindex_q">q</A></H2>
-<DIR>
-<LI><A HREF="gettext_5.html#IDX172">Qt format strings</A>
-<LI><A HREF="gettext_10.html#IDX885">Qt mode, and <CODE>msgfmt</CODE> program</A>
-<LI><A HREF="gettext_6.html#IDX239">quotation marks</A>, <A HREF="gettext_13.html#IDX1045">quotation marks</A>
-<LI><A HREF="gettext_6.html#IDX238">quote characters, use in PO files</A>
-</DIR>
-<H2><A NAME="cindex_r">r</A></H2>
-<DIR>
-<LI><A HREF="gettext_16.html#IDX1167">related reading</A>
-<LI><A HREF="gettext_13.html#IDX1071">release</A>
-<LI><A HREF="gettext_15.html#IDX1165">RST</A>
-</DIR>
-<H2><A NAME="cindex_s">s</A></H2>
-<DIR>
-<LI><A HREF="gettext_15.html#IDX1135">Scheme</A>
-<LI><A HREF="gettext_15.html#IDX1079">scripting languages</A>
-<LI><A HREF="gettext_9.html#IDX582">search messages in a catalog</A>
-<LI><A HREF="gettext_2.html#IDX43">selecting message language</A>
-<LI><A HREF="gettext_4.html#IDX111">sentences</A>
-<LI><A HREF="gettext_14.html#IDX1076">setting up <CODE>gettext</CODE> at build time</A>
-<LI><A HREF="gettext_2.html#IDX42">setting up <CODE>gettext</CODE> at run time</A>
-<LI><A HREF="gettext_11.html#IDX989">several domains</A>
-<LI><A HREF="gettext_1.html#IDX1">sex</A>
-<LI><A HREF="gettext_11.html#IDX1007">sgettext</A>
-<LI><A HREF="gettext_1.html#IDX3">she, he, and they</A>
-<LI><A HREF="gettext_15.html#IDX1114">shell format string</A>
-<LI><A HREF="gettext_15.html#IDX1083">shell scripts</A>
-<LI><A HREF="gettext_15.html#IDX1137">Smalltalk</A>
-<LI><A HREF="gettext_9.html#IDX541">sorting <CODE>msgcat</CODE> output</A>
-<LI><A HREF="gettext_7.html#IDX277">sorting <CODE>msgmerge</CODE> output</A>
-<LI><A HREF="gettext_10.html#IDX969">sorting <CODE>msgunfmt</CODE> output</A>
-<LI><A HREF="gettext_5.html#IDX189">sorting output of <CODE>xgettext</CODE></A>
-<LI><A HREF="gettext_11.html#IDX1000">specifying plural form in a PO file</A>
-<LI><A HREF="gettext_9.html#IDX513">standard output, and <CODE>msgcat</CODE></A>
-<LI><A HREF="gettext_7.html#IDX251">standard output, and <CODE>msgmerge</CODE> program</A>
-<LI><A HREF="gettext_4.html#IDX114">string concatenation</A>
-<LI><A HREF="gettext_8.html#IDX349">string normalization in entries</A>
-<LI><A HREF="gettext_4.html#IDX109">style</A>
-<LI><A HREF="gettext_5.html#IDX150">supported languages, <CODE>xgettext</CODE></A>
-</DIR>
-<H2><A NAME="cindex_t">t</A></H2>
-<DIR>
-<LI><A HREF="gettext_15.html#IDX1150">Tcl</A>
-<LI><A HREF="gettext_10.html#IDX883">Tcl mode, and <CODE>msgfmt</CODE> program</A>
-<LI><A HREF="gettext_10.html#IDX942">Tcl mode, and <CODE>msgunfmt</CODE> program</A>
-<LI><A HREF="gettext_1.html#IDX36">template PO file</A>
-<LI><A HREF="gettext_5.html#IDX193">testing <TT>`.po´</TT> files for equivalence</A>
-<LI><A HREF="gettext_15.html#IDX1151">Tk's scripting language</A>
-<LI><A HREF="gettext_8.html#IDX354">translated entries</A>
-<LI><A HREF="gettext_11.html#IDX1005">translating menu entries</A>
-<LI><A HREF="gettext_1.html#IDX13">translation aspects</A>
-<LI><A HREF="gettext_2.html#IDX39">Translation Matrix</A>
-<LI><A HREF="gettext_1.html#IDX5">Translation Project</A>
-<LI><A HREF="gettext_13.html#IDX1053">turning off NLS support</A>
-<LI><A HREF="gettext_1.html#IDX31">tutorial of <CODE>gettext</CODE> usage</A>
-</DIR>
-<H2><A NAME="cindex_u">u</A></H2>
-<DIR>
-<LI><A HREF="gettext_9.html#IDX670">unify duplicate translations</A>
-<LI><A HREF="gettext_8.html#IDX379">untranslated entries</A>
-<LI><A HREF="gettext_8.html#IDX494">update translations from a compendium</A>
-<LI><A HREF="gettext_13.html#IDX1028">upgrading to new versions of <CODE>gettext</CODE></A>
-</DIR>
-<H2><A NAME="cindex_v">v</A></H2>
-<DIR>
-<LI><A HREF="gettext_7.html#IDX255">version control for backup files, <CODE>msgmerge</CODE></A>
-</DIR>
-<H2><A NAME="cindex_w">w</A></H2>
-<DIR>
-<LI><A HREF="gettext_15.html#IDX1147"><CODE>wxWindows</CODE> library</A>
-</DIR>
-<H2><A NAME="cindex_x">x</A></H2>
-<DIR>
-<LI><A HREF="gettext_9.html#IDX841"><CODE>xargs</CODE>, and output from <CODE>msgexec</CODE></A>
-<LI><A HREF="gettext_5.html#IDX136"><CODE>xgettext</CODE> program, usage</A>
-<LI><A HREF="gettext_6.html#IDX240"><CODE>xmodmap</CODE> program, and typing quotation marks</A>
-</DIR>
-<H2><A NAME="cindex_y">y</A></H2>
-<DIR>
-<LI><A HREF="gettext_15.html#IDX1149">YaST2 scripting language</A>
-<LI><A HREF="gettext_15.html#IDX1148">YCP</A>
+<LI><A HREF="gettext_13.html#IDX1083">AM_GNU_GETTEXT</A>
+<LI><A HREF="gettext_13.html#IDX1085">AM_GNU_GETTEXT_VERSION</A>
+<LI><A HREF="gettext_13.html#IDX1087">AM_ICONV</A>
+<LI><A HREF="gettext_13.html#IDX1086">AM_PO_SUBDIRS</A>
</DIR>
</P>
-
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_23.html">previous</A>,
next, last section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_23.html">previous</A>,
<A HREF="gettext_25.html">next</A>, <A HREF="gettext_25.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
--- /dev/null
+<HTML>
+<HEAD>
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+<TITLE>GNU gettext utilities - General Index</TITLE>
+</HEAD>
+<BODY>
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_24.html">previous</A>, next, last section, <A HREF="gettext_toc.html">table of contents</A>.
+<P><HR><P>
+
+
+<H1><A NAME="SEC313" HREF="gettext_toc.html#TOC313">General Index</A></H1>
+
+<P>
+Jump to:
+<A HREF="#cindex_&">&</A>
+-
+<A HREF="#cindex__">_</A>
+-
+<A HREF="#cindex_a">a</A>
+-
+<A HREF="#cindex_b">b</A>
+-
+<A HREF="#cindex_c">c</A>
+-
+<A HREF="#cindex_d">d</A>
+-
+<A HREF="#cindex_e">e</A>
+-
+<A HREF="#cindex_f">f</A>
+-
+<A HREF="#cindex_g">g</A>
+-
+<A HREF="#cindex_h">h</A>
+-
+<A HREF="#cindex_i">i</A>
+-
+<A HREF="#cindex_j">j</A>
+-
+<A HREF="#cindex_k">k</A>
+-
+<A HREF="#cindex_l">l</A>
+-
+<A HREF="#cindex_m">m</A>
+-
+<A HREF="#cindex_n">n</A>
+-
+<A HREF="#cindex_o">o</A>
+-
+<A HREF="#cindex_p">p</A>
+-
+<A HREF="#cindex_q">q</A>
+-
+<A HREF="#cindex_r">r</A>
+-
+<A HREF="#cindex_s">s</A>
+-
+<A HREF="#cindex_t">t</A>
+-
+<A HREF="#cindex_u">u</A>
+-
+<A HREF="#cindex_v">v</A>
+-
+<A HREF="#cindex_w">w</A>
+-
+<A HREF="#cindex_x">x</A>
+-
+<A HREF="#cindex_y">y</A>
+<P>
+<H2><A NAME="cindex_&">&</A></H2>
+<DIR>
+<LI><A HREF="gettext_2.html#IDX41"><TT>‘ABOUT-NLS’</TT> file</A>
+<LI><A HREF="gettext_13.html#IDX1076"><TT>‘acconfig.h’</TT> file</A>
+<LI><A HREF="gettext_13.html#IDX1075"><TT>‘aclocal.m4’</TT> file</A>
+<LI><A HREF="gettext_13.html#IDX1077"><TT>‘config.h.in’</TT> file</A>
+<LI><A HREF="gettext_13.html#IDX1078"><TT>‘gettext.h’</TT> file</A>
+<LI><A HREF="gettext_13.html#IDX1068"><TT>‘LINGUAS’</TT> file</A>
+<LI><A HREF="gettext_13.html#IDX1070"><TT>‘Makefile.in.in’</TT> extensions</A>
+<LI><A HREF="gettext_13.html#IDX1069"><TT>‘Makevars’</TT> file</A>
+<LI><A HREF="gettext_13.html#IDX1074"><TT>‘mkinstalldirs’</TT> file</A>
+<LI><A HREF="gettext_13.html#IDX1067"><TT>‘POTFILES.in’</TT> file</A>
+</DIR>
+<H2><A NAME="cindex__">_</A></H2>
+<DIR>
+<LI><A HREF="gettext_4.html#IDX126"><CODE>_</CODE>, a macro to mark strings for translation</A>
+<LI><A HREF="gettext_11.html#IDX1048"><CODE>_nl_msg_cat_cntr</CODE></A>
+</DIR>
+<H2><A NAME="cindex_a">a</A></H2>
+<DIR>
+<LI><A HREF="gettext_8.html#IDX500">accumulating translations</A>
+<LI><A HREF="gettext_5.html#IDX170">adding keywords, <CODE>xgettext</CODE></A>
+<LI><A HREF="gettext_4.html#IDX116">ambiguities</A>
+<LI><A HREF="gettext_9.html#IDX644">apply a filter to translations</A>
+<LI><A HREF="gettext_9.html#IDX857">apply command to all translations in a catalog</A>
+<LI><A HREF="gettext_15.html#IDX1107">Arabic digits</A>
+<LI><A HREF="gettext_9.html#IDX781">attribute manipulation</A>
+<LI><A HREF="gettext_8.html#IDX374">attribute, fuzzy</A>
+<LI><A HREF="gettext_8.html#IDX373">attributes of a PO file entry</A>
+<LI><A HREF="gettext_9.html#IDX511">attributes, manipulating</A>
+<LI><A HREF="gettext_13.html#IDX1082">autoconf macros for <CODE>gettext</CODE></A>
+<LI><A HREF="gettext_13.html#IDX1090"><CODE>autopoint</CODE> program, usage</A>
+<LI><A HREF="gettext_8.html#IDX480">auxiliary PO file</A>
+<LI><A HREF="gettext_2.html#IDX40">available translations</A>
+<LI><A HREF="gettext_15.html#IDX1168">awk</A>
+</DIR>
+<H2><A NAME="cindex_b">b</A></H2>
+<DIR>
+<LI><A HREF="gettext_7.html#IDX262">backup old file, and <CODE>msgmerge</CODE> program</A>
+<LI><A HREF="gettext_15.html#IDX1153">bash</A>
+<LI><A HREF="gettext_16.html#IDX1194">bibliography</A>
+<LI><A HREF="gettext_1.html#IDX30">big picture</A>
+<LI><A HREF="gettext_11.html#IDX1014">bind_textdomain_codeset</A>
+<LI><A HREF="gettext_5.html#IDX181">Boost format strings</A>
+<LI><A HREF="gettext_1.html#IDX4">bug report address</A>
+</DIR>
+<H2><A NAME="cindex_c">c</A></H2>
+<DIR>
+<LI><A HREF="gettext_15.html#IDX1108">C and C-like languages</A>
+<LI><A HREF="gettext_5.html#IDX177">C trigraphs</A>
+<LI><A HREF="gettext_15.html#IDX1166">C#</A>
+<LI><A HREF="gettext_10.html#IDX897">C# mode, and <CODE>msgfmt</CODE> program</A>
+<LI><A HREF="gettext_10.html#IDX956">C# mode, and <CODE>msgunfmt</CODE> program</A>
+<LI><A HREF="gettext_10.html#IDX899">C# resources mode, and <CODE>msgfmt</CODE> program</A>
+<LI><A HREF="gettext_10.html#IDX958">C# resources mode, and <CODE>msgunfmt</CODE> program</A>
+<LI><A HREF="gettext_4.html#IDX124">C#, string concatenation</A>
+<LI><A HREF="gettext_9.html#IDX862">catalog encoding and <CODE>msgexec</CODE> output</A>
+<LI><A HREF="gettext_11.html#IDX1004"><CODE>catclose</CODE>, a <CODE>catgets</CODE> function</A>
+<LI><A HREF="gettext_11.html#IDX1000"><CODE>catgets</CODE>, X/Open specification</A>
+<LI><A HREF="gettext_11.html#IDX1003"><CODE>catgets</CODE>, a <CODE>catgets</CODE> function</A>
+<LI><A HREF="gettext_11.html#IDX1002"><CODE>catopen</CODE>, a <CODE>catgets</CODE> function</A>
+<LI><A HREF="gettext_1.html#IDX17">character encoding</A>
+<LI><A HREF="gettext_11.html#IDX1012">charset conversion at runtime</A>
+<LI><A HREF="gettext_6.html#IDX242">charset of PO files</A>
+<LI><A HREF="gettext_10.html#IDX926">check format strings</A>
+<LI><A HREF="gettext_9.html#IDX509">checking of translations</A>
+<LI><A HREF="gettext_15.html#IDX1157">clisp</A>
+<LI><A HREF="gettext_15.html#IDX1158">clisp C sources</A>
+<LI><A HREF="gettext_1.html#IDX15">codeset</A>
+<LI><A HREF="gettext_3.html#IDX101">comments in PO files</A>
+<LI><A HREF="gettext_3.html#IDX49">comments, automatic</A>
+<LI><A HREF="gettext_3.html#IDX50">comments, extracted</A>
+<LI><A HREF="gettext_3.html#IDX48">comments, translator</A>
+<LI><A HREF="gettext_15.html#IDX1155">Common Lisp</A>
+<LI><A HREF="gettext_9.html#IDX766">compare PO files</A>
+<LI><A HREF="gettext_11.html#IDX1035">comparison of interfaces</A>
+<LI><A HREF="gettext_10.html#IDX931">compatibility with X/Open <CODE>msgfmt</CODE></A>
+<LI><A HREF="gettext_8.html#IDX496">compendium</A>
+<LI><A HREF="gettext_8.html#IDX498">compendium, creating</A>
+<LI><A HREF="gettext_9.html#IDX514">concatenate PO files</A>
+<LI><A HREF="gettext_8.html#IDX499">concatenating PO files into a compendium</A>
+<LI><A HREF="gettext_4.html#IDX121">concatenation of strings</A>
+<LI><A HREF="gettext_11.html#IDX1015">context</A>
+<LI><A HREF="gettext_5.html#IDX171">context, argument specification in <CODE>xgettext</CODE></A>
+<LI><A HREF="gettext_10.html#IDX998">context, in MO files</A>
+<LI><A HREF="gettext_3.html#IDX97">context, in PO files</A>
+<LI><A HREF="gettext_10.html#IDX951">convert binary message catalog into PO file</A>
+<LI><A HREF="gettext_9.html#IDX559">convert translations to a different encoding</A>
+<LI><A HREF="gettext_13.html#IDX1051">converting a package to use <CODE>gettext</CODE></A>
+<LI><A HREF="gettext_18.html#IDX1197">country codes</A>
+<LI><A HREF="gettext_6.html#IDX217">create new PO file</A>
+<LI><A HREF="gettext_6.html#IDX214">creating a new PO file</A>
+<LI><A HREF="gettext_8.html#IDX497">creating compendia</A>
+<LI><A HREF="gettext_1.html#IDX19">currency symbols</A>
+</DIR>
+<H2><A NAME="cindex_d">d</A></H2>
+<DIR>
+<LI><A HREF="gettext_1.html#IDX21">date format</A>
+<LI><A HREF="gettext_11.html#IDX1028">dcngettext</A>
+<LI><A HREF="gettext_11.html#IDX1021">dcpgettext</A>
+<LI><A HREF="gettext_11.html#IDX1024">dcpgettext_expr</A>
+<LI><A HREF="gettext_5.html#IDX183">debugging messages marked as format strings</A>
+<LI><A HREF="gettext_9.html#IDX507">dialect</A>
+<LI><A HREF="gettext_13.html#IDX1080">disabling NLS</A>
+<LI><A HREF="gettext_13.html#IDX1098">distribution tarball</A>
+<LI><A HREF="gettext_11.html#IDX1027">dngettext</A>
+<LI><A HREF="gettext_15.html#IDX1141">dollar substitution</A>
+<LI><A HREF="gettext_11.html#IDX1009">domain ambiguities</A>
+<LI><A HREF="gettext_11.html#IDX1020">dpgettext</A>
+<LI><A HREF="gettext_11.html#IDX1023">dpgettext_expr</A>
+<LI><A HREF="gettext_9.html#IDX510">duplicate elimination</A>
+<LI><A HREF="gettext_9.html#IDX688">duplicate removal</A>
+</DIR>
+<H2><A NAME="cindex_e">e</A></H2>
+<DIR>
+<LI><A HREF="gettext_8.html#IDX435">editing comments in PO files</A>
+<LI><A HREF="gettext_8.html#IDX298">Editing PO Files</A>
+<LI><A HREF="gettext_8.html#IDX412">editing translations</A>
+<LI><A HREF="gettext_15.html#IDX1159">Emacs Lisp</A>
+<LI><A HREF="gettext_8.html#IDX301">Emacs PO Mode</A>
+<LI><A HREF="gettext_1.html#IDX16">encoding</A>
+<LI><A HREF="gettext_9.html#IDX506">encoding conversion</A>
+<LI><A HREF="gettext_11.html#IDX1013">encoding conversion at runtime</A>
+<LI><A HREF="gettext_6.html#IDX246">encoding for your language</A>
+<LI><A HREF="gettext_6.html#IDX244">encoding list</A>
+<LI><A HREF="gettext_6.html#IDX241">encoding of PO files</A>
+<LI><A HREF="gettext_15.html#IDX1142">environment variables</A>
+<LI><A HREF="gettext_15.html#IDX1139"><CODE>envsubst</CODE> program, usage</A>
+<LI><A HREF="gettext_15.html#IDX1149"><CODE>eval_gettext</CODE> function, usage</A>
+<LI><A HREF="gettext_15.html#IDX1151"><CODE>eval_ngettext</CODE> function, usage</A>
+<LI><A HREF="gettext_1.html#IDX38">evolution of packages</A>
+<LI><A HREF="gettext_8.html#IDX501">extracting parts of a PO file into a compendium</A>
+</DIR>
+<H2><A NAME="cindex_f">f</A></H2>
+<DIR>
+<LI><A HREF="gettext_19.html#IDX1204">FDL, GNU Free Documentation License</A>
+<LI><A HREF="gettext_10.html#IDX995">file format, <TT>‘.mo’</TT></A>
+<LI><A HREF="gettext_3.html#IDX47">file format, <TT>‘.po’</TT></A>
+<LI><A HREF="gettext_1.html#IDX28">files, <TT>‘.po’</TT> and <TT>‘.mo’</TT></A>
+<LI><A HREF="gettext_1.html#IDX37">files, <TT>‘.pot’</TT></A>
+<LI><A HREF="gettext_9.html#IDX780">filter messages according to attributes</A>
+<LI><A HREF="gettext_9.html#IDX726">find common messages</A>
+<LI><A HREF="gettext_10.html#IDX938">force use of fuzzy entries</A>
+<LI><A HREF="gettext_4.html#IDX136">format strings</A>
+<LI><A HREF="gettext_15.html#IDX1171">Free Pascal</A>
+<LI><A HREF="gettext_5.html#IDX173">function attribute, __format__</A>
+<LI><A HREF="gettext_5.html#IDX174">function attribute, __format_arg__</A>
+<LI><A HREF="gettext_8.html#IDX372">fuzzy entries</A>
+</DIR>
+<H2><A NAME="cindex_g">g</A></H2>
+<DIR>
+<LI><A HREF="gettext_15.html#IDX1169">gawk</A>
+<LI><A HREF="gettext_15.html#IDX1190">GCC-source</A>
+<LI><A HREF="gettext_10.html#IDX889">generate binary message catalog from PO file</A>
+<LI><A HREF="gettext_9.html#IDX827">generate translation catalog in English</A>
+<LI><A HREF="gettext_13.html#IDX1066"><CODE>gettext</CODE> files</A>
+<LI><A HREF="gettext_8.html#IDX303"><CODE>gettext</CODE> installation</A>
+<LI><A HREF="gettext_11.html#IDX1007"><CODE>gettext</CODE> interface</A>
+<LI><A HREF="gettext_15.html#IDX1116"><CODE>gettext</CODE> program, usage</A>
+<LI><A HREF="gettext_11.html#IDX1006"><CODE>gettext</CODE>, a programmer's view</A>
+<LI><A HREF="gettext_11.html#IDX1034"><CODE>gettext</CODE> vs <CODE>catgets</CODE></A>
+<LI><A HREF="gettext_13.html#IDX1055"><CODE>gettextize</CODE> program, usage</A>
+<LI><A HREF="gettext_8.html#IDX300">GNOME PO file editor</A>
+<LI><A HREF="gettext_19.html#IDX1200">GPL, GNU General Public License</A>
+<LI><A HREF="gettext_11.html#IDX1016">GUI programs</A>
+<LI><A HREF="gettext_15.html#IDX1162">guile</A>
+</DIR>
+<H2><A NAME="cindex_h">h</A></H2>
+<DIR>
+<LI><A HREF="gettext_10.html#IDX997">hash table, inside MO files</A>
+<LI><A HREF="gettext_1.html#IDX2">he, she, and they</A>
+<LI><A HREF="gettext_6.html#IDX239">header entry of a PO file</A>
+<LI><A HREF="gettext_4.html#IDX119">help option</A>
+<LI><A HREF="gettext_16.html#IDX1192">history of GNU <CODE>gettext</CODE></A>
+</DIR>
+<H2><A NAME="cindex_i">i</A></H2>
+<DIR>
+<LI><A HREF="gettext_1.html#IDX6">i18n</A>
+<LI><A HREF="gettext_8.html#IDX361">importing PO files</A>
+<LI><A HREF="gettext_1.html#IDX33">include file <TT>‘libintl.h’</TT></A>, <A HREF="gettext_4.html#IDX103">include file <TT>‘libintl.h’</TT></A>, <A HREF="gettext_11.html#IDX1036">include file <TT>‘libintl.h’</TT></A>, <A HREF="gettext_13.html#IDX1081">include file <TT>‘libintl.h’</TT></A>
+<LI><A HREF="gettext_4.html#IDX104">initialization</A>
+<LI><A HREF="gettext_6.html#IDX218">initialize new PO file</A>
+<LI><A HREF="gettext_8.html#IDX502">initialize translations from a compendium</A>
+<LI><A HREF="gettext_8.html#IDX302">installing <CODE>gettext</CODE></A>
+<LI><A HREF="gettext_11.html#IDX1001">interface to <CODE>catgets</CODE></A>
+<LI><A HREF="gettext_1.html#IDX8">internationalization</A>
+<LI><A HREF="gettext_4.html#IDX122"><CODE>inttypes.h</CODE></A>
+<LI><A HREF="gettext_18.html#IDX1198">ISO 3166</A>
+<LI><A HREF="gettext_17.html#IDX1196">ISO 639</A>
+</DIR>
+<H2><A NAME="cindex_j">j</A></H2>
+<DIR>
+<LI><A HREF="gettext_15.html#IDX1164">Java</A>
+<LI><A HREF="gettext_10.html#IDX894">Java mode, and <CODE>msgfmt</CODE> program</A>
+<LI><A HREF="gettext_10.html#IDX954">Java mode, and <CODE>msgunfmt</CODE> program</A>
+<LI><A HREF="gettext_4.html#IDX123">Java, string concatenation</A>
+</DIR>
+<H2><A NAME="cindex_k">k</A></H2>
+<DIR>
+<LI><A HREF="gettext_8.html#IDX299">KDE PO file editor</A>
+<LI><A HREF="gettext_10.html#IDX933">keyboard accelerator checking</A>
+</DIR>
+<H2><A NAME="cindex_l">l</A></H2>
+<DIR>
+<LI><A HREF="gettext_1.html#IDX7">l10n</A>
+<LI><A HREF="gettext_17.html#IDX1195">language codes</A>
+<LI><A HREF="gettext_2.html#IDX44">language selection</A>
+<LI><A HREF="gettext_11.html#IDX1038">language selection at runtime</A>
+<LI><A HREF="gettext_11.html#IDX1010">large package</A>
+<LI><A HREF="gettext_19.html#IDX1202">LGPL, GNU Lesser General Public License</A>
+<LI><A HREF="gettext_13.html#IDX1088"><CODE>libiconv</CODE> library</A>
+<LI><A HREF="gettext_15.html#IDX1167"><CODE>libintl</CODE> for C#</A>
+<LI><A HREF="gettext_15.html#IDX1165"><CODE>libintl</CODE> for Java</A>
+<LI><A HREF="gettext_13.html#IDX1084"><CODE>libintl</CODE> library</A>
+<LI><A HREF="gettext_15.html#IDX1160"><CODE>librep</CODE> Lisp</A>
+<LI><A HREF="gettext_19.html#IDX1205">License, GNU FDL</A>
+<LI><A HREF="gettext_19.html#IDX1201">License, GNU GPL</A>
+<LI><A HREF="gettext_19.html#IDX1203">License, GNU LGPL</A>
+<LI><A HREF="gettext_19.html#IDX1199">Licenses</A>
+<LI><A HREF="gettext_1.html#IDX34">link with <TT>‘libintl’</TT></A>
+<LI><A HREF="gettext_1.html#IDX27">Linux</A>, <A HREF="gettext_1.html#IDX35">Linux</A>, <A HREF="gettext_6.html#IDX245">Linux</A>
+<LI><A HREF="gettext_15.html#IDX1156">Lisp</A>
+<LI><A HREF="gettext_6.html#IDX240">list of translation teams, where to find</A>
+<LI><A HREF="gettext_4.html#IDX105">locale facet, LC_ALL</A>
+<LI><A HREF="gettext_4.html#IDX108">locale facet, LC_COLLATE</A>
+<LI><A HREF="gettext_1.html#IDX18">locale facet, LC_CTYPE</A>, <A HREF="gettext_4.html#IDX106">locale facet, LC_CTYPE</A>, <A HREF="gettext_4.html#IDX107">locale facet, LC_CTYPE</A>
+<LI><A HREF="gettext_1.html#IDX26">locale facet, LC_MESSAGES</A>, <A HREF="gettext_4.html#IDX112">locale facet, LC_MESSAGES</A>
+<LI><A HREF="gettext_1.html#IDX20">locale facet, LC_MONETARY</A>, <A HREF="gettext_4.html#IDX109">locale facet, LC_MONETARY</A>
+<LI><A HREF="gettext_1.html#IDX24">locale facet, LC_NUMERIC</A>, <A HREF="gettext_4.html#IDX110">locale facet, LC_NUMERIC</A>
+<LI><A HREF="gettext_4.html#IDX113">locale facet, LC_RESPONSES</A>
+<LI><A HREF="gettext_1.html#IDX22">locale facet, LC_TIME</A>, <A HREF="gettext_4.html#IDX111">locale facet, LC_TIME</A>
+<LI><A HREF="gettext_1.html#IDX14">locale facets</A>
+<LI><A HREF="gettext_6.html#IDX243"><CODE>locale</CODE> program</A>
+<LI><A HREF="gettext_1.html#IDX9">localization</A>
+<LI><A HREF="gettext_15.html#IDX1117">lookup message translation</A>, <A HREF="gettext_15.html#IDX1150">lookup message translation</A>
+<LI><A HREF="gettext_15.html#IDX1129">lookup plural message translation</A>, <A HREF="gettext_15.html#IDX1152">lookup plural message translation</A>
+</DIR>
+<H2><A NAME="cindex_m">m</A></H2>
+<DIR>
+<LI><A HREF="gettext_10.html#IDX996">magic signature of MO files</A>
+<LI><A HREF="gettext_9.html#IDX504">manipulating PO files</A>
+<LI><A HREF="gettext_15.html#IDX1179">marking Perl sources</A>
+<LI><A HREF="gettext_4.html#IDX139">marking string initializers</A>
+<LI><A HREF="gettext_4.html#IDX125">marking strings that require translation</A>
+<LI><A HREF="gettext_4.html#IDX114">marking strings, preparations</A>
+<LI><A HREF="gettext_1.html#IDX32">marking translatable strings</A>
+<LI><A HREF="gettext_11.html#IDX1018">menu entries</A>
+<LI><A HREF="gettext_10.html#IDX934">menu, keyboard accelerator support</A>
+<LI><A HREF="gettext_9.html#IDX515">merge PO files</A>
+<LI><A HREF="gettext_9.html#IDX505">merging two PO files</A>
+<LI><A HREF="gettext_11.html#IDX1011">message catalog files location</A>
+<LI><A HREF="gettext_1.html#IDX25">messages</A>
+<LI><A HREF="gettext_13.html#IDX1052">migration from earlier versions of <CODE>gettext</CODE></A>
+<LI><A HREF="gettext_10.html#IDX935">mnemonics of menu entries</A>
+<LI><A HREF="gettext_10.html#IDX994">MO file's format</A>
+<LI><A HREF="gettext_9.html#IDX792">modify message attrributes</A>
+<LI><A HREF="gettext_9.html#IDX779"><CODE>msgattrib</CODE> program, usage</A>
+<LI><A HREF="gettext_9.html#IDX513"><CODE>msgcat</CODE> program, usage</A>
+<LI><A HREF="gettext_9.html#IDX765"><CODE>msgcmp</CODE> program, usage</A>
+<LI><A HREF="gettext_9.html#IDX725"><CODE>msgcomm</CODE> program, usage</A>
+<LI><A HREF="gettext_9.html#IDX558"><CODE>msgconv</CODE> program, usage</A>
+<LI><A HREF="gettext_9.html#IDX826"><CODE>msgen</CODE> program, usage</A>
+<LI><A HREF="gettext_9.html#IDX856"><CODE>msgexec</CODE> program, usage</A>
+<LI><A HREF="gettext_9.html#IDX651"><CODE>msgfilter</CODE> filter and catalog encoding</A>
+<LI><A HREF="gettext_9.html#IDX643"><CODE>msgfilter</CODE> program, usage</A>
+<LI><A HREF="gettext_10.html#IDX888"><CODE>msgfmt</CODE> program, usage</A>
+<LI><A HREF="gettext_9.html#IDX590"><CODE>msggrep</CODE> program, usage</A>
+<LI><A HREF="gettext_6.html#IDX216"><CODE>msginit</CODE> program, usage</A>
+<LI><A HREF="gettext_7.html#IDX251"><CODE>msgmerge</CODE> program, usage</A>
+<LI><A HREF="gettext_10.html#IDX950"><CODE>msgunfmt</CODE> program, usage</A>
+<LI><A HREF="gettext_9.html#IDX686"><CODE>msguniq</CODE> program, usage</A>
+<LI><A HREF="gettext_8.html#IDX362">multi-line strings</A>
+</DIR>
+<H2><A NAME="cindex_n">n</A></H2>
+<DIR>
+<LI><A HREF="gettext_11.html#IDX1037"><CODE>N_</CODE>, a convenience macro</A>
+<LI><A HREF="gettext_1.html#IDX11">Native Language Support</A>
+<LI><A HREF="gettext_1.html#IDX12">Natural Language Support</A>
+<LI><A HREF="gettext_3.html#IDX100">newlines in PO files</A>
+<LI><A HREF="gettext_11.html#IDX1026">ngettext</A>
+<LI><A HREF="gettext_15.html#IDX1128"><CODE>ngettext</CODE> program, usage</A>
+<LI><A HREF="gettext_1.html#IDX10">NLS</A>
+<LI><A HREF="gettext_1.html#IDX23">number format</A>
+</DIR>
+<H2><A NAME="cindex_o">o</A></H2>
+<DIR>
+<LI><A HREF="gettext_15.html#IDX1172">Object Pascal</A>
+<LI><A HREF="gettext_8.html#IDX399">obsolete entries</A>
+<LI><A HREF="gettext_11.html#IDX1033">optimization of <CODE>gettext</CODE> functions</A>
+<LI><A HREF="gettext_9.html#IDX508">orthography</A>
+<LI><A HREF="gettext_15.html#IDX1106">outdigits</A>
+<LI><A HREF="gettext_5.html#IDX153">output to stdout, <CODE>xgettext</CODE></A>
+<LI><A HREF="gettext_1.html#IDX29">overview of <CODE>gettext</CODE></A>
+</DIR>
+<H2><A NAME="cindex_p">p</A></H2>
+<DIR>
+<LI><A HREF="gettext_13.html#IDX1073">package and version declaration in <TT>‘configure.in’</TT></A>
+<LI><A HREF="gettext_14.html#IDX1101">package build and installation options</A>
+<LI><A HREF="gettext_14.html#IDX1100">package distributor's view of <CODE>gettext</CODE></A>
+<LI><A HREF="gettext_14.html#IDX1099">package installer's view of <CODE>gettext</CODE></A>
+<LI><A HREF="gettext_13.html#IDX1050">package maintainer's view of <CODE>gettext</CODE></A>
+<LI><A HREF="gettext_4.html#IDX118">paragraphs</A>
+<LI><A HREF="gettext_15.html#IDX1170">Pascal</A>
+<LI><A HREF="gettext_15.html#IDX1178">Perl</A>
+<LI><A HREF="gettext_15.html#IDX1180">Perl default keywords</A>
+<LI><A HREF="gettext_15.html#IDX1183">Perl invalid string interpolation</A>
+<LI><A HREF="gettext_15.html#IDX1186">Perl long lines</A>
+<LI><A HREF="gettext_15.html#IDX1185">Perl parentheses</A>
+<LI><A HREF="gettext_15.html#IDX1187">Perl pitfalls</A>
+<LI><A HREF="gettext_15.html#IDX1182">Perl quote-like expressions</A>
+<LI><A HREF="gettext_15.html#IDX1181">Perl special keywords for hash-lookups</A>
+<LI><A HREF="gettext_15.html#IDX1184">Perl valid string interpolation</A>
+<LI><A HREF="gettext_11.html#IDX1019">pgettext</A>
+<LI><A HREF="gettext_11.html#IDX1022">pgettext_expr</A>
+<LI><A HREF="gettext_15.html#IDX1188">PHP</A>
+<LI><A HREF="gettext_15.html#IDX1189">Pike</A>
+<LI><A HREF="gettext_11.html#IDX1032">plural form formulas</A>
+<LI><A HREF="gettext_11.html#IDX1025">plural forms</A>
+<LI><A HREF="gettext_10.html#IDX999">plural forms, in MO files</A>
+<LI><A HREF="gettext_3.html#IDX99">plural forms, in PO files</A>
+<LI><A HREF="gettext_3.html#IDX46">PO files' format</A>
+<LI><A HREF="gettext_8.html#IDX306">PO mode (Emacs) commands</A>
+<LI><A HREF="gettext_5.html#IDX140">PO template file</A>
+<LI><A HREF="gettext_9.html#IDX879">po_file_domains</A>
+<LI><A HREF="gettext_9.html#IDX878">po_file_free</A>
+<LI><A HREF="gettext_9.html#IDX877">po_file_read</A>
+<LI><A HREF="gettext_9.html#IDX880">po_message_iterator</A>
+<LI><A HREF="gettext_9.html#IDX881">po_message_iterator_free</A>
+<LI><A HREF="gettext_9.html#IDX883">po_message_msgid</A>
+<LI><A HREF="gettext_9.html#IDX884">po_message_msgid_plural</A>
+<LI><A HREF="gettext_9.html#IDX885">po_message_msgstr</A>
+<LI><A HREF="gettext_9.html#IDX886">po_message_msgstr_plural</A>
+<LI><A HREF="gettext_9.html#IDX882">po_next_message</A>
+<LI><A HREF="gettext_9.html#IDX652">portability problems with <CODE>sed</CODE></A>
+<LI><A HREF="gettext_4.html#IDX102">preparing programs for translation</A>
+<LI><A HREF="gettext_15.html#IDX1114">preparing shell scripts for translation</A>
+<LI><A HREF="gettext_11.html#IDX1005">problems with <CODE>catgets</CODE> interface</A>
+<LI><A HREF="gettext_15.html#IDX1104">programming languages</A>
+<LI><A HREF="gettext_15.html#IDX1154">Python</A>
+</DIR>
+<H2><A NAME="cindex_q">q</A></H2>
+<DIR>
+<LI><A HREF="gettext_5.html#IDX179">Qt format strings</A>
+<LI><A HREF="gettext_10.html#IDX903">Qt mode, and <CODE>msgfmt</CODE> program</A>
+<LI><A HREF="gettext_6.html#IDX248">quotation marks</A>, <A HREF="gettext_13.html#IDX1071">quotation marks</A>
+<LI><A HREF="gettext_6.html#IDX247">quote characters, use in PO files</A>
+</DIR>
+<H2><A NAME="cindex_r">r</A></H2>
+<DIR>
+<LI><A HREF="gettext_9.html#IDX661"><CODE>recode-sr-latin</CODE> program</A>
+<LI><A HREF="gettext_16.html#IDX1193">related reading</A>
+<LI><A HREF="gettext_13.html#IDX1097">release</A>
+<LI><A HREF="gettext_15.html#IDX1191">RST</A>
+</DIR>
+<H2><A NAME="cindex_s">s</A></H2>
+<DIR>
+<LI><A HREF="gettext_15.html#IDX1161">Scheme</A>
+<LI><A HREF="gettext_15.html#IDX1105">scripting languages</A>
+<LI><A HREF="gettext_9.html#IDX591">search messages in a catalog</A>
+<LI><A HREF="gettext_2.html#IDX43">selecting message language</A>
+<LI><A HREF="gettext_4.html#IDX117">sentences</A>
+<LI><A HREF="gettext_14.html#IDX1102">setting up <CODE>gettext</CODE> at build time</A>
+<LI><A HREF="gettext_2.html#IDX42">setting up <CODE>gettext</CODE> at run time</A>
+<LI><A HREF="gettext_11.html#IDX1008">several domains</A>
+<LI><A HREF="gettext_1.html#IDX1">sex</A>
+<LI><A HREF="gettext_1.html#IDX3">she, he, and they</A>
+<LI><A HREF="gettext_15.html#IDX1140">shell format string</A>
+<LI><A HREF="gettext_15.html#IDX1109">shell scripts</A>
+<LI><A HREF="gettext_15.html#IDX1163">Smalltalk</A>
+<LI><A HREF="gettext_9.html#IDX550">sorting <CODE>msgcat</CODE> output</A>
+<LI><A HREF="gettext_7.html#IDX286">sorting <CODE>msgmerge</CODE> output</A>
+<LI><A HREF="gettext_10.html#IDX987">sorting <CODE>msgunfmt</CODE> output</A>
+<LI><A HREF="gettext_5.html#IDX198">sorting output of <CODE>xgettext</CODE></A>
+<LI><A HREF="gettext_11.html#IDX1029">specifying plural form in a PO file</A>
+<LI><A HREF="gettext_9.html#IDX522">standard output, and <CODE>msgcat</CODE></A>
+<LI><A HREF="gettext_7.html#IDX260">standard output, and <CODE>msgmerge</CODE> program</A>
+<LI><A HREF="gettext_4.html#IDX120">string concatenation</A>
+<LI><A HREF="gettext_8.html#IDX358">string normalization in entries</A>
+<LI><A HREF="gettext_4.html#IDX115">style</A>
+<LI><A HREF="gettext_5.html#IDX156">supported languages, <CODE>xgettext</CODE></A>
+</DIR>
+<H2><A NAME="cindex_t">t</A></H2>
+<DIR>
+<LI><A HREF="gettext_15.html#IDX1176">Tcl</A>
+<LI><A HREF="gettext_10.html#IDX901">Tcl mode, and <CODE>msgfmt</CODE> program</A>
+<LI><A HREF="gettext_10.html#IDX960">Tcl mode, and <CODE>msgunfmt</CODE> program</A>
+<LI><A HREF="gettext_1.html#IDX36">template PO file</A>
+<LI><A HREF="gettext_5.html#IDX202">testing <TT>‘.po’</TT> files for equivalence</A>
+<LI><A HREF="gettext_15.html#IDX1177">Tk's scripting language</A>
+<LI><A HREF="gettext_8.html#IDX363">translated entries</A>
+<LI><A HREF="gettext_11.html#IDX1017">translating menu entries</A>
+<LI><A HREF="gettext_1.html#IDX13">translation aspects</A>
+<LI><A HREF="gettext_2.html#IDX39">Translation Matrix</A>
+<LI><A HREF="gettext_1.html#IDX5">Translation Project</A>
+<LI><A HREF="gettext_13.html#IDX1079">turning off NLS support</A>
+<LI><A HREF="gettext_1.html#IDX31">tutorial of <CODE>gettext</CODE> usage</A>
+</DIR>
+<H2><A NAME="cindex_u">u</A></H2>
+<DIR>
+<LI><A HREF="gettext_9.html#IDX687">unify duplicate translations</A>
+<LI><A HREF="gettext_8.html#IDX388">untranslated entries</A>
+<LI><A HREF="gettext_8.html#IDX503">update translations from a compendium</A>
+<LI><A HREF="gettext_13.html#IDX1053">upgrading to new versions of <CODE>gettext</CODE></A>
+</DIR>
+<H2><A NAME="cindex_v">v</A></H2>
+<DIR>
+<LI><A HREF="gettext_7.html#IDX264">version control for backup files, <CODE>msgmerge</CODE></A>
+</DIR>
+<H2><A NAME="cindex_w">w</A></H2>
+<DIR>
+<LI><A HREF="gettext_15.html#IDX1173"><CODE>wxWidgets</CODE> library</A>
+</DIR>
+<H2><A NAME="cindex_x">x</A></H2>
+<DIR>
+<LI><A HREF="gettext_9.html#IDX858"><CODE>xargs</CODE>, and output from <CODE>msgexec</CODE></A>
+<LI><A HREF="gettext_5.html#IDX142"><CODE>xgettext</CODE> program, usage</A>
+<LI><A HREF="gettext_6.html#IDX249"><CODE>xmodmap</CODE> program, and typing quotation marks</A>
+</DIR>
+<H2><A NAME="cindex_y">y</A></H2>
+<DIR>
+<LI><A HREF="gettext_15.html#IDX1175">YaST2 scripting language</A>
+<LI><A HREF="gettext_15.html#IDX1174">YCP</A>
+</DIR>
+
+</P>
+
+<P><HR><P>
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_24.html">previous</A>, next, last section, <A HREF="gettext_toc.html">table of contents</A>.
+</BODY>
+</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 3 The Format of PO Files</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_2.html">previous</A>, <A HREF="gettext_4.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_2.html">previous</A>, <A HREF="gettext_4.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
<PRE>
<VAR>white-space</VAR>
# <VAR>translator-comments</VAR>
-#. <VAR>automatic-comments</VAR>
+#. <VAR>extracted-comments</VAR>
#: <VAR>reference</VAR>...
#, <VAR>flag</VAR>...
msgid <VAR>untranslated-string</VAR>
</PRE>
<P>
+<A NAME="IDX48"></A>
+<A NAME="IDX49"></A>
+<A NAME="IDX50"></A>
Entries begin with some optional white space. Usually, when generated
through GNU <CODE>gettext</CODE> tools, there is exactly one blank line
between entries. Then comments follow, on lines all starting with the
character <CODE>#</CODE>. There are two kinds of comments: those which have
-some white space immediately following the <CODE>#</CODE>, which comments are
-created and maintained exclusively by the translator, and those which
-have some non-white character just after the <CODE>#</CODE>, which comments
-are created and maintained automatically by GNU <CODE>gettext</CODE> tools.
+some white space immediately following the <CODE>#</CODE> - the <VAR>translator
+comments</VAR> -, which comments are created and maintained exclusively by the
+translator, and those which have some non-white character just after the
+<CODE>#</CODE> - the <VAR>automatic comments</VAR> -, which comments are created and
+maintained automatically by GNU <CODE>gettext</CODE> tools. Comment lines
+starting with <CODE>#.</CODE> contain comments given by the programmer, directed
+at the translator; these comments are called <VAR>extracted comments</VAR>
+because the <CODE>xgettext</CODE> program extracts them from the program's
+source code. Comment lines starting with <CODE>#:</CODE> contain references to
+the program's source code. Comment lines starting with <CODE>#,</CODE> contain
+flags; more about these below.
All comments, of either kind, are optional.
</P>
<P>
-<A NAME="IDX48"></A>
-<A NAME="IDX49"></A>
+<A NAME="IDX51"></A>
+<A NAME="IDX52"></A>
After white space and comments, entries show two strings, namely
first the untranslated string as it appears in the original program
sources, and then, the translation of this string. The original
<DT><CODE>fuzzy</CODE>
<DD>
-<A NAME="IDX50"></A>
+<A NAME="IDX53"></A>
This flag can be generated by the <CODE>msgmerge</CODE> program or it can be
inserted by the translator herself. It shows that the <CODE>msgstr</CODE>
string might not be a correct translation (anymore). Only the translator
acceptable as is. Once satisfied with the translation, she then removes
this <CODE>fuzzy</CODE> attribute. The <CODE>msgmerge</CODE> program inserts this
when it combined the <CODE>msgid</CODE> and <CODE>msgstr</CODE> entries after fuzzy
-search only. See section <A HREF="gettext_8.html#SEC57">8.3.6 Fuzzy Entries</A>.
+search only. See section <A HREF="gettext_8.html#SEC58">8.3.6 Fuzzy Entries</A>.
<DT><CODE>c-format</CODE>
<DD>
-<A NAME="IDX51"></A>
+<A NAME="IDX54"></A>
<DT><CODE>no-c-format</CODE>
<DD>
-<A NAME="IDX52"></A>
+<A NAME="IDX55"></A>
These flags should not be added by a human. Instead only the
<CODE>xgettext</CODE> program adds them. In an automated PO file processing
system as proposed here the user changes would be thrown away again as
The <CODE>c-format</CODE> flag tells that the untranslated string and the
translation are supposed to be C format strings. The <CODE>no-c-format</CODE>
flag tells that they are not C format strings, even though the untranslated
-string happens to look like a C format string (with <SAMP>`%´</SAMP> directives).
+string happens to look like a C format string (with <SAMP>‘%’</SAMP> directives).
In case the <CODE>c-format</CODE> flag is given for a string the <CODE>msgfmt</CODE>
does some more tests to check to validity of the translation.
-See section <A HREF="gettext_10.html#SEC141">10.1 Invoking the <CODE>msgfmt</CODE> Program</A>, section <A HREF="gettext_4.html#SEC16">4.5 Special Comments preceding Keywords</A> and section <A HREF="gettext_15.html#SEC228">15.3.1 C Format Strings</A>.
+See section <A HREF="gettext_10.html#SEC143">10.1 Invoking the <CODE>msgfmt</CODE> Program</A>, section <A HREF="gettext_4.html#SEC17">4.6 Special Comments preceding Keywords</A> and section <A HREF="gettext_15.html#SEC231">15.3.1 C Format Strings</A>.
<DT><CODE>objc-format</CODE>
<DD>
-<A NAME="IDX53"></A>
+<A NAME="IDX56"></A>
<DT><CODE>no-objc-format</CODE>
<DD>
-<A NAME="IDX54"></A>
-Likewise for Objective C, see section <A HREF="gettext_15.html#SEC229">15.3.2 Objective C Format Strings</A>.
+<A NAME="IDX57"></A>
+Likewise for Objective C, see section <A HREF="gettext_15.html#SEC232">15.3.2 Objective C Format Strings</A>.
<DT><CODE>sh-format</CODE>
<DD>
-<A NAME="IDX55"></A>
+<A NAME="IDX58"></A>
<DT><CODE>no-sh-format</CODE>
<DD>
-<A NAME="IDX56"></A>
-Likewise for Shell, see section <A HREF="gettext_15.html#SEC230">15.3.3 Shell Format Strings</A>.
+<A NAME="IDX59"></A>
+Likewise for Shell, see section <A HREF="gettext_15.html#SEC233">15.3.3 Shell Format Strings</A>.
<DT><CODE>python-format</CODE>
<DD>
-<A NAME="IDX57"></A>
+<A NAME="IDX60"></A>
<DT><CODE>no-python-format</CODE>
<DD>
-<A NAME="IDX58"></A>
-Likewise for Python, see section <A HREF="gettext_15.html#SEC231">15.3.4 Python Format Strings</A>.
+<A NAME="IDX61"></A>
+Likewise for Python, see section <A HREF="gettext_15.html#SEC234">15.3.4 Python Format Strings</A>.
<DT><CODE>lisp-format</CODE>
<DD>
-<A NAME="IDX59"></A>
+<A NAME="IDX62"></A>
<DT><CODE>no-lisp-format</CODE>
<DD>
-<A NAME="IDX60"></A>
-Likewise for Lisp, see section <A HREF="gettext_15.html#SEC232">15.3.5 Lisp Format Strings</A>.
+<A NAME="IDX63"></A>
+Likewise for Lisp, see section <A HREF="gettext_15.html#SEC235">15.3.5 Lisp Format Strings</A>.
<DT><CODE>elisp-format</CODE>
<DD>
-<A NAME="IDX61"></A>
+<A NAME="IDX64"></A>
<DT><CODE>no-elisp-format</CODE>
<DD>
-<A NAME="IDX62"></A>
-Likewise for Emacs Lisp, see section <A HREF="gettext_15.html#SEC233">15.3.6 Emacs Lisp Format Strings</A>.
+<A NAME="IDX65"></A>
+Likewise for Emacs Lisp, see section <A HREF="gettext_15.html#SEC236">15.3.6 Emacs Lisp Format Strings</A>.
<DT><CODE>librep-format</CODE>
<DD>
-<A NAME="IDX63"></A>
+<A NAME="IDX66"></A>
<DT><CODE>no-librep-format</CODE>
<DD>
-<A NAME="IDX64"></A>
-Likewise for librep, see section <A HREF="gettext_15.html#SEC234">15.3.7 librep Format Strings</A>.
+<A NAME="IDX67"></A>
+Likewise for librep, see section <A HREF="gettext_15.html#SEC237">15.3.7 librep Format Strings</A>.
<DT><CODE>scheme-format</CODE>
<DD>
-<A NAME="IDX65"></A>
+<A NAME="IDX68"></A>
<DT><CODE>no-scheme-format</CODE>
<DD>
-<A NAME="IDX66"></A>
-Likewise for Scheme, see section <A HREF="gettext_15.html#SEC235">15.3.8 Scheme Format Strings</A>.
+<A NAME="IDX69"></A>
+Likewise for Scheme, see section <A HREF="gettext_15.html#SEC238">15.3.8 Scheme Format Strings</A>.
<DT><CODE>smalltalk-format</CODE>
<DD>
-<A NAME="IDX67"></A>
+<A NAME="IDX70"></A>
<DT><CODE>no-smalltalk-format</CODE>
<DD>
-<A NAME="IDX68"></A>
-Likewise for Smalltalk, see section <A HREF="gettext_15.html#SEC236">15.3.9 Smalltalk Format Strings</A>.
+<A NAME="IDX71"></A>
+Likewise for Smalltalk, see section <A HREF="gettext_15.html#SEC239">15.3.9 Smalltalk Format Strings</A>.
<DT><CODE>java-format</CODE>
<DD>
-<A NAME="IDX69"></A>
+<A NAME="IDX72"></A>
<DT><CODE>no-java-format</CODE>
<DD>
-<A NAME="IDX70"></A>
-Likewise for Java, see section <A HREF="gettext_15.html#SEC237">15.3.10 Java Format Strings</A>.
+<A NAME="IDX73"></A>
+Likewise for Java, see section <A HREF="gettext_15.html#SEC240">15.3.10 Java Format Strings</A>.
<DT><CODE>csharp-format</CODE>
<DD>
-<A NAME="IDX71"></A>
+<A NAME="IDX74"></A>
<DT><CODE>no-csharp-format</CODE>
<DD>
-<A NAME="IDX72"></A>
-Likewise for C#, see section <A HREF="gettext_15.html#SEC238">15.3.11 C# Format Strings</A>.
+<A NAME="IDX75"></A>
+Likewise for C#, see section <A HREF="gettext_15.html#SEC241">15.3.11 C# Format Strings</A>.
<DT><CODE>awk-format</CODE>
<DD>
-<A NAME="IDX73"></A>
+<A NAME="IDX76"></A>
<DT><CODE>no-awk-format</CODE>
<DD>
-<A NAME="IDX74"></A>
-Likewise for awk, see section <A HREF="gettext_15.html#SEC239">15.3.12 awk Format Strings</A>.
+<A NAME="IDX77"></A>
+Likewise for awk, see section <A HREF="gettext_15.html#SEC242">15.3.12 awk Format Strings</A>.
<DT><CODE>object-pascal-format</CODE>
<DD>
-<A NAME="IDX75"></A>
+<A NAME="IDX78"></A>
<DT><CODE>no-object-pascal-format</CODE>
<DD>
-<A NAME="IDX76"></A>
-Likewise for Object Pascal, see section <A HREF="gettext_15.html#SEC240">15.3.13 Object Pascal Format Strings</A>.
+<A NAME="IDX79"></A>
+Likewise for Object Pascal, see section <A HREF="gettext_15.html#SEC243">15.3.13 Object Pascal Format Strings</A>.
<DT><CODE>ycp-format</CODE>
<DD>
-<A NAME="IDX77"></A>
+<A NAME="IDX80"></A>
<DT><CODE>no-ycp-format</CODE>
<DD>
-<A NAME="IDX78"></A>
-Likewise for YCP, see section <A HREF="gettext_15.html#SEC241">15.3.14 YCP Format Strings</A>.
+<A NAME="IDX81"></A>
+Likewise for YCP, see section <A HREF="gettext_15.html#SEC244">15.3.14 YCP Format Strings</A>.
<DT><CODE>tcl-format</CODE>
<DD>
-<A NAME="IDX79"></A>
+<A NAME="IDX82"></A>
<DT><CODE>no-tcl-format</CODE>
<DD>
-<A NAME="IDX80"></A>
-Likewise for Tcl, see section <A HREF="gettext_15.html#SEC242">15.3.15 Tcl Format Strings</A>.
+<A NAME="IDX83"></A>
+Likewise for Tcl, see section <A HREF="gettext_15.html#SEC245">15.3.15 Tcl Format Strings</A>.
<DT><CODE>perl-format</CODE>
<DD>
-<A NAME="IDX81"></A>
+<A NAME="IDX84"></A>
<DT><CODE>no-perl-format</CODE>
<DD>
-<A NAME="IDX82"></A>
-Likewise for Perl, see section <A HREF="gettext_15.html#SEC243">15.3.16 Perl Format Strings</A>.
+<A NAME="IDX85"></A>
+Likewise for Perl, see section <A HREF="gettext_15.html#SEC246">15.3.16 Perl Format Strings</A>.
<DT><CODE>perl-brace-format</CODE>
<DD>
-<A NAME="IDX83"></A>
+<A NAME="IDX86"></A>
<DT><CODE>no-perl-brace-format</CODE>
<DD>
-<A NAME="IDX84"></A>
-Likewise for Perl brace, see section <A HREF="gettext_15.html#SEC243">15.3.16 Perl Format Strings</A>.
+<A NAME="IDX87"></A>
+Likewise for Perl brace, see section <A HREF="gettext_15.html#SEC246">15.3.16 Perl Format Strings</A>.
<DT><CODE>php-format</CODE>
<DD>
-<A NAME="IDX85"></A>
+<A NAME="IDX88"></A>
<DT><CODE>no-php-format</CODE>
<DD>
-<A NAME="IDX86"></A>
-Likewise for PHP, see section <A HREF="gettext_15.html#SEC244">15.3.17 PHP Format Strings</A>.
+<A NAME="IDX89"></A>
+Likewise for PHP, see section <A HREF="gettext_15.html#SEC247">15.3.17 PHP Format Strings</A>.
<DT><CODE>gcc-internal-format</CODE>
<DD>
-<A NAME="IDX87"></A>
+<A NAME="IDX90"></A>
<DT><CODE>no-gcc-internal-format</CODE>
<DD>
-<A NAME="IDX88"></A>
-Likewise for the GCC sources, see section <A HREF="gettext_15.html#SEC245">15.3.18 GCC internal Format Strings</A>.
+<A NAME="IDX91"></A>
+Likewise for the GCC sources, see section <A HREF="gettext_15.html#SEC248">15.3.18 GCC internal Format Strings</A>.
<DT><CODE>qt-format</CODE>
<DD>
-<A NAME="IDX89"></A>
+<A NAME="IDX92"></A>
<DT><CODE>no-qt-format</CODE>
<DD>
-<A NAME="IDX90"></A>
-Likewise for Qt, see section <A HREF="gettext_15.html#SEC246">15.3.19 Qt Format Strings</A>.
+<A NAME="IDX93"></A>
+Likewise for Qt, see section <A HREF="gettext_15.html#SEC249">15.3.19 Qt Format Strings</A>.
+
+<DT><CODE>boost-format</CODE>
+<DD>
+<A NAME="IDX94"></A>
+<DT><CODE>no-boost-format</CODE>
+<DD>
+<A NAME="IDX95"></A>
+Likewise for Boost, see section <A HREF="gettext_15.html#SEC250">15.3.20 Boost Format Strings</A>.
</DL>
<P>
-<A NAME="IDX91"></A>
-<A NAME="IDX92"></A>
+<A NAME="IDX96"></A>
+<A NAME="IDX97"></A>
+It is also possible to have entries with a context specifier. They look like
+this:
+
+</P>
+
+<PRE>
+<VAR>white-space</VAR>
+# <VAR>translator-comments</VAR>
+#. <VAR>extracted-comments</VAR>
+#: <VAR>reference</VAR>...
+#, <VAR>flag</VAR>...
+msgctxt <VAR>context</VAR>
+msgid <VAR>untranslated-string</VAR>
+msgstr <VAR>translated-string</VAR>
+</PRE>
+
+<P>
+The context serves to disambiguate messages with the same
+<VAR>untranslated-string</VAR>. It is possible to have several entries with
+the same <VAR>untranslated-string</VAR> in a PO file, provided that they each
+have a different <VAR>context</VAR>. Note that an empty <VAR>context</VAR> string
+and an absent <CODE>msgctxt</CODE> line do not mean the same thing.
+
+</P>
+<P>
+<A NAME="IDX98"></A>
+<A NAME="IDX99"></A>
A different kind of entries is used for translations which involve
plural forms.
<PRE>
<VAR>white-space</VAR>
# <VAR>translator-comments</VAR>
-#. <VAR>automatic-comments</VAR>
+#. <VAR>extracted-comments</VAR>
#: <VAR>reference</VAR>...
#, <VAR>flag</VAR>...
msgid <VAR>untranslated-string-singular</VAR>
</PRE>
<P>
-<A NAME="IDX93"></A>
+Here also, a <CODE>msgctxt</CODE> context can be specified before <CODE>msgid</CODE>,
+like above.
+
+</P>
+<P>
It happens that some lines, usually whitespace or comments, follow the
very last entry of a PO file. Such lines are not part of any entry,
-and PO mode is unable to take action on those lines. By using the
-PO mode function <KBD>M-x po-normalize</KBD>, the translator may get
-rid of those spurious lines. See section <A HREF="gettext_8.html#SEC55">8.3.4 Normalizing Strings in Entries</A>.
+and will be dropped when the PO file is processed by the tools, or may
+disturb some PO file editors.
</P>
<P>
The remainder of this section may be safely skipped by those using
-PO mode, yet it may be interesting for everybody to have a better
+a PO file editor, yet it may be interesting for everybody to have a better
idea of the precise format of a PO file. On the other hand, those
-not having Emacs handy should carefully continue reading on.
+wishing to modify PO files by hand should carefully continue reading on.
</P>
<P>
<P>
In this example, the empty string is used on the first line, to
-allow better alignment of the <CODE>H</CODE> from the word <SAMP>`Here´</SAMP>
-over the <CODE>f</CODE> from the word <SAMP>`for´</SAMP>. In this example, the
+allow better alignment of the <CODE>H</CODE> from the word <SAMP>‘Here’</SAMP>
+over the <CODE>f</CODE> from the word <SAMP>‘for’</SAMP>. In this example, the
<CODE>msgid</CODE> keyword is followed by three strings, which are meant
to be concatenated. Concatenating the empty string does not change
the resulting overall string, but it is a way for us to comply with
the necessity of <CODE>msgid</CODE> to be followed by a string on the same
line, while keeping the multi-line presentation left-justified, as
we find this to be a cleaner disposition. The empty string could have
-been omitted, but only if the string starting with <SAMP>`Here´</SAMP> was
+been omitted, but only if the string starting with <SAMP>‘Here’</SAMP> was
promoted on the first line, right after <CODE>msgid</CODE>.<A NAME="DOCF2" HREF="gettext_foot.html#FOOT2">(2)</A> It was not really necessary
either to switch between the two last quoted strings immediately after
-the newline <SAMP>`\n´</SAMP>, the switch could have occurred after <EM>any</EM>
+the newline <SAMP>‘\n’</SAMP>, the switch could have occurred after <EM>any</EM>
other character, we just did it this way because it is neater.
</P>
<P>
-<A NAME="IDX94"></A>
+<A NAME="IDX100"></A>
One should carefully distinguish between end of lines marked as
-<SAMP>`\n´</SAMP> <EM>inside</EM> quotes, which are part of the represented
+<SAMP>‘\n’</SAMP> <EM>inside</EM> quotes, which are part of the represented
string, and end of lines in the PO file itself, outside string quotes,
which have no incidence on the represented string.
</P>
<P>
-<A NAME="IDX95"></A>
+<A NAME="IDX101"></A>
Outside strings, white lines and comments may be used freely.
-Comments start at the beginning of a line with <SAMP>`#´</SAMP> and extend
+Comments start at the beginning of a line with <SAMP>‘#’</SAMP> and extend
until the end of the PO file line. Comments written by translators
-should have the initial <SAMP>`#´</SAMP> immediately followed by some white
-space. If the <SAMP>`#´</SAMP> is not immediately followed by white space,
+should have the initial <SAMP>‘#’</SAMP> immediately followed by some white
+space. If the <SAMP>‘#’</SAMP> is not immediately followed by white space,
this comment is most likely generated and managed by specialized GNU
tools, and might disappear or be replaced unexpectedly when the PO
file is given to <CODE>msgmerge</CODE>.
</P>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_2.html">previous</A>, <A HREF="gettext_4.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_2.html">previous</A>, <A HREF="gettext_4.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 4 Preparing Program Sources</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_3.html">previous</A>, <A HREF="gettext_5.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_3.html">previous</A>, <A HREF="gettext_5.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
<H1><A NAME="SEC11" HREF="gettext_toc.html#TOC11">4 Preparing Program Sources</A></H1>
<P>
-<A NAME="IDX96"></A>
+<A NAME="IDX102"></A>
</P>
known to all modules needing message translation. Second, you should
properly trigger the operation of GNU <CODE>gettext</CODE> when the program
initializes, usually from the <CODE>main</CODE> function. Last, you should
-identify and especially mark all constant strings in your program
+identify, adjust and mark all constant strings in your program
needing translation.
</P>
+
+
+
+<H2><A NAME="SEC12" HREF="gettext_toc.html#TOC12">4.1 Importing the <CODE>gettext</CODE> declaration</A></H2>
+
<P>
Presuming that your set of programs, or package, has been adjusted
so all needed GNU <CODE>gettext</CODE> files are available, and your
-<TT>`Makefile´</TT> files are adjusted (see section <A HREF="gettext_13.html#SEC194">13 The Maintainer's View</A>), each C module
+<TT>‘Makefile’</TT> files are adjusted (see section <A HREF="gettext_13.html#SEC196">13 The Maintainer's View</A>), each C module
having translated C strings should contain the line:
</P>
<P>
-<A NAME="IDX97"></A>
+<A NAME="IDX103"></A>
<PRE>
#include <libintl.h>
#include <libintl.h>
</PRE>
-<P>
-The remaining changes to your C sources are discussed in the further
-sections of this chapter.
-
-</P>
-
-<H2><A NAME="SEC12" HREF="gettext_toc.html#TOC12">4.1 Triggering <CODE>gettext</CODE> Operations</A></H2>
+<H2><A NAME="SEC13" HREF="gettext_toc.html#TOC13">4.2 Triggering <CODE>gettext</CODE> Operations</A></H2>
<P>
-<A NAME="IDX98"></A>
+<A NAME="IDX104"></A>
The initialization of locale data should be done with more or less
the same code in every program, as demonstrated below:
<P>
<VAR>PACKAGE</VAR> and <VAR>LOCALEDIR</VAR> should be provided either by
-<TT>`config.h´</TT> or by the Makefile. For now consult the <CODE>gettext</CODE>
+<TT>‘config.h’</TT> or by the Makefile. For now consult the <CODE>gettext</CODE>
or <CODE>hello</CODE> sources for more information.
</P>
<P>
-<A NAME="IDX99"></A>
-<A NAME="IDX100"></A>
+<A NAME="IDX105"></A>
+<A NAME="IDX106"></A>
The use of <CODE>LC_ALL</CODE> might not be appropriate for you.
<CODE>LC_ALL</CODE> includes all locale categories and especially
<CODE>LC_CTYPE</CODE>. This later category is responsible for determining
character classes with the <CODE>isalnum</CODE> etc. functions from
-<TT>`ctype.h´</TT> which could especially for programs, which process some
+<TT>‘ctype.h’</TT> which could especially for programs, which process some
kind of input language, be wrong. For example this would mean that a
source code using the ç (c-cedilla character) is runnable in
France but not in the U.S.
</PRE>
<P>
-<A NAME="IDX101"></A>
-<A NAME="IDX102"></A>
-<A NAME="IDX103"></A>
-<A NAME="IDX104"></A>
-<A NAME="IDX105"></A>
-<A NAME="IDX106"></A>
<A NAME="IDX107"></A>
+<A NAME="IDX108"></A>
+<A NAME="IDX109"></A>
+<A NAME="IDX110"></A>
+<A NAME="IDX111"></A>
+<A NAME="IDX112"></A>
+<A NAME="IDX113"></A>
On all POSIX conformant systems the locale categories <CODE>LC_CTYPE</CODE>,
<CODE>LC_MESSAGES</CODE>, <CODE>LC_COLLATE</CODE>, <CODE>LC_MONETARY</CODE>,
<CODE>LC_NUMERIC</CODE>, and <CODE>LC_TIME</CODE> are available. On some systems
</P>
-<H2><A NAME="SEC13" HREF="gettext_toc.html#TOC13">4.2 Preparing Translatable Strings</A></H2>
+<H2><A NAME="SEC14" HREF="gettext_toc.html#TOC14">4.3 Preparing Translatable Strings</A></H2>
<P>
-<A NAME="IDX108"></A>
+<A NAME="IDX114"></A>
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
</P>
<P>
-<A NAME="IDX109"></A>
+<A NAME="IDX115"></A>
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.
</P>
<P>
-<A NAME="IDX110"></A>
+<A NAME="IDX116"></A>
In both cases, adding more words to the message will help both the
translator and the English speaking user.
</P>
<P>
-<A NAME="IDX111"></A>
+<A NAME="IDX117"></A>
Translatable strings should be entire sentences. It is often not possible
to translate single verbs or adjectives in a substitutable way.
<P>
This way the translator will not only understand the message, she will
-also be able to find the appropriate grammatical construction. The French
+also be able to find the appropriate grammatical construction. A French
translator for example translates "write protected" like "protected
against writing".
</P>
<P>
-<A NAME="IDX112"></A>
+<A NAME="IDX118"></A>
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
</P>
<P>
-<A NAME="IDX113"></A>
-Many GNU programs have a <SAMP>`--help´</SAMP> output that extends over several
+<A NAME="IDX119"></A>
+Many GNU programs have a <SAMP>‘--help’</SAMP> 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,
</P>
<P>
-<A NAME="IDX114"></A>
-<A NAME="IDX115"></A>
+<A NAME="IDX120"></A>
+<A NAME="IDX121"></A>
Hardcoded string concatenation is sometimes used to construct English
strings:
</PRE>
<P>
-<A NAME="IDX116"></A>
+<A NAME="IDX122"></A>
A similar case is compile time concatenation of strings. The ISO C 99
include file <CODE><inttypes.h></CODE> contains a macro <CODE>PRId64</CODE> that
-can be used as a formatting directive for outputting an <SAMP>`int64_t´</SAMP>
+can be used as a formatting directive for outputting an <SAMP>‘int64_t’</SAMP>
integer through <CODE>printf</CODE>. 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
</P>
<P>
This works only for the predefined <CODE><inttypes.h></CODE> macros. If
-you have defined your own similar macros, let's say <SAMP>`MYPRId64´</SAMP>,
+you have defined your own similar macros, let's say <SAMP>‘MYPRId64’</SAMP>,
that are not known to <CODE>xgettext</CODE>, the solution for this problem
is to change the code like this:
</P>
<P>
-<A NAME="IDX117"></A>
-<A NAME="IDX118"></A>
+<A NAME="IDX123"></A>
+<A NAME="IDX124"></A>
All this applies to other programming languages as well. For example, in
Java and C#, string contenation is very frequently used, because it is a
compiler built-in operator. Like in C, in Java, you would change
-<H2><A NAME="SEC14" HREF="gettext_toc.html#TOC14">4.3 How Marks Appear in Sources</A></H2>
+<H2><A NAME="SEC15" HREF="gettext_toc.html#TOC15">4.4 How Marks Appear in Sources</A></H2>
<P>
-<A NAME="IDX119"></A>
+<A NAME="IDX125"></A>
</P>
<P>
attached to strings themselves, rather than to what we do with them.
This approach has more uses. A blatant example is an error message
produced by formatting. The format string needs translation, as
-well as some strings inserted through some <SAMP>`%s´</SAMP> specification
+well as some strings inserted through some <SAMP>‘%s’</SAMP> specification
in the format, while the result from <CODE>sprintf</CODE> may have so many
different instances that it is impractical to list them all in some
-<SAMP>`error_string_out()´</SAMP> routine, say.
+<SAMP>‘error_string_out()’</SAMP> routine, say.
</P>
<P>
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 <A HREF="gettext_4.html#SEC17">4.6 Special Cases of Translatable Strings</A>.
+strings appear in structured initializations. See section <A HREF="gettext_4.html#SEC18">4.7 Special Cases of Translatable Strings</A>.
</P>
<P>
</P>
<P>
The canonical keyword for marking translatable strings is
-<SAMP>`gettext´</SAMP>, it gave its name to the whole GNU <CODE>gettext</CODE>
-package. For packages making only light use of the <SAMP>`gettext´</SAMP>
+<SAMP>‘gettext’</SAMP>, it gave its name to the whole GNU <CODE>gettext</CODE>
+package. For packages making only light use of the <SAMP>‘gettext’</SAMP>
keyword, macro or function, it is easily used <EM>as is</EM>. However,
for packages using the <CODE>gettext</CODE> interface more heavily, it
is usually more convenient to give the main keyword a shorter, less
</P>
<P>
-<A NAME="IDX120"></A>
-Many packages use <SAMP>`_´</SAMP> (a simple underline) as a keyword,
-and write <SAMP>`_("Translatable string")´</SAMP> instead of <SAMP>`gettext
-("Translatable string")´</SAMP>. Further, the coding rule, from GNU standards,
+<A NAME="IDX126"></A>
+Many packages use <SAMP>‘_’</SAMP> (a simple underline) as a keyword,
+and write <SAMP>‘_("Translatable string")’</SAMP> instead of <SAMP>‘gettext
+("Translatable string")’</SAMP>. Further, the coding rule, from GNU standards,
wanting that there is a space between the keyword and the opening
parenthesis is relaxed, in practice, for this particular usage.
So, the textual overhead per translatable string is reduced to
only three characters: the underline and the two parentheses.
However, even if GNU <CODE>gettext</CODE> uses this convention internally,
it does not offer it officially. The real, genuine keyword is truly
-<SAMP>`gettext´</SAMP> indeed. It is fairly easy for those wanting to use
-<SAMP>`_´</SAMP> instead of <SAMP>`gettext´</SAMP> to declare:
+<SAMP>‘gettext’</SAMP> indeed. It is fairly easy for those wanting to use
+<SAMP>‘_’</SAMP> instead of <SAMP>‘gettext’</SAMP> to declare:
</P>
</PRE>
<P>
-instead of merely using <SAMP>`#include <libintl.h>´</SAMP>.
+instead of merely using <SAMP>‘#include <libintl.h>’</SAMP>.
</P>
<P>
Later on, the maintenance is relatively easy. If, as a programmer,
you add or modify a string, you will have to ask yourself if the
new or altered string requires translation, and include it within
-<SAMP>`_()´</SAMP> if you think it should be translated. <SAMP>`"%s: %d"´</SAMP> is
+<SAMP>‘_()’</SAMP> if you think it should be translated. <SAMP>‘"%s: %d"’</SAMP> is
an example of string <EM>not</EM> requiring translation!
</P>
-<H2><A NAME="SEC15" HREF="gettext_toc.html#TOC15">4.4 Marking Translatable Strings</A></H2>
+<H2><A NAME="SEC16" HREF="gettext_toc.html#TOC16">4.5 Marking Translatable Strings</A></H2>
<P>
-<A NAME="IDX121"></A>
+<A NAME="IDX127"></A>
</P>
<P>
</P>
<P>
-<A NAME="IDX122"></A>
+<A NAME="IDX128"></A>
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
</PRE>
<P>
-presuming here you want to process all <TT>`.h´</TT> and <TT>`.c´</TT> files
-from the <TT>`src/´</TT> and <TT>`lib/´</TT> directories. This command will
-explore all said files and create a <TT>`TAGS´</TT> file in your root
+presuming here you want to process all <TT>‘.h’</TT> and <TT>‘.c’</TT> files
+from the <TT>‘src/’</TT> and <TT>‘lib/’</TT> directories. This command will
+explore all said files and create a <TT>‘TAGS’</TT> file in your root
directory, somewhat summarizing the contents using a special file
format Emacs can understand.
</P>
<P>
-<A NAME="IDX123"></A>
+<A NAME="IDX129"></A>
For packages following the GNU coding standards, there is
a make goal <CODE>tags</CODE> or <CODE>TAGS</CODE> which constructs the tag files in
all directories and for all files containing source code.
</P>
<P>
-Once your <TT>`TAGS´</TT> file is ready, the following commands assist
+Once your <TT>‘TAGS’</TT> file is ready, the following commands assist
the programmer at marking translatable strings in his set of sources.
But these commands are necessarily driven from within a PO file
window, and it is likely that you do not even have such a PO file yet.
<DT><KBD>,</KBD>
<DD>
-<A NAME="IDX124"></A>
+<A NAME="IDX130"></A>
Search through program sources for a string which looks like a
candidate for translation (<CODE>po-tags-search</CODE>).
<DT><KBD>M-,</KBD>
<DD>
-<A NAME="IDX125"></A>
-Mark the last string found with <SAMP>`_()´</SAMP> (<CODE>po-mark-translatable</CODE>).
+<A NAME="IDX131"></A>
+Mark the last string found with <SAMP>‘_()’</SAMP> (<CODE>po-mark-translatable</CODE>).
<DT><KBD>M-.</KBD>
<DD>
-<A NAME="IDX126"></A>
+<A NAME="IDX132"></A>
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 (<CODE>po-select-mark-and-mark</CODE>).
</DL>
<P>
-<A NAME="IDX127"></A>
+<A NAME="IDX133"></A>
The <KBD>,</KBD> (<CODE>po-tags-search</CODE>) 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,
</P>
<P>
-If you have never told Emacs about some <TT>`TAGS´</TT> file to use, the
+If you have never told Emacs about some <TT>‘TAGS’</TT> file to use, the
command will request that you specify one from the minibuffer, the
-first time you use the command. You may later change your <TT>`TAGS´</TT>
+first time you use the command. You may later change your <TT>‘TAGS’</TT>
file by using the regular Emacs command <KBD>M-x visit-tags-table</KBD>,
-which will ask you to name the precise <TT>`TAGS´</TT> file you want
-to use. See section `Tag Tables' in <CITE>The Emacs Editor</CITE>.
+which will ask you to name the precise <TT>‘TAGS’</TT> file you want
+to use. See section ‘Tag Tables’ in <CITE>The Emacs Editor</CITE>.
</P>
<P>
Each time you use the <KBD>,</KBD> command, the search resumes from where it was
left by the previous search, and goes through all program sources,
-obeying the <TT>`TAGS´</TT> file, until all sources have been processed.
+obeying the <TT>‘TAGS’</TT> file, until all sources have been processed.
However, by giving a prefix argument to the command (<KBD>C-u
,)</KBD>, you may request that the search be restarted all over again
from the first program source; but in this case, strings that you
</P>
<P>
-<A NAME="IDX128"></A>
-<A NAME="IDX129"></A>
+<A NAME="IDX134"></A>
+<A NAME="IDX135"></A>
The <KBD>M-,</KBD> (<CODE>po-mark-translatable</CODE>) command will mark the
-recently found string with the <SAMP>`_´</SAMP> keyword. The <KBD>M-.</KBD>
+recently found string with the <SAMP>‘_’</SAMP> keyword. The <KBD>M-.</KBD>
(<CODE>po-select-mark-and-mark</CODE>) command will request that you type
one keyword from the minibuffer and use that keyword for marking
the string. Both commands will automatically create a new PO file
There is no provision in PO mode, currently, for deleting a known
keyword, you have to quit the file (maybe using <KBD>q</KBD>) and reopen
it afresh. When a PO file is newly brought up in an Emacs window, only
-<SAMP>`gettext´</SAMP> and <SAMP>`_´</SAMP> are known as keywords, and <SAMP>`gettext´</SAMP>
+<SAMP>‘gettext’</SAMP> and <SAMP>‘_’</SAMP> are known as keywords, and <SAMP>‘gettext’</SAMP>
is preferred for the <KBD>M-.</KBD> command. In fact, this is not useful to
-prefer <SAMP>`_´</SAMP>, as this one is already built in the <KBD>M-,</KBD> command.
+prefer <SAMP>‘_’</SAMP>, as this one is already built in the <KBD>M-,</KBD> command.
</P>
-<H2><A NAME="SEC16" HREF="gettext_toc.html#TOC16">4.5 Special Comments preceding Keywords</A></H2>
+<H2><A NAME="SEC17" HREF="gettext_toc.html#TOC17">4.6 Special Comments preceding Keywords</A></H2>
<P>
-<A NAME="IDX130"></A>
+<A NAME="IDX136"></A>
In C programs strings are often used within calls of functions from the
<CODE>printf</CODE> family. The special thing about these format strings is
that they can contain format specifiers introduced with <KBD>%</KBD>. Assume
To prevent errors at runtime caused by translations the <CODE>msgfmt</CODE>
tool can check statically whether the arguments in the original and the
translation string match in type and number. If this is not the case
-and the <SAMP>`-c´</SAMP> option has been passed to <CODE>msgfmt</CODE>, <CODE>msgfmt</CODE>
+and the <SAMP>‘-c’</SAMP> option has been passed to <CODE>msgfmt</CODE>, <CODE>msgfmt</CODE>
will give an error and refuse to produce a MO file. Thus consequent
-use of <SAMP>`msgfmt -c´</SAMP> will catch the error, so that it cannot cause
+use of <SAMP>‘msgfmt -c’</SAMP> will catch the error, so that it cannot cause
cause problems at runtime.
</P>
</P>
<P>
Because not all strings in a program must be format strings it is not
-useful for <CODE>msgfmt</CODE> to test all the strings in the <TT>`.po´</TT> file.
+useful for <CODE>msgfmt</CODE> to test all the strings in the <TT>‘.po’</TT> file.
This might cause problems because the string might contain what looks
like a format specifier, but the string is not used in <CODE>printf</CODE>.
<P>
Therefore the <CODE>xgettext</CODE> adds a special tag to those messages it
thinks might be a format string. There is no absolute rule for this,
-only a heuristic. In the <TT>`.po´</TT> file the entry is marked using the
+only a heuristic. In the <TT>‘.po’</TT> file the entry is marked using the
<CODE>c-format</CODE> flag in the <CODE>#,</CODE> comment line (see section <A HREF="gettext_3.html#SEC10">3 The Format of PO Files</A>).
</P>
<P>
-<A NAME="IDX131"></A>
-<A NAME="IDX132"></A>
+<A NAME="IDX137"></A>
+<A NAME="IDX138"></A>
The careful reader now might say that this again can cause problems.
The heuristic might guess it wrong. This is true and therefore
<CODE>xgettext</CODE> knows about a special kind of comment which lets
<CODE>xgettext</CODE> of course could make a wrong decision the other way
round, i.e. a string marked as a format string actually is not a format
string. In this case the <CODE>msgfmt</CODE> might give too many warnings and
-would prevent translating the <TT>`.po´</TT> file. The method to prevent
+would prevent translating the <TT>‘.po’</TT> file. The method to prevent
this wrong decision is similar to the one used above, only the comment
to use must contain the string <CODE>xgettext:no-c-format</CODE>.
<P>
If a string is marked with <CODE>c-format</CODE> and this is not correct the
user can find out who is responsible for the decision. See
-section <A HREF="gettext_5.html#SEC21">5.1 Invoking the <CODE>xgettext</CODE> Program</A> to see how the <CODE>--debug</CODE> option can be
+section <A HREF="gettext_5.html#SEC22">5.1 Invoking the <CODE>xgettext</CODE> Program</A> to see how the <CODE>--debug</CODE> option can be
used for solving this problem.
</P>
-<H2><A NAME="SEC17" HREF="gettext_toc.html#TOC17">4.6 Special Cases of Translatable Strings</A></H2>
+<H2><A NAME="SEC18" HREF="gettext_toc.html#TOC18">4.7 Special Cases of Translatable Strings</A></H2>
<P>
-<A NAME="IDX133"></A>
+<A NAME="IDX139"></A>
The attentive reader might now point out that it is not always possible
to mark translatable string with <CODE>gettext</CODE> or something like this.
Consider the following case:
While it is no problem to mark the string <CODE>"a default message"</CODE> it
is not possible to mark the string initializers for <CODE>messages</CODE>.
What is to be done? We have to fulfill two tasks. First we have to mark the
-strings so that the <CODE>xgettext</CODE> program (see section <A HREF="gettext_5.html#SEC21">5.1 Invoking the <CODE>xgettext</CODE> Program</A>)
+strings so that the <CODE>xgettext</CODE> program (see section <A HREF="gettext_5.html#SEC22">5.1 Invoking the <CODE>xgettext</CODE> Program</A>)
can find them, and second we have to translate the string at runtime
before printing them.
<P>
Please convince yourself that the string which is written by
<CODE>fputs</CODE> is translated in any case. How to get <CODE>xgettext</CODE> know
-the additional keyword <CODE>gettext_noop</CODE> is explained in section <A HREF="gettext_5.html#SEC21">5.1 Invoking the <CODE>xgettext</CODE> Program</A>.
+the additional keyword <CODE>gettext_noop</CODE> is explained in section <A HREF="gettext_5.html#SEC22">5.1 Invoking the <CODE>xgettext</CODE> Program</A>.
</P>
<P>
</P>
-<H2><A NAME="SEC18" HREF="gettext_toc.html#TOC18">4.7 Marking Proper Names for Translation</A></H2>
+<H2><A NAME="SEC19" HREF="gettext_toc.html#TOC19">4.8 Marking Proper Names for Translation</A></H2>
<P>
Should names of persons, cities, locations etc. be marked for translation
or not? People who only know languages that can be written with Latin
-letters (English, Spanish, French, German, etc.) are tempted to say "no",
+letters (English, Spanish, French, German, etc.) are tempted to say “no”,
because names usually do not change when transported between these languages.
However, in general when translating from one script to another, names
are translated too, usually phonetically or by transliteration. For
</P>
-<H2><A NAME="SEC19" HREF="gettext_toc.html#TOC19">4.8 Preparing Library Sources</A></H2>
+<H2><A NAME="SEC20" HREF="gettext_toc.html#TOC20">4.9 Preparing Library Sources</A></H2>
<P>
When you are preparing a library, not a program, for the use of
<LI>
-The usual declaration of the <SAMP>`_´</SAMP> macro in each source file was
+The usual declaration of the <SAMP>‘_’</SAMP> macro in each source file was
<PRE>
</OL>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_3.html">previous</A>, <A HREF="gettext_5.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_3.html">previous</A>, <A HREF="gettext_5.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 5 Making the PO Template File</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_4.html">previous</A>, <A HREF="gettext_6.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_4.html">previous</A>, <A HREF="gettext_6.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC20" HREF="gettext_toc.html#TOC20">5 Making the PO Template File</A></H1>
+<H1><A NAME="SEC21" HREF="gettext_toc.html#TOC21">5 Making the PO Template File</A></H1>
<P>
-<A NAME="IDX134"></A>
+<A NAME="IDX140"></A>
</P>
<P>
</P>
<P>
-<CODE>xgettext</CODE> creates a file named <TT>`<VAR>domainname</VAR>.po´</TT>. You
-should then rename it to <TT>`<VAR>domainname</VAR>.pot´</TT>. (Why doesn't
-<CODE>xgettext</CODE> create it under the name <TT>`<VAR>domainname</VAR>.pot´</TT>
+<CODE>xgettext</CODE> creates a file named <TT>‘<VAR>domainname</VAR>.po’</TT>. You
+should then rename it to <TT>‘<VAR>domainname</VAR>.pot’</TT>. (Why doesn't
+<CODE>xgettext</CODE> create it under the name <TT>‘<VAR>domainname</VAR>.pot’</TT>
right away? The answer is: for historical reasons. When <CODE>xgettext</CODE>
was specified, the distinction between a PO file and PO file template
-was fuzzy, and the suffix <SAMP>`.pot´</SAMP> wasn't in use at that time.)
+was fuzzy, and the suffix <SAMP>‘.pot’</SAMP> wasn't in use at that time.)
</P>
-<H2><A NAME="SEC21" HREF="gettext_toc.html#TOC21">5.1 Invoking the <CODE>xgettext</CODE> Program</A></H2>
+<H2><A NAME="SEC22" HREF="gettext_toc.html#TOC22">5.1 Invoking the <CODE>xgettext</CODE> Program</A></H2>
<P>
-<A NAME="IDX135"></A>
-<A NAME="IDX136"></A>
+<A NAME="IDX141"></A>
+<A NAME="IDX142"></A>
<PRE>
xgettext [<VAR>option</VAR>] [<VAR>inputfile</VAR>] ...
</P>
-<H3><A NAME="SEC22" HREF="gettext_toc.html#TOC22">5.1.1 Input file location</A></H3>
+<H3><A NAME="SEC23" HREF="gettext_toc.html#TOC23">5.1.1 Input file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`<VAR>inputfile</VAR> ...´</SAMP>
+<DT><SAMP>‘<VAR>inputfile</VAR> ...’</SAMP>
<DD>
Input files.
-<DT><SAMP>`-f <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-f <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--files-from=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--files-from=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX137"></A>
-<A NAME="IDX138"></A>
+<A NAME="IDX143"></A>
+<A NAME="IDX144"></A>
Read the names of the input files from <VAR>file</VAR> instead of getting
them from the command line.
-<DT><SAMP>`-D <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-D <VAR>directory</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--directory=<VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘--directory=<VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX139"></A>
-<A NAME="IDX140"></A>
+<A NAME="IDX145"></A>
+<A NAME="IDX146"></A>
Add <VAR>directory</VAR> to the list of directories. Source files are
-searched relative to this list of directories. The resulting <TT>`.po´</TT>
+searched relative to this list of directories. The resulting <TT>‘.po’</TT>
file will be written relative to the current directory, though.
</DL>
<P>
-If <VAR>inputfile</VAR> is <SAMP>`-´</SAMP>, standard input is read.
+If <VAR>inputfile</VAR> is <SAMP>‘-’</SAMP>, standard input is read.
</P>
-<H3><A NAME="SEC23" HREF="gettext_toc.html#TOC23">5.1.2 Output file location</A></H3>
+<H3><A NAME="SEC24" HREF="gettext_toc.html#TOC24">5.1.2 Output file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`-d <VAR>name</VAR>´</SAMP>
+<DT><SAMP>‘-d <VAR>name</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--default-domain=<VAR>name</VAR>´</SAMP>
+<DT><SAMP>‘--default-domain=<VAR>name</VAR>’</SAMP>
<DD>
-<A NAME="IDX141"></A>
-<A NAME="IDX142"></A>
-Use <TT>`<VAR>name</VAR>.po´</TT> for output (instead of <TT>`messages.po´</TT>).
+<A NAME="IDX147"></A>
+<A NAME="IDX148"></A>
+Use <TT>‘<VAR>name</VAR>.po’</TT> for output (instead of <TT>‘messages.po’</TT>).
-<DT><SAMP>`-o <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-o <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--output=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--output=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX143"></A>
-<A NAME="IDX144"></A>
-Write output to specified file (instead of <TT>`<VAR>name</VAR>.po´</TT> or
-<TT>`messages.po´</TT>).
+<A NAME="IDX149"></A>
+<A NAME="IDX150"></A>
+Write output to specified file (instead of <TT>‘<VAR>name</VAR>.po’</TT> or
+<TT>‘messages.po’</TT>).
-<DT><SAMP>`-p <VAR>dir</VAR>´</SAMP>
+<DT><SAMP>‘-p <VAR>dir</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--output-dir=<VAR>dir</VAR>´</SAMP>
+<DT><SAMP>‘--output-dir=<VAR>dir</VAR>’</SAMP>
<DD>
-<A NAME="IDX145"></A>
-<A NAME="IDX146"></A>
+<A NAME="IDX151"></A>
+<A NAME="IDX152"></A>
Output files will be placed in directory <VAR>dir</VAR>.
</DL>
<P>
-<A NAME="IDX147"></A>
-If the output <VAR>file</VAR> is <SAMP>`-´</SAMP> or <SAMP>`/dev/stdout´</SAMP>, the output
+<A NAME="IDX153"></A>
+If the output <VAR>file</VAR> is <SAMP>‘-’</SAMP> or <SAMP>‘/dev/stdout’</SAMP>, the output
is written to standard output.
</P>
-<H3><A NAME="SEC24" HREF="gettext_toc.html#TOC24">5.1.3 Choice of input file language</A></H3>
+<H3><A NAME="SEC25" HREF="gettext_toc.html#TOC25">5.1.3 Choice of input file language</A></H3>
<DL COMPACT>
-<DT><SAMP>`-L <VAR>name</VAR>´</SAMP>
+<DT><SAMP>‘-L <VAR>name</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--language=<VAR>name</VAR>´</SAMP>
+<DT><SAMP>‘--language=<VAR>name</VAR>’</SAMP>
<DD>
-<A NAME="IDX148"></A>
-<A NAME="IDX149"></A>
-<A NAME="IDX150"></A>
+<A NAME="IDX154"></A>
+<A NAME="IDX155"></A>
+<A NAME="IDX156"></A>
Specifies the language of the input files. The supported languages
are <CODE>C</CODE>, <CODE>C++</CODE>, <CODE>ObjectiveC</CODE>, <CODE>PO</CODE>, <CODE>Python</CODE>,
<CODE>Lisp</CODE>, <CODE>EmacsLisp</CODE>, <CODE>librep</CODE>, <CODE>Scheme</CODE>, <CODE>Smalltalk</CODE>,
<CODE>Tcl</CODE>, <CODE>Perl</CODE>, <CODE>PHP</CODE>, <CODE>GCC-source</CODE>, <CODE>NXStringTable</CODE>,
<CODE>RST</CODE>, <CODE>Glade</CODE>.
-<DT><SAMP>`-C´</SAMP>
+<DT><SAMP>‘-C’</SAMP>
<DD>
-<DT><SAMP>`--c++´</SAMP>
+<DT><SAMP>‘--c++’</SAMP>
<DD>
-<A NAME="IDX151"></A>
-<A NAME="IDX152"></A>
+<A NAME="IDX157"></A>
+<A NAME="IDX158"></A>
This is a shorthand for <CODE>--language=C++</CODE>.
</DL>
</P>
-<H3><A NAME="SEC25" HREF="gettext_toc.html#TOC25">5.1.4 Input file interpretation</A></H3>
+<H3><A NAME="SEC26" HREF="gettext_toc.html#TOC26">5.1.4 Input file interpretation</A></H3>
<DL COMPACT>
-<DT><SAMP>`--from-code=<VAR>name</VAR>´</SAMP>
+<DT><SAMP>‘--from-code=<VAR>name</VAR>’</SAMP>
<DD>
-<A NAME="IDX153"></A>
+<A NAME="IDX159"></A>
Specifies the encoding of the input files. This option is needed only
if some untranslated message strings or their corresponding comments
-contain non-ASCII characters. Note that Python, Tcl, and Glade input
-files are always assumed to be in UTF-8, regardless of this option.
+contain non-ASCII characters. Note that Tcl and Glade input files are
+always assumed to be in UTF-8, regardless of this option.
</DL>
</P>
-<H3><A NAME="SEC26" HREF="gettext_toc.html#TOC26">5.1.5 Operation mode</A></H3>
+<H3><A NAME="SEC27" HREF="gettext_toc.html#TOC27">5.1.5 Operation mode</A></H3>
<DL COMPACT>
-<DT><SAMP>`-j´</SAMP>
+<DT><SAMP>‘-j’</SAMP>
<DD>
-<DT><SAMP>`--join-existing´</SAMP>
+<DT><SAMP>‘--join-existing’</SAMP>
<DD>
-<A NAME="IDX154"></A>
-<A NAME="IDX155"></A>
+<A NAME="IDX160"></A>
+<A NAME="IDX161"></A>
Join messages with existing file.
-<DT><SAMP>`-x <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-x <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--exclude-file=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--exclude-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX156"></A>
-<A NAME="IDX157"></A>
+<A NAME="IDX162"></A>
+<A NAME="IDX163"></A>
Entries from <VAR>file</VAR> are not extracted. <VAR>file</VAR> should be a PO or
POT file.
-<DT><SAMP>`-c [<VAR>tag</VAR>]´</SAMP>
+<DT><SAMP>‘-c [<VAR>tag</VAR>]’</SAMP>
<DD>
-<DT><SAMP>`--add-comments[=<VAR>tag</VAR>]´</SAMP>
+<DT><SAMP>‘--add-comments[=<VAR>tag</VAR>]’</SAMP>
<DD>
-<A NAME="IDX158"></A>
-<A NAME="IDX159"></A>
+<A NAME="IDX164"></A>
+<A NAME="IDX165"></A>
Place comment block with <VAR>tag</VAR> (or those preceding keyword lines)
in output file.
-<H3><A NAME="SEC27" HREF="gettext_toc.html#TOC27">5.1.6 Language specific options</A></H3>
+<H3><A NAME="SEC28" HREF="gettext_toc.html#TOC28">5.1.6 Language specific options</A></H3>
<DL COMPACT>
-<DT><SAMP>`-a´</SAMP>
+<DT><SAMP>‘-a’</SAMP>
<DD>
-<DT><SAMP>`--extract-all´</SAMP>
+<DT><SAMP>‘--extract-all’</SAMP>
<DD>
-<A NAME="IDX160"></A>
-<A NAME="IDX161"></A>
+<A NAME="IDX166"></A>
+<A NAME="IDX167"></A>
Extract all strings.
This option has an effect with most languages, namely C, C++, ObjectiveC,
Shell, Python, Lisp, EmacsLisp, librep, Java, C#, awk, Tcl, Perl, PHP,
GCC-source, Glade.
-<DT><SAMP>`-k <VAR>keywordspec</VAR>´</SAMP>
+<DT><SAMP>‘-k <VAR>keywordspec</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--keyword[=<VAR>keywordspec</VAR>]´</SAMP>
+<DT><SAMP>‘--keyword[=<VAR>keywordspec</VAR>]’</SAMP>
<DD>
-<A NAME="IDX162"></A>
-<A NAME="IDX163"></A>
+<A NAME="IDX168"></A>
+<A NAME="IDX169"></A>
Additional keyword to be looked for (without <VAR>keywordspec</VAR> means not to
use default keywords).
-<A NAME="IDX164"></A>
+<A NAME="IDX170"></A>
+<A NAME="IDX171"></A>
If <VAR>keywordspec</VAR> is a C identifer <VAR>id</VAR>, <CODE>xgettext</CODE> looks
for strings in the first argument of each call to the function or macro
<VAR>id</VAR>. If <VAR>keywordspec</VAR> is of the form
-<SAMP>`<VAR>id</VAR>:<VAR>argnum</VAR>´</SAMP>, <CODE>xgettext</CODE> looks for strings in the
+<SAMP>‘<VAR>id</VAR>:<VAR>argnum</VAR>’</SAMP>, <CODE>xgettext</CODE> looks for strings in the
<VAR>argnum</VAR>th argument of the call. If <VAR>keywordspec</VAR> is of the form
-<SAMP>`<VAR>id</VAR>:<VAR>argnum1</VAR>,<VAR>argnum2</VAR>´</SAMP>, <CODE>xgettext</CODE> looks for
+<SAMP>‘<VAR>id</VAR>:<VAR>argnum1</VAR>,<VAR>argnum2</VAR>’</SAMP>, <CODE>xgettext</CODE> looks for
strings in the <VAR>argnum1</VAR>st argument and in the <VAR>argnum2</VAR>nd argument
of the call, and treats them as singular/plural variants for a message
-with plural handling.
+with plural handling. Also, if <VAR>keywordspec</VAR> is of the form
+<SAMP>‘<VAR>id</VAR>:<VAR>contextargnum</VAR>c,<VAR>argnum</VAR>’</SAMP> or
+<SAMP>‘<VAR>id</VAR>:<VAR>argnum</VAR>,<VAR>contextargnum</VAR>c’</SAMP>, <CODE>xgettext</CODE> treats
+strings in the <VAR>contextargnum</VAR>th argument as a context specifier.
+And, as a special-purpose support for GNOME, if <VAR>keywordspec</VAR> is of the
+form <SAMP>‘<VAR>id</VAR>:<VAR>argnum</VAR>g’</SAMP>, <CODE>xgettext</CODE> recognizes the
+<VAR>argnum</VAR>th argument as a string with context, using the GNOME <CODE>glib</CODE>
+syntax <SAMP>‘"msgctxt|msgid"’</SAMP>.
<BR>
-The default keyword specifications, which are always looked for if not
-explicitly disabled, are <CODE>gettext</CODE>, <CODE>dgettext:2</CODE>,
-<CODE>dcgettext:2</CODE>, <CODE>ngettext:1,2</CODE>, <CODE>dngettext:2,3</CODE>,
-<CODE>dcngettext:2,3</CODE>, and <CODE>gettext_noop</CODE>.
+Furthermore, if <VAR>keywordspec</VAR> is of the form
+<SAMP>‘<VAR>id</VAR>:...,<VAR>totalnumargs</VAR>t’</SAMP>, <CODE>xgettext</CODE> recognizes this
+argument specification only if the number of actual arguments is equal to
+<VAR>totalnumargs</VAR>. This is useful for disambiguating overloaded function
+calls in C++.
<BR>
+Finally, if <VAR>keywordspec</VAR> is of the form
+<SAMP>‘<VAR>id</VAR>:<VAR>argnum</VAR>...,"<VAR>xcomment</VAR>"’</SAMP>, <CODE>xgettext</CODE>, when
+extracting a message from the specified argument strings, adds an extracted
+comment <VAR>xcomment</VAR> to the message. Note that when used through a normal
+shell command line, the double-quotes around the <VAR>xcomment</VAR> need to be
+escaped.
+
This option has an effect with most languages, namely C, C++, ObjectiveC,
Shell, Python, Lisp, EmacsLisp, librep, Java, C#, awk, Tcl, Perl, PHP,
GCC-source, Glade.
-<DT><SAMP>`--flag=<VAR>word</VAR>:<VAR>arg</VAR>:<VAR>flag</VAR>´</SAMP>
+The default keyword specifications, which are always looked for if not
+explicitly disabled, are language dependent. They are:
+
+
+<UL>
+<LI>
+
+For C, C++, and GCC-source: <CODE>gettext</CODE>, <CODE>dgettext:2</CODE>,
+<CODE>dcgettext:2</CODE>, <CODE>ngettext:1,2</CODE>, <CODE>dngettext:2,3</CODE>,
+<CODE>dcngettext:2,3</CODE>, <CODE>gettext_noop</CODE>, and <CODE>pgettext:1c,2</CODE>,
+<CODE>dpgettext:2c,3</CODE>, <CODE>dcpgettext:2c,3</CODE>, <CODE>npgettext:1c,2,3</CODE>,
+<CODE>dnpgettext:2c,3,4</CODE>, <CODE>dcnpgettext:2c,3,4</CODE>.
+
+<LI>
+
+For Objective C: Like for C, and also <CODE>NSLocalizedString</CODE>, <CODE>_</CODE>,
+<CODE>NSLocalizedStaticString</CODE>, <CODE>__</CODE>.
+
+<LI>
+
+For Shell scripts: <CODE>gettext</CODE>, <CODE>ngettext:1,2</CODE>, <CODE>eval_gettext</CODE>,
+<CODE>eval_ngettext:1,2</CODE>.
+
+<LI>
+
+For Python: <CODE>gettext</CODE>, <CODE>ugettext</CODE>, <CODE>dgettext:2</CODE>,
+<CODE>ngettext:1,2</CODE>, <CODE>ungettext:1,2</CODE>, <CODE>dngettext:2,3</CODE>, <CODE>_</CODE>.
+
+<LI>
+
+For Lisp: <CODE>gettext</CODE>, <CODE>ngettext:1,2</CODE>, <CODE>gettext-noop</CODE>.
+
+<LI>
+
+For EmacsLisp: <CODE>_</CODE>.
+
+<LI>
+
+For librep: <CODE>_</CODE>.
+
+<LI>
+
+For Scheme: <CODE>gettext</CODE>, <CODE>ngettext:1,2</CODE>, <CODE>gettext-noop</CODE>.
+
+<LI>
+
+For Java: <CODE>GettextResource.gettext:2</CODE>,
+<CODE>GettextResource.ngettext:2,3</CODE>, <CODE>gettext</CODE>, <CODE>ngettext:1,2</CODE>,
+<CODE>getString</CODE>.
+
+<LI>
+
+For C#: <CODE>GetString</CODE>, <CODE>GetPluralString:1,2</CODE>.
+
+<LI>
+
+For awk: <CODE>dcgettext</CODE>, <CODE>dcngettext:1,2</CODE>.
+
+<LI>
+
+For Tcl: <CODE>::msgcat::mc</CODE>.
+
+<LI>
+
+For Perl: <CODE>gettext</CODE>, <CODE>%gettext</CODE>, <CODE>$gettext</CODE>, <CODE>dgettext:2</CODE>,
+<CODE>dcgettext:2</CODE>, <CODE>ngettext:1,2</CODE>, <CODE>dngettext:2,3</CODE>,
+<CODE>dcngettext:2,3</CODE>, <CODE>gettext_noop</CODE>.
+
+<LI>
+
+For PHP: <CODE>_</CODE>, <CODE>gettext</CODE>, <CODE>dgettext:2</CODE>, <CODE>dcgettext:2</CODE>,
+<CODE>ngettext:1,2</CODE>, <CODE>dngettext:2,3</CODE>, <CODE>dcngettext:2,3</CODE>.
+
+<LI>
+
+For Glade 1: <CODE>label</CODE>, <CODE>title</CODE>, <CODE>text</CODE>, <CODE>format</CODE>,
+<CODE>copyright</CODE>, <CODE>comments</CODE>, <CODE>preview_text</CODE>, <CODE>tooltip</CODE>.
+</UL>
+
+To disable the default keyword specifications, the option <SAMP>‘-k’</SAMP> or
+<SAMP>‘--keyword’</SAMP> or <SAMP>‘--keyword=’</SAMP>, without a <VAR>keywordspec</VAR>, can be
+used.
+
+<DT><SAMP>‘--flag=<VAR>word</VAR>:<VAR>arg</VAR>:<VAR>flag</VAR>’</SAMP>
<DD>
-<A NAME="IDX165"></A>
+<A NAME="IDX172"></A>
Specifies additional flags for strings occurring as part of the <VAR>arg</VAR>th
argument of the function <VAR>word</VAR>. The possible flags are the possible
-format string indicators, such as <SAMP>`c-format´</SAMP>, and their negations,
-such as <SAMP>`no-c-format´</SAMP>, possibly prefixed with <SAMP>`pass-´</SAMP>.
+format string indicators, such as <SAMP>‘c-format’</SAMP>, and their negations,
+such as <SAMP>‘no-c-format’</SAMP>, possibly prefixed with <SAMP>‘pass-’</SAMP>.
<BR>
-<A NAME="IDX166"></A>
+<A NAME="IDX173"></A>
The meaning of <CODE>--flag=<VAR>function</VAR>:<VAR>arg</VAR>:<VAR>lang</VAR>-format</CODE>
is that in language <VAR>lang</VAR>, the specified <VAR>function</VAR> expects as
<VAR>arg</VAR>th argument a format string. (For those of you familiar with
GCC function attributes, <CODE>--flag=<VAR>function</VAR>:<VAR>arg</VAR>:c-format</CODE> is
roughly equivalent to the declaration
-<SAMP>`__attribute__ ((__format__ (__printf__, <VAR>arg</VAR>, ...)))´</SAMP> attached
+<SAMP>‘__attribute__ ((__format__ (__printf__, <VAR>arg</VAR>, ...)))’</SAMP> attached
to <VAR>function</VAR> in a C source file.)
-For example, if you use the <SAMP>`error´</SAMP> function from GNU libc, you can
+For example, if you use the <SAMP>‘error’</SAMP> function from GNU libc, you can
specify its behaviour through <CODE>--flag=error:3:c-format</CODE>. The effect of
this specification is that <CODE>xgettext</CODE> will mark as format strings all
<CODE>gettext</CODE> invocations that occur as <VAR>arg</VAR>th argument of
<VAR>function</VAR>.
This is useful when such strings contain no format string directives:
-together with the checks done by <SAMP>`msgfmt -c´</SAMP> it will ensure that
+together with the checks done by <SAMP>‘msgfmt -c’</SAMP> it will ensure that
translators cannot accidentally use format string directives that would
lead to a crash at runtime.
<BR>
-<A NAME="IDX167"></A>
+<A NAME="IDX174"></A>
The meaning of <CODE>--flag=<VAR>function</VAR>:<VAR>arg</VAR>:pass-<VAR>lang</VAR>-format</CODE>
is that in language <VAR>lang</VAR>, if the <VAR>function</VAR> call occurs in a
position that must yield a format string, then its <VAR>arg</VAR>th argument
must yield a format string of the same type as well. (If you know GCC
function attributes, the <CODE>--flag=<VAR>function</VAR>:<VAR>arg</VAR>:pass-c-format</CODE>
option is roughly equivalent to the declaration
-<SAMP>`__attribute__ ((__format_arg__ (<VAR>arg</VAR>)))´</SAMP> attached to <VAR>function</VAR>
+<SAMP>‘__attribute__ ((__format_arg__ (<VAR>arg</VAR>)))’</SAMP> attached to <VAR>function</VAR>
in a C source file.)
-For example, if you use the <SAMP>`_´</SAMP> shortcut for the <CODE>gettext</CODE> function,
+For example, if you use the <SAMP>‘_’</SAMP> shortcut for the <CODE>gettext</CODE> function,
you should use <CODE>--flag=_:1:pass-c-format</CODE>. The effect of this
specification is that <CODE>xgettext</CODE> will propagate a format string
requirement for a <CODE>_("string")</CODE> call to its first argument, the literal
<CODE>"string"</CODE>, and thus mark it as a format string.
This is useful when such strings contain no format string directives:
-together with the checks done by <SAMP>`msgfmt -c´</SAMP> it will ensure that
+together with the checks done by <SAMP>‘msgfmt -c’</SAMP> it will ensure that
translators cannot accidentally use format string directives that would
lead to a crash at runtime.
<BR>
Shell, Python, Lisp, EmacsLisp, librep, Scheme, Java, C#, awk, YCP, Tcl, Perl, PHP,
GCC-source.
-<DT><SAMP>`-T´</SAMP>
+<DT><SAMP>‘-T’</SAMP>
<DD>
-<DT><SAMP>`--trigraphs´</SAMP>
+<DT><SAMP>‘--trigraphs’</SAMP>
<DD>
-<A NAME="IDX168"></A>
-<A NAME="IDX169"></A>
-<A NAME="IDX170"></A>
+<A NAME="IDX175"></A>
+<A NAME="IDX176"></A>
+<A NAME="IDX177"></A>
Understand ANSI C trigraphs for input.
<BR>
This option has an effect only with the languages C, C++, ObjectiveC.
-<DT><SAMP>`--qt´</SAMP>
+<DT><SAMP>‘--qt’</SAMP>
<DD>
-<A NAME="IDX171"></A>
-<A NAME="IDX172"></A>
+<A NAME="IDX178"></A>
+<A NAME="IDX179"></A>
Recognize Qt format strings.
<BR>
This option has an effect only with the language C++.
-<DT><SAMP>`--debug´</SAMP>
+<DT><SAMP>‘--boost’</SAMP>
<DD>
-<A NAME="IDX173"></A>
-<A NAME="IDX174"></A>
+<A NAME="IDX180"></A>
+<A NAME="IDX181"></A>
+Recognize Boost format strings.
+<BR>
+This option has an effect only with the language C++.
+
+<DT><SAMP>‘--debug’</SAMP>
+<DD>
+<A NAME="IDX182"></A>
+<A NAME="IDX183"></A>
Use the flags <CODE>c-format</CODE> and <CODE>possible-c-format</CODE> to show who was
responsible for marking a message as a format string. The latter form is
used if the <CODE>xgettext</CODE> program decided, the format form is used if
</P>
-<H3><A NAME="SEC28" HREF="gettext_toc.html#TOC28">5.1.7 Output details</A></H3>
+<H3><A NAME="SEC29" HREF="gettext_toc.html#TOC29">5.1.7 Output details</A></H3>
<DL COMPACT>
-<DT><SAMP>`--force-po´</SAMP>
+<DT><SAMP>‘--force-po’</SAMP>
<DD>
-<A NAME="IDX175"></A>
+<A NAME="IDX184"></A>
Always write an output file even if no message is defined.
-<DT><SAMP>`-i´</SAMP>
+<DT><SAMP>‘-i’</SAMP>
<DD>
-<DT><SAMP>`--indent´</SAMP>
+<DT><SAMP>‘--indent’</SAMP>
<DD>
-<A NAME="IDX176"></A>
-<A NAME="IDX177"></A>
+<A NAME="IDX185"></A>
+<A NAME="IDX186"></A>
Write the .po file using indented style.
-<DT><SAMP>`--no-location´</SAMP>
+<DT><SAMP>‘--no-location’</SAMP>
<DD>
-<A NAME="IDX178"></A>
-Do not write <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines.
+<A NAME="IDX187"></A>
+Do not write <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines.
-<DT><SAMP>`-n´</SAMP>
+<DT><SAMP>‘-n’</SAMP>
<DD>
-<DT><SAMP>`--add-location´</SAMP>
+<DT><SAMP>‘--add-location’</SAMP>
<DD>
-<A NAME="IDX179"></A>
-<A NAME="IDX180"></A>
-Generate <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines (default).
+<A NAME="IDX188"></A>
+<A NAME="IDX189"></A>
+Generate <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines (default).
-<DT><SAMP>`--strict´</SAMP>
+<DT><SAMP>‘--strict’</SAMP>
<DD>
-<A NAME="IDX181"></A>
+<A NAME="IDX190"></A>
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
-<DT><SAMP>`--properties-output´</SAMP>
+<DT><SAMP>‘--properties-output’</SAMP>
<DD>
-<A NAME="IDX182"></A>
+<A NAME="IDX191"></A>
Write out a Java ResourceBundle in Java <CODE>.properties</CODE> syntax. Note
that this file format doesn't support plural forms and silently drops
obsolete messages.
-<DT><SAMP>`--stringtable-output´</SAMP>
+<DT><SAMP>‘--stringtable-output’</SAMP>
<DD>
-<A NAME="IDX183"></A>
+<A NAME="IDX192"></A>
Write out a NeXTstep/GNUstep localized resource file in <CODE>.strings</CODE> syntax.
Note that this file format doesn't support plural forms.
-<DT><SAMP>`-w <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-w <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--width=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--width=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX184"></A>
-<A NAME="IDX185"></A>
+<A NAME="IDX193"></A>
+<A NAME="IDX194"></A>
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 <VAR>number</VAR>.
-<DT><SAMP>`--no-wrap´</SAMP>
+<DT><SAMP>‘--no-wrap’</SAMP>
<DD>
-<A NAME="IDX186"></A>
+<A NAME="IDX195"></A>
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.
-<DT><SAMP>`-s´</SAMP>
+<DT><SAMP>‘-s’</SAMP>
<DD>
-<DT><SAMP>`--sort-output´</SAMP>
+<DT><SAMP>‘--sort-output’</SAMP>
<DD>
-<A NAME="IDX187"></A>
-<A NAME="IDX188"></A>
-<A NAME="IDX189"></A>
+<A NAME="IDX196"></A>
+<A NAME="IDX197"></A>
+<A NAME="IDX198"></A>
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
-<DT><SAMP>`-F´</SAMP>
+<DT><SAMP>‘-F’</SAMP>
<DD>
-<DT><SAMP>`--sort-by-file´</SAMP>
+<DT><SAMP>‘--sort-by-file’</SAMP>
<DD>
-<A NAME="IDX190"></A>
-<A NAME="IDX191"></A>
+<A NAME="IDX199"></A>
+<A NAME="IDX200"></A>
Sort output by file location.
-<DT><SAMP>`--omit-header´</SAMP>
+<DT><SAMP>‘--omit-header’</SAMP>
<DD>
-<A NAME="IDX192"></A>
-Don't write header with <SAMP>`msgid ""´</SAMP> entry.
+<A NAME="IDX201"></A>
+Don't write header with <SAMP>‘msgid ""’</SAMP> entry.
-<A NAME="IDX193"></A>
+<A NAME="IDX202"></A>
This is useful for testing purposes because it eliminates a source
of variance for generated <CODE>.gmo</CODE> files. With <CODE>--omit-header</CODE>,
two invocations of <CODE>xgettext</CODE> on the same files with the same
options at different times are guaranteed to produce the same results.
-<DT><SAMP>`--copyright-holder=<VAR>string</VAR>´</SAMP>
+<DT><SAMP>‘--copyright-holder=<VAR>string</VAR>’</SAMP>
<DD>
-<A NAME="IDX194"></A>
+<A NAME="IDX203"></A>
Set the copyright holder in the output. <VAR>string</VAR> should be the
copyright holder of the surrounding package. (Note that the msgstr
strings, extracted from the package's sources, belong to the copyright
The default value for <VAR>string</VAR> is the Free Software Foundation, Inc.,
simply because <CODE>xgettext</CODE> was first used in the GNU project.
-<DT><SAMP>`--foreign-user´</SAMP>
+<DT><SAMP>‘--foreign-user’</SAMP>
<DD>
-<A NAME="IDX195"></A>
+<A NAME="IDX204"></A>
Omit FSF copyright in output. This option is equivalent to
-<SAMP>`--copyright-holder="´</SAMP>. It can be useful for packages outside the GNU
+<SAMP>‘--copyright-holder=”’</SAMP>. It can be useful for packages outside the GNU
project that want their translations to be in the public domain.
-<DT><SAMP>`--msgid-bugs-address=<VAR>email@address</VAR>´</SAMP>
+<DT><SAMP>‘--msgid-bugs-address=<VAR>email@address</VAR>’</SAMP>
<DD>
-<A NAME="IDX196"></A>
+<A NAME="IDX205"></A>
Set the reporting address for msgid bugs. This is the email address or URL
to which the translators shall report bugs in the untranslated strings:
<UL>
<LI>Strings which are not entire sentences, see the maintainer guidelines
-in section <A HREF="gettext_4.html#SEC13">4.2 Preparing Translatable Strings</A>.
+in section <A HREF="gettext_4.html#SEC14">4.3 Preparing Translatable Strings</A>.
<LI>Strings which use unclear terms or require additional context to be
understood.
The default value is empty, which means that translators will be clueless!
Don't forget to specify this option.
-<DT><SAMP>`-m [<VAR>string</VAR>]´</SAMP>
+<DT><SAMP>‘-m [<VAR>string</VAR>]’</SAMP>
<DD>
-<DT><SAMP>`--msgstr-prefix[=<VAR>string</VAR>]´</SAMP>
+<DT><SAMP>‘--msgstr-prefix[=<VAR>string</VAR>]’</SAMP>
<DD>
-<A NAME="IDX197"></A>
-<A NAME="IDX198"></A>
+<A NAME="IDX206"></A>
+<A NAME="IDX207"></A>
Use <VAR>string</VAR> (or "" if not specified) as prefix for msgstr entries.
-<DT><SAMP>`-M [<VAR>string</VAR>]´</SAMP>
+<DT><SAMP>‘-M [<VAR>string</VAR>]’</SAMP>
<DD>
-<DT><SAMP>`--msgstr-suffix[=<VAR>string</VAR>]´</SAMP>
+<DT><SAMP>‘--msgstr-suffix[=<VAR>string</VAR>]’</SAMP>
<DD>
-<A NAME="IDX199"></A>
-<A NAME="IDX200"></A>
+<A NAME="IDX208"></A>
+<A NAME="IDX209"></A>
Use <VAR>string</VAR> (or "" if not specified) as suffix for msgstr entries.
</DL>
-<H3><A NAME="SEC29" HREF="gettext_toc.html#TOC29">5.1.8 Informative output</A></H3>
+<H3><A NAME="SEC30" HREF="gettext_toc.html#TOC30">5.1.8 Informative output</A></H3>
<DL COMPACT>
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX201"></A>
-<A NAME="IDX202"></A>
+<A NAME="IDX210"></A>
+<A NAME="IDX211"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX203"></A>
-<A NAME="IDX204"></A>
+<A NAME="IDX212"></A>
+<A NAME="IDX213"></A>
Output version information and exit.
</DL>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_4.html">previous</A>, <A HREF="gettext_6.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_4.html">previous</A>, <A HREF="gettext_6.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 6 Creating a New PO File</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_5.html">previous</A>, <A HREF="gettext_7.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_5.html">previous</A>, <A HREF="gettext_7.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC30" HREF="gettext_toc.html#TOC30">6 Creating a New PO File</A></H1>
+<H1><A NAME="SEC31" HREF="gettext_toc.html#TOC31">6 Creating a New PO File</A></H1>
<P>
-<A NAME="IDX205"></A>
+<A NAME="IDX214"></A>
</P>
<P>
When starting a new translation, the translator creates a file called
-<TT>`<VAR>LANG</VAR>.po´</TT>, as a copy of the <TT>`<VAR>package</VAR>.pot´</TT> template
+<TT>‘<VAR>LANG</VAR>.po’</TT>, as a copy of the <TT>‘<VAR>package</VAR>.pot’</TT> template
file with modifications in the initial comments (at the beginning of the file)
and in the header entry (the first entry, near the beginning of the file).
</P>
<P>
-The easiest way to do so is by use of the <SAMP>`msginit´</SAMP> program.
+The easiest way to do so is by use of the <SAMP>‘msginit’</SAMP> program.
For example:
</P>
<P>
The alternative way is to do the copy and modifications by hand.
-To do so, the translator copies <TT>`<VAR>package</VAR>.pot´</TT> to
-<TT>`<VAR>LANG</VAR>.po´</TT>. Then she modifies the initial comments and
+To do so, the translator copies <TT>‘<VAR>package</VAR>.pot’</TT> to
+<TT>‘<VAR>LANG</VAR>.po’</TT>. Then she modifies the initial comments and
the header entry of this file.
</P>
-<H2><A NAME="SEC31" HREF="gettext_toc.html#TOC31">6.1 Invoking the <CODE>msginit</CODE> Program</A></H2>
+<H2><A NAME="SEC32" HREF="gettext_toc.html#TOC32">6.1 Invoking the <CODE>msginit</CODE> Program</A></H2>
<P>
-<A NAME="IDX206"></A>
-<A NAME="IDX207"></A>
+<A NAME="IDX215"></A>
+<A NAME="IDX216"></A>
<PRE>
msginit [<VAR>option</VAR>]
</PRE>
<P>
-<A NAME="IDX208"></A>
-<A NAME="IDX209"></A>
+<A NAME="IDX217"></A>
+<A NAME="IDX218"></A>
The <CODE>msginit</CODE> program creates a new PO file, initializing the meta
information with values from the user's environment.
</P>
-<H3><A NAME="SEC32" HREF="gettext_toc.html#TOC32">6.1.1 Input file location</A></H3>
+<H3><A NAME="SEC33" HREF="gettext_toc.html#TOC33">6.1.1 Input file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`-i <VAR>inputfile</VAR>´</SAMP>
+<DT><SAMP>‘-i <VAR>inputfile</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--input=<VAR>inputfile</VAR>´</SAMP>
+<DT><SAMP>‘--input=<VAR>inputfile</VAR>’</SAMP>
<DD>
-<A NAME="IDX210"></A>
-<A NAME="IDX211"></A>
+<A NAME="IDX219"></A>
+<A NAME="IDX220"></A>
Input POT file.
</DL>
<P>
If no <VAR>inputfile</VAR> is given, the current directory is searched for the
-POT file. If it is <SAMP>`-´</SAMP>, standard input is read.
+POT file. If it is <SAMP>‘-’</SAMP>, standard input is read.
</P>
-<H3><A NAME="SEC33" HREF="gettext_toc.html#TOC33">6.1.2 Output file location</A></H3>
+<H3><A NAME="SEC34" HREF="gettext_toc.html#TOC34">6.1.2 Output file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`-o <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-o <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--output-file=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--output-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX212"></A>
-<A NAME="IDX213"></A>
+<A NAME="IDX221"></A>
+<A NAME="IDX222"></A>
Write output to specified PO file.
</DL>
<P>
-If no output file is given, it depends on the <SAMP>`--locale´</SAMP> option or the
-user's locale setting. If it is <SAMP>`-´</SAMP>, the results are written to
+If no output file is given, it depends on the <SAMP>‘--locale’</SAMP> option or the
+user's locale setting. If it is <SAMP>‘-’</SAMP>, the results are written to
standard output.
</P>
-<H3><A NAME="SEC34" HREF="gettext_toc.html#TOC34">6.1.3 Input file syntax</A></H3>
+<H3><A NAME="SEC35" HREF="gettext_toc.html#TOC35">6.1.3 Input file syntax</A></H3>
<DL COMPACT>
-<DT><SAMP>`-P´</SAMP>
+<DT><SAMP>‘-P’</SAMP>
<DD>
-<DT><SAMP>`--properties-input´</SAMP>
+<DT><SAMP>‘--properties-input’</SAMP>
<DD>
-<A NAME="IDX214"></A>
-<A NAME="IDX215"></A>
+<A NAME="IDX223"></A>
+<A NAME="IDX224"></A>
Assume the input file is a Java ResourceBundle in Java <CODE>.properties</CODE>
syntax, not in PO file syntax.
-<DT><SAMP>`--stringtable-input´</SAMP>
+<DT><SAMP>‘--stringtable-input’</SAMP>
<DD>
-<A NAME="IDX216"></A>
+<A NAME="IDX225"></A>
Assume the input file is a NeXTstep/GNUstep localized resource file in
<CODE>.strings</CODE> syntax, not in PO file syntax.
-<H3><A NAME="SEC35" HREF="gettext_toc.html#TOC35">6.1.4 Output details</A></H3>
+<H3><A NAME="SEC36" HREF="gettext_toc.html#TOC36">6.1.4 Output details</A></H3>
<DL COMPACT>
-<DT><SAMP>`-l <VAR>ll_CC</VAR>´</SAMP>
+<DT><SAMP>‘-l <VAR>ll_CC</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--locale=<VAR>ll_CC</VAR>´</SAMP>
+<DT><SAMP>‘--locale=<VAR>ll_CC</VAR>’</SAMP>
<DD>
-<A NAME="IDX217"></A>
-<A NAME="IDX218"></A>
+<A NAME="IDX226"></A>
+<A NAME="IDX227"></A>
Set target locale. <VAR>ll</VAR> should be a language code, and <VAR>CC</VAR> should
-be a country code. The command <SAMP>`locale -a´</SAMP> can be used to output a list
+be a country code. The command <SAMP>‘locale -a’</SAMP> can be used to output a list
of all installed locales. The default is the user's locale setting.
-<DT><SAMP>`--no-translator´</SAMP>
+<DT><SAMP>‘--no-translator’</SAMP>
<DD>
-<A NAME="IDX219"></A>
+<A NAME="IDX228"></A>
Declares that the PO file will not have a human translator and is instead
automatically generated.
-<DT><SAMP>`-p´</SAMP>
+<DT><SAMP>‘-p’</SAMP>
<DD>
-<DT><SAMP>`--properties-output´</SAMP>
+<DT><SAMP>‘--properties-output’</SAMP>
<DD>
-<A NAME="IDX220"></A>
-<A NAME="IDX221"></A>
+<A NAME="IDX229"></A>
+<A NAME="IDX230"></A>
Write out a Java ResourceBundle in Java <CODE>.properties</CODE> syntax. Note
that this file format doesn't support plural forms and silently drops
obsolete messages.
-<DT><SAMP>`--stringtable-output´</SAMP>
+<DT><SAMP>‘--stringtable-output’</SAMP>
<DD>
-<A NAME="IDX222"></A>
+<A NAME="IDX231"></A>
Write out a NeXTstep/GNUstep localized resource file in <CODE>.strings</CODE> syntax.
Note that this file format doesn't support plural forms.
-<DT><SAMP>`-w <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-w <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--width=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--width=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX223"></A>
-<A NAME="IDX224"></A>
+<A NAME="IDX232"></A>
+<A NAME="IDX233"></A>
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 <VAR>number</VAR>.
-<DT><SAMP>`--no-wrap´</SAMP>
+<DT><SAMP>‘--no-wrap’</SAMP>
<DD>
-<A NAME="IDX225"></A>
+<A NAME="IDX234"></A>
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.
-<H3><A NAME="SEC36" HREF="gettext_toc.html#TOC36">6.1.5 Informative output</A></H3>
+<H3><A NAME="SEC37" HREF="gettext_toc.html#TOC37">6.1.5 Informative output</A></H3>
<DL COMPACT>
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX226"></A>
-<A NAME="IDX227"></A>
+<A NAME="IDX235"></A>
+<A NAME="IDX236"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX228"></A>
-<A NAME="IDX229"></A>
+<A NAME="IDX237"></A>
+<A NAME="IDX238"></A>
Output version information and exit.
</DL>
-<H2><A NAME="SEC37" HREF="gettext_toc.html#TOC37">6.2 Filling in the Header Entry</A></H2>
+<H2><A NAME="SEC38" HREF="gettext_toc.html#TOC38">6.2 Filling in the Header Entry</A></H2>
<P>
-<A NAME="IDX230"></A>
+<A NAME="IDX239"></A>
</P>
<P>
<UL>
<LI>Strings which are not entire sentences, see the maintainer guidelines
-in section <A HREF="gettext_4.html#SEC13">4.2 Preparing Translatable Strings</A>.
+in section <A HREF="gettext_4.html#SEC14">4.3 Preparing Translatable Strings</A>.
<LI>Strings which use unclear terms or require additional context to be
understood.
<DT>PO-Revision-Date
<DD>
-You don't need to fill this in. It will be filled by the Emacs PO mode
+You don't need to fill this in. It will be filled by the PO file editor
when you save the file.
<DT>Last-Translator
your translation team, not only to make sure you don't do duplicated work,
but also to coordinate difficult linguistic issues.
-<A NAME="IDX231"></A>
+<A NAME="IDX240"></A>
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, <A HREF="http://www.iro.umontreal.ca/contrib/po/HTML/">http://www.iro.umontreal.ca/contrib/po/HTML/</A>,
<DT>Content-Type
<DD>
-<A NAME="IDX232"></A>
-<A NAME="IDX233"></A>
-Replace <SAMP>`CHARSET´</SAMP> with the character encoding used for your language,
+<A NAME="IDX241"></A>
+<A NAME="IDX242"></A>
+Replace <SAMP>‘CHARSET’</SAMP> with the character encoding used for your language,
in your locale, or UTF-8. This field is needed for correct operation of the
<CODE>msgmerge</CODE> and <CODE>msgfmt</CODE> programs, as well as for users whose
-locale's character encoding differs from yours (see section <A HREF="gettext_11.html#SEC170">11.2.4 How to specify the output character set <CODE>gettext</CODE> uses</A>).
+locale's character encoding differs from yours (see section <A HREF="gettext_11.html#SEC172">11.2.4 How to specify the output character set <CODE>gettext</CODE> uses</A>).
-<A NAME="IDX234"></A>
+<A NAME="IDX243"></A>
You get the character encoding of your locale by running the shell command
-<SAMP>`locale charmap´</SAMP>. If the result is <SAMP>`C´</SAMP> or <SAMP>`ANSI_X3.4-1968´</SAMP>,
-which is equivalent to <SAMP>`ASCII´</SAMP> (= <SAMP>`US-ASCII´</SAMP>), it means that your
+<SAMP>‘locale charmap’</SAMP>. If the result is <SAMP>‘C’</SAMP> or <SAMP>‘ANSI_X3.4-1968’</SAMP>,
+which is equivalent to <SAMP>‘ASCII’</SAMP> (= <SAMP>‘US-ASCII’</SAMP>), it means that your
locale is not correctly configured. In this case, ask your translation
-team which charset to use. <SAMP>`ASCII´</SAMP> is not usable for any language
+team which charset to use. <SAMP>‘ASCII’</SAMP> is not usable for any language
except Latin.
-<A NAME="IDX235"></A>
+<A NAME="IDX244"></A>
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 <CODE>libc</CODE> and GNU
<CODE>BIG5</CODE>, <CODE>BIG5-HKSCS</CODE>, <CODE>GBK</CODE>, <CODE>GB18030</CODE>, <CODE>SHIFT_JIS</CODE>,
<CODE>JOHAB</CODE>, <CODE>TIS-620</CODE>, <CODE>VISCII</CODE>, <CODE>GEORGIAN-PS</CODE>, <CODE>UTF-8</CODE>.
-<A NAME="IDX236"></A>
+<A NAME="IDX245"></A>
In the GNU system, the following encodings are frequently used for the
corresponding languages.
-<A NAME="IDX237"></A>
+<A NAME="IDX246"></A>
<UL>
<LI><CODE>ISO-8859-1</CODE> for
</UL>
-<A NAME="IDX238"></A>
-<A NAME="IDX239"></A>
+<A NAME="IDX247"></A>
+<A NAME="IDX248"></A>
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
vertical apostrophe and the vertical double quote instead (because that's
what the character set conversion will transliterate them to).
-<A NAME="IDX240"></A>
+<A NAME="IDX249"></A>
To enter such quote characters under X11, you can change your keyboard
mapping using the <CODE>xmodmap</CODE> program. The X11 names of the quote
characters are "leftsinglequotemark", "rightsinglequotemark",
<DT>Plural-Forms
<DD>
This field is optional. It is only needed if the PO file has plural forms.
-You can find them by searching for the <SAMP>`msgid_plural´</SAMP> keyword. The
-format of the plural forms field is described in section <A HREF="gettext_11.html#SEC171">11.2.5 Additional functions for plural forms</A>.
+You can find them by searching for the <SAMP>‘msgid_plural’</SAMP> keyword. The
+format of the plural forms field is described in section <A HREF="gettext_11.html#SEC174">11.2.6 Additional functions for plural forms</A>.
</DL>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_5.html">previous</A>, <A HREF="gettext_7.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_5.html">previous</A>, <A HREF="gettext_7.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 7 Updating Existing PO Files</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_6.html">previous</A>, <A HREF="gettext_8.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_6.html">previous</A>, <A HREF="gettext_8.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC38" HREF="gettext_toc.html#TOC38">7 Updating Existing PO Files</A></H1>
+<H1><A NAME="SEC39" HREF="gettext_toc.html#TOC39">7 Updating Existing PO Files</A></H1>
-<H2><A NAME="SEC39" HREF="gettext_toc.html#TOC39">7.1 Invoking the <CODE>msgmerge</CODE> Program</A></H2>
+<H2><A NAME="SEC40" HREF="gettext_toc.html#TOC40">7.1 Invoking the <CODE>msgmerge</CODE> Program</A></H2>
<P>
-<A NAME="IDX241"></A>
-<A NAME="IDX242"></A>
+<A NAME="IDX250"></A>
+<A NAME="IDX251"></A>
<PRE>
msgmerge [<VAR>option</VAR>] <VAR>def</VAR>.po <VAR>ref</VAR>.pot
</P>
-<H3><A NAME="SEC40" HREF="gettext_toc.html#TOC40">7.1.1 Input file location</A></H3>
+<H3><A NAME="SEC41" HREF="gettext_toc.html#TOC41">7.1.1 Input file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`<VAR>def</VAR>.po´</SAMP>
+<DT><SAMP>‘<VAR>def</VAR>.po’</SAMP>
<DD>
Translations referring to old sources.
-<DT><SAMP>`<VAR>ref</VAR>.pot´</SAMP>
+<DT><SAMP>‘<VAR>ref</VAR>.pot’</SAMP>
<DD>
References to the new sources.
-<DT><SAMP>`-D <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-D <VAR>directory</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--directory=<VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘--directory=<VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX243"></A>
-<A NAME="IDX244"></A>
+<A NAME="IDX252"></A>
+<A NAME="IDX253"></A>
Add <VAR>directory</VAR> to the list of directories. Source files are
-searched relative to this list of directories. The resulting <TT>`.po´</TT>
+searched relative to this list of directories. The resulting <TT>‘.po’</TT>
file will be written relative to the current directory, though.
-<DT><SAMP>`-C <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-C <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--compendium=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--compendium=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX245"></A>
-<A NAME="IDX246"></A>
-Specify an additional library of message translations. See section <A HREF="gettext_8.html#SEC65">8.3.14 Using Translation Compendia</A>.
+<A NAME="IDX254"></A>
+<A NAME="IDX255"></A>
+Specify an additional library of message translations. See section <A HREF="gettext_8.html#SEC66">8.3.14 Using Translation Compendia</A>.
This option may be specified more than once.
</DL>
-<H3><A NAME="SEC41" HREF="gettext_toc.html#TOC41">7.1.2 Operation mode</A></H3>
+<H3><A NAME="SEC42" HREF="gettext_toc.html#TOC42">7.1.2 Operation mode</A></H3>
<DL COMPACT>
-<DT><SAMP>`-U´</SAMP>
+<DT><SAMP>‘-U’</SAMP>
<DD>
-<DT><SAMP>`--update´</SAMP>
+<DT><SAMP>‘--update’</SAMP>
<DD>
-<A NAME="IDX247"></A>
-<A NAME="IDX248"></A>
+<A NAME="IDX256"></A>
+<A NAME="IDX257"></A>
Update <VAR>def</VAR>.po. Do nothing if <VAR>def</VAR>.po is already up to date.
</DL>
-<H3><A NAME="SEC42" HREF="gettext_toc.html#TOC42">7.1.3 Output file location</A></H3>
+<H3><A NAME="SEC43" HREF="gettext_toc.html#TOC43">7.1.3 Output file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`-o <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-o <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--output-file=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--output-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX249"></A>
-<A NAME="IDX250"></A>
+<A NAME="IDX258"></A>
+<A NAME="IDX259"></A>
Write output to specified file.
</DL>
<P>
-<A NAME="IDX251"></A>
+<A NAME="IDX260"></A>
The results are written to standard output if no output file is specified
-or if it is <SAMP>`-´</SAMP>.
+or if it is <SAMP>‘-’</SAMP>.
</P>
-<H3><A NAME="SEC43" HREF="gettext_toc.html#TOC43">7.1.4 Output file location in update mode</A></H3>
+<H3><A NAME="SEC44" HREF="gettext_toc.html#TOC44">7.1.4 Output file location in update mode</A></H3>
<P>
The result is written back to <VAR>def</VAR>.po.
</P>
<DL COMPACT>
-<DT><SAMP>`--backup=<VAR>control</VAR>´</SAMP>
+<DT><SAMP>‘--backup=<VAR>control</VAR>’</SAMP>
<DD>
-<A NAME="IDX252"></A>
-<A NAME="IDX253"></A>
+<A NAME="IDX261"></A>
+<A NAME="IDX262"></A>
Make a backup of <VAR>def</VAR>.po
-<DT><SAMP>`--suffix=<VAR>suffix</VAR>´</SAMP>
+<DT><SAMP>‘--suffix=<VAR>suffix</VAR>’</SAMP>
<DD>
-<A NAME="IDX254"></A>
+<A NAME="IDX263"></A>
Override the usual backup suffix.
</DL>
<P>
-<A NAME="IDX255"></A>
+<A NAME="IDX264"></A>
The version control method may be selected via the <CODE>--backup</CODE> option
or through the <CODE>VERSION_CONTROL</CODE> environment variable. Here are the
values:
</P>
<DL COMPACT>
-<DT><SAMP>`none´</SAMP>
+<DT><SAMP>‘none’</SAMP>
<DD>
-<DT><SAMP>`off´</SAMP>
+<DT><SAMP>‘off’</SAMP>
<DD>
Never make backups (even if <CODE>--backup</CODE> is given).
-<DT><SAMP>`numbered´</SAMP>
+<DT><SAMP>‘numbered’</SAMP>
<DD>
-<DT><SAMP>`t´</SAMP>
+<DT><SAMP>‘t’</SAMP>
<DD>
Make numbered backups.
-<DT><SAMP>`existing´</SAMP>
+<DT><SAMP>‘existing’</SAMP>
<DD>
-<DT><SAMP>`nil´</SAMP>
+<DT><SAMP>‘nil’</SAMP>
<DD>
Make numbered backups if numbered backups for this file already exist,
otherwise make simple backups.
-<DT><SAMP>`simple´</SAMP>
+<DT><SAMP>‘simple’</SAMP>
<DD>
-<DT><SAMP>`never´</SAMP>
+<DT><SAMP>‘never’</SAMP>
<DD>
Always make simple backups.
</DL>
<P>
-The backup suffix is <SAMP>`~´</SAMP>, unless set with <CODE>--suffix</CODE> or the
+The backup suffix is <SAMP>‘~’</SAMP>, unless set with <CODE>--suffix</CODE> or the
<CODE>SIMPLE_BACKUP_SUFFIX</CODE> environment variable.
</P>
-<H3><A NAME="SEC44" HREF="gettext_toc.html#TOC44">7.1.5 Operation modifiers</A></H3>
+<H3><A NAME="SEC45" HREF="gettext_toc.html#TOC45">7.1.5 Operation modifiers</A></H3>
<DL COMPACT>
-<DT><SAMP>`-m´</SAMP>
+<DT><SAMP>‘-m’</SAMP>
<DD>
-<DT><SAMP>`--multi-domain´</SAMP>
+<DT><SAMP>‘--multi-domain’</SAMP>
<DD>
-<A NAME="IDX256"></A>
-<A NAME="IDX257"></A>
+<A NAME="IDX265"></A>
+<A NAME="IDX266"></A>
Apply <VAR>ref</VAR>.pot to each of the domains in <VAR>def</VAR>.po.
-<DT><SAMP>`-N´</SAMP>
+<DT><SAMP>‘-N’</SAMP>
<DD>
-<DT><SAMP>`--no-fuzzy-matching´</SAMP>
+<DT><SAMP>‘--no-fuzzy-matching’</SAMP>
<DD>
-<A NAME="IDX258"></A>
-<A NAME="IDX259"></A>
+<A NAME="IDX267"></A>
+<A NAME="IDX268"></A>
Do not use fuzzy matching when an exact match is not found. This may speed
up the operation considerably.
</DL>
-<H3><A NAME="SEC45" HREF="gettext_toc.html#TOC45">7.1.6 Input file syntax</A></H3>
+<H3><A NAME="SEC46" HREF="gettext_toc.html#TOC46">7.1.6 Input file syntax</A></H3>
<DL COMPACT>
-<DT><SAMP>`-P´</SAMP>
+<DT><SAMP>‘-P’</SAMP>
<DD>
-<DT><SAMP>`--properties-input´</SAMP>
+<DT><SAMP>‘--properties-input’</SAMP>
<DD>
-<A NAME="IDX260"></A>
-<A NAME="IDX261"></A>
+<A NAME="IDX269"></A>
+<A NAME="IDX270"></A>
Assume the input files are Java ResourceBundles in Java <CODE>.properties</CODE>
syntax, not in PO file syntax.
-<DT><SAMP>`--stringtable-input´</SAMP>
+<DT><SAMP>‘--stringtable-input’</SAMP>
<DD>
-<A NAME="IDX262"></A>
+<A NAME="IDX271"></A>
Assume the input files are NeXTstep/GNUstep localized resource files in
<CODE>.strings</CODE> syntax, not in PO file syntax.
-<H3><A NAME="SEC46" HREF="gettext_toc.html#TOC46">7.1.7 Output details</A></H3>
+<H3><A NAME="SEC47" HREF="gettext_toc.html#TOC47">7.1.7 Output details</A></H3>
<DL COMPACT>
-<DT><SAMP>`--force-po´</SAMP>
+<DT><SAMP>‘--force-po’</SAMP>
<DD>
-<A NAME="IDX263"></A>
+<A NAME="IDX272"></A>
Always write an output file even if it contains no message.
-<DT><SAMP>`-i´</SAMP>
+<DT><SAMP>‘-i’</SAMP>
<DD>
-<DT><SAMP>`--indent´</SAMP>
+<DT><SAMP>‘--indent’</SAMP>
<DD>
-<A NAME="IDX264"></A>
-<A NAME="IDX265"></A>
+<A NAME="IDX273"></A>
+<A NAME="IDX274"></A>
Write the .po file using indented style.
-<DT><SAMP>`--no-location´</SAMP>
+<DT><SAMP>‘--no-location’</SAMP>
<DD>
-<A NAME="IDX266"></A>
-Do not write <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines.
+<A NAME="IDX275"></A>
+Do not write <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines.
-<DT><SAMP>`--add-location´</SAMP>
+<DT><SAMP>‘--add-location’</SAMP>
<DD>
-<A NAME="IDX267"></A>
-Generate <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines (default).
+<A NAME="IDX276"></A>
+Generate <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines (default).
-<DT><SAMP>`--strict´</SAMP>
+<DT><SAMP>‘--strict’</SAMP>
<DD>
-<A NAME="IDX268"></A>
+<A NAME="IDX277"></A>
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
-<DT><SAMP>`-p´</SAMP>
+<DT><SAMP>‘-p’</SAMP>
<DD>
-<DT><SAMP>`--properties-output´</SAMP>
+<DT><SAMP>‘--properties-output’</SAMP>
<DD>
-<A NAME="IDX269"></A>
-<A NAME="IDX270"></A>
+<A NAME="IDX278"></A>
+<A NAME="IDX279"></A>
Write out a Java ResourceBundle in Java <CODE>.properties</CODE> syntax. Note
that this file format doesn't support plural forms and silently drops
obsolete messages.
-<DT><SAMP>`--stringtable-output´</SAMP>
+<DT><SAMP>‘--stringtable-output’</SAMP>
<DD>
-<A NAME="IDX271"></A>
+<A NAME="IDX280"></A>
Write out a NeXTstep/GNUstep localized resource file in <CODE>.strings</CODE> syntax.
Note that this file format doesn't support plural forms.
-<DT><SAMP>`-w <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-w <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--width=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--width=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX272"></A>
-<A NAME="IDX273"></A>
+<A NAME="IDX281"></A>
+<A NAME="IDX282"></A>
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 <VAR>number</VAR>.
-<DT><SAMP>`--no-wrap´</SAMP>
+<DT><SAMP>‘--no-wrap’</SAMP>
<DD>
-<A NAME="IDX274"></A>
+<A NAME="IDX283"></A>
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.
-<DT><SAMP>`-s´</SAMP>
+<DT><SAMP>‘-s’</SAMP>
<DD>
-<DT><SAMP>`--sort-output´</SAMP>
+<DT><SAMP>‘--sort-output’</SAMP>
<DD>
-<A NAME="IDX275"></A>
-<A NAME="IDX276"></A>
-<A NAME="IDX277"></A>
+<A NAME="IDX284"></A>
+<A NAME="IDX285"></A>
+<A NAME="IDX286"></A>
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
-<DT><SAMP>`-F´</SAMP>
+<DT><SAMP>‘-F’</SAMP>
<DD>
-<DT><SAMP>`--sort-by-file´</SAMP>
+<DT><SAMP>‘--sort-by-file’</SAMP>
<DD>
-<A NAME="IDX278"></A>
-<A NAME="IDX279"></A>
+<A NAME="IDX287"></A>
+<A NAME="IDX288"></A>
Sort output by file location.
</DL>
-<H3><A NAME="SEC47" HREF="gettext_toc.html#TOC47">7.1.8 Informative output</A></H3>
+<H3><A NAME="SEC48" HREF="gettext_toc.html#TOC48">7.1.8 Informative output</A></H3>
<DL COMPACT>
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX280"></A>
-<A NAME="IDX281"></A>
+<A NAME="IDX289"></A>
+<A NAME="IDX290"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX282"></A>
-<A NAME="IDX283"></A>
+<A NAME="IDX291"></A>
+<A NAME="IDX292"></A>
Output version information and exit.
-<DT><SAMP>`-v´</SAMP>
+<DT><SAMP>‘-v’</SAMP>
<DD>
-<DT><SAMP>`--verbose´</SAMP>
+<DT><SAMP>‘--verbose’</SAMP>
<DD>
-<A NAME="IDX284"></A>
-<A NAME="IDX285"></A>
+<A NAME="IDX293"></A>
+<A NAME="IDX294"></A>
Increase verbosity level.
-<DT><SAMP>`-q´</SAMP>
+<DT><SAMP>‘-q’</SAMP>
<DD>
-<DT><SAMP>`--quiet´</SAMP>
+<DT><SAMP>‘--quiet’</SAMP>
<DD>
-<DT><SAMP>`--silent´</SAMP>
+<DT><SAMP>‘--silent’</SAMP>
<DD>
-<A NAME="IDX286"></A>
-<A NAME="IDX287"></A>
-<A NAME="IDX288"></A>
+<A NAME="IDX295"></A>
+<A NAME="IDX296"></A>
+<A NAME="IDX297"></A>
Suppress progress indicators.
</DL>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_6.html">previous</A>, <A HREF="gettext_8.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_6.html">previous</A>, <A HREF="gettext_8.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 8 Editing PO Files</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_7.html">previous</A>, <A HREF="gettext_9.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_7.html">previous</A>, <A HREF="gettext_9.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC48" HREF="gettext_toc.html#TOC48">8 Editing PO Files</A></H1>
+<H1><A NAME="SEC49" HREF="gettext_toc.html#TOC49">8 Editing PO Files</A></H1>
<P>
-<A NAME="IDX289"></A>
+<A NAME="IDX298"></A>
</P>
-<H2><A NAME="SEC49" HREF="gettext_toc.html#TOC49">8.1 KDE's PO File Editor</A></H2>
+<H2><A NAME="SEC50" HREF="gettext_toc.html#TOC50">8.1 KDE's PO File Editor</A></H2>
<P>
-<A NAME="IDX290"></A>
+<A NAME="IDX299"></A>
</P>
-<H2><A NAME="SEC50" HREF="gettext_toc.html#TOC50">8.2 GNOME's PO File Editor</A></H2>
+<H2><A NAME="SEC51" HREF="gettext_toc.html#TOC51">8.2 GNOME's PO File Editor</A></H2>
<P>
-<A NAME="IDX291"></A>
+<A NAME="IDX300"></A>
</P>
-<H2><A NAME="SEC51" HREF="gettext_toc.html#TOC51">8.3 Emacs's PO File Editor</A></H2>
+<H2><A NAME="SEC52" HREF="gettext_toc.html#TOC52">8.3 Emacs's PO File Editor</A></H2>
<P>
-<A NAME="IDX292"></A>
+<A NAME="IDX301"></A>
</P>
+<P>
+For those of you being
+the lucky users of Emacs, PO mode has been specifically created
+for providing a cozy environment for editing or modifying PO files.
+While editing a PO file, PO mode allows for the easy browsing of
+auxiliary and compendium PO files, as well as for following references into
+the set of C program sources from which PO files have been derived.
+It has a few special features, among which are the interactive marking
+of program strings as translatable, and the validation of PO files
+with easy repositioning to PO file lines showing errors.
+
+</P>
+<P>
+For the beginning, besides main PO mode commands
+(see section <A HREF="gettext_8.html#SEC54">8.3.2 Main PO mode Commands</A>), you should know how to move between entries
+(see section <A HREF="gettext_8.html#SEC55">8.3.3 Entry Positioning</A>), and how to handle untranslated entries
+(see section <A HREF="gettext_8.html#SEC59">8.3.7 Untranslated Entries</A>).
+
+</P>
-<H3><A NAME="SEC52" HREF="gettext_toc.html#TOC52">8.3.1 Completing GNU <CODE>gettext</CODE> Installation</A></H3>
+
+<H3><A NAME="SEC53" HREF="gettext_toc.html#TOC53">8.3.1 Completing GNU <CODE>gettext</CODE> Installation</A></H3>
<P>
-<A NAME="IDX293"></A>
-<A NAME="IDX294"></A>
+<A NAME="IDX302"></A>
+<A NAME="IDX303"></A>
Once you have received, unpacked, configured and compiled the GNU
-<CODE>gettext</CODE> distribution, the <SAMP>`make install´</SAMP> command puts in
+<CODE>gettext</CODE> distribution, the <SAMP>‘make install’</SAMP> command puts in
place the programs <CODE>xgettext</CODE>, <CODE>msgfmt</CODE>, <CODE>gettext</CODE>, and
<CODE>msgmerge</CODE>, as well as their available message catalogs. To
top off a comfortable installation, you might also want to make the
</P>
<P>
-<A NAME="IDX295"></A>
-<A NAME="IDX296"></A>
+<A NAME="IDX304"></A>
+<A NAME="IDX305"></A>
During the installation of the PO mode, you might want to modify your
-file <TT>`.emacs´</TT>, once and for all, so it contains a few lines looking
+file <TT>‘.emacs’</TT>, once and for all, so it contains a few lines looking
like:
</P>
</PRE>
<P>
-Later, whenever you edit some <TT>`.po´</TT>
-file, or any file having the string <SAMP>`.po.´</SAMP> within its name,
-Emacs loads <TT>`po-mode.elc´</TT> (or <TT>`po-mode.el´</TT>) as needed, and
+Later, whenever you edit some <TT>‘.po’</TT>
+file, or any file having the string <SAMP>‘.po.’</SAMP> within its name,
+Emacs loads <TT>‘po-mode.elc’</TT> (or <TT>‘po-mode.el’</TT>) as needed, and
automatically activates PO mode commands for the associated buffer.
The string <EM>PO</EM> appears in the mode line for any buffer for
which PO mode is active. Many PO files may be active at once in a
</PRE>
<P>
-to your <TT>`.emacs´</TT> file. If, with this, you still see boxes instead
+to your <TT>‘.emacs’</TT> file. If, with this, you still see boxes instead
of international characters, try a different font set (via Shift Mouse
button 1).
</P>
-<H3><A NAME="SEC53" HREF="gettext_toc.html#TOC53">8.3.2 Main PO mode Commands</A></H3>
+<H3><A NAME="SEC54" HREF="gettext_toc.html#TOC54">8.3.2 Main PO mode Commands</A></H3>
<P>
-<A NAME="IDX297"></A>
-<A NAME="IDX298"></A>
+<A NAME="IDX306"></A>
+<A NAME="IDX307"></A>
After setting up Emacs with something similar to the lines in
-section <A HREF="gettext_8.html#SEC52">8.3.1 Completing GNU <CODE>gettext</CODE> Installation</A>, PO mode is activated for a window when Emacs finds a
+section <A HREF="gettext_8.html#SEC53">8.3.1 Completing GNU <CODE>gettext</CODE> Installation</A>, PO mode is activated for a window when Emacs finds a
PO file in that window. This puts the window read-only and establishes a
po-mode-map, which is a genuine Emacs mode, in a way that is not derived
from text mode in any way. Functions found on <CODE>po-mode-hook</CODE>,
</P>
<P>
-When PO mode is active in a window, the letters <SAMP>`PO´</SAMP> appear
+When PO mode is active in a window, the letters <SAMP>‘PO’</SAMP> 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 <SAMP>`132t+3f+10u+2o´</SAMP> would tell the translator that the
-PO mode contains 132 translated entries (see section <A HREF="gettext_8.html#SEC56">8.3.5 Translated Entries</A>,
-3 fuzzy entries (see section <A HREF="gettext_8.html#SEC57">8.3.6 Fuzzy Entries</A>), 10 untranslated entries
-(see section <A HREF="gettext_8.html#SEC58">8.3.7 Untranslated Entries</A>) and 2 obsolete entries (see section <A HREF="gettext_8.html#SEC59">8.3.8 Obsolete Entries</A>). Zero-coefficients items are not shown. So, in this example, if
+the string <SAMP>‘132t+3f+10u+2o’</SAMP> would tell the translator that the
+PO mode contains 132 translated entries (see section <A HREF="gettext_8.html#SEC57">8.3.5 Translated Entries</A>,
+3 fuzzy entries (see section <A HREF="gettext_8.html#SEC58">8.3.6 Fuzzy Entries</A>), 10 untranslated entries
+(see section <A HREF="gettext_8.html#SEC59">8.3.7 Untranslated Entries</A>) and 2 obsolete entries (see section <A HREF="gettext_8.html#SEC60">8.3.8 Obsolete Entries</A>). 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
-<SAMP>`145t´</SAMP> for the counters.
+<SAMP>‘145t’</SAMP> for the counters.
</P>
<P>
<DT><KBD>_</KBD>
<DD>
-<A NAME="IDX299"></A>
+<A NAME="IDX308"></A>
Undo last modification to the PO file (<CODE>po-undo</CODE>).
<DT><KBD>Q</KBD>
<DD>
-<A NAME="IDX300"></A>
+<A NAME="IDX309"></A>
Quit processing and save the PO file (<CODE>po-quit</CODE>).
<DT><KBD>q</KBD>
<DD>
-<A NAME="IDX301"></A>
+<A NAME="IDX310"></A>
Quit processing, possibly after confirmation (<CODE>po-confirm-and-quit</CODE>).
<DT><KBD>0</KBD>
<DD>
-<A NAME="IDX302"></A>
+<A NAME="IDX311"></A>
Temporary leave the PO file window (<CODE>po-other-window</CODE>).
<DT><KBD>?</KBD>
<DD>
<DT><KBD>h</KBD>
<DD>
-<A NAME="IDX303"></A>
-<A NAME="IDX304"></A>
+<A NAME="IDX312"></A>
+<A NAME="IDX313"></A>
Show help about PO mode (<CODE>po-help</CODE>).
<DT><KBD>=</KBD>
<DD>
-<A NAME="IDX305"></A>
+<A NAME="IDX314"></A>
Give some PO file statistics (<CODE>po-statistics</CODE>).
<DT><KBD>V</KBD>
<DD>
-<A NAME="IDX306"></A>
+<A NAME="IDX315"></A>
Batch validate the format of the whole PO file (<CODE>po-validate</CODE>).
</DL>
<P>
-<A NAME="IDX307"></A>
-<A NAME="IDX308"></A>
+<A NAME="IDX316"></A>
+<A NAME="IDX317"></A>
The command <KBD>_</KBD> (<CODE>po-undo</CODE>) interfaces to the Emacs
-<EM>undo</EM> facility. See section `Undoing Changes' in <CITE>The Emacs Editor</CITE>. Each time <KBD>U</KBD> is typed, modifications which the translator
+<EM>undo</EM> facility. See section ‘Undoing Changes’ in <CITE>The Emacs Editor</CITE>. Each time <KBD>U</KBD> is typed, modifications which the translator
did to the PO file are undone a little more. For the purpose of
undoing, each PO mode command is atomic. This is especially true for
the <KBD><KBD>RET</KBD></KBD> command: the whole edition made by using a single
</P>
<P>
-<A NAME="IDX309"></A>
-<A NAME="IDX310"></A>
-<A NAME="IDX311"></A>
-<A NAME="IDX312"></A>
+<A NAME="IDX318"></A>
+<A NAME="IDX319"></A>
+<A NAME="IDX320"></A>
+<A NAME="IDX321"></A>
The commands <KBD>Q</KBD> (<CODE>po-quit</CODE>) and <KBD>q</KBD>
(<CODE>po-confirm-and-quit</CODE>) are used when the translator is done with the
PO file. The former is a bit less verbose than the latter. If the file
</P>
<P>
-<A NAME="IDX313"></A>
-<A NAME="IDX314"></A>
+<A NAME="IDX322"></A>
+<A NAME="IDX323"></A>
The command <KBD>0</KBD> (<CODE>po-other-window</CODE>) is another, softer way,
to leave PO mode, temporarily. It just moves the cursor to some other
Emacs window, and pops one if necessary. For example, if the translator
</P>
<P>
-<A NAME="IDX315"></A>
-<A NAME="IDX316"></A>
-<A NAME="IDX317"></A>
+<A NAME="IDX324"></A>
+<A NAME="IDX325"></A>
+<A NAME="IDX326"></A>
The command <KBD>h</KBD> (<CODE>po-help</CODE>) displays a summary of all available PO
mode commands. The translator should then type any character to resume
normal PO mode operations. The command <KBD>?</KBD> has the same effect
</P>
<P>
-<A NAME="IDX318"></A>
-<A NAME="IDX319"></A>
+<A NAME="IDX327"></A>
+<A NAME="IDX328"></A>
The command <KBD>=</KBD> (<CODE>po-statistics</CODE>) computes the total number of
entries in the PO file, the ordinal of the current entry (counted from
1), the number of untranslated entries, the number of obsolete entries,
</P>
<P>
-<A NAME="IDX320"></A>
-<A NAME="IDX321"></A>
+<A NAME="IDX329"></A>
+<A NAME="IDX330"></A>
The command <KBD>V</KBD> (<CODE>po-validate</CODE>) launches <CODE>msgfmt</CODE> in
checking and verbose
mode over the current PO file. This command first offers to save the
</P>
<P>
-<A NAME="IDX322"></A>
+<A NAME="IDX331"></A>
The program <CODE>msgfmt</CODE> runs asynchronously with Emacs, so the
translator regains control immediately while her PO file is being studied.
-Error output is collected in the Emacs <SAMP>`*compilation*´</SAMP> buffer,
+Error output is collected in the Emacs <SAMP>‘*compilation*’</SAMP> buffer,
displayed in another window. The regular Emacs command <KBD>C-x`</KBD>
(<CODE>next-error</CODE>), as well as other usual compile commands, allow the
translator to reposition quickly to the offending parts of the PO file.
</P>
-<H3><A NAME="SEC54" HREF="gettext_toc.html#TOC54">8.3.3 Entry Positioning</A></H3>
+<H3><A NAME="SEC55" HREF="gettext_toc.html#TOC55">8.3.3 Entry Positioning</A></H3>
<P>
-<A NAME="IDX323"></A>
+<A NAME="IDX332"></A>
The cursor in a PO file window is almost always part of
an entry. The only exceptions are the special case when the cursor
is after the last entry in the file, or when the PO file is
</P>
<P>
-<A NAME="IDX324"></A>
+<A NAME="IDX333"></A>
Some PO mode commands alter the position of the cursor in a specialized
way. A few of those special purpose positioning are described here,
the others are described in following sections (for a complete list try
<DT><KBD>.</KBD>
<DD>
-<A NAME="IDX325"></A>
+<A NAME="IDX334"></A>
Redisplay the current entry (<CODE>po-current-entry</CODE>).
<DT><KBD>n</KBD>
<DD>
-<A NAME="IDX326"></A>
+<A NAME="IDX335"></A>
Select the entry after the current one (<CODE>po-next-entry</CODE>).
<DT><KBD>p</KBD>
<DD>
-<A NAME="IDX327"></A>
+<A NAME="IDX336"></A>
Select the entry before the current one (<CODE>po-previous-entry</CODE>).
<DT><KBD><</KBD>
<DD>
-<A NAME="IDX328"></A>
+<A NAME="IDX337"></A>
Select the first entry in the PO file (<CODE>po-first-entry</CODE>).
<DT><KBD>></KBD>
<DD>
-<A NAME="IDX329"></A>
+<A NAME="IDX338"></A>
Select the last entry in the PO file (<CODE>po-last-entry</CODE>).
<DT><KBD>m</KBD>
<DD>
-<A NAME="IDX330"></A>
+<A NAME="IDX339"></A>
Record the location of the current entry for later use
(<CODE>po-push-location</CODE>).
<DT><KBD>r</KBD>
<DD>
-<A NAME="IDX331"></A>
+<A NAME="IDX340"></A>
Return to a previously saved entry location (<CODE>po-pop-location</CODE>).
<DT><KBD>x</KBD>
<DD>
-<A NAME="IDX332"></A>
+<A NAME="IDX341"></A>
Exchange the current entry location with the previously saved one
(<CODE>po-exchange-location</CODE>).
</DL>
<P>
-<A NAME="IDX333"></A>
-<A NAME="IDX334"></A>
+<A NAME="IDX342"></A>
+<A NAME="IDX343"></A>
Any Emacs command able to reposition the cursor may be used
to select the current entry in PO mode, including commands which
move by characters, lines, paragraphs, screens or pages, and search
</P>
<P>
-<A NAME="IDX335"></A>
-<A NAME="IDX336"></A>
-<A NAME="IDX337"></A>
-<A NAME="IDX338"></A>
+<A NAME="IDX344"></A>
+<A NAME="IDX345"></A>
+<A NAME="IDX346"></A>
+<A NAME="IDX347"></A>
The commands <KBD>n</KBD> (<CODE>po-next-entry</CODE>) and <KBD>p</KBD>
(<CODE>po-previous-entry</CODE>) move the cursor the entry following,
or preceding, the current one. If <KBD>n</KBD> is given while the
</P>
<P>
-<A NAME="IDX339"></A>
-<A NAME="IDX340"></A>
-<A NAME="IDX341"></A>
-<A NAME="IDX342"></A>
+<A NAME="IDX348"></A>
+<A NAME="IDX349"></A>
+<A NAME="IDX350"></A>
+<A NAME="IDX351"></A>
The commands <KBD><</KBD> (<CODE>po-first-entry</CODE>) and <KBD>></KBD>
(<CODE>po-last-entry</CODE>) move the cursor to the first entry, or last
entry, of the PO file. When the cursor is located past the last
entry in a PO file, most PO mode commands will return an error saying
-<SAMP>`After last entry´</SAMP>. Moreover, the commands <KBD><</KBD> and <KBD>></KBD>
+<SAMP>‘After last entry’</SAMP>. Moreover, the commands <KBD><</KBD> and <KBD>></KBD>
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 <A HREF="gettext_4.html#SEC15">4.4 Marking Translatable Strings</A>.
+to interactively fill an empty PO file from sources. See section <A HREF="gettext_4.html#SEC16">4.5 Marking Translatable Strings</A>.
</P>
<P>
</P>
<P>
-<A NAME="IDX343"></A>
-<A NAME="IDX344"></A>
-<A NAME="IDX345"></A>
-<A NAME="IDX346"></A>
+<A NAME="IDX352"></A>
+<A NAME="IDX353"></A>
+<A NAME="IDX354"></A>
+<A NAME="IDX355"></A>
PO mode offers another approach, by which cursor locations may be saved
onto a special stack. The command <KBD>m</KBD> (<CODE>po-push-location</CODE>)
merely adds the location of current entry to the stack, pushing
</P>
<P>
-<A NAME="IDX347"></A>
-<A NAME="IDX348"></A>
+<A NAME="IDX356"></A>
+<A NAME="IDX357"></A>
The command <KBD>x</KBD> (<CODE>po-exchange-location</CODE>) simultaneously
repositions the cursor to the entry associated with the top element of
the stack of saved locations, and replaces that top element with the
</P>
-<H3><A NAME="SEC55" HREF="gettext_toc.html#TOC55">8.3.4 Normalizing Strings in Entries</A></H3>
+<H3><A NAME="SEC56" HREF="gettext_toc.html#TOC56">8.3.4 Normalizing Strings in Entries</A></H3>
<P>
-<A NAME="IDX349"></A>
+<A NAME="IDX358"></A>
</P>
<P>
</P>
<P>
-<A NAME="IDX350"></A>
+<A NAME="IDX359"></A>
<DL COMPACT>
<DT><KBD>M-x po-normalize</KBD>
<DD>
-<A NAME="IDX351"></A>
+<A NAME="IDX360"></A>
Tidy the whole PO file by making entries more uniform.
</DL>
</P>
<P>
-<A NAME="IDX352"></A>
+<A NAME="IDX361"></A>
Having such an explicit normalizing command allows for importing PO
files from other sources, but also eases the evolution of the current
convention, evolution driven mostly by aesthetic concerns, as of now.
</P>
<P>
-<A NAME="IDX353"></A>
+<A NAME="IDX362"></A>
Right now, in PO mode, strings are single line or multi-line. A string
goes multi-line if and only if it has <EM>embedded</EM> newlines, that
-is, if it matches <SAMP>`[^\n]\n+[^\n]´</SAMP>. So, we would have:
+is, if it matches <SAMP>‘[^\n]\n+[^\n]’</SAMP>. So, we would have:
</P>
</P>
-<H3><A NAME="SEC56" HREF="gettext_toc.html#TOC56">8.3.5 Translated Entries</A></H3>
+<H3><A NAME="SEC57" HREF="gettext_toc.html#TOC57">8.3.5 Translated Entries</A></H3>
<P>
-<A NAME="IDX354"></A>
+<A NAME="IDX363"></A>
</P>
<P>
Each PO file entry for which the <CODE>msgstr</CODE> field has been filled with
-a translation, and which is not marked as fuzzy (see section <A HREF="gettext_8.html#SEC57">8.3.6 Fuzzy Entries</A>),
+a translation, and which is not marked as fuzzy (see section <A HREF="gettext_8.html#SEC58">8.3.6 Fuzzy Entries</A>),
is said to be a <EM>translated</EM> entry. Only translated entries will
later be compiled by GNU <CODE>msgfmt</CODE> and become usable in programs.
Other entry types will be excluded; translation will not occur for them.
</P>
<P>
-<A NAME="IDX355"></A>
+<A NAME="IDX364"></A>
Some commands are more specifically related to translated entry processing.
</P>
<DT><KBD>t</KBD>
<DD>
-<A NAME="IDX356"></A>
+<A NAME="IDX365"></A>
Find the next translated entry (<CODE>po-next-translated-entry</CODE>).
<DT><KBD>T</KBD>
<DD>
-<A NAME="IDX357"></A>
+<A NAME="IDX366"></A>
Find the previous translated entry (<CODE>po-previous-translated-entry</CODE>).
</DL>
<P>
-<A NAME="IDX358"></A>
-<A NAME="IDX359"></A>
-<A NAME="IDX360"></A>
-<A NAME="IDX361"></A>
+<A NAME="IDX367"></A>
+<A NAME="IDX368"></A>
+<A NAME="IDX369"></A>
+<A NAME="IDX370"></A>
The commands <KBD>t</KBD> (<CODE>po-next-translated-entry</CODE>) and <KBD>T</KBD>
(<CODE>po-previous-translated-entry</CODE>) move forwards or backwards, chasing
for an translated entry. If none is found, the search is extended and
</P>
<P>
-<A NAME="IDX362"></A>
+<A NAME="IDX371"></A>
Translated entries usually result from the translator having edited in
-a translation for them, section <A HREF="gettext_8.html#SEC60">8.3.9 Modifying Translations</A>. However, if the
+a translation for them, section <A HREF="gettext_8.html#SEC61">8.3.9 Modifying Translations</A>. However, if the
variable <CODE>po-auto-fuzzy-on-edit</CODE> is not <CODE>nil</CODE>, 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 <A HREF="gettext_8.html#SEC57">8.3.6 Fuzzy Entries</A>.
+See section <A HREF="gettext_8.html#SEC58">8.3.6 Fuzzy Entries</A>.
</P>
-<H3><A NAME="SEC57" HREF="gettext_toc.html#TOC57">8.3.6 Fuzzy Entries</A></H3>
+<H3><A NAME="SEC58" HREF="gettext_toc.html#TOC58">8.3.6 Fuzzy Entries</A></H3>
<P>
-<A NAME="IDX363"></A>
+<A NAME="IDX372"></A>
</P>
<P>
-<A NAME="IDX364"></A>
-<A NAME="IDX365"></A>
+<A NAME="IDX373"></A>
+<A NAME="IDX374"></A>
Each PO file entry may have a set of <EM>attributes</EM>, which are
qualities given a name and explicitly associated with the translation,
using a special system comment. One of these attributes
</P>
<P>
-<A NAME="IDX366"></A>
+<A NAME="IDX375"></A>
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
<DT><KBD>z</KBD>
<DD>
-<A NAME="IDX367"></A>
+<A NAME="IDX376"></A>
Find the next fuzzy entry (<CODE>po-next-fuzzy-entry</CODE>).
<DT><KBD>Z</KBD>
<DD>
-<A NAME="IDX368"></A>
+<A NAME="IDX377"></A>
Find the previous fuzzy entry (<CODE>po-previous-fuzzy-entry</CODE>).
<DT><KBD><KBD>TAB</KBD></KBD>
<DD>
-<A NAME="IDX369"></A>
+<A NAME="IDX378"></A>
Remove the fuzzy attribute of the current entry (<CODE>po-unfuzzy</CODE>).
</DL>
<P>
-<A NAME="IDX370"></A>
-<A NAME="IDX371"></A>
-<A NAME="IDX372"></A>
-<A NAME="IDX373"></A>
+<A NAME="IDX379"></A>
+<A NAME="IDX380"></A>
+<A NAME="IDX381"></A>
+<A NAME="IDX382"></A>
The commands <KBD>z</KBD> (<CODE>po-next-fuzzy-entry</CODE>) and <KBD>Z</KBD>
(<CODE>po-previous-fuzzy-entry</CODE>) move forwards or backwards, chasing for
a fuzzy entry. If none is found, the search is extended and wraps
</P>
<P>
-<A NAME="IDX374"></A>
-<A NAME="IDX375"></A>
-<A NAME="IDX376"></A>
+<A NAME="IDX383"></A>
+<A NAME="IDX384"></A>
+<A NAME="IDX385"></A>
The command <KBD><KBD>TAB</KBD></KBD> (<CODE>po-unfuzzy</CODE>) removes the fuzzy
attribute associated with an entry, usually leaving it translated.
Further, if the variable <CODE>po-auto-select-on-unfuzzy</CODE> has not
</P>
<P>
-<A NAME="IDX377"></A>
-<A NAME="IDX378"></A>
+<A NAME="IDX386"></A>
+<A NAME="IDX387"></A>
The translator may also use the <KBD><KBD>DEL</KBD></KBD> command
(<CODE>po-fade-out-entry</CODE>) over any translated entry to mark it as being
fuzzy, when she wants to easily leave a trace she wants to later return
</P>
-<H3><A NAME="SEC58" HREF="gettext_toc.html#TOC58">8.3.7 Untranslated Entries</A></H3>
+<H3><A NAME="SEC59" HREF="gettext_toc.html#TOC59">8.3.7 Untranslated Entries</A></H3>
<P>
-<A NAME="IDX379"></A>
+<A NAME="IDX388"></A>
</P>
<P>
<P>
The usual commands moving from entry to entry consider untranslated
entries on the same level as active entries. Untranslated entries
-are easily recognizable by the fact they end with <SAMP>`msgstr ""´</SAMP>.
+are easily recognizable by the fact they end with <SAMP>‘msgstr ""’</SAMP>.
</P>
<P>
-<A NAME="IDX380"></A>
+<A NAME="IDX389"></A>
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.
<DT><KBD>u</KBD>
<DD>
-<A NAME="IDX381"></A>
+<A NAME="IDX390"></A>
Find the next untranslated entry (<CODE>po-next-untranslated-entry</CODE>).
<DT><KBD>U</KBD>
<DD>
-<A NAME="IDX382"></A>
+<A NAME="IDX391"></A>
Find the previous untranslated entry (<CODE>po-previous-untransted-entry</CODE>).
<DT><KBD>k</KBD>
<DD>
-<A NAME="IDX383"></A>
+<A NAME="IDX392"></A>
Turn the current entry into an untranslated one (<CODE>po-kill-msgstr</CODE>).
</DL>
<P>
-<A NAME="IDX384"></A>
-<A NAME="IDX385"></A>
-<A NAME="IDX386"></A>
-<A NAME="IDX387"></A>
+<A NAME="IDX393"></A>
+<A NAME="IDX394"></A>
+<A NAME="IDX395"></A>
+<A NAME="IDX396"></A>
The commands <KBD>u</KBD> (<CODE>po-next-untranslated-entry</CODE>) and <KBD>U</KBD>
(<CODE>po-previous-untransted-entry</CODE>) move forwards or backwards,
chasing for an untranslated entry. If none is found, the search is
</P>
<P>
-<A NAME="IDX388"></A>
-<A NAME="IDX389"></A>
+<A NAME="IDX397"></A>
+<A NAME="IDX398"></A>
An entry can be turned back into an untranslated entry by
merely emptying its translation, using the command <KBD>k</KBD>
-(<CODE>po-kill-msgstr</CODE>). See section <A HREF="gettext_8.html#SEC60">8.3.9 Modifying Translations</A>.
+(<CODE>po-kill-msgstr</CODE>). See section <A HREF="gettext_8.html#SEC61">8.3.9 Modifying Translations</A>.
</P>
<P>
</P>
-<H3><A NAME="SEC59" HREF="gettext_toc.html#TOC59">8.3.8 Obsolete Entries</A></H3>
+<H3><A NAME="SEC60" HREF="gettext_toc.html#TOC60">8.3.8 Obsolete Entries</A></H3>
<P>
-<A NAME="IDX390"></A>
+<A NAME="IDX399"></A>
</P>
<P>
</P>
<P>
-<A NAME="IDX391"></A>
+<A NAME="IDX400"></A>
Moreover, some commands are more specifically related to obsolete
entry processing.
<DT><KBD>o</KBD>
<DD>
-<A NAME="IDX392"></A>
+<A NAME="IDX401"></A>
Find the next obsolete entry (<CODE>po-next-obsolete-entry</CODE>).
<DT><KBD>O</KBD>
<DD>
-<A NAME="IDX393"></A>
+<A NAME="IDX402"></A>
Find the previous obsolete entry (<CODE>po-previous-obsolete-entry</CODE>).
<DT><KBD><KBD>DEL</KBD></KBD>
<DD>
-<A NAME="IDX394"></A>
+<A NAME="IDX403"></A>
Make an active entry obsolete, or zap out an obsolete entry
(<CODE>po-fade-out-entry</CODE>).
</DL>
<P>
-<A NAME="IDX395"></A>
-<A NAME="IDX396"></A>
-<A NAME="IDX397"></A>
-<A NAME="IDX398"></A>
+<A NAME="IDX404"></A>
+<A NAME="IDX405"></A>
+<A NAME="IDX406"></A>
+<A NAME="IDX407"></A>
The commands <KBD>o</KBD> (<CODE>po-next-obsolete-entry</CODE>) and <KBD>O</KBD>
(<CODE>po-previous-obsolete-entry</CODE>) move forwards or backwards,
chasing for an obsolete entry. If none is found, the search is
</P>
<P>
-<A NAME="IDX399"></A>
-<A NAME="IDX400"></A>
-<A NAME="IDX401"></A>
-<A NAME="IDX402"></A>
+<A NAME="IDX408"></A>
+<A NAME="IDX409"></A>
+<A NAME="IDX410"></A>
+<A NAME="IDX411"></A>
However, it is possible to comment out an active entry, so making
it obsolete. GNU <CODE>gettext</CODE> utilities will later react to the
disappearance of a translation by using the untranslated string.
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 <A HREF="gettext_8.html#SEC60">8.3.9 Modifying Translations</A>.
+entry, usually one which is untranslated. See section <A HREF="gettext_8.html#SEC61">8.3.9 Modifying Translations</A>.
</P>
<P>
</P>
-<H3><A NAME="SEC60" HREF="gettext_toc.html#TOC60">8.3.9 Modifying Translations</A></H3>
+<H3><A NAME="SEC61" HREF="gettext_toc.html#TOC61">8.3.9 Modifying Translations</A></H3>
<P>
-<A NAME="IDX403"></A>
-<A NAME="IDX404"></A>
+<A NAME="IDX412"></A>
+<A NAME="IDX413"></A>
</P>
<P>
<DT><KBD><KBD>RET</KBD></KBD>
<DD>
-<A NAME="IDX405"></A>
+<A NAME="IDX414"></A>
Interactively edit the translation (<CODE>po-edit-msgstr</CODE>).
<DT><KBD><KBD>LFD</KBD></KBD>
<DD>
<DT><KBD>C-j</KBD>
<DD>
-<A NAME="IDX406"></A>
-<A NAME="IDX407"></A>
+<A NAME="IDX415"></A>
+<A NAME="IDX416"></A>
Reinitialize the translation with the original, untranslated string
(<CODE>po-msgid-to-msgstr</CODE>).
<DT><KBD>k</KBD>
<DD>
-<A NAME="IDX408"></A>
+<A NAME="IDX417"></A>
Save the translation on the kill ring, and delete it (<CODE>po-kill-msgstr</CODE>).
<DT><KBD>w</KBD>
<DD>
-<A NAME="IDX409"></A>
+<A NAME="IDX418"></A>
Save the translation on the kill ring, without deleting it
(<CODE>po-kill-ring-save-msgstr</CODE>).
<DT><KBD>y</KBD>
<DD>
-<A NAME="IDX410"></A>
+<A NAME="IDX419"></A>
Replace the translation, taking the new from the kill ring
(<CODE>po-yank-msgstr</CODE>).
</DL>
<P>
-<A NAME="IDX411"></A>
-<A NAME="IDX412"></A>
+<A NAME="IDX420"></A>
+<A NAME="IDX421"></A>
The command <KBD><KBD>RET</KBD></KBD> (<CODE>po-edit-msgstr</CODE>) 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
marks, fully modifiable and with the complete extent of Emacs modifying
commands. When the translator is done with her modifications, she may use
<KBD>C-c C-c</KBD> to close the subedit window with the automatically requoted
-results, or <KBD>C-c C-k</KBD> to abort her modifications. See section <A HREF="gettext_8.html#SEC62">8.3.11 Details of Sub Edition</A>,
+results, or <KBD>C-c C-k</KBD> to abort her modifications. See section <A HREF="gettext_8.html#SEC63">8.3.11 Details of Sub Edition</A>,
for more information.
</P>
<P>
-<A NAME="IDX413"></A>
-<A NAME="IDX414"></A>
-<A NAME="IDX415"></A>
+<A NAME="IDX422"></A>
+<A NAME="IDX423"></A>
+<A NAME="IDX424"></A>
The command <KBD><KBD>LFD</KBD></KBD> (<CODE>po-msgid-to-msgstr</CODE>) initializes, or
reinitializes the translation with the original string. This command is
normally used when the translator wants to redo a fresh translation of
</P>
<P>
-<A NAME="IDX416"></A>
+<A NAME="IDX425"></A>
It is possible to arrange so, whenever editing an untranslated
entry, the <KBD><KBD>LFD</KBD></KBD> command be automatically executed. If you set
<CODE>po-auto-edit-with-msgid</CODE> to <CODE>t</CODE>, the translation gets
</P>
<P>
-<A NAME="IDX417"></A>
+<A NAME="IDX426"></A>
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
</P>
<P>
-<A NAME="IDX418"></A>
-<A NAME="IDX419"></A>
-<A NAME="IDX420"></A>
-<A NAME="IDX421"></A>
-<A NAME="IDX422"></A>
+<A NAME="IDX427"></A>
+<A NAME="IDX428"></A>
+<A NAME="IDX429"></A>
+<A NAME="IDX430"></A>
+<A NAME="IDX431"></A>
The command <KBD>k</KBD> (<CODE>po-kill-msgstr</CODE>) merely empties the
translation string, so turning the entry into an untranslated
one. But while doing so, its previous contents is put apart in
</P>
<P>
-<A NAME="IDX423"></A>
-<A NAME="IDX424"></A>
+<A NAME="IDX432"></A>
+<A NAME="IDX433"></A>
The command <KBD>y</KBD> (<CODE>po-yank-msgstr</CODE>) 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
string is <EM>yanked</EM> into the PO file buffer.
-See section `Yanking' in <CITE>The Emacs Editor</CITE>.
+See section ‘Yanking’ in <CITE>The Emacs Editor</CITE>.
The first time <KBD>y</KBD> is used, the translation receives the value of
the most recent addition to the kill ring. If <KBD>y</KBD> is typed once
again, immediately, without intervening keystrokes, the translation
</P>
<P>
-<A NAME="IDX425"></A>
+<A NAME="IDX434"></A>
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
When some sequence of keys has to be typed over and over again, the
translator may find it useful to become better acquainted with the Emacs
capability of learning these sequences and playing them back under request.
-See section `Keyboard Macros' in <CITE>The Emacs Editor</CITE>.
+See section ‘Keyboard Macros’ in <CITE>The Emacs Editor</CITE>.
</P>
-<H3><A NAME="SEC61" HREF="gettext_toc.html#TOC61">8.3.10 Modifying Comments</A></H3>
+<H3><A NAME="SEC62" HREF="gettext_toc.html#TOC62">8.3.10 Modifying Comments</A></H3>
<P>
-<A NAME="IDX426"></A>
-<A NAME="IDX427"></A>
+<A NAME="IDX435"></A>
+<A NAME="IDX436"></A>
</P>
<P>
</P>
<P>
-Comments not having whitespace after the initial <SAMP>`#´</SAMP>, for example,
-those beginning with <SAMP>`#.´</SAMP> or <SAMP>`#:´</SAMP>, are <EM>not</EM> translator
+Comments not having whitespace after the initial <SAMP>‘#’</SAMP>, for example,
+those beginning with <SAMP>‘#.’</SAMP> or <SAMP>‘#:’</SAMP>, are <EM>not</EM> translator
comments, they are exclusively created by other <CODE>gettext</CODE> tools.
So, the commands below will never alter such system added comments,
they are not meant for the translator to modify. See section <A HREF="gettext_3.html#SEC10">3 The Format of PO Files</A>.
</P>
<P>
The following commands are somewhat similar to those modifying translations,
-so the general indications given for those apply here. See section <A HREF="gettext_8.html#SEC60">8.3.9 Modifying Translations</A>.
+so the general indications given for those apply here. See section <A HREF="gettext_8.html#SEC61">8.3.9 Modifying Translations</A>.
</P>
<DL COMPACT>
<DT><KBD>#</KBD>
<DD>
-<A NAME="IDX428"></A>
+<A NAME="IDX437"></A>
Interactively edit the translator comments (<CODE>po-edit-comment</CODE>).
<DT><KBD>K</KBD>
<DD>
-<A NAME="IDX429"></A>
+<A NAME="IDX438"></A>
Save the translator comments on the kill ring, and delete it
(<CODE>po-kill-comment</CODE>).
<DT><KBD>W</KBD>
<DD>
-<A NAME="IDX430"></A>
+<A NAME="IDX439"></A>
Save the translator comments on the kill ring, without deleting it
(<CODE>po-kill-ring-save-comment</CODE>).
<DT><KBD>Y</KBD>
<DD>
-<A NAME="IDX431"></A>
+<A NAME="IDX440"></A>
Replace the translator comments, taking the new from the kill ring
(<CODE>po-yank-comment</CODE>).
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 <A HREF="gettext_8.html#SEC60">8.3.9 Modifying Translations</A>.
+See section <A HREF="gettext_8.html#SEC61">8.3.9 Modifying Translations</A>.
</P>
<P>
-<A NAME="IDX432"></A>
-<A NAME="IDX433"></A>
+<A NAME="IDX441"></A>
+<A NAME="IDX442"></A>
The command <KBD>#</KBD> (<CODE>po-edit-comment</CODE>) 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
pertaining to obsolete entries, the uncommenting and recommenting operations
are done twice. Once in the editing window, the keys <KBD>C-c C-c</KBD>
allow the translator to tell she is finished with editing the comment.
-See section <A HREF="gettext_8.html#SEC62">8.3.11 Details of Sub Edition</A>, for further details.
+See section <A HREF="gettext_8.html#SEC63">8.3.11 Details of Sub Edition</A>, for further details.
</P>
<P>
-<A NAME="IDX434"></A>
+<A NAME="IDX443"></A>
Functions found on <CODE>po-subedit-mode-hook</CODE>, if any, are executed after
the string has been inserted in the edit buffer.
</P>
<P>
-<A NAME="IDX435"></A>
-<A NAME="IDX436"></A>
-<A NAME="IDX437"></A>
-<A NAME="IDX438"></A>
-<A NAME="IDX439"></A>
-<A NAME="IDX440"></A>
+<A NAME="IDX444"></A>
+<A NAME="IDX445"></A>
+<A NAME="IDX446"></A>
+<A NAME="IDX447"></A>
+<A NAME="IDX448"></A>
+<A NAME="IDX449"></A>
The command <KBD>K</KBD> (<CODE>po-kill-comment</CODE>) gets rid of all
translator comments, while saving those comments on the kill ring.
The command <KBD>W</KBD> (<CODE>po-kill-ring-save-comment</CODE>) takes
</P>
-<H3><A NAME="SEC62" HREF="gettext_toc.html#TOC62">8.3.11 Details of Sub Edition</A></H3>
+<H3><A NAME="SEC63" HREF="gettext_toc.html#TOC63">8.3.11 Details of Sub Edition</A></H3>
<P>
-<A NAME="IDX441"></A>
+<A NAME="IDX450"></A>
</P>
<P>
<DT><KBD>C-c C-c</KBD>
<DD>
-<A NAME="IDX442"></A>
+<A NAME="IDX451"></A>
Complete edition (<CODE>po-subedit-exit</CODE>).
<DT><KBD>C-c C-k</KBD>
<DD>
-<A NAME="IDX443"></A>
+<A NAME="IDX452"></A>
Abort edition (<CODE>po-subedit-abort</CODE>).
<DT><KBD>C-c C-a</KBD>
<DD>
-<A NAME="IDX444"></A>
+<A NAME="IDX453"></A>
Consult auxiliary PO files (<CODE>po-subedit-cycle-auxiliary</CODE>).
</DL>
<P>
-<A NAME="IDX445"></A>
-<A NAME="IDX446"></A>
-<A NAME="IDX447"></A>
+<A NAME="IDX454"></A>
+<A NAME="IDX455"></A>
+<A NAME="IDX456"></A>
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 <KBD>C-c C-c</KBD>
</P>
<P>
-<A NAME="IDX448"></A>
-<A NAME="IDX449"></A>
+<A NAME="IDX457"></A>
+<A NAME="IDX458"></A>
If the translator becomes unsatisfied with her translation or comment,
to the extent she prefers keeping what was existent prior to the
<KBD><KBD>RET</KBD></KBD> or <KBD>#</KBD> command, she may use the command <KBD>C-c C-k</KBD>
</P>
<P>
-<A NAME="IDX450"></A>
-<A NAME="IDX451"></A>
+<A NAME="IDX459"></A>
+<A NAME="IDX460"></A>
The command <KBD>C-c C-a</KBD> (<CODE>po-subedit-cycle-auxiliary</CODE>)
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 <A HREF="gettext_8.html#SEC64">8.3.13 Consulting Auxiliary PO Files</A>).
+auxiliary PO files are already available to her (see section <A HREF="gettext_8.html#SEC65">8.3.13 Consulting Auxiliary PO Files</A>).
</P>
<P>
</P>
<P>
-<A NAME="IDX452"></A>
+<A NAME="IDX461"></A>
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
</P>
<P>
-<A NAME="IDX453"></A>
+<A NAME="IDX462"></A>
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 <KBD>q</KBD> command), subedits
</P>
-<H3><A NAME="SEC63" HREF="gettext_toc.html#TOC63">8.3.12 C Sources Context</A></H3>
+<H3><A NAME="SEC64" HREF="gettext_toc.html#TOC64">8.3.12 C Sources Context</A></H3>
<P>
-<A NAME="IDX454"></A>
-<A NAME="IDX455"></A>
-<A NAME="IDX456"></A>
+<A NAME="IDX463"></A>
+<A NAME="IDX464"></A>
+<A NAME="IDX465"></A>
</P>
<P>
</P>
<P>
-<A NAME="IDX457"></A>
+<A NAME="IDX466"></A>
The following commands are meant to help the translator at getting
program source context for a PO file entry.
<DT><KBD>s</KBD>
<DD>
-<A NAME="IDX458"></A>
+<A NAME="IDX467"></A>
Resume the display of a program source context, or cycle through them
(<CODE>po-cycle-source-reference</CODE>).
<DT><KBD>M-s</KBD>
<DD>
-<A NAME="IDX459"></A>
+<A NAME="IDX468"></A>
Display of a program source context selected by menu
(<CODE>po-select-source-reference</CODE>).
<DT><KBD>S</KBD>
<DD>
-<A NAME="IDX460"></A>
+<A NAME="IDX469"></A>
Add a directory to the search path for source files
(<CODE>po-consider-source-path</CODE>).
<DT><KBD>M-S</KBD>
<DD>
-<A NAME="IDX461"></A>
+<A NAME="IDX470"></A>
Delete a directory from the search path for source files
(<CODE>po-ignore-source-path</CODE>).
</DL>
<P>
-<A NAME="IDX462"></A>
-<A NAME="IDX463"></A>
-<A NAME="IDX464"></A>
-<A NAME="IDX465"></A>
+<A NAME="IDX471"></A>
+<A NAME="IDX472"></A>
+<A NAME="IDX473"></A>
+<A NAME="IDX474"></A>
The commands <KBD>s</KBD> (<CODE>po-cycle-source-reference</CODE>) and <KBD>M-s</KBD>
(<CODE>po-select-source-reference</CODE>) both open another window displaying
some source program file, and already positioned in such a way that
</P>
<P>
-<A NAME="IDX466"></A>
-<A NAME="IDX467"></A>
-<A NAME="IDX468"></A>
-<A NAME="IDX469"></A>
+<A NAME="IDX475"></A>
+<A NAME="IDX476"></A>
+<A NAME="IDX477"></A>
+<A NAME="IDX478"></A>
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.
</P>
-<H3><A NAME="SEC64" HREF="gettext_toc.html#TOC64">8.3.13 Consulting Auxiliary PO Files</A></H3>
+<H3><A NAME="SEC65" HREF="gettext_toc.html#TOC65">8.3.13 Consulting Auxiliary PO Files</A></H3>
<P>
-<A NAME="IDX470"></A>
+<A NAME="IDX479"></A>
</P>
<P>
</P>
<P>
-<A NAME="IDX471"></A>
-<A NAME="IDX472"></A>
+<A NAME="IDX480"></A>
+<A NAME="IDX481"></A>
An <EM>auxiliary</EM> 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
<DT><KBD>a</KBD>
<DD>
-<A NAME="IDX473"></A>
+<A NAME="IDX482"></A>
Seek auxiliary files for another translation for the same entry
(<CODE>po-cycle-auxiliary</CODE>).
<DT><KBD>C-c C-a</KBD>
<DD>
-<A NAME="IDX474"></A>
+<A NAME="IDX483"></A>
Switch to a particular auxiliary file (<CODE>po-select-auxiliary</CODE>).
<DT><KBD>A</KBD>
<DD>
-<A NAME="IDX475"></A>
+<A NAME="IDX484"></A>
Declare this PO file as an auxiliary file (<CODE>po-consider-as-auxiliary</CODE>).
<DT><KBD>M-A</KBD>
<DD>
-<A NAME="IDX476"></A>
+<A NAME="IDX485"></A>
Remove this PO file from the list of auxiliary files
(<CODE>po-ignore-as-auxiliary</CODE>).
</DL>
<P>
-<A NAME="IDX477"></A>
-<A NAME="IDX478"></A>
-<A NAME="IDX479"></A>
-<A NAME="IDX480"></A>
+<A NAME="IDX486"></A>
+<A NAME="IDX487"></A>
+<A NAME="IDX488"></A>
+<A NAME="IDX489"></A>
Command <KBD>A</KBD> (<CODE>po-consider-as-auxiliary</CODE>) adds the current
PO file to the list of auxiliary files, while command <KBD>M-A</KBD>
(<CODE>po-ignore-as-auxiliary</CODE> just removes it.
</P>
<P>
-<A NAME="IDX481"></A>
-<A NAME="IDX482"></A>
+<A NAME="IDX490"></A>
+<A NAME="IDX491"></A>
The command <KBD>a</KBD> (<CODE>po-cycle-auxiliary</CODE>) seeks all auxiliary PO
files, round-robin, searching for a translated entry in some other language
having an <CODE>msgid</CODE> field identical as the one for the current entry.
</P>
<P>
-<A NAME="IDX483"></A>
-<A NAME="IDX484"></A>
+<A NAME="IDX492"></A>
+<A NAME="IDX493"></A>
The command <KBD>C-c C-a</KBD> (<CODE>po-select-auxiliary</CODE>) 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
</P>
<P>
-<A NAME="IDX485"></A>
+<A NAME="IDX494"></A>
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 <SAMP>`M-x normalize´</SAMP> command. Until these
+files resulting of the the <SAMP>‘M-x normalize’</SAMP> command. Until these
discrepancies between PO mode and other GNU <CODE>gettext</CODE> tools get
fully resolved, the translator should stay aware of normalisation issues.
</P>
-<H3><A NAME="SEC65" HREF="gettext_toc.html#TOC65">8.3.14 Using Translation Compendia</A></H3>
+<H3><A NAME="SEC66" HREF="gettext_toc.html#TOC66">8.3.14 Using Translation Compendia</A></H3>
<P>
-<A NAME="IDX486"></A>
+<A NAME="IDX495"></A>
</P>
<P>
-<A NAME="IDX487"></A>
+<A NAME="IDX496"></A>
A <EM>compendium</EM> 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
-<H4><A NAME="SEC66" HREF="gettext_toc.html#TOC66">8.3.14.1 Creating Compendia</A></H4>
+<H4><A NAME="SEC67" HREF="gettext_toc.html#TOC67">8.3.14.1 Creating Compendia</A></H4>
<P>
-<A NAME="IDX488"></A>
-<A NAME="IDX489"></A>
+<A NAME="IDX497"></A>
+<A NAME="IDX498"></A>
</P>
<P>
</P>
-<H4><A NAME="SEC67" HREF="gettext_toc.html#TOC67">8.3.14.2 Concatenate PO Files</A></H4>
+<H4><A NAME="SEC68" HREF="gettext_toc.html#TOC68">8.3.14.2 Concatenate PO Files</A></H4>
<P>
-<A NAME="IDX490"></A>
-<A NAME="IDX491"></A>
+<A NAME="IDX499"></A>
+<A NAME="IDX500"></A>
To concatenate several valid PO files into one compendium file you can
-use <SAMP>`msgcomm´</SAMP> or <SAMP>`msgcat´</SAMP> (the latter preferred):
+use <SAMP>‘msgcomm’</SAMP> or <SAMP>‘msgcat’</SAMP> (the latter preferred):
</P>
By default, <CODE>msgcat</CODE> will accumulate divergent translations
for the same string. Those occurences will be marked as <CODE>fuzzy</CODE>
and highly visible decorated; calling <CODE>msgcat</CODE> on
-<TT>`file1.po´</TT>:
+<TT>‘file1.po’</TT>:
</P>
</PRE>
<P>
-and <TT>`file2.po´</TT>:
+and <TT>‘file2.po’</TT>:
</P>
</PRE>
<P>
-The translator will have to resolve this "conflict" manually; she
+The translator will have to resolve this “conflict” manually; she
has to decide whether the first or the second version is appropriate
-(or provide a new translation), to delete the "marker lines", and
+(or provide a new translation), to delete the “marker lines”, and
finally to remove the <CODE>fuzzy</CODE> mark.
</P>
<P>
If the translator knows in advance the first found translation of a
message is always the best translation she can make use to the
-<SAMP>`--use-first´</SAMP> switch:
+<SAMP>‘--use-first’</SAMP> switch:
</P>
<P>
A good compendium file must not contain <CODE>fuzzy</CODE> or untranslated
-entries. If input files are "dirty" you must preprocess the input
-files or postprocess the result using <SAMP>`msgattrib --translated --no-fuzzy´</SAMP>.
+entries. If input files are “dirty” you must preprocess the input
+files or postprocess the result using <SAMP>‘msgattrib --translated --no-fuzzy’</SAMP>.
</P>
-<H4><A NAME="SEC68" HREF="gettext_toc.html#TOC68">8.3.14.3 Extract a Message Subset from a PO File</A></H4>
+<H4><A NAME="SEC69" HREF="gettext_toc.html#TOC69">8.3.14.3 Extract a Message Subset from a PO File</A></H4>
<P>
-<A NAME="IDX492"></A>
+<A NAME="IDX501"></A>
</P>
<P>
Nobody wants to translate the same messages again and again; thus you
-may wish to have a compendium file containing <TT>`getopt.c´</TT> messages.
+may wish to have a compendium file containing <TT>‘getopt.c’</TT> messages.
</P>
<P>
-To extract a message subset (e.g., all <TT>`getopt.c´</TT> messages) from an
-existing PO file into one compendium file you can use <SAMP>`msggrep´</SAMP>:
+To extract a message subset (e.g., all <TT>‘getopt.c’</TT> messages) from an
+existing PO file into one compendium file you can use <SAMP>‘msggrep’</SAMP>:
</P>
-<H4><A NAME="SEC69" HREF="gettext_toc.html#TOC69">8.3.14.4 Using Compendia</A></H4>
+<H4><A NAME="SEC70" HREF="gettext_toc.html#TOC70">8.3.14.4 Using Compendia</A></H4>
<P>
You can use a compendium file to initialize a translation from scratch
</P>
-<H4><A NAME="SEC70" HREF="gettext_toc.html#TOC70">8.3.14.5 Initialize a New Translation File</A></H4>
+<H4><A NAME="SEC71" HREF="gettext_toc.html#TOC71">8.3.14.5 Initialize a New Translation File</A></H4>
<P>
-<A NAME="IDX493"></A>
+<A NAME="IDX502"></A>
</P>
<P>
Since a PO file with translations does not exist the translator can
-merely use <TT>`/dev/null´</TT> to fake the "old" translation file.
+merely use <TT>‘/dev/null’</TT> to fake the “old” translation file.
</P>
-<H4><A NAME="SEC71" HREF="gettext_toc.html#TOC71">8.3.14.6 Update an Existing Translation File</A></H4>
+<H4><A NAME="SEC72" HREF="gettext_toc.html#TOC72">8.3.14.6 Update an Existing Translation File</A></H4>
<P>
-<A NAME="IDX494"></A>
+<A NAME="IDX503"></A>
</P>
<P>
Concatenate the compendium file(s) and the existing PO, merge the
result with the POT file and remove the obsolete entries (optional,
-here done using <SAMP>`sed´</SAMP>):
+here done using <SAMP>‘sed’</SAMP>):
</P>
</PRE>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_7.html">previous</A>, <A HREF="gettext_9.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_7.html">previous</A>, <A HREF="gettext_9.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 21 July 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - 9 Manipulating PO Files</TITLE>
</HEAD>
<BODY>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_8.html">previous</A>, <A HREF="gettext_10.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_8.html">previous</A>, <A HREF="gettext_10.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
<P><HR><P>
-<H1><A NAME="SEC72" HREF="gettext_toc.html#TOC72">9 Manipulating PO Files</A></H1>
+<H1><A NAME="SEC73" HREF="gettext_toc.html#TOC73">9 Manipulating PO Files</A></H1>
<P>
-<A NAME="IDX495"></A>
+<A NAME="IDX504"></A>
</P>
<P>
</P>
<P>
-<A NAME="IDX496"></A>
+<A NAME="IDX505"></A>
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
a single translation catalog, for each language. This is best performed
-using <SAMP>`msgcat´</SAMP>. It is then the translators' duty to deal with any
+using <SAMP>‘msgcat’</SAMP>. It is then the translators' duty to deal with any
possible conflicts that arose during the merge.
</P>
<P>
-<A NAME="IDX497"></A>
+<A NAME="IDX506"></A>
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
-the <SAMP>`msgconv´</SAMP> program.
+the <SAMP>‘msgconv’</SAMP> program.
</P>
<P>
When a maintainer takes a source file with tagged messages from another
package, he should also take the existing translations for this source
file (and not let the translators do the same job twice). One way to do
-this is through <SAMP>`msggrep´</SAMP>, another is to create a POT file for
-that source file and use <SAMP>`msgmerge´</SAMP>.
+this is through <SAMP>‘msggrep’</SAMP>, another is to create a POT file for
+that source file and use <SAMP>‘msgmerge’</SAMP>.
</P>
<P>
-<A NAME="IDX498"></A>
-<A NAME="IDX499"></A>
+<A NAME="IDX507"></A>
+<A NAME="IDX508"></A>
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
processing to every message in the catalog. The tool for doing this is
-<SAMP>`msgfilter´</SAMP>.
+<SAMP>‘msgfilter’</SAMP>.
</P>
<P>
Another use of <CODE>msgfilter</CODE> is to produce approximately the POT file for
which a given PO file was made. This can be done through a filter command
-like <SAMP>`msgfilter sed -e d | sed -e '/^# /d'´</SAMP>. Note that the original
+like <SAMP>‘msgfilter sed -e d | sed -e '/^# /d'’</SAMP>. Note that the original
POT file may have had different comments and different plural message counts,
that's why it's better to use the original POT file if available.
</P>
<P>
-<A NAME="IDX500"></A>
+<A NAME="IDX509"></A>
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 <SAMP>`msgexec´</SAMP> program.
+so using the <SAMP>‘msgexec’</SAMP> program.
</P>
<P>
-<A NAME="IDX501"></A>
+<A NAME="IDX510"></A>
When third party tools create PO or POT files, sometimes duplicates cannot
be avoided. But the GNU <CODE>gettext</CODE> tools give an error when they
encounter duplicate msgids in the same file and in the same domain.
-To merge duplicates, the <SAMP>`msguniq´</SAMP> program can be used.
+To merge duplicates, the <SAMP>‘msguniq’</SAMP> program can be used.
</P>
<P>
-<SAMP>`msgcomm´</SAMP> is a more general tool for keeping or throwing away
+<SAMP>‘msgcomm’</SAMP> is a more general tool for keeping or throwing away
duplicates, occurring in different files.
</P>
<P>
-<SAMP>`msgcmp´</SAMP> can be used to check whether a translation catalog is
+<SAMP>‘msgcmp’</SAMP> can be used to check whether a translation catalog is
completely translated.
</P>
<P>
-<A NAME="IDX502"></A>
-<SAMP>`msgattrib´</SAMP> can be used to select and extract only the fuzzy
+<A NAME="IDX511"></A>
+<SAMP>‘msgattrib’</SAMP> can be used to select and extract only the fuzzy
or untranslated messages of a translation catalog.
</P>
<P>
-<SAMP>`msgen´</SAMP> is useful as a first step for preparing English translation
+<SAMP>‘msgen’</SAMP> is useful as a first step for preparing English translation
catalogs. It copies each message's msgid to its msgstr.
</P>
<P>
Finally, for those applications where all these various programs are not
-sufficient, a library <SAMP>`libgettextpo´</SAMP> is provided that can be used to
+sufficient, a library <SAMP>‘libgettextpo’</SAMP> is provided that can be used to
write other specialized programs that process PO files.
</P>
-<H2><A NAME="SEC73" HREF="gettext_toc.html#TOC73">9.1 Invoking the <CODE>msgcat</CODE> Program</A></H2>
+<H2><A NAME="SEC74" HREF="gettext_toc.html#TOC74">9.1 Invoking the <CODE>msgcat</CODE> Program</A></H2>
<P>
-<A NAME="IDX503"></A>
-<A NAME="IDX504"></A>
+<A NAME="IDX512"></A>
+<A NAME="IDX513"></A>
<PRE>
msgcat [<VAR>option</VAR>] [<VAR>inputfile</VAR>]...
</PRE>
<P>
-<A NAME="IDX505"></A>
-<A NAME="IDX506"></A>
+<A NAME="IDX514"></A>
+<A NAME="IDX515"></A>
The <CODE>msgcat</CODE> 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 <CODE>--more-than</CODE> option, greater commonality may be requested
before messages are printed. Conversely, the <CODE>--less-than</CODE> option may be
used to specify less commonality before messages are printed (i.e.
-<SAMP>`--less-than=2´</SAMP> will only print the unique messages). Translations,
+<SAMP>‘--less-than=2’</SAMP> will only print the unique messages). Translations,
comments and extract comments will be cumulated, except that if
<CODE>--use-first</CODE> is specified, they will be taken from the first PO file
to define them. File positions from all PO files will be cumulated.
</P>
-<H3><A NAME="SEC74" HREF="gettext_toc.html#TOC74">9.1.1 Input file location</A></H3>
+<H3><A NAME="SEC75" HREF="gettext_toc.html#TOC75">9.1.1 Input file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`<VAR>inputfile</VAR> ...´</SAMP>
+<DT><SAMP>‘<VAR>inputfile</VAR> ...’</SAMP>
<DD>
Input files.
-<DT><SAMP>`-f <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-f <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--files-from=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--files-from=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX507"></A>
-<A NAME="IDX508"></A>
+<A NAME="IDX516"></A>
+<A NAME="IDX517"></A>
Read the names of the input files from <VAR>file</VAR> instead of getting
them from the command line.
-<DT><SAMP>`-D <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-D <VAR>directory</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--directory=<VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘--directory=<VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX509"></A>
-<A NAME="IDX510"></A>
+<A NAME="IDX518"></A>
+<A NAME="IDX519"></A>
Add <VAR>directory</VAR> to the list of directories. Source files are
-searched relative to this list of directories. The resulting <TT>`.po´</TT>
+searched relative to this list of directories. The resulting <TT>‘.po’</TT>
file will be written relative to the current directory, though.
</DL>
<P>
-If <VAR>inputfile</VAR> is <SAMP>`-´</SAMP>, standard input is read.
+If <VAR>inputfile</VAR> is <SAMP>‘-’</SAMP>, standard input is read.
</P>
-<H3><A NAME="SEC75" HREF="gettext_toc.html#TOC75">9.1.2 Output file location</A></H3>
+<H3><A NAME="SEC76" HREF="gettext_toc.html#TOC76">9.1.2 Output file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`-o <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-o <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--output-file=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--output-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX511"></A>
-<A NAME="IDX512"></A>
+<A NAME="IDX520"></A>
+<A NAME="IDX521"></A>
Write output to specified file.
</DL>
<P>
-<A NAME="IDX513"></A>
+<A NAME="IDX522"></A>
The results are written to standard output if no output file is specified
-or if it is <SAMP>`-´</SAMP>.
+or if it is <SAMP>‘-’</SAMP>.
</P>
-<H3><A NAME="SEC76" HREF="gettext_toc.html#TOC76">9.1.3 Message selection</A></H3>
+<H3><A NAME="SEC77" HREF="gettext_toc.html#TOC77">9.1.3 Message selection</A></H3>
<DL COMPACT>
-<DT><SAMP>`-< <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-< <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--less-than=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--less-than=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX514"></A>
-<A NAME="IDX515"></A>
+<A NAME="IDX523"></A>
+<A NAME="IDX524"></A>
Print messages with less than <VAR>number</VAR> definitions, defaults to infinite
if not set.
-<DT><SAMP>`-> <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-> <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--more-than=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--more-than=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX516"></A>
-<A NAME="IDX517"></A>
+<A NAME="IDX525"></A>
+<A NAME="IDX526"></A>
Print messages with more than <VAR>number</VAR> definitions, defaults to 0 if not
set.
-<DT><SAMP>`-u´</SAMP>
+<DT><SAMP>‘-u’</SAMP>
<DD>
-<DT><SAMP>`--unique´</SAMP>
+<DT><SAMP>‘--unique’</SAMP>
<DD>
-<A NAME="IDX518"></A>
-<A NAME="IDX519"></A>
-Shorthand for <SAMP>`--less-than=2´</SAMP>. Requests that only unique messages be
+<A NAME="IDX527"></A>
+<A NAME="IDX528"></A>
+Shorthand for <SAMP>‘--less-than=2’</SAMP>. Requests that only unique messages be
printed.
</DL>
-<H3><A NAME="SEC77" HREF="gettext_toc.html#TOC77">9.1.4 Input file syntax</A></H3>
+<H3><A NAME="SEC78" HREF="gettext_toc.html#TOC78">9.1.4 Input file syntax</A></H3>
<DL COMPACT>
-<DT><SAMP>`-P´</SAMP>
+<DT><SAMP>‘-P’</SAMP>
<DD>
-<DT><SAMP>`--properties-input´</SAMP>
+<DT><SAMP>‘--properties-input’</SAMP>
<DD>
-<A NAME="IDX520"></A>
-<A NAME="IDX521"></A>
+<A NAME="IDX529"></A>
+<A NAME="IDX530"></A>
Assume the input files are Java ResourceBundles in Java <CODE>.properties</CODE>
syntax, not in PO file syntax.
-<DT><SAMP>`--stringtable-input´</SAMP>
+<DT><SAMP>‘--stringtable-input’</SAMP>
<DD>
-<A NAME="IDX522"></A>
+<A NAME="IDX531"></A>
Assume the input files are NeXTstep/GNUstep localized resource files in
<CODE>.strings</CODE> syntax, not in PO file syntax.
-<H3><A NAME="SEC78" HREF="gettext_toc.html#TOC78">9.1.5 Output details</A></H3>
+<H3><A NAME="SEC79" HREF="gettext_toc.html#TOC79">9.1.5 Output details</A></H3>
<DL COMPACT>
-<DT><SAMP>`-t´</SAMP>
+<DT><SAMP>‘-t’</SAMP>
<DD>
-<DT><SAMP>`--to-code=<VAR>name</VAR>´</SAMP>
+<DT><SAMP>‘--to-code=<VAR>name</VAR>’</SAMP>
<DD>
-<A NAME="IDX523"></A>
-<A NAME="IDX524"></A>
+<A NAME="IDX532"></A>
+<A NAME="IDX533"></A>
Specify encoding for output.
-<DT><SAMP>`--use-first´</SAMP>
+<DT><SAMP>‘--use-first’</SAMP>
<DD>
-<A NAME="IDX525"></A>
+<A NAME="IDX534"></A>
Use first available translation for each message. Don't merge several
translations into one.
-<DT><SAMP>`--force-po´</SAMP>
+<DT><SAMP>‘--force-po’</SAMP>
<DD>
-<A NAME="IDX526"></A>
+<A NAME="IDX535"></A>
Always write an output file even if it contains no message.
-<DT><SAMP>`-i´</SAMP>
+<DT><SAMP>‘-i’</SAMP>
<DD>
-<DT><SAMP>`--indent´</SAMP>
+<DT><SAMP>‘--indent’</SAMP>
<DD>
-<A NAME="IDX527"></A>
-<A NAME="IDX528"></A>
+<A NAME="IDX536"></A>
+<A NAME="IDX537"></A>
Write the .po file using indented style.
-<DT><SAMP>`--no-location´</SAMP>
+<DT><SAMP>‘--no-location’</SAMP>
<DD>
-<A NAME="IDX529"></A>
-Do not write <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines.
+<A NAME="IDX538"></A>
+Do not write <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines.
-<DT><SAMP>`-n´</SAMP>
+<DT><SAMP>‘-n’</SAMP>
<DD>
-<DT><SAMP>`--add-location´</SAMP>
+<DT><SAMP>‘--add-location’</SAMP>
<DD>
-<A NAME="IDX530"></A>
-<A NAME="IDX531"></A>
-Generate <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines (default).
+<A NAME="IDX539"></A>
+<A NAME="IDX540"></A>
+Generate <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines (default).
-<DT><SAMP>`--strict´</SAMP>
+<DT><SAMP>‘--strict’</SAMP>
<DD>
-<A NAME="IDX532"></A>
+<A NAME="IDX541"></A>
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
-<DT><SAMP>`-p´</SAMP>
+<DT><SAMP>‘-p’</SAMP>
<DD>
-<DT><SAMP>`--properties-output´</SAMP>
+<DT><SAMP>‘--properties-output’</SAMP>
<DD>
-<A NAME="IDX533"></A>
-<A NAME="IDX534"></A>
+<A NAME="IDX542"></A>
+<A NAME="IDX543"></A>
Write out a Java ResourceBundle in Java <CODE>.properties</CODE> syntax. Note
that this file format doesn't support plural forms and silently drops
obsolete messages.
-<DT><SAMP>`--stringtable-output´</SAMP>
+<DT><SAMP>‘--stringtable-output’</SAMP>
<DD>
-<A NAME="IDX535"></A>
+<A NAME="IDX544"></A>
Write out a NeXTstep/GNUstep localized resource file in <CODE>.strings</CODE> syntax.
Note that this file format doesn't support plural forms.
-<DT><SAMP>`-w <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-w <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--width=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--width=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX536"></A>
-<A NAME="IDX537"></A>
+<A NAME="IDX545"></A>
+<A NAME="IDX546"></A>
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 <VAR>number</VAR>.
-<DT><SAMP>`--no-wrap´</SAMP>
+<DT><SAMP>‘--no-wrap’</SAMP>
<DD>
-<A NAME="IDX538"></A>
+<A NAME="IDX547"></A>
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.
-<DT><SAMP>`-s´</SAMP>
+<DT><SAMP>‘-s’</SAMP>
<DD>
-<DT><SAMP>`--sort-output´</SAMP>
+<DT><SAMP>‘--sort-output’</SAMP>
<DD>
-<A NAME="IDX539"></A>
-<A NAME="IDX540"></A>
-<A NAME="IDX541"></A>
+<A NAME="IDX548"></A>
+<A NAME="IDX549"></A>
+<A NAME="IDX550"></A>
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
-<DT><SAMP>`-F´</SAMP>
+<DT><SAMP>‘-F’</SAMP>
<DD>
-<DT><SAMP>`--sort-by-file´</SAMP>
+<DT><SAMP>‘--sort-by-file’</SAMP>
<DD>
-<A NAME="IDX542"></A>
-<A NAME="IDX543"></A>
+<A NAME="IDX551"></A>
+<A NAME="IDX552"></A>
Sort output by file location.
</DL>
-<H3><A NAME="SEC79" HREF="gettext_toc.html#TOC79">9.1.6 Informative output</A></H3>
+<H3><A NAME="SEC80" HREF="gettext_toc.html#TOC80">9.1.6 Informative output</A></H3>
<DL COMPACT>
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX544"></A>
-<A NAME="IDX545"></A>
+<A NAME="IDX553"></A>
+<A NAME="IDX554"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX546"></A>
-<A NAME="IDX547"></A>
+<A NAME="IDX555"></A>
+<A NAME="IDX556"></A>
Output version information and exit.
</DL>
-<H2><A NAME="SEC80" HREF="gettext_toc.html#TOC80">9.2 Invoking the <CODE>msgconv</CODE> Program</A></H2>
+<H2><A NAME="SEC81" HREF="gettext_toc.html#TOC81">9.2 Invoking the <CODE>msgconv</CODE> Program</A></H2>
<P>
-<A NAME="IDX548"></A>
-<A NAME="IDX549"></A>
+<A NAME="IDX557"></A>
+<A NAME="IDX558"></A>
<PRE>
msgconv [<VAR>option</VAR>] [<VAR>inputfile</VAR>]
</PRE>
<P>
-<A NAME="IDX550"></A>
+<A NAME="IDX559"></A>
The <CODE>msgconv</CODE> program converts a translation catalog to a different
character encoding.
</P>
-<H3><A NAME="SEC81" HREF="gettext_toc.html#TOC81">9.2.1 Input file location</A></H3>
+<H3><A NAME="SEC82" HREF="gettext_toc.html#TOC82">9.2.1 Input file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`<VAR>inputfile</VAR>´</SAMP>
+<DT><SAMP>‘<VAR>inputfile</VAR>’</SAMP>
<DD>
Input PO file.
-<DT><SAMP>`-D <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-D <VAR>directory</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--directory=<VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘--directory=<VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX551"></A>
-<A NAME="IDX552"></A>
+<A NAME="IDX560"></A>
+<A NAME="IDX561"></A>
Add <VAR>directory</VAR> to the list of directories. Source files are
-searched relative to this list of directories. The resulting <TT>`.po´</TT>
+searched relative to this list of directories. The resulting <TT>‘.po’</TT>
file will be written relative to the current directory, though.
</DL>
<P>
-If no <VAR>inputfile</VAR> is given or if it is <SAMP>`-´</SAMP>, standard input is read.
+If no <VAR>inputfile</VAR> is given or if it is <SAMP>‘-’</SAMP>, standard input is read.
</P>
-<H3><A NAME="SEC82" HREF="gettext_toc.html#TOC82">9.2.2 Output file location</A></H3>
+<H3><A NAME="SEC83" HREF="gettext_toc.html#TOC83">9.2.2 Output file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`-o <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-o <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--output-file=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--output-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX553"></A>
-<A NAME="IDX554"></A>
+<A NAME="IDX562"></A>
+<A NAME="IDX563"></A>
Write output to specified file.
</DL>
<P>
The results are written to standard output if no output file is specified
-or if it is <SAMP>`-´</SAMP>.
+or if it is <SAMP>‘-’</SAMP>.
</P>
-<H3><A NAME="SEC83" HREF="gettext_toc.html#TOC83">9.2.3 Conversion target</A></H3>
+<H3><A NAME="SEC84" HREF="gettext_toc.html#TOC84">9.2.3 Conversion target</A></H3>
<DL COMPACT>
-<DT><SAMP>`-t´</SAMP>
+<DT><SAMP>‘-t’</SAMP>
<DD>
-<DT><SAMP>`--to-code=<VAR>name</VAR>´</SAMP>
+<DT><SAMP>‘--to-code=<VAR>name</VAR>’</SAMP>
<DD>
-<A NAME="IDX555"></A>
-<A NAME="IDX556"></A>
+<A NAME="IDX564"></A>
+<A NAME="IDX565"></A>
Specify encoding for output.
</DL>
</P>
-<H3><A NAME="SEC84" HREF="gettext_toc.html#TOC84">9.2.4 Input file syntax</A></H3>
+<H3><A NAME="SEC85" HREF="gettext_toc.html#TOC85">9.2.4 Input file syntax</A></H3>
<DL COMPACT>
-<DT><SAMP>`-P´</SAMP>
+<DT><SAMP>‘-P’</SAMP>
<DD>
-<DT><SAMP>`--properties-input´</SAMP>
+<DT><SAMP>‘--properties-input’</SAMP>
<DD>
-<A NAME="IDX557"></A>
-<A NAME="IDX558"></A>
+<A NAME="IDX566"></A>
+<A NAME="IDX567"></A>
Assume the input file is a Java ResourceBundle in Java <CODE>.properties</CODE>
syntax, not in PO file syntax.
-<DT><SAMP>`--stringtable-input´</SAMP>
+<DT><SAMP>‘--stringtable-input’</SAMP>
<DD>
-<A NAME="IDX559"></A>
+<A NAME="IDX568"></A>
Assume the input file is a NeXTstep/GNUstep localized resource file in
<CODE>.strings</CODE> syntax, not in PO file syntax.
-<H3><A NAME="SEC85" HREF="gettext_toc.html#TOC85">9.2.5 Output details</A></H3>
+<H3><A NAME="SEC86" HREF="gettext_toc.html#TOC86">9.2.5 Output details</A></H3>
<DL COMPACT>
-<DT><SAMP>`--force-po´</SAMP>
+<DT><SAMP>‘--force-po’</SAMP>
<DD>
-<A NAME="IDX560"></A>
+<A NAME="IDX569"></A>
Always write an output file even if it contains no message.
-<DT><SAMP>`-i´</SAMP>
+<DT><SAMP>‘-i’</SAMP>
<DD>
-<DT><SAMP>`--indent´</SAMP>
+<DT><SAMP>‘--indent’</SAMP>
<DD>
-<A NAME="IDX561"></A>
-<A NAME="IDX562"></A>
+<A NAME="IDX570"></A>
+<A NAME="IDX571"></A>
Write the .po file using indented style.
-<DT><SAMP>`--no-location´</SAMP>
+<DT><SAMP>‘--no-location’</SAMP>
<DD>
-<A NAME="IDX563"></A>
-Do not write <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines.
+<A NAME="IDX572"></A>
+Do not write <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines.
-<DT><SAMP>`--add-location´</SAMP>
+<DT><SAMP>‘--add-location’</SAMP>
<DD>
-<A NAME="IDX564"></A>
-Generate <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines (default).
+<A NAME="IDX573"></A>
+Generate <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines (default).
-<DT><SAMP>`--strict´</SAMP>
+<DT><SAMP>‘--strict’</SAMP>
<DD>
-<A NAME="IDX565"></A>
+<A NAME="IDX574"></A>
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
-<DT><SAMP>`-p´</SAMP>
+<DT><SAMP>‘-p’</SAMP>
<DD>
-<DT><SAMP>`--properties-output´</SAMP>
+<DT><SAMP>‘--properties-output’</SAMP>
<DD>
-<A NAME="IDX566"></A>
-<A NAME="IDX567"></A>
+<A NAME="IDX575"></A>
+<A NAME="IDX576"></A>
Write out a Java ResourceBundle in Java <CODE>.properties</CODE> syntax. Note
that this file format doesn't support plural forms and silently drops
obsolete messages.
-<DT><SAMP>`--stringtable-output´</SAMP>
+<DT><SAMP>‘--stringtable-output’</SAMP>
<DD>
-<A NAME="IDX568"></A>
+<A NAME="IDX577"></A>
Write out a NeXTstep/GNUstep localized resource file in <CODE>.strings</CODE> syntax.
Note that this file format doesn't support plural forms.
-<DT><SAMP>`-w <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-w <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--width=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--width=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX569"></A>
-<A NAME="IDX570"></A>
+<A NAME="IDX578"></A>
+<A NAME="IDX579"></A>
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 <VAR>number</VAR>.
-<DT><SAMP>`--no-wrap´</SAMP>
+<DT><SAMP>‘--no-wrap’</SAMP>
<DD>
-<A NAME="IDX571"></A>
+<A NAME="IDX580"></A>
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.
-<DT><SAMP>`-s´</SAMP>
+<DT><SAMP>‘-s’</SAMP>
<DD>
-<DT><SAMP>`--sort-output´</SAMP>
+<DT><SAMP>‘--sort-output’</SAMP>
<DD>
-<A NAME="IDX572"></A>
-<A NAME="IDX573"></A>
+<A NAME="IDX581"></A>
+<A NAME="IDX582"></A>
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
-<DT><SAMP>`-F´</SAMP>
+<DT><SAMP>‘-F’</SAMP>
<DD>
-<DT><SAMP>`--sort-by-file´</SAMP>
+<DT><SAMP>‘--sort-by-file’</SAMP>
<DD>
-<A NAME="IDX574"></A>
-<A NAME="IDX575"></A>
+<A NAME="IDX583"></A>
+<A NAME="IDX584"></A>
Sort output by file location.
</DL>
-<H3><A NAME="SEC86" HREF="gettext_toc.html#TOC86">9.2.6 Informative output</A></H3>
+<H3><A NAME="SEC87" HREF="gettext_toc.html#TOC87">9.2.6 Informative output</A></H3>
<DL COMPACT>
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX576"></A>
-<A NAME="IDX577"></A>
+<A NAME="IDX585"></A>
+<A NAME="IDX586"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX578"></A>
-<A NAME="IDX579"></A>
+<A NAME="IDX587"></A>
+<A NAME="IDX588"></A>
Output version information and exit.
</DL>
-<H2><A NAME="SEC87" HREF="gettext_toc.html#TOC87">9.3 Invoking the <CODE>msggrep</CODE> Program</A></H2>
+<H2><A NAME="SEC88" HREF="gettext_toc.html#TOC88">9.3 Invoking the <CODE>msggrep</CODE> Program</A></H2>
<P>
-<A NAME="IDX580"></A>
-<A NAME="IDX581"></A>
+<A NAME="IDX589"></A>
+<A NAME="IDX590"></A>
<PRE>
msggrep [<VAR>option</VAR>] [<VAR>inputfile</VAR>]
</PRE>
<P>
-<A NAME="IDX582"></A>
+<A NAME="IDX591"></A>
The <CODE>msggrep</CODE> program extracts all messages of a translation catalog
that match a given pattern or belong to some given source files.
</P>
-<H3><A NAME="SEC88" HREF="gettext_toc.html#TOC88">9.3.1 Input file location</A></H3>
+<H3><A NAME="SEC89" HREF="gettext_toc.html#TOC89">9.3.1 Input file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`<VAR>inputfile</VAR>´</SAMP>
+<DT><SAMP>‘<VAR>inputfile</VAR>’</SAMP>
<DD>
Input PO file.
-<DT><SAMP>`-D <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-D <VAR>directory</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--directory=<VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘--directory=<VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX583"></A>
-<A NAME="IDX584"></A>
+<A NAME="IDX592"></A>
+<A NAME="IDX593"></A>
Add <VAR>directory</VAR> to the list of directories. Source files are
-searched relative to this list of directories. The resulting <TT>`.po´</TT>
+searched relative to this list of directories. The resulting <TT>‘.po’</TT>
file will be written relative to the current directory, though.
</DL>
<P>
-If no <VAR>inputfile</VAR> is given or if it is <SAMP>`-´</SAMP>, standard input is read.
+If no <VAR>inputfile</VAR> is given or if it is <SAMP>‘-’</SAMP>, standard input is read.
</P>
-<H3><A NAME="SEC89" HREF="gettext_toc.html#TOC89">9.3.2 Output file location</A></H3>
+<H3><A NAME="SEC90" HREF="gettext_toc.html#TOC90">9.3.2 Output file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`-o <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-o <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--output-file=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--output-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX585"></A>
-<A NAME="IDX586"></A>
+<A NAME="IDX594"></A>
+<A NAME="IDX595"></A>
Write output to specified file.
</DL>
<P>
The results are written to standard output if no output file is specified
-or if it is <SAMP>`-´</SAMP>.
+or if it is <SAMP>‘-’</SAMP>.
</P>
-<H3><A NAME="SEC90" HREF="gettext_toc.html#TOC90">9.3.3 Message selection</A></H3>
+<H3><A NAME="SEC91" HREF="gettext_toc.html#TOC91">9.3.3 Message selection</A></H3>
<PRE>
[-N <VAR>sourcefile</VAR>]... [-M <VAR>domainname</VAR>]...
- [-K <VAR>msgid-pattern</VAR>] [-T <VAR>msgstr-pattern</VAR>] [-C <VAR>comment-pattern</VAR>]
+ [-J <VAR>msgctxt-pattern</VAR> [-K <VAR>msgid-pattern</VAR>] [-T <VAR>msgstr-pattern</VAR>]
+ [-C <VAR>comment-pattern</VAR>]
</PRE>
<P>
<LI>or if it comes from one of the specified domains,
-<LI>or if <SAMP>`-K´</SAMP> is given and its key (msgid or msgid_plural) matches
+<LI>or if <SAMP>‘-J’</SAMP> is given and its context (msgctxt) matches
+
+ <VAR>msgctxt-pattern</VAR>,
+<LI>or if <SAMP>‘-K’</SAMP> is given and its key (msgid or msgid_plural) matches
<VAR>msgid-pattern</VAR>,
-<LI>or if <SAMP>`-T´</SAMP> is given and its translation (msgstr) matches
+<LI>or if <SAMP>‘-T’</SAMP> is given and its translation (msgstr) matches
<VAR>msgstr-pattern</VAR>,
-<LI>or if <SAMP>`-C´</SAMP> is given and the translator's comment matches
+<LI>or if <SAMP>‘-C’</SAMP> is given and the translator's comment matches
<VAR>comment-pattern</VAR>.
</UL>
</P>
<DL COMPACT>
-<DT><SAMP>`-N <VAR>sourcefile</VAR>´</SAMP>
+<DT><SAMP>‘-N <VAR>sourcefile</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--location=<VAR>sourcefile</VAR>´</SAMP>
+<DT><SAMP>‘--location=<VAR>sourcefile</VAR>’</SAMP>
<DD>
-<A NAME="IDX587"></A>
-<A NAME="IDX588"></A>
+<A NAME="IDX596"></A>
+<A NAME="IDX597"></A>
Select messages extracted from <VAR>sourcefile</VAR>. <VAR>sourcefile</VAR> can be
either a literal file name or a wildcard pattern.
-<DT><SAMP>`-M <VAR>domainname</VAR>´</SAMP>
+<DT><SAMP>‘-M <VAR>domainname</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--domain=<VAR>domainname</VAR>´</SAMP>
+<DT><SAMP>‘--domain=<VAR>domainname</VAR>’</SAMP>
<DD>
-<A NAME="IDX589"></A>
-<A NAME="IDX590"></A>
+<A NAME="IDX598"></A>
+<A NAME="IDX599"></A>
Select messages belonging to domain <VAR>domainname</VAR>.
-<DT><SAMP>`-K´</SAMP>
+<DT><SAMP>‘-J’</SAMP>
<DD>
-<DT><SAMP>`--msgid´</SAMP>
+<DT><SAMP>‘--msgctxt’</SAMP>
<DD>
-<A NAME="IDX591"></A>
-<A NAME="IDX592"></A>
+<A NAME="IDX600"></A>
+<A NAME="IDX601"></A>
+Start of patterns for the msgctxt.
+
+<DT><SAMP>‘-K’</SAMP>
+<DD>
+<DT><SAMP>‘--msgid’</SAMP>
+<DD>
+<A NAME="IDX602"></A>
+<A NAME="IDX603"></A>
Start of patterns for the msgid.
-<DT><SAMP>`-T´</SAMP>
+<DT><SAMP>‘-T’</SAMP>
<DD>
-<DT><SAMP>`--msgstr´</SAMP>
+<DT><SAMP>‘--msgstr’</SAMP>
<DD>
-<A NAME="IDX593"></A>
-<A NAME="IDX594"></A>
+<A NAME="IDX604"></A>
+<A NAME="IDX605"></A>
Start of patterns for the msgstr.
-<DT><SAMP>`-C´</SAMP>
+<DT><SAMP>‘-C’</SAMP>
<DD>
-<DT><SAMP>`--comment´</SAMP>
+<DT><SAMP>‘--comment’</SAMP>
<DD>
-<A NAME="IDX595"></A>
-<A NAME="IDX596"></A>
+<A NAME="IDX606"></A>
+<A NAME="IDX607"></A>
Start of patterns for the translator's comment.
-<DT><SAMP>`-E´</SAMP>
+<DT><SAMP>‘-X’</SAMP>
<DD>
-<DT><SAMP>`--extended-regexp´</SAMP>
+<DT><SAMP>‘--extracted-comment’</SAMP>
<DD>
-<A NAME="IDX597"></A>
-<A NAME="IDX598"></A>
+<A NAME="IDX608"></A>
+<A NAME="IDX609"></A>
+Start of patterns for the extracted comments.
+
+<DT><SAMP>‘-E’</SAMP>
+<DD>
+<DT><SAMP>‘--extended-regexp’</SAMP>
+<DD>
+<A NAME="IDX610"></A>
+<A NAME="IDX611"></A>
Specify that <VAR>pattern</VAR> is an extended regular expression.
-<DT><SAMP>`-F´</SAMP>
+<DT><SAMP>‘-F’</SAMP>
<DD>
-<DT><SAMP>`--fixed-strings´</SAMP>
+<DT><SAMP>‘--fixed-strings’</SAMP>
<DD>
-<A NAME="IDX599"></A>
-<A NAME="IDX600"></A>
+<A NAME="IDX612"></A>
+<A NAME="IDX613"></A>
Specify that <VAR>pattern</VAR> is a set of newline-separated strings.
-<DT><SAMP>`-e <VAR>pattern</VAR>´</SAMP>
+<DT><SAMP>‘-e <VAR>pattern</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--regexp=<VAR>pattern</VAR>´</SAMP>
+<DT><SAMP>‘--regexp=<VAR>pattern</VAR>’</SAMP>
<DD>
-<A NAME="IDX601"></A>
-<A NAME="IDX602"></A>
+<A NAME="IDX614"></A>
+<A NAME="IDX615"></A>
Use <VAR>pattern</VAR> as a regular expression.
-<DT><SAMP>`-f <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-f <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--file=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX603"></A>
-<A NAME="IDX604"></A>
+<A NAME="IDX616"></A>
+<A NAME="IDX617"></A>
Obtain <VAR>pattern</VAR> from <VAR>file</VAR>.
-<DT><SAMP>`-i´</SAMP>
+<DT><SAMP>‘-i’</SAMP>
<DD>
-<DT><SAMP>`--ignore-case´</SAMP>
+<DT><SAMP>‘--ignore-case’</SAMP>
<DD>
-<A NAME="IDX605"></A>
-<A NAME="IDX606"></A>
+<A NAME="IDX618"></A>
+<A NAME="IDX619"></A>
Ignore case distinctions.
+<DT><SAMP>‘-v’</SAMP>
+<DD>
+<DT><SAMP>‘--invert-match’</SAMP>
+<DD>
+<A NAME="IDX620"></A>
+<A NAME="IDX621"></A>
+Output only the messages that do not match any selection criterion, instead
+of the messages that match a selection criterion.
+
</DL>
-<H3><A NAME="SEC91" HREF="gettext_toc.html#TOC91">9.3.4 Input file syntax</A></H3>
+<H3><A NAME="SEC92" HREF="gettext_toc.html#TOC92">9.3.4 Input file syntax</A></H3>
<DL COMPACT>
-<DT><SAMP>`-P´</SAMP>
+<DT><SAMP>‘-P’</SAMP>
<DD>
-<DT><SAMP>`--properties-input´</SAMP>
+<DT><SAMP>‘--properties-input’</SAMP>
<DD>
-<A NAME="IDX607"></A>
-<A NAME="IDX608"></A>
+<A NAME="IDX622"></A>
+<A NAME="IDX623"></A>
Assume the input file is a Java ResourceBundle in Java <CODE>.properties</CODE>
syntax, not in PO file syntax.
-<DT><SAMP>`--stringtable-input´</SAMP>
+<DT><SAMP>‘--stringtable-input’</SAMP>
<DD>
-<A NAME="IDX609"></A>
+<A NAME="IDX624"></A>
Assume the input file is a NeXTstep/GNUstep localized resource file in
<CODE>.strings</CODE> syntax, not in PO file syntax.
-<H3><A NAME="SEC92" HREF="gettext_toc.html#TOC92">9.3.5 Output details</A></H3>
+<H3><A NAME="SEC93" HREF="gettext_toc.html#TOC93">9.3.5 Output details</A></H3>
<DL COMPACT>
-<DT><SAMP>`--force-po´</SAMP>
+<DT><SAMP>‘--force-po’</SAMP>
<DD>
-<A NAME="IDX610"></A>
+<A NAME="IDX625"></A>
Always write an output file even if it contains no message.
-<DT><SAMP>`--indent´</SAMP>
+<DT><SAMP>‘--indent’</SAMP>
<DD>
-<A NAME="IDX611"></A>
+<A NAME="IDX626"></A>
Write the .po file using indented style.
-<DT><SAMP>`--no-location´</SAMP>
+<DT><SAMP>‘--no-location’</SAMP>
<DD>
-<A NAME="IDX612"></A>
-Do not write <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines.
+<A NAME="IDX627"></A>
+Do not write <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines.
-<DT><SAMP>`--add-location´</SAMP>
+<DT><SAMP>‘--add-location’</SAMP>
<DD>
-<A NAME="IDX613"></A>
-Generate <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines (default).
+<A NAME="IDX628"></A>
+Generate <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines (default).
-<DT><SAMP>`--strict´</SAMP>
+<DT><SAMP>‘--strict’</SAMP>
<DD>
-<A NAME="IDX614"></A>
+<A NAME="IDX629"></A>
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
-<DT><SAMP>`-p´</SAMP>
+<DT><SAMP>‘-p’</SAMP>
<DD>
-<DT><SAMP>`--properties-output´</SAMP>
+<DT><SAMP>‘--properties-output’</SAMP>
<DD>
-<A NAME="IDX615"></A>
-<A NAME="IDX616"></A>
+<A NAME="IDX630"></A>
+<A NAME="IDX631"></A>
Write out a Java ResourceBundle in Java <CODE>.properties</CODE> syntax. Note
that this file format doesn't support plural forms and silently drops
obsolete messages.
-<DT><SAMP>`--stringtable-output´</SAMP>
+<DT><SAMP>‘--stringtable-output’</SAMP>
<DD>
-<A NAME="IDX617"></A>
+<A NAME="IDX632"></A>
Write out a NeXTstep/GNUstep localized resource file in <CODE>.strings</CODE> syntax.
Note that this file format doesn't support plural forms.
-<DT><SAMP>`-w <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-w <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--width=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--width=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX618"></A>
-<A NAME="IDX619"></A>
+<A NAME="IDX633"></A>
+<A NAME="IDX634"></A>
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 <VAR>number</VAR>.
-<DT><SAMP>`--no-wrap´</SAMP>
+<DT><SAMP>‘--no-wrap’</SAMP>
<DD>
-<A NAME="IDX620"></A>
+<A NAME="IDX635"></A>
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.
-<DT><SAMP>`--sort-output´</SAMP>
+<DT><SAMP>‘--sort-output’</SAMP>
<DD>
-<A NAME="IDX621"></A>
+<A NAME="IDX636"></A>
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
-<DT><SAMP>`--sort-by-file´</SAMP>
+<DT><SAMP>‘--sort-by-file’</SAMP>
<DD>
-<A NAME="IDX622"></A>
+<A NAME="IDX637"></A>
Sort output by file location.
</DL>
-<H3><A NAME="SEC93" HREF="gettext_toc.html#TOC93">9.3.6 Informative output</A></H3>
+<H3><A NAME="SEC94" HREF="gettext_toc.html#TOC94">9.3.6 Informative output</A></H3>
<DL COMPACT>
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX623"></A>
-<A NAME="IDX624"></A>
+<A NAME="IDX638"></A>
+<A NAME="IDX639"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX625"></A>
-<A NAME="IDX626"></A>
+<A NAME="IDX640"></A>
+<A NAME="IDX641"></A>
Output version information and exit.
</DL>
-<H2><A NAME="SEC94" HREF="gettext_toc.html#TOC94">9.4 Invoking the <CODE>msgfilter</CODE> Program</A></H2>
+<H2><A NAME="SEC95" HREF="gettext_toc.html#TOC95">9.4 Invoking the <CODE>msgfilter</CODE> Program</A></H2>
<P>
-<A NAME="IDX627"></A>
-<A NAME="IDX628"></A>
+<A NAME="IDX642"></A>
+<A NAME="IDX643"></A>
<PRE>
msgfilter [<VAR>option</VAR>] <VAR>filter</VAR> [<VAR>filter-option</VAR>]
</PRE>
<P>
-<A NAME="IDX629"></A>
+<A NAME="IDX644"></A>
The <CODE>msgfilter</CODE> program applies a filter to all translations of a
translation catalog.
</P>
-<H3><A NAME="SEC95" HREF="gettext_toc.html#TOC95">9.4.1 Input file location</A></H3>
+<H3><A NAME="SEC96" HREF="gettext_toc.html#TOC96">9.4.1 Input file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`-i <VAR>inputfile</VAR>´</SAMP>
+<DT><SAMP>‘-i <VAR>inputfile</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--input=<VAR>inputfile</VAR>´</SAMP>
+<DT><SAMP>‘--input=<VAR>inputfile</VAR>’</SAMP>
<DD>
-<A NAME="IDX630"></A>
-<A NAME="IDX631"></A>
+<A NAME="IDX645"></A>
+<A NAME="IDX646"></A>
Input PO file.
-<DT><SAMP>`-D <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-D <VAR>directory</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--directory=<VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘--directory=<VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX632"></A>
-<A NAME="IDX633"></A>
+<A NAME="IDX647"></A>
+<A NAME="IDX648"></A>
Add <VAR>directory</VAR> to the list of directories. Source files are
-searched relative to this list of directories. The resulting <TT>`.po´</TT>
+searched relative to this list of directories. The resulting <TT>‘.po’</TT>
file will be written relative to the current directory, though.
</DL>
<P>
-If no <VAR>inputfile</VAR> is given or if it is <SAMP>`-´</SAMP>, standard input is read.
+If no <VAR>inputfile</VAR> is given or if it is <SAMP>‘-’</SAMP>, standard input is read.
</P>
-<H3><A NAME="SEC96" HREF="gettext_toc.html#TOC96">9.4.2 Output file location</A></H3>
+<H3><A NAME="SEC97" HREF="gettext_toc.html#TOC97">9.4.2 Output file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`-o <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-o <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--output-file=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--output-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX634"></A>
-<A NAME="IDX635"></A>
+<A NAME="IDX649"></A>
+<A NAME="IDX650"></A>
Write output to specified file.
</DL>
<P>
The results are written to standard output if no output file is specified
-or if it is <SAMP>`-´</SAMP>.
+or if it is <SAMP>‘-’</SAMP>.
</P>
-<H3><A NAME="SEC97" HREF="gettext_toc.html#TOC97">9.4.3 The filter</A></H3>
+<H3><A NAME="SEC98" HREF="gettext_toc.html#TOC98">9.4.3 The filter</A></H3>
<P>
The <VAR>filter</VAR> can be any program that reads a translation from standard
input and writes a modified translation to standard output. A frequently
-used filter is <SAMP>`sed´</SAMP>.
+used filter is <SAMP>‘sed’</SAMP>. A few particular built-in filters are also
+recognized.
</P>
<P>
-<A NAME="IDX636"></A>
-Note: It is your responsibility to ensure that the <VAR>filter</VAR> can cope
+<A NAME="IDX651"></A>
+Note: If the filter is not a built-in filter, you have to care about encodings:
+It is your responsibility to ensure that the <VAR>filter</VAR> can cope
with input encoded in the translation catalog's encoding. If the
<VAR>filter</VAR> wants input in a particular encoding, you can in a first step
-convert the translation catalog to that encoding using the <SAMP>`msgconv´</SAMP>
-program, before invoking <SAMP>`msgfilter´</SAMP>. If the <VAR>filter</VAR> wants input
+convert the translation catalog to that encoding using the <SAMP>‘msgconv’</SAMP>
+program, before invoking <SAMP>‘msgfilter’</SAMP>. If the <VAR>filter</VAR> wants input
in the locale's encoding, but you want to avoid the locale's encoding, then
you can first convert the translation catalog to UTF-8 using the
-<SAMP>`msgconv´</SAMP> program and then make <SAMP>`msgfilter´</SAMP> work in an UTF-8
+<SAMP>‘msgconv’</SAMP> program and then make <SAMP>‘msgfilter’</SAMP> work in an UTF-8
locale, by using the <CODE>LC_ALL</CODE> environment variable.
</P>
<P>
-<A NAME="IDX637"></A>
+<A NAME="IDX652"></A>
Note: Most translations in a translation catalog don't end with a newline
character. For this reason, it is important that the <VAR>filter</VAR>
recognizes its last input line even if it ends without a newline, and that
-it doesn't add an undesired trailing newline at the end. The <SAMP>`sed´</SAMP>
+it doesn't add an undesired trailing newline at the end. The <SAMP>‘sed’</SAMP>
program on some platforms is known to ignore the last line of input if it
is not terminated with a newline. You can use GNU <CODE>sed</CODE> instead; it
does not have this limitation.
</P>
-<H3><A NAME="SEC98" HREF="gettext_toc.html#TOC98">9.4.4 Useful <VAR>filter-option</VAR>s when the <VAR>filter</VAR> is <SAMP>`sed´</SAMP></A></H3>
+<H3><A NAME="SEC99" HREF="gettext_toc.html#TOC99">9.4.4 Useful <VAR>filter-option</VAR>s when the <VAR>filter</VAR> is <SAMP>‘sed’</SAMP></A></H3>
<DL COMPACT>
-<DT><SAMP>`-e <VAR>script</VAR>´</SAMP>
+<DT><SAMP>‘-e <VAR>script</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--expression=<VAR>script</VAR>´</SAMP>
+<DT><SAMP>‘--expression=<VAR>script</VAR>’</SAMP>
<DD>
-<A NAME="IDX638"></A>
-<A NAME="IDX639"></A>
+<A NAME="IDX653"></A>
+<A NAME="IDX654"></A>
Add <VAR>script</VAR> to the commands to be executed.
-<DT><SAMP>`-f <VAR>scriptfile</VAR>´</SAMP>
+<DT><SAMP>‘-f <VAR>scriptfile</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--file=<VAR>scriptfile</VAR>´</SAMP>
+<DT><SAMP>‘--file=<VAR>scriptfile</VAR>’</SAMP>
<DD>
-<A NAME="IDX640"></A>
-<A NAME="IDX641"></A>
+<A NAME="IDX655"></A>
+<A NAME="IDX656"></A>
Add the contents of <VAR>scriptfile</VAR> to the commands to be executed.
-<DT><SAMP>`-n´</SAMP>
+<DT><SAMP>‘-n’</SAMP>
<DD>
-<DT><SAMP>`--quiet´</SAMP>
+<DT><SAMP>‘--quiet’</SAMP>
<DD>
-<DT><SAMP>`--silent´</SAMP>
+<DT><SAMP>‘--silent’</SAMP>
<DD>
-<A NAME="IDX642"></A>
-<A NAME="IDX643"></A>
-<A NAME="IDX644"></A>
+<A NAME="IDX657"></A>
+<A NAME="IDX658"></A>
+<A NAME="IDX659"></A>
Suppress automatic printing of pattern space.
</DL>
-<H3><A NAME="SEC99" HREF="gettext_toc.html#TOC99">9.4.5 Input file syntax</A></H3>
+<H3><A NAME="SEC100" HREF="gettext_toc.html#TOC100">9.4.5 Built-in <VAR>filter</VAR>s</A></H3>
+
+<P>
+<A NAME="IDX660"></A>
+<A NAME="IDX661"></A>
+The filter <SAMP>‘recode-sr-latin’</SAMP> is recognized as a built-in filter.
+The command <SAMP>‘recode-sr-latin’</SAMP> converts Serbian text, written in the
+Cyrillic script, to the Latin script.
+The command <SAMP>‘msgfilter recode-sr-latin’</SAMP> applies this conversion to the
+translations of a PO file. Thus, it can be used to convert an <TT>‘sr.po’</TT>
+file to an <TT>‘sr@latin.po’</TT> file.
+
+</P>
+<P>
+The use of built-in filters is not sensitive to the current locale's encoding.
+Moreover, when used with a built-in filter, <SAMP>‘msgfilter’</SAMP> can automatically
+convert the message catalog to the UTF-8 encoding when needed.
+
+</P>
+
+
+<H3><A NAME="SEC101" HREF="gettext_toc.html#TOC101">9.4.6 Input file syntax</A></H3>
<DL COMPACT>
-<DT><SAMP>`-P´</SAMP>
+<DT><SAMP>‘-P’</SAMP>
<DD>
-<DT><SAMP>`--properties-input´</SAMP>
+<DT><SAMP>‘--properties-input’</SAMP>
<DD>
-<A NAME="IDX645"></A>
-<A NAME="IDX646"></A>
+<A NAME="IDX662"></A>
+<A NAME="IDX663"></A>
Assume the input file is a Java ResourceBundle in Java <CODE>.properties</CODE>
syntax, not in PO file syntax.
-<DT><SAMP>`--stringtable-input´</SAMP>
+<DT><SAMP>‘--stringtable-input’</SAMP>
<DD>
-<A NAME="IDX647"></A>
+<A NAME="IDX664"></A>
Assume the input file is a NeXTstep/GNUstep localized resource file in
<CODE>.strings</CODE> syntax, not in PO file syntax.
-<H3><A NAME="SEC100" HREF="gettext_toc.html#TOC100">9.4.6 Output details</A></H3>
+<H3><A NAME="SEC102" HREF="gettext_toc.html#TOC102">9.4.7 Output details</A></H3>
<DL COMPACT>
-<DT><SAMP>`--force-po´</SAMP>
+<DT><SAMP>‘--force-po’</SAMP>
<DD>
-<A NAME="IDX648"></A>
+<A NAME="IDX665"></A>
Always write an output file even if it contains no message.
-<DT><SAMP>`--indent´</SAMP>
+<DT><SAMP>‘--indent’</SAMP>
<DD>
-<A NAME="IDX649"></A>
+<A NAME="IDX666"></A>
Write the .po file using indented style.
-<DT><SAMP>`--keep-header´</SAMP>
+<DT><SAMP>‘--keep-header’</SAMP>
<DD>
-<A NAME="IDX650"></A>
-Keep the header entry, i.e. the message with <SAMP>`msgid ""´</SAMP>, unmodified,
+<A NAME="IDX667"></A>
+Keep the header entry, i.e. the message with <SAMP>‘msgid ""’</SAMP>, unmodified,
instead of filtering it. By default, the header entry is subject to
filtering like any other message.
-<DT><SAMP>`--no-location´</SAMP>
+<DT><SAMP>‘--no-location’</SAMP>
<DD>
-<A NAME="IDX651"></A>
-Do not write <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines.
+<A NAME="IDX668"></A>
+Do not write <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines.
-<DT><SAMP>`--add-location´</SAMP>
+<DT><SAMP>‘--add-location’</SAMP>
<DD>
-<A NAME="IDX652"></A>
-Generate <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines (default).
+<A NAME="IDX669"></A>
+Generate <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines (default).
-<DT><SAMP>`--strict´</SAMP>
+<DT><SAMP>‘--strict’</SAMP>
<DD>
-<A NAME="IDX653"></A>
+<A NAME="IDX670"></A>
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
-<DT><SAMP>`-p´</SAMP>
+<DT><SAMP>‘-p’</SAMP>
<DD>
-<DT><SAMP>`--properties-output´</SAMP>
+<DT><SAMP>‘--properties-output’</SAMP>
<DD>
-<A NAME="IDX654"></A>
-<A NAME="IDX655"></A>
+<A NAME="IDX671"></A>
+<A NAME="IDX672"></A>
Write out a Java ResourceBundle in Java <CODE>.properties</CODE> syntax. Note
that this file format doesn't support plural forms and silently drops
obsolete messages.
-<DT><SAMP>`--stringtable-output´</SAMP>
+<DT><SAMP>‘--stringtable-output’</SAMP>
<DD>
-<A NAME="IDX656"></A>
+<A NAME="IDX673"></A>
Write out a NeXTstep/GNUstep localized resource file in <CODE>.strings</CODE> syntax.
Note that this file format doesn't support plural forms.
-<DT><SAMP>`-w <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-w <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--width=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--width=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX657"></A>
-<A NAME="IDX658"></A>
+<A NAME="IDX674"></A>
+<A NAME="IDX675"></A>
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 <VAR>number</VAR>.
-<DT><SAMP>`--no-wrap´</SAMP>
+<DT><SAMP>‘--no-wrap’</SAMP>
<DD>
-<A NAME="IDX659"></A>
+<A NAME="IDX676"></A>
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.
-<DT><SAMP>`-s´</SAMP>
+<DT><SAMP>‘-s’</SAMP>
<DD>
-<DT><SAMP>`--sort-output´</SAMP>
+<DT><SAMP>‘--sort-output’</SAMP>
<DD>
-<A NAME="IDX660"></A>
-<A NAME="IDX661"></A>
+<A NAME="IDX677"></A>
+<A NAME="IDX678"></A>
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
-<DT><SAMP>`-F´</SAMP>
+<DT><SAMP>‘-F’</SAMP>
<DD>
-<DT><SAMP>`--sort-by-file´</SAMP>
+<DT><SAMP>‘--sort-by-file’</SAMP>
<DD>
-<A NAME="IDX662"></A>
-<A NAME="IDX663"></A>
+<A NAME="IDX679"></A>
+<A NAME="IDX680"></A>
Sort output by file location.
</DL>
-<H3><A NAME="SEC101" HREF="gettext_toc.html#TOC101">9.4.7 Informative output</A></H3>
+<H3><A NAME="SEC103" HREF="gettext_toc.html#TOC103">9.4.8 Informative output</A></H3>
<DL COMPACT>
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX664"></A>
-<A NAME="IDX665"></A>
+<A NAME="IDX681"></A>
+<A NAME="IDX682"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX666"></A>
-<A NAME="IDX667"></A>
+<A NAME="IDX683"></A>
+<A NAME="IDX684"></A>
Output version information and exit.
</DL>
-<H2><A NAME="SEC102" HREF="gettext_toc.html#TOC102">9.5 Invoking the <CODE>msguniq</CODE> Program</A></H2>
+<H2><A NAME="SEC104" HREF="gettext_toc.html#TOC104">9.5 Invoking the <CODE>msguniq</CODE> Program</A></H2>
<P>
-<A NAME="IDX668"></A>
-<A NAME="IDX669"></A>
+<A NAME="IDX685"></A>
+<A NAME="IDX686"></A>
<PRE>
msguniq [<VAR>option</VAR>] [<VAR>inputfile</VAR>]
</PRE>
<P>
-<A NAME="IDX670"></A>
-<A NAME="IDX671"></A>
+<A NAME="IDX687"></A>
+<A NAME="IDX688"></A>
The <CODE>msguniq</CODE> 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 <CODE>msgfmt</CODE>,
<CODE>msgmerge</CODE> or <CODE>msgcat</CODE>. By default, duplicates are merged
-together. When using the <SAMP>`--repeated´</SAMP> option, only duplicates are
+together. When using the <SAMP>‘--repeated’</SAMP> option, only duplicates are
output, and all other messages are discarded. Comments and extracted
-comments will be cumulated, except that if <SAMP>`--use-first´</SAMP> is
+comments will be cumulated, except that if <SAMP>‘--use-first’</SAMP> is
specified, they will be taken from the first translation. File positions
-will be cumulated. When using the <SAMP>`--unique´</SAMP> option, duplicates are
+will be cumulated. When using the <SAMP>‘--unique’</SAMP> option, duplicates are
discarded.
</P>
-<H3><A NAME="SEC103" HREF="gettext_toc.html#TOC103">9.5.1 Input file location</A></H3>
+<H3><A NAME="SEC105" HREF="gettext_toc.html#TOC105">9.5.1 Input file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`<VAR>inputfile</VAR>´</SAMP>
+<DT><SAMP>‘<VAR>inputfile</VAR>’</SAMP>
<DD>
Input PO file.
-<DT><SAMP>`-D <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-D <VAR>directory</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--directory=<VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘--directory=<VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX672"></A>
-<A NAME="IDX673"></A>
+<A NAME="IDX689"></A>
+<A NAME="IDX690"></A>
Add <VAR>directory</VAR> to the list of directories. Source files are
-searched relative to this list of directories. The resulting <TT>`.po´</TT>
+searched relative to this list of directories. The resulting <TT>‘.po’</TT>
file will be written relative to the current directory, though.
</DL>
<P>
-If no <VAR>inputfile</VAR> is given or if it is <SAMP>`-´</SAMP>, standard input is read.
+If no <VAR>inputfile</VAR> is given or if it is <SAMP>‘-’</SAMP>, standard input is read.
</P>
-<H3><A NAME="SEC104" HREF="gettext_toc.html#TOC104">9.5.2 Output file location</A></H3>
+<H3><A NAME="SEC106" HREF="gettext_toc.html#TOC106">9.5.2 Output file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`-o <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-o <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--output-file=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--output-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX674"></A>
-<A NAME="IDX675"></A>
+<A NAME="IDX691"></A>
+<A NAME="IDX692"></A>
Write output to specified file.
</DL>
<P>
The results are written to standard output if no output file is specified
-or if it is <SAMP>`-´</SAMP>.
+or if it is <SAMP>‘-’</SAMP>.
</P>
-<H3><A NAME="SEC105" HREF="gettext_toc.html#TOC105">9.5.3 Message selection</A></H3>
+<H3><A NAME="SEC107" HREF="gettext_toc.html#TOC107">9.5.3 Message selection</A></H3>
<DL COMPACT>
-<DT><SAMP>`-d´</SAMP>
+<DT><SAMP>‘-d’</SAMP>
<DD>
-<DT><SAMP>`--repeated´</SAMP>
+<DT><SAMP>‘--repeated’</SAMP>
<DD>
-<A NAME="IDX676"></A>
-<A NAME="IDX677"></A>
+<A NAME="IDX693"></A>
+<A NAME="IDX694"></A>
Print only duplicates.
-<DT><SAMP>`-u´</SAMP>
+<DT><SAMP>‘-u’</SAMP>
<DD>
-<DT><SAMP>`--unique´</SAMP>
+<DT><SAMP>‘--unique’</SAMP>
<DD>
-<A NAME="IDX678"></A>
-<A NAME="IDX679"></A>
+<A NAME="IDX695"></A>
+<A NAME="IDX696"></A>
Print only unique messages, discard duplicates.
</DL>
-<H3><A NAME="SEC106" HREF="gettext_toc.html#TOC106">9.5.4 Input file syntax</A></H3>
+<H3><A NAME="SEC108" HREF="gettext_toc.html#TOC108">9.5.4 Input file syntax</A></H3>
<DL COMPACT>
-<DT><SAMP>`-P´</SAMP>
+<DT><SAMP>‘-P’</SAMP>
<DD>
-<DT><SAMP>`--properties-input´</SAMP>
+<DT><SAMP>‘--properties-input’</SAMP>
<DD>
-<A NAME="IDX680"></A>
-<A NAME="IDX681"></A>
+<A NAME="IDX697"></A>
+<A NAME="IDX698"></A>
Assume the input file is a Java ResourceBundle in Java <CODE>.properties</CODE>
syntax, not in PO file syntax.
-<DT><SAMP>`--stringtable-input´</SAMP>
+<DT><SAMP>‘--stringtable-input’</SAMP>
<DD>
-<A NAME="IDX682"></A>
+<A NAME="IDX699"></A>
Assume the input file is a NeXTstep/GNUstep localized resource file in
<CODE>.strings</CODE> syntax, not in PO file syntax.
-<H3><A NAME="SEC107" HREF="gettext_toc.html#TOC107">9.5.5 Output details</A></H3>
+<H3><A NAME="SEC109" HREF="gettext_toc.html#TOC109">9.5.5 Output details</A></H3>
<DL COMPACT>
-<DT><SAMP>`-t´</SAMP>
+<DT><SAMP>‘-t’</SAMP>
<DD>
-<DT><SAMP>`--to-code=<VAR>name</VAR>´</SAMP>
+<DT><SAMP>‘--to-code=<VAR>name</VAR>’</SAMP>
<DD>
-<A NAME="IDX683"></A>
-<A NAME="IDX684"></A>
+<A NAME="IDX700"></A>
+<A NAME="IDX701"></A>
Specify encoding for output.
-<DT><SAMP>`--use-first´</SAMP>
+<DT><SAMP>‘--use-first’</SAMP>
<DD>
-<A NAME="IDX685"></A>
+<A NAME="IDX702"></A>
Use first available translation for each message. Don't merge several
translations into one.
-<DT><SAMP>`--force-po´</SAMP>
+<DT><SAMP>‘--force-po’</SAMP>
<DD>
-<A NAME="IDX686"></A>
+<A NAME="IDX703"></A>
Always write an output file even if it contains no message.
-<DT><SAMP>`-i´</SAMP>
+<DT><SAMP>‘-i’</SAMP>
<DD>
-<DT><SAMP>`--indent´</SAMP>
+<DT><SAMP>‘--indent’</SAMP>
<DD>
-<A NAME="IDX687"></A>
-<A NAME="IDX688"></A>
+<A NAME="IDX704"></A>
+<A NAME="IDX705"></A>
Write the .po file using indented style.
-<DT><SAMP>`--no-location´</SAMP>
+<DT><SAMP>‘--no-location’</SAMP>
<DD>
-<A NAME="IDX689"></A>
-Do not write <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines.
+<A NAME="IDX706"></A>
+Do not write <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines.
-<DT><SAMP>`-n´</SAMP>
+<DT><SAMP>‘-n’</SAMP>
<DD>
-<DT><SAMP>`--add-location´</SAMP>
+<DT><SAMP>‘--add-location’</SAMP>
<DD>
-<A NAME="IDX690"></A>
-<A NAME="IDX691"></A>
-Generate <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines (default).
+<A NAME="IDX707"></A>
+<A NAME="IDX708"></A>
+Generate <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines (default).
-<DT><SAMP>`--strict´</SAMP>
+<DT><SAMP>‘--strict’</SAMP>
<DD>
-<A NAME="IDX692"></A>
+<A NAME="IDX709"></A>
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
-<DT><SAMP>`-p´</SAMP>
+<DT><SAMP>‘-p’</SAMP>
<DD>
-<DT><SAMP>`--properties-output´</SAMP>
+<DT><SAMP>‘--properties-output’</SAMP>
<DD>
-<A NAME="IDX693"></A>
-<A NAME="IDX694"></A>
+<A NAME="IDX710"></A>
+<A NAME="IDX711"></A>
Write out a Java ResourceBundle in Java <CODE>.properties</CODE> syntax. Note
that this file format doesn't support plural forms and silently drops
obsolete messages.
-<DT><SAMP>`--stringtable-output´</SAMP>
+<DT><SAMP>‘--stringtable-output’</SAMP>
<DD>
-<A NAME="IDX695"></A>
+<A NAME="IDX712"></A>
Write out a NeXTstep/GNUstep localized resource file in <CODE>.strings</CODE> syntax.
Note that this file format doesn't support plural forms.
-<DT><SAMP>`-w <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-w <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--width=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--width=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX696"></A>
-<A NAME="IDX697"></A>
+<A NAME="IDX713"></A>
+<A NAME="IDX714"></A>
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 <VAR>number</VAR>.
-<DT><SAMP>`--no-wrap´</SAMP>
+<DT><SAMP>‘--no-wrap’</SAMP>
<DD>
-<A NAME="IDX698"></A>
+<A NAME="IDX715"></A>
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.
-<DT><SAMP>`-s´</SAMP>
+<DT><SAMP>‘-s’</SAMP>
<DD>
-<DT><SAMP>`--sort-output´</SAMP>
+<DT><SAMP>‘--sort-output’</SAMP>
<DD>
-<A NAME="IDX699"></A>
-<A NAME="IDX700"></A>
+<A NAME="IDX716"></A>
+<A NAME="IDX717"></A>
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
-<DT><SAMP>`-F´</SAMP>
+<DT><SAMP>‘-F’</SAMP>
<DD>
-<DT><SAMP>`--sort-by-file´</SAMP>
+<DT><SAMP>‘--sort-by-file’</SAMP>
<DD>
-<A NAME="IDX701"></A>
-<A NAME="IDX702"></A>
+<A NAME="IDX718"></A>
+<A NAME="IDX719"></A>
Sort output by file location.
</DL>
-<H3><A NAME="SEC108" HREF="gettext_toc.html#TOC108">9.5.6 Informative output</A></H3>
+<H3><A NAME="SEC110" HREF="gettext_toc.html#TOC110">9.5.6 Informative output</A></H3>
<DL COMPACT>
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX703"></A>
-<A NAME="IDX704"></A>
+<A NAME="IDX720"></A>
+<A NAME="IDX721"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX705"></A>
-<A NAME="IDX706"></A>
+<A NAME="IDX722"></A>
+<A NAME="IDX723"></A>
Output version information and exit.
</DL>
-<H2><A NAME="SEC109" HREF="gettext_toc.html#TOC109">9.6 Invoking the <CODE>msgcomm</CODE> Program</A></H2>
+<H2><A NAME="SEC111" HREF="gettext_toc.html#TOC111">9.6 Invoking the <CODE>msgcomm</CODE> Program</A></H2>
<P>
-<A NAME="IDX707"></A>
-<A NAME="IDX708"></A>
+<A NAME="IDX724"></A>
+<A NAME="IDX725"></A>
<PRE>
msgcomm [<VAR>option</VAR>] [<VAR>inputfile</VAR>]...
</PRE>
<P>
-<A NAME="IDX709"></A>
+<A NAME="IDX726"></A>
The <CODE>msgcomm</CODE> program finds messages which are common to two or more
of the specified PO files.
By using the <CODE>--more-than</CODE> option, greater commonality may be requested
before messages are printed. Conversely, the <CODE>--less-than</CODE> option may be
used to specify less commonality before messages are printed (i.e.
-<SAMP>`--less-than=2´</SAMP> will only print the unique messages). Translations,
+<SAMP>‘--less-than=2’</SAMP> will only print the unique messages). Translations,
comments and extract comments will be preserved, but only from the first
PO file to define them. File positions from all PO files will be
cumulated.
</P>
-<H3><A NAME="SEC110" HREF="gettext_toc.html#TOC110">9.6.1 Input file location</A></H3>
+<H3><A NAME="SEC112" HREF="gettext_toc.html#TOC112">9.6.1 Input file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`<VAR>inputfile</VAR> ...´</SAMP>
+<DT><SAMP>‘<VAR>inputfile</VAR> ...’</SAMP>
<DD>
Input files.
-<DT><SAMP>`-f <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-f <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--files-from=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--files-from=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX710"></A>
-<A NAME="IDX711"></A>
+<A NAME="IDX727"></A>
+<A NAME="IDX728"></A>
Read the names of the input files from <VAR>file</VAR> instead of getting
them from the command line.
-<DT><SAMP>`-D <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-D <VAR>directory</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--directory=<VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘--directory=<VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX712"></A>
-<A NAME="IDX713"></A>
+<A NAME="IDX729"></A>
+<A NAME="IDX730"></A>
Add <VAR>directory</VAR> to the list of directories. Source files are
-searched relative to this list of directories. The resulting <TT>`.po´</TT>
+searched relative to this list of directories. The resulting <TT>‘.po’</TT>
file will be written relative to the current directory, though.
</DL>
<P>
-If <VAR>inputfile</VAR> is <SAMP>`-´</SAMP>, standard input is read.
+If <VAR>inputfile</VAR> is <SAMP>‘-’</SAMP>, standard input is read.
</P>
-<H3><A NAME="SEC111" HREF="gettext_toc.html#TOC111">9.6.2 Output file location</A></H3>
+<H3><A NAME="SEC113" HREF="gettext_toc.html#TOC113">9.6.2 Output file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`-o <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-o <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--output-file=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--output-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX714"></A>
-<A NAME="IDX715"></A>
+<A NAME="IDX731"></A>
+<A NAME="IDX732"></A>
Write output to specified file.
</DL>
<P>
The results are written to standard output if no output file is specified
-or if it is <SAMP>`-´</SAMP>.
+or if it is <SAMP>‘-’</SAMP>.
</P>
-<H3><A NAME="SEC112" HREF="gettext_toc.html#TOC112">9.6.3 Message selection</A></H3>
+<H3><A NAME="SEC114" HREF="gettext_toc.html#TOC114">9.6.3 Message selection</A></H3>
<DL COMPACT>
-<DT><SAMP>`-< <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-< <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--less-than=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--less-than=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX716"></A>
-<A NAME="IDX717"></A>
+<A NAME="IDX733"></A>
+<A NAME="IDX734"></A>
Print messages with less than <VAR>number</VAR> definitions, defaults to infinite
if not set.
-<DT><SAMP>`-> <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-> <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--more-than=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--more-than=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX718"></A>
-<A NAME="IDX719"></A>
+<A NAME="IDX735"></A>
+<A NAME="IDX736"></A>
Print messages with more than <VAR>number</VAR> definitions, defaults to 1 if not
set.
-<DT><SAMP>`-u´</SAMP>
+<DT><SAMP>‘-u’</SAMP>
<DD>
-<DT><SAMP>`--unique´</SAMP>
+<DT><SAMP>‘--unique’</SAMP>
<DD>
-<A NAME="IDX720"></A>
-<A NAME="IDX721"></A>
-Shorthand for <SAMP>`--less-than=2´</SAMP>. Requests that only unique messages be
+<A NAME="IDX737"></A>
+<A NAME="IDX738"></A>
+Shorthand for <SAMP>‘--less-than=2’</SAMP>. Requests that only unique messages be
printed.
</DL>
-<H3><A NAME="SEC113" HREF="gettext_toc.html#TOC113">9.6.4 Input file syntax</A></H3>
+<H3><A NAME="SEC115" HREF="gettext_toc.html#TOC115">9.6.4 Input file syntax</A></H3>
<DL COMPACT>
-<DT><SAMP>`-P´</SAMP>
+<DT><SAMP>‘-P’</SAMP>
<DD>
-<DT><SAMP>`--properties-input´</SAMP>
+<DT><SAMP>‘--properties-input’</SAMP>
<DD>
-<A NAME="IDX722"></A>
-<A NAME="IDX723"></A>
+<A NAME="IDX739"></A>
+<A NAME="IDX740"></A>
Assume the input files are Java ResourceBundles in Java <CODE>.properties</CODE>
syntax, not in PO file syntax.
-<DT><SAMP>`--stringtable-input´</SAMP>
+<DT><SAMP>‘--stringtable-input’</SAMP>
<DD>
-<A NAME="IDX724"></A>
+<A NAME="IDX741"></A>
Assume the input files are NeXTstep/GNUstep localized resource files in
<CODE>.strings</CODE> syntax, not in PO file syntax.
-<H3><A NAME="SEC114" HREF="gettext_toc.html#TOC114">9.6.5 Output details</A></H3>
+<H3><A NAME="SEC116" HREF="gettext_toc.html#TOC116">9.6.5 Output details</A></H3>
<DL COMPACT>
-<DT><SAMP>`--force-po´</SAMP>
+<DT><SAMP>‘--force-po’</SAMP>
<DD>
-<A NAME="IDX725"></A>
+<A NAME="IDX742"></A>
Always write an output file even if it contains no message.
-<DT><SAMP>`-i´</SAMP>
+<DT><SAMP>‘-i’</SAMP>
<DD>
-<DT><SAMP>`--indent´</SAMP>
+<DT><SAMP>‘--indent’</SAMP>
<DD>
-<A NAME="IDX726"></A>
-<A NAME="IDX727"></A>
+<A NAME="IDX743"></A>
+<A NAME="IDX744"></A>
Write the .po file using indented style.
-<DT><SAMP>`--no-location´</SAMP>
+<DT><SAMP>‘--no-location’</SAMP>
<DD>
-<A NAME="IDX728"></A>
-Do not write <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines.
+<A NAME="IDX745"></A>
+Do not write <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines.
-<DT><SAMP>`-n´</SAMP>
+<DT><SAMP>‘-n’</SAMP>
<DD>
-<DT><SAMP>`--add-location´</SAMP>
+<DT><SAMP>‘--add-location’</SAMP>
<DD>
-<A NAME="IDX729"></A>
-<A NAME="IDX730"></A>
-Generate <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines (default).
+<A NAME="IDX746"></A>
+<A NAME="IDX747"></A>
+Generate <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines (default).
-<DT><SAMP>`--strict´</SAMP>
+<DT><SAMP>‘--strict’</SAMP>
<DD>
-<A NAME="IDX731"></A>
+<A NAME="IDX748"></A>
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
-<DT><SAMP>`-p´</SAMP>
+<DT><SAMP>‘-p’</SAMP>
<DD>
-<DT><SAMP>`--properties-output´</SAMP>
+<DT><SAMP>‘--properties-output’</SAMP>
<DD>
-<A NAME="IDX732"></A>
-<A NAME="IDX733"></A>
+<A NAME="IDX749"></A>
+<A NAME="IDX750"></A>
Write out a Java ResourceBundle in Java <CODE>.properties</CODE> syntax. Note
that this file format doesn't support plural forms and silently drops
obsolete messages.
-<DT><SAMP>`--stringtable-output´</SAMP>
+<DT><SAMP>‘--stringtable-output’</SAMP>
<DD>
-<A NAME="IDX734"></A>
+<A NAME="IDX751"></A>
Write out a NeXTstep/GNUstep localized resource file in <CODE>.strings</CODE> syntax.
Note that this file format doesn't support plural forms.
-<DT><SAMP>`-w <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-w <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--width=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--width=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX735"></A>
-<A NAME="IDX736"></A>
+<A NAME="IDX752"></A>
+<A NAME="IDX753"></A>
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 <VAR>number</VAR>.
-<DT><SAMP>`--no-wrap´</SAMP>
+<DT><SAMP>‘--no-wrap’</SAMP>
<DD>
-<A NAME="IDX737"></A>
+<A NAME="IDX754"></A>
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.
-<DT><SAMP>`-s´</SAMP>
+<DT><SAMP>‘-s’</SAMP>
<DD>
-<DT><SAMP>`--sort-output´</SAMP>
+<DT><SAMP>‘--sort-output’</SAMP>
<DD>
-<A NAME="IDX738"></A>
-<A NAME="IDX739"></A>
+<A NAME="IDX755"></A>
+<A NAME="IDX756"></A>
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
-<DT><SAMP>`-F´</SAMP>
+<DT><SAMP>‘-F’</SAMP>
<DD>
-<DT><SAMP>`--sort-by-file´</SAMP>
+<DT><SAMP>‘--sort-by-file’</SAMP>
<DD>
-<A NAME="IDX740"></A>
-<A NAME="IDX741"></A>
+<A NAME="IDX757"></A>
+<A NAME="IDX758"></A>
Sort output by file location.
-<DT><SAMP>`--omit-header´</SAMP>
+<DT><SAMP>‘--omit-header’</SAMP>
<DD>
-<A NAME="IDX742"></A>
-Don't write header with <SAMP>`msgid ""´</SAMP> entry.
+<A NAME="IDX759"></A>
+Don't write header with <SAMP>‘msgid ""’</SAMP> entry.
</DL>
-<H3><A NAME="SEC115" HREF="gettext_toc.html#TOC115">9.6.6 Informative output</A></H3>
+<H3><A NAME="SEC117" HREF="gettext_toc.html#TOC117">9.6.6 Informative output</A></H3>
<DL COMPACT>
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX743"></A>
-<A NAME="IDX744"></A>
+<A NAME="IDX760"></A>
+<A NAME="IDX761"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX745"></A>
-<A NAME="IDX746"></A>
+<A NAME="IDX762"></A>
+<A NAME="IDX763"></A>
Output version information and exit.
</DL>
-<H2><A NAME="SEC116" HREF="gettext_toc.html#TOC116">9.7 Invoking the <CODE>msgcmp</CODE> Program</A></H2>
+<H2><A NAME="SEC118" HREF="gettext_toc.html#TOC118">9.7 Invoking the <CODE>msgcmp</CODE> Program</A></H2>
<P>
-<A NAME="IDX747"></A>
-<A NAME="IDX748"></A>
+<A NAME="IDX764"></A>
+<A NAME="IDX765"></A>
<PRE>
msgcmp [<VAR>option</VAR>] <VAR>def</VAR>.po <VAR>ref</VAR>.pot
</PRE>
<P>
-<A NAME="IDX749"></A>
+<A NAME="IDX766"></A>
The <CODE>msgcmp</CODE> program compares two Uniforum style .po files to check that
both contain the same set of msgid strings. The <VAR>def</VAR>.po file is an
existing PO file with the translations. The <VAR>ref</VAR>.pot file is the last
</P>
-<H3><A NAME="SEC117" HREF="gettext_toc.html#TOC117">9.7.1 Input file location</A></H3>
+<H3><A NAME="SEC119" HREF="gettext_toc.html#TOC119">9.7.1 Input file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`<VAR>def</VAR>.po´</SAMP>
+<DT><SAMP>‘<VAR>def</VAR>.po’</SAMP>
<DD>
Translations.
-<DT><SAMP>`<VAR>ref</VAR>.pot´</SAMP>
+<DT><SAMP>‘<VAR>ref</VAR>.pot’</SAMP>
<DD>
References to the sources.
-<DT><SAMP>`-D <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-D <VAR>directory</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--directory=<VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘--directory=<VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX750"></A>
-<A NAME="IDX751"></A>
+<A NAME="IDX767"></A>
+<A NAME="IDX768"></A>
Add <VAR>directory</VAR> to the list of directories. Source files are
searched relative to this list of directories.
-<H3><A NAME="SEC118" HREF="gettext_toc.html#TOC118">9.7.2 Operation modifiers</A></H3>
+<H3><A NAME="SEC120" HREF="gettext_toc.html#TOC120">9.7.2 Operation modifiers</A></H3>
<DL COMPACT>
-<DT><SAMP>`-m´</SAMP>
+<DT><SAMP>‘-m’</SAMP>
<DD>
-<DT><SAMP>`--multi-domain´</SAMP>
+<DT><SAMP>‘--multi-domain’</SAMP>
<DD>
-<A NAME="IDX752"></A>
-<A NAME="IDX753"></A>
+<A NAME="IDX769"></A>
+<A NAME="IDX770"></A>
Apply <VAR>ref</VAR>.pot to each of the domains in <VAR>def</VAR>.po.
</DL>
-<H3><A NAME="SEC119" HREF="gettext_toc.html#TOC119">9.7.3 Input file syntax</A></H3>
+<H3><A NAME="SEC121" HREF="gettext_toc.html#TOC121">9.7.3 Input file syntax</A></H3>
<DL COMPACT>
-<DT><SAMP>`-P´</SAMP>
+<DT><SAMP>‘-P’</SAMP>
<DD>
-<DT><SAMP>`--properties-input´</SAMP>
+<DT><SAMP>‘--properties-input’</SAMP>
<DD>
-<A NAME="IDX754"></A>
-<A NAME="IDX755"></A>
+<A NAME="IDX771"></A>
+<A NAME="IDX772"></A>
Assume the input files are Java ResourceBundles in Java <CODE>.properties</CODE>
syntax, not in PO file syntax.
-<DT><SAMP>`--stringtable-input´</SAMP>
+<DT><SAMP>‘--stringtable-input’</SAMP>
<DD>
-<A NAME="IDX756"></A>
+<A NAME="IDX773"></A>
Assume the input files are NeXTstep/GNUstep localized resource files in
<CODE>.strings</CODE> syntax, not in PO file syntax.
-<H3><A NAME="SEC120" HREF="gettext_toc.html#TOC120">9.7.4 Informative output</A></H3>
+<H3><A NAME="SEC122" HREF="gettext_toc.html#TOC122">9.7.4 Informative output</A></H3>
<DL COMPACT>
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX757"></A>
-<A NAME="IDX758"></A>
+<A NAME="IDX774"></A>
+<A NAME="IDX775"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX759"></A>
-<A NAME="IDX760"></A>
+<A NAME="IDX776"></A>
+<A NAME="IDX777"></A>
Output version information and exit.
</DL>
-<H2><A NAME="SEC121" HREF="gettext_toc.html#TOC121">9.8 Invoking the <CODE>msgattrib</CODE> Program</A></H2>
+<H2><A NAME="SEC123" HREF="gettext_toc.html#TOC123">9.8 Invoking the <CODE>msgattrib</CODE> Program</A></H2>
<P>
-<A NAME="IDX761"></A>
-<A NAME="IDX762"></A>
+<A NAME="IDX778"></A>
+<A NAME="IDX779"></A>
<PRE>
msgattrib [<VAR>option</VAR>] [<VAR>inputfile</VAR>]
</PRE>
<P>
-<A NAME="IDX763"></A>
-<A NAME="IDX764"></A>
+<A NAME="IDX780"></A>
+<A NAME="IDX781"></A>
The <CODE>msgattrib</CODE> program filters the messages of a translation catalog
according to their attributes, and manipulates the attributes.
</P>
-<H3><A NAME="SEC122" HREF="gettext_toc.html#TOC122">9.8.1 Input file location</A></H3>
+<H3><A NAME="SEC124" HREF="gettext_toc.html#TOC124">9.8.1 Input file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`<VAR>inputfile</VAR>´</SAMP>
+<DT><SAMP>‘<VAR>inputfile</VAR>’</SAMP>
<DD>
Input PO file.
-<DT><SAMP>`-D <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-D <VAR>directory</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--directory=<VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘--directory=<VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX765"></A>
-<A NAME="IDX766"></A>
+<A NAME="IDX782"></A>
+<A NAME="IDX783"></A>
Add <VAR>directory</VAR> to the list of directories. Source files are
-searched relative to this list of directories. The resulting <TT>`.po´</TT>
+searched relative to this list of directories. The resulting <TT>‘.po’</TT>
file will be written relative to the current directory, though.
</DL>
<P>
-If no <VAR>inputfile</VAR> is given or if it is <SAMP>`-´</SAMP>, standard input is read.
+If no <VAR>inputfile</VAR> is given or if it is <SAMP>‘-’</SAMP>, standard input is read.
</P>
-<H3><A NAME="SEC123" HREF="gettext_toc.html#TOC123">9.8.2 Output file location</A></H3>
+<H3><A NAME="SEC125" HREF="gettext_toc.html#TOC125">9.8.2 Output file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`-o <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-o <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--output-file=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--output-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX767"></A>
-<A NAME="IDX768"></A>
+<A NAME="IDX784"></A>
+<A NAME="IDX785"></A>
Write output to specified file.
</DL>
<P>
The results are written to standard output if no output file is specified
-or if it is <SAMP>`-´</SAMP>.
+or if it is <SAMP>‘-’</SAMP>.
</P>
-<H3><A NAME="SEC124" HREF="gettext_toc.html#TOC124">9.8.3 Message selection</A></H3>
+<H3><A NAME="SEC126" HREF="gettext_toc.html#TOC126">9.8.3 Message selection</A></H3>
<DL COMPACT>
-<DT><SAMP>`--translated´</SAMP>
+<DT><SAMP>‘--translated’</SAMP>
<DD>
-<A NAME="IDX769"></A>
+<A NAME="IDX786"></A>
Keep translated messages, remove untranslated messages.
-<DT><SAMP>`--untranslated´</SAMP>
+<DT><SAMP>‘--untranslated’</SAMP>
<DD>
-<A NAME="IDX770"></A>
+<A NAME="IDX787"></A>
Keep untranslated messages, remove translated messages.
-<DT><SAMP>`--no-fuzzy´</SAMP>
+<DT><SAMP>‘--no-fuzzy’</SAMP>
<DD>
-<A NAME="IDX771"></A>
-Remove `fuzzy' marked messages.
+<A NAME="IDX788"></A>
+Remove
+‘fuzzy’
+marked messages.
-<DT><SAMP>`--only-fuzzy´</SAMP>
+<DT><SAMP>‘--only-fuzzy’</SAMP>
<DD>
-<A NAME="IDX772"></A>
-Keep `fuzzy' marked messages, remove all other messsages.
+<A NAME="IDX789"></A>
+Keep
+‘fuzzy’
+marked messages, remove all other messsages.
-<DT><SAMP>`--no-obsolete´</SAMP>
+<DT><SAMP>‘--no-obsolete’</SAMP>
<DD>
-<A NAME="IDX773"></A>
+<A NAME="IDX790"></A>
Remove obsolete #~ messages.
-<DT><SAMP>`--only-obsolete´</SAMP>
+<DT><SAMP>‘--only-obsolete’</SAMP>
<DD>
-<A NAME="IDX774"></A>
+<A NAME="IDX791"></A>
Keep obsolete #~ messages, remove all other messages.
</DL>
-<H3><A NAME="SEC125" HREF="gettext_toc.html#TOC125">9.8.4 Attribute manipulation</A></H3>
+<H3><A NAME="SEC127" HREF="gettext_toc.html#TOC127">9.8.4 Attribute manipulation</A></H3>
<P>
-<A NAME="IDX775"></A>
+<A NAME="IDX792"></A>
Attributes are modified after the message selection/removal has been
-performed. If the <SAMP>`--only-file´</SAMP> or <SAMP>`--ignore-file´</SAMP> option is
+performed. If the <SAMP>‘--only-file’</SAMP> or <SAMP>‘--ignore-file’</SAMP> option is
specified, the attribute modification is applied only to those messages
that are listed in the <VAR>only-file</VAR> and not listed in the
<VAR>ignore-file</VAR>.
</P>
<DL COMPACT>
-<DT><SAMP>`--set-fuzzy´</SAMP>
+<DT><SAMP>‘--set-fuzzy’</SAMP>
<DD>
-<A NAME="IDX776"></A>
-Set all messages `fuzzy'.
+<A NAME="IDX793"></A>
+Set all messages
+‘fuzzy’.
-<DT><SAMP>`--clear-fuzzy´</SAMP>
+<DT><SAMP>‘--clear-fuzzy’</SAMP>
<DD>
-<A NAME="IDX777"></A>
-Set all messages non-`fuzzy'.
+<A NAME="IDX794"></A>
+Set all messages
+non-‘fuzzy’.
-<DT><SAMP>`--set-obsolete´</SAMP>
+<DT><SAMP>‘--set-obsolete’</SAMP>
<DD>
-<A NAME="IDX778"></A>
+<A NAME="IDX795"></A>
Set all messages obsolete.
-<DT><SAMP>`--clear-obsolete´</SAMP>
+<DT><SAMP>‘--clear-obsolete’</SAMP>
<DD>
-<A NAME="IDX779"></A>
+<A NAME="IDX796"></A>
Set all messages non-obsolete.
-<DT><SAMP>`--only-file=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--only-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX780"></A>
+<A NAME="IDX797"></A>
Limit the attribute changes to entries that are listed in <VAR>file</VAR>.
<VAR>file</VAR> should be a PO or POT file.
-<DT><SAMP>`--ignore-file=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--ignore-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX781"></A>
+<A NAME="IDX798"></A>
Limit the attribute changes to entries that are not listed in <VAR>file</VAR>.
<VAR>file</VAR> should be a PO or POT file.
-<DT><SAMP>`--fuzzy´</SAMP>
+<DT><SAMP>‘--fuzzy’</SAMP>
<DD>
-<A NAME="IDX782"></A>
-Synonym for <SAMP>`--only-fuzzy --clear-fuzzy´</SAMP>: It keeps only the fuzzy
-messages and removes their `fuzzy' mark.
+<A NAME="IDX799"></A>
+Synonym for <SAMP>‘--only-fuzzy --clear-fuzzy’</SAMP>: It keeps only the fuzzy
+messages and removes their
+‘fuzzy’
+mark.
-<DT><SAMP>`--obsolete´</SAMP>
+<DT><SAMP>‘--obsolete’</SAMP>
<DD>
-<A NAME="IDX783"></A>
-Synonym for <SAMP>`--only-obsolete --clear-obsolete´</SAMP>: It keeps only the
+<A NAME="IDX800"></A>
+Synonym for <SAMP>‘--only-obsolete --clear-obsolete’</SAMP>: It keeps only the
obsolete messages and makes them non-obsolete.
</DL>
-<H3><A NAME="SEC126" HREF="gettext_toc.html#TOC126">9.8.5 Input file syntax</A></H3>
+<H3><A NAME="SEC128" HREF="gettext_toc.html#TOC128">9.8.5 Input file syntax</A></H3>
<DL COMPACT>
-<DT><SAMP>`-P´</SAMP>
+<DT><SAMP>‘-P’</SAMP>
<DD>
-<DT><SAMP>`--properties-input´</SAMP>
+<DT><SAMP>‘--properties-input’</SAMP>
<DD>
-<A NAME="IDX784"></A>
-<A NAME="IDX785"></A>
+<A NAME="IDX801"></A>
+<A NAME="IDX802"></A>
Assume the input file is a Java ResourceBundle in Java <CODE>.properties</CODE>
syntax, not in PO file syntax.
-<DT><SAMP>`--stringtable-input´</SAMP>
+<DT><SAMP>‘--stringtable-input’</SAMP>
<DD>
-<A NAME="IDX786"></A>
+<A NAME="IDX803"></A>
Assume the input file is a NeXTstep/GNUstep localized resource file in
<CODE>.strings</CODE> syntax, not in PO file syntax.
-<H3><A NAME="SEC127" HREF="gettext_toc.html#TOC127">9.8.6 Output details</A></H3>
+<H3><A NAME="SEC129" HREF="gettext_toc.html#TOC129">9.8.6 Output details</A></H3>
<DL COMPACT>
-<DT><SAMP>`--force-po´</SAMP>
+<DT><SAMP>‘--force-po’</SAMP>
<DD>
-<A NAME="IDX787"></A>
+<A NAME="IDX804"></A>
Always write an output file even if it contains no message.
-<DT><SAMP>`-i´</SAMP>
+<DT><SAMP>‘-i’</SAMP>
<DD>
-<DT><SAMP>`--indent´</SAMP>
+<DT><SAMP>‘--indent’</SAMP>
<DD>
-<A NAME="IDX788"></A>
-<A NAME="IDX789"></A>
+<A NAME="IDX805"></A>
+<A NAME="IDX806"></A>
Write the .po file using indented style.
-<DT><SAMP>`--no-location´</SAMP>
+<DT><SAMP>‘--no-location’</SAMP>
<DD>
-<A NAME="IDX790"></A>
-Do not write <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines.
+<A NAME="IDX807"></A>
+Do not write <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines.
-<DT><SAMP>`-n´</SAMP>
+<DT><SAMP>‘-n’</SAMP>
<DD>
-<DT><SAMP>`--add-location´</SAMP>
+<DT><SAMP>‘--add-location’</SAMP>
<DD>
-<A NAME="IDX791"></A>
-<A NAME="IDX792"></A>
-Generate <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines (default).
+<A NAME="IDX808"></A>
+<A NAME="IDX809"></A>
+Generate <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines (default).
-<DT><SAMP>`--strict´</SAMP>
+<DT><SAMP>‘--strict’</SAMP>
<DD>
-<A NAME="IDX793"></A>
+<A NAME="IDX810"></A>
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
-<DT><SAMP>`-p´</SAMP>
+<DT><SAMP>‘-p’</SAMP>
<DD>
-<DT><SAMP>`--properties-output´</SAMP>
+<DT><SAMP>‘--properties-output’</SAMP>
<DD>
-<A NAME="IDX794"></A>
-<A NAME="IDX795"></A>
+<A NAME="IDX811"></A>
+<A NAME="IDX812"></A>
Write out a Java ResourceBundle in Java <CODE>.properties</CODE> syntax. Note
that this file format doesn't support plural forms and silently drops
obsolete messages.
-<DT><SAMP>`--stringtable-output´</SAMP>
+<DT><SAMP>‘--stringtable-output’</SAMP>
<DD>
-<A NAME="IDX796"></A>
+<A NAME="IDX813"></A>
Write out a NeXTstep/GNUstep localized resource file in <CODE>.strings</CODE> syntax.
Note that this file format doesn't support plural forms.
-<DT><SAMP>`-w <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-w <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--width=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--width=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX797"></A>
-<A NAME="IDX798"></A>
+<A NAME="IDX814"></A>
+<A NAME="IDX815"></A>
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 <VAR>number</VAR>.
-<DT><SAMP>`--no-wrap´</SAMP>
+<DT><SAMP>‘--no-wrap’</SAMP>
<DD>
-<A NAME="IDX799"></A>
+<A NAME="IDX816"></A>
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.
-<DT><SAMP>`-s´</SAMP>
+<DT><SAMP>‘-s’</SAMP>
<DD>
-<DT><SAMP>`--sort-output´</SAMP>
+<DT><SAMP>‘--sort-output’</SAMP>
<DD>
-<A NAME="IDX800"></A>
-<A NAME="IDX801"></A>
+<A NAME="IDX817"></A>
+<A NAME="IDX818"></A>
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
-<DT><SAMP>`-F´</SAMP>
+<DT><SAMP>‘-F’</SAMP>
<DD>
-<DT><SAMP>`--sort-by-file´</SAMP>
+<DT><SAMP>‘--sort-by-file’</SAMP>
<DD>
-<A NAME="IDX802"></A>
-<A NAME="IDX803"></A>
+<A NAME="IDX819"></A>
+<A NAME="IDX820"></A>
Sort output by file location.
</DL>
-<H3><A NAME="SEC128" HREF="gettext_toc.html#TOC128">9.8.7 Informative output</A></H3>
+<H3><A NAME="SEC130" HREF="gettext_toc.html#TOC130">9.8.7 Informative output</A></H3>
<DL COMPACT>
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX804"></A>
-<A NAME="IDX805"></A>
+<A NAME="IDX821"></A>
+<A NAME="IDX822"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX806"></A>
-<A NAME="IDX807"></A>
+<A NAME="IDX823"></A>
+<A NAME="IDX824"></A>
Output version information and exit.
</DL>
-<H2><A NAME="SEC129" HREF="gettext_toc.html#TOC129">9.9 Invoking the <CODE>msgen</CODE> Program</A></H2>
+<H2><A NAME="SEC131" HREF="gettext_toc.html#TOC131">9.9 Invoking the <CODE>msgen</CODE> Program</A></H2>
<P>
-<A NAME="IDX808"></A>
-<A NAME="IDX809"></A>
+<A NAME="IDX825"></A>
+<A NAME="IDX826"></A>
<PRE>
msgen [<VAR>option</VAR>] <VAR>inputfile</VAR>
</PRE>
<P>
-<A NAME="IDX810"></A>
+<A NAME="IDX827"></A>
The <CODE>msgen</CODE> 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
</P>
<P>
-Note: <SAMP>`msginit --no-translator --locale=en´</SAMP> performs a very similar
+Note: <SAMP>‘msginit --no-translator --locale=en’</SAMP> performs a very similar
task. The main difference is that <CODE>msginit</CODE> cares specially about
the header entry, whereas <CODE>msgen</CODE> doesn't.
</P>
-<H3><A NAME="SEC130" HREF="gettext_toc.html#TOC130">9.9.1 Input file location</A></H3>
+<H3><A NAME="SEC132" HREF="gettext_toc.html#TOC132">9.9.1 Input file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`<VAR>inputfile</VAR>´</SAMP>
+<DT><SAMP>‘<VAR>inputfile</VAR>’</SAMP>
<DD>
Input PO or POT file.
-<DT><SAMP>`-D <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-D <VAR>directory</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--directory=<VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘--directory=<VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX811"></A>
-<A NAME="IDX812"></A>
+<A NAME="IDX828"></A>
+<A NAME="IDX829"></A>
Add <VAR>directory</VAR> to the list of directories. Source files are
-searched relative to this list of directories. The resulting <TT>`.po´</TT>
+searched relative to this list of directories. The resulting <TT>‘.po’</TT>
file will be written relative to the current directory, though.
</DL>
<P>
-If <VAR>inputfile</VAR> is <SAMP>`-´</SAMP>, standard input is read.
+If <VAR>inputfile</VAR> is <SAMP>‘-’</SAMP>, standard input is read.
</P>
-<H3><A NAME="SEC131" HREF="gettext_toc.html#TOC131">9.9.2 Output file location</A></H3>
+<H3><A NAME="SEC133" HREF="gettext_toc.html#TOC133">9.9.2 Output file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`-o <VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘-o <VAR>file</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--output-file=<VAR>file</VAR>´</SAMP>
+<DT><SAMP>‘--output-file=<VAR>file</VAR>’</SAMP>
<DD>
-<A NAME="IDX813"></A>
-<A NAME="IDX814"></A>
+<A NAME="IDX830"></A>
+<A NAME="IDX831"></A>
Write output to specified file.
</DL>
<P>
The results are written to standard output if no output file is specified
-or if it is <SAMP>`-´</SAMP>.
+or if it is <SAMP>‘-’</SAMP>.
</P>
-<H3><A NAME="SEC132" HREF="gettext_toc.html#TOC132">9.9.3 Input file syntax</A></H3>
+<H3><A NAME="SEC134" HREF="gettext_toc.html#TOC134">9.9.3 Input file syntax</A></H3>
<DL COMPACT>
-<DT><SAMP>`-P´</SAMP>
+<DT><SAMP>‘-P’</SAMP>
<DD>
-<DT><SAMP>`--properties-input´</SAMP>
+<DT><SAMP>‘--properties-input’</SAMP>
<DD>
-<A NAME="IDX815"></A>
-<A NAME="IDX816"></A>
+<A NAME="IDX832"></A>
+<A NAME="IDX833"></A>
Assume the input file is a Java ResourceBundle in Java <CODE>.properties</CODE>
syntax, not in PO file syntax.
-<DT><SAMP>`--stringtable-input´</SAMP>
+<DT><SAMP>‘--stringtable-input’</SAMP>
<DD>
-<A NAME="IDX817"></A>
+<A NAME="IDX834"></A>
Assume the input file is a NeXTstep/GNUstep localized resource file in
<CODE>.strings</CODE> syntax, not in PO file syntax.
-<H3><A NAME="SEC133" HREF="gettext_toc.html#TOC133">9.9.4 Output details</A></H3>
+<H3><A NAME="SEC135" HREF="gettext_toc.html#TOC135">9.9.4 Output details</A></H3>
<DL COMPACT>
-<DT><SAMP>`--force-po´</SAMP>
+<DT><SAMP>‘--force-po’</SAMP>
<DD>
-<A NAME="IDX818"></A>
+<A NAME="IDX835"></A>
Always write an output file even if it contains no message.
-<DT><SAMP>`-i´</SAMP>
+<DT><SAMP>‘-i’</SAMP>
<DD>
-<DT><SAMP>`--indent´</SAMP>
+<DT><SAMP>‘--indent’</SAMP>
<DD>
-<A NAME="IDX819"></A>
-<A NAME="IDX820"></A>
+<A NAME="IDX836"></A>
+<A NAME="IDX837"></A>
Write the .po file using indented style.
-<DT><SAMP>`--no-location´</SAMP>
+<DT><SAMP>‘--no-location’</SAMP>
<DD>
-<A NAME="IDX821"></A>
-Do not write <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines.
+<A NAME="IDX838"></A>
+Do not write <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines.
-<DT><SAMP>`--add-location´</SAMP>
+<DT><SAMP>‘--add-location’</SAMP>
<DD>
-<A NAME="IDX822"></A>
-Generate <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>´</SAMP> lines (default).
+<A NAME="IDX839"></A>
+Generate <SAMP>‘#: <VAR>filename</VAR>:<VAR>line</VAR>’</SAMP> lines (default).
-<DT><SAMP>`--strict´</SAMP>
+<DT><SAMP>‘--strict’</SAMP>
<DD>
-<A NAME="IDX823"></A>
+<A NAME="IDX840"></A>
Write out a strict Uniforum conforming PO file. Note that this
Uniforum format should be avoided because it doesn't support the
GNU extensions.
-<DT><SAMP>`-p´</SAMP>
+<DT><SAMP>‘-p’</SAMP>
<DD>
-<DT><SAMP>`--properties-output´</SAMP>
+<DT><SAMP>‘--properties-output’</SAMP>
<DD>
-<A NAME="IDX824"></A>
-<A NAME="IDX825"></A>
+<A NAME="IDX841"></A>
+<A NAME="IDX842"></A>
Write out a Java ResourceBundle in Java <CODE>.properties</CODE> syntax. Note
that this file format doesn't support plural forms and silently drops
obsolete messages.
-<DT><SAMP>`--stringtable-output´</SAMP>
+<DT><SAMP>‘--stringtable-output’</SAMP>
<DD>
-<A NAME="IDX826"></A>
+<A NAME="IDX843"></A>
Write out a NeXTstep/GNUstep localized resource file in <CODE>.strings</CODE> syntax.
Note that this file format doesn't support plural forms.
-<DT><SAMP>`-w <VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘-w <VAR>number</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--width=<VAR>number</VAR>´</SAMP>
+<DT><SAMP>‘--width=<VAR>number</VAR>’</SAMP>
<DD>
-<A NAME="IDX827"></A>
-<A NAME="IDX828"></A>
+<A NAME="IDX844"></A>
+<A NAME="IDX845"></A>
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 <VAR>number</VAR>.
-<DT><SAMP>`--no-wrap´</SAMP>
+<DT><SAMP>‘--no-wrap’</SAMP>
<DD>
-<A NAME="IDX829"></A>
+<A NAME="IDX846"></A>
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.
-<DT><SAMP>`-s´</SAMP>
+<DT><SAMP>‘-s’</SAMP>
<DD>
-<DT><SAMP>`--sort-output´</SAMP>
+<DT><SAMP>‘--sort-output’</SAMP>
<DD>
-<A NAME="IDX830"></A>
-<A NAME="IDX831"></A>
+<A NAME="IDX847"></A>
+<A NAME="IDX848"></A>
Generate sorted output. Note that using this option makes it much harder
for the translator to understand each message's context.
-<DT><SAMP>`-F´</SAMP>
+<DT><SAMP>‘-F’</SAMP>
<DD>
-<DT><SAMP>`--sort-by-file´</SAMP>
+<DT><SAMP>‘--sort-by-file’</SAMP>
<DD>
-<A NAME="IDX832"></A>
-<A NAME="IDX833"></A>
+<A NAME="IDX849"></A>
+<A NAME="IDX850"></A>
Sort output by file location.
</DL>
-<H3><A NAME="SEC134" HREF="gettext_toc.html#TOC134">9.9.5 Informative output</A></H3>
+<H3><A NAME="SEC136" HREF="gettext_toc.html#TOC136">9.9.5 Informative output</A></H3>
<DL COMPACT>
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX834"></A>
-<A NAME="IDX835"></A>
+<A NAME="IDX851"></A>
+<A NAME="IDX852"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX836"></A>
-<A NAME="IDX837"></A>
+<A NAME="IDX853"></A>
+<A NAME="IDX854"></A>
Output version information and exit.
</DL>
-<H2><A NAME="SEC135" HREF="gettext_toc.html#TOC135">9.10 Invoking the <CODE>msgexec</CODE> Program</A></H2>
+<H2><A NAME="SEC137" HREF="gettext_toc.html#TOC137">9.10 Invoking the <CODE>msgexec</CODE> Program</A></H2>
<P>
-<A NAME="IDX838"></A>
-<A NAME="IDX839"></A>
+<A NAME="IDX855"></A>
+<A NAME="IDX856"></A>
<PRE>
msgexec [<VAR>option</VAR>] <VAR>command</VAR> [<VAR>command-option</VAR>]
</PRE>
<P>
-<A NAME="IDX840"></A>
+<A NAME="IDX857"></A>
The <CODE>msgexec</CODE> program applies a command to all translations of a
translation catalog.
The <VAR>command</VAR> can be any program that reads a translation from standard
</P>
<P>
-<A NAME="IDX841"></A>
-A special builtin command called <SAMP>`0´</SAMP> outputs the translation, followed
-by a null byte. The output of <SAMP>`msgexec 0´</SAMP> is suitable as input for
-<SAMP>`xargs -0´</SAMP>.
+<A NAME="IDX858"></A>
+A special builtin command called <SAMP>‘0’</SAMP> outputs the translation, followed
+by a null byte. The output of <SAMP>‘msgexec 0’</SAMP> is suitable as input for
+<SAMP>‘xargs -0’</SAMP>.
</P>
<P>
-<A NAME="IDX842"></A>
-<A NAME="IDX843"></A>
+<A NAME="IDX859"></A>
+<A NAME="IDX860"></A>
+<A NAME="IDX861"></A>
During each <VAR>command</VAR> invocation, the environment variable
<CODE>MSGEXEC_MSGID</CODE> is bound to the message's msgid, and the environment
variable <CODE>MSGEXEC_LOCATION</CODE> is bound to the location in the PO file
-of the message.
+of the message. If the message has a context, the environment variable
+<CODE>MSGEXEC_MSGCTXT</CODE> is bound to the message's msgctxt, otherwise it is
+unbound.
</P>
<P>
-<A NAME="IDX844"></A>
+<A NAME="IDX862"></A>
Note: It is your responsibility to ensure that the <VAR>command</VAR> can cope
with input encoded in the translation catalog's encoding. If the
<VAR>command</VAR> wants input in a particular encoding, you can in a first step
-convert the translation catalog to that encoding using the <SAMP>`msgconv´</SAMP>
-program, before invoking <SAMP>`msgexec´</SAMP>. If the <VAR>command</VAR> wants input
+convert the translation catalog to that encoding using the <SAMP>‘msgconv’</SAMP>
+program, before invoking <SAMP>‘msgexec’</SAMP>. If the <VAR>command</VAR> wants input
in the locale's encoding, but you want to avoid the locale's encoding, then
you can first convert the translation catalog to UTF-8 using the
-<SAMP>`msgconv´</SAMP> program and then make <SAMP>`msgexec´</SAMP> work in an UTF-8
+<SAMP>‘msgconv’</SAMP> program and then make <SAMP>‘msgexec’</SAMP> work in an UTF-8
locale, by using the <CODE>LC_ALL</CODE> environment variable.
</P>
-<H3><A NAME="SEC136" HREF="gettext_toc.html#TOC136">9.10.1 Input file location</A></H3>
+<H3><A NAME="SEC138" HREF="gettext_toc.html#TOC138">9.10.1 Input file location</A></H3>
<DL COMPACT>
-<DT><SAMP>`-i <VAR>inputfile</VAR>´</SAMP>
+<DT><SAMP>‘-i <VAR>inputfile</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--input=<VAR>inputfile</VAR>´</SAMP>
+<DT><SAMP>‘--input=<VAR>inputfile</VAR>’</SAMP>
<DD>
-<A NAME="IDX845"></A>
-<A NAME="IDX846"></A>
+<A NAME="IDX863"></A>
+<A NAME="IDX864"></A>
Input PO file.
-<DT><SAMP>`-D <VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘-D <VAR>directory</VAR>’</SAMP>
<DD>
-<DT><SAMP>`--directory=<VAR>directory</VAR>´</SAMP>
+<DT><SAMP>‘--directory=<VAR>directory</VAR>’</SAMP>
<DD>
-<A NAME="IDX847"></A>
-<A NAME="IDX848"></A>
+<A NAME="IDX865"></A>
+<A NAME="IDX866"></A>
Add <VAR>directory</VAR> to the list of directories. Source files are
-searched relative to this list of directories. The resulting <TT>`.po´</TT>
+searched relative to this list of directories. The resulting <TT>‘.po’</TT>
file will be written relative to the current directory, though.
</DL>
<P>
-If no <VAR>inputfile</VAR> is given or if it is <SAMP>`-´</SAMP>, standard input is read.
+If no <VAR>inputfile</VAR> is given or if it is <SAMP>‘-’</SAMP>, standard input is read.
</P>
-<H3><A NAME="SEC137" HREF="gettext_toc.html#TOC137">9.10.2 Input file syntax</A></H3>
+<H3><A NAME="SEC139" HREF="gettext_toc.html#TOC139">9.10.2 Input file syntax</A></H3>
<DL COMPACT>
-<DT><SAMP>`-P´</SAMP>
+<DT><SAMP>‘-P’</SAMP>
<DD>
-<DT><SAMP>`--properties-input´</SAMP>
+<DT><SAMP>‘--properties-input’</SAMP>
<DD>
-<A NAME="IDX849"></A>
-<A NAME="IDX850"></A>
+<A NAME="IDX867"></A>
+<A NAME="IDX868"></A>
Assume the input file is a Java ResourceBundle in Java <CODE>.properties</CODE>
syntax, not in PO file syntax.
-<DT><SAMP>`--stringtable-input´</SAMP>
+<DT><SAMP>‘--stringtable-input’</SAMP>
<DD>
-<A NAME="IDX851"></A>
+<A NAME="IDX869"></A>
Assume the input file is a NeXTstep/GNUstep localized resource file in
<CODE>.strings</CODE> syntax, not in PO file syntax.
-<H3><A NAME="SEC138" HREF="gettext_toc.html#TOC138">9.10.3 Informative output</A></H3>
+<H3><A NAME="SEC140" HREF="gettext_toc.html#TOC140">9.10.3 Informative output</A></H3>
<DL COMPACT>
-<DT><SAMP>`-h´</SAMP>
+<DT><SAMP>‘-h’</SAMP>
<DD>
-<DT><SAMP>`--help´</SAMP>
+<DT><SAMP>‘--help’</SAMP>
<DD>
-<A NAME="IDX852"></A>
-<A NAME="IDX853"></A>
+<A NAME="IDX870"></A>
+<A NAME="IDX871"></A>
Display this help and exit.
-<DT><SAMP>`-V´</SAMP>
+<DT><SAMP>‘-V’</SAMP>
<DD>
-<DT><SAMP>`--version´</SAMP>
+<DT><SAMP>‘--version’</SAMP>
<DD>
-<A NAME="IDX854"></A>
-<A NAME="IDX855"></A>
+<A NAME="IDX872"></A>
+<A NAME="IDX873"></A>
Output version information and exit.
</DL>
-<H2><A NAME="SEC139" HREF="gettext_toc.html#TOC139">9.11 Writing your own programs that process PO files</A></H2>
+<H2><A NAME="SEC141" HREF="gettext_toc.html#TOC141">9.11 Writing your own programs that process PO files</A></H2>
<P>
-For the tasks for which a combination of <SAMP>`msgattrib´</SAMP>, <SAMP>`msgcat´</SAMP> etc.
+For the tasks for which a combination of <SAMP>‘msgattrib’</SAMP>, <SAMP>‘msgcat’</SAMP> etc.
is not sufficient, a set of C functions is provided in a library, to make it
possible to process PO files in your own programs. When you use this library,
you don't need to write routines to parse the PO file; instead, you retreive
</P>
<P>
-The functions are declared in the header file <SAMP>`<gettext-po.h>´</SAMP>, and are
-defined in a library called <SAMP>`libgettextpo´</SAMP>.
+The functions are declared in the header file <SAMP>‘<gettext-po.h>’</SAMP>, and are
+defined in a library called <SAMP>‘libgettextpo’</SAMP>.
</P>
<P>
<DL>
<DT><U>Data Type:</U> <B>po_file_t</B>
-<DD><A NAME="IDX856"></A>
+<DD><A NAME="IDX874"></A>
This is a pointer type that refers to the contents of a PO file, after it has
been read into memory.
</DL>
<P>
<DL>
<DT><U>Data Type:</U> <B>po_message_iterator_t</B>
-<DD><A NAME="IDX857"></A>
+<DD><A NAME="IDX875"></A>
This is a pointer type that refers to an iterator that produces a sequence of
messages.
</DL>
<P>
<DL>
<DT><U>Data Type:</U> <B>po_message_t</B>
-<DD><A NAME="IDX858"></A>
+<DD><A NAME="IDX876"></A>
This is a pointer type that refers to a message of a PO file, including its
translation.
</DL>
<P>
<DL>
<DT><U>Function:</U> po_file_t <B>po_file_read</B> <I>(const char *<VAR>filename</VAR>)</I>
-<DD><A NAME="IDX859"></A>
+<DD><A NAME="IDX877"></A>
The <CODE>po_file_read</CODE> function reads a PO file into memory. The file name
is given as argument. The return value is a handle to the PO file's contents,
valid until <CODE>po_file_free</CODE> is called on it. In case of error, the return
<P>
<DL>
<DT><U>Function:</U> void <B>po_file_free</B> <I>(po_file_t <VAR>file</VAR>)</I>
-<DD><A NAME="IDX860"></A>
+<DD><A NAME="IDX878"></A>
The <CODE>po_file_free</CODE> function frees a PO file's contents from memory,
including all messages that are only implicitly accessible through iterators.
</DL>
<P>
<DL>
<DT><U>Function:</U> const char * const * <B>po_file_domains</B> <I>(po_file_t <VAR>file</VAR>)</I>
-<DD><A NAME="IDX861"></A>
+<DD><A NAME="IDX879"></A>
The <CODE>po_file_domains</CODE> function returns the domains for which the given
PO file has messages. The return value is a <CODE>NULL</CODE> terminated array
which is valid as long as the <VAR>file</VAR> handle is valid. For PO files which
-contain no <SAMP>`domain´</SAMP> directive, the return value contains only one domain,
+contain no <SAMP>‘domain’</SAMP> directive, the return value contains only one domain,
namely the default domain <CODE>"messages"</CODE>.
</DL>
<P>
<DL>
<DT><U>Function:</U> po_message_iterator_t <B>po_message_iterator</B> <I>(po_file_t <VAR>file</VAR>, const char *<VAR>domain</VAR>)</I>
-<DD><A NAME="IDX862"></A>
+<DD><A NAME="IDX880"></A>
The <CODE>po_message_iterator</CODE> returns an iterator that will produce the
messages of <VAR>file</VAR> that belong to the given <VAR>domain</VAR>. If <VAR>domain</VAR>
is <CODE>NULL</CODE>, the default domain is used instead. To list the messages,
<P>
<DL>
<DT><U>Function:</U> void <B>po_message_iterator_free</B> <I>(po_message_iterator_t <VAR>iterator</VAR>)</I>
-<DD><A NAME="IDX863"></A>
+<DD><A NAME="IDX881"></A>
The <CODE>po_message_iterator_free</CODE> function frees an iterator previously
allocated through the <CODE>po_message_iterator</CODE> function.
</DL>
<P>
<DL>
<DT><U>Function:</U> po_message_t <B>po_next_message</B> <I>(po_message_iterator_t <VAR>iterator</VAR>)</I>
-<DD><A NAME="IDX864"></A>
+<DD><A NAME="IDX882"></A>
The <CODE>po_next_message</CODE> function returns the next message from
<VAR>iterator</VAR> and advances the iterator. It returns <CODE>NULL</CODE> when the
iterator has reached the end of its message list.
<P>
<DL>
<DT><U>Function:</U> const char * <B>po_message_msgid</B> <I>(po_message_t <VAR>message</VAR>)</I>
-<DD><A NAME="IDX865"></A>
+<DD><A NAME="IDX883"></A>
The <CODE>po_message_msgid</CODE> function returns the <CODE>msgid</CODE> (untranslated
English string) of a message. This is guaranteed to be non-<CODE>NULL</CODE>.
</DL>
<P>
<DL>
<DT><U>Function:</U> const char * <B>po_message_msgid_plural</B> <I>(po_message_t <VAR>message</VAR>)</I>
-<DD><A NAME="IDX866"></A>
+<DD><A NAME="IDX884"></A>
The <CODE>po_message_msgid_plural</CODE> function returns the <CODE>msgid_plural</CODE>
(untranslated English plural string) of a message with plurals, or <CODE>NULL</CODE>
for a message without plural.
<P>
<DL>
<DT><U>Function:</U> const char * <B>po_message_msgstr</B> <I>(po_message_t <VAR>message</VAR>)</I>
-<DD><A NAME="IDX867"></A>
+<DD><A NAME="IDX885"></A>
The <CODE>po_message_msgstr</CODE> function returns the <CODE>msgstr</CODE> (translation)
of a message. For an untranslated message, the return value is an empty
string.
<P>
<DL>
<DT><U>Function:</U> const char * <B>po_message_msgstr_plural</B> <I>(po_message_t <VAR>message</VAR>, int <VAR>index</VAR>)</I>
-<DD><A NAME="IDX868"></A>
+<DD><A NAME="IDX886"></A>
The <CODE>po_message_msgstr_plural</CODE> function returns the
<CODE>msgstr[<VAR>index</VAR>]</CODE> of a message with plurals, or <CODE>NULL</CODE> when
the <VAR>index</VAR> is out of range or for a message without plural.
</PRE>
<P><HR><P>
-Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_8.html">previous</A>, <A HREF="gettext_10.html">next</A>, <A HREF="gettext_2
4.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
+Go to the <A HREF="gettext_1.html">first</A>, <A HREF="gettext_8.html">previous</A>, <A HREF="gettext_10.html">next</A>, <A HREF="gettext_2
5.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 11 April 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - Footnotes</TITLE>
</HEAD>
<BODY>
-<H1>GNU gettext tools, version 0.14.4</H1>
+<H1>GNU gettext tools, version 0.15</H1>
<H2>Native Language Support Library and Tools</H2>
-<H2>Edition 0.14.4, 8 March 2005</H2>
+<H2>Edition 0.15, 30 June 2006</H2>
<ADDRESS>Ulrich Drepper</ADDRESS>
<ADDRESS>Jim Meyering</ADDRESS>
<ADDRESS>François Pinard</ADDRESS>
<P>In this manual, all mentions of Emacs
refers to either GNU Emacs or to XEmacs, which people sometimes call FSF
Emacs and Lucid Emacs, respectively.
-<H3><A NAME="FOOT2" HREF="gettext_2.html#DOCF2">(2)</A></H3>
+<H3><A NAME="FOOT2" HREF="gettext_3.html#DOCF2">(2)</A></H3>
<P>This
limitation is not imposed by GNU <CODE>gettext</CODE>, but is for compatibility
with the <CODE>msgfmt</CODE> implementation on Solaris.
-<H3><A NAME="FOOT3" HREF="gettext_10.html#DOCF3">(3)</A></H3>
+<H3><A NAME="FOOT3" HREF="gettext_11.html#DOCF3">(3)</A></H3>
<P>Some
system, eg Ultrix, don't have <CODE>LC_MESSAGES</CODE>. Here we use a more or
less arbitrary value for it, namely 1729, the smallest positive integer
which can be represented in two different ways as the sum of two cubes.
-<H3><A NAME="FOOT4" HREF="gettext_10.html#DOCF4">(4)</A></H3>
+<H3><A NAME="FOOT4" HREF="gettext_11.html#DOCF4">(4)</A></H3>
<P>When the system does not support <CODE>setlocale</CODE> its behavior
in setting the locale values is simulated by looking at the environment
variables.
-<H3><A NAME="FOOT5" HREF="gettext_10.html#DOCF5">(5)</A></H3>
+<H3><A NAME="FOOT5" HREF="gettext_11.html#DOCF5">(5)</A></H3>
<P>Additions are welcome. Send appropriate information to
<A HREF="mailto:bug-glibc-manual@gnu.org">bug-glibc-manual@gnu.org</A>.
<P><HR><P>
-This document was generated on 11 April 2005 using the
+This document was generated on 20 July 2006 using the
<A HREF="http://wwwinfo.cern.ch/dis/texi2html/">texi2html</A>
-translator version 1.52a.</P>
+translator version 1.52b.</P>
</BODY>
</HTML>
<HTML>
<HEAD>
-<!-- This HTML file has been created by texi2html 1.52a
- from gettext.texi on 11 April 2005 -->
+<!-- This HTML file has been created by texi2html 1.52b
+ from gettext.texi on 20 July 2006 -->
+<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<TITLE>GNU gettext utilities - Table of Contents</TITLE>
</HEAD>
<BODY>
-<H1>GNU gettext tools, version 0.14.4</H1>
+<H1>GNU gettext tools, version 0.15</H1>
<H2>Native Language Support Library and Tools</H2>
-<H2>Edition 0.14.4, 8 March 2005</H2>
+<H2>Edition 0.15, 30 June 2006</H2>
<ADDRESS>Ulrich Drepper</ADDRESS>
<ADDRESS>Jim Meyering</ADDRESS>
<ADDRESS>François Pinard</ADDRESS>
<LI><A NAME="TOC5" HREF="gettext_1.html#SEC5">1.4 Files Conveying Translations</A>
<LI><A NAME="TOC6" HREF="gettext_1.html#SEC6">1.5 Overview of GNU <CODE>gettext</CODE></A>
</UL>
-<LI><A NAME="TOC7" HREF="gettext_2.html#SEC7">2 PO Files and PO Mode Basics</A>
+<LI><A NAME="TOC7" HREF="gettext_2.html#SEC7">2 The User's View</A>
<UL>
-<LI><A NAME="TOC8" HREF="gettext_2.html#SEC8">2.1 Completing GNU <CODE>gettext</CODE> Installation</A>
-<LI><A NAME="TOC9" HREF="gettext_2.html#SEC9">2.2 The Format of PO Files</A>
-<LI><A NAME="TOC10" HREF="gettext_2.html#SEC10">2.3 Main PO mode Commands</A>
-<LI><A NAME="TOC11" HREF="gettext_2.html#SEC11">2.4 Entry Positioning</A>
-<LI><A NAME="TOC12" HREF="gettext_2.html#SEC12">2.5 Normalizing Strings in Entries</A>
+<LI><A NAME="TOC8" HREF="gettext_2.html#SEC8">2.1 The Current <TT>‘ABOUT-NLS’</TT> Matrix</A>
+<LI><A NAME="TOC9" HREF="gettext_2.html#SEC9">2.2 Magic for End Users</A>
</UL>
-<LI><A NAME="TOC13" HREF="gettext_3.html#SEC13">3 Preparing Program Sources</A>
+<LI><A NAME="TOC10" HREF="gettext_3.html#SEC10">3 The Format of PO Files</A>
+<LI><A NAME="TOC11" HREF="gettext_4.html#SEC11">4 Preparing Program Sources</A>
<UL>
-<LI><A NAME="TOC14" HREF="gettext_3.html#SEC14">3.1 Triggering <CODE>gettext</CODE> Operations</A>
-<LI><A NAME="TOC15" HREF="gettext_3.html#SEC15">3.2 Preparing Translatable Strings</A>
-<LI><A NAME="TOC16" HREF="gettext_3.html#SEC16">3.3 How Marks Appear in Sources</A>
-<LI><A NAME="TOC17" HREF="gettext_3.html#SEC17">3.4 Marking Translatable Strings</A>
-<LI><A NAME="TOC18" HREF="gettext_3.html#SEC18">3.5 Special Comments preceding Keywords</A>
-<LI><A NAME="TOC19" HREF="gettext_3.html#SEC19">3.6 Special Cases of Translatable Strings</A>
-<LI><A NAME="TOC20" HREF="gettext_3.html#SEC20">3.7 Marking Proper Names for Translation</A>
-<LI><A NAME="TOC21" HREF="gettext_3.html#SEC21">3.8 Preparing Library Sources</A>
+<LI><A NAME="TOC12" HREF="gettext_4.html#SEC12">4.1 Importing the <CODE>gettext</CODE> declaration</A>
+<LI><A NAME="TOC13" HREF="gettext_4.html#SEC13">4.2 Triggering <CODE>gettext</CODE> Operations</A>
+<LI><A NAME="TOC14" HREF="gettext_4.html#SEC14">4.3 Preparing Translatable Strings</A>
+<LI><A NAME="TOC15" HREF="gettext_4.html#SEC15">4.4 How Marks Appear in Sources</A>
+<LI><A NAME="TOC16" HREF="gettext_4.html#SEC16">4.5 Marking Translatable Strings</A>
+<LI><A NAME="TOC17" HREF="gettext_4.html#SEC17">4.6 Special Comments preceding Keywords</A>
+<LI><A NAME="TOC18" HREF="gettext_4.html#SEC18">4.7 Special Cases of Translatable Strings</A>
+<LI><A NAME="TOC19" HREF="gettext_4.html#SEC19">4.8 Marking Proper Names for Translation</A>
+<LI><A NAME="TOC20" HREF="gettext_4.html#SEC20">4.9 Preparing Library Sources</A>
</UL>
-<LI><A NAME="TOC22" HREF="gettext_4.html#SEC22">4 Making the PO Template File</A>
+<LI><A NAME="TOC21" HREF="gettext_5.html#SEC21">5 Making the PO Template File</A>
<UL>
-<LI><A NAME="TOC23" HREF="gettext_4.html#SEC23">4.1 Invoking the <CODE>xgettext</CODE> Program</A>
+<LI><A NAME="TOC22" HREF="gettext_5.html#SEC22">5.1 Invoking the <CODE>xgettext</CODE> Program</A>
<UL>
-<LI><A NAME="TOC24" HREF="gettext_4.html#SEC24">4.1.1 Input file location</A>
-<LI><A NAME="TOC25" HREF="gettext_4.html#SEC25">4.1.2 Output file location</A>
-<LI><A NAME="TOC26" HREF="gettext_4.html#SEC26">4.1.3 Choice of input file language</A>
-<LI><A NAME="TOC27" HREF="gettext_4.html#SEC27">4.1.4 Input file interpretation</A>
-<LI><A NAME="TOC28" HREF="gettext_4.html#SEC28">4.1.5 Operation mode</A>
-<LI><A NAME="TOC29" HREF="gettext_4.html#SEC29">4.1.6 Language specific options</A>
-<LI><A NAME="TOC30" HREF="gettext_4.html#SEC30">4.1.7 Output details</A>
-<LI><A NAME="TOC31" HREF="gettext_4.html#SEC31">4.1.8 Informative output</A>
+<LI><A NAME="TOC23" HREF="gettext_5.html#SEC23">5.1.1 Input file location</A>
+<LI><A NAME="TOC24" HREF="gettext_5.html#SEC24">5.1.2 Output file location</A>
+<LI><A NAME="TOC25" HREF="gettext_5.html#SEC25">5.1.3 Choice of input file language</A>
+<LI><A NAME="TOC26" HREF="gettext_5.html#SEC26">5.1.4 Input file interpretation</A>
+<LI><A NAME="TOC27" HREF="gettext_5.html#SEC27">5.1.5 Operation mode</A>
+<LI><A NAME="TOC28" HREF="gettext_5.html#SEC28">5.1.6 Language specific options</A>
+<LI><A NAME="TOC29" HREF="gettext_5.html#SEC29">5.1.7 Output details</A>
+<LI><A NAME="TOC30" HREF="gettext_5.html#SEC30">5.1.8 Informative output</A>
</UL>
</UL>
-<LI><A NAME="TOC32" HREF="gettext_5.html#SEC32">5 Creating a New PO File</A>
+<LI><A NAME="TOC31" HREF="gettext_6.html#SEC31">6 Creating a New PO File</A>
<UL>
-<LI><A NAME="TOC33" HREF="gettext_5.html#SEC33">5.1 Invoking the <CODE>msginit</CODE> Program</A>
-<UL>
-<LI><A NAME="TOC34" HREF="gettext_5.html#SEC34">5.1.1 Input file location</A>
-<LI><A NAME="TOC35" HREF="gettext_5.html#SEC35">5.1.2 Output file location</A>
-<LI><A NAME="TOC36" HREF="gettext_5.html#SEC36">5.1.3 Input file syntax</A>
-<LI><A NAME="TOC37" HREF="gettext_5.html#SEC37">5.1.4 Output details</A>
-<LI><A NAME="TOC38" HREF="gettext_5.html#SEC38">5.1.5 Informative output</A>
-</UL>
-<LI><A NAME="TOC39" HREF="gettext_5.html#SEC39">5.2 Filling in the Header Entry</A>
-</UL>
-<LI><A NAME="TOC40" HREF="gettext_6.html#SEC40">6 Updating Existing PO Files</A>
-<UL>
-<LI><A NAME="TOC41" HREF="gettext_6.html#SEC41">6.1 Invoking the <CODE>msgmerge</CODE> Program</A>
-<UL>
-<LI><A NAME="TOC42" HREF="gettext_6.html#SEC42">6.1.1 Input file location</A>
-<LI><A NAME="TOC43" HREF="gettext_6.html#SEC43">6.1.2 Operation mode</A>
-<LI><A NAME="TOC44" HREF="gettext_6.html#SEC44">6.1.3 Output file location</A>
-<LI><A NAME="TOC45" HREF="gettext_6.html#SEC45">6.1.4 Output file location in update mode</A>
-<LI><A NAME="TOC46" HREF="gettext_6.html#SEC46">6.1.5 Operation modifiers</A>
-<LI><A NAME="TOC47" HREF="gettext_6.html#SEC47">6.1.6 Input file syntax</A>
-<LI><A NAME="TOC48" HREF="gettext_6.html#SEC48">6.1.7 Output details</A>
-<LI><A NAME="TOC49" HREF="gettext_6.html#SEC49">6.1.8 Informative output</A>
-</UL>
-<LI><A NAME="TOC50" HREF="gettext_6.html#SEC50">6.2 Translated Entries</A>
-<LI><A NAME="TOC51" HREF="gettext_6.html#SEC51">6.3 Fuzzy Entries</A>
-<LI><A NAME="TOC52" HREF="gettext_6.html#SEC52">6.4 Untranslated Entries</A>
-<LI><A NAME="TOC53" HREF="gettext_6.html#SEC53">6.5 Obsolete Entries</A>
-<LI><A NAME="TOC54" HREF="gettext_6.html#SEC54">6.6 Modifying Translations</A>
-<LI><A NAME="TOC55" HREF="gettext_6.html#SEC55">6.7 Modifying Comments</A>
-<LI><A NAME="TOC56" HREF="gettext_6.html#SEC56">6.8 Details of Sub Edition</A>
-<LI><A NAME="TOC57" HREF="gettext_6.html#SEC57">6.9 C Sources Context</A>
-<LI><A NAME="TOC58" HREF="gettext_6.html#SEC58">6.10 Consulting Auxiliary PO Files</A>
-<LI><A NAME="TOC59" HREF="gettext_6.html#SEC59">6.11 Using Translation Compendia</A>
-<UL>
-<LI><A NAME="TOC60" HREF="gettext_6.html#SEC60">6.11.1 Creating Compendia</A>
-<UL>
-<LI><A NAME="TOC61" HREF="gettext_6.html#SEC61">6.11.1.1 Concatenate PO Files</A>
-<LI><A NAME="TOC62" HREF="gettext_6.html#SEC62">6.11.1.2 Extract a Message Subset from a PO File</A>
-</UL>
-<LI><A NAME="TOC63" HREF="gettext_6.html#SEC63">6.11.2 Using Compendia</A>
-<UL>
-<LI><A NAME="TOC64" HREF="gettext_6.html#SEC64">6.11.2.1 Initialize a New Translation File</A>
-<LI><A NAME="TOC65" HREF="gettext_6.html#SEC65">6.11.2.2 Update an Existing Translation File</A>
-</UL>
+<LI><A NAME="TOC32" HREF="gettext_6.html#SEC32">6.1 Invoking the <CODE>msginit</CODE> Program</A>
+<UL>
+<LI><A NAME="TOC33" HREF="gettext_6.html#SEC33">6.1.1 Input file location</A>
+<LI><A NAME="TOC34" HREF="gettext_6.html#SEC34">6.1.2 Output file location</A>
+<LI><A NAME="TOC35" HREF="gettext_6.html#SEC35">6.1.3 Input file syntax</A>
+<LI><A NAME="TOC36" HREF="gettext_6.html#SEC36">6.1.4 Output details</A>
+<LI><A NAME="TOC37" HREF="gettext_6.html#SEC37">6.1.5 Informative output</A>
</UL>
-</UL>
-<LI><A NAME="TOC66" HREF="gettext_7.html#SEC66">7 Manipulating PO Files</A>
+<LI><A NAME="TOC38" HREF="gettext_6.html#SEC38">6.2 Filling in the Header Entry</A>
+</UL>
+<LI><A NAME="TOC39" HREF="gettext_7.html#SEC39">7 Updating Existing PO Files</A>
<UL>
-<LI><A NAME="TOC67" HREF="gettext_7.html#SEC67">7.1 Invoking the <CODE>msgcat</CODE> Program</A>
+<LI><A NAME="TOC40" HREF="gettext_7.html#SEC40">7.1 Invoking the <CODE>msgmerge</CODE> Program</A>
<UL>
-<LI><A NAME="TOC68" HREF="gettext_7.html#SEC68">7.1.1 Input file location</A>
-<LI><A NAME="TOC69" HREF="gettext_7.html#SEC69">7.1.2 Output file location</A>
-<LI><A NAME="TOC70" HREF="gettext_7.html#SEC70">7.1.3 Message selection</A>
-<LI><A NAME="TOC71" HREF="gettext_7.html#SEC71">7.1.4 Input file syntax</A>
-<LI><A NAME="TOC72" HREF="gettext_7.html#SEC72">7.1.5 Output details</A>
-<LI><A NAME="TOC73" HREF="gettext_7.html#SEC73">7.1.6 Informative output</A>
+<LI><A NAME="TOC41" HREF="gettext_7.html#SEC41">7.1.1 Input file location</A>
+<LI><A NAME="TOC42" HREF="gettext_7.html#SEC42">7.1.2 Operation mode</A>
+<LI><A NAME="TOC43" HREF="gettext_7.html#SEC43">7.1.3 Output file location</A>
+<LI><A NAME="TOC44" HREF="gettext_7.html#SEC44">7.1.4 Output file location in update mode</A>
+<LI><A NAME="TOC45" HREF="gettext_7.html#SEC45">7.1.5 Operation modifiers</A>
+<LI><A NAME="TOC46" HREF="gettext_7.html#SEC46">7.1.6 Input file syntax</A>
+<LI><A NAME="TOC47" HREF="gettext_7.html#SEC47">7.1.7 Output details</A>
+<LI><A NAME="TOC48" HREF="gettext_7.html#SEC48">7.1.8 Informative output</A>
</UL>
-<LI><A NAME="TOC74" HREF="gettext_7.html#SEC74">7.2 Invoking the <CODE>msgconv</CODE> Program</A>
-<UL>
-<LI><A NAME="TOC75" HREF="gettext_7.html#SEC75">7.2.1 Input file location</A>
-<LI><A NAME="TOC76" HREF="gettext_7.html#SEC76">7.2.2 Output file location</A>
-<LI><A NAME="TOC77" HREF="gettext_7.html#SEC77">7.2.3 Conversion target</A>
-<LI><A NAME="TOC78" HREF="gettext_7.html#SEC78">7.2.4 Input file syntax</A>
-<LI><A NAME="TOC79" HREF="gettext_7.html#SEC79">7.2.5 Output details</A>
-<LI><A NAME="TOC80" HREF="gettext_7.html#SEC80">7.2.6 Informative output</A>
</UL>
-<LI><A NAME="TOC81" HREF="gettext_7.html#SEC81">7.3 Invoking the <CODE>msggrep</CODE> Program</A>
+<LI><A NAME="TOC49" HREF="gettext_8.html#SEC49">8 Editing PO Files</A>
+<UL>
+<LI><A NAME="TOC50" HREF="gettext_8.html#SEC50">8.1 KDE's PO File Editor</A>
+<LI><A NAME="TOC51" HREF="gettext_8.html#SEC51">8.2 GNOME's PO File Editor</A>
+<LI><A NAME="TOC52" HREF="gettext_8.html#SEC52">8.3 Emacs's PO File Editor</A>
+<UL>
+<LI><A NAME="TOC53" HREF="gettext_8.html#SEC53">8.3.1 Completing GNU <CODE>gettext</CODE> Installation</A>
+<LI><A NAME="TOC54" HREF="gettext_8.html#SEC54">8.3.2 Main PO mode Commands</A>
+<LI><A NAME="TOC55" HREF="gettext_8.html#SEC55">8.3.3 Entry Positioning</A>
+<LI><A NAME="TOC56" HREF="gettext_8.html#SEC56">8.3.4 Normalizing Strings in Entries</A>
+<LI><A NAME="TOC57" HREF="gettext_8.html#SEC57">8.3.5 Translated Entries</A>
+<LI><A NAME="TOC58" HREF="gettext_8.html#SEC58">8.3.6 Fuzzy Entries</A>
+<LI><A NAME="TOC59" HREF="gettext_8.html#SEC59">8.3.7 Untranslated Entries</A>
+<LI><A NAME="TOC60" HREF="gettext_8.html#SEC60">8.3.8 Obsolete Entries</A>
+<LI><A NAME="TOC61" HREF="gettext_8.html#SEC61">8.3.9 Modifying Translations</A>
+<LI><A NAME="TOC62" HREF="gettext_8.html#SEC62">8.3.10 Modifying Comments</A>
+<LI><A NAME="TOC63" HREF="gettext_8.html#SEC63">8.3.11 Details of Sub Edition</A>
+<LI><A NAME="TOC64" HREF="gettext_8.html#SEC64">8.3.12 C Sources Context</A>
+<LI><A NAME="TOC65" HREF="gettext_8.html#SEC65">8.3.13 Consulting Auxiliary PO Files</A>
+<LI><A NAME="TOC66" HREF="gettext_8.html#SEC66">8.3.14 Using Translation Compendia</A>
<UL>
-<LI><A NAME="TOC82" HREF="gettext_7.html#SEC82">7.3.1 Input file location</A>
-<LI><A NAME="TOC83" HREF="gettext_7.html#SEC83">7.3.2 Output file location</A>
-<LI><A NAME="TOC84" HREF="gettext_7.html#SEC84">7.3.3 Message selection</A>
-<LI><A NAME="TOC85" HREF="gettext_7.html#SEC85">7.3.4 Input file syntax</A>
-<LI><A NAME="TOC86" HREF="gettext_7.html#SEC86">7.3.5 Output details</A>
-<LI><A NAME="TOC87" HREF="gettext_7.html#SEC87">7.3.6 Informative output</A>
+<LI><A NAME="TOC67" HREF="gettext_8.html#SEC67">8.3.14.1 Creating Compendia</A>
+<LI><A NAME="TOC68" HREF="gettext_8.html#SEC68">8.3.14.2 Concatenate PO Files</A>
+<LI><A NAME="TOC69" HREF="gettext_8.html#SEC69">8.3.14.3 Extract a Message Subset from a PO File</A>
+<LI><A NAME="TOC70" HREF="gettext_8.html#SEC70">8.3.14.4 Using Compendia</A>
+<LI><A NAME="TOC71" HREF="gettext_8.html#SEC71">8.3.14.5 Initialize a New Translation File</A>
+<LI><A NAME="TOC72" HREF="gettext_8.html#SEC72">8.3.14.6 Update an Existing Translation File</A>
</UL>
-<LI><A NAME="TOC88" HREF="gettext_7.html#SEC88">7.4 Invoking the <CODE>msgfilter</CODE> Program</A>
-<UL>
-<LI><A NAME="TOC89" HREF="gettext_7.html#SEC89">7.4.1 Input file location</A>
-<LI><A NAME="TOC90" HREF="gettext_7.html#SEC90">7.4.2 Output file location</A>
-<LI><A NAME="TOC91" HREF="gettext_7.html#SEC91">7.4.3 The filter</A>
-<LI><A NAME="TOC92" HREF="gettext_7.html#SEC92">7.4.4 Useful <VAR>filter-option</VAR>s when the <VAR>filter</VAR> is <SAMP>`sed´</SAMP></A>
-<LI><A NAME="TOC93" HREF="gettext_7.html#SEC93">7.4.5 Input file syntax</A>
-<LI><A NAME="TOC94" HREF="gettext_7.html#SEC94">7.4.6 Output details</A>
-<LI><A NAME="TOC95" HREF="gettext_7.html#SEC95">7.4.7 Informative output</A>
</UL>
-<LI><A NAME="TOC96" HREF="gettext_7.html#SEC96">7.5 Invoking the <CODE>msguniq</CODE> Program</A>
-<UL>
-<LI><A NAME="TOC97" HREF="gettext_7.html#SEC97">7.5.1 Input file location</A>
-<LI><A NAME="TOC98" HREF="gettext_7.html#SEC98">7.5.2 Output file location</A>
-<LI><A NAME="TOC99" HREF="gettext_7.html#SEC99">7.5.3 Message selection</A>
-<LI><A NAME="TOC100" HREF="gettext_7.html#SEC100">7.5.4 Input file syntax</A>
-<LI><A NAME="TOC101" HREF="gettext_7.html#SEC101">7.5.5 Output details</A>
-<LI><A NAME="TOC102" HREF="gettext_7.html#SEC102">7.5.6 Informative output</A>
</UL>
-<LI><A NAME="TOC103" HREF="gettext_7.html#SEC103">7.6 Invoking the <CODE>msgcomm</CODE> Program</A>
+<LI><A NAME="TOC73" HREF="gettext_9.html#SEC73">9 Manipulating PO Files</A>
<UL>
-<LI><A NAME="TOC104" HREF="gettext_7.html#SEC104">7.6.1 Input file location</A>
-<LI><A NAME="TOC105" HREF="gettext_7.html#SEC105">7.6.2 Output file location</A>
-<LI><A NAME="TOC106" HREF="gettext_7.html#SEC106">7.6.3 Message selection</A>
-<LI><A NAME="TOC107" HREF="gettext_7.html#SEC107">7.6.4 Input file syntax</A>
-<LI><A NAME="TOC108" HREF="gettext_7.html#SEC108">7.6.5 Output details</A>
-<LI><A NAME="TOC109" HREF="gettext_7.html#SEC109">7.6.6 Informative output</A>
+<LI><A NAME="TOC74" HREF="gettext_9.html#SEC74">9.1 Invoking the <CODE>msgcat</CODE> Program</A>
+<UL>
+<LI><A NAME="TOC75" HREF="gettext_9.html#SEC75">9.1.1 Input file location</A>
+<LI><A NAME="TOC76" HREF="gettext_9.html#SEC76">9.1.2 Output file location</A>
+<LI><A NAME="TOC77" HREF="gettext_9.html#SEC77">9.1.3 Message selection</A>
+<LI><A NAME="TOC78" HREF="gettext_9.html#SEC78">9.1.4 Input file syntax</A>
+<LI><A NAME="TOC79" HREF="gettext_9.html#SEC79">9.1.5 Output details</A>
+<LI><A NAME="TOC80" HREF="gettext_9.html#SEC80">9.1.6 Informative output</A>
+</UL>
+<LI><A NAME="TOC81" HREF="gettext_9.html#SEC81">9.2 Invoking the <CODE>msgconv</CODE> Program</A>
+<UL>
+<LI><A NAME="TOC82" HREF="gettext_9.html#SEC82">9.2.1 Input file location</A>
+<LI><A NAME="TOC83" HREF="gettext_9.html#SEC83">9.2.2 Output file location</A>
+<LI><A NAME="TOC84" HREF="gettext_9.html#SEC84">9.2.3 Conversion target</A>
+<LI><A NAME="TOC85" HREF="gettext_9.html#SEC85">9.2.4 Input file syntax</A>
+<LI><A NAME="TOC86" HREF="gettext_9.html#SEC86">9.2.5 Output details</A>
+<LI><A NAME="TOC87" HREF="gettext_9.html#SEC87">9.2.6 Informative output</A>
+</UL>
+<LI><A NAME="TOC88" HREF="gettext_9.html#SEC88">9.3 Invoking the <CODE>msggrep</CODE> Program</A>
+<UL>
+<LI><A NAME="TOC89" HREF="gettext_9.html#SEC89">9.3.1 Input file location</A>
+<LI><A NAME="TOC90" HREF="gettext_9.html#SEC90">9.3.2 Output file location</A>
+<LI><A NAME="TOC91" HREF="gettext_9.html#SEC91">9.3.3 Message selection</A>
+<LI><A NAME="TOC92" HREF="gettext_9.html#SEC92">9.3.4 Input file syntax</A>
+<LI><A NAME="TOC93" HREF="gettext_9.html#SEC93">9.3.5 Output details</A>
+<LI><A NAME="TOC94" HREF="gettext_9.html#SEC94">9.3.6 Informative output</A>
</UL>
-<LI><A NAME="TOC110" HREF="gettext_7.html#SEC110">7.7 Invoking the <CODE>msgcmp</CODE> Program</A>
+<LI><A NAME="TOC95" HREF="gettext_9.html#SEC95">9.4 Invoking the <CODE>msgfilter</CODE> Program</A>
<UL>
-<LI><A NAME="TOC111" HREF="gettext_7.html#SEC111">7.7.1 Input file location</A>
-<LI><A NAME="TOC112" HREF="gettext_7.html#SEC112">7.7.2 Operation modifiers</A>
-<LI><A NAME="TOC113" HREF="gettext_7.html#SEC113">7.7.3 Input file syntax</A>
-<LI><A NAME="TOC114" HREF="gettext_7.html#SEC114">7.7.4 Informative output</A>
-</UL>
-<LI><A NAME="TOC115" HREF="gettext_7.html#SEC115">7.8 Invoking the <CODE>msgattrib</CODE> Program</A>
+<LI><A NAME="TOC96" HREF="gettext_9.html#SEC96">9.4.1 Input file location</A>
+<LI><A NAME="TOC97" HREF="gettext_9.html#SEC97">9.4.2 Output file location</A>
+<LI><A NAME="TOC98" HREF="gettext_9.html#SEC98">9.4.3 The filter</A>
+<LI><A NAME="TOC99" HREF="gettext_9.html#SEC99">9.4.4 Useful <VAR>filter-option</VAR>s when the <VAR>filter</VAR> is <SAMP>‘sed’</SAMP></A>
+<LI><A NAME="TOC100" HREF="gettext_9.html#SEC100">9.4.5 Built-in <VAR>filter</VAR>s</A>
+<LI><A NAME="TOC101" HREF="gettext_9.html#SEC101">9.4.6 Input file syntax</A>
+<LI><A NAME="TOC102" HREF="gettext_9.html#SEC102">9.4.7 Output details</A>
+<LI><A NAME="TOC103" HREF="gettext_9.html#SEC103">9.4.8 Informative output</A>
+</UL>
+<LI><A NAME="TOC104" HREF="gettext_9.html#SEC104">9.5 Invoking the <CODE>msguniq</CODE> Program</A>
<UL>
-<LI><A NAME="TOC116" HREF="gettext_7.html#SEC116">7.8.1 Input file location</A>
-<LI><A NAME="TOC117" HREF="gettext_7.html#SEC117">7.8.2 Output file location</A>
-<LI><A NAME="TOC118" HREF="gettext_7.html#SEC118">7.8.3 Message selection</A>
-<LI><A NAME="TOC119" HREF="gettext_7.html#SEC119">7.8.4 Attribute manipulation</A>
-<LI><A NAME="TOC120" HREF="gettext_7.html#SEC120">7.8.5 Input file syntax</A>
-<LI><A NAME="TOC121" HREF="gettext_7.html#SEC121">7.8.6 Output details</A>
-<LI><A NAME="TOC122" HREF="gettext_7.html#SEC122">7.8.7 Informative output</A>
+<LI><A NAME="TOC105" HREF="gettext_9.html#SEC105">9.5.1 Input file location</A>
+<LI><A NAME="TOC106" HREF="gettext_9.html#SEC106">9.5.2 Output file location</A>
+<LI><A NAME="TOC107" HREF="gettext_9.html#SEC107">9.5.3 Message selection</A>
+<LI><A NAME="TOC108" HREF="gettext_9.html#SEC108">9.5.4 Input file syntax</A>
+<LI><A NAME="TOC109" HREF="gettext_9.html#SEC109">9.5.5 Output details</A>
+<LI><A NAME="TOC110" HREF="gettext_9.html#SEC110">9.5.6 Informative output</A>
+</UL>
+<LI><A NAME="TOC111" HREF="gettext_9.html#SEC111">9.6 Invoking the <CODE>msgcomm</CODE> Program</A>
+<UL>
+<LI><A NAME="TOC112" HREF="gettext_9.html#SEC112">9.6.1 Input file location</A>
+<LI><A NAME="TOC113" HREF="gettext_9.html#SEC113">9.6.2 Output file location</A>
+<LI><A NAME="TOC114" HREF="gettext_9.html#SEC114">9.6.3 Message selection</A>
+<LI><A NAME="TOC115" HREF="gettext_9.html#SEC115">9.6.4 Input file syntax</A>
+<LI><A NAME="TOC116" HREF="gettext_9.html#SEC116">9.6.5 Output details</A>
+<LI><A NAME="TOC117" HREF="gettext_9.html#SEC117">9.6.6 Informative output</A>
+</UL>
+<LI><A NAME="TOC118" HREF="gettext_9.html#SEC118">9.7 Invoking the <CODE>msgcmp</CODE> Program</A>
+<UL>
+<LI><A NAME="TOC119" HREF="gettext_9.html#SEC119">9.7.1 Input file location</A>
+<LI><A NAME="TOC120" HREF="gettext_9.html#SEC120">9.7.2 Operation modifiers</A>
+<LI><A NAME="TOC121" HREF="gettext_9.html#SEC121">9.7.3 Input file syntax</A>
+<LI><A NAME="TOC122" HREF="gettext_9.html#SEC122">9.7.4 Informative output</A>
</UL>
-<LI><A NAME="TOC123" HREF="gettext_7.html#SEC123">7.9 Invoking the <CODE>msgen</CODE> Program</A>
+<LI><A NAME="TOC123" HREF="gettext_9.html#SEC123">9.8 Invoking the <CODE>msgattrib</CODE> Program</A>
<UL>
-<LI><A NAME="TOC124" HREF="gettext_7.html#SEC124">7.9.1 Input file location</A>
-<LI><A NAME="TOC125" HREF="gettext_7.html#SEC125">7.9.2 Output file location</A>
-<LI><A NAME="TOC126" HREF="gettext_7.html#SEC126">7.9.3 Input file syntax</A>
-<LI><A NAME="TOC127" HREF="gettext_7.html#SEC127">7.9.4 Output details</A>
-<LI><A NAME="TOC128" HREF="gettext_7.html#SEC128">7.9.5 Informative output</A>
+<LI><A NAME="TOC124" HREF="gettext_9.html#SEC124">9.8.1 Input file location</A>
+<LI><A NAME="TOC125" HREF="gettext_9.html#SEC125">9.8.2 Output file location</A>
+<LI><A NAME="TOC126" HREF="gettext_9.html#SEC126">9.8.3 Message selection</A>
+<LI><A NAME="TOC127" HREF="gettext_9.html#SEC127">9.8.4 Attribute manipulation</A>
+<LI><A NAME="TOC128" HREF="gettext_9.html#SEC128">9.8.5 Input file syntax</A>
+<LI><A NAME="TOC129" HREF="gettext_9.html#SEC129">9.8.6 Output details</A>
+<LI><A NAME="TOC130" HREF="gettext_9.html#SEC130">9.8.7 Informative output</A>
+</UL>
+<LI><A NAME="TOC131" HREF="gettext_9.html#SEC131">9.9 Invoking the <CODE>msgen</CODE> Program</A>
+<UL>
+<LI><A NAME="TOC132" HREF="gettext_9.html#SEC132">9.9.1 Input file location</A>
+<LI><A NAME="TOC133" HREF="gettext_9.html#SEC133">9.9.2 Output file location</A>
+<LI><A NAME="TOC134" HREF="gettext_9.html#SEC134">9.9.3 Input file syntax</A>
+<LI><A NAME="TOC135" HREF="gettext_9.html#SEC135">9.9.4 Output details</A>
+<LI><A NAME="TOC136" HREF="gettext_9.html#SEC136">9.9.5 Informative output</A>
+</UL>
+<LI><A NAME="TOC137" HREF="gettext_9.html#SEC137">9.10 Invoking the <CODE>msgexec</CODE> Program</A>
+<UL>
+<LI><A NAME="TOC138" HREF="gettext_9.html#SEC138">9.10.1 Input file location</A>
+<LI><A NAME="TOC139" HREF="gettext_9.html#SEC139">9.10.2 Input file syntax</A>
+<LI><A NAME="TOC140" HREF="gettext_9.html#SEC140">9.10.3 Informative output</A>
</UL>
-<LI><A NAME="TOC129" HREF="gettext_7.html#SEC129">7.10 Invoking the <CODE>msgexec</CODE> Program</A>
-<UL>
-<LI><A NAME="TOC130" HREF="gettext_7.html#SEC130">7.10.1 Input file location</A>
-<LI><A NAME="TOC131" HREF="gettext_7.html#SEC131">7.10.2 Input file syntax</A>
-<LI><A NAME="TOC132" HREF="gettext_7.html#SEC132">7.10.3 Informative output</A>
+<LI><A NAME="TOC141" HREF="gettext_9.html#SEC141">9.11 Writing your own programs that process PO files</A>
</UL>
-<LI><A NAME="TOC133" HREF="gettext_7.html#SEC133">7.11 Writing your own programs that process PO files</A>
-</UL>
-<LI><A NAME="TOC134" HREF="gettext_8.html#SEC134">8 Producing Binary MO Files</A>
-<UL>
-<LI><A NAME="TOC135" HREF="gettext_8.html#SEC135">8.1 Invoking the <CODE>msgfmt</CODE> Program</A>
+<LI><A NAME="TOC142" HREF="gettext_10.html#SEC142">10 Producing Binary MO Files</A>
<UL>
-<LI><A NAME="TOC136" HREF="gettext_8.html#SEC136">8.1.1 Input file location</A>
-<LI><A NAME="TOC137" HREF="gettext_8.html#SEC137">8.1.2 Operation mode</A>
-<LI><A NAME="TOC138" HREF="gettext_8.html#SEC138">8.1.3 Output file location</A>
-<LI><A NAME="TOC139" HREF="gettext_8.html#SEC139">8.1.4 Output file location in Java mode</A>
-<LI><A NAME="TOC140" HREF="gettext_8.html#SEC140">8.1.5 Output file location in C# mode</A>
-<LI><A NAME="TOC141" HREF="gettext_8.html#SEC141">8.1.6 Output file location in Tcl mode</A>
-<LI><A NAME="TOC142" HREF="gettext_8.html#SEC142">8.1.7 Input file syntax</A>
-<LI><A NAME="TOC143" HREF="gettext_8.html#SEC143">8.1.8 Input file interpretation</A>
-<LI><A NAME="TOC144" HREF="gettext_8.html#SEC144">8.1.9 Output details</A>
-<LI><A NAME="TOC145" HREF="gettext_8.html#SEC145">8.1.10 Informative output</A>
-</UL>
-<LI><A NAME="TOC146" HREF="gettext_8.html#SEC146">8.2 Invoking the <CODE>msgunfmt</CODE> Program</A>
+<LI><A NAME="TOC143" HREF="gettext_10.html#SEC143">10.1 Invoking the <CODE>msgfmt</CODE> Program</A>
<UL>
-<LI><A NAME="TOC147" HREF="gettext_8.html#SEC147">8.2.1 Operation mode</A>
-<LI><A NAME="TOC148" HREF="gettext_8.html#SEC148">8.2.2 Input file location</A>
-<LI><A NAME="TOC149" HREF="gettext_8.html#SEC149">8.2.3 Input file location in Java mode</A>
-<LI><A NAME="TOC150" HREF="gettext_8.html#SEC150">8.2.4 Input file location in C# mode</A>
-<LI><A NAME="TOC151" HREF="gettext_8.html#SEC151">8.2.5 Input file location in Tcl mode</A>
-<LI><A NAME="TOC152" HREF="gettext_8.html#SEC152">8.2.6 Output file location</A>
-<LI><A NAME="TOC153" HREF="gettext_8.html#SEC153">8.2.7 Output details</A>
-<LI><A NAME="TOC154" HREF="gettext_8.html#SEC154">8.2.8 Informative output</A>
-</UL>
-<LI><A NAME="TOC155" HREF="gettext_8.html#SEC155">8.3 The Format of GNU MO Files</A>
+<LI><A NAME="TOC144" HREF="gettext_10.html#SEC144">10.1.1 Input file location</A>
+<LI><A NAME="TOC145" HREF="gettext_10.html#SEC145">10.1.2 Operation mode</A>
+<LI><A NAME="TOC146" HREF="gettext_10.html#SEC146">10.1.3 Output file location</A>
+<LI><A NAME="TOC147" HREF="gettext_10.html#SEC147">10.1.4 Output file location in Java mode</A>
+<LI><A NAME="TOC148" HREF="gettext_10.html#SEC148">10.1.5 Output file location in C# mode</A>
+<LI><A NAME="TOC149" HREF="gettext_10.html#SEC149">10.1.6 Output file location in Tcl mode</A>
+<LI><A NAME="TOC150" HREF="gettext_10.html#SEC150">10.1.7 Input file syntax</A>
+<LI><A NAME="TOC151" HREF="gettext_10.html#SEC151">10.1.8 Input file interpretation</A>
+<LI><A NAME="TOC152" HREF="gettext_10.html#SEC152">10.1.9 Output details</A>
+<LI><A NAME="TOC153" HREF="gettext_10.html#SEC153">10.1.10 Informative output</A>
</UL>
-<LI><A NAME="TOC156" HREF="gettext_9.html#SEC156">9 The User's View</A>
+<LI><A NAME="TOC154" HREF="gettext_10.html#SEC154">10.2 Invoking the <CODE>msgunfmt</CODE> Program</A>
<UL>
-<LI><A NAME="TOC157" HREF="gettext_9.html#SEC157">9.1 The Current <TT>`ABOUT-NLS´</TT> Matrix</A>
-<LI><A NAME="TOC158" HREF="gettext_9.html#SEC158">9.2 Magic for Installers</A>
-<LI><A NAME="TOC159" HREF="gettext_9.html#SEC159">9.3 Magic for End Users</A>
+<LI><A NAME="TOC155" HREF="gettext_10.html#SEC155">10.2.1 Operation mode</A>
+<LI><A NAME="TOC156" HREF="gettext_10.html#SEC156">10.2.2 Input file location</A>
+<LI><A NAME="TOC157" HREF="gettext_10.html#SEC157">10.2.3 Input file location in Java mode</A>
+<LI><A NAME="TOC158" HREF="gettext_10.html#SEC158">10.2.4 Input file location in C# mode</A>
+<LI><A NAME="TOC159" HREF="gettext_10.html#SEC159">10.2.5 Input file location in Tcl mode</A>
+<LI><A NAME="TOC160" HREF="gettext_10.html#SEC160">10.2.6 Output file location</A>
+<LI><A NAME="TOC161" HREF="gettext_10.html#SEC161">10.2.7 Output details</A>
+<LI><A NAME="TOC162" HREF="gettext_10.html#SEC162">10.2.8 Informative output</A>
</UL>
-<LI><A NAME="TOC160" HREF="gettext_10.html#SEC160">10 The Programmer's View</A>
-<UL>
-<LI><A NAME="TOC161" HREF="gettext_10.html#SEC161">10.1 About <CODE>catgets</CODE></A>
-<UL>
-<LI><A NAME="TOC162" HREF="gettext_10.html#SEC162">10.1.1 The Interface</A>
-<LI><A NAME="TOC163" HREF="gettext_10.html#SEC163">10.1.2 Problems with the <CODE>catgets</CODE> Interface?!</A>
-</UL>
-<LI><A NAME="TOC164" HREF="gettext_10.html#SEC164">10.2 About <CODE>gettext</CODE></A>
-<UL>
-<LI><A NAME="TOC165" HREF="gettext_10.html#SEC165">10.2.1 The Interface</A>
-<LI><A NAME="TOC166" HREF="gettext_10.html#SEC166">10.2.2 Solving Ambiguities</A>
-<LI><A NAME="TOC167" HREF="gettext_10.html#SEC167">10.2.3 Locating Message Catalog Files</A>
-<LI><A NAME="TOC168" HREF="gettext_10.html#SEC168">10.2.4 How to specify the output character set <CODE>gettext</CODE> uses</A>
-<LI><A NAME="TOC169" HREF="gettext_10.html#SEC169">10.2.5 Additional functions for plural forms</A>
-<LI><A NAME="TOC170" HREF="gettext_10.html#SEC170">10.2.6 How to use <CODE>gettext</CODE> in GUI programs</A>
-<LI><A NAME="TOC171" HREF="gettext_10.html#SEC171">10.2.7 Optimization of the *gettext functions</A>
+<LI><A NAME="TOC163" HREF="gettext_10.html#SEC163">10.3 The Format of GNU MO Files</A>
</UL>
-<LI><A NAME="TOC172" HREF="gettext_10.html#SEC172">10.3 Comparing the Two Interfaces</A>
-<LI><A NAME="TOC173" HREF="gettext_10.html#SEC173">10.4 Using libintl.a in own programs</A>
-<LI><A NAME="TOC174" HREF="gettext_10.html#SEC174">10.5 Being a <CODE>gettext</CODE> grok</A>
-<LI><A NAME="TOC175" HREF="gettext_10.html#SEC175">10.6 Temporary Notes for the Programmers Chapter</A>
-<UL>
-<LI><A NAME="TOC176" HREF="gettext_10.html#SEC176">10.6.1 Temporary - Two Possible Implementations</A>
-<LI><A NAME="TOC177" HREF="gettext_10.html#SEC177">10.6.2 Temporary - About <CODE>catgets</CODE></A>
-<LI><A NAME="TOC178" HREF="gettext_10.html#SEC178">10.6.3 Temporary - Why a single implementation</A>
-<LI><A NAME="TOC179" HREF="gettext_10.html#SEC179">10.6.4 Temporary - Notes</A>
-</UL>
-</UL>
-<LI><A NAME="TOC180" HREF="gettext_11.html#SEC180">11 The Translator's View</A>
-<UL>
-<LI><A NAME="TOC181" HREF="gettext_11.html#SEC181">11.1 Introduction 0</A>
-<LI><A NAME="TOC182" HREF="gettext_11.html#SEC182">11.2 Introduction 1</A>
-<LI><A NAME="TOC183" HREF="gettext_11.html#SEC183">11.3 Discussions</A>
-<LI><A NAME="TOC184" HREF="gettext_11.html#SEC184">11.4 Organization</A>
-<UL>
-<LI><A NAME="TOC185" HREF="gettext_11.html#SEC185">11.4.1 Central Coordination</A>
-<LI><A NAME="TOC186" HREF="gettext_11.html#SEC186">11.4.2 National Teams</A>
-<UL>
-<LI><A NAME="TOC187" HREF="gettext_11.html#SEC187">11.4.2.1 Sub-Cultures</A>
-<LI><A NAME="TOC188" HREF="gettext_11.html#SEC188">11.4.2.2 Organizational Ideas</A>
-</UL>
-<LI><A NAME="TOC189" HREF="gettext_11.html#SEC189">11.4.3 Mailing Lists</A>
-</UL>
-<LI><A NAME="TOC190" HREF="gettext_11.html#SEC190">11.5 Information Flow</A>
-<LI><A NAME="TOC191" HREF="gettext_11.html#SEC191">11.6 Prioritizing messages: How to determine which messages to translate first</A>
-</UL>
-<LI><A NAME="TOC192" HREF="gettext_12.html#SEC192">12 The Maintainer's View</A>
-<UL>
-<LI><A NAME="TOC193" HREF="gettext_12.html#SEC193">12.1 Flat or Non-Flat Directory Structures</A>
-<LI><A NAME="TOC194" HREF="gettext_12.html#SEC194">12.2 Prerequisite Works</A>
-<LI><A NAME="TOC195" HREF="gettext_12.html#SEC195">12.3 Invoking the <CODE>gettextize</CODE> Program</A>
-<LI><A NAME="TOC196" HREF="gettext_12.html#SEC196">12.4 Files You Must Create or Alter</A>
-<UL>
-<LI><A NAME="TOC197" HREF="gettext_12.html#SEC197">12.4.1 <TT>`POTFILES.in´</TT> in <TT>`po/´</TT></A>
-<LI><A NAME="TOC198" HREF="gettext_12.html#SEC198">12.4.2 <TT>`LINGUAS´</TT> in <TT>`po/´</TT></A>
-<LI><A NAME="TOC199" HREF="gettext_12.html#SEC199">12.4.3 <TT>`Makevars´</TT> in <TT>`po/´</TT></A>
-<LI><A NAME="TOC200" HREF="gettext_12.html#SEC200">12.4.4 <TT>`configure.in´</TT> at top level</A>
-<LI><A NAME="TOC201" HREF="gettext_12.html#SEC201">12.4.5 <TT>`config.guess´</TT>, <TT>`config.sub´</TT> at top level</A>
-<LI><A NAME="TOC202" HREF="gettext_12.html#SEC202">12.4.6 <TT>`mkinstalldirs´</TT> at top level</A>
-<LI><A NAME="TOC203" HREF="gettext_12.html#SEC203">12.4.7 <TT>`aclocal.m4´</TT> at top level</A>
-<LI><A NAME="TOC204" HREF="gettext_12.html#SEC204">12.4.8 <TT>`acconfig.h´</TT> at top level</A>
-<LI><A NAME="TOC205" HREF="gettext_12.html#SEC205">12.4.9 <TT>`config.h.in´</TT> at top level</A>
-<LI><A NAME="TOC206" HREF="gettext_12.html#SEC206">12.4.10 <TT>`Makefile.in´</TT> at top level</A>
-<LI><A NAME="TOC207" HREF="gettext_12.html#SEC207">12.4.11 <TT>`Makefile.in´</TT> in <TT>`src/´</TT></A>
-<LI><A NAME="TOC208" HREF="gettext_12.html#SEC208">12.4.12 <TT>`gettext.h´</TT> in <TT>`lib/´</TT></A>
-</UL>
-<LI><A NAME="TOC209" HREF="gettext_12.html#SEC209">12.5 Autoconf macros for use in <TT>`configure.in´</TT></A>
-<UL>
-<LI><A NAME="TOC210" HREF="gettext_12.html#SEC210">12.5.1 AM_GNU_GETTEXT in <TT>`gettext.m4´</TT></A>
-<LI><A NAME="TOC211" HREF="gettext_12.html#SEC211">12.5.2 AM_GNU_GETTEXT_VERSION in <TT>`gettext.m4´</TT></A>
-<LI><A NAME="TOC212" HREF="gettext_12.html#SEC212">12.5.3 AM_PO_SUBDIRS in <TT>`po.m4´</TT></A>
-<LI><A NAME="TOC213" HREF="gettext_12.html#SEC213">12.5.4 AM_ICONV in <TT>`iconv.m4´</TT></A>
-</UL>
-<LI><A NAME="TOC214" HREF="gettext_12.html#SEC214">12.6 Integrating with CVS</A>
-<UL>
-<LI><A NAME="TOC215" HREF="gettext_12.html#SEC215">12.6.1 Avoiding version mismatch in distributed development</A>
-<LI><A NAME="TOC216" HREF="gettext_12.html#SEC216">12.6.2 Files to put under CVS version control</A>
-<LI><A NAME="TOC217" HREF="gettext_12.html#SEC217">12.6.3 Invoking the <CODE>autopoint</CODE> Program</A>
-<UL>
-<LI><A NAME="TOC218" HREF="gettext_12.html#SEC218">12.6.3.1 Options</A>
-<LI><A NAME="TOC219" HREF="gettext_12.html#SEC219">12.6.3.2 Informative output</A>
-</UL>
-</UL>
-<LI><A NAME="TOC220" HREF="gettext_12.html#SEC220">12.7 Creating a Distribution Tarball</A>
-</UL>
-<LI><A NAME="TOC221" HREF="gettext_13.html#SEC221">13 Other Programming Languages</A>
-<UL>
-<LI><A NAME="TOC222" HREF="gettext_13.html#SEC222">13.1 The Language Implementor's View</A>
-<LI><A NAME="TOC223" HREF="gettext_13.html#SEC223">13.2 The Programmer's View</A>
-<LI><A NAME="TOC224" HREF="gettext_13.html#SEC224">13.3 The Translator's View</A>
-<UL>
-<LI><A NAME="TOC225" HREF="gettext_13.html#SEC225">13.3.1 C Format Strings</A>
-<LI><A NAME="TOC226" HREF="gettext_13.html#SEC226">13.3.2 Objective C Format Strings</A>
-<LI><A NAME="TOC227" HREF="gettext_13.html#SEC227">13.3.3 Shell Format Strings</A>
-<LI><A NAME="TOC228" HREF="gettext_13.html#SEC228">13.3.4 Python Format Strings</A>
-<LI><A NAME="TOC229" HREF="gettext_13.html#SEC229">13.3.5 Lisp Format Strings</A>
-<LI><A NAME="TOC230" HREF="gettext_13.html#SEC230">13.3.6 Emacs Lisp Format Strings</A>
-<LI><A NAME="TOC231" HREF="gettext_13.html#SEC231">13.3.7 librep Format Strings</A>
-<LI><A NAME="TOC232" HREF="gettext_13.html#SEC232">13.3.8 Scheme Format Strings</A>
-<LI><A NAME="TOC233" HREF="gettext_13.html#SEC233">13.3.9 Smalltalk Format Strings</A>
-<LI><A NAME="TOC234" HREF="gettext_13.html#SEC234">13.3.10 Java Format Strings</A>
-<LI><A NAME="TOC235" HREF="gettext_13.html#SEC235">13.3.11 C# Format Strings</A>
-<LI><A NAME="TOC236" HREF="gettext_13.html#SEC236">13.3.12 awk Format Strings</A>
-<LI><A NAME="TOC237" HREF="gettext_13.html#SEC237">13.3.13 Object Pascal Format Strings</A>
-<LI><A NAME="TOC238" HREF="gettext_13.html#SEC238">13.3.14 YCP Format Strings</A>
-<LI><A NAME="TOC239" HREF="gettext_13.html#SEC239">13.3.15 Tcl Format Strings</A>
-<LI><A NAME="TOC240" HREF="gettext_13.html#SEC240">13.3.16 Perl Format Strings</A>
-<LI><A NAME="TOC241" HREF="gettext_13.html#SEC241">13.3.17 PHP Format Strings</A>
-<LI><A NAME="TOC242" HREF="gettext_13.html#SEC242">13.3.18 GCC internal Format Strings</A>
-<LI><A NAME="TOC243" HREF="gettext_13.html#SEC243">13.3.19 Qt Format Strings</A>
-</UL>
-<LI><A NAME="TOC244" HREF="gettext_13.html#SEC244">13.4 The Maintainer's View</A>
-<LI><A NAME="TOC245" HREF="gettext_13.html#SEC245">13.5 Individual Programming Languages</A>
-<UL>
-<LI><A NAME="TOC246" HREF="gettext_13.html#SEC246">13.5.1 C, C++, Objective C</A>
-<LI><A NAME="TOC247" HREF="gettext_13.html#SEC247">13.5.2 sh - Shell Script</A>
-<UL>
-<LI><A NAME="TOC248" HREF="gettext_13.html#SEC248">13.5.2.1 Preparing Shell Scripts for Internationalization</A>
-<LI><A NAME="TOC249" HREF="gettext_13.html#SEC249">13.5.2.2 Contents of <CODE>gettext.sh</CODE></A>
-<LI><A NAME="TOC250" HREF="gettext_13.html#SEC250">13.5.2.3 Invoking the <CODE>gettext</CODE> program</A>
-<LI><A NAME="TOC251" HREF="gettext_13.html#SEC251">13.5.2.4 Invoking the <CODE>ngettext</CODE> program</A>
-<LI><A NAME="TOC252" HREF="gettext_13.html#SEC252">13.5.2.5 Invoking the <CODE>envsubst</CODE> program</A>
-<LI><A NAME="TOC253" HREF="gettext_13.html#SEC253">13.5.2.6 Invoking the <CODE>eval_gettext</CODE> function</A>
-<LI><A NAME="TOC254" HREF="gettext_13.html#SEC254">13.5.2.7 Invoking the <CODE>eval_ngettext</CODE> function</A>
-</UL>
-<LI><A NAME="TOC255" HREF="gettext_13.html#SEC255">13.5.3 bash - Bourne-Again Shell Script</A>
-<LI><A NAME="TOC256" HREF="gettext_13.html#SEC256">13.5.4 Python</A>
-<LI><A NAME="TOC257" HREF="gettext_13.html#SEC257">13.5.5 GNU clisp - Common Lisp</A>
-<LI><A NAME="TOC258" HREF="gettext_13.html#SEC258">13.5.6 GNU clisp C sources</A>
-<LI><A NAME="TOC259" HREF="gettext_13.html#SEC259">13.5.7 Emacs Lisp</A>
-<LI><A NAME="TOC260" HREF="gettext_13.html#SEC260">13.5.8 librep</A>
-<LI><A NAME="TOC261" HREF="gettext_13.html#SEC261">13.5.9 GNU guile - Scheme</A>
-<LI><A NAME="TOC262" HREF="gettext_13.html#SEC262">13.5.10 GNU Smalltalk</A>
-<LI><A NAME="TOC263" HREF="gettext_13.html#SEC263">13.5.11 Java</A>
-<LI><A NAME="TOC264" HREF="gettext_13.html#SEC264">13.5.12 C#</A>
-<LI><A NAME="TOC265" HREF="gettext_13.html#SEC265">13.5.13 GNU awk</A>
-<LI><A NAME="TOC266" HREF="gettext_13.html#SEC266">13.5.14 Pascal - Free Pascal Compiler</A>
-<LI><A NAME="TOC267" HREF="gettext_13.html#SEC267">13.5.15 wxWindows library</A>
-<LI><A NAME="TOC268" HREF="gettext_13.html#SEC268">13.5.16 YCP - YaST2 scripting language</A>
-<LI><A NAME="TOC269" HREF="gettext_13.html#SEC269">13.5.17 Tcl - Tk's scripting language</A>
-<LI><A NAME="TOC270" HREF="gettext_13.html#SEC270">13.5.18 Perl</A>
-<UL>
-<LI><A NAME="TOC271" HREF="gettext_13.html#SEC271">13.5.18.1 General Problems Parsing Perl Code</A>
-<LI><A NAME="TOC272" HREF="gettext_13.html#SEC272">13.5.18.2 Which keywords will xgettext look for?</A>
-<LI><A NAME="TOC273" HREF="gettext_13.html#SEC273">13.5.18.3 How to Extract Hash Keys</A>
-<LI><A NAME="TOC274" HREF="gettext_13.html#SEC274">13.5.18.4 What are Strings And Quote-like Expressions?</A>
-<LI><A NAME="TOC275" HREF="gettext_13.html#SEC275">13.5.18.5 Invalid Uses Of String Interpolation</A>
-<LI><A NAME="TOC276" HREF="gettext_13.html#SEC276">13.5.18.6 Valid Uses Of String Interpolation</A>
-<LI><A NAME="TOC277" HREF="gettext_13.html#SEC277">13.5.18.7 When To Use Parentheses</A>
-<LI><A NAME="TOC278" HREF="gettext_13.html#SEC278">13.5.18.8 How To Grok with Long Lines</A>
-<LI><A NAME="TOC279" HREF="gettext_13.html#SEC279">13.5.18.9 Bugs, Pitfalls, And Things That Do Not Work</A>
-</UL>
-<LI><A NAME="TOC280" HREF="gettext_13.html#SEC280">13.5.19 PHP Hypertext Preprocessor</A>
-<LI><A NAME="TOC281" HREF="gettext_13.html#SEC281">13.5.20 Pike</A>
-<LI><A NAME="TOC282" HREF="gettext_13.html#SEC282">13.5.21 GNU Compiler Collection sources</A>
-</UL>
-<LI><A NAME="TOC283" HREF="gettext_13.html#SEC283">13.6 Internationalizable Data</A>
-<UL>
-<LI><A NAME="TOC284" HREF="gettext_13.html#SEC284">13.6.1 POT - Portable Object Template</A>
-<LI><A NAME="TOC285" HREF="gettext_13.html#SEC285">13.6.2 Resource String Table</A>
-<LI><A NAME="TOC286" HREF="gettext_13.html#SEC286">13.6.3 Glade - GNOME user interface description</A>
-</UL>
-</UL>
-<LI><A NAME="TOC287" HREF="gettext_14.html#SEC287">14 Concluding Remarks</A>
-<UL>
-<LI><A NAME="TOC288" HREF="gettext_14.html#SEC288">14.1 History of GNU <CODE>gettext</CODE></A>
-<LI><A NAME="TOC289" HREF="gettext_14.html#SEC289">14.2 Related Readings</A>
-</UL>
-<LI><A NAME="TOC290" HREF="gettext_15.html#SEC290">A Language Codes</A>
-<LI><A NAME="TOC291" HREF="gettext_16.html#SEC291">B Country Codes</A>
-<LI><A NAME="TOC292" HREF="gettext_17.html#SEC292">Program Index</A>
-<LI><A NAME="TOC293" HREF="gettext_18.html#SEC293">Option Index</A>
-<LI><A NAME="TOC294" HREF="gettext_19.html#SEC294">Variable Index</A>
-<LI><A NAME="TOC295" HREF="gettext_20.html#SEC295">PO Mode Index</A>
-<LI><A NAME="TOC296" HREF="gettext_21.html#SEC296">Autoconf Macro Index</A>
-<LI><A NAME="TOC297" HREF="gettext_22.html#SEC297">General Index</A>
+<LI><A NAME="TOC164" HREF="gettext_11.html#SEC164">11 The Programmer's View</A>
+<UL>
+<LI><A NAME="TOC165" HREF="gettext_11.html#SEC165">11.1 About <CODE>catgets</CODE></A>
+<UL>
+<LI><A NAME="TOC166" HREF="gettext_11.html#SEC166">11.1.1 The Interface</A>
+<LI><A NAME="TOC167" HREF="gettext_11.html#SEC167">11.1.2 Problems with the <CODE>catgets</CODE> Interface?!</A>
+</UL>
+<LI><A NAME="TOC168" HREF="gettext_11.html#SEC168">11.2 About <CODE>gettext</CODE></A>
+<UL>
+<LI><A NAME="TOC169" HREF="gettext_11.html#SEC169">11.2.1 The Interface</A>
+<LI><A NAME="TOC170" HREF="gettext_11.html#SEC170">11.2.2 Solving Ambiguities</A>
+<LI><A NAME="TOC171" HREF="gettext_11.html#SEC171">11.2.3 Locating Message Catalog Files</A>
+<LI><A NAME="TOC172" HREF="gettext_11.html#SEC172">11.2.4 How to specify the output character set <CODE>gettext</CODE> uses</A>
+<LI><A NAME="TOC173" HREF="gettext_11.html#SEC173">11.2.5 Using contexts for solving ambiguities</A>
+<LI><A NAME="TOC174" HREF="gettext_11.html#SEC174">11.2.6 Additional functions for plural forms</A>
+<LI><A NAME="TOC175" HREF="gettext_11.html#SEC175">11.2.7 Optimization of the *gettext functions</A>
+</UL>
+<LI><A NAME="TOC176" HREF="gettext_11.html#SEC176">11.3 Comparing the Two Interfaces</A>
+<LI><A NAME="TOC177" HREF="gettext_11.html#SEC177">11.4 Using libintl.a in own programs</A>
+<LI><A NAME="TOC178" HREF="gettext_11.html#SEC178">11.5 Being a <CODE>gettext</CODE> grok</A>
+<LI><A NAME="TOC179" HREF="gettext_11.html#SEC179">11.6 Temporary Notes for the Programmers Chapter</A>
+<UL>
+<LI><A NAME="TOC180" HREF="gettext_11.html#SEC180">11.6.1 Temporary - Two Possible Implementations</A>
+<LI><A NAME="TOC181" HREF="gettext_11.html#SEC181">11.6.2 Temporary - About <CODE>catgets</CODE></A>
+<LI><A NAME="TOC182" HREF="gettext_11.html#SEC182">11.6.3 Temporary - Why a single implementation</A>
+<LI><A NAME="TOC183" HREF="gettext_11.html#SEC183">11.6.4 Temporary - Notes</A>
+</UL>
+</UL>
+<LI><A NAME="TOC184" HREF="gettext_12.html#SEC184">12 The Translator's View</A>
+<UL>
+<LI><A NAME="TOC185" HREF="gettext_12.html#SEC185">12.1 Introduction 0</A>
+<LI><A NAME="TOC186" HREF="gettext_12.html#SEC186">12.2 Introduction 1</A>
+<LI><A NAME="TOC187" HREF="gettext_12.html#SEC187">12.3 Discussions</A>
+<LI><A NAME="TOC188" HREF="gettext_12.html#SEC188">12.4 Organization</A>
+<UL>
+<LI><A NAME="TOC189" HREF="gettext_12.html#SEC189">12.4.1 Central Coordination</A>
+<LI><A NAME="TOC190" HREF="gettext_12.html#SEC190">12.4.2 National Teams</A>
+<UL>
+<LI><A NAME="TOC191" HREF="gettext_12.html#SEC191">12.4.2.1 Sub-Cultures</A>
+<LI><A NAME="TOC192" HREF="gettext_12.html#SEC192">12.4.2.2 Organizational Ideas</A>
+</UL>
+<LI><A NAME="TOC193" HREF="gettext_12.html#SEC193">12.4.3 Mailing Lists</A>
+</UL>
+<LI><A NAME="TOC194" HREF="gettext_12.html#SEC194">12.5 Information Flow</A>
+<LI><A NAME="TOC195" HREF="gettext_12.html#SEC195">12.6 Prioritizing messages: How to determine which messages to translate first</A>
+</UL>
+<LI><A NAME="TOC196" HREF="gettext_13.html#SEC196">13 The Maintainer's View</A>
+<UL>
+<LI><A NAME="TOC197" HREF="gettext_13.html#SEC197">13.1 Flat or Non-Flat Directory Structures</A>
+<LI><A NAME="TOC198" HREF="gettext_13.html#SEC198">13.2 Prerequisite Works</A>
+<LI><A NAME="TOC199" HREF="gettext_13.html#SEC199">13.3 Invoking the <CODE>gettextize</CODE> Program</A>
+<LI><A NAME="TOC200" HREF="gettext_13.html#SEC200">13.4 Files You Must Create or Alter</A>
+<UL>
+<LI><A NAME="TOC201" HREF="gettext_13.html#SEC201">13.4.1 <TT>‘POTFILES.in’</TT> in <TT>‘po/’</TT></A>
+<LI><A NAME="TOC202" HREF="gettext_13.html#SEC202">13.4.2 <TT>‘LINGUAS’</TT> in <TT>‘po/’</TT></A>
+<LI><A NAME="TOC203" HREF="gettext_13.html#SEC203">13.4.3 <TT>‘Makevars’</TT> in <TT>‘po/’</TT></A>
+<LI><A NAME="TOC204" HREF="gettext_13.html#SEC204">13.4.4 Extending <TT>‘Makefile’</TT> in <TT>‘po/’</TT></A>
+<LI><A NAME="TOC205" HREF="gettext_13.html#SEC205">13.4.5 <TT>‘configure.in’</TT> at top level</A>
+<LI><A NAME="TOC206" HREF="gettext_13.html#SEC206">13.4.6 <TT>‘config.guess’</TT>, <TT>‘config.sub’</TT> at top level</A>
+<LI><A NAME="TOC207" HREF="gettext_13.html#SEC207">13.4.7 <TT>‘mkinstalldirs’</TT> at top level</A>
+<LI><A NAME="TOC208" HREF="gettext_13.html#SEC208">13.4.8 <TT>‘aclocal.m4’</TT> at top level</A>
+<LI><A NAME="TOC209" HREF="gettext_13.html#SEC209">13.4.9 <TT>‘acconfig.h’</TT> at top level</A>
+<LI><A NAME="TOC210" HREF="gettext_13.html#SEC210">13.4.10 <TT>‘config.h.in’</TT> at top level</A>
+<LI><A NAME="TOC211" HREF="gettext_13.html#SEC211">13.4.11 <TT>‘Makefile.in’</TT> at top level</A>
+<LI><A NAME="TOC212" HREF="gettext_13.html#SEC212">13.4.12 <TT>‘Makefile.in’</TT> in <TT>‘src/’</TT></A>
+<LI><A NAME="TOC213" HREF="gettext_13.html#SEC213">13.4.13 <TT>‘gettext.h’</TT> in <TT>‘lib/’</TT></A>
+</UL>
+<LI><A NAME="TOC214" HREF="gettext_13.html#SEC214">13.5 Autoconf macros for use in <TT>‘configure.in’</TT></A>
+<UL>
+<LI><A NAME="TOC215" HREF="gettext_13.html#SEC215">13.5.1 AM_GNU_GETTEXT in <TT>‘gettext.m4’</TT></A>
+<LI><A NAME="TOC216" HREF="gettext_13.html#SEC216">13.5.2 AM_GNU_GETTEXT_VERSION in <TT>‘gettext.m4’</TT></A>
+<LI><A NAME="TOC217" HREF="gettext_13.html#SEC217">13.5.3 AM_PO_SUBDIRS in <TT>‘po.m4’</TT></A>
+<LI><A NAME="TOC218" HREF="gettext_13.html#SEC218">13.5.4 AM_ICONV in <TT>‘iconv.m4’</TT></A>
+</UL>
+<LI><A NAME="TOC219" HREF="gettext_13.html#SEC219">13.6 Integrating with CVS</A>
+<UL>
+<LI><A NAME="TOC220" HREF="gettext_13.html#SEC220">13.6.1 Avoiding version mismatch in distributed development</A>
+<LI><A NAME="TOC221" HREF="gettext_13.html#SEC221">13.6.2 Files to put under CVS version control</A>
+<LI><A NAME="TOC222" HREF="gettext_13.html#SEC222">13.6.3 Invoking the <CODE>autopoint</CODE> Program</A>
+<UL>
+<LI><A NAME="TOC223" HREF="gettext_13.html#SEC223">13.6.3.1 Options</A>
+<LI><A NAME="TOC224" HREF="gettext_13.html#SEC224">13.6.3.2 Informative output</A>
+</UL>
+</UL>
+<LI><A NAME="TOC225" HREF="gettext_13.html#SEC225">13.7 Creating a Distribution Tarball</A>
+</UL>
+<LI><A NAME="TOC226" HREF="gettext_14.html#SEC226">14 The Installer's and Distributor's View</A>
+<LI><A NAME="TOC227" HREF="gettext_15.html#SEC227">15 Other Programming Languages</A>
+<UL>
+<LI><A NAME="TOC228" HREF="gettext_15.html#SEC228">15.1 The Language Implementor's View</A>
+<LI><A NAME="TOC229" HREF="gettext_15.html#SEC229">15.2 The Programmer's View</A>
+<LI><A NAME="TOC230" HREF="gettext_15.html#SEC230">15.3 The Translator's View</A>
+<UL>
+<LI><A NAME="TOC231" HREF="gettext_15.html#SEC231">15.3.1 C Format Strings</A>
+<LI><A NAME="TOC232" HREF="gettext_15.html#SEC232">15.3.2 Objective C Format Strings</A>
+<LI><A NAME="TOC233" HREF="gettext_15.html#SEC233">15.3.3 Shell Format Strings</A>
+<LI><A NAME="TOC234" HREF="gettext_15.html#SEC234">15.3.4 Python Format Strings</A>
+<LI><A NAME="TOC235" HREF="gettext_15.html#SEC235">15.3.5 Lisp Format Strings</A>
+<LI><A NAME="TOC236" HREF="gettext_15.html#SEC236">15.3.6 Emacs Lisp Format Strings</A>
+<LI><A NAME="TOC237" HREF="gettext_15.html#SEC237">15.3.7 librep Format Strings</A>
+<LI><A NAME="TOC238" HREF="gettext_15.html#SEC238">15.3.8 Scheme Format Strings</A>
+<LI><A NAME="TOC239" HREF="gettext_15.html#SEC239">15.3.9 Smalltalk Format Strings</A>
+<LI><A NAME="TOC240" HREF="gettext_15.html#SEC240">15.3.10 Java Format Strings</A>
+<LI><A NAME="TOC241" HREF="gettext_15.html#SEC241">15.3.11 C# Format Strings</A>
+<LI><A NAME="TOC242" HREF="gettext_15.html#SEC242">15.3.12 awk Format Strings</A>
+<LI><A NAME="TOC243" HREF="gettext_15.html#SEC243">15.3.13 Object Pascal Format Strings</A>
+<LI><A NAME="TOC244" HREF="gettext_15.html#SEC244">15.3.14 YCP Format Strings</A>
+<LI><A NAME="TOC245" HREF="gettext_15.html#SEC245">15.3.15 Tcl Format Strings</A>
+<LI><A NAME="TOC246" HREF="gettext_15.html#SEC246">15.3.16 Perl Format Strings</A>
+<LI><A NAME="TOC247" HREF="gettext_15.html#SEC247">15.3.17 PHP Format Strings</A>
+<LI><A NAME="TOC248" HREF="gettext_15.html#SEC248">15.3.18 GCC internal Format Strings</A>
+<LI><A NAME="TOC249" HREF="gettext_15.html#SEC249">15.3.19 Qt Format Strings</A>
+<LI><A NAME="TOC250" HREF="gettext_15.html#SEC250">15.3.20 Boost Format Strings</A>
+</UL>
+<LI><A NAME="TOC251" HREF="gettext_15.html#SEC251">15.4 The Maintainer's View</A>
+<LI><A NAME="TOC252" HREF="gettext_15.html#SEC252">15.5 Individual Programming Languages</A>
+<UL>
+<LI><A NAME="TOC253" HREF="gettext_15.html#SEC253">15.5.1 C, C++, Objective C</A>
+<LI><A NAME="TOC254" HREF="gettext_15.html#SEC254">15.5.2 sh - Shell Script</A>
+<UL>
+<LI><A NAME="TOC255" HREF="gettext_15.html#SEC255">15.5.2.1 Preparing Shell Scripts for Internationalization</A>
+<LI><A NAME="TOC256" HREF="gettext_15.html#SEC256">15.5.2.2 Contents of <CODE>gettext.sh</CODE></A>
+<LI><A NAME="TOC257" HREF="gettext_15.html#SEC257">15.5.2.3 Invoking the <CODE>gettext</CODE> program</A>
+<LI><A NAME="TOC258" HREF="gettext_15.html#SEC258">15.5.2.4 Invoking the <CODE>ngettext</CODE> program</A>
+<LI><A NAME="TOC259" HREF="gettext_15.html#SEC259">15.5.2.5 Invoking the <CODE>envsubst</CODE> program</A>
+<LI><A NAME="TOC260" HREF="gettext_15.html#SEC260">15.5.2.6 Invoking the <CODE>eval_gettext</CODE> function</A>
+<LI><A NAME="TOC261" HREF="gettext_15.html#SEC261">15.5.2.7 Invoking the <CODE>eval_ngettext</CODE> function</A>
+</UL>
+<LI><A NAME="TOC262" HREF="gettext_15.html#SEC262">15.5.3 bash - Bourne-Again Shell Script</A>
+<LI><A NAME="TOC263" HREF="gettext_15.html#SEC263">15.5.4 Python</A>
+<LI><A NAME="TOC264" HREF="gettext_15.html#SEC264">15.5.5 GNU clisp - Common Lisp</A>
+<LI><A NAME="TOC265" HREF="gettext_15.html#SEC265">15.5.6 GNU clisp C sources</A>
+<LI><A NAME="TOC266" HREF="gettext_15.html#SEC266">15.5.7 Emacs Lisp</A>
+<LI><A NAME="TOC267" HREF="gettext_15.html#SEC267">15.5.8 librep</A>
+<LI><A NAME="TOC268" HREF="gettext_15.html#SEC268">15.5.9 GNU guile - Scheme</A>
+<LI><A NAME="TOC269" HREF="gettext_15.html#SEC269">15.5.10 GNU Smalltalk</A>
+<LI><A NAME="TOC270" HREF="gettext_15.html#SEC270">15.5.11 Java</A>
+<LI><A NAME="TOC271" HREF="gettext_15.html#SEC271">15.5.12 C#</A>
+<LI><A NAME="TOC272" HREF="gettext_15.html#SEC272">15.5.13 GNU awk</A>
+<LI><A NAME="TOC273" HREF="gettext_15.html#SEC273">15.5.14 Pascal - Free Pascal Compiler</A>
+<LI><A NAME="TOC274" HREF="gettext_15.html#SEC274">15.5.15 wxWidgets library</A>
+<LI><A NAME="TOC275" HREF="gettext_15.html#SEC275">15.5.16 YCP - YaST2 scripting language</A>
+<LI><A NAME="TOC276" HREF="gettext_15.html#SEC276">15.5.17 Tcl - Tk's scripting language</A>
+<LI><A NAME="TOC277" HREF="gettext_15.html#SEC277">15.5.18 Perl</A>
+<UL>
+<LI><A NAME="TOC278" HREF="gettext_15.html#SEC278">15.5.18.1 General Problems Parsing Perl Code</A>
+<LI><A NAME="TOC279" HREF="gettext_15.html#SEC279">15.5.18.2 Which keywords will xgettext look for?</A>
+<LI><A NAME="TOC280" HREF="gettext_15.html#SEC280">15.5.18.3 How to Extract Hash Keys</A>
+<LI><A NAME="TOC281" HREF="gettext_15.html#SEC281">15.5.18.4 What are Strings And Quote-like Expressions?</A>
+<LI><A NAME="TOC282" HREF="gettext_15.html#SEC282">15.5.18.5 Invalid Uses Of String Interpolation</A>
+<LI><A NAME="TOC283" HREF="gettext_15.html#SEC283">15.5.18.6 Valid Uses Of String Interpolation</A>
+<LI><A NAME="TOC284" HREF="gettext_15.html#SEC284">15.5.18.7 When To Use Parentheses</A>
+<LI><A NAME="TOC285" HREF="gettext_15.html#SEC285">15.5.18.8 How To Grok with Long Lines</A>
+<LI><A NAME="TOC286" HREF="gettext_15.html#SEC286">15.5.18.9 Bugs, Pitfalls, And Things That Do Not Work</A>
+</UL>
+<LI><A NAME="TOC287" HREF="gettext_15.html#SEC287">15.5.19 PHP Hypertext Preprocessor</A>
+<LI><A NAME="TOC288" HREF="gettext_15.html#SEC288">15.5.20 Pike</A>
+<LI><A NAME="TOC289" HREF="gettext_15.html#SEC289">15.5.21 GNU Compiler Collection sources</A>
+</UL>
+<LI><A NAME="TOC290" HREF="gettext_15.html#SEC290">15.6 Internationalizable Data</A>
+<UL>
+<LI><A NAME="TOC291" HREF="gettext_15.html#SEC291">15.6.1 POT - Portable Object Template</A>
+<LI><A NAME="TOC292" HREF="gettext_15.html#SEC292">15.6.2 Resource String Table</A>
+<LI><A NAME="TOC293" HREF="gettext_15.html#SEC293">15.6.3 Glade - GNOME user interface description</A>
+</UL>
+</UL>
+<LI><A NAME="TOC294" HREF="gettext_16.html#SEC294">16 Concluding Remarks</A>
+<UL>
+<LI><A NAME="TOC295" HREF="gettext_16.html#SEC295">16.1 History of GNU <CODE>gettext</CODE></A>
+<LI><A NAME="TOC296" HREF="gettext_16.html#SEC296">16.2 Related Readings</A>
+</UL>
+<LI><A NAME="TOC297" HREF="gettext_17.html#SEC297">A Language Codes</A>
+<LI><A NAME="TOC298" HREF="gettext_18.html#SEC298">B Country Codes</A>
+<LI><A NAME="TOC299" HREF="gettext_19.html#SEC299">C Licenses</A>
+<UL>
+<LI><A NAME="TOC300" HREF="gettext_19.html#SEC300">C.1 GNU GENERAL PUBLIC LICENSE</A>
+<UL>
+<LI><A NAME="TOC301" HREF="gettext_19.html#SEC301">Preamble</A>
+<LI><A NAME="TOC302" HREF="gettext_19.html#SEC302">Appendix: How to Apply These Terms to Your New Programs</A>
+</UL>
+<LI><A NAME="TOC303" HREF="gettext_19.html#SEC303">C.2 GNU LESSER GENERAL PUBLIC LICENSE</A>
+<UL>
+<LI><A NAME="TOC304" HREF="gettext_19.html#SEC304">Preamble</A>
+<LI><A NAME="TOC305" HREF="gettext_19.html#SEC305">How to Apply These Terms to Your New Libraries</A>
+</UL>
+<LI><A NAME="TOC306" HREF="gettext_19.html#SEC306">C.3 GNU Free Documentation License</A>
+<UL>
+<LI><A NAME="TOC307" HREF="gettext_19.html#SEC307">ADDENDUM: How to use this License for your documents</A>
+</UL>
+</UL>
+<LI><A NAME="TOC308" HREF="gettext_20.html#SEC308">Program Index</A>
+<LI><A NAME="TOC309" HREF="gettext_21.html#SEC309">Option Index</A>
+<LI><A NAME="TOC310" HREF="gettext_22.html#SEC310">Variable Index</A>
+<LI><A NAME="TOC311" HREF="gettext_23.html#SEC311">PO Mode Index</A>
+<LI><A NAME="TOC312" HREF="gettext_24.html#SEC312">Autoconf Macro Index</A>
+<LI><A NAME="TOC313" HREF="gettext_25.html#SEC313">General Index</A>
</UL>
<P><HR><P>
-This document was generated on 11 April 2005 using the
+This document was generated on 20 July 2006 using the
<A HREF="http://wwwinfo.cern.ch/dis/texi2html/">texi2html</A>
-translator version 1.52a.</P>
+translator version 1.52b.</P>
</BODY>
</HTML>
-@set UPDATED 8 March 2005
-@set UPDATED-MONTH March 2005
-@set EDITION 0.14.4
-@set VERSION 0.14.4
+@set UPDATED 30 June 2006
+@set UPDATED-MONTH June 2006
+@set EDITION 0.15
+@set VERSION 0.15
-# Makefile.in generated by automake 1.9.5 from Makefile.am.
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
# @configure_input@
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
pkgdatadir = $(datadir)/@PACKAGE@
pkglibdir = $(libdir)/@PACKAGE@
pkgincludedir = $(includedir)/@PACKAGE@
-top_builddir = ../..
+top_builddir = ..
am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
INSTALL = @INSTALL@
install_sh_DATA = $(install_sh) -c -m 644
NORMAL_UNINSTALL = :
PRE_UNINSTALL = :
POST_UNINSTALL = :
-build_triplet = @build@
-host_triplet = @host@
-subdir = examples/po
+subdir = po
DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in
ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
-am__aclocal_m4_deps = $(top_srcdir)/../m4/fixautomake.m4 \
- $(top_srcdir)/../m4/libtool.m4 \
- $(top_srcdir)/../autoconf-lib-link/m4/lib-ld.m4 \
- $(top_srcdir)/../autoconf-lib-link/m4/lib-link.m4 \
- $(top_srcdir)/../autoconf-lib-link/m4/lib-prefix.m4 \
- $(top_srcdir)/../gettext-runtime/m4/ansi-c++.m4 \
- $(top_srcdir)/../gettext-runtime/m4/codeset.m4 \
- $(top_srcdir)/../gettext-runtime/m4/gettext.m4 \
- $(top_srcdir)/../gettext-runtime/m4/glibc2.m4 \
- $(top_srcdir)/../gettext-runtime/m4/glibc21.m4 \
- $(top_srcdir)/../gettext-runtime/m4/iconv.m4 \
- $(top_srcdir)/../gettext-runtime/m4/intdiv0.m4 \
- $(top_srcdir)/../gettext-runtime/m4/intmax.m4 \
- $(top_srcdir)/../gettext-runtime/m4/inttypes-pri.m4 \
- $(top_srcdir)/../gettext-runtime/m4/inttypes.m4 \
- $(top_srcdir)/../gettext-runtime/m4/inttypes_h.m4 \
- $(top_srcdir)/../gettext-runtime/m4/lcmessage.m4 \
- $(top_srcdir)/../gettext-runtime/m4/lock.m4 \
- $(top_srcdir)/../gettext-runtime/m4/longdouble.m4 \
- $(top_srcdir)/../gettext-runtime/m4/longlong.m4 \
- $(top_srcdir)/../gettext-runtime/m4/nls.m4 \
- $(top_srcdir)/../gettext-runtime/m4/po.m4 \
- $(top_srcdir)/../gettext-runtime/m4/printf-posix.m4 \
- $(top_srcdir)/../gettext-runtime/m4/progtest.m4 \
- $(top_srcdir)/../gettext-runtime/m4/signed.m4 \
- $(top_srcdir)/../gettext-runtime/m4/size_max.m4 \
- $(top_srcdir)/../gettext-runtime/m4/stdint_h.m4 \
- $(top_srcdir)/../gettext-runtime/m4/uintmax_t.m4 \
- $(top_srcdir)/../gettext-runtime/m4/ulonglong.m4 \
- $(top_srcdir)/../gettext-runtime/m4/visibility.m4 \
- $(top_srcdir)/../gettext-runtime/m4/wchar_t.m4 \
- $(top_srcdir)/../gettext-runtime/m4/wint_t.m4 \
- $(top_srcdir)/../gettext-runtime/m4/xsize.m4 \
- $(top_srcdir)/m4/alloca.m4 $(top_srcdir)/m4/allocsa.m4 \
- $(top_srcdir)/m4/backupfile.m4 $(top_srcdir)/m4/byteswap.m4 \
- $(top_srcdir)/m4/canonicalize.m4 $(top_srcdir)/m4/csharp.m4 \
- $(top_srcdir)/m4/csharpcomp.m4 $(top_srcdir)/m4/csharpexec.m4 \
- $(top_srcdir)/m4/eaccess.m4 $(top_srcdir)/m4/eealloc.m4 \
- $(top_srcdir)/m4/error.m4 $(top_srcdir)/m4/exitfail.m4 \
- $(top_srcdir)/m4/extensions.m4 $(top_srcdir)/m4/fnmatch.m4 \
- $(top_srcdir)/m4/gcj.m4 $(top_srcdir)/m4/getline.m4 \
- $(top_srcdir)/m4/getndelim2.m4 $(top_srcdir)/m4/getopt.m4 \
- $(top_srcdir)/m4/hard-locale.m4 $(top_srcdir)/m4/hostname.m4 \
- $(top_srcdir)/m4/java.m4 $(top_srcdir)/m4/javacomp.m4 \
- $(top_srcdir)/m4/javaexec.m4 $(top_srcdir)/m4/libgrep.m4 \
- $(top_srcdir)/m4/locale-fr.m4 $(top_srcdir)/m4/mbrtowc.m4 \
- $(top_srcdir)/m4/mbstate_t.m4 $(top_srcdir)/m4/mbswidth.m4 \
- $(top_srcdir)/m4/memchr.m4 $(top_srcdir)/m4/mkdtemp.m4 \
- $(top_srcdir)/m4/onceonly.m4 $(top_srcdir)/m4/pathmax.m4 \
- $(top_srcdir)/m4/quote.m4 $(top_srcdir)/m4/quotearg.m4 \
- $(top_srcdir)/m4/readlink.m4 $(top_srcdir)/m4/regex.m4 \
- $(top_srcdir)/m4/relocatable.m4 $(top_srcdir)/m4/restrict.m4 \
- $(top_srcdir)/m4/setenv.m4 $(top_srcdir)/m4/setlocale.m4 \
- $(top_srcdir)/m4/sig_atomic_t.m4 $(top_srcdir)/m4/siginfo.m4 \
- $(top_srcdir)/m4/signalblocking.m4 $(top_srcdir)/m4/ssize_t.m4 \
- $(top_srcdir)/m4/stdbool.m4 $(top_srcdir)/m4/stpncpy.m4 \
- $(top_srcdir)/m4/strdup.m4 $(top_srcdir)/m4/strerror.m4 \
- $(top_srcdir)/m4/strtol.m4 $(top_srcdir)/m4/strtoul.m4 \
- $(top_srcdir)/m4/tmpdir.m4 $(top_srcdir)/m4/unionwait.m4 \
- $(top_srcdir)/m4/unlocked-io.m4 $(top_srcdir)/m4/xreadlink.m4 \
+am__aclocal_m4_deps = $(top_srcdir)/../../m4/fixautomake.m4 \
+ $(top_srcdir)/../../gettext-runtime/m4/nls.m4 \
+ $(top_srcdir)/../../gettext-runtime/m4/po.m4 \
+ $(top_srcdir)/../../gettext-runtime/m4/progtest.m4 \
$(top_srcdir)/configure.ac
am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
$(ACLOCAL_M4)
-mkinstalldirs = $(SHELL) $(top_srcdir)/../build-aux/mkinstalldirs
-CONFIG_HEADER = $(top_builddir)/config.h
+mkinstalldirs = $(SHELL) $(top_srcdir)/../../build-aux/mkinstalldirs
CONFIG_CLEAN_FILES =
SOURCES =
DIST_SOURCES =
DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
ACLOCAL = @ACLOCAL@
-ALLOCA = @ALLOCA@
-ALLOCA_H = @ALLOCA_H@
-AMDEP_FALSE = @AMDEP_FALSE@
-AMDEP_TRUE = @AMDEP_TRUE@
AMTAR = @AMTAR@
-AR = @AR@
-AS = @AS@
AUTOCONF = @AUTOCONF@
AUTOHEADER = @AUTOHEADER@
AUTOMAKE = @AUTOMAKE@
AWK = @AWK@
-BUILDCSHARP = @BUILDCSHARP@
-BUILDJAVA = @BUILDJAVA@
-BUILDJAVAEXE = @BUILDJAVAEXE@
-BUILD_INCLUDED_LIBINTL = @BUILD_INCLUDED_LIBINTL@
-BYTESWAP_H = @BYTESWAP_H@
-CATOBJEXT = @CATOBJEXT@
-CC = @CC@
-CCDEPMODE = @CCDEPMODE@
-CFLAGS = @CFLAGS@
-CFLAG_VISIBILITY = @CFLAG_VISIBILITY@
-CLASSPATH = @CLASSPATH@
-CLASSPATH_SEPARATOR = @CLASSPATH_SEPARATOR@
-CPP = @CPP@
-CPPFLAGS = @CPPFLAGS@
-CROSS_COMPILING = @CROSS_COMPILING@
-CSHARP_CHOICE = @CSHARP_CHOICE@
-CXX = @CXX@
-CXXCPP = @CXXCPP@
-CXXDEPMODE = @CXXDEPMODE@
-CXXFLAGS = @CXXFLAGS@
CYGPATH_W = @CYGPATH_W@
-DATADIRNAME = @DATADIRNAME@
DEFS = @DEFS@
-DEPDIR = @DEPDIR@
-DLLTOOL = @DLLTOOL@
-DVIPS = @DVIPS@
-ECHO = @ECHO@
ECHO_C = @ECHO_C@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
-EGREP = @EGREP@
-EMACS = @EMACS@
-EMACSLOADPATH = @EMACSLOADPATH@
-EXEEXT = @EXEEXT@
-F77 = @F77@
-FFLAGS = @FFLAGS@
-FNMATCH_H = @FNMATCH_H@
-GCJ = @GCJ@
-GCJFLAGS = @GCJFLAGS@
-GENCAT = @GENCAT@
-GETOPT_H = @GETOPT_H@
-GLIBC2 = @GLIBC2@
-GLIBC21 = @GLIBC21@
GMSGFMT = @GMSGFMT@
-HAVE_ASPRINTF = @HAVE_ASPRINTF@
-HAVE_CSC = @HAVE_CSC@
-HAVE_CSCC = @HAVE_CSCC@
-HAVE_CSCC_IN_PATH = @HAVE_CSCC_IN_PATH@
-HAVE_CSC_IN_PATH = @HAVE_CSC_IN_PATH@
-HAVE_GCJ = @HAVE_GCJ@
-HAVE_GCJ_C = @HAVE_GCJ_C@
-HAVE_GCJ_IN_PATH = @HAVE_GCJ_IN_PATH@
-HAVE_GIJ = @HAVE_GIJ@
-HAVE_GIJ_IN_PATH = @HAVE_GIJ_IN_PATH@
-HAVE_ILRUN = @HAVE_ILRUN@
-HAVE_ILRUN_IN_PATH = @HAVE_ILRUN_IN_PATH@
-HAVE_JAVA = @HAVE_JAVA@
-HAVE_JAVAC = @HAVE_JAVAC@
-HAVE_JAVAC_IN_PATH = @HAVE_JAVAC_IN_PATH@
-HAVE_JAVA_IN_PATH = @HAVE_JAVA_IN_PATH@
-HAVE_JIKES = @HAVE_JIKES@
-HAVE_JIKES_IN_PATH = @HAVE_JIKES_IN_PATH@
-HAVE_JRE = @HAVE_JRE@
-HAVE_JRE_IN_PATH = @HAVE_JRE_IN_PATH@
-HAVE_JVIEW = @HAVE_JVIEW@
-HAVE_JVIEW_IN_PATH = @HAVE_JVIEW_IN_PATH@
-HAVE_LIBEXPAT = @HAVE_LIBEXPAT@
-HAVE_MCS = @HAVE_MCS@
-HAVE_MCS_IN_PATH = @HAVE_MCS_IN_PATH@
-HAVE_MONO = @HAVE_MONO@
-HAVE_MONO_IN_PATH = @HAVE_MONO_IN_PATH@
-HAVE_POSIX_PRINTF = @HAVE_POSIX_PRINTF@
-HAVE_SNPRINTF = @HAVE_SNPRINTF@
-HAVE_VISIBILITY = @HAVE_VISIBILITY@
-HAVE_WPRINTF = @HAVE_WPRINTF@
-HAVE__BOOL = @HAVE__BOOL@
+GMSGFMT_015 = @GMSGFMT_015@
INSTALL_DATA = @INSTALL_DATA@
INSTALL_PROGRAM = @INSTALL_PROGRAM@
INSTALL_SCRIPT = @INSTALL_SCRIPT@
INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
-INSTOBJEXT = @INSTOBJEXT@
-INTLBISON = @INTLBISON@
-INTLLIBS = @INTLLIBS@
-INTLOBJS = @INTLOBJS@
-INTL_LIBTOOL_SUFFIX_PREFIX = @INTL_LIBTOOL_SUFFIX_PREFIX@
-INTL_MACOSX_LIBS = @INTL_MACOSX_LIBS@
-JAR = @JAR@
-JAVA = @JAVA@
-JAVAC = @JAVAC@
-JAVA_CHOICE = @JAVA_CHOICE@
-LDFLAGS = @LDFLAGS@
-LIBEXPAT = @LIBEXPAT@
-LIBGREPOBJS = @LIBGREPOBJS@
-LIBICONV = @LIBICONV@
-LIBINTL = @LIBINTL@
-LIBMULTITHREAD = @LIBMULTITHREAD@
LIBOBJS = @LIBOBJS@
-LIBPTH = @LIBPTH@
LIBS = @LIBS@
-LIBTHREAD = @LIBTHREAD@
-LIBTOOL = @LIBTOOL@
-LN_S = @LN_S@
-LOCALE_FR = @LOCALE_FR@
-LOCALE_FR_UTF8 = @LOCALE_FR_UTF8@
-LTLIBEXPAT = @LTLIBEXPAT@
-LTLIBICONV = @LTLIBICONV@
-LTLIBINTL = @LTLIBINTL@
-LTLIBMULTITHREAD = @LTLIBMULTITHREAD@
LTLIBOBJS = @LTLIBOBJS@
-LTLIBPTH = @LTLIBPTH@
-LTLIBTHREAD = @LTLIBTHREAD@
-LTNOUNDEF = @LTNOUNDEF@
MAKEINFO = @MAKEINFO@
-MINGW_FALSE = @MINGW_FALSE@
-MINGW_TRUE = @MINGW_TRUE@
-MKINSTALLDIRS = @MKINSTALLDIRS@
-MONO_PATH = @MONO_PATH@
-MONO_PATH_SEPARATOR = @MONO_PATH_SEPARATOR@
MSGFMT = @MSGFMT@
+MSGFMT_015 = @MSGFMT_015@
MSGMERGE = msgmerge
-OBJDUMP = @OBJDUMP@
-OBJEXT = @OBJEXT@
PACKAGE = @PACKAGE@
PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
PACKAGE_NAME = @PACKAGE_NAME@
PACKAGE_TARNAME = @PACKAGE_TARNAME@
PACKAGE_VERSION = @PACKAGE_VERSION@
PATH_SEPARATOR = @PATH_SEPARATOR@
-PERL = @PERL@
-POSUB = @POSUB@
-RANLIB = @RANLIB@
-RELOCATABLE = @RELOCATABLE@
-RELOCATABLE_VIA_LD_FALSE = @RELOCATABLE_VIA_LD_FALSE@
-RELOCATABLE_VIA_LD_TRUE = @RELOCATABLE_VIA_LD_TRUE@
SET_MAKE = @SET_MAKE@
-SET_RELOCATABLE = @SET_RELOCATABLE@
SHELL = @SHELL@
-STDBOOL_H = @STDBOOL_H@
STRIP = @STRIP@
-TESTCSHARP = @TESTCSHARP@
-TESTJAVA = @TESTJAVA@
-TESTLIBASPRINTF = @TESTLIBASPRINTF@
-TEXI2PDF = @TEXI2PDF@
-USE_INCLUDED_LIBINTL = @USE_INCLUDED_LIBINTL@
USE_NLS = @USE_NLS@
VERSION = @VERSION@
XGETTEXT = @XGETTEXT@
-YACC = @YACC@
-ac_ct_AR = @ac_ct_AR@
-ac_ct_AS = @ac_ct_AS@
-ac_ct_CC = @ac_ct_CC@
-ac_ct_CXX = @ac_ct_CXX@
-ac_ct_DLLTOOL = @ac_ct_DLLTOOL@
-ac_ct_F77 = @ac_ct_F77@
-ac_ct_OBJDUMP = @ac_ct_OBJDUMP@
-ac_ct_RANLIB = @ac_ct_RANLIB@
-ac_ct_STRIP = @ac_ct_STRIP@
+XGETTEXT_015 = @XGETTEXT_015@
aclocaldir = @aclocaldir@
-am__fastdepCC_FALSE = @am__fastdepCC_FALSE@
-am__fastdepCC_TRUE = @am__fastdepCC_TRUE@
-am__fastdepCXX_FALSE = @am__fastdepCXX_FALSE@
-am__fastdepCXX_TRUE = @am__fastdepCXX_TRUE@
-am__include = @am__include@
am__leading_dot = @am__leading_dot@
-am__quote = @am__quote@
am__tar = @am__tar@
am__untar = @am__untar@
bindir = @bindir@
-build = @build@
build_alias = @build_alias@
-build_cpu = @build_cpu@
-build_os = @build_os@
-build_vendor = @build_vendor@
datadir = @datadir@
+datarootdir = @datarootdir@
docdir = @docdir@
+dvidir = @dvidir@
exec_prefix = @exec_prefix@
-host = @host@
host_alias = @host_alias@
-host_cpu = @host_cpu@
-host_os = @host_os@
-host_vendor = @host_vendor@
+htmldir = @htmldir@
includedir = @includedir@
infodir = @infodir@
install_sh = @install_sh@
libdir = @libdir@
libexecdir = @libexecdir@
-lispdir = @lispdir@
-localedir = $(datadir)/locale
+localedir = @localedir@
localstatedir = @localstatedir@
mandir = @mandir@
mkdir_p = @mkdir_p@
oldincludedir = @oldincludedir@
+pdfdir = @pdfdir@
prefix = @prefix@
program_transform_name = @program_transform_name@
+psdir = @psdir@
sbindir = @sbindir@
sharedstatedir = @sharedstatedir@
sysconfdir = @sysconfdir@
# List of files which contain translatable strings.
POTFILES = \
- examples/hello-c/hello.c \
- examples/hello-c-gnome/hello.c \
- examples/hello-c++/hello.cc \
- examples/hello-c++-qt/hello.cc \
- examples/hello-c++-kde/hello.cc \
- examples/hello-c++-kde/hellowindow.h \
- examples/hello-c++-kde/hellowindow.cc \
- examples/hello-c++-gnome/hello.cc \
- examples/hello-objc/hello.m \
- examples/hello-objc-gnustep/main.m \
- examples/hello-objc-gnustep/AppController.h \
- examples/hello-objc-gnustep/AppController.m \
- examples/hello-objc-gnustep/Hello.h \
- examples/hello-objc-gnustep/Hello.m \
- examples/hello-objc-gnome/hello.m \
- examples/hello-sh/hello.sh \
- examples/hello-python/hello.py.in \
- examples/hello-clisp/hello.lisp.in \
- examples/hello-librep/hello.jl.in \
- examples/hello-guile/hello.scm \
- examples/hello-smalltalk/hello.st.in \
- examples/hello-java/Hello.java \
- examples/hello-java-awt/Hello.java \
- examples/hello-java-swing/Hello.java \
- examples/hello-csharp/hello.cs \
- examples/hello-csharp-forms/hello.cs \
- examples/hello-gawk/hello.awk \
- examples/hello-pascal/hello.pas \
- examples/hello-ycp/hello.ycp \
- examples/hello-tcl/hello.tcl \
- examples/hello-tcl-tk/hello.tcl \
- examples/hello-perl/hello-1.pl.in \
- examples/hello-perl/hello-2.pl.in \
- examples/hello-php/hello.php
+ hello-c/hello.c \
+ hello-c-gnome/hello.c \
+ hello-c++/hello.cc \
+ hello-c++-qt/hello.cc \
+ hello-c++-kde/hello.cc \
+ hello-c++-kde/hellowindow.h \
+ hello-c++-kde/hellowindow.cc \
+ hello-c++-gnome/hello.cc \
+ hello-c++-wxwidgets/hello.cc \
+ hello-objc/hello.m \
+ hello-objc-gnustep/main.m \
+ hello-objc-gnustep/AppController.h \
+ hello-objc-gnustep/AppController.m \
+ hello-objc-gnustep/Hello.h \
+ hello-objc-gnustep/Hello.m \
+ hello-objc-gnome/hello.m \
+ hello-sh/hello.sh \
+ hello-python/hello.py.in \
+ hello-clisp/hello.lisp.in \
+ hello-librep/hello.jl.in \
+ hello-guile/hello.scm \
+ hello-smalltalk/hello.st.in \
+ hello-java/Hello.java \
+ hello-java-awt/Hello.java \
+ hello-java-swing/Hello.java \
+ hello-csharp/hello.cs \
+ hello-csharp-forms/hello.cs \
+ hello-gawk/hello.awk \
+ hello-pascal/hello.pas \
+ hello-ycp/hello.ycp \
+ hello-tcl/hello.tcl \
+ hello-tcl-tk/hello.tcl \
+ hello-perl/hello-1.pl.in \
+ hello-perl/hello-2.pl.in \
+ hello-php/hello.php
# List of small POT files.
hello-c++-qt.pot \
hello-c++-kde.pot \
hello-c++-gnome.pot \
+ hello-c++-wxwidgets.pot \
hello-objc.pot \
hello-objc-gnustep.pot \
hello-objc-gnome.pot \
DUMMYPOFILES = @DUMMYPOFILES@
SUFFIXES = .po .sed .sin .nop .po-update
MOSTLYCLEANFILES = remove-potcdate.sed stamp-poT core core.* \
- $(DOMAIN).po $(DOMAIN).1po $(DOMAIN).2po *.new.po *.o
+ *.stackdump $(DOMAIN).po $(DOMAIN).1po $(DOMAIN).2po *.new.po \
+ *.o
DISTCLEANFILES = $(SMALLPOTS)
MAINTAINERCLEANFILES = stamp-po
EXTRA_DIST = remove-potcdate.sin xsmallpot.sh mmsmallpo.sh LINGUAS \
../hello-c++-qt/po/$$lang.po \
../hello-c++-kde/po/$$lang.po \
../hello-c++-gnome/po/$$lang.po \
+ ../hello-c++-wxwidgets/po/$$lang.po \
../hello-objc/po/$$lang.po \
../hello-objc-gnustep/po/$$lang.po \
../hello-objc-gnome/po/$$lang.po \
exit 1;; \
esac; \
done; \
- echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnits examples/po/Makefile'; \
+ echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnits po/Makefile'; \
cd $(top_srcdir) && \
- $(AUTOMAKE) --gnits examples/po/Makefile
+ $(AUTOMAKE) --gnits po/Makefile
.PRECIOUS: Makefile
Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
@case '$?' in \
cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
$(ACLOCAL_M4): $(am__aclocal_m4_deps)
cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
-
-mostlyclean-libtool:
- -rm -f *.lo
-
-clean-libtool:
- -rm -rf .libs _libs
-
-distclean-libtool:
- -rm -f libtool
uninstall-info-am:
tags: TAGS
TAGS:
-test -z "$(MAINTAINERCLEANFILES)" || rm -f $(MAINTAINERCLEANFILES)
clean: clean-am
-clean-am: clean-generic clean-libtool mostlyclean-am
+clean-am: clean-generic mostlyclean-am
distclean: distclean-am
-rm -f Makefile
-distclean-am: clean-am distclean-generic distclean-libtool
+distclean-am: clean-am distclean-generic
dvi: dvi-am
mostlyclean: mostlyclean-am
-mostlyclean-am: mostlyclean-generic mostlyclean-libtool
+mostlyclean-am: mostlyclean-generic
pdf: pdf-am
uninstall-am: uninstall-info-am
.PHONY: all all-am all-local check check-am clean clean-generic \
- clean-libtool distclean distclean-generic distclean-libtool \
- distdir dvi dvi-am html html-am info info-am install \
- install-am install-data install-data-am install-exec \
- install-exec-am install-info install-info-am install-man \
- install-strip installcheck installcheck-am installdirs \
- maintainer-clean maintainer-clean-generic mostlyclean \
- mostlyclean-generic mostlyclean-libtool pdf pdf-am ps ps-am \
- uninstall uninstall-am uninstall-info-am
+ distclean distclean-generic distdir dvi dvi-am html html-am \
+ info info-am install install-am install-data install-data-am \
+ install-exec install-exec-am install-info install-info-am \
+ install-man install-strip installcheck installcheck-am \
+ installdirs maintainer-clean maintainer-clean-generic \
+ mostlyclean mostlyclean-generic pdf pdf-am ps ps-am uninstall \
+ uninstall-am uninstall-info-am
.sin.sed:
hello-c++-gnome.pot : $(POTFILES_DEPS)
$(SHELL) '$(srcdir)/xsmallpot.sh' '$(srcdir)' hello-c++-gnome
+hello-c++-wxwidgets.pot : $(POTFILES_DEPS)
+ $(SHELL) '$(srcdir)/xsmallpot.sh' '$(srcdir)' hello-c++-wxwidgets
+
hello-objc.pot : $(POTFILES_DEPS)
$(SHELL) '$(srcdir)/xsmallpot.sh' '$(srcdir)' hello-objc
../hello-c++-gnome/po/$(LL).po: hello-c++-gnome.pot $(LL).po
$(SHELL) mmsmallpo.sh hello-c++-gnome $(LL)
+../hello-c++-wxwidgets/po/$(LL).po: hello-c++-wxwidgets.pot $(LL).po
+ $(SHELL) mmsmallpo.sh hello-c++-wxwidgets $(LL)
+
../hello-objc/po/$(LL).po: hello-objc.pot $(LL).po
$(SHELL) mmsmallpo.sh hello-objc $(LL)
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:50+0200\n"
+"POT-Creation-Date: 2006-07-21 16:31+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:50+0200\n"
+"POT-Creation-Date: 2006-07-21 16:31+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:50+0200\n"
+"POT-Creation-Date: 2006-07-21 16:31+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:50+0200\n"
+"POT-Creation-Date: 2006-07-21 16:31+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:50+0200\n"
+"POT-Creation-Date: 2006-07-21 16:31+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:49+0200\n"
+"POT-Creation-Date: 2006-07-21 16:30+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:49+0200\n"
+"POT-Creation-Date: 2006-07-21 16:30+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:51+0200\n"
+"POT-Creation-Date: 2006-07-21 16:32+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:52+0200\n"
+"POT-Creation-Date: 2006-07-21 16:33+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:52+0200\n"
+"POT-Creation-Date: 2006-07-21 16:33+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:52+0200\n"
+"POT-Creation-Date: 2006-07-21 16:33+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:51+0200\n"
+"POT-Creation-Date: 2006-07-21 16:32+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:52+0200\n"
+"POT-Creation-Date: 2006-07-21 16:32+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:52+0200\n"
+"POT-Creation-Date: 2006-07-21 16:33+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:51+0200\n"
+"POT-Creation-Date: 2006-07-21 16:32+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:51+0200\n"
+"POT-Creation-Date: 2006-07-21 16:32+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:51+0200\n"
+"POT-Creation-Date: 2006-07-21 16:32+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:51+0200\n"
+"POT-Creation-Date: 2006-07-21 16:32+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:51+0200\n"
+"POT-Creation-Date: 2006-07-21 16:32+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:52+0200\n"
+"POT-Creation-Date: 2006-07-21 16:33+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:53+0200\n"
+"POT-Creation-Date: 2006-07-21 16:33+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:53+0200\n"
+"POT-Creation-Date: 2006-07-21 16:34+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:51+0200\n"
+"POT-Creation-Date: 2006-07-21 16:32+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:51+0200\n"
+"POT-Creation-Date: 2006-07-21 16:32+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:51+0200\n"
+"POT-Creation-Date: 2006-07-21 16:32+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:52+0200\n"
+"POT-Creation-Date: 2006-07-21 16:33+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:52+0200\n"
+"POT-Creation-Date: 2006-07-21 16:33+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2006-04-20 15:52+0200\n"
+"POT-Creation-Date: 2006-07-21 16:33+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH AUTOPOINT "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH AUTOPOINT "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
autopoint \- copies standard gettext infrastructure
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 2002-2005 Free Software Foundation, Inc.
+Copyright \(co 2002-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 2002-2005 Free Software Foundation, Inc.<br>
+Copyright 2002-2006 Free Software Foundation, Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
MERCHANTABILITY or FITNESS FOR A PARTICULAR
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH GETTEXTIZE "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH GETTEXTIZE "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
gettextize \- install or upgrade gettext infrastructure
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 1995-1998, 2000-2005 Free Software Foundation, Inc.
+Copyright \(co 1995-1998, 2000-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 1995-1998, 2000-2005 Free Software Foundation,
+Copyright 1995-1998, 2000-2006 Free Software Foundation,
Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGATTRIB "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH MSGATTRIB "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
msgattrib \- attribute matching and manipulation on message catalog
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 2001-2005 Free Software Foundation, Inc.
+Copyright \(co 2001-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 2001-2005 Free Software Foundation, Inc.<br>
+Copyright 2001-2006 Free Software Foundation, Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
MERCHANTABILITY or FITNESS FOR A PARTICULAR
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGCAT "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH MSGCAT "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
msgcat \- combines several message catalogs
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 2001-2005 Free Software Foundation, Inc.
+Copyright \(co 2001-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 2001-2005 Free Software Foundation, Inc.<br>
+Copyright 2001-2006 Free Software Foundation, Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
MERCHANTABILITY or FITNESS FOR A PARTICULAR
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGCMP "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH MSGCMP "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
msgcmp \- compare message catalog and template
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 1995-1998, 2000-2005 Free Software Foundation, Inc.
+Copyright \(co 1995-1998, 2000-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 1995-1998, 2000-2005 Free Software Foundation,
+Copyright 1995-1998, 2000-2006 Free Software Foundation,
Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGCOMM "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH MSGCOMM "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
msgcomm \- match two message catalogs
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 1995-1998, 2000-2005 Free Software Foundation, Inc.
+Copyright \(co 1995-1998, 2000-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 1995-1998, 2000-2005 Free Software Foundation,
+Copyright 1995-1998, 2000-2006 Free Software Foundation,
Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGCONV "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH MSGCONV "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
msgconv \- character set conversion for message catalog
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 2001-2005 Free Software Foundation, Inc.
+Copyright \(co 2001-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 2001-2005 Free Software Foundation, Inc.<br>
+Copyright 2001-2006 Free Software Foundation, Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
MERCHANTABILITY or FITNESS FOR A PARTICULAR
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGEN "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH MSGEN "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
msgen \- create English message catalog
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 2001-2005 Free Software Foundation, Inc.
+Copyright \(co 2001-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 2001-2005 Free Software Foundation, Inc.<br>
+Copyright 2001-2006 Free Software Foundation, Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
MERCHANTABILITY or FITNESS FOR A PARTICULAR
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGEXEC "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH MSGEXEC "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
msgexec \- process translations of message catalog
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 2001-2005 Free Software Foundation, Inc.
+Copyright \(co 2001-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 2001-2005 Free Software Foundation, Inc.<br>
+Copyright 2001-2006 Free Software Foundation, Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
MERCHANTABILITY or FITNESS FOR A PARTICULAR
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGFILTER "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH MSGFILTER "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
msgfilter \- edit translations of message catalog
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 2001-2005 Free Software Foundation, Inc.
+Copyright \(co 2001-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 2001-2005 Free Software Foundation, Inc.<br>
+Copyright 2001-2006 Free Software Foundation, Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
MERCHANTABILITY or FITNESS FOR A PARTICULAR
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGFMT "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH MSGFMT "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
msgfmt \- compile message catalog to binary format
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 1995-1998, 2000-2005 Free Software Foundation, Inc.
+Copyright \(co 1995-1998, 2000-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 1995-1998, 2000-2005 Free Software Foundation,
+Copyright 1995-1998, 2000-2006 Free Software Foundation,
Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGGREP "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH MSGGREP "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
msggrep \- pattern matching on message catalog
.SH SYNOPSIS
.SS "Message selection:"
.IP
[-N SOURCEFILE]... [-M DOMAINNAME]...
-[-K MSGID-PATTERN] [-T MSGSTR-PATTERN] [-C COMMENT-PATTERN]
+[-J MSGCTXT-PATTERN] [-K MSGID-PATTERN] [-T MSGSTR-PATTERN]
+[-C COMMENT-PATTERN] [-X EXTRACTED-COMMENT-PATTERN]
.PP
A message is selected if it comes from one of the specified source files,
or if it comes from one of the specified domains,
+or if \fB\-J\fR is given and its context (msgctxt) matches MSGCTXT-PATTERN,
or if \fB\-K\fR is given and its key (msgid or msgid_plural) matches MSGID-PATTERN,
or if \fB\-T\fR is given and its translation (msgstr) matches MSGSTR-PATTERN,
-or if \fB\-C\fR is given and the translator's comment matches COMMENT-PATTERN.
+or if \fB\-C\fR is given and the translator's comment matches COMMENT-PATTERN,
+or if \fB\-X\fR is given and the extracted comment matches EXTRACTED-COMMENT-PATTERN.
.PP
When more than one selection criterion is specified, the set of selected
messages is the union of the selected messages of each criterion.
-.SS "MSGID-PATTERN or MSGSTR-PATTERN or COMMENT-PATTERN syntax:"
+.PP
+MSGCTXT-PATTERN or MSGID-PATTERN or MSGSTR-PATTERN or COMMENT-PATTERN or
+EXTRACTED-COMMENT-PATTERN syntax:
.IP
[-E | \fB\-F]\fR [-e PATTERN | \fB\-f\fR FILE]...
.PP
\fB\-M\fR, \fB\-\-domain\fR=\fIDOMAINNAME\fR
select messages belonging to domain DOMAINNAME
.TP
+\fB\-J\fR, \fB\-\-msgctxt\fR
+start of patterns for the msgctxt
+.TP
\fB\-K\fR, \fB\-\-msgid\fR
start of patterns for the msgid
.TP
\fB\-C\fR, \fB\-\-comment\fR
start of patterns for the translator's comment
.TP
+\fB\-X\fR, \fB\-\-extracted\-comment\fR
+start of patterns for the extracted comment
+.TP
\fB\-E\fR, \fB\-\-extended\-regexp\fR
PATTERN is an extended regular expression
.TP
.TP
\fB\-i\fR, \fB\-\-ignore\-case\fR
ignore case distinctions
+.TP
+\fB\-v\fR, \fB\-\-invert\-match\fR
+output only the messages that do not match any
+selection criterion
.SS "Input file syntax:"
.TP
\fB\-P\fR, \fB\-\-properties\-input\fR
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 2001-2005 Free Software Foundation, Inc.
+Copyright \(co 2001-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
-[-N SOURCEFILE]... [-M DOMAINNAME]... [-K MSGID-PATTERN] [-T
-MSGSTR-PATTERN] [-C COMMENT-PATTERN]</td></table>
+[-N SOURCEFILE]... [-M DOMAINNAME]... [-J MSGCTXT-PATTERN]
+[-K MSGID-PATTERN] [-T MSGSTR-PATTERN] [-C COMMENT-PATTERN]
+[-X EXTRACTED-COMMENT-PATTERN]</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<td width="10%"></td><td width="90%">
A message is selected if it comes from one of the specified
source files, or if it comes from one of the specified
-domains, or if <b>-K</b> is given and its key (msgid or
-msgid_plural) matches MSGID-PATTERN, or if <b>-T</b> is
-given and its translation (msgstr) matches MSGSTR-PATTERN,
-or if <b>-C</b> is given and the translator's comment
-matches COMMENT-PATTERN.</td></table>
+domains, or if <b>-J</b> is given and its context (msgctxt)
+matches MSGCTXT-PATTERN, or if <b>-K</b> is given and its
+key (msgid or msgid_plural) matches MSGID-PATTERN, or if
+<b>-T</b> is given and its translation (msgstr) matches
+MSGSTR-PATTERN, or if <b>-C</b> is given and the
+translator's comment matches COMMENT-PATTERN, or if
+<b>-X</b> is given and the extracted comment matches
+EXTRACTED-COMMENT-PATTERN.</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
-<td width="4%"></td><td width="96%">
-<b>MSGID-PATTERN or MSGSTR-PATTERN or COMMENT-PATTERN
-syntax:</b></td></table>
+<td width="10%"></td><td width="90%">
+MSGCTXT-PATTERN or MSGID-PATTERN or MSGSTR-PATTERN or
+COMMENT-PATTERN or EXTRACTED-COMMENT-PATTERN
+syntax:</td></table>
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<td width="21%"></td><td width="79%">
select messages belonging to domain DOMAINNAME</td></table>
+<table width="100%" border=0 rules="none" frame="void"
+ cols="2" cellspacing="0" cellpadding="0">
+<tr valign="top" align="left">
+<td width="10%"></td><td width="90%">
+<b>-J</b>, <b>--msgctxt</b></td></table>
+
+<table width="100%" border=0 rules="none" frame="void"
+ cols="2" cellspacing="0" cellpadding="0">
+<tr valign="top" align="left">
+<td width="21%"></td><td width="79%">
+start of patterns for the msgctxt</td></table>
+
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
start of patterns for the translator's comment</td></table>
+<table width="100%" border=0 rules="none" frame="void"
+ cols="2" cellspacing="0" cellpadding="0">
+<tr valign="top" align="left">
+<td width="10%"></td><td width="90%">
+<b>-X</b>, <b>--extracted-comment</b></td></table>
+
+<table width="100%" border=0 rules="none" frame="void"
+ cols="2" cellspacing="0" cellpadding="0">
+<tr valign="top" align="left">
+<td width="21%"></td><td width="79%">
+start of patterns for the extracted comment</td></table>
+
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="21%"></td><td width="79%">
ignore case distinctions</td></table>
+<table width="100%" border=0 rules="none" frame="void"
+ cols="2" cellspacing="0" cellpadding="0">
+<tr valign="top" align="left">
+<td width="10%"></td><td width="90%">
+<b>-v</b>, <b>--invert-match</b></td></table>
+
+<table width="100%" border=0 rules="none" frame="void"
+ cols="2" cellspacing="0" cellpadding="0">
+<tr valign="top" align="left">
+<td width="21%"></td><td width="79%">
+output only the messages that do not match any selection
+criterion</td></table>
+
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 2001-2005 Free Software Foundation, Inc.<br>
+Copyright 2001-2006 Free Software Foundation, Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
MERCHANTABILITY or FITNESS FOR A PARTICULAR
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGINIT "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH MSGINIT "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
msginit \- initialize a message catalog
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 2001-2005 Free Software Foundation, Inc.
+Copyright \(co 2001-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 2001-2005 Free Software Foundation, Inc.<br>
+Copyright 2001-2006 Free Software Foundation, Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
MERCHANTABILITY or FITNESS FOR A PARTICULAR
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGMERGE "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH MSGMERGE "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
msgmerge \- merge message catalog and template
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 1995-1998, 2000-2005 Free Software Foundation, Inc.
+Copyright \(co 1995-1998, 2000-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 1995-1998, 2000-2005 Free Software Foundation,
+Copyright 1995-1998, 2000-2006 Free Software Foundation,
Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGUNFMT "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH MSGUNFMT "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
msgunfmt \- uncompile message catalog from binary format
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 1995-1998, 2000-2005 Free Software Foundation, Inc.
+Copyright \(co 1995-1998, 2000-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 1995-1998, 2000-2005 Free Software Foundation,
+Copyright 1995-1998, 2000-2006 Free Software Foundation,
Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH MSGUNIQ "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH MSGUNIQ "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
msguniq \- unify duplicate translations in message catalog
.SH SYNOPSIS
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 2001-2005 Free Software Foundation, Inc.
+Copyright \(co 2001-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 2001-2005 Free Software Foundation, Inc.<br>
+Copyright 2001-2006 Free Software Foundation, Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
MERCHANTABILITY or FITNESS FOR A PARTICULAR
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
-.TH XGETTEXT "1" "April 2005" "GNU gettext-tools 0.14.4" GNU
+.TH XGETTEXT "1" "July 2006" "GNU gettext-tools 0.15" GNU
.SH NAME
xgettext \- extract gettext strings from source
.SH SYNOPSIS
recognize Qt format strings
(only language C++)
.TP
+\fB\-\-boost\fR
+recognize Boost format strings
+(only language C++)
+.TP
\fB\-\-debug\fR
more detailed formatstring recognition result
.SS "Output details:"
.SH "REPORTING BUGS"
Report bugs to <bug-gnu-gettext@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 1995-1998, 2000-2005 Free Software Foundation, Inc.
+Copyright \(co 1995-1998, 2000-2006 Free Software Foundation, Inc.
.br
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
<td width="21%"></td><td width="79%">
recognize Qt format strings (only language C++)</td></table>
+<table width="100%" border=0 rules="none" frame="void"
+ cols="2" cellspacing="0" cellpadding="0">
+<tr valign="top" align="left">
+<td width="10%"></td><td width="90%">
+<b>--boost</b></td></table>
+
+<table width="100%" border=0 rules="none" frame="void"
+ cols="2" cellspacing="0" cellpadding="0">
+<tr valign="top" align="left">
+<td width="21%"></td><td width="79%">
+recognize Boost format strings (only language
+C++)</td></table>
+
<table width="100%" border=0 rules="none" frame="void"
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
cols="2" cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="10%"></td><td width="90%">
-Copyright 1995-1998, 2000-2005 Free Software Foundation,
+Copyright 1995-1998, 2000-2006 Free Software Foundation,
Inc.<br>
This is free software; see the source for copying
conditions. There is NO warranty; not even for
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
-"POT-Creation-Date: 2005-02-12 20:12+0100\n"
+"POT-Creation-Date: 2006-07-01 00:52+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n"
-#: lib/argmatch.c:137
+#: lib/argmatch.c:136
#, c-format
msgid "invalid argument %s for %s"
msgstr ""
-#: lib/argmatch.c:138
+#: lib/argmatch.c:137
#, c-format
msgid "ambiguous argument %s for %s"
msgstr ""
-#: lib/argmatch.c:157
+#: lib/argmatch.c:156
#, c-format
msgid "Valid arguments are:"
msgstr ""
msgid "write error"
msgstr ""
-#: lib/copy-file.c:65 src/file-list.c:56 src/msggrep.c:231 src/open-po.c:118
-#: src/read-mo.c:245 src/read-tcl.c:125 src/urlget.c:200 src/xgettext.c:1569
-#: src/xgettext.c:1582 src/xgettext.c:1592
+#: lib/copy-file.c:62 src/file-list.c:56 src/msggrep.c:238 src/open-po.c:122
+#: src/read-mo.c:245 src/read-tcl.c:125 src/urlget.c:198 src/xgettext.c:1754
+#: src/xgettext.c:1767 src/xgettext.c:1777
#, c-format
msgid "error while opening \"%s\" for reading"
msgstr ""
-#: lib/copy-file.c:72
+#: lib/copy-file.c:69
#, c-format
msgid "cannot open backup file \"%s\" for writing"
msgstr ""
-#: lib/copy-file.c:80 src/urlget.c:212
+#: lib/copy-file.c:77 src/urlget.c:210
#, c-format
msgid "error reading \"%s\""
msgstr ""
-#: lib/copy-file.c:85 lib/copy-file.c:89
+#: lib/copy-file.c:82 lib/copy-file.c:86
#, c-format
msgid "error writing \"%s\""
msgstr ""
-#: lib/copy-file.c:91 src/urlget.c:222
+#: lib/copy-file.c:88 src/urlget.c:220
#, c-format
msgid "error after reading \"%s\""
msgstr ""
-#: lib/csharpcomp.c:273 src/msginit.c:970 src/msginit.c:1037
-#: src/msginit.c:1195 src/msginit.c:1277 src/read-csharp.c:73
-#: src/read-java.c:71 src/read-resources.c:74 src/read-tcl.c:111
-#: src/write-resources.c:79
+#: lib/csharpcomp.c:282 lib/javaversion.c:77 src/msginit.c:773
+#: src/msginit.c:841 src/msginit.c:1000 src/msginit.c:1083
+#: src/read-csharp.c:73 src/read-java.c:71 src/read-resources.c:74
+#: src/read-tcl.c:111 src/write-resources.c:79
#, c-format
msgid "fdopen() failed"
msgstr ""
-#: lib/csharpcomp.c:526
+#: lib/csharpcomp.c:541
#, c-format
msgid "C# compiler not found, try installing pnet"
msgstr ""
-#: lib/csharpexec.c:251
+#: lib/csharpexec.c:346
#, c-format
msgid "C# virtual machine not found, try installing pnet"
msgstr ""
msgid "Unknown system error"
msgstr ""
-#: lib/execute.c:186 lib/execute.c:262 lib/execute.c:304 lib/pipe.c:231
-#: lib/pipe.c:349 lib/pipe.c:409 lib/wait-process.c:336 lib/wait-process.c:403
+#: lib/execute.c:183 lib/execute.c:259 lib/execute.c:301 lib/pipe.c:228
+#: lib/pipe.c:346 lib/pipe.c:406 lib/wait-process.c:336 lib/wait-process.c:403
#, c-format
msgid "%s subprocess failed"
msgstr ""
msgid "%s: option `-W %s' doesn't allow an argument\n"
msgstr ""
-#: lib/javacomp.c:467
+#: lib/javacomp.c:125 lib/javacomp.c:139 lib/javacomp.c:155
+#, c-format
+msgid "invalid source_version argument to compile_java_class"
+msgstr ""
+
+#: lib/javacomp.c:170 lib/javacomp.c:191
+#, c-format
+msgid "invalid target_version argument to compile_java_class"
+msgstr ""
+
+#: lib/javacomp.c:475 src/write-csharp.c:721 src/write-java.c:996
+#: src/write-java.c:1008
+#, c-format
+msgid "failed to create \"%s\""
+msgstr ""
+
+#: lib/javacomp.c:482 src/write-csharp.c:730 src/write-java.c:1017
+#: src/write-mo.c:819 src/write-po.c:1214 src/write-qt.c:752
+#: src/write-tcl.c:223
+#, c-format
+msgid "error while writing \"%s\" file"
+msgstr ""
+
+#: lib/javacomp.c:1797
#, c-format
msgid "Java compiler not found, try installing gcj or set $JAVAC"
msgstr ""
msgid "Java virtual machine not found, try installing gij or set $JAVA"
msgstr ""
-#: lib/obstack.c:438 lib/obstack.c:441 lib/xerror.c:51 lib/xmalloc.c:41
-#: lib/xsetenv.c:40 src/gettext-po.c:901 src/po-lex.c:89 src/po-lex.c:118
-#: src/x-glade.c:390
+#: lib/javaversion.c:85 src/msginit.c:781 src/msginit.c:849 src/msginit.c:1008
+#, c-format
+msgid "%s subprocess I/O error"
+msgstr ""
+
+#: lib/obstack.c:438 lib/obstack.c:441 lib/xmalloc.c:41 lib/xsetenv.c:40
+#: src/gettext-po.c:1140 src/msgl-check.c:450 src/po-lex.c:86 src/po-lex.c:105
+#: src/x-glade.c:406
#, c-format
msgid "memory exhausted"
msgstr ""
-#: lib/pipe.c:157 lib/pipe.c:160 lib/pipe.c:264 lib/pipe.c:267
+#: lib/pipe.c:154 lib/pipe.c:157 lib/pipe.c:261 lib/pipe.c:264
#, c-format
msgid "cannot create pipe"
msgstr ""
+#: lib/quotearg.c:239
+msgid "`"
+msgstr ""
+
+#: lib/quotearg.c:240
+msgid "'"
+msgstr ""
+
#: lib/w32spawn.h:48
#, c-format
msgid "DuplicateHandle failed with error code 0x%08x"
msgid "%s subprocess got fatal signal %d"
msgstr ""
-#: src/format.c:127
+#: src/format.c:149
#, c-format
msgid "'%s' is not a valid %s format string, unlike 'msgid'. Reason: %s"
msgstr ""
-#: src/format-awk.c:489 src/format-elisp.c:337 src/format-librep.c:301
+#: src/format-awk.c:489 src/format-boost.c:589 src/format-elisp.c:337
+#: src/format-gcc-internal.c:582 src/format-librep.c:301
#: src/format-pascal.c:390 src/format-perl.c:567 src/format-php.c:337
#: src/format-qt.c:132 src/format-tcl.c:376 src/format-ycp.c:133
#, c-format
"a format specification for argument %u, as in '%s', doesn't exist in 'msgid'"
msgstr ""
-#: src/format-awk.c:499 src/format-elisp.c:347 src/format-librep.c:311
+#: src/format-awk.c:499 src/format-boost.c:599 src/format-elisp.c:347
+#: src/format-gcc-internal.c:592 src/format-librep.c:311
#: src/format-pascal.c:400 src/format-perl.c:577 src/format-php.c:347
#: src/format-qt.c:131 src/format-tcl.c:386 src/format-ycp.c:132
#, c-format
msgid "a format specification for argument %u doesn't exist in '%s'"
msgstr ""
-#: src/format-awk.c:519 src/format-c.c:856 src/format-elisp.c:367
-#: src/format-gcc-internal.c:274 src/format-librep.c:331
-#: src/format-pascal.c:420 src/format-perl.c:597 src/format-php.c:367
-#: src/format-python.c:494 src/format-tcl.c:406
+#: src/format-awk.c:519 src/format-boost.c:619 src/format-c.c:873
+#: src/format-elisp.c:367 src/format-gcc-internal.c:612
+#: src/format-librep.c:331 src/format-pascal.c:420 src/format-perl.c:597
+#: src/format-php.c:367 src/format-python.c:494 src/format-tcl.c:406
#, c-format
msgid ""
"format specifications in 'msgid' and '%s' for argument %u are not the same"
msgstr ""
-#: src/format-c.c:176
+#: src/format-boost.c:427
+#, c-format
+msgid "The directive number %u starts with | but does not end with |."
+msgstr ""
+
+#: src/format-c.c:177
#, c-format
msgid ""
"In the directive number %u, the token after '<' is not the name of a format "
"specifier macro. The valid macro names are listed in ISO C 99 section 7.8.1."
msgstr ""
-#: src/format-c.c:563
+#: src/format-c.c:565
#, c-format
msgid "In the directive number %u, the token after '<' is not followed by '>'."
msgstr ""
-#: src/format-c.c:770
+#: src/format-c.c:779
#, c-format
msgid "The string refers to argument number %u but ignores argument number %u."
msgstr ""
-#: src/format-c.c:847 src/format-csharp.c:195 src/format-gcc-internal.c:265
-#: src/format-python.c:485
+#: src/format-c.c:864 src/format-csharp.c:195 src/format-python.c:485
#, c-format
msgid "number of format specifications in 'msgid' and '%s' does not match"
msgstr ""
msgid "The string contains a lone '}' after directive number %u."
msgstr ""
-#: src/format-gcc-internal.c:202
+#: src/format-gcc-internal.c:245
+#, c-format
+msgid "In the directive number %u, the flags combination is invalid."
+msgstr ""
+
+#: src/format-gcc-internal.c:276 src/format-gcc-internal.c:370
+#, c-format
+msgid "In the directive number %u, a precision is not allowed before '%c'."
+msgstr ""
+
+#: src/format-gcc-internal.c:314
+#, c-format
+msgid ""
+"In the directive number %u, the argument number for the precision must be "
+"equal to %u."
+msgstr ""
+
+#: src/format-gcc-internal.c:376
+#, c-format
+msgid "In the directive number %u, the precision specification is invalid."
+msgstr ""
+
+#: src/format-gcc-internal.c:424
#, c-format
msgid "In the directive number %u, flags are not allowed before '%c'."
msgstr ""
+#: src/format-gcc-internal.c:630
+#, c-format
+msgid "'msgid' uses %%m but '%s' doesn't"
+msgstr ""
+
+#: src/format-gcc-internal.c:633
+#, c-format
+msgid "'msgid' does not use %%m but '%s' uses %%m"
+msgstr ""
+
#: src/format-invalid.h:23
msgid "The string ends in the middle of a directive."
msgstr ""
"format specifications in 'msgid' and '%s' for argument {%u} are not the same"
msgstr ""
-#: src/format-lisp.c:2352 src/format-lisp.c:2364
+#: src/format-lisp.c:2352 src/format-lisp.c:2364 src/format-scheme.c:2378
+#: src/format-scheme.c:2390
#, c-format
msgid ""
"In the directive number %u, parameter %u is of type '%s' but a parameter of "
"type '%s' is expected."
msgstr ""
-#: src/format-lisp.c:2387
+#: src/format-lisp.c:2387 src/format-scheme.c:2413
#, c-format
msgid ""
"In the directive number %u, too many parameters are given; expected at most %"
msgstr[0] ""
msgstr[1] ""
-#: src/format-lisp.c:2502
+#: src/format-lisp.c:2502 src/format-scheme.c:2505
#, c-format
msgid "In the directive number %u, '%c' is not followed by a digit."
msgstr ""
-#: src/format-lisp.c:2700
+#: src/format-lisp.c:2700 src/format-scheme.c:2715
#, c-format
msgid "In the directive number %u, the argument %d is negative."
msgstr ""
msgstr ""
#: src/format-lisp.c:2792 src/format-lisp.c:3025 src/format-lisp.c:3131
-#: src/format-lisp.c:3180 src/format-lisp.c:3266
+#: src/format-lisp.c:3180 src/format-lisp.c:3266 src/format-scheme.c:2790
+#: src/format-scheme.c:3023 src/format-scheme.c:3129 src/format-scheme.c:3204
#, c-format
msgid "Found '~%c' without matching '~%c'."
msgstr ""
-#: src/format-lisp.c:2808
+#: src/format-lisp.c:2808 src/format-scheme.c:2806
#, c-format
msgid "In the directive number %u, both the @ and the : modifiers are given."
msgstr ""
-#: src/format-lisp.c:2906
+#: src/format-lisp.c:2906 src/format-scheme.c:2904
#, c-format
msgid ""
"In the directive number %u, '~:[' is not followed by two clauses, separated "
"by '~;'."
msgstr ""
-#: src/format-lisp.c:3214
+#: src/format-lisp.c:3214 src/format-scheme.c:3163
#, c-format
msgid "In the directive number %u, '~;' is used in an invalid position."
msgstr ""
-#: src/format-lisp.c:3300
+#: src/format-lisp.c:3300 src/format-scheme.c:3238
msgid "The string refers to some argument in incompatible ways."
msgstr ""
-#: src/format-lisp.c:3342
+#: src/format-lisp.c:3342 src/format-scheme.c:3280
#, c-format
msgid "format specifications in 'msgid' and '%s' are not equivalent"
msgstr ""
-#: src/format-lisp.c:3358
+#: src/format-lisp.c:3358 src/format-scheme.c:3296
#, c-format
msgid "format specifications in '%s' are not a subset of those in 'msgid'"
msgstr ""
"1 and 9."
msgstr ""
-#: src/gettext-po.c:80
+#: src/gettext-po.c:83
msgid "<unnamed>"
msgstr ""
-#: src/gettext-po.c:98 src/gettext-po.c:141 src/open-po.c:55
+#: src/gettext-po.c:101 src/gettext-po.c:145 src/gettext-po.c:189
+#: src/open-po.c:56
msgid "<stdin>"
msgstr ""
-#: src/hostname.c:182 src/msgattrib.c:311 src/msgcat.c:263 src/msgcmp.c:140
-#: src/msgcomm.c:260 src/msgconv.c:217 src/msgen.c:203 src/msgexec.c:177
-#: src/msgfilter.c:270 src/msgfmt.c:361 src/msggrep.c:373 src/msginit.c:268
-#: src/msgmerge.c:297 src/msgunfmt.c:246 src/msguniq.c:239 src/urlget.c:134
-#: src/xgettext.c:503
+#: src/hostname.c:180 src/msgattrib.c:313 src/msgcat.c:265 src/msgcmp.c:142
+#: src/msgcomm.c:262 src/msgconv.c:219 src/msgen.c:205 src/msgexec.c:176
+#: src/msgfilter.c:278 src/msgfmt.c:362 src/msggrep.c:392 src/msginit.c:252
+#: src/msgmerge.c:304 src/msgunfmt.c:248 src/msguniq.c:241
+#: src/recode-sr-latin.c:112 src/urlget.c:132 src/xgettext.c:515
#, c-format, no-wrap
msgid ""
"Copyright (C) %s Free Software Foundation, Inc.\n"
"warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n"
msgstr ""
-#: src/hostname.c:187 src/msgattrib.c:316 src/msgcat.c:268 src/msgcmp.c:145
-#: src/msgcomm.c:265 src/msgconv.c:222 src/msgen.c:208 src/msgexec.c:182
-#: src/msgfilter.c:275 src/msgfmt.c:366 src/msggrep.c:378 src/msginit.c:273
-#: src/msgmerge.c:302 src/msgunfmt.c:251 src/msguniq.c:244 src/urlget.c:139
-#: src/xgettext.c:508
+#: src/hostname.c:185 src/msgattrib.c:318 src/msgcat.c:270 src/msgcmp.c:147
+#: src/msgcomm.c:267 src/msgconv.c:224 src/msgen.c:210 src/msgexec.c:181
+#: src/msgfilter.c:283 src/msgfmt.c:367 src/msggrep.c:397 src/msginit.c:257
+#: src/msgmerge.c:309 src/msgunfmt.c:253 src/msguniq.c:246 src/urlget.c:137
+#: src/xgettext.c:520
#, c-format
msgid "Written by %s.\n"
msgstr ""
-#: src/hostname.c:197 src/msginit.c:283
+#. This is a proper name. See the gettext manual, section Names.
+#: src/hostname.c:185 src/msgattrib.c:318 src/msgcat.c:270 src/msgconv.c:224
+#: src/msgen.c:210 src/msgexec.c:181 src/msgfilter.c:283 src/msggrep.c:397
+#: src/msginit.c:257 src/msguniq.c:246 src/recode-sr-latin.c:122
+#: src/urlget.c:137
+msgid "Bruno Haible"
+msgstr ""
+
+#: src/hostname.c:195 src/msginit.c:267 src/recode-sr-latin.c:131
#, c-format
msgid "too many arguments"
msgstr ""
-#: src/hostname.c:210 src/msgattrib.c:372 src/msgcat.c:327 src/msgcmp.c:176
-#: src/msgcomm.c:333 src/msgconv.c:280 src/msgen.c:258 src/msgexec.c:234
-#: src/msgfilter.c:367 src/msgfmt.c:607 src/msggrep.c:467 src/msginit.c:361
-#: src/msgmerge.c:421 src/msgunfmt.c:406 src/msguniq.c:300 src/urlget.c:162
-#: src/xgettext.c:717
+#: src/hostname.c:208 src/msgattrib.c:374 src/msgcat.c:329 src/msgcmp.c:178
+#: src/msgcomm.c:335 src/msgconv.c:282 src/msgen.c:260 src/msgexec.c:233
+#: src/msgfilter.c:388 src/msgfmt.c:625 src/msggrep.c:488 src/msginit.c:341
+#: src/msgmerge.c:428 src/msgunfmt.c:408 src/msguniq.c:302
+#: src/recode-sr-latin.c:144 src/urlget.c:160 src/xgettext.c:736
#, c-format
msgid "Try `%s --help' for more information.\n"
msgstr ""
-#: src/hostname.c:214 src/msginit.c:365
-#, c-format
+#: src/hostname.c:212 src/msginit.c:345 src/recode-sr-latin.c:149
+#, c-format, no-wrap
msgid "Usage: %s [OPTION]\n"
msgstr ""
-#: src/hostname.c:218
+#: src/hostname.c:216
#, c-format
msgid "Print the machine's hostname.\n"
msgstr ""
-#: src/hostname.c:221
+#: src/hostname.c:219
#, c-format
msgid "Output format:\n"
msgstr ""
-#: src/hostname.c:223
+#: src/hostname.c:221
#, c-format
msgid " -s, --short short host name\n"
msgstr ""
-#: src/hostname.c:225
+#: src/hostname.c:223
#, c-format
msgid ""
" -f, --fqdn, --long long host name, includes fully qualified "
" name, and aliases\n"
msgstr ""
-#: src/hostname.c:228
+#: src/hostname.c:226
#, c-format
msgid " -i, --ip-address addresses for the hostname\n"
msgstr ""
-#: src/hostname.c:231 src/msgattrib.c:476 src/msgcat.c:425 src/msgcmp.c:219
-#: src/msgcomm.c:427 src/msgconv.c:356 src/msgen.c:331 src/msgexec.c:276
-#: src/msgfilter.c:453 src/msgfmt.c:729 src/msggrep.c:569 src/msginit.c:417
-#: src/msgmerge.c:536 src/msgunfmt.c:504 src/msguniq.c:389 src/urlget.c:176
-#: src/xgettext.c:863
-#, c-format
+#: src/hostname.c:229 src/msgattrib.c:478 src/msgcat.c:427 src/msgcmp.c:221
+#: src/msgcomm.c:429 src/msgconv.c:358 src/msgen.c:333 src/msgexec.c:275
+#: src/msgfilter.c:474 src/msgfmt.c:747 src/msggrep.c:598 src/msginit.c:397
+#: src/msgmerge.c:543 src/msgunfmt.c:506 src/msguniq.c:391
+#: src/recode-sr-latin.c:162 src/urlget.c:174 src/xgettext.c:886
+#, c-format, no-wrap
msgid "Informative output:\n"
msgstr ""
-#: src/hostname.c:233 src/msgattrib.c:478 src/msgcat.c:427 src/msgcmp.c:221
-#: src/msgcomm.c:429 src/msgconv.c:358 src/msgen.c:333 src/msgexec.c:278
-#: src/msgfilter.c:455 src/msgfmt.c:731 src/msggrep.c:571 src/msginit.c:419
-#: src/msgmerge.c:538 src/msgunfmt.c:506 src/msguniq.c:391 src/urlget.c:178
-#: src/xgettext.c:865
-#, c-format
+#: src/hostname.c:231 src/msgattrib.c:480 src/msgcat.c:429 src/msgcmp.c:223
+#: src/msgcomm.c:431 src/msgconv.c:360 src/msgen.c:335 src/msgexec.c:277
+#: src/msgfilter.c:476 src/msgfmt.c:749 src/msggrep.c:600 src/msginit.c:399
+#: src/msgmerge.c:545 src/msgunfmt.c:508 src/msguniq.c:393
+#: src/recode-sr-latin.c:165 src/urlget.c:176 src/xgettext.c:888
+#, c-format, no-wrap
msgid " -h, --help display this help and exit\n"
msgstr ""
-#: src/hostname.c:235 src/msgattrib.c:480 src/msgcat.c:429 src/msgcmp.c:223
-#: src/msgcomm.c:431 src/msgconv.c:360 src/msgen.c:335 src/msgexec.c:280
-#: src/msgfilter.c:457 src/msgfmt.c:733 src/msggrep.c:573 src/msginit.c:421
-#: src/msgmerge.c:540 src/msgunfmt.c:508 src/msguniq.c:393 src/urlget.c:180
-#: src/xgettext.c:867
-#, c-format
+#: src/hostname.c:233 src/msgattrib.c:482 src/msgcat.c:431 src/msgcmp.c:225
+#: src/msgcomm.c:433 src/msgconv.c:362 src/msgen.c:337 src/msgexec.c:279
+#: src/msgfilter.c:478 src/msgfmt.c:751 src/msggrep.c:602 src/msginit.c:401
+#: src/msgmerge.c:547 src/msgunfmt.c:510 src/msguniq.c:395
+#: src/recode-sr-latin.c:168 src/urlget.c:178 src/xgettext.c:890
+#, c-format, no-wrap
msgid " -V, --version output version information and exit\n"
msgstr ""
-#: src/hostname.c:238 src/msgattrib.c:483 src/msgcat.c:432 src/msgcmp.c:226
-#: src/msgcomm.c:434 src/msgconv.c:363 src/msgen.c:338 src/msgexec.c:283
-#: src/msgfilter.c:460 src/msgfmt.c:740 src/msggrep.c:576 src/msginit.c:424
-#: src/msgmerge.c:547 src/msgunfmt.c:513 src/msguniq.c:396 src/urlget.c:183
-#: src/xgettext.c:870
+#: src/hostname.c:236 src/msgattrib.c:485 src/msgcat.c:434 src/msgcmp.c:228
+#: src/msgcomm.c:436 src/msgconv.c:365 src/msgen.c:340 src/msgexec.c:282
+#: src/msgfilter.c:481 src/msgfmt.c:758 src/msggrep.c:605 src/msginit.c:404
+#: src/msgmerge.c:554 src/msgunfmt.c:515 src/msguniq.c:398
+#: src/recode-sr-latin.c:171 src/urlget.c:181 src/xgettext.c:893
msgid "Report bugs to <bug-gnu-gettext@gnu.org>.\n"
msgstr ""
-#: src/hostname.c:254 src/hostname.c:260 src/hostname.c:267
+#: src/hostname.c:252 src/hostname.c:258 src/hostname.c:265
#, c-format
msgid "could not get host name"
msgstr ""
-#: src/msgattrib.c:331 src/msgconv.c:237 src/msgexec.c:149 src/msgfilter.c:200
-#: src/msggrep.c:393 src/msginit.c:206 src/msguniq.c:259
+#: src/msgattrib.c:333 src/msgconv.c:239 src/msgexec.c:148 src/msgfilter.c:208
+#: src/msggrep.c:412 src/msginit.c:190 src/msguniq.c:261
#, c-format
msgid "at most one input file allowed"
msgstr ""
-#: src/msgattrib.c:337 src/msgattrib.c:341 src/msgcat.c:278 src/msgcat.c:282
-#: src/msgcomm.c:275 src/msgcomm.c:279 src/msgconv.c:243 src/msgconv.c:247
-#: src/msgen.c:230 src/msgen.c:234 src/msgfilter.c:290 src/msgfilter.c:294
-#: src/msgfmt.c:405 src/msgfmt.c:413 src/msgfmt.c:428 src/msgfmt.c:450
-#: src/msggrep.c:399 src/msggrep.c:403 src/msgmerge.c:327 src/msgmerge.c:348
-#: src/msgmerge.c:352 src/msgunfmt.c:282 src/msguniq.c:265 src/msguniq.c:269
-#: src/xgettext.c:518 src/xgettext.c:522
+#: src/msgattrib.c:339 src/msgattrib.c:343 src/msgcat.c:280 src/msgcat.c:284
+#: src/msgcomm.c:277 src/msgcomm.c:281 src/msgconv.c:245 src/msgconv.c:249
+#: src/msgen.c:232 src/msgen.c:236 src/msgfilter.c:298 src/msgfilter.c:302
+#: src/msgfmt.c:406 src/msgfmt.c:414 src/msgfmt.c:429 src/msgfmt.c:451
+#: src/msggrep.c:418 src/msggrep.c:422 src/msgmerge.c:334 src/msgmerge.c:355
+#: src/msgmerge.c:359 src/msgunfmt.c:284 src/msguniq.c:267 src/msguniq.c:271
+#: src/xgettext.c:530 src/xgettext.c:534 src/xgettext.c:541
#, c-format
msgid "%s and %s are mutually exclusive"
msgstr ""
-#: src/msgattrib.c:376 src/msgconv.c:284 src/msggrep.c:471 src/msguniq.c:304
+#: src/msgattrib.c:378 src/msgconv.c:286 src/msggrep.c:492 src/msguniq.c:306
#, c-format
msgid "Usage: %s [OPTION] [INPUTFILE]\n"
msgstr ""
-#: src/msgattrib.c:381
+#: src/msgattrib.c:383
#, c-format, no-wrap
msgid ""
"Filters the messages of a translation catalog according to their attributes,\n"
"and manipulates the attributes.\n"
msgstr ""
-#: src/msgattrib.c:385 src/msgcat.c:348 src/msgcmp.c:194 src/msgcomm.c:353
-#: src/msgconv.c:292 src/msgen.c:274 src/msgexec.c:257 src/msgfilter.c:379
-#: src/msggrep.c:481 src/msginit.c:375 src/msgmerge.c:442 src/msgunfmt.c:418
-#: src/msguniq.c:320
+#: src/msgattrib.c:387 src/msgcat.c:350 src/msgcmp.c:196 src/msgcomm.c:355
+#: src/msgconv.c:294 src/msgen.c:276 src/msgexec.c:256 src/msgfilter.c:400
+#: src/msggrep.c:502 src/msginit.c:355 src/msgmerge.c:449 src/msgunfmt.c:420
+#: src/msguniq.c:322
#, c-format
msgid ""
"Mandatory arguments to long options are mandatory for short options too.\n"
msgstr ""
-#: src/msgattrib.c:388 src/msgcat.c:351 src/msgcmp.c:197 src/msgcomm.c:356
-#: src/msgconv.c:295 src/msgen.c:277 src/msgexec.c:260 src/msgfilter.c:382
-#: src/msgfmt.c:625 src/msggrep.c:484 src/msginit.c:378 src/msgmerge.c:445
-#: src/msgunfmt.c:432 src/msguniq.c:323 src/xgettext.c:735
+#: src/msgattrib.c:390 src/msgcat.c:353 src/msgcmp.c:199 src/msgcomm.c:358
+#: src/msgconv.c:297 src/msgen.c:279 src/msgexec.c:259 src/msgfilter.c:403
+#: src/msgfmt.c:643 src/msggrep.c:505 src/msginit.c:358 src/msgmerge.c:452
+#: src/msgunfmt.c:434 src/msguniq.c:325 src/xgettext.c:754
#, c-format
msgid "Input file location:\n"
msgstr ""
-#: src/msgattrib.c:390 src/msgconv.c:297 src/msggrep.c:486 src/msguniq.c:325
+#: src/msgattrib.c:392 src/msgconv.c:299 src/msggrep.c:507 src/msguniq.c:327
#, c-format
msgid " INPUTFILE input PO file\n"
msgstr ""
-#: src/msgattrib.c:392 src/msgcat.c:357 src/msgcmp.c:203 src/msgcomm.c:362
-#: src/msgconv.c:299 src/msgen.c:281 src/msgexec.c:264 src/msgfilter.c:386
-#: src/msgfmt.c:629 src/msggrep.c:488 src/msgmerge.c:451 src/msguniq.c:327
-#: src/xgettext.c:741
+#: src/msgattrib.c:394 src/msgcat.c:359 src/msgcmp.c:205 src/msgcomm.c:364
+#: src/msgconv.c:301 src/msgen.c:283 src/msgexec.c:263 src/msgfilter.c:407
+#: src/msgfmt.c:647 src/msggrep.c:509 src/msgmerge.c:458 src/msguniq.c:329
+#: src/xgettext.c:760
#, c-format
msgid ""
" -D, --directory=DIRECTORY add DIRECTORY to list for input files search\n"
msgstr ""
-#: src/msgattrib.c:394 src/msgconv.c:301 src/msgexec.c:266 src/msgfilter.c:388
-#: src/msggrep.c:490 src/msgunfmt.c:436 src/msguniq.c:329
+#: src/msgattrib.c:396 src/msgconv.c:303 src/msgexec.c:265 src/msgfilter.c:409
+#: src/msggrep.c:511 src/msgunfmt.c:438 src/msguniq.c:331
#, c-format
msgid "If no input file is given or if it is -, standard input is read.\n"
msgstr ""
-#: src/msgattrib.c:397 src/msgcat.c:362 src/msgcomm.c:367 src/msgconv.c:304
-#: src/msgen.c:286 src/msgfilter.c:391 src/msgfmt.c:649 src/msggrep.c:493
-#: src/msginit.c:386 src/msgmerge.c:463 src/msgunfmt.c:472 src/msguniq.c:332
-#: src/xgettext.c:746
+#: src/msgattrib.c:399 src/msgcat.c:364 src/msgcomm.c:369 src/msgconv.c:306
+#: src/msgen.c:288 src/msgfilter.c:412 src/msgfmt.c:667 src/msggrep.c:514
+#: src/msginit.c:366 src/msgmerge.c:470 src/msgunfmt.c:474 src/msguniq.c:334
+#: src/xgettext.c:765
#, c-format
msgid "Output file location:\n"
msgstr ""
-#: src/msgattrib.c:399 src/msgcat.c:364 src/msgcomm.c:369 src/msgconv.c:306
-#: src/msgen.c:288 src/msgfilter.c:393 src/msgfmt.c:651 src/msggrep.c:495
-#: src/msgmerge.c:465 src/msgunfmt.c:474 src/msguniq.c:334
+#: src/msgattrib.c:401 src/msgcat.c:366 src/msgcomm.c:371 src/msgconv.c:308
+#: src/msgen.c:290 src/msgfilter.c:414 src/msgfmt.c:669 src/msggrep.c:516
+#: src/msgmerge.c:472 src/msgunfmt.c:476 src/msguniq.c:336
#, c-format
msgid " -o, --output-file=FILE write output to specified file\n"
msgstr ""
-#: src/msgattrib.c:401 src/msgcat.c:366 src/msgcomm.c:371 src/msgconv.c:308
-#: src/msgen.c:290 src/msgfilter.c:395 src/msggrep.c:497 src/msgmerge.c:467
-#: src/msgunfmt.c:476 src/msguniq.c:336
+#: src/msgattrib.c:403 src/msgcat.c:368 src/msgcomm.c:373 src/msgconv.c:310
+#: src/msgen.c:292 src/msgfilter.c:416 src/msggrep.c:518 src/msgmerge.c:474
+#: src/msgunfmt.c:478 src/msguniq.c:338
#, c-format
msgid ""
"The results are written to standard output if no output file is specified\n"
"or if it is -.\n"
msgstr ""
-#: src/msgattrib.c:405 src/msgcat.c:370 src/msgcomm.c:375 src/msguniq.c:340
+#: src/msgattrib.c:407 src/msgcat.c:372 src/msgcomm.c:377 src/msguniq.c:342
#, c-format
msgid "Message selection:\n"
msgstr ""
-#: src/msgattrib.c:407
+#: src/msgattrib.c:409
#, c-format
msgid ""
" --translated keep translated, remove untranslated messages\n"
msgstr ""
-#: src/msgattrib.c:409
+#: src/msgattrib.c:411
#, c-format
msgid ""
" --untranslated keep untranslated, remove translated messages\n"
msgstr ""
-#: src/msgattrib.c:411
+#: src/msgattrib.c:413
#, c-format
msgid " --no-fuzzy remove 'fuzzy' marked messages\n"
msgstr ""
-#: src/msgattrib.c:413
+#: src/msgattrib.c:415
#, c-format
msgid " --only-fuzzy keep 'fuzzy' marked messages\n"
msgstr ""
-#: src/msgattrib.c:415
+#: src/msgattrib.c:417
#, c-format
msgid " --no-obsolete remove obsolete #~ messages\n"
msgstr ""
-#: src/msgattrib.c:417
+#: src/msgattrib.c:419
#, c-format
msgid " --only-obsolete keep obsolete #~ messages\n"
msgstr ""
-#: src/msgattrib.c:420
+#: src/msgattrib.c:422
#, c-format
msgid "Attribute manipulation:\n"
msgstr ""
-#: src/msgattrib.c:422
+#: src/msgattrib.c:424
#, c-format
msgid " --set-fuzzy set all messages 'fuzzy'\n"
msgstr ""
-#: src/msgattrib.c:424
+#: src/msgattrib.c:426
#, c-format
msgid " --clear-fuzzy set all messages non-'fuzzy'\n"
msgstr ""
-#: src/msgattrib.c:426
+#: src/msgattrib.c:428
#, c-format
msgid " --set-obsolete set all messages obsolete\n"
msgstr ""
-#: src/msgattrib.c:428
+#: src/msgattrib.c:430
#, c-format
msgid " --clear-obsolete set all messages non-obsolete\n"
msgstr ""
-#: src/msgattrib.c:430
+#: src/msgattrib.c:432
#, c-format
msgid ""
" --only-file=FILE.po manipulate only entries listed in FILE.po\n"
msgstr ""
-#: src/msgattrib.c:432
+#: src/msgattrib.c:434
#, c-format
msgid ""
" --ignore-file=FILE.po manipulate only entries not listed in FILE.po\n"
msgstr ""
-#: src/msgattrib.c:434
+#: src/msgattrib.c:436
#, c-format
msgid " --fuzzy synonym for --only-fuzzy --clear-fuzzy\n"
msgstr ""
-#: src/msgattrib.c:436
+#: src/msgattrib.c:438
#, c-format
msgid ""
" --obsolete synonym for --only-obsolete --clear-obsolete\n"
msgstr ""
-#: src/msgattrib.c:439 src/msgcat.c:382 src/msgcmp.c:211 src/msgcomm.c:387
-#: src/msgconv.c:319 src/msgen.c:294 src/msgexec.c:269 src/msgfilter.c:414
-#: src/msgfmt.c:694 src/msggrep.c:532 src/msginit.c:394 src/msgmerge.c:498
-#: src/msguniq.c:347
+#: src/msgattrib.c:441 src/msgcat.c:384 src/msgcmp.c:213 src/msgcomm.c:389
+#: src/msgconv.c:321 src/msgen.c:296 src/msgexec.c:268 src/msgfilter.c:435
+#: src/msgfmt.c:712 src/msggrep.c:561 src/msginit.c:374 src/msgmerge.c:505
+#: src/msguniq.c:349
#, c-format
msgid "Input file syntax:\n"
msgstr ""
-#: src/msgattrib.c:441 src/msgconv.c:321 src/msgen.c:296 src/msgexec.c:271
-#: src/msgfilter.c:416 src/msggrep.c:534 src/msginit.c:396 src/msguniq.c:349
+#: src/msgattrib.c:443 src/msgconv.c:323 src/msgen.c:298 src/msgexec.c:270
+#: src/msgfilter.c:437 src/msggrep.c:563 src/msginit.c:376 src/msguniq.c:351
#, c-format
msgid ""
" -P, --properties-input input file is in Java .properties syntax\n"
msgstr ""
-#: src/msgattrib.c:443 src/msgconv.c:323 src/msgen.c:298 src/msgexec.c:273
-#: src/msgfilter.c:418 src/msggrep.c:536 src/msginit.c:398 src/msguniq.c:351
+#: src/msgattrib.c:445 src/msgconv.c:325 src/msgen.c:300 src/msgexec.c:272
+#: src/msgfilter.c:439 src/msggrep.c:565 src/msginit.c:378 src/msguniq.c:353
#, c-format
msgid ""
" --stringtable-input input file is in NeXTstep/GNUstep .strings "
"syntax\n"
msgstr ""
-#: src/msgattrib.c:446 src/msgcat.c:390 src/msgcomm.c:395 src/msgconv.c:326
-#: src/msgen.c:301 src/msgfilter.c:421 src/msgfmt.c:722 src/msggrep.c:539
-#: src/msginit.c:401 src/msgmerge.c:506 src/msgunfmt.c:480 src/msguniq.c:354
-#: src/xgettext.c:821
+#: src/msgattrib.c:448 src/msgcat.c:392 src/msgcomm.c:397 src/msgconv.c:328
+#: src/msgen.c:303 src/msgfilter.c:442 src/msgfmt.c:740 src/msggrep.c:568
+#: src/msginit.c:381 src/msgmerge.c:513 src/msgunfmt.c:482 src/msguniq.c:356
+#: src/xgettext.c:844
#, c-format
msgid "Output details:\n"
msgstr ""
-#: src/msgattrib.c:448 src/msgcat.c:397 src/msgcomm.c:397 src/msgconv.c:328
-#: src/msgen.c:303 src/msgmerge.c:508 src/msgunfmt.c:482 src/msguniq.c:361
-#: src/xgettext.c:823
+#: src/msgattrib.c:450 src/msgcat.c:399 src/msgcomm.c:399 src/msgconv.c:330
+#: src/msgen.c:305 src/msgmerge.c:515 src/msgunfmt.c:484 src/msguniq.c:363
+#: src/xgettext.c:846
#, c-format
msgid ""
" -e, --no-escape do not use C escapes in output (default)\n"
msgstr ""
-#: src/msgattrib.c:450 src/msgcat.c:399 src/msgcomm.c:399 src/msgconv.c:330
-#: src/msgen.c:305 src/msgfilter.c:425 src/msgmerge.c:510 src/msgunfmt.c:484
-#: src/msguniq.c:363 src/xgettext.c:825
+#: src/msgattrib.c:452 src/msgcat.c:401 src/msgcomm.c:401 src/msgconv.c:332
+#: src/msgen.c:307 src/msgfilter.c:446 src/msgmerge.c:517 src/msgunfmt.c:486
+#: src/msguniq.c:365 src/xgettext.c:848
#, c-format
msgid ""
" -E, --escape use C escapes in output, no extended chars\n"
msgstr ""
-#: src/msgattrib.c:452 src/msgcat.c:401 src/msgcomm.c:401 src/msgconv.c:332
-#: src/msgen.c:307 src/msgfilter.c:427 src/msggrep.c:545 src/msgmerge.c:512
-#: src/msgunfmt.c:486 src/msguniq.c:365 src/xgettext.c:827
+#: src/msgattrib.c:454 src/msgcat.c:403 src/msgcomm.c:403 src/msgconv.c:334
+#: src/msgen.c:309 src/msgfilter.c:448 src/msggrep.c:574 src/msgmerge.c:519
+#: src/msgunfmt.c:488 src/msguniq.c:367 src/xgettext.c:850
#, c-format
msgid " --force-po write PO file even if empty\n"
msgstr ""
-#: src/msgattrib.c:454 src/msgcat.c:403 src/msgcomm.c:403 src/msguniq.c:367
-#: src/xgettext.c:829
+#: src/msgattrib.c:456 src/msgcat.c:405 src/msgcomm.c:405 src/msguniq.c:369
+#: src/xgettext.c:852
#, c-format
msgid " -i, --indent write the .po file using indented style\n"
msgstr ""
-#: src/msgattrib.c:456 src/msgcat.c:405 src/msgcomm.c:405 src/msguniq.c:369
-#: src/xgettext.c:831
+#: src/msgattrib.c:458 src/msgcat.c:407 src/msgcomm.c:407 src/msguniq.c:371
+#: src/xgettext.c:854
#, c-format
msgid " --no-location do not write '#: filename:line' lines\n"
msgstr ""
-#: src/msgattrib.c:458 src/msgcat.c:407 src/msgcomm.c:407 src/msguniq.c:371
-#: src/xgettext.c:833
+#: src/msgattrib.c:460 src/msgcat.c:409 src/msgcomm.c:409 src/msguniq.c:373
+#: src/xgettext.c:856
#, c-format
msgid ""
" -n, --add-location generate '#: filename:line' lines (default)\n"
msgstr ""
-#: src/msgattrib.c:460 src/msgcat.c:409 src/msgcomm.c:409 src/msguniq.c:373
-#: src/xgettext.c:835
+#: src/msgattrib.c:462 src/msgcat.c:411 src/msgcomm.c:411 src/msguniq.c:375
+#: src/xgettext.c:858
#, c-format
msgid ""
" --strict write out strict Uniforum conforming .po file\n"
msgstr ""
-#: src/msgattrib.c:462 src/msgcat.c:411 src/msgcomm.c:411 src/msgconv.c:342
-#: src/msgen.c:317 src/msgfilter.c:439 src/msggrep.c:555 src/msginit.c:407
-#: src/msgmerge.c:522 src/msgunfmt.c:492 src/msguniq.c:375
+#: src/msgattrib.c:464 src/msgcat.c:413 src/msgcomm.c:413 src/msgconv.c:344
+#: src/msgen.c:319 src/msgfilter.c:460 src/msggrep.c:584 src/msginit.c:387
+#: src/msgmerge.c:529 src/msgunfmt.c:494 src/msguniq.c:377
#, c-format
msgid " -p, --properties-output write out a Java .properties file\n"
msgstr ""
-#: src/msgattrib.c:464 src/msgcat.c:413 src/msgcomm.c:413 src/msgconv.c:344
-#: src/msgen.c:319 src/msgfilter.c:441 src/msggrep.c:557 src/msginit.c:409
-#: src/msgmerge.c:524 src/msgunfmt.c:494 src/msguniq.c:377 src/xgettext.c:839
+#: src/msgattrib.c:466 src/msgcat.c:415 src/msgcomm.c:415 src/msgconv.c:346
+#: src/msgen.c:321 src/msgfilter.c:462 src/msggrep.c:586 src/msginit.c:389
+#: src/msgmerge.c:531 src/msgunfmt.c:496 src/msguniq.c:379 src/xgettext.c:862
#, c-format
msgid ""
" --stringtable-output write out a NeXTstep/GNUstep .strings file\n"
msgstr ""
-#: src/msgattrib.c:466 src/msgcat.c:415 src/msgcomm.c:415 src/msgconv.c:346
-#: src/msgen.c:321 src/msgfilter.c:443 src/msggrep.c:559 src/msginit.c:411
-#: src/msgmerge.c:526 src/msgunfmt.c:496 src/msguniq.c:379 src/xgettext.c:841
+#: src/msgattrib.c:468 src/msgcat.c:417 src/msgcomm.c:417 src/msgconv.c:348
+#: src/msgen.c:323 src/msgfilter.c:464 src/msggrep.c:588 src/msginit.c:391
+#: src/msgmerge.c:533 src/msgunfmt.c:498 src/msguniq.c:381 src/xgettext.c:864
#, c-format
msgid " -w, --width=NUMBER set output page width\n"
msgstr ""
-#: src/msgattrib.c:468 src/msgcat.c:417 src/msgcomm.c:417 src/msgconv.c:348
-#: src/msgen.c:323 src/msgfilter.c:445 src/msggrep.c:561 src/msginit.c:413
-#: src/msgmerge.c:528 src/msgunfmt.c:498 src/msguniq.c:381 src/xgettext.c:843
+#: src/msgattrib.c:470 src/msgcat.c:419 src/msgcomm.c:419 src/msgconv.c:350
+#: src/msgen.c:325 src/msgfilter.c:466 src/msggrep.c:590 src/msginit.c:393
+#: src/msgmerge.c:535 src/msgunfmt.c:500 src/msguniq.c:383 src/xgettext.c:866
#, c-format
msgid ""
" --no-wrap do not break long message lines, longer than\n"
" the output page width, into several lines\n"
msgstr ""
-#: src/msgattrib.c:471 src/msgcat.c:420 src/msgcomm.c:420 src/msgconv.c:351
-#: src/msgen.c:326 src/msgfilter.c:448 src/msgmerge.c:531 src/msgunfmt.c:501
-#: src/msguniq.c:384 src/xgettext.c:846
+#: src/msgattrib.c:473 src/msgcat.c:422 src/msgcomm.c:422 src/msgconv.c:353
+#: src/msgen.c:328 src/msgfilter.c:469 src/msgmerge.c:538 src/msgunfmt.c:503
+#: src/msguniq.c:386 src/xgettext.c:869
#, c-format
msgid " -s, --sort-output generate sorted output\n"
msgstr ""
-#: src/msgattrib.c:473 src/msgcat.c:422 src/msgcomm.c:422 src/msgconv.c:353
-#: src/msgen.c:328 src/msgfilter.c:450 src/msgmerge.c:533 src/msguniq.c:386
-#: src/xgettext.c:848
+#: src/msgattrib.c:475 src/msgcat.c:424 src/msgcomm.c:424 src/msgconv.c:355
+#: src/msgen.c:330 src/msgfilter.c:471 src/msgmerge.c:540 src/msguniq.c:388
+#: src/xgettext.c:871
#, c-format
msgid " -F, --sort-by-file sort output by file location\n"
msgstr ""
-#: src/msgcat.c:288 src/msgcomm.c:305
+#: src/msgcat.c:290 src/msgcomm.c:307
#, c-format
msgid "impossible selection criteria specified (%d < n < %d)"
msgstr ""
-#: src/msgcat.c:331 src/msgcomm.c:337 src/xgettext.c:721
+#: src/msgcat.c:333 src/msgcomm.c:339 src/xgettext.c:740
#, c-format
msgid "Usage: %s [OPTION] [INPUTFILE]...\n"
msgstr ""
-#: src/msgcat.c:336
+#: src/msgcat.c:338
#, c-format, no-wrap
msgid ""
"Concatenates and merges the specified PO files.\n"
"File positions from all PO files will be cumulated.\n"
msgstr ""
-#: src/msgcat.c:353 src/msgcomm.c:358 src/xgettext.c:737
+#: src/msgcat.c:355 src/msgcomm.c:360 src/xgettext.c:756
#, c-format
msgid " INPUTFILE ... input files\n"
msgstr ""
-#: src/msgcat.c:355 src/msgcomm.c:360 src/xgettext.c:739
+#: src/msgcat.c:357 src/msgcomm.c:362 src/xgettext.c:758
#, c-format
msgid " -f, --files-from=FILE get list of input files from FILE\n"
msgstr ""
-#: src/msgcat.c:359 src/msgcomm.c:364 src/msgen.c:283 src/msgfmt.c:631
-#: src/xgettext.c:743
+#: src/msgcat.c:361 src/msgcomm.c:366 src/msgen.c:285 src/msgfmt.c:649
+#: src/xgettext.c:762
#, c-format
msgid "If input file is -, standard input is read.\n"
msgstr ""
-#: src/msgcat.c:372 src/msgcomm.c:377
+#: src/msgcat.c:374 src/msgcomm.c:379
#, c-format
msgid ""
" -<, --less-than=NUMBER print messages with less than this many\n"
" definitions, defaults to infinite if not set\n"
msgstr ""
-#: src/msgcat.c:375
+#: src/msgcat.c:377
#, c-format
msgid ""
" ->, --more-than=NUMBER print messages with more than this many\n"
" definitions, defaults to 0 if not set\n"
msgstr ""
-#: src/msgcat.c:378 src/msgcomm.c:383
+#: src/msgcat.c:380 src/msgcomm.c:385
#, c-format
msgid ""
" -u, --unique shorthand for --less-than=2, requests\n"
" that only unique messages be printed\n"
msgstr ""
-#: src/msgcat.c:384 src/msgcmp.c:213 src/msgcomm.c:389 src/msgfmt.c:696
-#: src/msgmerge.c:500
+#: src/msgcat.c:386 src/msgcmp.c:215 src/msgcomm.c:391 src/msgfmt.c:714
+#: src/msgmerge.c:507
#, c-format
msgid ""
" -P, --properties-input input files are in Java .properties syntax\n"
msgstr ""
-#: src/msgcat.c:386 src/msgcmp.c:215 src/msgcomm.c:391 src/msgfmt.c:698
-#: src/msgmerge.c:502
+#: src/msgcat.c:388 src/msgcmp.c:217 src/msgcomm.c:393 src/msgfmt.c:716
+#: src/msgmerge.c:509
#, c-format
msgid ""
" --stringtable-input input files are in NeXTstep/GNUstep .strings\n"
" syntax\n"
msgstr ""
-#: src/msgcat.c:392 src/msgconv.c:314 src/msguniq.c:356
+#: src/msgcat.c:394 src/msgconv.c:316 src/msguniq.c:358
#, c-format
msgid " -t, --to-code=NAME encoding for output\n"
msgstr ""
-#: src/msgcat.c:394 src/msguniq.c:358
+#: src/msgcat.c:396 src/msguniq.c:360
#, c-format
msgid ""
" --use-first use first available translation for each\n"
" message, don't merge several translations\n"
msgstr ""
-#: src/msgcmp.c:156 src/msgmerge.c:313
+#. This is a proper name. See the gettext manual, section Names.
+#: src/msgcmp.c:147 src/msgcomm.c:267 src/msgmerge.c:309
+msgid "Peter Miller"
+msgstr ""
+
+#: src/msgcmp.c:158 src/msgmerge.c:320
#, c-format
msgid "no input files given"
msgstr ""
-#: src/msgcmp.c:161 src/msgmerge.c:318
+#: src/msgcmp.c:163 src/msgmerge.c:325
#, c-format
msgid "exactly 2 input files required"
msgstr ""
-#: src/msgcmp.c:180 src/msgmerge.c:425
+#: src/msgcmp.c:182 src/msgmerge.c:432
#, c-format
msgid "Usage: %s [OPTION] def.po ref.pot\n"
msgstr ""
-#: src/msgcmp.c:185
+#: src/msgcmp.c:187
#, c-format, no-wrap
msgid ""
"Compare two Uniforum style .po files to check that both contain the same\n"
"match cannot be found, fuzzy matching is used to produce better diagnostics.\n"
msgstr ""
-#: src/msgcmp.c:199
+#: src/msgcmp.c:201
#, c-format
msgid " def.po translations\n"
msgstr ""
-#: src/msgcmp.c:201
+#: src/msgcmp.c:203
#, c-format
msgid " ref.pot references to the sources\n"
msgstr ""
-#: src/msgcmp.c:206 src/msgmerge.c:491
+#: src/msgcmp.c:208 src/msgmerge.c:498
#, c-format
msgid "Operation modifiers:\n"
msgstr ""
-#: src/msgcmp.c:208 src/msgmerge.c:493
+#: src/msgcmp.c:210 src/msgmerge.c:500
#, c-format
msgid ""
" -m, --multi-domain apply ref.pot to each of the domains in def."
"po\n"
msgstr ""
-#: src/msgcmp.c:285 src/msgmerge.c:965
+#: src/msgcmp.c:288 src/msgmerge.c:1097
#, c-format
msgid "this message is used but not defined..."
msgstr ""
-#: src/msgcmp.c:287 src/msgmerge.c:967
+#: src/msgcmp.c:291 src/msgmerge.c:1100
#, c-format
msgid "...but this definition is similar"
msgstr ""
-#: src/msgcmp.c:292 src/msgmerge.c:997
+#: src/msgcmp.c:296 src/msgmerge.c:1130
#, c-format
msgid "this message is used but not defined in %s"
msgstr ""
-#: src/msgcmp.c:396
+#: src/msgcmp.c:400
#, c-format
msgid "warning: this message is not used"
msgstr ""
-#: src/msgcmp.c:403
+#: src/msgcmp.c:407 src/msgfmt.c:541
#, c-format
msgid "found %d fatal error"
msgid_plural "found %d fatal errors"
msgstr[0] ""
msgstr[1] ""
-#: src/msgcomm.c:294
+#: src/msgcomm.c:296
#, c-format
msgid "at least two files must be specified"
msgstr ""
-#: src/msgcomm.c:342
+#: src/msgcomm.c:344
#, c-format, no-wrap
msgid ""
"Find messages which are common to two or more of the specified PO files.\n"
"cumulated.\n"
msgstr ""
-#: src/msgcomm.c:380
+#: src/msgcomm.c:382
#, c-format
msgid ""
" ->, --more-than=NUMBER print messages with more than this many\n"
" definitions, defaults to 1 if not set\n"
msgstr ""
-#: src/msgcomm.c:424 src/xgettext.c:850
+#: src/msgcomm.c:426 src/xgettext.c:873
#, c-format
msgid ""
" --omit-header don't write header with `msgid \"\"' entry\n"
msgstr ""
-#: src/msgconv.c:288
+#: src/msgconv.c:290
#, c-format
msgid "Converts a translation catalog to a different character encoding.\n"
msgstr ""
-#: src/msgconv.c:312
+#: src/msgconv.c:314
#, c-format
msgid "Conversion target:\n"
msgstr ""
-#: src/msgconv.c:316
+#: src/msgconv.c:318
#, c-format
msgid "The default encoding is the current locale's encoding.\n"
msgstr ""
-#: src/msgconv.c:334 src/msgen.c:309 src/msgmerge.c:514
+#: src/msgconv.c:336 src/msgen.c:311 src/msgmerge.c:521
#, c-format
msgid " -i, --indent indented output style\n"
msgstr ""
-#: src/msgconv.c:336 src/msgen.c:311 src/msgfilter.c:433 src/msggrep.c:549
-#: src/msgmerge.c:516
+#: src/msgconv.c:338 src/msgen.c:313 src/msgfilter.c:454 src/msggrep.c:578
+#: src/msgmerge.c:523
#, c-format
msgid " --no-location suppress '#: filename:line' lines\n"
msgstr ""
-#: src/msgconv.c:338 src/msgen.c:313 src/msgfilter.c:435 src/msggrep.c:551
-#: src/msgmerge.c:518
+#: src/msgconv.c:340 src/msgen.c:315 src/msgfilter.c:456 src/msggrep.c:580
+#: src/msgmerge.c:525
#, c-format
msgid ""
" --add-location preserve '#: filename:line' lines (default)\n"
msgstr ""
-#: src/msgconv.c:340 src/msgen.c:315 src/msgfilter.c:437 src/msggrep.c:553
-#: src/msgmerge.c:520
+#: src/msgconv.c:342 src/msgen.c:317 src/msgfilter.c:458 src/msggrep.c:582
+#: src/msgmerge.c:527
#, c-format
msgid " --strict strict Uniforum output style\n"
msgstr ""
-#: src/msgen.c:219 src/msgfmt.c:377 src/xgettext.c:539
+#: src/msgen.c:221 src/msgfmt.c:378 src/xgettext.c:558
#, c-format
msgid "no input file given"
msgstr ""
-#: src/msgen.c:224
+#: src/msgen.c:226
#, c-format
msgid "exactly one input file required"
msgstr ""
-#: src/msgen.c:262
+#: src/msgen.c:264
#, c-format
msgid "Usage: %s [OPTION] INPUTFILE\n"
msgstr ""
-#: src/msgen.c:267
+#: src/msgen.c:269
#, c-format, no-wrap
msgid ""
"Creates an English translation catalog. The input file is the last\n"
"identical to the msgid.\n"
msgstr ""
-#: src/msgen.c:279
+#: src/msgen.c:281
#, c-format
msgid " INPUTFILE input PO or POT file\n"
msgstr ""
-#: src/msgexec.c:192
+#: src/msgexec.c:191
#, c-format
msgid "missing command name"
msgstr ""
-#: src/msgexec.c:238
+#: src/msgexec.c:237
#, c-format
msgid "Usage: %s [OPTION] COMMAND [COMMAND-OPTION]\n"
msgstr ""
-#: src/msgexec.c:243
+#: src/msgexec.c:242
#, c-format, no-wrap
msgid ""
"Applies a command to all translations of a translation catalog.\n"
"across all invocations.\n"
msgstr ""
-#: src/msgexec.c:252
+#: src/msgexec.c:251
#, c-format, no-wrap
msgid ""
"A special builtin command called '0' outputs the translation, followed by a\n"
"null byte. The output of \"msgexec 0\" is suitable as input for \"xargs -0\".\n"
msgstr ""
-#: src/msgexec.c:262 src/msgfilter.c:384
+#: src/msgexec.c:261 src/msgfilter.c:405
#, c-format
msgid " -i, --input=INPUTFILE input PO file\n"
msgstr ""
-#: src/msgexec.c:322
+#: src/msgexec.c:321
#, c-format
msgid "write to stdout failed"
msgstr ""
-#: src/msgexec.c:345 src/msgfilter.c:637
+#: src/msgexec.c:348 src/msgfilter.c:657
#, c-format
msgid "write to %s subprocess failed"
msgstr ""
-#: src/msgfilter.c:285
+#: src/msgfilter.c:293
#, c-format
msgid "missing filter name"
msgstr ""
-#: src/msgfilter.c:309
+#: src/msgfilter.c:317
#, c-format
msgid "at least one sed script must be specified"
msgstr ""
-#: src/msgfilter.c:371
+#: src/msgfilter.c:392
#, c-format
msgid "Usage: %s [OPTION] FILTER [FILTER-OPTION]\n"
msgstr ""
-#: src/msgfilter.c:375
+#: src/msgfilter.c:396
#, c-format
msgid "Applies a filter to all translations of a translation catalog.\n"
msgstr ""
-#: src/msgfilter.c:399
+#: src/msgfilter.c:420
#, c-format
msgid ""
"The FILTER can be any program that reads a translation from standard input\n"
"and writes a modified translation to standard output.\n"
msgstr ""
-#: src/msgfilter.c:404
+#: src/msgfilter.c:425
#, c-format
msgid "Useful FILTER-OPTIONs when the FILTER is 'sed':\n"
msgstr ""
-#: src/msgfilter.c:406
+#: src/msgfilter.c:427
#, c-format
msgid ""
" -e, --expression=SCRIPT add SCRIPT to the commands to be executed\n"
msgstr ""
-#: src/msgfilter.c:408
+#: src/msgfilter.c:429
#, c-format
msgid ""
" -f, --file=SCRIPTFILE add the contents of SCRIPTFILE to the "
" to be executed\n"
msgstr ""
-#: src/msgfilter.c:411
+#: src/msgfilter.c:432
#, c-format
msgid ""
" -n, --quiet, --silent suppress automatic printing of pattern space\n"
msgstr ""
-#: src/msgfilter.c:423 src/msggrep.c:541
+#: src/msgfilter.c:444 src/msggrep.c:570
#, c-format
msgid ""
" --no-escape do not use C escapes in output (default)\n"
msgstr ""
-#: src/msgfilter.c:429 src/msggrep.c:547
+#: src/msgfilter.c:450 src/msggrep.c:576
#, c-format
msgid " --indent indented output style\n"
msgstr ""
-#: src/msgfilter.c:431
+#: src/msgfilter.c:452
#, c-format
msgid ""
" --keep-header keep header entry unmodified, don't filter it\n"
msgstr ""
-#: src/msgfilter.c:560
+#: src/msgfilter.c:580
#, c-format
msgid "Not yet implemented."
msgstr ""
-#: src/msgfilter.c:589
+#: src/msgfilter.c:609
#, c-format
msgid "cannot set up nonblocking I/O to %s subprocess"
msgstr ""
-#: src/msgfilter.c:617
+#: src/msgfilter.c:637
#, c-format
msgid "communication with %s subprocess failed"
msgstr ""
-#: src/msgfilter.c:668
+#: src/msgfilter.c:688
#, c-format
msgid "read from %s subprocess failed"
msgstr ""
-#: src/msgfilter.c:684
+#: src/msgfilter.c:704
#, c-format
msgid "%s subprocess terminated with exit code %d"
msgstr ""
-#: src/msgfmt.c:316
+#: src/msgfmt.c:300
#, c-format
msgid "the argument to %s should be a single punctuation character"
msgstr ""
-#: src/msgfmt.c:419 src/msgfmt.c:441 src/msgfmt.c:463 src/msgunfmt.c:313
-#: src/msgunfmt.c:336
+#: src/msgfmt.c:347
+#, c-format
+msgid "invalid endianness: %s"
+msgstr ""
+
+#. This is a proper name. See the gettext manual, section Names.
+#: src/msgfmt.c:367 src/msgunfmt.c:253 src/xgettext.c:520
+msgid "Ulrich Drepper"
+msgstr ""
+
+#: src/msgfmt.c:420 src/msgfmt.c:442 src/msgfmt.c:464 src/msgunfmt.c:315
+#: src/msgunfmt.c:338
#, c-format
msgid "%s requires a \"-d directory\" specification"
msgstr ""
-#: src/msgfmt.c:434 src/msgfmt.c:456 src/msgunfmt.c:306 src/msgunfmt.c:329
+#: src/msgfmt.c:435 src/msgfmt.c:457 src/msgunfmt.c:308 src/msgunfmt.c:331
#, c-format
msgid "%s requires a \"-l locale\" specification"
msgstr ""
-#: src/msgfmt.c:472 src/msgunfmt.c:345 src/msgunfmt.c:351
+#: src/msgfmt.c:473 src/msgunfmt.c:347 src/msgunfmt.c:353
#, c-format
msgid "%s is only valid with %s or %s"
msgstr ""
-#: src/msgfmt.c:478 src/msgfmt.c:484
+#: src/msgfmt.c:479 src/msgfmt.c:485
#, c-format
msgid "%s is only valid with %s, %s or %s"
msgstr ""
-#: src/msgfmt.c:581
+#: src/msgfmt.c:599
#, c-format
msgid "%d translated message"
msgid_plural "%d translated messages"
msgstr[0] ""
msgstr[1] ""
-#: src/msgfmt.c:586
+#: src/msgfmt.c:604
#, c-format
msgid ", %d fuzzy translation"
msgid_plural ", %d fuzzy translations"
msgstr[0] ""
msgstr[1] ""
-#: src/msgfmt.c:591
+#: src/msgfmt.c:609
#, c-format
msgid ", %d untranslated message"
msgid_plural ", %d untranslated messages"
msgstr[0] ""
msgstr[1] ""
-#: src/msgfmt.c:611
+#: src/msgfmt.c:629
#, c-format
msgid "Usage: %s [OPTION] filename.po ...\n"
msgstr ""
-#: src/msgfmt.c:615
+#: src/msgfmt.c:633
#, c-format
msgid "Generate binary message catalog from textual translation description.\n"
msgstr ""
-#: src/msgfmt.c:620 src/xgettext.c:730
+#: src/msgfmt.c:638 src/xgettext.c:749
#, c-format, no-wrap
msgid ""
"Mandatory arguments to long options are mandatory for short options too.\n"
"Similarly for optional arguments.\n"
msgstr ""
-#: src/msgfmt.c:627
+#: src/msgfmt.c:645
#, c-format
msgid " filename.po ... input files\n"
msgstr ""
-#: src/msgfmt.c:634 src/msgmerge.c:457 src/msgunfmt.c:421 src/xgettext.c:778
+#: src/msgfmt.c:652 src/msgmerge.c:464 src/msgunfmt.c:423 src/xgettext.c:797
#, c-format
msgid "Operation mode:\n"
msgstr ""
-#: src/msgfmt.c:636
+#: src/msgfmt.c:654
#, c-format
msgid ""
" -j, --java Java mode: generate a Java ResourceBundle "
"class\n"
msgstr ""
-#: src/msgfmt.c:638
+#: src/msgfmt.c:656
#, c-format
msgid ""
" --java2 like --java, and assume Java2 (JDK 1.2 or "
"higher)\n"
msgstr ""
-#: src/msgfmt.c:640
+#: src/msgfmt.c:658
#, c-format
msgid " --csharp C# mode: generate a .NET .dll file\n"
msgstr ""
-#: src/msgfmt.c:642
+#: src/msgfmt.c:660
#, c-format
msgid ""
" --csharp-resources C# resources mode: generate a .NET .resources "
"file\n"
msgstr ""
-#: src/msgfmt.c:644
+#: src/msgfmt.c:662
#, c-format
msgid ""
" --tcl Tcl mode: generate a tcl/msgcat .msg file\n"
msgstr ""
-#: src/msgfmt.c:646
+#: src/msgfmt.c:664
#, c-format
msgid " --qt Qt mode: generate a Qt .qm file\n"
msgstr ""
-#: src/msgfmt.c:653
+#: src/msgfmt.c:671
#, c-format
msgid " --strict enable strict Uniforum mode\n"
msgstr ""
-#: src/msgfmt.c:655 src/xgettext.c:754
+#: src/msgfmt.c:673 src/xgettext.c:773
#, c-format
msgid "If output file is -, output is written to standard output.\n"
msgstr ""
-#: src/msgfmt.c:658
+#: src/msgfmt.c:676
#, c-format
msgid "Output file location in Java mode:\n"
msgstr ""
-#: src/msgfmt.c:660 src/msgfmt.c:674 src/msgunfmt.c:441 src/msgunfmt.c:452
+#: src/msgfmt.c:678 src/msgfmt.c:692 src/msgunfmt.c:443 src/msgunfmt.c:454
#, c-format
msgid " -r, --resource=RESOURCE resource name\n"
msgstr ""
-#: src/msgfmt.c:662 src/msgfmt.c:676 src/msgfmt.c:686 src/msgunfmt.c:443
-#: src/msgunfmt.c:454 src/msgunfmt.c:464
+#: src/msgfmt.c:680 src/msgfmt.c:694 src/msgfmt.c:704 src/msgunfmt.c:445
+#: src/msgunfmt.c:456 src/msgunfmt.c:466
#, c-format
msgid ""
" -l, --locale=LOCALE locale name, either language or "
"language_COUNTRY\n"
msgstr ""
-#: src/msgfmt.c:664
+#: src/msgfmt.c:682
#, c-format
msgid ""
" -d DIRECTORY base directory of classes directory hierarchy\n"
msgstr ""
-#: src/msgfmt.c:666
+#: src/msgfmt.c:684
#, c-format
msgid ""
"The class name is determined by appending the locale name to the resource "
"written under the specified directory.\n"
msgstr ""
-#: src/msgfmt.c:672
+#: src/msgfmt.c:690
#, c-format
msgid "Output file location in C# mode:\n"
msgstr ""
-#: src/msgfmt.c:678 src/msgunfmt.c:456
+#: src/msgfmt.c:696 src/msgunfmt.c:458
#, c-format
msgid ""
" -d DIRECTORY base directory for locale dependent .dll "
"files\n"
msgstr ""
-#: src/msgfmt.c:680
+#: src/msgfmt.c:698
#, c-format
msgid ""
"The -l and -d options are mandatory. The .dll file is written in a\n"
"subdirectory of the specified directory whose name depends on the locale.\n"
msgstr ""
-#: src/msgfmt.c:684
+#: src/msgfmt.c:702
#, c-format
msgid "Output file location in Tcl mode:\n"
msgstr ""
-#: src/msgfmt.c:688 src/msgunfmt.c:466
+#: src/msgfmt.c:706 src/msgunfmt.c:468
#, c-format
msgid " -d DIRECTORY base directory of .msg message catalogs\n"
msgstr ""
-#: src/msgfmt.c:690
+#: src/msgfmt.c:708
#, c-format
msgid ""
"The -l and -d options are mandatory. The .msg file is written in the\n"
"specified directory.\n"
msgstr ""
-#: src/msgfmt.c:702 src/xgettext.c:770
+#: src/msgfmt.c:720 src/xgettext.c:789
#, c-format
msgid "Input file interpretation:\n"
msgstr ""
-#: src/msgfmt.c:704
+#: src/msgfmt.c:722
#, c-format
msgid ""
" -c, --check perform all the checks implied by\n"
"domain\n"
msgstr ""
-#: src/msgfmt.c:707
+#: src/msgfmt.c:725
#, c-format
msgid " --check-format check language dependent format strings\n"
msgstr ""
-#: src/msgfmt.c:709
+#: src/msgfmt.c:727
#, c-format
msgid ""
" --check-header verify presence and contents of the header "
"entry\n"
msgstr ""
-#: src/msgfmt.c:711
+#: src/msgfmt.c:729
#, c-format
msgid ""
" --check-domain check for conflicts between domain directives\n"
" and the --output-file option\n"
msgstr ""
-#: src/msgfmt.c:714
+#: src/msgfmt.c:732
#, c-format
msgid ""
" -C, --check-compatibility check that GNU msgfmt behaves like X/Open "
"msgfmt\n"
msgstr ""
-#: src/msgfmt.c:716
+#: src/msgfmt.c:734
#, c-format
msgid ""
" --check-accelerators[=CHAR] check presence of keyboard accelerators "
" menu items\n"
msgstr ""
-#: src/msgfmt.c:719
+#: src/msgfmt.c:737
#, c-format
msgid " -f, --use-fuzzy use fuzzy entries in output\n"
msgstr ""
-#: src/msgfmt.c:724
+#: src/msgfmt.c:742
#, c-format
msgid ""
" -a, --alignment=NUMBER align strings to NUMBER bytes (default: %d)\n"
msgstr ""
-#: src/msgfmt.c:726
+#: src/msgfmt.c:744
#, c-format
msgid ""
" --no-hash binary file will not include the hash table\n"
msgstr ""
-#: src/msgfmt.c:735
+#: src/msgfmt.c:753
#, c-format
msgid " --statistics print statistics about translations\n"
msgstr ""
-#: src/msgfmt.c:737 src/msgmerge.c:542 src/msgunfmt.c:510
+#: src/msgfmt.c:755 src/msgmerge.c:549 src/msgunfmt.c:512
#, c-format
msgid " -v, --verbose increase verbosity level\n"
msgstr ""
-#: src/msgfmt.c:875
-#, c-format
-msgid "plural expression can produce negative values"
-msgstr ""
-
-#: src/msgfmt.c:888
-#, c-format
-msgid "nplurals = %lu but plural expression can produce values as large as %lu"
-msgstr ""
-
-#: src/msgfmt.c:915
-#, c-format
-msgid "plural expression can produce division by zero"
-msgstr ""
-
-#: src/msgfmt.c:921
-#, c-format
-msgid "plural expression can produce integer overflow"
-msgstr ""
-
-#: src/msgfmt.c:927
-#, c-format
-msgid ""
-"plural expression can produce arithmetic exceptions, possibly division by "
-"zero"
-msgstr ""
-
-#: src/msgfmt.c:1005 src/msgfmt.c:1017
-#, c-format
-msgid "message catalog has plural form translations..."
-msgstr ""
-
-#: src/msgfmt.c:1008
-#, c-format
-msgid "...but header entry lacks a \"plural=EXPRESSION\" attribute"
-msgstr ""
-
-#: src/msgfmt.c:1020
-#, c-format
-msgid "...but header entry lacks a \"nplurals=INTEGER\" attribute"
-msgstr ""
-
-#: src/msgfmt.c:1045
-#, c-format
-msgid "invalid nplurals value"
-msgstr ""
-
-#: src/msgfmt.c:1059
-#, c-format
-msgid "invalid plural expression"
-msgstr ""
-
-#: src/msgfmt.c:1078 src/msgfmt.c:1093
-#, c-format
-msgid "nplurals = %lu..."
-msgstr ""
-
-#: src/msgfmt.c:1081
-#, c-format
-msgid "...but some messages have only one plural form"
-msgid_plural "...but some messages have only %lu plural forms"
-msgstr[0] ""
-msgstr[1] ""
-
-#: src/msgfmt.c:1096
-#, c-format
-msgid "...but some messages have one plural form"
-msgid_plural "...but some messages have %lu plural forms"
-msgstr[0] ""
-msgstr[1] ""
-
-#: src/msgfmt.c:1126
-#, c-format
-msgid "Try using the following, valid for %s:\n"
-msgstr ""
-
-#: src/msgfmt.c:1139
-#, c-format
-msgid ""
-"message catalog has plural form translations, but lacks a header entry with "
-"\"Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\""
-msgstr ""
-
-#: src/msgfmt.c:1191
-#, c-format
-msgid "`msgid' and `msgid_plural' entries do not both begin with '\\n'"
-msgstr ""
-
-#: src/msgfmt.c:1201
-#, c-format
-msgid "`msgid' and `msgstr[%u]' entries do not both begin with '\\n'"
-msgstr ""
-
-#: src/msgfmt.c:1213
-#, c-format
-msgid "`msgid' and `msgstr' entries do not both begin with '\\n'"
-msgstr ""
-
-#: src/msgfmt.c:1230
-#, c-format
-msgid "`msgid' and `msgid_plural' entries do not both end with '\\n'"
-msgstr ""
-
-#: src/msgfmt.c:1240
-#, c-format
-msgid "`msgid' and `msgstr[%u]' entries do not both end with '\\n'"
-msgstr ""
-
-#: src/msgfmt.c:1252
-#, c-format
-msgid "`msgid' and `msgstr' entries do not both end with '\\n'"
-msgstr ""
-
-#: src/msgfmt.c:1264
-#, c-format
-msgid "plural handling is a GNU gettext extension"
-msgstr ""
-
-#: src/msgfmt.c:1305
-#, c-format
-msgid "msgstr lacks the keyboard accelerator mark '%c'"
-msgstr ""
-
-#: src/msgfmt.c:1313
-#, c-format
-msgid "msgstr has too many keyboard accelerator marks '%c'"
-msgstr ""
-
-#: src/msgfmt.c:1347
-#, c-format
-msgid "headerfield `%s' missing in header\n"
-msgstr ""
-
-#: src/msgfmt.c:1351
-#, c-format
-msgid "header field `%s' should start at beginning of line\n"
-msgstr ""
-
-#: src/msgfmt.c:1362
-msgid "some header fields still have the initial default value\n"
-msgstr ""
-
-#: src/msgfmt.c:1374
-#, c-format
-msgid "field `%s' still has initial default value\n"
-msgstr ""
-
-#: src/msgfmt.c:1432
+#: src/msgfmt.c:865
#, c-format
msgid "warning: PO file header missing or invalid\n"
msgstr ""
-#: src/msgfmt.c:1435
+#: src/msgfmt.c:868
#, c-format
msgid "warning: charset conversion will not work\n"
msgstr ""
-#: src/msgfmt.c:1445
+#: src/msgfmt.c:878
#, c-format
msgid "warning: PO file header fuzzy\n"
msgstr ""
-#: src/msgfmt.c:1447
+#: src/msgfmt.c:880
#, c-format
msgid "warning: older versions of msgfmt will give an error on this\n"
msgstr ""
-#: src/msgfmt.c:1471
+#: src/msgfmt.c:904
#, c-format
msgid "domain name \"%s\" not suitable as file name"
msgstr ""
-#: src/msgfmt.c:1476
+#: src/msgfmt.c:909
#, c-format
msgid "domain name \"%s\" not suitable as file name: will use prefix"
msgstr ""
-#: src/msgfmt.c:1490
+#: src/msgfmt.c:923
#, c-format
msgid "`domain %s' directive ignored"
msgstr ""
-#: src/msgfmt.c:1544
+#: src/msgfmt.c:978
#, c-format
msgid "empty `msgstr' entry ignored"
msgstr ""
-#: src/msgfmt.c:1545
+#: src/msgfmt.c:979
#, c-format
msgid "fuzzy `msgstr' entry ignored"
msgstr ""
-#: src/msgfmt.c:1603
+#: src/msgfmt.c:1028
#, c-format
msgid "%s: warning: source file contains fuzzy translation"
msgstr ""
-#: src/msggrep.c:242 src/po-lex.c:666 src/read-mo.c:79
-#: src/read-properties.c:80 src/read-stringtable.c:95 src/x-awk.c:143
-#: src/x-c.c:354 src/x-csharp.c:161 src/x-elisp.c:149 src/x-glade.c:406
-#: src/x-java.c:176 src/x-librep.c:151 src/x-lisp.c:214 src/x-perl.c:230
-#: src/x-perl.c:305 src/x-perl.c:398 src/x-php.c:162 src/x-python.c:170
-#: src/x-rst.c:232 src/x-sh.c:159 src/x-smalltalk.c:91 src/x-tcl.c:152
-#: src/x-ycp.c:91
+#: src/msggrep.c:249 src/po-lex.c:657 src/read-mo.c:79
+#: src/read-properties.c:85 src/read-stringtable.c:100 src/x-awk.c:139
+#: src/x-c.c:414 src/x-csharp.c:159 src/x-elisp.c:145 src/x-glade.c:422
+#: src/x-java.c:172 src/x-librep.c:147 src/x-lisp.c:212 src/x-perl.c:226
+#: src/x-perl.c:301 src/x-perl.c:394 src/x-php.c:162 src/x-python.c:176
+#: src/x-rst.c:232 src/x-scheme.c:171 src/x-sh.c:155 src/x-smalltalk.c:91
+#: src/x-tcl.c:150 src/x-ycp.c:91
#, c-format
msgid "error while reading \"%s\""
msgstr ""
-#: src/msggrep.c:456
+#: src/msggrep.c:477
#, c-format
-msgid "option '%c' cannot be used before 'K' or 'T' or 'C' has been specified"
+msgid ""
+"option '%c' cannot be used before 'J' or 'K' or 'T' or 'C' or 'X' has been "
+"specified"
msgstr ""
-#: src/msggrep.c:476
+#: src/msggrep.c:497
#, c-format, no-wrap
msgid ""
"Extracts all messages of a translation catalog that match a given pattern\n"
"or belong to some given source files.\n"
msgstr ""
-#: src/msggrep.c:502
+#: src/msggrep.c:523
#, c-format, no-wrap
msgid ""
"Message selection:\n"
" [-N SOURCEFILE]... [-M DOMAINNAME]...\n"
-" [-K MSGID-PATTERN] [-T MSGSTR-PATTERN] [-C COMMENT-PATTERN]\n"
+" [-J MSGCTXT-PATTERN] [-K MSGID-PATTERN] [-T MSGSTR-PATTERN]\n"
+" [-C COMMENT-PATTERN] [-X EXTRACTED-COMMENT-PATTERN]\n"
"A message is selected if it comes from one of the specified source files,\n"
"or if it comes from one of the specified domains,\n"
+"or if -J is given and its context (msgctxt) matches MSGCTXT-PATTERN,\n"
"or if -K is given and its key (msgid or msgid_plural) matches MSGID-PATTERN,\n"
"or if -T is given and its translation (msgstr) matches MSGSTR-PATTERN,\n"
-"or if -C is given and the translator's comment matches COMMENT-PATTERN.\n"
+"or if -C is given and the translator's comment matches COMMENT-PATTERN,\n"
+"or if -X is given and the extracted comment matches EXTRACTED-COMMENT-PATTERN.\n"
"\n"
"When more than one selection criterion is specified, the set of selected\n"
"messages is the union of the selected messages of each criterion.\n"
"\n"
-"MSGID-PATTERN or MSGSTR-PATTERN or COMMENT-PATTERN syntax:\n"
+"MSGCTXT-PATTERN or MSGID-PATTERN or MSGSTR-PATTERN or COMMENT-PATTERN or\n"
+"EXTRACTED-COMMENT-PATTERN syntax:\n"
" [-E | -F] [-e PATTERN | -f FILE]...\n"
"PATTERNs are basic regular expressions by default, or extended regular\n"
"expressions if -E is given, or fixed strings if -F is given.\n"
"\n"
" -N, --location=SOURCEFILE select messages extracted from SOURCEFILE\n"
" -M, --domain=DOMAINNAME select messages belonging to domain DOMAINNAME\n"
+" -J, --msgctxt start of patterns for the msgctxt\n"
" -K, --msgid start of patterns for the msgid\n"
" -T, --msgstr start of patterns for the msgstr\n"
" -C, --comment start of patterns for the translator's comment\n"
+" -X, --extracted-comment start of patterns for the extracted comment\n"
" -E, --extended-regexp PATTERN is an extended regular expression\n"
" -F, --fixed-strings PATTERN is a set of newline-separated strings\n"
" -e, --regexp=PATTERN use PATTERN as a regular expression\n"
" -f, --file=FILE obtain PATTERN from FILE\n"
" -i, --ignore-case ignore case distinctions\n"
+" -v, --invert-match output only the messages that do not match any\n"
+" selection criterion\n"
msgstr ""
-#: src/msggrep.c:543
+#: src/msggrep.c:572
#, c-format
msgid ""
" --escape use C escapes in output, no extended chars\n"
msgstr ""
-#: src/msggrep.c:564
+#: src/msggrep.c:593
#, c-format
msgid " --sort-output generate sorted output\n"
msgstr ""
-#: src/msggrep.c:566
+#: src/msggrep.c:595
#, c-format
msgid " --sort-by-file sort output by file location\n"
msgstr ""
-#: src/msginit.c:296
+#: src/msginit.c:280
msgid ""
"You are in a language indifferent environment. Please set\n"
"your LANG environment variable, as described in the ABOUT-NLS\n"
"file. This is necessary so you can test your translations.\n"
msgstr ""
-#: src/msginit.c:324
+#: src/msginit.c:304
#, c-format
msgid ""
"Output file %s already exists.\n"
"the output .po file through the --output-file option.\n"
msgstr ""
-#: src/msginit.c:350
+#: src/msginit.c:330
#, c-format
msgid "Created %s.\n"
msgstr ""
-#: src/msginit.c:370
+#: src/msginit.c:350
#, c-format, no-wrap
msgid ""
"Creates a new PO file, initializing the meta information with values from the\n"
"user's environment.\n"
msgstr ""
-#: src/msginit.c:380
+#: src/msginit.c:360
#, c-format
msgid " -i, --input=INPUTFILE input POT file\n"
msgstr ""
-#: src/msginit.c:382
+#: src/msginit.c:362
#, c-format
msgid ""
"If no input file is given, the current directory is searched for the POT "
"If it is -, standard input is read.\n"
msgstr ""
-#: src/msginit.c:388
+#: src/msginit.c:368
#, c-format
msgid " -o, --output-file=FILE write output to specified PO file\n"
msgstr ""
-#: src/msginit.c:390
+#: src/msginit.c:370
#, c-format
msgid ""
"If no output file is given, it depends on the --locale option or the user's\n"
"locale setting. If it is -, the results are written to standard output.\n"
msgstr ""
-#: src/msginit.c:403
+#: src/msginit.c:383
#, c-format
msgid " -l, --locale=LL_CC set target locale\n"
msgstr ""
-#: src/msginit.c:405
+#: src/msginit.c:385
#, c-format
msgid ""
" --no-translator assume the PO file is automatically generated\n"
msgstr ""
-#: src/msginit.c:461
+#: src/msginit.c:441
msgid ""
"Found more than one .pot file.\n"
"Please specify the input .pot file through the --input option.\n"
msgstr ""
-#: src/msginit.c:469 src/msginit.c:474
+#: src/msginit.c:449 src/msginit.c:454
#, c-format
msgid "error reading current directory"
msgstr ""
-#: src/msginit.c:482
+#: src/msginit.c:462
msgid ""
"Found no .pot file in the current directory.\n"
"Please specify the input .pot file through the --input option.\n"
msgstr ""
-#: src/msginit.c:978 src/msginit.c:1045 src/msginit.c:1203
-#, c-format
-msgid "%s subprocess I/O error"
-msgstr ""
-
-#: src/msginit.c:990 src/msginit.c:1057 src/msginit.c:1215 src/msginit.c:1294
+#: src/msginit.c:794 src/msginit.c:862 src/msginit.c:1021 src/msginit.c:1100
#: src/read-csharp.c:83 src/read-java.c:81 src/read-resources.c:84
#: src/read-tcl.c:127 src/write-resources.c:105
#, c-format
msgid "%s subprocess failed with exit code %d"
msgstr ""
-#: src/msginit.c:1181
+#: src/msginit.c:986
msgid ""
"The new message catalog should contain your email address, so that users "
"can\n"
#. TRANSLATORS: "English" needs to be replaced by your language.
#. For example in it.po write "Traduzioni italiani ...",
#. *not* "Traduzioni inglesi ...".
-#: src/msginit.c:1567
+#: src/msginit.c:1373
#, c-format
msgid "English translations for %s package"
msgstr ""
-#: src/msgl-cat.c:176 src/msgl-charset.c:86 src/msgl-iconv.c:305
+#: src/msgl-cat.c:177 src/msgl-charset.c:88 src/msgl-iconv.c:215
#, c-format
msgid "present charset \"%s\" is not a portable encoding name"
msgstr ""
-#: src/msgl-cat.c:187 src/msgl-iconv.c:316
+#: src/msgl-cat.c:188 src/msgl-iconv.c:227
#, c-format
msgid "two different charsets \"%s\" and \"%s\" in input file"
msgstr ""
-#: src/msgl-cat.c:202
+#: src/msgl-cat.c:203
#, c-format
msgid ""
"input file `%s' doesn't contain a header entry with a charset specification"
msgstr ""
-#: src/msgl-cat.c:206
+#: src/msgl-cat.c:207
#, c-format
msgid ""
"domain \"%s\" in input file `%s' doesn't contain a header entry with a "
"charset specification"
msgstr ""
-#: src/msgl-cat.c:383 src/msgl-iconv.c:405
+#: src/msgl-cat.c:384 src/msgl-iconv.c:331
#, c-format
msgid "target charset \"%s\" is not a portable encoding name."
msgstr ""
-#: src/msgl-cat.c:433 src/msgl-cat.c:439 src/msgl-charset.c:92
-#: src/msgl-charset.c:127 src/write-po.c:851 src/write-po.c:917
-#: src/xgettext.c:2070
+#: src/msgl-cat.c:434 src/msgl-cat.c:440 src/msgl-charset.c:94
+#: src/msgl-charset.c:129 src/po-xerror.c:123 src/po-xerror.c:148
+#: src/xgettext.c:2773
#, c-format
msgid "warning: "
msgstr ""
-#: src/msgl-cat.c:434
+#: src/msgl-cat.c:435
#, c-format
msgid ""
"Input files contain messages in different encodings, UTF-8 among others.\n"
"Converting the output to UTF-8.\n"
msgstr ""
-#: src/msgl-cat.c:440
+#: src/msgl-cat.c:441
#, c-format
msgid ""
"Input files contain messages in different encodings, %s and %s among "
"To select a different output encoding, use the --to-code option.\n"
msgstr ""
-#: src/msgl-charset.c:93
+#: src/msgl-cat.c:479
#, c-format
msgid ""
-"Locale charset \"%s\" is different from\n"
-"input file charset \"%s\".\n"
-"Output of '%s' might be incorrect.\n"
+"Conversion of file %s from %s encoding to %s encoding\n"
+"changes some msgids or msgctxts.\n"
+"Either change all msgids and msgctxts to be pure ASCII, or ensure they are\n"
+"UTF-8 encoded from the beginning, i.e. already in your source code files.\n"
+msgstr ""
+
+#: src/msgl-charset.c:95
+#, c-format
+msgid ""
+"Locale charset \"%s\" is different from\n"
+"input file charset \"%s\".\n"
+"Output of '%s' might be incorrect.\n"
"Possible workarounds are:\n"
msgstr ""
-#: src/msgl-charset.c:100
+#: src/msgl-charset.c:102
#, c-format
msgid "- Set LC_ALL to a locale with encoding %s.\n"
msgstr ""
-#: src/msgl-charset.c:105
+#: src/msgl-charset.c:107
#, c-format
msgid ""
"- Convert the translation catalog to %s using 'msgconv',\n"
" then convert back to %s using 'msgconv'.\n"
msgstr ""
-#: src/msgl-charset.c:114
+#: src/msgl-charset.c:116
#, c-format
msgid ""
"- Set LC_ALL to a locale with encoding %s,\n"
" then convert back to %s using 'msgconv'.\n"
msgstr ""
-#: src/msgl-charset.c:128
+#: src/msgl-charset.c:130
#, c-format
msgid ""
"Locale charset \"%s\" is not a portable encoding name.\n"
"A possible workaround is to set LC_ALL=C.\n"
msgstr ""
-#: src/msgl-iconv.c:187 src/msgl-iconv.c:245
+#: src/msgl-check.c:92
+msgid "plural expression can produce negative values"
+msgstr ""
+
+#: src/msgl-check.c:102
+#, c-format
+msgid "nplurals = %lu but plural expression can produce values as large as %lu"
+msgstr ""
+
+#: src/msgl-check.c:143
+msgid "plural expression can produce division by zero"
+msgstr ""
+
+#: src/msgl-check.c:148
+msgid "plural expression can produce integer overflow"
+msgstr ""
+
+#: src/msgl-check.c:153
+msgid ""
+"plural expression can produce arithmetic exceptions, possibly division by "
+"zero"
+msgstr ""
+
+#: src/msgl-check.c:185
+#, c-format
+msgid "Try using the following, valid for %s:"
+msgstr ""
+
+#: src/msgl-check.c:268 src/msgl-check.c:292
+msgid "message catalog has plural form translations"
+msgstr ""
+
+#: src/msgl-check.c:270
+msgid "but header entry lacks a \"plural=EXPRESSION\" attribute"
+msgstr ""
+
+#: src/msgl-check.c:294
+msgid "but header entry lacks a \"nplurals=INTEGER\" attribute"
+msgstr ""
+
+#: src/msgl-check.c:330
+msgid "invalid nplurals value"
+msgstr ""
+
+#: src/msgl-check.c:352
+msgid "invalid plural expression"
+msgstr ""
+
+#: src/msgl-check.c:382 src/msgl-check.c:398
+#, c-format
+msgid "nplurals = %lu"
+msgstr ""
+
+#: src/msgl-check.c:384
+#, c-format
+msgid "but some messages have only one plural form"
+msgid_plural "but some messages have only %lu plural forms"
+msgstr[0] ""
+msgstr[1] ""
+
+#: src/msgl-check.c:400
+#, c-format
+msgid "but some messages have one plural form"
+msgid_plural "but some messages have %lu plural forms"
+msgstr[0] ""
+msgstr[1] ""
+
+#: src/msgl-check.c:420
+msgid ""
+"message catalog has plural form translations, but lacks a header entry with "
+"\"Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\""
+msgstr ""
+
+#: src/msgl-check.c:498
+msgid "`msgid' and `msgid_plural' entries do not both begin with '\\n'"
+msgstr ""
+
+#: src/msgl-check.c:506
+#, c-format
+msgid "`msgid' and `msgstr[%u]' entries do not both begin with '\\n'"
+msgstr ""
+
+#: src/msgl-check.c:521
+msgid "`msgid' and `msgstr' entries do not both begin with '\\n'"
+msgstr ""
+
+#: src/msgl-check.c:537
+msgid "`msgid' and `msgid_plural' entries do not both end with '\\n'"
+msgstr ""
+
+#: src/msgl-check.c:545
+#, c-format
+msgid "`msgid' and `msgstr[%u]' entries do not both end with '\\n'"
+msgstr ""
+
+#: src/msgl-check.c:560
+msgid "`msgid' and `msgstr' entries do not both end with '\\n'"
+msgstr ""
+
+#: src/msgl-check.c:572
+msgid "plural handling is a GNU gettext extension"
+msgstr ""
+
+#: src/msgl-check.c:614
#, c-format
-msgid "conversion failure"
+msgid "msgstr lacks the keyboard accelerator mark '%c'"
+msgstr ""
+
+#: src/msgl-check.c:624
+#, c-format
+msgid "msgstr has too many keyboard accelerator marks '%c'"
+msgstr ""
+
+#: src/msgl-check.c:664
+#, c-format
+msgid "headerfield `%s' missing in header\n"
msgstr ""
-#: src/msgl-iconv.c:339
+#: src/msgl-check.c:672
#, c-format
+msgid "header field `%s' should start at beginning of line\n"
+msgstr ""
+
+#: src/msgl-check.c:686
+msgid "some header fields still have the initial default value\n"
+msgstr ""
+
+#: src/msgl-check.c:699
+#, c-format
+msgid "field `%s' still has initial default value\n"
+msgstr ""
+
+#: src/msgl-iconv.c:65
+#, c-format
+msgid "%s: input is not valid in \"%s\" encoding"
+msgstr ""
+
+#: src/msgl-iconv.c:69
+#, c-format
+msgid "%s: error while converting from \"%s\" encoding to \"%s\" encoding"
+msgstr ""
+
+#: src/msgl-iconv.c:251
msgid "input file doesn't contain a header entry with a charset specification"
msgstr ""
-#: src/msgl-iconv.c:358 src/xgettext.c:597
+#: src/msgl-iconv.c:273 src/recode-sr-latin.c:284 src/recode-sr-latin.c:289
+#: src/x-python.c:618 src/xgettext.c:616
#, c-format
msgid ""
"Cannot convert from \"%s\" to \"%s\". %s relies on iconv(), and iconv() does "
"not support this conversion."
msgstr ""
-#: src/msgl-iconv.c:380
+#: src/msgl-iconv.c:302
#, c-format
msgid ""
"Conversion from \"%s\" to \"%s\" introduces duplicates: some different "
"msgids become equal."
msgstr ""
-#: src/msgl-iconv.c:385 src/xgettext.c:604
+#: src/msgl-iconv.c:308 src/recode-sr-latin.c:298 src/x-python.c:625
+#: src/xgettext.c:623
#, c-format
msgid ""
"Cannot convert from \"%s\" to \"%s\". %s relies on iconv(). This version was "
"built without iconv()."
msgstr ""
-#: src/msgmerge.c:335 src/msgmerge.c:341
+#: src/msgmerge.c:342 src/msgmerge.c:348
#, c-format
msgid "%s is only valid with %s"
msgstr ""
-#: src/msgmerge.c:395
+#: src/msgmerge.c:402
msgid "backup type"
msgstr ""
-#: src/msgmerge.c:430
+#: src/msgmerge.c:437
#, c-format, no-wrap
msgid ""
"Merges two Uniforum style .po files together. The def.po file is an\n"
"cannot be found, fuzzy matching is used to produce better results.\n"
msgstr ""
-#: src/msgmerge.c:447
+#: src/msgmerge.c:454
#, c-format
msgid " def.po translations referring to old sources\n"
msgstr ""
-#: src/msgmerge.c:449
+#: src/msgmerge.c:456
#, c-format
msgid " ref.pot references to new sources\n"
msgstr ""
-#: src/msgmerge.c:453
+#: src/msgmerge.c:460
#, c-format
msgid ""
" -C, --compendium=FILE additional library of message translations,\n"
" may be specified more than once\n"
msgstr ""
-#: src/msgmerge.c:459
+#: src/msgmerge.c:466
#, c-format
msgid ""
" -U, --update update def.po,\n"
" do nothing if def.po already up to date\n"
msgstr ""
-#: src/msgmerge.c:471
+#: src/msgmerge.c:478
#, c-format
msgid "Output file location in update mode:\n"
msgstr ""
-#: src/msgmerge.c:473
+#: src/msgmerge.c:480
#, c-format
msgid "The result is written back to def.po.\n"
msgstr ""
-#: src/msgmerge.c:475
+#: src/msgmerge.c:482
#, c-format
msgid " --backup=CONTROL make a backup of def.po\n"
msgstr ""
-#: src/msgmerge.c:477
+#: src/msgmerge.c:484
#, c-format
msgid " --suffix=SUFFIX override the usual backup suffix\n"
msgstr ""
-#: src/msgmerge.c:479
+#: src/msgmerge.c:486
#, c-format
msgid ""
"The version control method may be selected via the --backup option or "
" simple, never always make simple backups\n"
msgstr ""
-#: src/msgmerge.c:486
+#: src/msgmerge.c:493
#, c-format
msgid ""
"The backup suffix is `~', unless set with --suffix or the "
"environment variable.\n"
msgstr ""
-#: src/msgmerge.c:495
+#: src/msgmerge.c:502
#, c-format
msgid " -N, --no-fuzzy-matching do not use fuzzy matching\n"
msgstr ""
-#: src/msgmerge.c:544
+#: src/msgmerge.c:551
#, c-format
msgid " -q, --quiet, --silent suppress progress indicators\n"
msgstr ""
-#: src/msgmerge.c:1067
+#: src/msgmerge.c:1201
#, c-format
msgid "this message should define plural forms"
msgstr ""
-#: src/msgmerge.c:1090
+#: src/msgmerge.c:1224
#, c-format
msgid "this message should not define plural forms"
msgstr ""
-#: src/msgmerge.c:1256
+#: src/msgmerge.c:1418
#, c-format
msgid ""
"%sRead %ld old + %ld reference, merged %ld, fuzzied %ld, missing %ld, "
"obsolete %ld.\n"
msgstr ""
-#: src/msgmerge.c:1264
+#: src/msgmerge.c:1426
msgid " done.\n"
msgstr ""
-#: src/msgunfmt.c:291 src/msgunfmt.c:300 src/msgunfmt.c:323
+#: src/msgunfmt.c:293 src/msgunfmt.c:302 src/msgunfmt.c:325
#, c-format
msgid "%s and explicit file names are mutually exclusive"
msgstr ""
-#: src/msgunfmt.c:410
+#: src/msgunfmt.c:412
#, c-format
msgid "Usage: %s [OPTION] [FILE]...\n"
msgstr ""
-#: src/msgunfmt.c:414
+#: src/msgunfmt.c:416
#, c-format
msgid "Convert binary message catalog to Uniforum style .po file.\n"
msgstr ""
-#: src/msgunfmt.c:423
+#: src/msgunfmt.c:425
#, c-format
msgid ""
" -j, --java Java mode: input is a Java ResourceBundle "
"class\n"
msgstr ""
-#: src/msgunfmt.c:425
+#: src/msgunfmt.c:427
#, c-format
msgid " --csharp C# mode: input is a .NET .dll file\n"
msgstr ""
-#: src/msgunfmt.c:427
+#: src/msgunfmt.c:429
#, c-format
msgid ""
" --csharp-resources C# resources mode: input is a .NET .resources "
"file\n"
msgstr ""
-#: src/msgunfmt.c:429
+#: src/msgunfmt.c:431
#, c-format
msgid ""
" --tcl Tcl mode: input is a tcl/msgcat .msg file\n"
msgstr ""
-#: src/msgunfmt.c:434
+#: src/msgunfmt.c:436
#, c-format
msgid " FILE ... input .mo files\n"
msgstr ""
-#: src/msgunfmt.c:439
+#: src/msgunfmt.c:441
#, c-format
msgid "Input file location in Java mode:\n"
msgstr ""
-#: src/msgunfmt.c:445
+#: src/msgunfmt.c:447
#, c-format
msgid ""
"The class name is determined by appending the locale name to the resource "
"separated with an underscore. The class is located using the CLASSPATH.\n"
msgstr ""
-#: src/msgunfmt.c:450
+#: src/msgunfmt.c:452
#, c-format
msgid "Input file location in C# mode:\n"
msgstr ""
-#: src/msgunfmt.c:458
+#: src/msgunfmt.c:460
#, c-format
msgid ""
"The -l and -d options are mandatory. The .dll file is located in a\n"
"subdirectory of the specified directory whose name depends on the locale.\n"
msgstr ""
-#: src/msgunfmt.c:462
+#: src/msgunfmt.c:464
#, c-format
msgid "Input file location in Tcl mode:\n"
msgstr ""
-#: src/msgunfmt.c:468
+#: src/msgunfmt.c:470
#, c-format
msgid ""
"The -l and -d options are mandatory. The .msg file is located in the\n"
"specified directory.\n"
msgstr ""
-#: src/msgunfmt.c:488
+#: src/msgunfmt.c:490
#, c-format
msgid " -i, --indent write indented output style\n"
msgstr ""
-#: src/msgunfmt.c:490
+#: src/msgunfmt.c:492
#, c-format
msgid " --strict write strict uniforum style\n"
msgstr ""
-#: src/msguniq.c:309
+#: src/msguniq.c:311
#, c-format, no-wrap
msgid ""
"Unifies duplicate translations in a translation catalog.\n"
"will be cumulated. When using the --unique option, duplicates are discarded.\n"
msgstr ""
-#: src/msguniq.c:342
+#: src/msguniq.c:344
#, c-format
msgid " -d, --repeated print only duplicates\n"
msgstr ""
-#: src/msguniq.c:344
+#: src/msguniq.c:346
#, c-format
msgid ""
" -u, --unique print only unique messages, discard "
"duplicates\n"
msgstr ""
-#: src/po-charset.c:226 src/po-charset.c:296 src/po-charset.c:324
-#: src/po-charset.c:351
-#, c-format
-msgid "%s: warning: "
-msgstr ""
-
-#: src/po-charset.c:227
+#: src/po-charset.c:490
#, c-format
msgid ""
"Charset \"%s\" is not a portable encoding name.\n"
"Message conversion to user's charset might not work.\n"
msgstr ""
-#: src/po-charset.c:292 src/po-charset.c:322
-msgid "Continuing anyway, expect parse errors."
-msgstr ""
-
-#: src/po-charset.c:294
-msgid "Continuing anyway."
-msgstr ""
-
-#: src/po-charset.c:297
+#: src/po-charset.c:557
#, c-format
msgid ""
"Charset \"%s\" is not supported. %s relies on iconv(),\n"
"and iconv() does not support \"%s\".\n"
msgstr ""
-#: src/po-charset.c:306 src/po-charset.c:332
-#, c-format
+#: src/po-charset.c:564 src/po-charset.c:612
msgid ""
"Installing GNU libiconv and then reinstalling GNU gettext\n"
"would fix this problem.\n"
msgstr ""
-#: src/po-charset.c:311 src/po-charset.c:336
-#, c-format
-msgid "%s\n"
+#: src/po-charset.c:578 src/po-charset.c:616
+msgid "Continuing anyway, expect parse errors."
+msgstr ""
+
+#: src/po-charset.c:580
+msgid "Continuing anyway."
msgstr ""
-#: src/po-charset.c:325
+#: src/po-charset.c:607
#, c-format
msgid ""
"Charset \"%s\" is not supported. %s relies on iconv().\n"
"This version was built without iconv().\n"
msgstr ""
-#: src/po-charset.c:352
-#, c-format
+#: src/po-charset.c:644
msgid ""
"Charset missing in header.\n"
"Message conversion to user's charset will not work.\n"
msgid "inconsistent use of #~"
msgstr ""
-#: src/po-gram-gen.y:198
+#: src/po-gram-gen.y:201
#, c-format
msgid "missing `msgstr[]' section"
msgstr ""
-#: src/po-gram-gen.y:206
+#: src/po-gram-gen.y:209
#, c-format
msgid "missing `msgid_plural' section"
msgstr ""
-#: src/po-gram-gen.y:213
+#: src/po-gram-gen.y:216
#, c-format
msgid "missing `msgstr' section"
msgstr ""
-#: src/po-gram-gen.y:258
+#: src/po-gram-gen.y:278
#, c-format
msgid "first plural form has nonzero index"
msgstr ""
-#: src/po-gram-gen.y:260
+#: src/po-gram-gen.y:280
#, c-format
msgid "plural form has wrong index"
msgstr ""
-#: src/po-lex.h:93 src/po-lex.h:108 src/po-lex.h:128 src/po-lex.h:143
-#: src/po-lex.c:103 src/po-lex.c:132
+#: src/po-lex.c:93 src/po-lex.c:112
#, c-format
msgid "too many errors, aborting"
msgstr ""
-#: src/po-lex.c:458 src/po-lex.c:522 src/write-po.c:555 src/write-po.c:661
+#: src/po-lex.c:440 src/po-lex.c:510 src/write-po.c:554 src/write-po.c:669
#, c-format
msgid "invalid multibyte sequence"
msgstr ""
-#: src/po-lex.c:486
+#: src/po-lex.c:468
#, c-format
msgid "incomplete multibyte sequence at end of file"
msgstr ""
-#: src/po-lex.c:496
+#: src/po-lex.c:478
#, c-format
msgid "incomplete multibyte sequence at end of line"
msgstr ""
-#: src/po-lex.c:504
-#, c-format
+#: src/po-lex.c:490
msgid "iconv failure"
msgstr ""
-#: src/po-lex.c:737
+#: src/po-lex.c:731
#, c-format
msgid "keyword \"%s\" unknown"
msgstr ""
-#: src/po-lex.c:847
+#: src/po-lex.c:841
#, c-format
msgid "invalid control sequence"
msgstr ""
-#: src/po-lex.c:955
+#: src/po-lex.c:949
#, c-format
msgid "end-of-file within string"
msgstr ""
-#: src/po-lex.c:961
+#: src/po-lex.c:955
#, c-format
msgid "end-of-line within string"
msgstr ""
+#: src/po-lex.c:976
+#, c-format
+msgid "context separator <EOT> within string"
+msgstr ""
+
#: src/read-mo.c:98 src/read-mo.c:119 src/read-mo.c:165 src/read-mo.c:192
#, c-format
msgid "file \"%s\" is truncated"
msgid "file \"%s\" contains a not NUL terminated string, at %s"
msgstr ""
-#: src/read-po.c:318 src/xgettext.c:882
+#: src/read-po.c:322 src/xgettext.c:905
#, c-format
msgid "this file may not contain domain directives"
msgstr ""
-#: src/read-po.c:357
-#, c-format
+#: src/read-po.c:364
msgid "duplicate message definition"
msgstr ""
-#: src/read-po.c:358
-#, c-format
-msgid "...this is the location of the first definition"
+#: src/read-po.c:366
+msgid "this is the location of the first definition"
msgstr ""
-#: src/read-properties.c:215
-#, c-format
-msgid "%s:%lu: warning: invalid \\uxxxx syntax for Unicode character"
+#: src/read-properties.c:223
+msgid "warning: invalid \\uxxxx syntax for Unicode character"
msgstr ""
-#: src/read-stringtable.c:803
-#, c-format
-msgid "%s:%lu: warning: unterminated string"
+#: src/read-stringtable.c:804
+msgid "warning: unterminated string"
msgstr ""
-#: src/read-stringtable.c:814
-#, c-format
-msgid "%s:%lu: warning: syntax error"
+#: src/read-stringtable.c:812
+msgid "warning: syntax error"
+msgstr ""
+
+#: src/read-stringtable.c:873 src/read-stringtable.c:894
+msgid "warning: unterminated key/value pair"
+msgstr ""
+
+#: src/read-stringtable.c:939
+msgid "warning: syntax error, expected ';' after string"
+msgstr ""
+
+#: src/read-stringtable.c:948
+msgid "warning: syntax error, expected '=' or ';' after string"
msgstr ""
-#: src/read-stringtable.c:877 src/read-stringtable.c:899
+#: src/recode-sr-latin.c:117
#, c-format
-msgid "%s:%lu: warning: unterminated key/value pair"
+msgid "Written by %s and %s.\n"
+msgstr ""
+
+#. TRANSLATORS: This is a proper name. The last name is
+#. (with Unicode escapes) "\u0160egan" or (with HTML entities)
+#. "Šegan".
+#. This is a proper name. See the gettext manual, section Names.
+#: src/recode-sr-latin.c:121
+msgid "Danilo Segan"
msgstr ""
-#: src/read-stringtable.c:945
+#: src/recode-sr-latin.c:154
+#, c-format, no-wrap
+msgid "Recode Serbian text from Cyrillic to Latin script.\n"
+msgstr ""
+
+#: src/recode-sr-latin.c:157
+#, c-format, no-wrap
+msgid ""
+"The input text is read from standard input. The converted text is output to\n"
+"standard output.\n"
+msgstr ""
+
+#: src/recode-sr-latin.c:332
#, c-format
-msgid "%s:%lu: warning: syntax error, expected ';' after string"
+msgid "input is not valid in \"%s\" encoding"
msgstr ""
-#: src/read-stringtable.c:955
+#: src/recode-sr-latin.c:350
#, c-format
-msgid "%s:%lu: warning: syntax error, expected '=' or ';' after string"
+msgid "error while converting from \"%s\" encoding to \"%s\" encoding"
msgstr ""
-#: src/urlget.c:149
+#: src/urlget.c:147
#, c-format
msgid "expected two arguments"
msgstr ""
-#: src/urlget.c:166
+#: src/urlget.c:164
#, c-format
msgid "Usage: %s [OPTION] URL FILE\n"
msgstr ""
-#: src/urlget.c:171
+#: src/urlget.c:169
#, c-format, no-wrap
msgid ""
"Fetches and outputs the contents of an URL. If the URL cannot be accessed,\n"
"the locally accessible FILE is used instead.\n"
msgstr ""
-#: src/urlget.c:218
+#: src/urlget.c:216
#, c-format
msgid "error writing stdout"
msgstr ""
-#: src/write-csharp.c:665 src/write-java.c:982
-#, c-format
-msgid "cannot find a temporary directory, try setting $TMPDIR"
-msgstr ""
-
-#: src/write-csharp.c:675 src/write-java.c:992
-#, c-format
-msgid "cannot create a temporary directory using template \"%s\""
+#: src/write-csharp.c:618
+msgid ""
+"message catalog has context dependent translations\n"
+"but the C# .dll format doesn't support contexts\n"
msgstr ""
-#: src/write-csharp.c:726
+#: src/write-csharp.c:685
#, c-format
msgid "failed to create directory \"%s\""
msgstr ""
-#: src/write-csharp.c:761 src/write-java.c:1063 src/write-java.c:1076
+#: src/write-csharp.c:747
#, c-format
-msgid "failed to create \"%s\""
-msgstr ""
-
-#: src/write-csharp.c:769 src/write-java.c:1084 src/write-mo.c:726
-#: src/write-po.c:1126 src/write-qt.c:530 src/write-tcl.c:204
-#, c-format
-msgid "error while writing \"%s\" file"
+msgid "compilation of C# class failed, please try --verbose"
msgstr ""
-#: src/write-csharp.c:787
-#, c-format
-msgid "compilation of C# class failed, please try --verbose"
+#: src/write-java.c:920
+msgid ""
+"message catalog has context dependent translations\n"
+"but the Java ResourceBundle format doesn't support contexts\n"
msgstr ""
-#: src/write-java.c:1005
+#: src/write-java.c:945
#, c-format
msgid "not a valid Java class name: %s"
msgstr ""
-#: src/write-java.c:1097
+#: src/write-java.c:1029
#, c-format
msgid "compilation of Java class failed, please try --verbose or set $JAVAC"
msgstr ""
-#: src/write-mo.c:714 src/write-qt.c:518 src/write-tcl.c:194
+#: src/write-mo.c:807 src/write-qt.c:740 src/write-tcl.c:213
#, c-format
msgid "error while opening \"%s\" for writing"
msgstr ""
-#: src/write-po.c:606
+#: src/write-po.c:609
#, c-format
msgid ""
"internationalized messages should not contain the `\\%c' escape sequence"
msgstr ""
-#: src/write-po.c:852 src/write-po.c:918
+#: src/write-po.c:861 src/write-po.c:951
+#, c-format
+msgid ""
+"The following msgctxt contains non-ASCII characters.\n"
+"This will cause problems to translators who use a character encoding\n"
+"different from yours. Consider using a pure ASCII msgctxt instead.\n"
+"%s\n"
+msgstr ""
+
+#: src/write-po.c:873 src/write-po.c:963
#, c-format
msgid ""
"The following msgid contains non-ASCII characters.\n"
"%s\n"
msgstr ""
-#: src/write-po.c:1063
-#, c-format
+#: src/write-po.c:1114
msgid ""
"Cannot output multiple translation domains into a single file with Java ."
"properties syntax. Try using PO file syntax instead."
msgstr ""
-#: src/write-po.c:1065
-#, c-format
+#: src/write-po.c:1117
msgid ""
"Cannot output multiple translation domains into a single file with NeXTstep/"
"GNUstep .strings syntax."
msgstr ""
-#: src/write-po.c:1091
-#, c-format
+#: src/write-po.c:1144
+msgid ""
+"message catalog has context dependent translations, but the output format "
+"does not support them."
+msgstr ""
+
+#: src/write-po.c:1167
msgid ""
"message catalog has plural form translations, but the output format does not "
"support them. Try generating a Java class using \"msgfmt --java\", instead "
"of a properties file."
msgstr ""
-#: src/write-po.c:1095
-#, c-format
+#: src/write-po.c:1172
msgid ""
"message catalog has plural form translations, but the output format does not "
"support them."
msgstr ""
-#: src/write-po.c:1107
+#: src/write-po.c:1189
#, c-format
msgid "cannot create output file \"%s\""
msgstr ""
-#: src/write-po.c:1114
+#: src/write-po.c:1198
#, no-c-format
msgid "standard output"
msgstr ""
-#: src/write-qt.c:475
+#: src/write-qt.c:671
msgid ""
"message catalog has plural form translations\n"
"but the Qt message catalog format doesn't support plural handling\n"
msgstr ""
-#: src/write-qt.c:499
+#: src/write-qt.c:697
+msgid ""
+"message catalog has msgctxt strings containing characters outside ISO-8859-"
+"1\n"
+"but the Qt message catalog format supports Unicode only in the translated\n"
+"strings, not in the context strings\n"
+msgstr ""
+
+#: src/write-qt.c:721
msgid ""
"message catalog has msgid strings containing characters outside ISO-8859-1\n"
"but the Qt message catalog format supports Unicode only in the translated\n"
#: src/write-resources.c:132
msgid ""
+"message catalog has context dependent translations\n"
+"but the C# .resources format doesn't support contexts\n"
+msgstr ""
+
+#: src/write-resources.c:151
+msgid ""
"message catalog has plural form translations\n"
"but the C# .resources format doesn't support plural handling\n"
msgstr ""
#: src/write-tcl.c:158
msgid ""
+"message catalog has context dependent translations\n"
+"but the Tcl message catalog format doesn't support contexts\n"
+msgstr ""
+
+#: src/write-tcl.c:177
+msgid ""
"message catalog has plural form translations\n"
"but the Tcl message catalog format doesn't support plural handling\n"
msgstr ""
-#: src/x-awk.c:345 src/x-python.c:396
+#: src/x-awk.c:341 src/x-python.c:1059
#, c-format
msgid "%s:%d: warning: unterminated string"
msgstr ""
-#: src/x-awk.c:596
+#: src/x-awk.c:592
#, c-format
msgid "%s:%d: warning: unterminated regular expression"
msgstr ""
-#: src/x-c.c:1093 src/x-csharp.c:1498 src/x-java.c:826
+#: src/x-c.c:1153 src/x-csharp.c:1501 src/x-java.c:822
#, c-format
msgid "%s:%d: warning: unterminated character constant"
msgstr ""
-#: src/x-c.c:1117
+#: src/x-c.c:1177
#, c-format
msgid "%s:%d: warning: unterminated string literal"
msgstr ""
-#: src/x-csharp.c:218 src/xgettext.c:1672
+#: src/x-csharp.c:216 src/xgettext.c:1849
#, c-format
msgid ""
"Non-ASCII string at %s%s.\n"
"Please specify the source encoding through --from-code.\n"
msgstr ""
-#: src/x-csharp.c:260
+#: src/x-csharp.c:263
#, c-format
msgid ""
"%s:%d: Invalid multibyte sequence.\n"
"Please specify the correct source encoding through --from-code.\n"
msgstr ""
-#: src/x-csharp.c:276
+#: src/x-csharp.c:279
#, c-format
msgid ""
"%s:%d: Long incomplete multibyte sequence.\n"
"Please specify the correct source encoding through --from-code.\n"
msgstr ""
-#: src/x-csharp.c:288
+#: src/x-csharp.c:291
#, c-format
msgid ""
"%s:%d: Incomplete multibyte sequence at end of file.\n"
"Please specify the correct source encoding through --from-code.\n"
msgstr ""
-#: src/x-csharp.c:297
+#: src/x-csharp.c:300
#, c-format
msgid ""
"%s:%d: Incomplete multibyte sequence at end of line.\n"
"Please specify the correct source encoding through --from-code.\n"
msgstr ""
-#: src/x-csharp.c:306
+#: src/x-csharp.c:309 src/x-python.c:332
#, c-format
msgid "%s:%d: iconv failure"
msgstr ""
-#: src/x-csharp.c:329
+#: src/x-csharp.c:332
#, c-format
msgid ""
"%s:%d: Invalid multibyte sequence.\n"
"Please specify the source encoding through --from-code.\n"
msgstr ""
-#: src/x-csharp.c:1379 src/x-python.c:596
+#: src/x-csharp.c:1382 src/x-python.c:1259
#, c-format
msgid "%s:%d: warning: invalid Unicode character"
msgstr ""
-#: src/x-csharp.c:1501 src/x-java.c:829
+#: src/x-csharp.c:1504 src/x-java.c:825
#, c-format
msgid "%s:%d: warning: unterminated string constant"
msgstr ""
-#: src/x-csharp.c:2005 src/x-java.c:1323
+#: src/x-csharp.c:2008 src/x-java.c:1319
#, c-format
msgid "%s:%d: warning: ')' found where '}' was expected"
msgstr ""
-#: src/x-csharp.c:2029 src/x-java.c:1347
+#: src/x-csharp.c:2042 src/x-java.c:1353
#, c-format
msgid "%s:%d: warning: '}' found where ')' was expected"
msgstr ""
-#: src/x-glade.c:413 src/x-glade.c:420
+#: src/x-glade.c:429 src/x-glade.c:436
#, c-format
-msgid "%s:%d:%d: %s"
+msgid "%s:%lu:%lu: %s"
msgstr ""
-#: src/x-glade.c:447
+#: src/x-glade.c:463
#, c-format
msgid ""
"Language \"glade\" is not supported. %s relies on expat.\n"
"This version was built without expat.\n"
msgstr ""
-#: src/x-perl.c:311
+#: src/x-perl.c:307
#, c-format
msgid "%s:%d: can't find string terminator \"%s\" anywhere before EOF"
msgstr ""
-#: src/x-perl.c:1038
+#: src/x-perl.c:1032
#, c-format
msgid "%s:%d: missing right brace on \\x{HEXNUMBER}"
msgstr ""
-#: src/x-perl.c:1158
+#: src/x-perl.c:1152
#, c-format
msgid "%s:%d: invalid interpolation (\"\\l\") of 8bit character \"%c\""
msgstr ""
-#: src/x-perl.c:1178
+#: src/x-perl.c:1172
#, c-format
msgid "%s:%d: invalid interpolation (\"\\u\") of 8bit character \"%c\""
msgstr ""
-#: src/x-perl.c:1212
+#: src/x-perl.c:1206
#, c-format
msgid "%s:%d: invalid variable interpolation at \"%c\""
msgstr ""
-#: src/x-perl.c:1225
+#: src/x-perl.c:1219
#, c-format
msgid "%s:%d: invalid interpolation (\"\\L\") of 8bit character \"%c\""
msgstr ""
-#: src/x-perl.c:1242
+#: src/x-perl.c:1236
#, c-format
msgid "%s:%d: invalid interpolation (\"\\U\") of 8bit character \"%c\""
msgstr ""
-#: src/x-perl.c:3006
+#: src/x-python.c:234
#, c-format
-msgid "%s:%d: fatal: plural message seen before singular message\n"
+msgid ""
+"Non-ASCII string at %s%s.\n"
+"Please specify the source encoding through --from-code or through a comment\n"
+"as specified in http://www.python.org/peps/pep-0263.html.\n"
+msgstr ""
+
+#: src/x-python.c:282
+#, c-format
+msgid ""
+"%s:%d: Invalid multibyte sequence.\n"
+"Please specify the correct source encoding through --from-code or through a\n"
+"comment as specified in http://www.python.org/peps/pep-0263.html.\n"
+msgstr ""
+
+#: src/x-python.c:299
+#, c-format
+msgid ""
+"%s:%d: Long incomplete multibyte sequence.\n"
+"Please specify the correct source encoding through --from-code or through a\n"
+"comment as specified in http://www.python.org/peps/pep-0263.html.\n"
+msgstr ""
+
+#: src/x-python.c:312
+#, c-format
+msgid ""
+"%s:%d: Incomplete multibyte sequence at end of file.\n"
+"Please specify the correct source encoding through --from-code or through a\n"
+"comment as specified in http://www.python.org/peps/pep-0263.html.\n"
+msgstr ""
+
+#: src/x-python.c:322
+#, c-format
+msgid ""
+"%s:%d: Incomplete multibyte sequence at end of line.\n"
+"Please specify the correct source encoding through --from-code or through a\n"
+"comment as specified in http://www.python.org/peps/pep-0263.html.\n"
+msgstr ""
+
+#: src/x-python.c:355
+#, c-format
+msgid ""
+"%s:%d: Invalid multibyte sequence.\n"
+"Please specify the source encoding through --from-code or through a comment\n"
+"as specified in http://www.python.org/peps/pep-0263.html.\n"
+msgstr ""
+
+#: src/x-python.c:675
+#, c-format
+msgid "Unknown encoding \"%s\". Proceeding with ASCII instead."
msgstr ""
#: src/x-rst.c:107
msgid "%s:%d: invalid string expression"
msgstr ""
-#: src/x-sh.c:1015
+#: src/x-sh.c:1074
#, c-format
msgid ""
"%s:%lu: warning: the syntax $\"...\" is deprecated due to security reasons; "
"use eval_gettext instead"
msgstr ""
-#: src/xgettext.c:526
+#: src/xgettext.c:545
#, c-format
msgid "--join-existing cannot be used when output is written to stdout"
msgstr ""
-#: src/xgettext.c:531
+#: src/xgettext.c:550
#, c-format
msgid "xgettext cannot work without keywords to look for"
msgstr ""
-#: src/xgettext.c:674
+#: src/xgettext.c:693
#, c-format
msgid "warning: file `%s' extension `%s' is unknown; will try C"
msgstr ""
-#: src/xgettext.c:725
+#: src/xgettext.c:744
#, c-format
msgid "Extract translatable strings from given input files.\n"
msgstr ""
-#: src/xgettext.c:748
+#: src/xgettext.c:767
#, c-format
msgid ""
" -d, --default-domain=NAME use NAME.po for output (instead of messages."
"po)\n"
msgstr ""
-#: src/xgettext.c:750
+#: src/xgettext.c:769
#, c-format
msgid " -o, --output=FILE write output to specified file\n"
msgstr ""
-#: src/xgettext.c:752
+#: src/xgettext.c:771
#, c-format
msgid ""
" -p, --output-dir=DIR output files will be placed in directory DIR\n"
msgstr ""
-#: src/xgettext.c:757
+#: src/xgettext.c:776
#, c-format
msgid "Choice of input file language:\n"
msgstr ""
-#: src/xgettext.c:759
+#: src/xgettext.c:778
#, c-format
msgid ""
" -L, --language=NAME recognise the specified language\n"
" GCC-source, NXStringTable, RST, Glade)\n"
msgstr ""
-#: src/xgettext.c:765
+#: src/xgettext.c:784
#, c-format
msgid " -C, --c++ shorthand for --language=C++\n"
msgstr ""
-#: src/xgettext.c:767
+#: src/xgettext.c:786
#, c-format
msgid ""
"By default the language is guessed depending on the input file name "
"extension.\n"
msgstr ""
-#: src/xgettext.c:772
+#: src/xgettext.c:791
#, c-format
msgid ""
" --from-code=NAME encoding of input files\n"
" (except for Python, Tcl, Glade)\n"
msgstr ""
-#: src/xgettext.c:775
+#: src/xgettext.c:794
#, c-format
msgid "By default the input files are assumed to be in ASCII.\n"
msgstr ""
-#: src/xgettext.c:780
+#: src/xgettext.c:799
#, c-format
msgid " -j, --join-existing join messages with existing file\n"
msgstr ""
-#: src/xgettext.c:782
+#: src/xgettext.c:801
#, c-format
msgid " -x, --exclude-file=FILE.po entries from FILE.po are not extracted\n"
msgstr ""
-#: src/xgettext.c:784
+#: src/xgettext.c:803
#, c-format
msgid ""
" -c, --add-comments[=TAG] place comment block with TAG (or those\n"
" preceding keyword lines) in output file\n"
msgstr ""
-#: src/xgettext.c:788
+#: src/xgettext.c:807
#, c-format
msgid "Language specific options:\n"
msgstr ""
-#: src/xgettext.c:790
+#: src/xgettext.c:809
#, c-format
msgid " -a, --extract-all extract all strings\n"
msgstr ""
-#: src/xgettext.c:792 src/xgettext.c:799
+#: src/xgettext.c:811 src/xgettext.c:818
#, c-format
msgid ""
" (only languages C, C++, ObjectiveC, Shell,\n"
" C#, awk, Tcl, Perl, PHP, GCC-source, Glade)\n"
msgstr ""
-#: src/xgettext.c:796
+#: src/xgettext.c:815
#, c-format
msgid ""
" -k, --keyword[=WORD] additional keyword to be looked for (without\n"
" WORD means not to use default keywords)\n"
msgstr ""
-#: src/xgettext.c:803
+#: src/xgettext.c:822
#, c-format
msgid ""
" --flag=WORD:ARG:FLAG additional flag for strings inside the "
" number ARG of keyword WORD\n"
msgstr ""
-#: src/xgettext.c:806
+#: src/xgettext.c:825
#, c-format
msgid ""
" (only languages C, C++, ObjectiveC, Shell,\n"
" C#, awk, YCP, Tcl, Perl, PHP, GCC-source)\n"
msgstr ""
-#: src/xgettext.c:810
+#: src/xgettext.c:829
#, c-format
msgid " -T, --trigraphs understand ANSI C trigraphs for input\n"
msgstr ""
-#: src/xgettext.c:812
+#: src/xgettext.c:831
#, c-format
msgid " (only languages C, C++, ObjectiveC)\n"
msgstr ""
-#: src/xgettext.c:814
+#: src/xgettext.c:833
#, c-format
msgid " --qt recognize Qt format strings\n"
msgstr ""
-#: src/xgettext.c:816
+#: src/xgettext.c:835 src/xgettext.c:839
#, c-format
msgid " (only language C++)\n"
msgstr ""
-#: src/xgettext.c:818
+#: src/xgettext.c:837
+#, c-format
+msgid " --boost recognize Boost format strings\n"
+msgstr ""
+
+#: src/xgettext.c:841
#, c-format
msgid ""
" --debug more detailed formatstring recognition result\n"
msgstr ""
-#: src/xgettext.c:837
+#: src/xgettext.c:860
#, c-format
msgid " --properties-output write out a Java .properties file\n"
msgstr ""
-#: src/xgettext.c:852
+#: src/xgettext.c:875
#, c-format
msgid " --copyright-holder=STRING set copyright holder in output\n"
msgstr ""
-#: src/xgettext.c:854
+#: src/xgettext.c:877
#, c-format
msgid ""
" --foreign-user omit FSF copyright in output for foreign user\n"
msgstr ""
-#: src/xgettext.c:856
+#: src/xgettext.c:879
#, c-format
msgid ""
" --msgid-bugs-address=EMAIL@ADDRESS set report address for msgid bugs\n"
msgstr ""
-#: src/xgettext.c:858
+#: src/xgettext.c:881
#, c-format
msgid ""
" -m, --msgstr-prefix[=STRING] use STRING or \"\" as prefix for msgstr "
"entries\n"
msgstr ""
-#: src/xgettext.c:860
+#: src/xgettext.c:883
#, c-format
msgid ""
" -M, --msgstr-suffix[=STRING] use STRING or \"\" as suffix for msgstr "
"entries\n"
msgstr ""
-#: src/xgettext.c:1462
+#: src/xgettext.c:1644
#, c-format
msgid ""
"A --flag argument doesn't have the <keyword>:<argnum>:[pass-]<flag> syntax: %"
"s"
msgstr ""
-#: src/xgettext.c:1560
+#: src/xgettext.c:1745
msgid "standard input"
msgstr ""
-#: src/xgettext.c:1731 src/xgettext.c:1786
+#: src/xgettext.c:1925 src/xgettext.c:1958 src/xgettext.c:2016
#, c-format
msgid "%s%s: warning: "
msgstr ""
-#: src/xgettext.c:1733
+#: src/xgettext.c:1928
#, c-format
msgid ""
"Although being used in a format string position, the %s is not a valid %s "
"format string. Reason: %s\n"
msgstr ""
-#: src/xgettext.c:1733
+#: src/xgettext.c:1929
#, c-format
msgid ""
"Although declared as such, the %s is not a valid %s format string. Reason: %"
"s\n"
msgstr ""
-#: src/xgettext.c:1788
+#: src/xgettext.c:1960
+#, c-format
msgid ""
-"Empty msgid. It is reserved by GNU gettext:\n"
-"gettext(\"\") returns the header entry with\n"
-"meta information, not the empty string.\n"
+"'%s' format string with unnamed arguments cannot be properly localized:\n"
+"The translator cannot reorder the arguments.\n"
+"Please consider using a format string with named arguments,\n"
+"and a mapping instead of a tuple for the arguments.\n"
msgstr ""
-#: src/xgettext.c:2071
+#: src/xgettext.c:2018
msgid ""
-"The option --msgid-bugs-address was not specified.\n"
-"If you are using a `Makevars' file, please specify\n"
-"the MSGID_BUGS_ADDRESS variable there; otherwise please\n"
-"specify an --msgid-bugs-address command line option.\n"
+"Empty msgid. It is reserved by GNU gettext:\n"
+"gettext(\"\") returns the header entry with\n"
+"meta information, not the empty string.\n"
msgstr ""
-#: src/xgettext.c:2262
+#: src/xgettext.c:2621
#, c-format
-msgid "language `%s' unknown"
-msgstr ""
-
-#: src/user-email.sh.in:340
-msgid "Which is your email address?"
-msgstr ""
-
-#: src/user-email.sh.in:342
-msgid "Please choose the number, or enter your email address."
-msgstr ""
-
-#: src/user-email.sh.in:360 src/user-email.sh.in:384 src/user-email.sh.in:403
-msgid "Invalid email address: invalid character."
+msgid "ambiguous argument specification for keyword '%.*s'"
msgstr ""
-#: src/user-email.sh.in:362 src/user-email.sh.in:386 src/user-email.sh.in:405
-msgid "Invalid email address: need a fully qualified host name or domain name."
-msgstr ""
-
-#: src/user-email.sh.in:363 src/user-email.sh.in:387 src/user-email.sh.in:406
-msgid "Invalid email address: missing @"
+#: src/xgettext.c:2648
+#, c-format
+msgid "warning: missing context for keyword '%.*s'"
msgstr ""
-#: src/user-email.sh.in:372
-msgid "Is the following your email address?"
+#: src/xgettext.c:2673
+#, c-format
+msgid "warning: missing context for plural argument of keyword '%.*s'"
msgstr ""
-#: src/user-email.sh.in:374
-msgid "Please confirm by pressing Return, or enter your email address."
+#: src/xgettext.c:2694
+#, c-format
+msgid "context mismatch between singular and plural form"
msgstr ""
-#: src/user-email.sh.in:395
-msgid "Couldn't find out about your email address."
+#: src/xgettext.c:2774
+msgid ""
+"The option --msgid-bugs-address was not specified.\n"
+"If you are using a `Makevars' file, please specify\n"
+"the MSGID_BUGS_ADDRESS variable there; otherwise please\n"
+"specify an --msgid-bugs-address command line option.\n"
msgstr ""
-#: src/user-email.sh.in:397
-msgid "Please enter your email address."
+#: src/xgettext.c:2975
+#, c-format
+msgid "language `%s' unknown"
msgstr ""
# define COMMENT 257
# define DOMAIN 258
# define JUNK 259
-# define MSGID 260
-# define MSGID_PLURAL 261
-# define MSGSTR 262
-# define NAME 263
-# define NUMBER 264
-# define STRING 265
+# define MSGCTXT 260
+# define MSGID 261
+# define MSGID_PLURAL 262
+# define MSGSTR 263
+# define NAME 264
+# define NUMBER 265
+# define STRING 266
#line 20 "po-gram-gen.y"
po_gram_error_at_line (&(value2).pos, _("inconsistent use of #~"));
static inline void
-do_callback_message (char *msgid, lex_pos_ty *msgid_pos, char *msgid_plural,
+do_callback_message (char *msgctxt,
+ char *msgid, lex_pos_ty *msgid_pos, char *msgid_plural,
char *msgstr, size_t msgstr_len, lex_pos_ty *msgstr_pos,
bool obsolete)
{
/* Test for header entry. Ignore fuzziness of the header entry. */
- if (msgid[0] == '\0' && !obsolete)
+ if (msgctxt == NULL && msgid[0] == '\0' && !obsolete)
po_lex_charset_set (msgstr, gram_pos.file_name);
- po_callback_message (msgid, msgid_pos, msgid_plural,
+ po_callback_message (msgctxt,
+ msgid, msgid_pos, msgid_plural,
msgstr, msgstr_len, msgstr_pos,
false, obsolete);
}
-#line 123 "po-gram-gen.y"
+#line 126 "po-gram-gen.y"
#ifndef YYSTYPE
typedef union
{
-#define YYFINAL 28
+#define YYFINAL 32
#define YYFLAG -32768
-#define YYNTBASE 14
+#define YYNTBASE 15
/* YYTRANSLATE(YYLEX) -- Bison token number corresponding to YYLEX. */
-#define YYTRANSLATE(x) ((unsigned)(x) <= 265 ? yytranslate[x] : 22)
+#define YYTRANSLATE(x) ((unsigned)(x) <= 266 ? yytranslate[x] : 24)
/* YYTRANSLATE[YYLEX] -- Bison token number corresponding to YYLEX. */
static const char yytranslate[] =
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
- 2, 10, 2, 11, 2, 2, 2, 2, 2, 2,
+ 2, 11, 2, 12, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 2, 2, 2, 2,
2, 2, 2, 2, 2, 2, 1, 3, 4, 5,
- 6, 7, 8, 9, 12, 13
+ 6, 7, 8, 9, 10, 13, 14
};
#if YYDEBUG
static const short yyprhs[] =
{
0, 0, 1, 4, 7, 10, 13, 16, 21, 26,
- 30, 34, 37, 40, 42, 45, 51, 53, 56
+ 30, 34, 37, 39, 43, 46, 48, 51, 57, 59,
+ 62
};
static const short yyrhs[] =
{
- -1, 14, 21, 0, 14, 15, 0, 14, 16, 0,
- 14, 1, 0, 4, 13, 0, 6, 20, 8, 20,
- 0, 6, 20, 17, 18, 0, 6, 20, 17, 0,
- 6, 20, 18, 0, 6, 20, 0, 7, 20, 0,
- 19, 0, 18, 19, 0, 8, 10, 12, 11, 20,
- 0, 13, 0, 20, 13, 0, 3, 0
+ -1, 15, 23, 0, 15, 16, 0, 15, 17, 0,
+ 15, 1, 0, 4, 14, 0, 18, 22, 9, 22,
+ 0, 18, 22, 19, 20, 0, 18, 22, 19, 0,
+ 18, 22, 20, 0, 18, 22, 0, 7, 0, 6,
+ 22, 7, 0, 8, 22, 0, 21, 0, 20, 21,
+ 0, 9, 11, 13, 12, 22, 0, 14, 0, 22,
+ 14, 0, 3, 0
};
#endif
/* YYRLINE[YYN] -- source line where rule number YYN was defined. */
static const short yyrline[] =
{
- 0, 143, 144, 145, 146, 147, 151, 158, 176, 194,
- 202, 210, 219, 230, 234, 249, 271, 278, 289
+ 0, 146, 147, 148, 149, 150, 154, 161, 179, 197,
+ 205, 213, 222, 228, 239, 250, 254, 269, 291, 298,
+ 309
};
#endif
/* YYTNAME[TOKEN_NUM] -- String name of the token TOKEN_NUM. */
static const char *const yytname[] =
{
- "$", "error", "$undefined.", "COMMENT", "DOMAIN", "JUNK", "MSGID",
- "MSGID_PLURAL", "MSGSTR", "NAME", "'['", "']'", "NUMBER", "STRING",
- "msgfmt", "domain", "message", "msgid_pluralform", "pluralform_list",
- "pluralform", "string_list", "comment", 0
+ "$", "error", "$undefined.", "COMMENT", "DOMAIN", "JUNK", "MSGCTXT",
+ "MSGID", "MSGID_PLURAL", "MSGSTR", "NAME", "'['", "']'", "NUMBER",
+ "STRING", "msgfmt", "domain", "message", "message_intro",
+ "msgid_pluralform", "pluralform_list", "pluralform", "string_list",
+ "comment", 0
};
#endif
/* YYR1[YYN] -- Symbol number of symbol that rule YYN derives. */
static const short yyr1[] =
{
- 0, 14, 14, 14, 14, 14, 15, 16, 16, 16,
- 16, 16, 17, 18, 18, 19, 20, 20, 21
+ 0, 15, 15, 15, 15, 15, 16, 17, 17, 17,
+ 17, 17, 18, 18, 19, 20, 20, 21, 22, 22,
+ 23
};
/* YYR2[YYN] -- Number of symbols composing right hand side of rule YYN. */
static const short yyr2[] =
{
0, 0, 2, 2, 2, 2, 2, 4, 4, 3,
- 3, 2, 2, 1, 2, 5, 1, 2, 1
+ 3, 2, 1, 3, 2, 1, 2, 5, 1, 2,
+ 1
};
/* YYDEFACT[S] -- default rule to reduce with in state S when YYTABLE
error. */
static const short yydefact[] =
{
- 1, 0, 5, 18, 0, 0, 3, 4, 2, 6,
- 16, 11, 0, 0, 17, 9, 10, 13, 12, 0,
- 7, 0, 8, 14, 0, 0, 15, 0, 0
+ 1, 0, 5, 20, 0, 0, 12, 3, 4, 0,
+ 2, 6, 18, 0, 11, 13, 19, 0, 0, 9,
+ 10, 15, 14, 0, 7, 0, 8, 16, 0, 0,
+ 17, 0, 0
};
static const short yydefgoto[] =
{
- 1, 6, 7, 15, 16, 17, 11, 8
+ 1, 7, 8, 9, 19, 20, 21, 13, 10
};
static const short yypact[] =
{
- -32768, 2,-32768,-32768, -1, 1,-32768,-32768,-32768,-32768,
- -32768, 3, 1, -6,-32768, 9, 9,-32768, 5, 7,
- 5, 10, 9,-32768, 11, 1, 5, 21,-32768
+ -32768, 10,-32768,-32768, -10, 4,-32768,-32768,-32768, 4,
+ -32768,-32768,-32768, -2, -7,-32768,-32768, 4, -8, 13,
+ 13,-32768, 5, 11, 5, 12, 13,-32768, 14, 4,
+ 5, 25,-32768
};
static const short yypgoto[] =
{
- -32768,-32768,-32768,-32768, 8, -7, -12,-32768
+ -32768,-32768,-32768,-32768,-32768, 8, -5, -9,-32768
};
-#define YYLAST 23
+#define YYLAST 27
static const short yytable[] =
{
- 18, 20, 27, 2, 19, 3, 4, 10, 5, 23,
- 12, 13, 9, 26, 10, 23, 14, 21, 14, 24,
- 19, 28, 25, 22
+ 14, 17, 18, 23, 11, 15, 12, 16, 22, 24,
+ 31, 2, 16, 3, 4, 27, 5, 6, 12, 16,
+ 30, 27, 25, 23, 28, 32, 29, 26
};
static const short yycheck[] =
{
- 12, 13, 0, 1, 10, 3, 4, 13, 6, 16,
- 7, 8, 13, 25, 13, 22, 13, 8, 13, 12,
- 10, 0, 11, 15
+ 9, 8, 9, 11, 14, 7, 14, 14, 17, 18,
+ 0, 1, 14, 3, 4, 20, 6, 7, 14, 14,
+ 29, 26, 9, 11, 13, 0, 12, 19
};
/* -*-C-*- Note some compilers choke on comments on `#line' lines. */
-#line 3 "/usr/local/share/bison/bison.simple"
+#line 3 "bison.simple"
/* Skeleton output parser for bison,
# endif
#endif
\f
-#line 315 "/usr/local/share/bison/bison.simple"
+#line 315 "bison.simple"
/* The user can define YYPARSE_PARAM as the name of an argument to be passed
switch (yyn) {
case 6:
-#line 152 "po-gram-gen.y"
+#line 155 "po-gram-gen.y"
{
po_callback_domain (yyvsp[0].string.string);
}
break;
case 7:
-#line 159 "po-gram-gen.y"
+#line 162 "po-gram-gen.y"
{
char *string2 = string_list_concat_destroy (&yyvsp[-2].stringlist.stringlist);
char *string4 = string_list_concat_destroy (&yyvsp[0].stringlist.stringlist);
- check_obsolete (yyvsp[-3].pos, yyvsp[-2].stringlist);
- check_obsolete (yyvsp[-3].pos, yyvsp[-1].pos);
- check_obsolete (yyvsp[-3].pos, yyvsp[0].stringlist);
- if (!yyvsp[-3].pos.obsolete || pass_obsolete_entries)
- do_callback_message (string2, &yyvsp[-3].pos.pos, NULL,
+ check_obsolete (yyvsp[-3].string, yyvsp[-2].stringlist);
+ check_obsolete (yyvsp[-3].string, yyvsp[-1].pos);
+ check_obsolete (yyvsp[-3].string, yyvsp[0].stringlist);
+ if (!yyvsp[-3].string.obsolete || pass_obsolete_entries)
+ do_callback_message (yyvsp[-3].string.string, string2, &yyvsp[-3].string.pos, NULL,
string4, strlen (string4) + 1, &yyvsp[-1].pos.pos,
- yyvsp[-3].pos.obsolete);
+ yyvsp[-3].string.obsolete);
else
{
free (string2);
}
break;
case 8:
-#line 177 "po-gram-gen.y"
+#line 180 "po-gram-gen.y"
{
char *string2 = string_list_concat_destroy (&yyvsp[-2].stringlist.stringlist);
- check_obsolete (yyvsp[-3].pos, yyvsp[-2].stringlist);
- check_obsolete (yyvsp[-3].pos, yyvsp[-1].string);
- check_obsolete (yyvsp[-3].pos, yyvsp[0].rhs);
- if (!yyvsp[-3].pos.obsolete || pass_obsolete_entries)
- do_callback_message (string2, &yyvsp[-3].pos.pos, yyvsp[-1].string.string,
+ check_obsolete (yyvsp[-3].string, yyvsp[-2].stringlist);
+ check_obsolete (yyvsp[-3].string, yyvsp[-1].string);
+ check_obsolete (yyvsp[-3].string, yyvsp[0].rhs);
+ if (!yyvsp[-3].string.obsolete || pass_obsolete_entries)
+ do_callback_message (yyvsp[-3].string.string, string2, &yyvsp[-3].string.pos, yyvsp[-1].string.string,
yyvsp[0].rhs.rhs.msgstr, yyvsp[0].rhs.rhs.msgstr_len, &yyvsp[0].rhs.pos,
- yyvsp[-3].pos.obsolete);
+ yyvsp[-3].string.obsolete);
else
{
free (string2);
}
break;
case 9:
-#line 195 "po-gram-gen.y"
+#line 198 "po-gram-gen.y"
{
- check_obsolete (yyvsp[-2].pos, yyvsp[-1].stringlist);
- check_obsolete (yyvsp[-2].pos, yyvsp[0].string);
- po_gram_error_at_line (&yyvsp[-2].pos.pos, _("missing `msgstr[]' section"));
+ check_obsolete (yyvsp[-2].string, yyvsp[-1].stringlist);
+ check_obsolete (yyvsp[-2].string, yyvsp[0].string);
+ po_gram_error_at_line (&yyvsp[-2].string.pos, _("missing `msgstr[]' section"));
string_list_destroy (&yyvsp[-1].stringlist.stringlist);
free (yyvsp[0].string.string);
}
break;
case 10:
-#line 203 "po-gram-gen.y"
+#line 206 "po-gram-gen.y"
{
- check_obsolete (yyvsp[-2].pos, yyvsp[-1].stringlist);
- check_obsolete (yyvsp[-2].pos, yyvsp[0].rhs);
- po_gram_error_at_line (&yyvsp[-2].pos.pos, _("missing `msgid_plural' section"));
+ check_obsolete (yyvsp[-2].string, yyvsp[-1].stringlist);
+ check_obsolete (yyvsp[-2].string, yyvsp[0].rhs);
+ po_gram_error_at_line (&yyvsp[-2].string.pos, _("missing `msgid_plural' section"));
string_list_destroy (&yyvsp[-1].stringlist.stringlist);
free (yyvsp[0].rhs.rhs.msgstr);
}
break;
case 11:
-#line 211 "po-gram-gen.y"
+#line 214 "po-gram-gen.y"
{
- check_obsolete (yyvsp[-1].pos, yyvsp[0].stringlist);
- po_gram_error_at_line (&yyvsp[-1].pos.pos, _("missing `msgstr' section"));
+ check_obsolete (yyvsp[-1].string, yyvsp[0].stringlist);
+ po_gram_error_at_line (&yyvsp[-1].string.pos, _("missing `msgstr' section"));
string_list_destroy (&yyvsp[0].stringlist.stringlist);
}
break;
case 12:
-#line 220 "po-gram-gen.y"
+#line 223 "po-gram-gen.y"
+{
+ yyval.string.string = NULL;
+ yyval.string.pos = yyvsp[0].pos.pos;
+ yyval.string.obsolete = yyvsp[0].pos.obsolete;
+ }
+ break;
+case 13:
+#line 229 "po-gram-gen.y"
+{
+ check_obsolete (yyvsp[-2].pos, yyvsp[-1].stringlist);
+ check_obsolete (yyvsp[-2].pos, yyvsp[0].pos);
+ yyval.string.string = string_list_concat_destroy (&yyvsp[-1].stringlist.stringlist);
+ yyval.string.pos = yyvsp[0].pos.pos;
+ yyval.string.obsolete = yyvsp[0].pos.obsolete;
+ }
+ break;
+case 14:
+#line 240 "po-gram-gen.y"
{
check_obsolete (yyvsp[-1].pos, yyvsp[0].stringlist);
plural_counter = 0;
yyval.string.obsolete = yyvsp[-1].pos.obsolete;
}
break;
-case 13:
-#line 231 "po-gram-gen.y"
+case 15:
+#line 251 "po-gram-gen.y"
{
yyval.rhs = yyvsp[0].rhs;
}
break;
-case 14:
-#line 235 "po-gram-gen.y"
+case 16:
+#line 255 "po-gram-gen.y"
{
check_obsolete (yyvsp[-1].rhs, yyvsp[0].rhs);
yyval.rhs.rhs.msgstr = (char *) xmalloc (yyvsp[-1].rhs.rhs.msgstr_len + yyvsp[0].rhs.rhs.msgstr_len);
yyval.rhs.obsolete = yyvsp[-1].rhs.obsolete;
}
break;
-case 15:
-#line 250 "po-gram-gen.y"
+case 17:
+#line 270 "po-gram-gen.y"
{
check_obsolete (yyvsp[-4].pos, yyvsp[-3].pos);
check_obsolete (yyvsp[-4].pos, yyvsp[-2].number);
yyval.rhs.obsolete = yyvsp[-4].pos.obsolete;
}
break;
-case 16:
-#line 272 "po-gram-gen.y"
+case 18:
+#line 292 "po-gram-gen.y"
{
string_list_init (&yyval.stringlist.stringlist);
string_list_append (&yyval.stringlist.stringlist, yyvsp[0].string.string);
yyval.stringlist.obsolete = yyvsp[0].string.obsolete;
}
break;
-case 17:
-#line 279 "po-gram-gen.y"
+case 19:
+#line 299 "po-gram-gen.y"
{
check_obsolete (yyvsp[-1].stringlist, yyvsp[0].string);
yyval.stringlist.stringlist = yyvsp[-1].stringlist.stringlist;
yyval.stringlist.obsolete = yyvsp[-1].stringlist.obsolete;
}
break;
-case 18:
-#line 290 "po-gram-gen.y"
+case 20:
+#line 310 "po-gram-gen.y"
{
po_callback_comment_dispatcher (yyvsp[0].string.string);
}
break;
}
-#line 705 "/usr/local/share/bison/bison.simple"
+#line 705 "bison.simple"
\f
yyvsp -= yylen;
#endif
return yyresult;
}
-#line 294 "po-gram-gen.y"
+#line 314 "po-gram-gen.y"
-#ifndef BISON_Y_TAB_H
-# define BISON_Y_TAB_H
+#ifndef BISON_PO_GRAM_GEN_H
+# define BISON_PO_GRAM_GEN_H
#ifndef YYSTYPE
typedef union
# define COMMENT 257
# define DOMAIN 258
# define JUNK 259
-# define MSGID 260
-# define MSGID_PLURAL 261
-# define MSGSTR 262
-# define NAME 263
-# define NUMBER 264
-# define STRING 265
+# define MSGCTXT 260
+# define MSGID 261
+# define MSGID_PLURAL 262
+# define MSGSTR 263
+# define NAME 264
+# define NUMBER 265
+# define STRING 266
extern YYSTYPE yylval;
-#endif /* not BISON_Y_TAB_H */
+#endif /* not BISON_PO_GRAM_GEN_H */
msgid " (only language C++)\n"
msgstr ""
+#, c-format
+msgid " --boost recognize Boost format strings\n"
+msgstr ""
+
#, c-format
msgid ""
" --debug more detailed formatstring recognition result\n"
"s\n"
msgstr ""
+#, c-format
+msgid ""
+"'%s' format string with unnamed arguments cannot be properly localized:\n"
+"The translator cannot reorder the arguments.\n"
+"Please consider using a format string with named arguments,\n"
+"and a mapping instead of a tuple for the arguments.\n"
+msgstr ""
+
msgid ""
"Empty msgid. It is reserved by GNU gettext:\n"
"gettext(\"\") returns the header entry with\n"
"meta information, not the empty string.\n"
msgstr ""
+#, c-format
+msgid "ambiguous argument specification for keyword '%.*s'"
+msgstr ""
+
+#, c-format
+msgid "warning: missing context for keyword '%.*s'"
+msgstr ""
+
+#, c-format
+msgid "warning: missing context for plural argument of keyword '%.*s'"
+msgstr ""
+
+msgid "context mismatch between singular and plural form"
+msgstr ""
+
msgid "warning: "
msgstr ""
msgid "the argument to %s should be a single punctuation character"
msgstr ""
+#, c-format
+msgid "invalid endianness: %s"
+msgstr ""
+
#, c-format
msgid "%s requires a \"-d directory\" specification"
msgstr ""
msgid "%s is only valid with %s, %s or %s"
msgstr ""
+#, c-format
+msgid "found %d fatal error"
+msgid_plural "found %d fatal errors"
+msgstr[0] ""
+msgstr[1] ""
+
#, c-format
msgid "%d translated message"
msgid_plural "%d translated messages"
msgid " -v, --verbose increase verbosity level\n"
msgstr ""
-msgid "plural expression can produce negative values"
-msgstr ""
-
-#, c-format
-msgid "nplurals = %lu but plural expression can produce values as large as %lu"
-msgstr ""
-
-#, c-format
-msgid "plural expression can produce division by zero"
-msgstr ""
-
-#, c-format
-msgid "plural expression can produce integer overflow"
-msgstr ""
-
-#, c-format
-msgid ""
-"plural expression can produce arithmetic exceptions, possibly division by "
-"zero"
-msgstr ""
-
-msgid "message catalog has plural form translations..."
-msgstr ""
-
-msgid "...but header entry lacks a \"plural=EXPRESSION\" attribute"
-msgstr ""
-
-msgid "...but header entry lacks a \"nplurals=INTEGER\" attribute"
-msgstr ""
-
-msgid "invalid nplurals value"
-msgstr ""
-
-msgid "invalid plural expression"
-msgstr ""
-
-#, c-format
-msgid "nplurals = %lu..."
-msgstr ""
-
-#, c-format
-msgid "...but some messages have only one plural form"
-msgid_plural "...but some messages have only %lu plural forms"
-msgstr[0] ""
-msgstr[1] ""
-
-#, c-format
-msgid "...but some messages have one plural form"
-msgid_plural "...but some messages have %lu plural forms"
-msgstr[0] ""
-msgstr[1] ""
-
-#, c-format
-msgid "Try using the following, valid for %s:\n"
-msgstr ""
-
-msgid ""
-"message catalog has plural form translations, but lacks a header entry with "
-"\"Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\""
-msgstr ""
-
-msgid "`msgid' and `msgid_plural' entries do not both begin with '\\n'"
-msgstr ""
-
-#, c-format
-msgid "`msgid' and `msgstr[%u]' entries do not both begin with '\\n'"
-msgstr ""
-
-msgid "`msgid' and `msgstr' entries do not both begin with '\\n'"
-msgstr ""
-
-msgid "`msgid' and `msgid_plural' entries do not both end with '\\n'"
-msgstr ""
-
-#, c-format
-msgid "`msgid' and `msgstr[%u]' entries do not both end with '\\n'"
-msgstr ""
-
-msgid "`msgid' and `msgstr' entries do not both end with '\\n'"
-msgstr ""
-
-msgid "plural handling is a GNU gettext extension"
-msgstr ""
-
-#, c-format
-msgid "msgstr lacks the keyboard accelerator mark '%c'"
-msgstr ""
-
-#, c-format
-msgid "msgstr has too many keyboard accelerator marks '%c'"
-msgstr ""
-
-#, c-format
-msgid "headerfield `%s' missing in header\n"
-msgstr ""
-
-#, c-format
-msgid "header field `%s' should start at beginning of line\n"
-msgstr ""
-
-msgid "some header fields still have the initial default value\n"
-msgstr ""
-
-#, c-format
-msgid "field `%s' still has initial default value\n"
-msgstr ""
-
msgid "warning: PO file header missing or invalid\n"
msgstr ""
projects / thirdparty / gettext.git / commitdiff
