rroonga 3.1.0-x86-mingw32 → 3.1.1-x86-mingw32

data/vendor/local/share/doc/groonga/en/html/_sources/tutorial/micro_blog.txt

@@ -8,7 +8,7 @@
 マイクロブログ検索システムの作成
 ================================
 
-これまで学んだgroongaの機能を用いて、マイクロブログの検索システムを作成してみましょう。マイクロブログとは、Twitterのような短いメッセージを投稿するブログです。
+これまで学んだGroongaの機能を用いて、マイクロブログの検索システムを作成してみましょう。マイクロブログとは、Twitterのような短いメッセージを投稿するブログです。
 
 テーブルの作成
 --------------
@@ -265,7 +265,7 @@ Commentsテーブルのlast_modifiedカラムは、Time型です。この型で
  table_create --name HashTags --flags TABLE_HASH_KEY --key_type ShortText
  table_create --name Bigram --flags TABLE_PAT_KEY|KEY_NORMALIZE --key_type ShortText --default_tokenizer TokenBigram
  table_create --name GeoIndex --flags TABLE_PAT_KEY --key_type WGS84GeoPoint
- 
+
  column_create --table Users --name name --flags COLUMN_SCALAR --type ShortText
  column_create --table Users --name follower --flags COLUMN_VECTOR --type Users
  column_create --table Users --name favorites --flags COLUMN_VECTOR --type Comments
@@ -273,7 +273,7 @@ Commentsテーブルのlast_modifiedカラムは、Time型です。この型で
  column_create --table Users --name location_str --flags COLUMN_SCALAR --type ShortText
  column_create --table Users --name description --flags COLUMN_SCALAR --type ShortText
  column_create --table Users --name followee --flags COLUMN_INDEX --type Users --source follower
- 
+
  column_create --table Comments --name comment --flags COLUMN_SCALAR --type ShortText
  column_create --table Comments --name last_modified --flags COLUMN_SCALAR --type Time
  column_create --table Comments --name replied_to --flags COLUMN_SCALAR --type Comments
@@ -282,15 +282,15 @@ Commentsテーブルのlast_modifiedカラムは、Time型です。この型で
  column_create --table Comments --name location --flags COLUMN_SCALAR --type WGS84GeoPoint
  column_create --table Comments --name posted_by --flags COLUMN_SCALAR --type Users
  column_create --table Comments --name favorited_by --flags COLUMN_INDEX --type Users --source favorites
- 
+
  column_create --table HashTags --name hash_index --flags COLUMN_INDEX --type Comments --source hash_tags
- 
+
  column_create --table Bigram --name users_index --flags COLUMN_INDEX|WITH_POSITION|WITH_SECTION --type Users --source name,location_str,description
  column_create --table Bigram --name comment_index --flags COLUMN_INDEX|WITH_POSITION --type Comments --source comment
- 
+
  column_create --table GeoIndex --name users_location --type Users --flags COLUMN_INDEX --source location
  column_create --table GeoIndex --name comments_location --type Comments --flags COLUMN_INDEX --source location
- 
+
  load --table Users
  [
    {
@@ -321,7 +321,7 @@ Commentsテーブルのlast_modifiedカラムは、Time型です。この型で
      "description": "がおがお"
    }
  ]
