/usr/share/doc/translate-toolkit/html/features.html is in translate-toolkit-doc 2.2.5-2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 | <!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>Features — Translate Toolkit 2.2.5 documentation</title>
<link rel="stylesheet" href="_static/alabaster.css" type="text/css" />
<link rel="stylesheet" href="_static/pygments.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: './',
VERSION: '2.2.5',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true,
SOURCELINK_SUFFIX: '.txt'
};
</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>
<link rel="index" title="Index" href="genindex.html" />
<link rel="search" title="Search" href="search.html" />
<link rel="next" title="Installation" href="installation.html" />
<link rel="prev" title="Translate Toolkit" href="index.html" />
<link rel="stylesheet" href="_static/custom.css" type="text/css" />
<meta name="viewport" content="width=device-width, initial-scale=0.9, maximum-scale=0.9" />
</head>
<body>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body" role="main">
<div class="section" id="features">
<span id="id1"></span><h1>Features<a class="headerlink" href="#features" title="Permalink to this headline">¶</a></h1>
<ul class="simple">
<li>Work with <strong>ONE localisation format</strong>. You’ll no longer be editing DTD files
in one tool, .properties in another, OpenOffice GSI in a third. Simply do
all your localisation in a PO or XLIFF editor</li>
<li><strong>Converters</strong> for a number of <a class="reference internal" href="formats/index.html"><span class="doc">formats</span></a><ul>
<li>OpenOffice.org SDF/GSI</li>
<li>Mozilla: .properties, DTD, XHTML, .inc, .ini, etc</li>
<li>Others: Comma Separated Value, TMX, XLIFF, TBX, PHP, WordFast TXT, Qt .ts,
txt, .ini, Windows .rc, ical, subtitles, Mac OS X strings</li>
</ul>
</li>
<li><strong>File access to localization files</strong> through the format API in all the above
formats, as well as .qph, .qm, .mo</li>
<li>Output <strong>valid target file</strong> types. We make sure that your output files
(e.g. .properties) contain all comments from the original file and preserves
the layout of the original as far as possible. If your PO entry is marked as
fuzzy we use the English text, not your half complete translation. The
converters for OpenOffice.org and Mozilla formats will also perform simple
checks and corrections to make sure you have none of those hard to find
localisation bugs.</li>
<li>Our checker has over <a class="reference internal" href="commands/pofilter_tests.html"><span class="doc">42 checks</span></a> to find
errors such as: missing or translated variables, missing accelerator keys,
bad escaping, start capitalisation, missing sentences, bad XML and much more.</li>
<li>Language awareness, taking language conventions for capitalisation, quotes
and other punctuation into account</li>
<li><strong>Find conflicting translations</strong> easily, cases where you have translated a
source word differently or used a target word for 2 very different English
concepts</li>
<li><strong>Extract messages</strong> using simple text or a regular expression allowing you
to quickly find and extract words that you need to fix due to glossary
changes.</li>
<li><strong>Merge snippets</strong> of PO files into your existing translations.</li>
<li>Create word, string and file <strong>counts</strong> of your files. Making it much easier
to budget time as string counts do not give you a good indication of expected
work.</li>
<li>Create a set of PO files with <strong>debugging</strong> entries to allow you to easily
locate the source of translations. Very useful in OpenOffice.org which
provides scant clues as to where the running application has sourced the
message.</li>
</ul>
<p>The Translate Toolkit is also a <strong>powerful API</strong> for writing translation and
localisation tools, already used by our own and several other projects. See the
<a class="reference internal" href="formats/base_classes.html"><span class="doc">base class</span></a> section for more information.</p>
</div>
</div>
</div>
</div>
<div class="sphinxsidebar" role="navigation" aria-label="main navigation">
<div class="sphinxsidebarwrapper"><div class="relations">
<h3>Related Topics</h3>
<ul>
<li><a href="index.html">Documentation overview</a><ul>
<li>Previous: <a href="index.html" title="previous chapter">Translate Toolkit</a></li>
<li>Next: <a href="installation.html" title="next chapter">Installation</a></li>
</ul></li>
</ul>
</div>
<div id="searchbox" style="display: none" role="search">
<h3>Quick search</h3>
<form class="search" action="search.html" method="get">
<div><input type="text" name="q" /></div>
<div><input type="submit" value="Go" /></div>
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="footer">
©2002-2018, Translate.
|
Powered by <a href="http://sphinx-doc.org/">Sphinx 1.6.5</a>
& <a href="https://github.com/bitprophet/alabaster">Alabaster 0.7.8</a>
</div>
</body>
</html>
|