/ - Diff - Application: gvSIG desktop - gvSIG

Revision 7940

     @echo off
     color F0
     PROMPT=$g
     echo Extraemos las calves de los ficheros cpp...
     gettext\bin\xgettext -C -n -k_ -o launcher.pot launcher.cpp statusdialog.cpp
     echo Fusionando con Idioma da...
     IF NOT EXIST da\launcher.po copy launcher.pot da\launcher.po
     gettext\bin\msgmerge.exe da\launcher.po launcher.pot -o da\launcher.po
     echo Fusionando con Idioma de...
     IF NOT EXIST de\launcher.po copy launcher.pot de\launcher.po
     gettext\bin\msgmerge.exe de\launcher.po launcher.pot -o de\launcher.po
     echo Fusionando con Idioma es...
     IF NOT EXIST es\launcher.po copy launcher.pot es\launcher.po
     gettext\bin\msgmerge.exe es\launcher.po launcher.pot -o es\launcher.po
     echo Fusionando con Idioma fr...
     IF NOT EXIST fr\launcher.po copy launcher.pot fr\launcher.po
     gettext\bin\msgmerge.exe fr\launcher.po launcher.pot -o fr\launcher.po
     echo Fusionando con Idioma it...
     IF NOT EXIST it\launcher.po copy launcher.pot it\launcher.po
     gettext\bin\msgmerge.exe it\launcher.po launcher.pot -o it\launcher.po
     echo Fusionando con Idioma nl...
     IF NOT EXIST nl\launcher.po copy launcher.pot nl\launcher.po
     gettext\bin\msgmerge.exe nl\launcher.po launcher.pot -o nl\launcher.po
     echo Fusionando con Idioma pt-BR...
     IF NOT EXIST pt-BR\launcher.po copy launcher.pot pt-BR\launcher.po
     gettext\bin\msgmerge.exe pt-BR\launcher.po launcher.pot -o pt-BR\launcher.po
     echo Termiando.

     <html>
     <head>
     <meta name="generator" content="groff -Thtml, see www.gnu.org">
     <meta name="Content-Style" content="text/css">
     <title>MSGEN</title>
     </head>
     <body>
     <h1 align=center>MSGEN</h1>
     <a href="#NAME">NAME</a><br>
     <a href="#SYNOPSIS">SYNOPSIS</a><br>
     <a href="#DESCRIPTION">DESCRIPTION</a><br>
     <a href="#AUTHOR">AUTHOR</a><br>
     <a href="#REPORTING BUGS">REPORTING BUGS</a><br>
     <a href="#COPYRIGHT">COPYRIGHT</a><br>
     <a href="#SEE ALSO">SEE ALSO</a><br>
     <hr>
     <!-- Creator     : groff version 1.17.2 -->
     <a name="NAME"></a>
     <h2>NAME</h2>
     <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%">
     msgen - create English message catalog</td></table>
     <a name="SYNOPSIS"></a>
     <h2>SYNOPSIS</h2>
     <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>msgen</b> [<i>OPTION</i>] <i>INPUTFILE</i></td></table>
     <a name="DESCRIPTION"></a>
     <h2>DESCRIPTION</h2>
     <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%">
     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 translation that is identical to the
     msgid.</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%">
     Mandatory arguments to long options are mandatory for short
     options too.</td></table>
     <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>Input file location:</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="10%"></td><td width="90%">
     INPUTFILE</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%">
     input PO or POT file</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>-D</b>, <b>--directory</b>=<i>DIRECTORY</i></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%">
     add DIRECTORY to list for input files search</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%">
     If input file is -, standard input is read.</td></table>
     <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>Output file location:</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="10%"></td><td width="90%">
     <b>-o</b>, <b>--output-file</b>=<i>FILE</i></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%">
     write output to specified file</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%">
     The results are written to standard output if no output file
     is specified or if it is -.</td></table>
     <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>Input file syntax:</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="10%"></td><td width="90%">
     <b>-P</b>, <b>--properties-input</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%">
     input file is in Java .properties syntax</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>--stringtable-input</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%">
     input file is in NeXTstep/GNUstep .strings
     syntax</td></table>
     <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>Output details:</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="10%"></td><td width="90%">
     <b>-e</b>, <b>--no-escape</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%">
     do not use C escapes in output (default)</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>-E</b>, <b>--escape</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%">
     use C escapes in output, no extended chars</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>--force-po</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%">
     write PO file even if empty</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>-i</b>, <b>--indent</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%">
     indented output style</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>--no-location</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%">
     suppress '#: filename:line' lines</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>--add-location</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%">
     preserve '#: filename:line' lines (default)</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>--strict</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%">
     strict Uniforum output style</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>-p</b>, <b>--properties-output</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%">
     write out a Java .properties file</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>--stringtable-output</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%">
     write out a NeXTstep/GNUstep .strings file</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>-w</b>, <b>--width</b>=<i>NUMBER</i></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%">
     set output page width</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>--no-wrap</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%">
     do not break long message lines, longer than the output page
     width, into several lines</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>-s</b>, <b>--sort-output</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%">
     generate sorted output</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>-F</b>, <b>--sort-by-file</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%">
     sort output by file location</td></table>
     <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>Informative output:</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="10%"></td><td width="90%">
     <b>-h</b>, <b>--help</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%">
     display this help and exit</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>--version</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 version information and exit</td></table>
     <a name="AUTHOR"></a>
     <h2>AUTHOR</h2>
     <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%">
     Written by Bruno Haible.</td></table>
     <a name="REPORTING BUGS"></a>
     <h2>REPORTING BUGS</h2>
     <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%">
     Report bugs to &lt;bug-gnu-gettext@gnu.org&gt;.</td></table>
     <a name="COPYRIGHT"></a>
     <h2>COPYRIGHT</h2>
     <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%">
     Copyright 2001-2003 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></table>
     <a name="SEE ALSO"></a>
     <h2>SEE ALSO</h2>
     <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%">
     The full documentation for <b>msgen</b> is maintained as a
     Texinfo manual. If the <b>info</b> and <b>msgen</b> programs
     are properly installed at your site, the
     command</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%">
     <b>info msgen</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="10%"></td><td width="90%">
     should give you access to the complete manual.</td></table>
     <hr>
     </body>
     </html>

     <html>
     <head>
     <meta name="generator" content="groff -Thtml, see www.gnu.org">
     <meta name="Content-Style" content="text/css">
     <title>ENVSUBST</title>
     </head>
     <body>
     <h1 align=center>ENVSUBST</h1>
     <a href="#NAME">NAME</a><br>
     <a href="#SYNOPSIS">SYNOPSIS</a><br>
     <a href="#DESCRIPTION">DESCRIPTION</a><br>
     <a href="#AUTHOR">AUTHOR</a><br>
     <a href="#REPORTING BUGS">REPORTING BUGS</a><br>
     <a href="#COPYRIGHT">COPYRIGHT</a><br>
     <a href="#SEE ALSO">SEE ALSO</a><br>
     <hr>
     <!-- Creator     : groff version 1.17.2 -->
     <a name="NAME"></a>
     <h2>NAME</h2>
     <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%">
     envsubst - substitutes environment variables in shell format strings</td></table>
     <a name="SYNOPSIS"></a>
     <h2>SYNOPSIS</h2>
     <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>envsubst</b> [<i>OPTION</i>]
     [<i>SHELL-FORMAT</i>]</td></table>
     <a name="DESCRIPTION"></a>
     <h2>DESCRIPTION</h2>
     <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%">
     Substitutes the values of environment
     variables.</td></table>
     <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>Operation mode:</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="10%"></td><td width="90%">
     <b>-v</b>, <b>--variables</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 the variables occurring in SHELL-FORMAT</td></table>
     <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>Informative output:</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="10%"></td><td width="90%">
     <b>-h</b>, <b>--help</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%">
     display this help and exit</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>--version</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 version information and exit</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%">
     In normal operation mode, standard input is copied to
     standard output, with references to environment variables of
     the form $VARIABLE or ${VARIABLE} being replaced with the
     corresponding values. If a SHELL-FORMAT is given, only those
     environment variables that are referenced in SHELL-FORMAT
     are substituted; otherwise all environment variables
     references occurring in standard input are
     substituted.</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%">
     When <b>--variables</b> is used, standard input is ignored,
     and the output consists of the environment variables that
     are referenced in SHELL-FORMAT, one per line.</td></table>
     <a name="AUTHOR"></a>
     <h2>AUTHOR</h2>
     <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%">
     Written by Bruno Haible.</td></table>
     <a name="REPORTING BUGS"></a>
     <h2>REPORTING BUGS</h2>
     <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%">
     Report bugs to &lt;bug-gnu-gettext@gnu.org&gt;.</td></table>
     <a name="COPYRIGHT"></a>
     <h2>COPYRIGHT</h2>
     <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%">
     Copyright 2003 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></table>
     <a name="SEE ALSO"></a>
     <h2>SEE ALSO</h2>
     <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%">
     The full documentation for <b>envsubst</b> is maintained as
     a Texinfo manual. If the <b>info</b> and <b>envsubst</b>
     programs are properly installed at your site, the
     command</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%">
     <b>info envsubst</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="10%"></td><td width="90%">
     should give you access to the complete manual.</td></table>
     <hr>
     </body>
     </html>

     <HTML>
     <HEAD>
     <!-- This HTML file has been created by texi2html 1.52a
          from gettext.texi on 9 December 2003 -->
     <TITLE>GNU gettext utilities - 6  Updating Existing PO Files</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_22.html">last</A> section, <A HREF="gettext_toc.html">table of contents</A>.
     <P><HR><P>
     <H1><A NAME="SEC39" HREF="gettext_toc.html#TOC39">6  Updating Existing PO Files</A></H1>
     <H2><A NAME="SEC40" HREF="gettext_toc.html#TOC40">6.1  Invoking the <CODE>msgmerge</CODE> Program</A></H2>
     <P>
     <A NAME="IDX290"></A>
     <A NAME="IDX291"></A>
     <PRE>
     msgmerge [<VAR>option</VAR>] <VAR>def</VAR>.po <VAR>ref</VAR>.pot
     </PRE>
     <P>
     The <CODE>msgmerge</CODE> program merges two Uniforum style .po files together.
     The <VAR>def</VAR>.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 <VAR>ref</VAR>.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 <CODE>xgettext</CODE>); 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.
     </P>
     <H3><A NAME="SEC41" HREF="gettext_toc.html#TOC41">6.1.1  Input file location</A></H3>
     <DL COMPACT>
     <DT><SAMP>`<VAR>def</VAR>.po&acute;</SAMP>
     <DD>
     Translations referring to old sources.
     <DT><SAMP>`<VAR>ref</VAR>.pot&acute;</SAMP>
     <DD>
     References to the new sources.
     <DT><SAMP>`-D <VAR>directory</VAR>&acute;</SAMP>
     <DD>
     <DT><SAMP>`--directory=<VAR>directory</VAR>&acute;</SAMP>
     <DD>
     <A NAME="IDX292"></A>
     <A NAME="IDX293"></A>
     Add <VAR>directory</VAR> to the list of directories.  Source files are
     searched relative to this list of directories.  The resulting <TT>`.po&acute;</TT>
     file will be written relative to the current directory, though.
     <DT><SAMP>`-C <VAR>file</VAR>&acute;</SAMP>
     <DD>
     <DT><SAMP>`--compendium=<VAR>file</VAR>&acute;</SAMP>
     <DD>
     <A NAME="IDX294"></A>
     <A NAME="IDX295"></A>
     Specify an additional library of message translations.  See section <A HREF="gettext_6.html#SEC58">6.11  Using Translation Compendia</A>.
     This option may be specified more than once.
     </DL>
     <H3><A NAME="SEC42" HREF="gettext_toc.html#TOC42">6.1.2  Operation mode</A></H3>
     <DL COMPACT>
     <DT><SAMP>`-U&acute;</SAMP>
     <DD>
     <DT><SAMP>`--update&acute;</SAMP>
     <DD>
     <A NAME="IDX296"></A>
     <A NAME="IDX297"></A>
     Update <VAR>def</VAR>.po.  Do nothing if <VAR>def</VAR>.po is already up to date.
     </DL>
     <H3><A NAME="SEC43" HREF="gettext_toc.html#TOC43">6.1.3  Output file location</A></H3>
     <DL COMPACT>
     <DT><SAMP>`-o <VAR>file</VAR>&acute;</SAMP>
     <DD>
     <DT><SAMP>`--output-file=<VAR>file</VAR>&acute;</SAMP>
     <DD>
     <A NAME="IDX298"></A>
     <A NAME="IDX299"></A>
     Write output to specified file.
     </DL>
     <P>
     <A NAME="IDX300"></A>
     The results are written to standard output if no output file is specified
     or if it is <SAMP>`-&acute;</SAMP>.
     </P>
     <H3><A NAME="SEC44" HREF="gettext_toc.html#TOC44">6.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>&acute;</SAMP>
     <DD>
     <A NAME="IDX301"></A>
     <A NAME="IDX302"></A>
     Make a backup of <VAR>def</VAR>.po
     <DT><SAMP>`--suffix=<VAR>suffix</VAR>&acute;</SAMP>
     <DD>
     <A NAME="IDX303"></A>
     Override the usual backup suffix.
     </DL>
     <P>
     <A NAME="IDX304"></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&acute;</SAMP>
     <DD>
     <DT><SAMP>`off&acute;</SAMP>
     <DD>
     Never make backups (even if <CODE>--backup</CODE> is given).
     <DT><SAMP>`numbered&acute;</SAMP>
     <DD>
     <DT><SAMP>`t&acute;</SAMP>
     <DD>
     Make numbered backups.
     <DT><SAMP>`existing&acute;</SAMP>
     <DD>
     <DT><SAMP>`nil&acute;</SAMP>
     <DD>
     Make numbered backups if numbered backups for this file already exist,
     otherwise make simple backups.
     <DT><SAMP>`simple&acute;</SAMP>
     <DD>
     <DT><SAMP>`never&acute;</SAMP>
     <DD>
     Always make simple backups.
     </DL>
     <P>
     The backup suffix is <SAMP>`~&acute;</SAMP>, unless set with <CODE>--suffix</CODE> or the
     <CODE>SIMPLE_BACKUP_SUFFIX</CODE> environment variable.
     </P>
     <H3><A NAME="SEC45" HREF="gettext_toc.html#TOC45">6.1.5  Operation modifiers</A></H3>
     <DL COMPACT>
     <DT><SAMP>`-m&acute;</SAMP>
     <DD>
     <DT><SAMP>`--multi-domain&acute;</SAMP>
     <DD>
     <A NAME="IDX305"></A>
     <A NAME="IDX306"></A>
     Apply <VAR>ref</VAR>.pot to each of the domains in <VAR>def</VAR>.po.
     <DT><SAMP>`-N&acute;</SAMP>
     <DD>
     <DT><SAMP>`--no-fuzzy-matching&acute;</SAMP>
     <DD>
     <A NAME="IDX307"></A>
     <A NAME="IDX308"></A>
     Do not use fuzzy matching when an exact match is not found.  This may speed
     up the operation considerably.
     </DL>
     <H3><A NAME="SEC46" HREF="gettext_toc.html#TOC46">6.1.6  Input file syntax</A></H3>
     <DL COMPACT>
     <DT><SAMP>`-P&acute;</SAMP>
     <DD>
     <DT><SAMP>`--properties-input&acute;</SAMP>
     <DD>
     <A NAME="IDX309"></A>
     <A NAME="IDX310"></A>
     Assume the input files are Java ResourceBundles in Java <CODE>.properties</CODE>
     syntax, not in PO file syntax.
     <DT><SAMP>`--stringtable-input&acute;</SAMP>
     <DD>
     <A NAME="IDX311"></A>
     Assume the input files are NeXTstep/GNUstep localized resource files in
     <CODE>.strings</CODE> syntax, not in PO file syntax.
     </DL>
     <H3><A NAME="SEC47" HREF="gettext_toc.html#TOC47">6.1.7  Output details</A></H3>
     <DL COMPACT>
     <DT><SAMP>`--force-po&acute;</SAMP>
     <DD>
     <A NAME="IDX312"></A>
     Always write an output file even if it contains no message.
     <DT><SAMP>`-i&acute;</SAMP>
     <DD>
     <DT><SAMP>`--indent&acute;</SAMP>
     <DD>
     <A NAME="IDX313"></A>
     <A NAME="IDX314"></A>
     Write the .po file using indented style.
     <DT><SAMP>`--no-location&acute;</SAMP>
     <DD>
     <A NAME="IDX315"></A>
     Do not write <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>&acute;</SAMP> lines.
     <DT><SAMP>`--add-location&acute;</SAMP>
     <DD>
     <A NAME="IDX316"></A>
     Generate <SAMP>`#: <VAR>filename</VAR>:<VAR>line</VAR>&acute;</SAMP> lines (default).
     <DT><SAMP>`--strict&acute;</SAMP>
     <DD>
     <A NAME="IDX317"></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&acute;</SAMP>
     <DD>
     <DT><SAMP>`--properties-output&acute;</SAMP>
     <DD>
     <A NAME="IDX318"></A>
     <A NAME="IDX319"></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&acute;</SAMP>
     <DD>
     <A NAME="IDX320"></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>&acute;</SAMP>
     <DD>
     <DT><SAMP>`--width=<VAR>number</VAR>&acute;</SAMP>
     <DD>
     <A NAME="IDX321"></A>
     <A NAME="IDX322"></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&acute;</SAMP>
     <DD>
     <A NAME="IDX323"></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&acute;</SAMP>
     <DD>
     <DT><SAMP>`--sort-output&acute;</SAMP>
     <DD>
     <A NAME="IDX324"></A>
     <A NAME="IDX325"></A>
     <A NAME="IDX326"></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&acute;</SAMP>
     <DD>
     <DT><SAMP>`--sort-by-file&acute;</SAMP>
     <DD>
     <A NAME="IDX327"></A>
     <A NAME="IDX328"></A>
     Sort output by file location.
     </DL>
     <H3><A NAME="SEC48" HREF="gettext_toc.html#TOC48">6.1.8  Informative output</A></H3>
     <DL COMPACT>
     <DT><SAMP>`-h&acute;</SAMP>
     <DD>
     <DT><SAMP>`--help&acute;</SAMP>
     <DD>
     <A NAME="IDX329"></A>
     <A NAME="IDX330"></A>
     Display this help and exit.
     <DT><SAMP>`-V&acute;</SAMP>
     <DD>
     <DT><SAMP>`--version&acute;</SAMP>
     <DD>
     <A NAME="IDX331"></A>
     <A NAME="IDX332"></A>
     Output version information and exit.
     <DT><SAMP>`-v&acute;</SAMP>
     <DD>
     <DT><SAMP>`--verbose&acute;</SAMP>
     <DD>
     <A NAME="IDX333"></A>
     <A NAME="IDX334"></A>
     Increase verbosity level.
     <DT><SAMP>`-q&acute;</SAMP>
     <DD>
     <DT><SAMP>`--quiet&acute;</SAMP>
     <DD>
     <DT><SAMP>`--silent&acute;</SAMP>
     <DD>
     <A NAME="IDX335"></A>
     <A NAME="IDX336"></A>
     <A NAME="IDX337"></A>
     Suppress progress indicators.
     </DL>
     <H2><A NAME="SEC49" HREF="gettext_toc.html#TOC49">6.2  Translated Entries</A></H2>
     <P>
     <A NAME="IDX338"></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_6.html#SEC50">6.3  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="IDX339"></A>
     Some commands are more specifically related to translated entry processing.
     </P>
     <DL COMPACT>
     <DT><KBD>t</KBD>
     <DD>
     <A NAME="IDX340"></A>
     Find the next translated entry (<CODE>po-next-translated-entry</CODE>).
     <DT><KBD>T</KBD>
     <DD>
     <A NAME="IDX341"></A>
     Find the previous translated entry (<CODE>po-previous-translated-entry</CODE>).
     </DL>
     <P>
     <A NAME="IDX342"></A>
     <A NAME="IDX343"></A>
     <A NAME="IDX344"></A>
     <A NAME="IDX345"></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
     wraps around in the PO file buffer.
     </P>
     <P>
     <A NAME="IDX346"></A>
     Translated entries usually result from the translator having edited in
     a translation for them, section <A HREF="gettext_6.html#SEC53">6.6  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_6.html#SEC50">6.3  Fuzzy Entries</A>.
     </P>
     <H2><A NAME="SEC50" HREF="gettext_toc.html#TOC50">6.3  Fuzzy Entries</A></H2>
     <P>
     <A NAME="IDX347"></A>
     </P>
     <P>
     <A NAME="IDX348"></A>
     <A NAME="IDX349"></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
     has the name <CODE>fuzzy</CODE>, and entries having this attribute are said
     to have a fuzzy translation.  They are called fuzzy entries, for short.
     </P>
     <P>
     Fuzzy entries, even if they account for translated entries for
     most other purposes, usually call for revision by the translator.
     Those may be produced by applying the program <CODE>msgmerge</CODE> to
     update an older translated PO files according to a new PO template
     file, when this tool hypothesises that some new <CODE>msgid</CODE> has
     been modified only slightly out of an older one, and chooses to pair
     what it thinks to be the old translation for the new modified entry.
     The slight alteration in the original string (the <CODE>msgid</CODE> string)
     should often be reflected in the translated string, and this requires
     the intervention of the translator.  For this reason, <CODE>msgmerge</CODE>
     might mark some entries as being fuzzy.
     </P>
     <P>
     <A NAME="IDX350"></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
     related to fuzzy entry processing.
     </P>
     <DL COMPACT>
     <DT><KBD>z</KBD>
     <DD>
     <A NAME="IDX351"></A>
     Find the next fuzzy entry (<CODE>po-next-fuzzy-entry</CODE>).
     <DT><KBD>Z</KBD>
     <DD>
     <A NAME="IDX352"></A>
     Find the previous fuzzy entry (<CODE>po-previous-fuzzy-entry</CODE>).
     <DT><KBD><KBD>TAB</KBD></KBD>
     <DD>
     <A NAME="IDX353"></A>
     Remove the fuzzy attribute of the current entry (<CODE>po-unfuzzy</CODE>).
     </DL>
     <P>
     <A NAME="IDX354"></A>
     <A NAME="IDX355"></A>
     <A NAME="IDX356"></A>
     <A NAME="IDX357"></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
     around in the PO file buffer.
     </P>
     <P>
     <A NAME="IDX358"></A>
     <A NAME="IDX359"></A>
     <A NAME="IDX360"></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
     the <CODE>nil</CODE> value, the <KBD><KBD>TAB</KBD></KBD> command will automatically chase
     for another interesting entry to work on.  The initial value of
     <CODE>po-auto-select-on-unfuzzy</CODE> is <CODE>nil</CODE>.
     </P>
     <P>
     The initial value of <CODE>po-auto-fuzzy-on-edit</CODE> is <CODE>nil</CODE>.  However,
     if the variable <CODE>po-auto-fuzzy-on-edit</CODE> is set to <CODE>t</CODE>, any entry
     edited through the <KBD><KBD>RET</KBD></KBD> command is marked fuzzy, as a way to
     ensure some kind of double check, later.  In this case, the usual paradigm
     is that an entry becomes fuzzy (if not already) whenever the translator
     modifies it.  If she is satisfied with the translation, she then uses
     <KBD><KBD>TAB</KBD></KBD> to pick another entry to work on, clearing the fuzzy attribute
     on the same blow.  If she is not satisfied yet, she merely uses <KBD><KBD>SPC</KBD></KBD>
     to chase another entry, leaving the entry fuzzy.
     </P>
     <P>
     <A NAME="IDX361"></A>
     <A NAME="IDX362"></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
     working at this entry.
     </P>
     <P>
     Also, when time comes to quit working on a PO file buffer with the <KBD>q</KBD>
     command, the translator is asked for confirmation, if fuzzy string
     still exists.
     </P>
     <H2><A NAME="SEC51" HREF="gettext_toc.html#TOC51">6.4  Untranslated Entries</A></H2>
     <P>
     <A NAME="IDX363"></A>
     </P>
     <P>
     When <CODE>xgettext</CODE> originally creates a PO file, unless told
     otherwise, it initializes the <CODE>msgid</CODE> field with the untranslated
     string, and leaves the <CODE>msgstr</CODE> string to be empty.  Such entries,
     having an empty translation, are said to be <EM>untranslated</EM> entries.
     Later, when the programmer slightly modifies some string right in
     the program, this change is later reflected in the PO file
     by the appearance of a new untranslated entry for the modified string.
     </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 ""&acute;</SAMP>.
     </P>
     <P>
     <A NAME="IDX364"></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.
     Some commands are more specifically related to untranslated entry
     processing.
     </P>
     <DL COMPACT>
     <DT><KBD>u</KBD>
     <DD>
     <A NAME="IDX365"></A>
     Find the next untranslated entry (<CODE>po-next-untranslated-entry</CODE>).
     <DT><KBD>U</KBD>
     <DD>
     <A NAME="IDX366"></A>
     Find the previous untranslated entry (<CODE>po-previous-untransted-entry</CODE>).
     <DT><KBD>k</KBD>
     <DD>
     <A NAME="IDX367"></A>
     Turn the current entry into an untranslated one (<CODE>po-kill-msgstr</CODE>).
     </DL>
     <P>
     <A NAME="IDX368"></A>
     <A NAME="IDX369"></A>
     <A NAME="IDX370"></A>
     <A NAME="IDX371"></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
     extended and wraps around in the PO file buffer.
     </P>
     <P>
     <A NAME="IDX372"></A>
     <A NAME="IDX373"></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_6.html#SEC53">6.6  Modifying Translations</A>.
     </P>
     <P>
     Also, when time comes to quit working on a PO file buffer
     with the <KBD>q</KBD> command, the translator is asked for confirmation,
     if some untranslated string still exists.
     </P>
     <H2><A NAME="SEC52" HREF="gettext_toc.html#TOC52">6.5  Obsolete Entries</A></H2>
     <P>
     <A NAME="IDX374"></A>
     </P>
     <P>
     By <EM>obsolete</EM> PO file entries, we mean those entries which are
     commented out, usually by <CODE>msgmerge</CODE> when it found that the
     translation is not needed anymore by the package being localized.
     </P>
     <P>
     The usual commands moving from entry to entry consider obsolete
     entries on the same level as active entries.  Obsolete entries are
     easily recognizable by the fact that all their lines start with
     <CODE>#</CODE>, even those lines containing <CODE>msgid</CODE> or <CODE>msgstr</CODE>.
     </P>
     <P>
     Commands exist for emptying the translation or reinitializing it
     to the original untranslated string.  Commands interfacing with the
     kill ring may force some previously saved text into the translation.
     The user may interactively edit the translation.  All these commands
     may apply to obsolete entries, carefully leaving the entry obsolete
     after the fact.
     </P>
     <P>
     <A NAME="IDX375"></A>
     Moreover, some commands are more specifically related to obsolete
     entry processing.
     </P>
     <DL COMPACT>
     <DT><KBD>o</KBD>
     <DD>
     <A NAME="IDX376"></A>
     Find the next obsolete entry (<CODE>po-next-obsolete-entry</CODE>).
     <DT><KBD>O</KBD>
     <DD>
     <A NAME="IDX377"></A>
     Find the previous obsolete entry (<CODE>po-previous-obsolete-entry</CODE>).
     <DT><KBD><KBD>DEL</KBD></KBD>
     <DD>
     <A NAME="IDX378"></A>
     Make an active entry obsolete, or zap out an obsolete entry
     (<CODE>po-fade-out-entry</CODE>).
     </DL>
     <P>
     <A NAME="IDX379"></A>
     <A NAME="IDX380"></A>
     <A NAME="IDX381"></A>
     <A NAME="IDX382"></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
     extended and wraps around in the PO file buffer.
     </P>
     <P>
     PO mode does not provide ways for un-commenting an obsolete entry
     and making it active, because this would reintroduce an original
     untranslated string which does not correspond to any marked string
     in the program sources.  This goes with the philosophy of never
     introducing useless <CODE>msgid</CODE> values.
     </P>
     <P>
     <A NAME="IDX383"></A>
     <A NAME="IDX384"></A>
     <A NAME="IDX385"></A>
     <A NAME="IDX386"></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.
     The command <KBD><KBD>DEL</KBD></KBD> (<CODE>po-fade-out-entry</CODE>) pushes the current entry
     a little further towards annihilation.  If the entry is active (it is a
     translated entry), then it is first made fuzzy.  If it is already fuzzy,
     then the entry is merely commented out, with confirmation.  If the entry
     is already obsolete, then it is completely deleted from the PO file.
     It is easy to recycle the translation so deleted into some other PO file
     entry, usually one which is untranslated.  See section <A HREF="gettext_6.html#SEC53">6.6  Modifying Translations</A>.
     </P>
     <P>
     Here is a quite interesting problem to solve for later development of
     PO mode, for those nights you are not sleepy.  The idea would be that
     PO mode might become bright enough, one of these days, to make good
     guesses at retrieving the most probable candidate, among all obsolete
     entries, for initializing the translation of a newly appeared string.
     I think it might be a quite hard problem to do this algorithmically, as
     we have to develop good and efficient measures of string similarity.
     Right now, PO mode completely lets the decision to the translator,
     when the time comes to find the adequate obsolete translation, it
     merely tries to provide handy tools for helping her to do so.
     </P>
     <H2><A NAME="SEC53" HREF="gettext_toc.html#TOC53">6.6  Modifying Translations</A></H2>
     <P>
     <A NAME="IDX387"></A>
     <A NAME="IDX388"></A>
     </P>
     <P>
     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 helping the translator to avoid little clerical errors
     about the overall file format, or the proper quoting of strings,
     as those errors would be easily made.  Other kinds of errors are
     still possible, but some may be caught and diagnosed by the batch
     validation process, which the translator may always trigger by the
     <KBD>V</KBD> command.  For all other errors, the translator has to rely on
     her own judgment, and also on the linguistic reports submitted to her
     by the users of the translated package, having the same mother tongue.
     </P>
     <P>
     When the time comes to create a translation, correct an error diagnosed
     mechanically or reported by a user, the translators have to resort to
     using the following commands for modifying the translations.
     </P>
     <DL COMPACT>
     <DT><KBD><KBD>RET</KBD></KBD>
     <DD>
     <A NAME="IDX389"></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="IDX390"></A>
     <A NAME="IDX391"></A>
     Reinitialize the translation with the original, untranslated string
     (<CODE>po-msgid-to-msgstr</CODE>).
     <DT><KBD>k</KBD>
     <DD>
     <A NAME="IDX392"></A>
     Save the translation on the kill ring, and delete it (<CODE>po-kill-msgstr</CODE>).
     <DT><KBD>w</KBD>
     <DD>
     <A NAME="IDX393"></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="IDX394"></A>
     Replace the translation, taking the new from the kill ring
     (<CODE>po-yank-msgstr</CODE>).
     </DL>
     <P>
     <A NAME="IDX395"></A>
     <A NAME="IDX396"></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
     the current PO file entry, all ready for edition, expunged of all quoting
     marks, fully modifiable and with the complete extent of Emacs modifying
     commands.  When the translator is done with her modifications, she may use
     <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_6.html#SEC55">6.8  Details of Sub Edition</A>,
     for more information.
     </P>
     <P>
     <A NAME="IDX397"></A>
     <A NAME="IDX398"></A>
     <A NAME="IDX399"></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
     the original string, disregarding any previous work.
     </P>
     <P>
     <A NAME="IDX400"></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
     initialised with the original string, in case none exists already.
     The default value for <CODE>po-auto-edit-with-msgid</CODE> is <CODE>nil</CODE>.
     </P>
     <P>
     <A NAME="IDX401"></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
     target language are so different that is simply best to start writing
     on an empty page.  At other times, the source and target languages
     are so close that it would be a waste to retype a number of words
     already being written in the original string.  A translator may also
     like having the original string right under her eyes, as she will
     progressively overwrite the original text with the translation, even
     if this requires some extra editing work to get rid of the original.
     </P>
     <P>
     <A NAME="IDX402"></A>
     <A NAME="IDX403"></A>
     <A NAME="IDX404"></A>
     <A NAME="IDX405"></A>
     <A NAME="IDX406"></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
     a special place, known as the kill ring.  The command <KBD>w</KBD>
     (<CODE>po-kill-ring-save-msgstr</CODE>) has also the effect of taking a
     copy of the translation onto the kill ring, but it otherwise leaves
     the entry alone, and does <EM>not</EM> remove the translation from the
     entry.  Both commands use exactly the Emacs kill ring, which is shared
     between buffers, and which is well known already to Emacs lovers.
     </P>
     <P>
     The translator may use <KBD>k</KBD> or <KBD>w</KBD> many times in the course
     of her work, as the kill ring may hold several saved translations.
     From the kill ring, strings may later be reinserted in various
     Emacs buffers.  In particular, the kill ring may be used for moving
     translation strings between different entries of a single PO file
     buffer, or if the translator is handling many such buffers at once,
     even between PO files.

... This diff was truncated because it exceeds the maximum size that can be displayed.

Also available in: Unified diff