- 
+
  load --table Comments
  [
    {

data/vendor/local/share/doc/groonga/en/html/_sources/tutorial/network.txt

@@ -10,21 +10,21 @@
 Remote access
 =============
 
-You can use groonga as a server which allows remote access. Groonga supports the original protocol (gqtp), the memcached binary protocol and HTTP.
+You can use Groonga as a server which allows remote access. Groonga supports the original protocol (GQTP), the memcached binary protocol and HTTP.
 
-Groonga query transfer protocol (gqtp)
+Groonga Query Transfer Protocol (GQTP)
 --------------------------------------
 
-How to run a gqtp server
+How to run a GQTP server
 ^^^^^^^^^^^^^^^^^^^^^^^^
 
-Groonga has a special protocol, named groonga query transfer ptorotocl (gqtp), for remote access to a database. The following form shows how to run groonga as a gqtp server.
+Groonga has a special protocol, named Groonga Query Transfer Protocol (GQTP), for remote access to a database. The following form shows how to run Groonga as a GQTP server.
 
 Form::
 
   groonga [-p PORT_NUMBER] -s DB_PATH
 
-The `-s` option specifies to run groonga as a server. DB_PATH specifies the path of the existing database to be hosted. The `-p` option and its argument, PORT_NUMBER, specify the port number of the server. The default port number is 10041, which is used when you don't specify PORT_NUMBER.
+The `-s` option specifies to run Groonga as a server. DB_PATH specifies the path of the existing database to be hosted. The `-p` option and its argument, PORT_NUMBER, specify the port number of the server. The default port number is 10041, which is used when you don't specify PORT_NUMBER.
 
 The following command runs a server that listens on the default port number. The server accepts operations to the specified database.
 
@@ -34,16 +34,16 @@ Execution example::
   Ctrl-c
   %
 
-How to run a gqtp daemon
+How to run a GQTP daemon
 ^^^^^^^^^^^^^^^^^^^^^^^^
 
-You can also run a gqtp server as a daemon by using the `-d` option, instead of the `-s` option.
+You can also run a GQTP server as a daemon by using the `-d` option, instead of the `-s` option.
 
 Form::
 
   groonga [-p PORT_NUMBER] -d DB_PATH
 
-A groonga daemon prints its process ID as follows. In this example, the process ID is 12345. Then, the daemon opens a specified database and accepts operations to that database.
+A Groonga daemon prints its process ID as follows. In this example, the process ID is 12345. Then, the daemon opens a specified database and accepts operations to that database.
 
 Execution example::
 
@@ -51,16 +51,16 @@ Execution example::
   12345
   %
 
-How to run a gqtp client
+How to run a GQTP client
 ^^^^^^^^^^^^^^^^^^^^^^^^
 
-You can run groonga as a gqtp client as follows:
+You can run Groonga as a GQTP client as follows:
 
 Form::
 
   groonga [-p PORT_NUMBER] -c [HOST_NAME_OR_IP_ADDRESS]
 
-This command establishes a connection with a gqtp server and then enters into interactive mode. HOST_NAME_OR_IP_ADDRESS specifies the hostname or the IP address of the server. If not specifed, groonga uses the default hostname "localhost". The `-p` option and its argument, PORT_NUMBER, specify the port number of the server. If not specified, groonga uses the default port number 10041.
+This command establishes a connection with a GQTP server and then enters into interactive mode. HOST_NAME_OR_IP_ADDRESS specifies the hostname or the IP address of the server. If not specified, Groonga uses the default hostname "localhost". The `-p` option and its argument, PORT_NUMBER, specify the port number of the server. If not specified, Groonga uses the default port number 10041.
 
 .. groonga-command
 .. include:: ../example/tutorial/network-1.log
@@ -69,12 +69,12 @@ This command establishes a connection with a gqtp server and then enters into in
 .. .. > ctrl-d
 .. .. %
 
-In interactive mode, groonga reads commands from the standard input and executes them one by one.
+In interactive mode, Groonga reads commands from the standard input and executes them one by one.
 
-How to terminate a gqtp server
+How to terminate a GQTP server
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-You can terminate a gqtp server with a :doc:`/reference/commands/shutdown` command.
+You can terminate a GQTP server with a :doc:`/reference/commands/shutdown` command.
 
 .. groonga-command
 .. include:: ../example/tutorial/network-2.log
@@ -85,7 +85,7 @@ You can terminate a gqtp server with a :doc:`/reference/commands/shutdown` comma
 Memcached binary protocol
 -------------------------
 
-Groonga supports the memcached binary protocol. The following form shows how to run groonga as a memcached binary protocol server daemon.
+Groonga supports the memcached binary protocol. The following form shows how to run Groonga as a memcached binary protocol server daemon.
 
 Form::
 
@@ -99,7 +99,7 @@ Hypertext transfer protocol (HTTP)
 How to run an HTTP server
 ^^^^^^^^^^^^^^^^^^^^^^^^^
 
-Groonga supports the hypertext transfer protocol (HTTP). The following form shows how to run groonga as an HTTP server daemon.
+Groonga supports the hypertext transfer protocol (HTTP). The following form shows how to run Groonga as an HTTP server daemon.
 
 Form::
 
@@ -130,7 +130,6 @@ The following example shows how to send commands to an HTTP server.
 .. .. http://HOST_NAME_OR_IP_ADDRESS[:PORT_NUMBER]/d/status
 .. .. Executed command:
 .. status
-.. .. 
 .. .. http://HOST_NAME_OR_IP_ADDRESS[:PORT_NUMBER]/d/select?table=Site&query=title:@this
 .. .. Executed command:
 .. select --table Site --query title:@this
@@ -138,9 +137,9 @@ The following example shows how to send commands to an HTTP server.
 Administration tool (HTTP)
 --------------------------
 
-An HTTP server of groonga provides a browser based administration tool that makes database management easy. After starting an HTTP server, you can use the administration tool by accessing http://HOST_NAME_OR_IP_ADDRESS[:PORT_NUMBER]/. Note that Javascript must be enabled for the tool to work properly.
+An HTTP server of Groonga provides a browser based administration tool that makes database management easy. After starting an HTTP server, you can use the administration tool by accessing http://HOST_NAME_OR_IP_ADDRESS[:PORT_NUMBER]/. Note that Javascript must be enabled for the tool to work properly.
 
 Security issues
 ---------------
 
-Groonga servers don't support user authentication. Everyone can view and modify databases hosted by groonga servers. You are recommended to restrict IP addresses that can access groonga servers. You can use iptables or similar for this purpose.
+Groonga servers don't support user authentication. Everyone can view and modify databases hosted by Groonga servers. You are recommended to restrict IP addresses that can access Groonga servers. You can use iptables or similar for this purpose.

data/vendor/local/share/doc/groonga/en/html/_sources/tutorial/patricia_trie.txt

@@ -8,7 +8,7 @@
 パトリシア木による前方一致検索
 ==============================
 
-groongaのテーブルは、テーブル作成時にパトリシア木オプションを指定すると、前方一致検索を行うことができます。また、追加のオプションを指定することにより、主キーの後方一致検索をも行うことができます。
+Groongaのテーブルは、テーブル作成時にパトリシア木オプションを指定すると、前方一致検索を行うことができます。また、追加のオプションを指定することにより、主キーの後方一致検索をも行うことができます。
 
 主キーによる前方一致検索
 ------------------------

data/vendor/local/share/doc/groonga/en/html/_sources/tutorial/query_expansion.txt

@@ -8,7 +8,7 @@
 クエリ拡張
 ==========
 
-groongaでは、 :doc:`/reference/commands/select` コマンドにquery_expanderパラメータを指定することによって、ユーザが指定した検索文字列を適宜拡張することが可能です。
+Groongaでは、 :doc:`/reference/commands/select` コマンドにquery_expanderパラメータを指定することによって、ユーザが指定した検索文字列を適宜拡張することが可能です。
 
 たとえば、ユーザが'シークヮーサー'という文字列で検索した場合に、'シークヮーサー OR シークァーサー'で検索した場合と同一の結果を返すことによって、本来ユーザが必要とする結果をよりもれなく検索できるようになります。
 

data/vendor/local/share/doc/groonga/en/html/_sources/tutorial/search.txt

@@ -10,7 +10,7 @@
 さまざまな検索条件の指定
 ========================
 
-groongaは、JavaScriptに似た文法での条件絞込や、計算した値を用いたソートを行うことができます。また、位置情報(緯度・経度)を用いた絞込・ソートを行うことができます。
+Groongaは、JavaScriptに似た文法での条件絞込や、計算した値を用いたソートを行うことができます。また、位置情報(緯度・経度)を用いた絞込・ソートを行うことができます。
 
 JavaScriptに似た文法での絞込・全文検索
 --------------------------------------
@@ -69,7 +69,7 @@ sortbyパラメータには、
 位置情報を用いた絞込・ソート
 ----------------------------
 
-groongaでは、位置情報（経緯度）を保存することができます。また、保存した経緯度を用いて絞込やソートができます。
+Groongaでは、位置情報（経緯度）を保存することができます。また、保存した経緯度を用いて絞込やソートができます。
 
 位置情報を保存するためのカラムの型として、TokyoGeoPoint/WGS84GeoPointの２つの型があります。前者は日本測地系、後者は世界測地系(WGS84相当)の経緯度を保存します。
 

data/vendor/local/share/doc/groonga/en/html/characteristic.html

@@ -7,7 +7,7 @@
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
     
-    <title>1. Characteristics of groonga &mdash; Groonga v3.1.0 documentation</title>
+    <title>1. Characteristics of Groonga &mdash; Groonga v3.1.1 documentation</title>
     
     <link rel="stylesheet" href="_static/groonga.css" type="text/css" />
     <link rel="stylesheet" href="_static/pygments.css" type="text/css" />
@@ -15,7 +15,7 @@
     <script type="text/javascript">
       var DOCUMENTATION_OPTIONS = {
         URL_ROOT:    './',
-        VERSION:     '3.1.0',
+        VERSION:     '3.1.1',
         COLLAPSE_INDEX: false,
         FILE_SUFFIX: '.html',
         HAS_SOURCE:  true
@@ -25,7 +25,7 @@
     <script type="text/javascript" src="_static/underscore.js"></script>
     <script type="text/javascript" src="_static/doctools.js"></script>
     <link rel="shortcut icon" href="_static/favicon.ico"/>
-    <link rel="top" title="Groonga v3.1.0 documentation" href="index.html" />
+    <link rel="top" title="Groonga v3.1.1 documentation" href="index.html" />
     <link rel="next" title="2. Install" href="install.html" />
     <link rel="prev" title="groonga documentation" href="index.html" /> 
   </head>
@@ -59,7 +59,7 @@
         <li class="right" >
           <a href="index.html" title="groonga documentation"
              accesskey="P">previous</a> |</li>
-        <li><a href="index.html">Groonga v3.1.0 documentation</a> &raquo;</li> 
+        <li><a href="index.html">Groonga v3.1.1 documentation</a> &raquo;</li> 
       </ul>
     </div>  
 
@@ -69,23 +69,23 @@
           <div class="body">
             
   <div class="section" id="characteristics-of-groonga">
-<h1>1. Characteristics of groonga<a class="headerlink" href="#characteristics-of-groonga" title="Permalink to this headline">¶</a></h1>
+<h1>1. Characteristics of Groonga<a class="headerlink" href="#characteristics-of-groonga" title="Permalink to this headline">¶</a></h1>
 <div class="section" id="groonga-overview">
 <h2>1.1. Groonga overview<a class="headerlink" href="#groonga-overview" title="Permalink to this headline">¶</a></h2>
-<p>Groonga is a fast and accurate full text search engine based on inverted index. One of the characteristics of groonga is that a newly registered document instantly appears in search results. Also, groonga allows updates without read locks. These characteristics result in superior performance on real-time applications.</p>
-<p>Groonga is also a column-oriented database management system (DBMS). Compared with well-known row-oriented systems, such as MySQL and PostgreSQL, column-oriented systems are more suited for aggregate queries. Due to this advantage, groonga can cover weakness of row-oriented systems.</p>
-<p>The basic functions of groonga are provided in a C library. Also, libraries for using groonga in other languages, such as Ruby, are provided by related projects. In addition, groonga-based storage engines are provided for MySQL and PostgreSQL. These libraries and storage engines allow any application to use groonga. See <a class="reference external" href="http://groonga.org/users/">usage examples</a>.</p>
+<p>Groonga is a fast and accurate full text search engine based on inverted index. One of the characteristics of Groonga is that a newly registered document instantly appears in search results. Also, Groonga allows updates without read locks. These characteristics result in superior performance on real-time applications.</p>
+<p>Groonga is also a column-oriented database management system (DBMS). Compared with well-known row-oriented systems, such as MySQL and PostgreSQL, column-oriented systems are more suited for aggregate queries. Due to this advantage, Groonga can cover weakness of row-oriented systems.</p>
+<p>The basic functions of Groonga are provided in a C library. Also, libraries for using Groonga in other languages, such as Ruby, are provided by related projects. In addition, groonga-based storage engines are provided for MySQL and PostgreSQL. These libraries and storage engines allow any application to use Groonga. See <a class="reference external" href="http://groonga.org/users/">usage examples</a>.</p>
 </div>
 <div class="section" id="full-text-search-and-instant-update">
 <h2>1.2. Full text search and Instant update<a class="headerlink" href="#full-text-search-and-instant-update" title="Permalink to this headline">¶</a></h2>
 <p>In widely used DBMSs, updates are immediately processed, for example, a newly registered record appears in the result of the next query. In contrast, some full text search engines do not support instant updates, because it is difficult to dynamically update inverted indexes, the underlying data structure.</p>
-<p>Groonga also uses inverted indexes but supports instant updates. In addition, groonga allows you to search documents even when updating the document collection. Due to these superior characteristics, groonga is very flexible as a full text search engine. Also, groonga always shows good performance because it divides a large task, inverted index merging, into smaller tasks.</p>
+<p>Groonga also uses inverted indexes but supports instant updates. In addition, Groonga allows you to search documents even when updating the document collection. Due to these superior characteristics, Groonga is very flexible as a full text search engine. Also, Groonga always shows good performance because it divides a large task, inverted index merging, into smaller tasks.</p>
 </div>
 <div class="section" id="column-store-and-aggregate-query">
 <h2>1.3. Column store and aggregate query<a class="headerlink" href="#column-store-and-aggregate-query" title="Permalink to this headline">¶</a></h2>
 <p>People can collect more than enough data in the Internet era. However, it is difficult to extract informative knowledge from a large database, and such a task requires a many-sided analysis through trial and error. For example, search refinement by date, time and location may reveal hidden patterns. Aggregate queries are useful to perform this kind of tasks.</p>
 <p>An aggregate query groups search results by specified column values and then counts the number of records in each group. For example, an aggregate query in which a location column is specified counts the number of records per location. Making a graph from the result of an aggregate query against a date column is an easy way to visualize changes over time. Also, a combination of refinement by location and an aggregate query against a date column allows visualization of changes over time in specific location. Thus refinement and aggregation are important to perform data mining.</p>
-<p>A column-oriented architecture allows groonga to efficiently process aggregate queries because a column-oriented database, which stores records by column, allows an aggregate query to access only a specified column. On the other hand, an aggregate query on a row-oriented database, which stores records by row, has to access neighbor columns, even though those columns are not required.</p>
+<p>A column-oriented architecture allows Groonga to efficiently process aggregate queries because a column-oriented database, which stores records by column, allows an aggregate query to access only a specified column. On the other hand, an aggregate query on a row-oriented database, which stores records by row, has to access neighbor columns, even though those columns are not required.</p>
 </div>
 <div class="section" id="inverted-index-and-tokenizer">
 <h2>1.4. Inverted index and tokenizer<a class="headerlink" href="#inverted-index-and-tokenizer" title="Permalink to this headline">¶</a></h2>
@@ -96,24 +96,24 @@
 <div class="section" id="sharable-storage-and-read-lock-free">
 <h2>1.5. Sharable storage and read lock-free<a class="headerlink" href="#sharable-storage-and-read-lock-free" title="Permalink to this headline">¶</a></h2>
 <p>Multi-core processors are mainstream today and the number of cores per processor is increasing. In order to exploit multiple cores, executing multiple queries in parallel or dividing a query into sub-queries for parallel processing is becoming more important.</p>
-<p>A database of groonga can be shared with multiple threads/processes. Also, multiple threads/processes can execute read queries in parallel even when another thread/process is executing an update query because groonga uses read lock-free data structures. This feature is suited to a real-time application that needs to update a database while executing read queries. In addition, groonga allows you to build flexible systems. For example, a database can receive read queries through the built-in HTTP server of groonga while accepting update queries through MySQL.</p>
+<p>A database of Groonga can be shared with multiple threads/processes. Also, multiple threads/processes can execute read queries in parallel even when another thread/process is executing an update query because Groonga uses read lock-free data structures. This feature is suited to a real-time application that needs to update a database while executing read queries. In addition, Groonga allows you to build flexible systems. For example, a database can receive read queries through the built-in HTTP server of Groonga while accepting update queries through MySQL.</p>
 </div>
 <div class="section" id="geo-location-latitude-and-longitude-search">
 <h2>1.6. Geo-location (latitude and longitude) search<a class="headerlink" href="#geo-location-latitude-and-longitude-search" title="Permalink to this headline">¶</a></h2>
 <p>Location services are getting more convenient because of mobile devices with GPS. For example, if you are going to have lunch or dinner at a nearby restaurant, a local search service for restaurants may be very useful, and for such services, fast geo-location search is becoming more important.</p>
-<p>Groonga provides inverted index-based fast geo-location search, which supports a query to find points in a rectangle or circle. Groonga gives high priority to points near the center of an area. Also, groonga supports distance measurement and you can sort points by distance from any point.</p>
+<p>Groonga provides inverted index-based fast geo-location search, which supports a query to find points in a rectangle or circle. Groonga gives high priority to points near the center of an area. Also, Groonga supports distance measurement and you can sort points by distance from any point.</p>
 </div>
 <div class="section" id="groonga-library">
 <h2>1.7. Groonga library<a class="headerlink" href="#groonga-library" title="Permalink to this headline">¶</a></h2>
-<p>The basic functions of groonga are provided in a C library and any application can use groonga as a full text search engine or a column-oriented database. Also, libraries for languages other than C/C++, such as Ruby, are provided in related projects. See <a class="reference external" href="http://groonga.org/related-projects.html">related projects</a> for details.</p>
+<p>The basic functions of Groonga are provided in a C library and any application can use Groonga as a full text search engine or a column-oriented database. Also, libraries for languages other than C/C++, such as Ruby, are provided in related projects. See <a class="reference external" href="http://groonga.org/related-projects.html">related projects</a> for details.</p>
 </div>
 <div class="section" id="groonga-server">
 <h2>1.8. Groonga server<a class="headerlink" href="#groonga-server" title="Permalink to this headline">¶</a></h2>
-<p>Groonga provides a built-in server command which supports HTTP, the memcached binary protocol and the groonga query transfer protocol (gqtp). Also, a groonga server supports query caching, which significantly reduces response time for repeated read queries. Using this command, groonga is available even on a server that does not allow you to install new libraries.</p>
+<p>Groonga provides a built-in server command which supports HTTP, the memcached binary protocol and the Groonga Query Transfer Protocol (GQTP). Also, a Groonga server supports query caching, which significantly reduces response time for repeated read queries. Using this command, Groonga is available even on a server that does not allow you to install new libraries.</p>
 </div>
 <div class="section" id="groonga-storage-engine">
 <h2>1.9. Groonga storage engine<a class="headerlink" href="#groonga-storage-engine" title="Permalink to this headline">¶</a></h2>
-<p>Groonga works not only as an independent column-oriented DBMS but also as storage engines of well-known DBMSs. For example, <a class="reference external" href="http://mroonga.org/">mroonga</a> is a MySQL pluggable storage engine using groonga. By using mroonga, you can use groonga for column-oriented storage and full text search. A combination of a built-in storage engine, MyISAM or InnoDB, and a groonga-based full text search engine is also available. All the combinations have good and bad points and the best one depends on the application. See <a class="reference external" href="http://groonga.org/related-projects.html">related projects</a> for details.</p>
+<p>Groonga works not only as an independent column-oriented DBMS but also as storage engines of well-known DBMSs. For example, <a class="reference external" href="http://mroonga.org/">mroonga</a> is a MySQL pluggable storage engine using Groonga. By using mroonga, you can use Groonga for column-oriented storage and full text search. A combination of a built-in storage engine, MyISAM or InnoDB, and a groonga-based full text search engine is also available. All the combinations have good and bad points and the best one depends on the application. See <a class="reference external" href="http://groonga.org/related-projects.html">related projects</a> for details.</p>
 </div>
 </div>
 
@@ -125,7 +125,7 @@
         <div class="sphinxsidebarwrapper">
   <h3><a href="index.html">Table Of Contents</a></h3>
   <ul>
-<li><a class="reference internal" href="#">1. Characteristics of groonga</a><ul>
+<li><a class="reference internal" href="#">1. Characteristics of Groonga</a><ul>
 <li><a class="reference internal" href="#groonga-overview">1.1. Groonga overview</a></li>
 <li><a class="reference internal" href="#full-text-search-and-instant-update">1.2. Full text search and Instant update</a></li>
 <li><a class="reference internal" href="#column-store-and-aggregate-query">1.3. Column store and aggregate query</a></li>
@@ -179,7 +179,7 @@
         <li class="right" >
           <a href="index.html" title="groonga documentation"
              >previous</a> |</li>
-        <li><a href="index.html">Groonga v3.1.0 documentation</a> &raquo;</li> 
+        <li><a href="index.html">Groonga v3.1.1 documentation</a> &raquo;</li> 
       </ul>
     </div>
     <div class="footer">

data/vendor/local/share/doc/groonga/en/html/community.html

@@ -7,7 +7,7 @@
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
     
-    <title>3. Community &mdash; Groonga v3.1.0 documentation</title>
+    <title>3. Community &mdash; Groonga v3.1.1 documentation</title>
     
     <link rel="stylesheet" href="_static/groonga.css" type="text/css" />
     <link rel="stylesheet" href="_static/pygments.css" type="text/css" />
@@ -15,7 +15,7 @@
     <script type="text/javascript">
       var DOCUMENTATION_OPTIONS = {
         URL_ROOT:    './',
-        VERSION:     '3.1.0',
+        VERSION:     '3.1.1',
         COLLAPSE_INDEX: false,
         FILE_SUFFIX: '.html',
         HAS_SOURCE:  true
@@ -25,7 +25,7 @@
     <script type="text/javascript" src="_static/underscore.js"></script>
     <script type="text/javascript" src="_static/doctools.js"></script>
     <link rel="shortcut icon" href="_static/favicon.ico"/>
-    <link rel="top" title="Groonga v3.1.0 documentation" href="index.html" />
+    <link rel="top" title="Groonga v3.1.1 documentation" href="index.html" />
     <link rel="next" title="4. Tutorial" href="tutorial.html" />
     <link rel="prev" title="2.8. Others" href="install/others.html" /> 
   </head>
@@ -59,7 +59,7 @@
         <li class="right" >
           <a href="install/others.html" title="2.8. Others"
              accesskey="P">previous</a> |</li>
-        <li><a href="index.html">Groonga v3.1.0 documentation</a> &raquo;</li> 
+        <li><a href="index.html">Groonga v3.1.1 documentation</a> &raquo;</li> 
       </ul>
     </div>  
 
@@ -70,11 +70,11 @@
             
   <div class="section" id="community">
 <h1>3. Community<a class="headerlink" href="#community" title="Permalink to this headline">¶</a></h1>
-<p>There are some places for sharing groonga information.
+<p>There are some places for sharing Groonga information.
 We welcome you to join our community.</p>
 <div class="section" id="mailing-list">
 <h2>3.1. Mailing List<a class="headerlink" href="#mailing-list" title="Permalink to this headline">¶</a></h2>
-<p>There are mailing lists for discussion about groonga.</p>
+<p>There are mailing lists for discussion about Groonga.</p>
 <dl class="docutils">
 <dt>For English speakers</dt>
 <dd><a class="reference external" href="http://lists.sourceforge.net/mailman/listinfo/groonga-talk">groonga-talk&#64;lists.sourceforge.net</a></dd>
@@ -84,16 +84,16 @@ We welcome you to join our community.</p>
 </div>
 <div class="section" id="twitter">
 <h2>3.2. Twitter<a class="headerlink" href="#twitter" title="Permalink to this headline">¶</a></h2>
-<p><a class="reference external" href="https://twitter.com/groonga/">&#64;groonga</a> tweets groonga related
+<p><a class="reference external" href="https://twitter.com/groonga/">&#64;groonga</a> tweets Groonga related
 information.</p>
-<p>Please follow the account to get the latest groonga related
+<p>Please follow the account to get the latest Groonga related
 information!</p>
 </div>
 <div class="section" id="facebook">
 <h2>3.3. Facebook<a class="headerlink" href="#facebook" title="Permalink to this headline">¶</a></h2>
-<p><a class="reference external" href="http://www.facebook.com/groonga">groonga page on Facebook</a> shares
-groonga related information.</p>
-<p>Please like the page to get the latest groonga related information!</p>
+<p><a class="reference external" href="http://www.facebook.com/groonga">Groonga page on Facebook</a> shares
+Groonga related information.</p>
+<p>Please like the page to get the latest Groonga related information!</p>
 </div>
 </div>
 
@@ -153,7 +153,7 @@ groonga related information.</p>
         <li class="right" >
           <a href="install/others.html" title="2.8. Others"
              >previous</a> |</li>
-        <li><a href="index.html">Groonga v3.1.0 documentation</a> &raquo;</li> 
+        <li><a href="index.html">Groonga v3.1.1 documentation</a> &raquo;</li> 
       </ul>
     </div>
     <div class="footer">

data/vendor/local/share/doc/groonga/en/html/contribution/development/com.html

@@ -7,7 +7,7 @@
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
     
-    <title>13.2.2. groonga 通信アーキテクチャ &mdash; Groonga v3.1.0 documentation</title>
+    <title>13.3.2. Groonga 通信アーキテクチャ &mdash; Groonga v3.1.1 documentation</title>
     
     <link rel="stylesheet" href="../../_static/groonga.css" type="text/css" />
     <link rel="stylesheet" href="../../_static/pygments.css" type="text/css" />
@@ -15,7 +15,7 @@
     <script type="text/javascript">
       var DOCUMENTATION_OPTIONS = {
         URL_ROOT:    '../../',
-        VERSION:     '3.1.0',
+        VERSION:     '3.1.1',
         COLLAPSE_INDEX: false,
         FILE_SUFFIX: '.html',
         HAS_SOURCE:  true
@@ -25,10 +25,10 @@
     <script type="text/javascript" src="../../_static/underscore.js"></script>
     <script type="text/javascript" src="../../_static/doctools.js"></script>
     <link rel="shortcut icon" href="../../_static/favicon.ico"/>
-    <link rel="top" title="Groonga v3.1.0 documentation" href="../../index.html" />
-    <link rel="up" title="13.2. groonga開発者向け情報" href="../development.html" />
-    <link rel="next" title="13.2.3. ユーザーと協力して開発をうまく進めていくための指針" href="cooperation.html" />
-    <link rel="prev" title="13.2.1. Repository" href="repository.html" /> 
+    <link rel="top" title="Groonga v3.1.1 documentation" href="../../index.html" />
+    <link rel="up" title="13.3. groonga開発者向け情報" href="../development.html" />
+    <link rel="next" title="13.3.3. ユーザーと協力して開発をうまく進めていくための指針" href="cooperation.html" />
+    <link rel="prev" title="13.3.1. Repository" href="repository.html" /> 
   </head>
   <body>
 <div class="header">
@@ -55,14 +55,14 @@
           <a href="../../genindex.html" title="General Index"
              accesskey="I">index</a></li>
         <li class="right" >
-          <a href="cooperation.html" title="13.2.3. ユーザーと協力して開発をうまく進めていくための指針"
+          <a href="cooperation.html" title="13.3.3. ユーザーと協力して開発をうまく進めていくための指針"
              accesskey="N">next</a> |</li>
         <li class="right" >
-          <a href="repository.html" title="13.2.1. Repository"
+          <a href="repository.html" title="13.3.1. Repository"
              accesskey="P">previous</a> |</li>
-        <li><a href="../../index.html">Groonga v3.1.0 documentation</a> &raquo;</li>
+        <li><a href="../../index.html">Groonga v3.1.1 documentation</a> &raquo;</li>
           <li><a href="../../contribution.html" >13. How to contribute to groonga</a> &raquo;</li>
-          <li><a href="../development.html" accesskey="U">13.2. groonga開発者向け情報</a> &raquo;</li> 
+          <li><a href="../development.html" accesskey="U">13.3. groonga開発者向け情報</a> &raquo;</li> 
       </ul>
     </div>  
 
@@ -72,9 +72,9 @@
           <div class="body">
             
   <div class="section" id="groonga">
-<h1>13.2.2. groonga 通信アーキテクチャ<a class="headerlink" href="#groonga" title="Permalink to this headline">¶</a></h1>
+<h1>13.3.2. Groonga 通信アーキテクチャ<a class="headerlink" href="#groonga" title="Permalink to this headline">¶</a></h1>
 <div class="section" id="gqtp">
-<h2>13.2.2.1. gqtpでのアーキテクチャ<a class="headerlink" href="#gqtp" title="Permalink to this headline">¶</a></h2>
+<h2>13.3.2.1. GQTPでのアーキテクチャ<a class="headerlink" href="#gqtp" title="Permalink to this headline">¶</a></h2>
 <ul class="simple">
 <li>comが外部からの接続を受け付ける。</li>
 <li>comは1スレッド。</li>
@@ -99,18 +99,18 @@ edgeがworkerに結びついていないときは、同時に、ctx_newという
         <div class="sphinxsidebarwrapper">
   <h3><a href="../../index.html">Table Of Contents</a></h3>
   <ul>
-<li><a class="reference internal" href="#">13.2.2. groonga 通信アーキテクチャ</a><ul>
-<li><a class="reference internal" href="#gqtp">13.2.2.1. gqtpでのアーキテクチャ</a></li>
+<li><a class="reference internal" href="#">13.3.2. Groonga 通信アーキテクチャ</a><ul>
+<li><a class="reference internal" href="#gqtp">13.3.2.1. GQTPでのアーキテクチャ</a></li>
 </ul>
 </li>
 </ul>
 
   <h4>Previous topic</h4>
   <p class="topless"><a href="repository.html"
-                        title="previous chapter">13.2.1. Repository</a></p>
+                        title="previous chapter">13.3.1. Repository</a></p>
   <h4>Next topic</h4>
   <p class="topless"><a href="cooperation.html"
-                        title="next chapter">13.2.3. ユーザーと協力して開発をうまく進めていくための指針</a></p>
+                        title="next chapter">13.3.3. ユーザーと協力して開発をうまく進めていくための指針</a></p>
   <h3>This Page</h3>
   <ul class="this-page-menu">
     <li><a href="../../_sources/contribution/development/com.txt"
@@ -140,14 +140,14 @@ edgeがworkerに結びついていないときは、同時に、ctx_newという
           <a href="../../genindex.html" title="General Index"
              >index</a></li>
         <li class="right" >
-          <a href="cooperation.html" title="13.2.3. ユーザーと協力して開発をうまく進めていくための指針"
+          <a href="cooperation.html" title="13.3.3. ユーザーと協力して開発をうまく進めていくための指針"
              >next</a> |</li>
         <li class="right" >
-          <a href="repository.html" title="13.2.1. Repository"
+          <a href="repository.html" title="13.3.1. Repository"
              >previous</a> |</li>
-        <li><a href="../../index.html">Groonga v3.1.0 documentation</a> &raquo;</li>
+        <li><a href="../../index.html">Groonga v3.1.1 documentation</a> &raquo;</li>
           <li><a href="../../contribution.html" >13. How to contribute to groonga</a> &raquo;</li>
-          <li><a href="../development.html" >13.2. groonga開発者向け情報</a> &raquo;</li> 
+          <li><a href="../development.html" >13.3. groonga開発者向け情報</a> &raquo;</li> 
       </ul>
     </div>
     <div class="footer">