<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>pomerge — Translate Toolkit 1.9.0 documentation</title>
<link rel="stylesheet" href="../_static/basic.css" type="text/css" />
<link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
<link rel="stylesheet" href="../_static/bootstrap.css" type="text/css" />
<link rel="stylesheet" href="../_static/bootstrap-sphinx.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: '../',
VERSION: '1.9.0',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true
};
</script>
<script type="text/javascript" src="../_static/jquery.js"></script>
<script type="text/javascript" src="../_static/underscore.js"></script>
<script type="text/javascript" src="../_static/doctools.js"></script>
<script type="text/javascript" src="../_static/bootstrap.js"></script>
<script type="text/javascript" src="../_static/bootstrap-sphinx.js"></script>
<link rel="top" title="Translate Toolkit 1.9.0 documentation" href="../index.html" />
<link rel="up" title="Converters" href="index.html" />
<link rel="next" title="porestructure" href="porestructure.html" />
<link rel="prev" title="pogrep" href="pogrep.html" />
</head>
<body>
<div id="navbar" class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container-fluid">
<a class="brand" href="../index.html">Translate Toolkit</a>
<span class="navbar-text pull-left"><b>1.9.0</b></span>
<ul class="nav">
<li class="divider-vertical"></li>
<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown">Site <b class="caret"></b></a>
<ul class="dropdown-menu globaltoc"><ul class="simple">
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../features.html">Features</a></li>
<li class="toctree-l1"><a class="reference internal" href="../installation.html">Installation</a></li>
<li class="toctree-l1"><a class="reference internal" href="index.html">Converters</a></li>
<li class="toctree-l1"><a class="reference internal" href="index.html#tools">Tools</a></li>
<li class="toctree-l1"><a class="reference internal" href="index.html#scripts">Scripts</a></li>
<li class="toctree-l1"><a class="reference internal" href="../guides/index.html">Use Cases</a></li>
<li class="toctree-l1"><a class="reference internal" href="../formats/index.html">Supported formats</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../styleguide.html">Translate Styleguide</a></li>
<li class="toctree-l1"><a class="reference internal" href="../styleguide.html#documentation">Documentation</a></li>
<li class="toctree-l1"><a class="reference internal" href="../development/building.html">Building</a></li>
<li class="toctree-l1"><a class="reference internal" href="../development/contributing.html">Contributing</a></li>
<li class="toctree-l1"><a class="reference internal" href="../development/developers.html">Translate Toolkit Developers Guide</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../api/index.html">API</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../changelog.html">Important Changes</a></li>
<li class="toctree-l1"><a class="reference internal" href="../history.html">History of the Translate Toolkit</a></li>
<li class="toctree-l1"><a class="reference internal" href="../license.html">License</a></li>
</ul>
</ul>
</li>
<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown">Page <b class="caret"></b></a>
<ul class="dropdown-menu localtoc"><ul>
<li><a class="reference internal" href="#">pomerge</a><ul>
<li><a class="reference internal" href="#usage">Usage</a></li>
<li><a class="reference internal" href="#examples">Examples</a></li>
<li><a class="reference internal" href="#issues">Issues</a></li>
</ul>
</li>
</ul>
</ul>
</li>
<li><a href="pogrep.html"
title="previous chapter">« pogrep</a></li>
<li><a href="porestructure.html"
title="next chapter">porestructure »</a></li>
</ul>
<form class="navbar-search pull-right" action="../search.html" method="get">
<input type="text" name="q" placeholder="Search" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
</ul>
</div>
</div>
</div>
</div>
<div class="container content">
<div class="section" id="pomerge">
<span id="id1"></span><h1>pomerge<a class="headerlink" href="#pomerge" title="Permalink to this headline">¶</a></h1>
<p>Pomerge will merge corrected PO, XLIFF, or TMX files (or snippets) into your
existing PO, XLIFF, TMX files. Usually you would extract errors using
<a class="reference internal" href="pofilter.html"><em>pofilter</em></a>, make corrections to these PO (or XLIFF, TMX) snippets then
merge them back using pomerge. You could also use <a class="reference internal" href="pogrep.html"><em>pogrep</em></a> to extract a
number of messages matching a certain string, make corrections then merge the
correction back using pomerge.</p>
<p>It is probably best to run pomerge against files stored in some kind of version
control system so that you can monitor what changes were made.</p>
<p>Pomerge will also attempt to make as small a change as possible to the text,
making it easier to see the changes using your version control system.</p>
<div class="section" id="usage">
<span id="pomerge-usage"></span><h2>Usage<a class="headerlink" href="#usage" title="Permalink to this headline">¶</a></h2>
<div class="highlight-python"><pre>pomerge [options] [-t <template>] -i <input> -o <output></pre>
</div>
<p>Where:</p>
<table border="1" class="docutils">
<colgroup>
<col width="16%" />
<col width="84%" />
</colgroup>
<tbody valign="top">
<tr class="row-odd"><td><template></td>
<td>is a set of reference PO, XLIFF, TMX files, either the
originals or a set of POT files</td>
</tr>
<tr class="row-even"><td><input></td>
<td>contains the corrected files that are to override content in
<output></td>
</tr>
<tr class="row-odd"><td><output></td>
<td>contains the files whose content will be overridden by
<input>. This can be the same directory as <template></td>
</tr>
</tbody>
</table>
<p>Options:</p>
<table class="docutils option-list" frame="void" rules="none">
<col class="option" />
<col class="description" />
<tbody valign="top">
<tr><td class="option-group">
<kbd><span class="option">--version</span></kbd></td>
<td>show program’s version number and exit</td></tr>
<tr><td class="option-group">
<kbd><span class="option">-h</span>, <span class="option">--help</span></kbd></td>
<td>show this help message and exit</td></tr>
<tr><td class="option-group">
<kbd><span class="option">--manpage</span></kbd></td>
<td>output a manpage based on the help</td></tr>
<tr><td class="option-group" colspan="2">
<kbd><span class="option">--progress=<var>PROGRESS</var></span></kbd></td>
</tr>
<tr><td> </td><td>show progress as: <a class="reference internal" href="option_progress.html"><em>dots, none, bar, names, verbose</em></a></td></tr>
<tr><td class="option-group" colspan="2">
<kbd><span class="option">--errorlevel=<var>ERRORLEVEL</var></span></kbd></td>
</tr>
<tr><td> </td><td>show errorlevel as: <a class="reference internal" href="option_errorlevel.html"><em>none, message, exception,
traceback</em></a></td></tr>
<tr><td class="option-group" colspan="2">
<kbd><span class="option">-i<var>INPUT</var></span>, <span class="option">--input=<var>INPUT</var></span></kbd></td>
</tr>
<tr><td> </td><td>read from INPUT in po, pot, xlf, tmx formats</td></tr>
<tr><td class="option-group" colspan="2">
<kbd><span class="option">-x<var>EXCLUDE</var></span>, <span class="option">--exclude=<var>EXCLUDE</var></span></kbd></td>
</tr>
<tr><td> </td><td>exclude names matching EXCLUDE from input paths</td></tr>
<tr><td class="option-group" colspan="2">
<kbd><span class="option">-o<var>OUTPUT</var></span>, <span class="option">--output=<var>OUTPUT</var></span></kbd></td>
</tr>
<tr><td> </td><td>write to OUTPUT in po, pot, xlf, tmx formats</td></tr>
<tr><td class="option-group" colspan="2">
<kbd><span class="option">-t<var>TEMPLATE</var></span>, <span class="option">--template=<var>TEMPLATE</var></span></kbd></td>
</tr>
<tr><td> </td><td>read from TEMPLATE in po, pot, xlf, tmx formats</td></tr>
<tr><td class="option-group">
<kbd><span class="option">--psyco=<var>MODE</var></span></kbd></td>
<td>use psyco to speed up the operation, modes: <a class="reference internal" href="option_psyco.html"><em>none,
full, profile</em></a></td></tr>
<tr><td class="option-group" colspan="2">
<kbd><span class="option">--mergeblanks=<var>MERGEBLANKS</var></span></kbd></td>
</tr>
<tr><td> </td><td>whether to overwrite existing translations with blank translations (yes/no). Default is yes.</td></tr>
<tr><td class="option-group" colspan="2">
<kbd><span class="option">--mergefuzzy=<var>MERGEFUZZY</var></span></kbd></td>
</tr>
<tr><td> </td><td>whether to overwrite existing translations with fuzzy translations (yes/no). Default is yes. (new in version 1.9)</td></tr>
<tr><td class="option-group" colspan="2">
<kbd><span class="option">--mergecomments=<var>MERGECOMMENTS</var></span></kbd></td>
</tr>
<tr><td> </td><td>whether to merge comments as well as translations (yes/no). Default is yes.</td></tr>
</tbody>
</table>
</div>
<div class="section" id="examples">
<span id="pomerge-examples"></span><h2>Examples<a class="headerlink" href="#examples" title="Permalink to this headline">¶</a></h2>
<p>These examples show pomerge in action.</p>
<div class="highlight-python"><pre>pomerge -t af -i af-check -o af</pre>
</div>
<p>Take corrections from <em>af-check</em> merge them with the templates in <em>af</em> and
output into <em>af</em>. Thus merge af-check and override entries found in <em>af</em>. Do
this only if you are using a version control system so that you can check
what changes pomerge made or if you have complete and utter confidence in this
tool.</p>
<div class="highlight-python"><pre>pomerge --mergeblanks=yes -t af -i af-check -o af-new</pre>
</div>
<p>Merge the corrections from <em>af-check</em> with templates in <em>af</em> and output to
<em>af-new</em>. If an entry is blank in <em>af-check</em> then make it blank in the output
in <em>af-new</em>.</p>
</div>
<div class="section" id="issues">
<span id="pomerge-issues"></span><h2>Issues<a class="headerlink" href="#issues" title="Permalink to this headline">¶</a></h2>
<ul class="simple">
<li>Seems to have trouble merging KDE style comments back. (Probably not relevant
with newest versions any more.)</li>
<li>Only files found in the input directory will be copied to the output. The
template directory is not searched for extra files to copy to the output.
Therefore it is always best to have your input directory in version control,
and use the same directory as output. This will allow you to use the diff
function of the version control system to double check changes made, with all
the files of the input still present.</li>
</ul>
</div>
</div>
</div>
<hr>
<footer class="footer">
<div class="container">
<p class="pull-right"><a href="#">Back to top ↑</a></p>
<ul class="unstyled muted">
<li><small>
© 2012, Translate.org.za.<br/>
</small></li>
<li><small>
Created using <a href="http://sphinx.pocoo.org/">Sphinx</a> 1.1.3.
</small></li>
</ul>
</div>
</footer>
</body>
</html>
