rroonga 1.3.0-x86-mingw32 → 1.3.1-x86-mingw32

data/vendor/local/share/doc/groonga/source/characteristic.txt

@@ -2,58 +2,68 @@
 
 .. highlightlang:: none
 
-The characteristics of groonga
-==============================
+Characteristics of groonga
+==========================
 
-The successor to the Senna that is an embeddable full text search engine
-------------------------------------------------------------------------
+Groonga overview
+----------------
 
-Groonga is developed as the successor project to Senna. Senna is an embeddable full text search engine and it is used widely. Groonga takes over from Senna's characteristics that are fast, high precision and high flexibility. We started to develop groonga to improve those Senna' characteristics.
+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.
 
-Groonga server supports multi-protocols such as HTTP
-----------------------------------------------------
+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.
 
-Senna is an component for an application that supports full text search. Groonga can be a server that provides search service. The groonga server supports HTTP, memcached binary protocol and gqtp (groonga query transfer protocol). Clients can search by those protocols via TCP/IP connection. It makes easy to use on a rental server that can install a library.
+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 `usage examples <http://groonga.org/users/>`_.
 
-Groonga also can be used as a C library like Senna.
+Full text search and Instant update
+-----------------------------------
 
-Fast data update
-----------------
+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.
+
+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.
+
+Column store and aggregate query
+--------------------------------
+
+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.
+
+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.
 
-Senna that is predecessor of groonga is a full text search engine without storage. Senna was commonly used with MySQL or PostgreSQL. Tritonn is a custom MyISAM storage engine that uses Senna as full text search engine. Ludia is a extension module for a PostgreSQL to use Senna as full text search engine. But those approaches can't fully utilize the performance characteristics of Senna. Senna can update index without read lock.
+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.
 
-For example, MyISAM acquires table lock while updating records in many cases. In those cases, data update by MyISAM is a bottleneck however Senna updates an index full text search fast.
+Inverted index and tokenizer
+----------------------------
 
-Groonga implements a storage that doesn't acquires read lock to realize search service that has immediacy.
+An inverted index is a traditional data structure used for large-scale full text search. A search engine based on inverted index extracts index terms from a document when it is added. Then in retrieval, a query is divided into index terms to find documents containing those index terms. In this way, index terms play an important role in full text search and thus the way of extracting index terms is a key to a better search engine.
 
+A tokenizer is a module to extract index terms. A Japanese full text search engine commonly uses a word-based tokenizer (hereafter referred to as a word tokenizer) and/or a character-based n-gram tokenizer (hereafter referred to as an n-gram tokenizer). A word tokenizer-based search engine is superior in time, space and precision, which is the fraction of relevant documents in a search result. On the other hand, an n-gram tokenizer-based search engine is superior in recall, which is the fraction of retrieved documents in the perfect search result. The best choice depends on the application in practice.
 
-Storage that can be shared with multi-processes and multi-threads
------------------------------------------------------------------
+Groonga supports both word and n-gram tokenizers. The simplest built-in tokenizer uses spaces as word delimiters. Built-in n-gram tokenizers (n = 1, 2, 3) are also available by default. In addition, a yet another built-in word tokenizer is available if MeCab, a part-of-speech and morphological analyzer, is embedded. Note that a tokenizer is pluggable and you can develop your own tokenizer, such as a tokenizer based on another part-of-speech tagger or a named-entity recognizer.
 
-Groonga's storage file can be shared with multi-processes and multi-threads. It doesn't require explicit lock.
+Sharable storage and read lock-free
+-----------------------------------
 
-`Mroonga <http://mroonga.github.com/>`_ that is the successor to the Tritonn is implemented as a MySQL pruggable storage engine. Groonga's storage files that are opened by mroonga can also be shared with groonga server. For example, you can update your data via SQL and search your data via HTTP.
+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.
 
-Fast aggregate query processing such as drilldown
--------------------------------------------------
+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.
 
-Groonga's storage uses column oriented database model that stores data for each column. Column oriented database is suitable for fast aggregate query processing such as OLAP.
+Geo-location (latitude and longitude) search
+--------------------------------------------
 
-"Drilldown" is a processing that groups full text search result by each specified column values and counts number of records in each group. Groonga does the processing fast because groonga uses column oriented database.
+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.
 
-Improved Senna's inverted index implementation
-----------------------------------------------
+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.
 
-Groonga's inverted index is the improved Senna's inverted index. It is more faster and more versatile.
+Groonga library
+---------------
 
