Navigation Menu

Skip to content

Commit

Permalink
Translate
Browse files Browse the repository at this point in the history
  • Loading branch information
kou committed Jan 20, 2015
1 parent d6bf0e7 commit 2361730
Show file tree
Hide file tree
Showing 21 changed files with 149 additions and 154 deletions.
2 changes: 1 addition & 1 deletion docs/reference/suggest.html
Expand Up @@ -101,7 +101,7 @@ <h1>7.14. Suggest<a class="headerlink" href="#suggest" title="Permalink to this
<li class="toctree-l2"><a class="reference internal" href="suggest/completion.html#how-it-works">7.14.2.1. How it works</a></li>
<li class="toctree-l2"><a class="reference internal" href="suggest/completion.html#how-to-use">7.14.2.2. How to use</a></li>
<li class="toctree-l2"><a class="reference internal" href="suggest/completion.html#how-it-learns">7.14.2.3. How it learns</a></li>
<li class="toctree-l2"><a class="reference internal" href="suggest/completion.html#how-to-update-rk-reading-data">7.14.2.4. How to update RK reading data</a></li>
<li class="toctree-l2"><a class="reference internal" href="suggest/completion.html#how-to-update-reading-data">7.14.2.4. How to update reading data</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="suggest/correction.html">7.14.3. Correction</a><ul>
Expand Down
49 changes: 26 additions & 23 deletions docs/reference/suggest/completion.html
Expand Up @@ -114,11 +114,11 @@ <h3>7.14.2.1.1. Prefix RK search<a class="headerlink" href="#prefix-rk-search" t
<p>For example, there is a registered word &quot;日本&quot;. And &quot;ニホン&quot;
(it must be katakana) is registered as its reading. An user
can find &quot;日本&quot; by &quot;ni&quot;, &quot;二&quot; or &quot;に&quot;.</p>
<p>If you create dataset which is named as example by
<a class="reference internal" href="../executables/groonga-suggest-create-dataset.html"><em>groonga-suggest-create-dataset</em></a> command,
you can update pairs of registered word and its reading by loading
data to '_key' and 'kana' column of item_example table explicitly for
prefix RK search.</p>
<p>If you create dataset which is named as <tt class="docutils literal"><span class="pre">example</span></tt> by
<a class="reference internal" href="../executables/groonga-suggest-create-dataset.html"><em>groonga-suggest-create-dataset</em></a>
executable file, you can update pairs of registered word and its
reading by loading data to <tt class="docutils literal"><span class="pre">_key</span></tt> and <tt class="docutils literal"><span class="pre">kana</span></tt> column of
<tt class="docutils literal"><span class="pre">item_example</span></tt> table explicitly for prefix RK search.</p>
</div>
<div class="section" id="cooccurrence-search">
<h3>7.14.2.1.2. Cooccurrence search<a class="headerlink" href="#cooccurrence-search" title="Permalink to this headline"></a></h3>
Expand Down Expand Up @@ -249,7 +249,7 @@ <h3>7.14.2.1.2. Cooccurrence search<a class="headerlink" href="#cooccurrence-sea
<h3>7.14.2.1.3. Prefix search<a class="headerlink" href="#prefix-search" title="Permalink to this headline"></a></h3>
<p>Prefix search can find registered word that start with
user's input. This search doesn't care about romaji,
katakana and hiragana not like Prefix RK search.</p>
katakana and hiragana not like prefix RK search.</p>
<p>This search isn't always ran. It's just ran when it's
requested explicitly or both prefix RK search and
cooccurrence search return nothing.</p>
Expand All @@ -261,7 +261,7 @@ <h3>7.14.2.1.3. Prefix search<a class="headerlink" href="#prefix-search" title="
<div class="section" id="how-to-use">
<h2>7.14.2.2. How to use<a class="headerlink" href="#how-to-use" title="Permalink to this headline"></a></h2>
<p>Groonga provides <a class="reference internal" href="../commands/suggest.html"><em>suggest</em></a> command to use
completion. <cite>--type complete</cite> option requests completion.</p>
completion. <tt class="docutils literal"><span class="pre">--type</span> <span class="pre">complete</span></tt> option requests completion.</p>
<p>For example, here is an command to get completion results by
&quot;en&quot;:</p>
<p>Execution example:</p>
Expand Down Expand Up @@ -301,7 +301,7 @@ <h2>7.14.2.2. How to use<a class="headerlink" href="#how-to-use" title="Permalin
<h2>7.14.2.3. How it learns<a class="headerlink" href="#how-it-learns" title="Permalink to this headline"></a></h2>
<p>Cooccurrence search uses learned data. They are based on
query logs, access logs and so on. To create learned data,
groonga needs user input sequence with time stamp and user
Groonga needs user input sequence with time stamp and user
submit input with time stamp.</p>
<p>For example, an user wants to search by &quot;engine&quot;. The user
inputs the query with the following sequence:</p>
Expand Down Expand Up @@ -329,10 +329,11 @@ <h2>7.14.2.3. How it learns<a class="headerlink" href="#how-it-learns" title="Pe
</pre></div>
</div>
</div>
<div class="section" id="how-to-update-rk-reading-data">
<h2>7.14.2.4. How to update RK reading data<a class="headerlink" href="#how-to-update-rk-reading-data" title="Permalink to this headline"></a></h2>
<p>Groonga requires registered word and its reading for RK search, so load such data in the advance.</p>
<p>Here is the example to register &quot;日本&quot; which means Japanese in english.</p>
<div class="section" id="how-to-update-reading-data">
<h2>7.14.2.4. How to update reading data<a class="headerlink" href="#how-to-update-reading-data" title="Permalink to this headline"></a></h2>
<p>Groonga requires registered word and its reading for prefix RK
search. This section describes how to register a word and its reading.</p>
<p>Here is an example to register &quot;日本&quot; which means Japan in English:</p>
<p>Execution example:</p>
<div class="highlight-none"><div class="highlight"><pre>load --table event_query --each &#39;suggest_preparer(_id, type, item, sequence, time, pair_query)&#39;
[
Expand All @@ -341,7 +342,7 @@ <h2>7.14.2.4. How to update RK reading data<a class="headerlink" href="#how-to-u
# [[0, 1337566253.89858, 0.000355720520019531], 1]
</pre></div>
</div>
<p>Here is the example to update RK data to complete &quot;日本&quot;.</p>
<p>Here is an example to update reading data to complete &quot;日本&quot;:</p>
<p>Execution example:</p>
<div class="highlight-none"><div class="highlight"><pre>load --table item_query
[
Expand All @@ -350,7 +351,8 @@ <h2>7.14.2.4. How to update RK reading data<a class="headerlink" href="#how-to-u
# [[0, 1337566253.89858, 0.000355720520019531], 1]
</pre></div>
</div>
<p>Then you can complete registered word &quot;日本&quot; by RK input - &quot;nihon&quot;.</p>
<p>Then you can complete registered word &quot;日本&quot; by Romaji input -
&quot;nihon&quot;.</p>
<p>Execution example:</p>
<div class="highlight-none"><div class="highlight"><pre>suggest --table item_query --column kana --types complete --frequency_threshold 1 --query nihon
# [
Expand Down Expand Up @@ -383,10 +385,11 @@ <h2>7.14.2.4. How to update RK reading data<a class="headerlink" href="#how-to-u
# ]
</pre></div>
</div>
<p>Without loading above RK data, you can't complete registered word &quot;日本&quot;
by query - &quot;nihon&quot;.</p>
<p>As the column type of item_query table is VECTOR_COLUMN, you can
register multiple readings for registered word.</p>
<p>Without loading above reading data, you can't complete registered word
&quot;日本&quot; by query - &quot;nihon&quot;.</p>
<p>You can register multiple readings for a registered word because
<tt class="docutils literal"><span class="pre">kana</span></tt> column in <tt class="docutils literal"><span class="pre">item_query</span></tt> table is defined as a
<a class="reference internal" href="../columns/vector.html"><em>Vector column</em></a>.</p>
<p>This is the reason that you can also complete the registered word &quot;日本&quot;
by query - &quot;nippon&quot;.</p>
<p>Execution example:</p>
Expand Down Expand Up @@ -422,11 +425,11 @@ <h2>7.14.2.4. How to update RK reading data<a class="headerlink" href="#how-to-u
</pre></div>
</div>
<p>This feature is very convenient because you can search registered word
even though Japanese IM is disabled.</p>
even though Japanese input method is disabled.</p>
<p>If there are multiple candidates as completed result, you can
customize priority to set the value of &quot;boost&quot; column in item_query
table.</p>
<p>Here is the example to customize priority for RK search.</p>
customize priority to set the value of <tt class="docutils literal"><span class="pre">boost</span></tt> column in
<tt class="docutils literal"><span class="pre">item_query</span></tt> table.</p>
<p>Here is an example to customize priority for prefix RK search:</p>
<p>Execution example:</p>
<div class="highlight-none"><div class="highlight"><pre>load --table event_query --each &#39;suggest_preparer(_id, type, item, sequence, time, pair_query)&#39;
[
Expand Down Expand Up @@ -541,7 +544,7 @@ <h3><a href="../../index.html">Table Of Contents</a></h3>
</li>
<li><a class="reference internal" href="#how-to-use">7.14.2.2. How to use</a></li>
<li><a class="reference internal" href="#how-it-learns">7.14.2.3. How it learns</a></li>
<li><a class="reference internal" href="#how-to-update-rk-reading-data">7.14.2.4. How to update RK reading data</a></li>
<li><a class="reference internal" href="#how-to-update-reading-data">7.14.2.4. How to update reading data</a></li>
</ul>
</li>
</ul>
Expand Down
2 changes: 1 addition & 1 deletion docs/searchindex.js

Large diffs are not rendered by default.

48 changes: 25 additions & 23 deletions docs/sources/reference/suggest/completion.txt
Expand Up @@ -37,11 +37,11 @@ For example, there is a registered word "日本". And "ニホン"
(it must be katakana) is registered as its reading. An user
can find "日本" by "ni", "二" or "に".

If you create dataset which is named as example by
:doc:`/reference/executables/groonga-suggest-create-dataset` command,
you can update pairs of registered word and its reading by loading
data to '_key' and 'kana' column of item_example table explicitly for
prefix RK search.
If you create dataset which is named as ``example`` by
:doc:`/reference/executables/groonga-suggest-create-dataset`
executable file, you can update pairs of registered word and its
reading by loading data to ``_key`` and ``kana`` column of
``item_example`` table explicitly for prefix RK search.

Cooccurrence search
^^^^^^^^^^^^^^^^^^^
Expand Down Expand Up @@ -135,7 +135,7 @@ Prefix search

Prefix search can find registered word that start with
user's input. This search doesn't care about romaji,
katakana and hiragana not like Prefix RK search.
katakana and hiragana not like prefix RK search.

This search isn't always ran. It's just ran when it's
requested explicitly or both prefix RK search and
Expand All @@ -160,7 +160,7 @@ How to use
.. ]
Groonga provides :doc:`/reference/commands/suggest` command to use
completion. `--type complete` option requests completion.
completion. ``--type complete`` option requests completion.

For example, here is an command to get completion results by
"en":
Expand All @@ -174,7 +174,7 @@ How it learns

Cooccurrence search uses learned data. They are based on
query logs, access logs and so on. To create learned data,
groonga needs user input sequence with time stamp and user
Groonga needs user input sequence with time stamp and user
submit input with time stamp.

For example, an user wants to search by "engine". The user
Expand All @@ -200,13 +200,13 @@ following command::
{"sequence": "1", "time": 1312950805.86057, "item": "engine", "type": "submit"}
]

How to update RK reading data
-----------------------------
How to update reading data
--------------------------

Groonga requires registered word and its reading for RK search, so load such data in the advance.
Groonga requires registered word and its reading for prefix RK
search. This section describes how to register a word and its reading.


Here is the example to register "日本" which means Japanese in english.
Here is an example to register "日本" which means Japan in English:

.. groonga-command
.. include:: ../../example/reference/suggest/complete/registered-word-japan.log
Expand All @@ -216,7 +216,7 @@ Here is the example to register "日本" which means Japanese in english.
.. ]
Here is the example to update RK data to complete "日本".
Here is an example to update reading data to complete "日本":

