This file is indexed.

/usr/share/doc/translate-toolkit/html/features.html is in translate-toolkit 1.10.0-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
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
<!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 &mdash; Translate Toolkit 1.10.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.10.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.10.0 documentation" href="index.html" />
    <link rel="next" title="Installation" href="installation.html" />
    <link rel="prev" title="Translate Toolkit" href="index.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.10</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 class="current">
<li class="toctree-l1 current"><a class="current reference internal" href="">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="commands/index.html">Converters</a></li>
<li class="toctree-l1"><a class="reference internal" href="commands/index.html#tools">Tools</a></li>
<li class="toctree-l1"><a class="reference internal" href="commands/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="#">Features</a></li>
</ul>
</ul>
</li>
            
            
              
  <li><a href="index.html"
         title="previous chapter">&laquo; Translate Toolkit</a></li>
  <li><a href="installation.html"
         title="next chapter">Installation &raquo;</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="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&#8217;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"><em>formats</em></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"><em>42 checks</em></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"><em>base class</em></a> section for more information.</p>
</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>
        &copy; 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>