-Groonga can also process some complex queries fast by utilizing inverted index. Those queries are difficult to process with SQL and RDB. For example, tag search and drilldown can be processed fast by utilizing inverted index.
+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 `related projects <http://groonga.org/related-projects.html>`_ for details.
 
-Geolocation (latitude and longitude) search
--------------------------------------------
+Groonga server
+--------------
 
-Groonga supports geolocation search. Supported geodetic systems are Japan geodetic system and world geodetic system (WGS 84). Supported geolocation refinement region types are circle and rectangle. Groonga also supports distance between two coordinates.
+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.
 
-Auto query cache mechanism
---------------------------
+Groonga storage engine
+----------------------
 
-Groonga caches reference queries automatically.
+Groonga works not only as an independent column-oriented DBMS but also as storage engines of well-known DBMSs. For example, `mroonga <http://mroonga.github.com/>`_ 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 `related projects <http://groonga.org/related-projects.html>`_ for details.

data/vendor/local/share/doc/groonga/source/commands/delete.txt

@@ -14,7 +14,7 @@ delete - 一件のレコードの削除
 ----
 ::
 
- delete table [key [id]]
+ delete table [key [id [filter]]]
 
 説明
 ----
@@ -38,6 +38,10 @@ deleteは、使用しているデータベースのテーブルに1件のレコ
 
   レコードIDによってレコードを指定します。idパラメータを指定する場合は、keyパラメータを指定してはいけません。
 
+``filter``
+
+  script形式のgrn_expr文字列によってレコードを指定します。filterパラメータを指定する場合は、id及びkeyパラメータを指定してはいけません。
+
 返値
 ---
 

data/vendor/local/share/doc/groonga/source/commands/table_create.txt

@@ -37,10 +37,13 @@ table_createコマンドは、使用しているデータベースに対して
   作成するテーブルの属性を示す数値か、パイプ('|')で組み合わせたシンボル名を指定します。(デフォルト値は0(="TABLE_HASH_KEY"))
 
    0, ``TABLE_HASH_KEY``
-     主キー値をハッシュ表で管理するテーブルを作成します。ハッシュ表を使用したテーブルでは、主キー値に完全一致するレコードを高速に検索することができます。
+     主キー値をハッシュ表で管理するテーブルを作成します。ハッシュ表を使用したテーブルでは、主キー値に完全一致するレコードを非常に高速に検索することができます。
 
    1, ``TABLE_PAT_KEY``
-     主キー値をパトリシア木で管理するテーブルを作成します。パトリシア木を使用したテーブルでは、主キー値に完全一致するレコード、前方一致するレコード、および最長共通接頭辞となるレコードを高速に検索することができます。また、キー値の昇降順でレコードを取り出したり、キー値の範囲での検索を行うことができます。また、flagsの値に64を加えることによって、後方一致検索も可能となります。
+     主キー値をパトリシア木で管理するテーブルを作成します。パトリシア木を使用したテーブルでは、主キー値に完全一致するレコードを検索することができるとともに、前方一致するレコード、および最長共通接頭辞となるレコードを高速に検索することができます。また、キー値の昇降順でレコードを取り出したり、キー値の範囲での検索を行うことができます。また、flagsの値に64を加えることによって、後方一致検索も可能となります。
+
+   2, ``TABLE_DAT_KEY``
+     主キー値をダブル配列で管理するテーブルを作成します。ダブル配列を使用したテーブルでは、主キー値に完全一致するレコードを高速に検索することができるとともに、前方一致するレコード、および最長共通接頭辞となるレコードを検索することができます。また、キー値の昇降順でレコードを取り出したり、キー値の範囲での検索を行うことができます。
 
    3, ``TABLE_NO_KEY``
      主キーを持たないテーブルを作成します。各レコードはIDのみによって特定することができます。

data/vendor/local/share/doc/groonga/source/community.txt

@@ -13,7 +13,8 @@ Mailing List
 
 There are mailing lists for discussion about groonga.
 
-For Japanese developers
-  `groonga-dev@lists.sourceforge.jp`_
+For English speaker
+  `groonga-talk@lists.sourceforge.net <http://lists.sourceforge.net/mailman/listinfo/groonga-talk>`_
 
-.. _groonga-dev@lists.sourceforge.jp: http://lists.sourceforge.jp/mailman/listinfo/groonga-dev
+For Japanese speaker
+  `groonga-dev@lists.sourceforge.jp <http://lists.sourceforge.jp/mailman/listinfo/groonga-dev>`_

data/vendor/local/share/doc/groonga/source/contribution.txt

@@ -5,16 +5,18 @@
 How to contribute to groonga
 ============================
 