.. groonga-command
.. include:: ../../example/reference/suggest/complete/update-rk-data.log
Expand All @@ -225,17 +225,19 @@ Here is the example to update RK data to complete "日本".
.. {"_key":"日本", "kana":["ニホン", "ニッポン"]}
.. ]
Then you can complete registered word "日本" by RK input - "nihon".
Then you can complete registered word "日本" by Romaji input -
"nihon".

.. groonga-command
.. include:: ../../example/reference/suggest/complete/rk-search-nihon.log
.. suggest --table item_query --column kana --types complete --frequency_threshold 1 --query nihon
Without loading above RK data, you can't complete registered word "日本"
by query - "nihon".
Without loading above reading data, you can't complete registered word
"日本" by query - "nihon".

As the column type of item_query table is VECTOR_COLUMN, you can
register multiple readings for registered word.
You can register multiple readings for a registered word because
``kana`` column in ``item_query`` table is defined as a
:doc:`/reference/columns/vector`.

This is the reason that you can also complete the registered word "日本"
by query - "nippon".
Expand All @@ -245,13 +247,13 @@ by query - "nippon".
.. suggest --table item_query --column kana --types complete --frequency_threshold 1 --query nippon
This feature is very convenient because you can search registered word
even though Japanese IM is disabled.
even though Japanese input method is disabled.