-We are welcome to you contribute the groonga project. There
-are many ways to contribute such as use, introduction, bug
-report, development and documentation.
+We welcome your contributions to the groonga project. There are many ways
+to contribute, such as using groonga, introduction to others, etc.
+For example, if you find a bug when using groonga, you are welcome to
+report the bug. Coding and documentation are also welcome for groonga and
+its related projects.
 
 Use:
-  Please read this document.
+  If you are interested in groonga, please read this document and try it.
 Introduction:
-  Please talk your friends about groonga.
+  Please introduce groonga to your friends and colleagues.
 Bug report, development and documentation:
-  We describe about them in this section.
+  This section describes the details.
 
 .. toctree::
    :maxdepth: 3

data/vendor/local/share/doc/groonga/source/example/tutorial/data-1.log

@@ -1,18 +1,18 @@
-実行例 ::
+Execution example::
 
   > table_create --name Type --flags TABLE_HASH_KEY --key_type ShortText
-  [[0,1308820985.62521,0.057448585],true]
+  [[0,1322616293.7274,0.012551106],true]
   > column_create --table Type --name number --type Int32
-  [[0,1308820985.88435,0.0506424],true]
+  [[0,1322616293.94115,0.008619605],true]
   > column_create --table Type --name float --type Float
-  [[0,1308820986.13667,0.06274076],true]
+  [[0,1322616294.15095,0.004959989],true]
   > column_create --table Type --name string --type ShortText
+  [[0,1322616294.35693,0.005551818],true]
   > column_create --table Type --name time --type Time
-  [[0,1308820986.40111,0.207566663],true]
-  [[0,1308820986.60872,0.060231324],true]
+  [[0,1322616294.56333,0.006356953],true]
   > load --table Type
   > [{"_key":"sample","number":12345,"float":42.195,"string":"GROONGA","time":1234567890.12}]
-  [[0,1308820986.87067,0.202168318],1]
+  [[0,1322616294.77086,0.202357708],1]
   > select --table Type
-  [[0,1308820987.27451,0.000171948],[[[1],[["_id","UInt32"],["_key","ShortText"],["time","Time"],["string","ShortText"],["number","Int32"],["float","Float"]],[1,"sample",1234567890.12,"GROONGA",12345,42.195]]]]
+  [[0,1322616295.1744,0.000340057],[[[1],[["_id","UInt32"],["_key","ShortText"],["float","Float"],["number","Int32"],["string","ShortText"],["time","Time"]],[1,"sample",42.195,12345,"GROONGA",1234567890.12]]]]
   

data/vendor/local/share/doc/groonga/source/example/tutorial/data-2.log

@@ -1,10 +1,10 @@
-実行例 ::
+Execution example::
 
   > column_create --table Site --name link --type Site
-  [[0,1308820987.47796,0.067493639],true]
+  [[0,1322616295.37864,0.005674045],true]
   > load --table Site
   > [{"_key":"http://example.org/","link":"http://example.net/"}]
-  [[0,1308820987.74711,0.201407365],1]
+  [[0,1322616295.5854,0.200879317],1]
   > select --table Site --output_columns _key,title,link._key,link.title --query title:@this
-  [[0,1308820988.15016,0.000502207],[[[1],[["_key","ShortText"],["title","ShortText"],["link._key","ShortText"],["link.title","ShortText"]],["http://example.org/","This is test record 1!","http://example.net/","test record 2."]]]]
+  [[0,1322616295.98732,0.000872177],[[[1],[["_key","ShortText"],["title","ShortText"],["link._key","ShortText"],["link.title","ShortText"]],["http://example.org/","This is test record 1!","http://example.net/","test record 2."]]]]
   

data/vendor/local/share/doc/groonga/source/example/tutorial/data-3.log

@@ -1,10 +1,10 @@
-実行例 ::
+Execution example::
 
   > column_create --table Site --name links --flags COLUMN_VECTOR --type Site
-  [[0,1308820988.35428,0.055857261],true]
+  [[0,1322616296.19238,0.007598942],true]
   > load --table Site
   > [{"_key":"http://example.org/","links":["http://example.net/","http://example.org/","http://example.com/"]}]
-  [[0,1308820988.61189,0.20152687],1]
+  [[0,1322616296.40092,0.201036234],1]
   > select --table Site --output_columns _key,title,links._key,links.title --query title:@this
-  [[0,1308820989.01506,0.000477611],[[[1],[["_key","ShortText"],["title","ShortText"],["links._key","ShortText"],["links.title","ShortText"]],["http://example.org/","This is test record 1!",["http://example.net/","http://example.org/","http://example.com/"],["test record 2.","This is test record 1!","test test record three."]]]]]
+  [[0,1322616296.80305,0.000899975],[[[1],[["_key","ShortText"],["title","ShortText"],["links._key","ShortText"],["links.title","ShortText"]],["http://example.org/","This is test record 1!",["http://example.net/","http://example.org/","http://example.com/"],["test record 2.","This is test record 1!","test test record three."]]]]]
   

data/vendor/local/share/doc/groonga/source/example/tutorial/introduction-1.log

@@ -1,18 +1,6 @@
 Execution example::
 
-  > table_create --name Type --flags TABLE_HASH_KEY --key_type ShortText
-  [[0,1317212791.02322,0.03942904],true]
-  > column_create --table Type --name number --type Int32
-  [[0,1317212791.26314,0.124383285],true]
-  > column_create --table Type --name float --type Float
-  [[0,1317212791.58803,0.027924039],true]
-  > column_create --table Type --name string --type ShortText
-  [[0,1317212791.81654,0.040399047],true]
-  > column_create --table Type --name time --type Time
-  [[0,1317212792.05751,0.027354067],true]
-  > load --table Type
-  > [{"_key":"sample","number":12345,"float":42.195,"string":"GROONGA","time":1234567890.12}]
-  [[0,1317212792.28516,0.200775839],1]
-  > select --table Type
-  [[0,1317212792.68655,0.000199477],[[[1],[["_id","UInt32"],["_key","ShortText"],["time","Time"],["string","ShortText"],["number","Int32"],["float","Float"]],[1,"sample",1234567890.12,"GROONGA",12345,42.195]]]]
+  % groonga -n /tmp/groonga-databases/introduction.db
+  > status
+  [[0,1322616280.40348,0.000158121],{"alloc_count":127,"starttime":1322616279,"uptime":1,"version":"1.2.8-9-gbf05b82","n_queries":0,"cache_hit_rate":0.0,"command_version":1,"default_command_version":1,"max_command_version":2}]
   

data/vendor/local/share/doc/groonga/source/example/tutorial/introduction-2.log

@@ -1,10 +1,5 @@
 Execution example::
 
-  > column_create --table Site --name link --type Site
-  [[0,1317212792.88872,0.060705006],true]
-  > load --table Site
-  > [{"_key":"http://example.org/","link":"http://example.net/"}]
-  [[0,1317212793.14984,0.200481934],1]
-  > select --table Site --output_columns _key,title,link._key,link.title --query title:@this
-  [[0,1317212793.55084,0.000485897],[[[1],[["_key","ShortText"],["title","ShortText"],["link._key","ShortText"],["link.title","ShortText"]],["http://example.org/","This is test record 1!","http://example.net/","test record 2."]]]]
+  > table_create --name Site --flags TABLE_HASH_KEY --key_type ShortText
+  [[0,1322616280.60791,0.01234375],true]
   

data/vendor/local/share/doc/groonga/source/example/tutorial/introduction-3.log

@@ -1,10 +1,5 @@
 Execution example::
 
-  > column_create --table Site --name links --flags COLUMN_VECTOR --type Site
-  [[0,1317212793.75262,0.049658904],true]
-  > load --table Site
-  > [{"_key":"http://example.org/","links":["http://example.net/","http://example.org/","http://example.com/"]}]
-  [[0,1317212794.00274,0.200473621],1]
-  > select --table Site --output_columns _key,title,links._key,links.title --query title:@this
-  [[0,1317212794.40349,0.000384272],[[[1],[["_key","ShortText"],["title","ShortText"],["links._key","ShortText"],["links.title","ShortText"]],["http://example.org/","This is test record 1!",["http://example.net/","http://example.org/","http://example.com/"],["test record 2.","This is test record 1!","test test record three."]]]]]
+  > select --table Site
+  [[0,1322616280.82196,0.000451873],[[[0],[["_id","UInt32"],["_key","ShortText"]]]]]
   

data/vendor/local/share/doc/groonga/source/functions/geo_distance.txt

@@ -14,7 +14,7 @@ geo_distance - 指定した2点の距離を計算する
 ----
 ::
 
- geo_distance(point1, point2)
+ geo_distance(point1, point2[, approximate_type])
 
 説明
 ----
@@ -22,7 +22,10 @@ geo_distance - 指定した2点の距離を計算する
 groonga組込関数の一つであるgeo_distanceについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
 
 geo_distance() 関数は、point1に指定した座標とpoint2に指定した座標の間の距離(近似値)を求めます。