If there are multiple candidates as completed result, you can
customize priority to set the value of "boost" column in item_query
table.
customize priority to set the value of ``boost`` column in
``item_query`` table.

Here is the example to customize priority for RK search.
Here is an example to customize priority for prefix RK search:

.. groonga-command
.. include:: ../../example/reference/suggest/complete/registered-word-japanese.log
Expand Down
4 changes: 2 additions & 2 deletions ja/docs/index.html
Expand Up @@ -270,7 +270,7 @@ <h1>Groonga ドキュメント<a class="headerlink" href="#groonga-documentation
<li class="toctree-l2"><a class="reference internal" href="reference/command.html">7.3. コマンド</a><ul>
<li class="toctree-l3"><a class="reference internal" href="reference/command/command_version.html">7.3.1. コマンドバージョン</a></li>
<li class="toctree-l3"><a class="reference internal" href="reference/command/output_format.html">7.3.2. 出力形式</a></li>
<li class="toctree-l3"><a class="reference internal" href="reference/command/request_id.html">7.3.3. Request ID</a></li>
<li class="toctree-l3"><a class="reference internal" href="reference/command/request_id.html">7.3.3. リクエストID</a></li>
<li class="toctree-l3"><a class="reference internal" href="reference/command/return_code.html">7.3.4. リターンコード</a></li>
<li class="toctree-l3"><a class="reference internal" href="reference/commands/cache_limit.html">7.3.5. <tt class="docutils literal"><span class="pre">cache_limit</span></tt></a></li>
<li class="toctree-l3"><a class="reference internal" href="reference/commands/check.html">7.3.6. <tt class="docutils literal"><span class="pre">check</span></tt></a></li>
Expand Down Expand Up @@ -329,7 +329,7 @@ <h1>Groonga ドキュメント<a class="headerlink" href="#groonga-documentation
<li class="toctree-l2"><a class="reference internal" href="reference/normalizers.html">7.7. ノーマライザー</a><ul>
<li class="toctree-l3"><a class="reference internal" href="reference/normalizers.html#summary">7.7.1. 概要</a></li>
<li class="toctree-l3"><a class="reference internal" href="reference/normalizers.html#built-in-normalizers">7.7.2. 組み込みノーマライザー</a></li>
<li class="toctree-l3"><a class="reference internal" href="reference/normalizers.html#additional-normalizers">7.7.3. 追加のノーマライザー</a></li>
<li class="toctree-l3"><a class="reference internal" href="reference/normalizers.html#additional-normalizers">7.7.3. 追加のノーマライザー一覧</a></li>
<li class="toctree-l3"><a class="reference internal" href="reference/normalizers.html#see-also">7.7.4. 参考</a></li>
</ul>
</li>
Expand Down
4 changes: 2 additions & 2 deletions ja/docs/reference.html
Expand Up @@ -107,7 +107,7 @@ <h1>7. リファレンスマニュアル<a class="headerlink" href="#reference-m
<li class="toctree-l1"><a class="reference internal" href="reference/command.html">7.3. コマンド</a><ul>
<li class="toctree-l2"><a class="reference internal" href="reference/command/command_version.html">7.3.1. コマンドバージョン</a></li>
<li class="toctree-l2"><a class="reference internal" href="reference/command/output_format.html">7.3.2. 出力形式</a></li>
<li class="toctree-l2"><a class="reference internal" href="reference/command/request_id.html">7.3.3. Request ID</a></li>
<li class="toctree-l2"><a class="reference internal" href="reference/command/request_id.html">7.3.3. リクエストID</a></li>
<li class="toctree-l2"><a class="reference internal" href="reference/command/return_code.html">7.3.4. リターンコード</a></li>
<li class="toctree-l2"><a class="reference internal" href="reference/commands/cache_limit.html">7.3.5. <tt class="docutils literal"><span class="pre">cache_limit</span></tt></a></li>
<li class="toctree-l2"><a class="reference internal" href="reference/commands/check.html">7.3.6. <tt class="docutils literal"><span class="pre">check</span></tt></a></li>
Expand Down Expand Up @@ -166,7 +166,7 @@ <h1>7. リファレンスマニュアル<a class="headerlink" href="#reference-m
<li class="toctree-l1"><a class="reference internal" href="reference/normalizers.html">7.7. ノーマライザー</a><ul>
<li class="toctree-l2"><a class="reference internal" href="reference/normalizers.html#summary">7.7.1. 概要</a></li>
<li class="toctree-l2"><a class="reference internal" href="reference/normalizers.html#built-in-normalizers">7.7.2. 組み込みノーマライザー</a></li>
<li class="toctree-l2"><a class="reference internal" href="reference/normalizers.html#additional-normalizers">7.7.3. 追加のノーマライザー</a></li>
<li class="toctree-l2"><a class="reference internal" href="reference/normalizers.html#additional-normalizers">7.7.3. 追加のノーマライザー一覧</a></li>
<li class="toctree-l2"><a class="reference internal" href="reference/normalizers.html#see-also">7.7.4. 参考</a></li>
</ul>
</li>
Expand Down
2 changes: 1 addition & 1 deletion ja/docs/reference/api/grn_column.html
Expand Up @@ -345,7 +345,7 @@ <h2>7.18.3.3. リファレンス<a class="headerlink" href="#reference" title="
<col class="field-body" />
<tbody valign="top">
<tr class="field-odd field"><th class="field-name">パラメタ:</th><td class="field-body"><ul class="first simple">
<li><strong>column</strong> -- The column to be truncated.</li>
<li><strong>column</strong> -- truncate対象のカラム。</li>
</ul>
</td>
</tr>
Expand Down
8 changes: 4 additions & 4 deletions ja/docs/reference/api/grn_db.html
Expand Up @@ -204,7 +204,7 @@ <h2>7.18.7.3. リファレンス<a class="headerlink" href="#reference" title="
grn_rc <tt class="descname">grn_db_recover</tt><big>(</big><a class="reference internal" href="grn_ctx.html#c.grn_ctx" title="grn_ctx">grn_ctx</a><em>&nbsp;*ctx</em>, <a class="reference internal" href="grn_obj.html#c.grn_obj" title="grn_obj">grn_obj</a><em>&nbsp;*db</em><big>)</big><a class="headerlink" href="#c.grn_db_recover" title="この定義へのパーマリンク"></a></dt>
<dd><div class="admonition note">
<p class="first admonition-title">注釈</p>
<p class="last">This is an experimental API.</p>
<p class="last">これは実験的なAPIです。</p>
</div>
<div class="admonition note">
<p class="first admonition-title">注釈</p>
Expand All @@ -219,13 +219,13 @@ <h2>7.18.7.3. リファレンス<a class="headerlink" href="#reference" title="
can be recovered.</p>
<p>This API uses lock existence for checking whether the database is
broken or not.</p>
<p>Here are recoverable cases:</p>
<p>以下は復旧可能なケースです。</p>
<blockquote>
<div><ul class="simple">
<li>Index column is broken. The index column must have source column.</li>
</ul>
</div></blockquote>
<p>Here are unrecoverable cases:</p>
<p>以下は復旧できないケースです。</p>
<blockquote>
<div><ul class="simple">
<li>Object name management feature is broken.</li>
Expand All @@ -243,7 +243,7 @@ <h2>7.18.7.3. リファレンス<a class="headerlink" href="#reference" title="
<col class="field-body" />
<tbody valign="top">
<tr class="field-odd field"><th class="field-name">パラメタ:</th><td class="field-body"><ul class="first simple">
<li><strong>db</strong> -- The database to be recovered.</li>
<li><strong>db</strong> -- 復旧対象のデータベース。</li>
</ul>
</td>
</tr>
Expand Down

0 comments on commit 2361730

Please sign in to comment.