-geo_distance()の他に、距離計算アルゴリズムの異なる、geo_distance2()、geo_distance3()が使用できます。それぞれ、長方形近似、球面近似、ヒュベニの距離計算式によって距離を算出します。
+
+... note::
+
+    geo_distance()の他に、距離計算アルゴリズムの異なる、geo_distance2()、geo_distance3()がありましたが、1.2.9から非推奨になりました。 ``geo_distance2()`` の代わりに ``geo_distance(point1, point2, "sphere")`` を、 ``geo_distance3()`` の代わりに ``geo_distance(point1, point2, "ellipsoid")`` を使ってください。
 
 引数
 ----
@@ -35,6 +38,30 @@ geo_distance()の他に、距離計算アルゴリズムの異なる、geo_dista
 
   距離を求める2点のうちもう一つを指定します。GeoPoint型の値、あるいは座標を示す文字列を指定できます。
 
+``approximate_type``
+
+  距離を求めるために地形をどのように近似するかを指定します。指定できる値は以下の通りです。
+
+  ``"rectangle"``
+
+    方形近似で近似します。単純な計算式で距離を求めることができるため高速ですが、極付近では誤差が大きくなります。
+
+    ``"rect"`` と省略して指定することもできます。
+
+    この近似方法がデフォルト値です。 ``approximate_type`` を省略した場合は方形近似になります。
+
+  ``"sphere"``
+
+    球面近似で近似します。 ``"rectangle"`` よりも遅くなりますが、誤差は小さいです。
+
+    ``"sphr"`` と省略して指定することもできます。
+
+  ``"ellipsoid"``
+
+    楕円体近似で近似します。距離の計算にはヒュベニの距離計算式を用います。 ``"sphere"`` よりも遅くなりますが、誤差は小さくなります。
+
+    ``"ellip"`` と省略して指定することもできます。
+
 
 返値
 ----
@@ -46,7 +73,19 @@ geo_distance()の他に、距離計算アルゴリズムの異なる、geo_dista
 ::
 
  geo_distance(pos, "150x150")
- 100
+ 100.0
+
+ # 方形近似を利用
+ geo_distance(pos, "150x150", "rectangle")
+ 100.0
+
+ # 球面近似を利用
+ geo_distance(pos, "150x150", "sphere")
+ 100.0
+
+ # 楕円体近似を利用
+ geo_distance(pos, "150x150", "ellipsoid")
+ 100.0
 
 .. rubric:: 脚注
 

data/vendor/local/share/doc/groonga/source/functions/geo_in_circle.txt

@@ -14,7 +14,7 @@ geo_in_circle - 座標が円の範囲内に存在するかどうかを調べま
 ----
 ::
 
- geo_in_circle(point, center, radious_or_point)
+ geo_in_circle(point, center, radious_or_point[, approximate_type])
 
 説明
 ----
@@ -39,6 +39,31 @@ geo_in_circle() 関数は、pointに指定した座標が、centerに指定し
   円の半径を指定します。数値を指定した場合には、半径(単位:メートル)が指定されたものとみなします。
   Point型の値、あるいは座標を示す文字列を指定した場合は、円周上の点の一つの座標が指定されたものとみなします。
 
+``approximate_type``
+
+  半径からの距離を求めるために地形をどのように近似するかを指定します。指定できる値は以下の通りです。
+
+  ``"rectangle"``
+
+    方形近似で近似します。単純な計算式で距離を求めることができるため高速ですが、極付近では誤差が大きくなります。
+
+    ``"rect"`` と省略して指定することもできます。
+
+    この近似方法がデフォルト値です。 ``approximate_type`` を省略した場合は方形近似になります。
+
+  ``"sphere"``
+
+    球面近似で近似します。 ``"rectangle"`` よりも遅くなりますが、誤差は小さいです。
+
+    ``"sphr"`` と省略して指定することもできます。
+
+  ``"ellipsoid"``
+
+    楕円体近似で近似します。距離の計算にはヒュベニの距離計算式を用います。 ``"sphere"`` よりも遅くなりますが、誤差は小さくなります。
+
+    ``"ellip"`` と省略して指定することもできます。
+
+
 返値
 ----
 

data/vendor/local/share/doc/groonga/source/index.txt

@@ -5,8 +5,8 @@
    You can adapt this file completely to your liking, but it should at least
    contain the root `toctree` directive.
 
-groonga ドキュメント
-====================
+groonga documentation
+=====================
 
 * :doc:`news`