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

data/vendor/local/share/man/man1/groonga.1

@@ -1,4 +1,4 @@
-.TH "GROONGA" "1" "November 27, 2011" "1.2.7" "groonga"
+.TH "GROONGA" "1" "January 29, 2012" "1.2.9" "groonga"
 .SH NAME
 groonga \- groonga documentation
 .
@@ -34,48 +34,57 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .IP \(bu 2
 \fBnews\fP
 .UNINDENT
-.SH THE CHARACTERISTICS OF GROONGA
-.SS The successor to the Senna that is an embeddable full text search engine
+.SH CHARACTERISTICS OF GROONGA
+.SS Groonga overview
 .sp
-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\(aqs characteristics that are fast, high precision and high flexibility. We started to develop groonga to improve those Senna\(aq characteristics.
-.SS Groonga server supports multi\-protocols such as HTTP
+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.
 .sp
-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.
+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.
 .sp
-Groonga also can be used as a C library like Senna.
-.SS Fast data update
+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 \fI\%usage examples\fP.
+.SS Full text search and Instant update
 .sp
-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\(aqt fully utilize the performance characteristics of Senna. Senna can update index without read lock.
+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.
 .sp
-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.
+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.
+.SS Column store and aggregate query
 .sp
-Groonga implements a storage that doesn\(aqt acquires read lock to realize search service that has immediacy.
-.SS Storage that can be shared with multi\-processes and multi\-threads
+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.
 .sp
-Groonga\(aqs storage file can be shared with multi\-processes and multi\-threads. It doesn\(aqt require explicit lock.
+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.
 .sp
-\fI\%Mroonga\fP that is the successor to the Tritonn is implemented as a MySQL pruggable storage engine. Groonga\(aqs 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.
-.SS Fast aggregate query processing such as drilldown
+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.
+.SS Inverted index and tokenizer
 .sp
-Groonga\(aqs 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.
+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.
 .sp
-"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.
-.SS Improved Senna\(aqs inverted index implementation
+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.
 .sp
-Groonga\(aqs inverted index is the improved Senna\(aqs inverted index. It is more faster and more versatile.
+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.
+.SS Sharable storage and read lock\-free
 .sp
-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.
-.SS Geolocation (latitude and longitude) search
+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.
 .sp
-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.
-.SS Auto query cache mechanism
+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.
+.SS Geo\-location (latitude and longitude) search
 .sp
-Groonga caches reference queries automatically.
+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.
+.sp
+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.
+.SS Groonga library
+.sp
+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 \fI\%related projects\fP for details.
+.SS Groonga server
+.sp
+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.
+.SS Groonga storage engine
+.sp
+Groonga works not only as an independent column\-oriented DBMS but also as storage engines of well\-known DBMSs. For example, \fI\%mroonga\fP 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 \fI\%related projects\fP for details.
 .SH INSTALL
 .sp
-We will explain of how to install Groonga for each environments.
+This section describes how to install groonga on each environment.
 .sp
-We distribute packages for both 32\-bit and 64\-bit but we recommend that you should use 64\-bit package for server. You should use 32\-bit package just only for test or development. You will get no memory error with 32\-bit package even if you just process medium size data.
+We distribute both 32\-bit and 64\-bit packages but we strongly recommend a 64\-bit package for server. You should use a 32\-bit package just only for tests or development. You will encounter an out of memory error with a 32\-bit package even if you just process medium size data.
 .SS Debian GNU/Linux squeeze
 .sp
 /etc/apt/sources.list.d/groonga.list:
@@ -96,6 +105,16 @@ Install:
 % sudo aptitude \-V \-D \-y install groonga
 .ft P
 .fi
+.sp
+There is a package that provides \fI\%Munin\fP plugins. If you want to monitor groonga status by Munin, please install groonga\-munin\-plugins package.
+.sp
+Install groonga\-munin\-plugins package:
+.sp
+.nf
+.ft C
+% sudo aptitude \-V \-D \-y install groonga\-munin\-plugins
+.ft P
+.fi
 .SS Debian GNU/Linux wheezy
 .sp
 /etc/apt/sources.list.d/groonga.list:
@@ -116,6 +135,14 @@ Install:
 % sudo aptitude \-V \-D \-y install groonga
 .ft P
 .fi
+.sp
+Install groonga\-munin\-plugins package:
+.sp
+.nf
+.ft C
+% sudo aptitude \-V \-D \-y install groonga\-munin\-plugins
+.ft P
+.fi
 .SS Debian GNU/Linux sid
 .sp
 /etc/apt/sources.list.d/groonga.list:
@@ -136,10 +163,18 @@ Install:
 % sudo aptitude \-V \-D \-y install groonga
 .ft P
 .fi
+.sp
+Install groonga\-munin\-plugins package:
+.sp
+.nf
+.ft C
+% sudo aptitude \-V \-D \-y install groonga\-munin\-plugins
+.ft P
+.fi
 .SS Ubuntu 10.04 LTS Lucid Lynx
 .IP Note
-You should add universe section in the official Ubuntu
-repository. The following describes how to add it.
+You\(aqll need to enable the universe repository of Ubuntu to install groonga.
+The following describes how to do it.
 .RE
 .sp
 /etc/apt/sources.list.d/groonga.list:
@@ -156,14 +191,22 @@ Install:
 .nf
 .ft C
 % sudo apt\-key adv \-\-recv\-keys \-\-keyserver keyserver.ubuntu.com 1C837F31
-% sudo aptitude update
-% sudo aptitude \-V \-D \-y install groonga
+% sudo apt\-get update
+% sudo apt\-get \-y install groonga
+.ft P
+.fi
+.sp
+Install groonga\-munin\-plugins package:
+.sp
+.nf
+.ft C
+% sudo apt\-get \-y install groonga\-munin\-plugins
 .ft P
 .fi
 .SS Ubuntu 11.04 Natty Narwhal
 .IP Note
-You should add universe section in the official Ubuntu
-repository. The following describes how to add it.
+You\(aqll need to enable the universe repository of Ubuntu to install groonga.
+The following describes how to do it.
 .RE
 .sp
 /etc/apt/sources.list.d/groonga.list:
@@ -180,14 +223,22 @@ Install:
 .nf
 .ft C
 % sudo apt\-key adv \-\-recv\-keys \-\-keyserver keyserver.ubuntu.com 1C837F31
-% sudo aptitude update
-% sudo aptitude \-V \-D \-y install groonga
+% sudo apt\-get update
+% sudo apt\-get \-y install groonga
+.ft P
+.fi
+.sp
+Install groonga\-munin\-plugins package:
+.sp
+.nf
+.ft C
+% sudo apt\-get \-y install groonga\-munin\-plugins
 .ft P
 .fi
 .SS Ubuntu 11.10 Oneiric Ocelot
 .IP Note
-You should add universe section in the official Ubuntu
-repository. The following describes how to add it.
+You\(aqll need to enable the universe repository of Ubuntu to install groonga.
+The following describes how to do it.
 .RE
 .sp
 /etc/apt/sources.list.d/groonga.list:
@@ -204,8 +255,16 @@ Install:
 .nf
 .ft C
 % sudo apt\-key adv \-\-recv\-keys \-\-keyserver keyserver.ubuntu.com 1C837F31
-% sudo aptitude update
-% sudo aptitude \-V \-D \-y install groonga
+% sudo apt\-get update
+% sudo apt\-get \-y install groonga
+.ft P
+.fi
+.sp
+Install groonga\-munin\-plugins package:
+.sp
+.nf
+.ft C
+% sudo apt\-get \-y install groonga\-munin\-plugins
 .ft P
 .fi
 .SS CentOS 5
@@ -219,6 +278,44 @@ Install:
 % sudo yum install \-y groonga
 .ft P
 .fi
+.sp
+There is a package that provides \fI\%Munin\fP plugins. If you want to monitor groonga status by Munin, please install groonga\-munin\-plugins package.
+.IP Note
+Groonga\-munin\-plugins package requires munin\-node package that isn\(aqt included in the official CentOS repository. You need to enable \fI\%RPMforge\fP repository or \fI\%EPEL\fP repository to install it by yum.
+.sp
+Enable RPMforge repository on i386 environment:
+.sp
+.nf
+.ft C
+% sudo rpm \-ivh http://pkgs.repoforge.org/rpmforge\-release/rpmforge\-release\-0.5.2\-2.el5.rf.i386.rpm
+.ft P
+.fi
+.sp
+Enable RPMforge repository on x86_64 environment:
+.sp
+.nf
+.ft C
+% sudo rpm \-ivh http://pkgs.repoforge.org/rpmforge\-release/rpmforge\-release\-0.5.2\-2.el5.rf.x86_64.rpm
+.ft P
+.fi
+.sp
+Enable EPEL repository on any environment:
+.sp
+.nf
+.ft C
+% sudo rpm \-ivh http://download.fedoraproject.org/pub/epel/5/i386/epel\-release\-5\-4.noarch.rpm
+.ft P
+.fi
+.RE
+.sp
+Install groonga\-munin\-plugins package:
+.sp
+.nf
+.ft C
+% sudo yum update
+% sudo yum install \-y groonga\-munin\-plugins
+.ft P
+.fi
 .SS CentOS 6
 .sp
 Install:
@@ -230,7 +327,45 @@ Install:
 % sudo yum install \-y groonga
 .ft P
 .fi
-.SS Fedora 15
+.sp
+There is a package that provides \fI\%Munin\fP plugins. If you want to monitor groonga status by Munin, please install groonga\-munin\-plugins package.
+.IP Note
+Groonga\-munin\-plugins package requires munin\-node package that isn\(aqt included in the official CentOS repository. You need to enable \fI\%RPMforge\fP repository or \fI\%EPEL\fP repository to install it by yum.
+.sp
+Enable RPMforge repository on i686 environment:
+.sp
+.nf
+.ft C
+% sudo rpm \-ivh http://pkgs.repoforge.org/rpmforge\-release/rpmforge\-release\-0.5.2\-2.el6.rf.i686.rpm
+.ft P
+.fi
+.sp
+Enable RPMforge repository on x86_64 environment:
+.sp
+.nf
+.ft C
+% sudo rpm \-ivh http://pkgs.repoforge.org/rpmforge\-release/rpmforge\-release\-0.5.2\-2.el6.rf.x86_64.rpm
+.ft P
+.fi
+.sp
+Enable EPEL repository on any environment:
+.sp
+.nf
+.ft C
+% sudo rpm \-ivh http://download.fedoraproject.org/pub/epel/6/i386/epel\-release\-6\-5.noarch.rpm
+.ft P
+.fi
+.RE
+.sp
+Install groonga\-munin\-plugins package:
+.sp
+.nf
+.ft C
+% sudo yum update
+% sudo yum install \-y groonga\-munin\-plugins
+.ft P
+.fi
+.SS Fedora 16
 .sp
 Install:
 .sp
@@ -241,6 +376,16 @@ Install:
 % sudo yum install \-y groonga
 .ft P
 .fi
+.sp
+There is a package that provides \fI\%Munin\fP plugins. If you want to monitor groonga status by Munin, please install groonga\-munin\-plugins package.
+.sp
+Install groonga\-munin\-plugins package:
+.sp
+.nf
+.ft C
+% sudo yum install \-y groonga\-munin\-plugins
+.ft P
+.fi
 .SS Mac OS X (MacPorts)
 .sp
 Install:
@@ -261,24 +406,21 @@ Install:
 .fi
 .SS Windows (Installer)
 .sp
-You just download installer (.exe file) from
+You just download an installer (.exe file) from
 \fI\%packages.groonga.org/windows/\fP
 and execute it.
 .SS Windows (zip)
 .sp
-You just download zip\-file from
+You just download a zip file from
 \fI\%packages.groonga.org/windows/\fP
 and extract it.
 .SS Others
 .sp
-If you will use indexes of tokenizing of each morpheme for
-full\-text search, you should install \fI\%MeCab\fP
-before you install groonga.
+If you want to use a morphological analyzer for tokenization in full\-text indexing, please install \fI\%MeCab\fP before installing groonga.
 .sp
-After, you should download tar.gz\-file from
-\fI\%packages.groonga.org/source/\fP
-for installing groonga. You should extract this file in
-place to install, and run commands below\-mentioned.
+Then, download a tar.gz file from \fI\%packages.groonga.org/source/\fP and extract it. After that, please run the following command to install groonga.
+.sp
+Install:
 .sp
 .nf
 .ft C
@@ -286,9 +428,9 @@ place to install, and run commands below\-mentioned.
 .ft P
 .fi
 .sp
-The "prefix" option is the paramater for specified place to install.
-If you won\(aqt specify the option, "/usr/local" is specified.
-Please specify "/usr" for this option if you don\(aqt know environment variables(LD_LIBRARY_PATH and so on) well.
+The "prefix" option specifies the path to install groonga. If you don\(aqt specify the install path, "/usr/local" is used. Please specify "/usr" if you are not familiar with environment variables such as LD_LIBRARY_PATH.
+.sp
+There are some \fI\%Munin\fP plugins in groonga package. You need to pass \fI\-\-with\-munin\-plugins\fP option to install them.
 .SH COMMUNITY
 .sp
 There are some places for sharing groonga information.
@@ -298,20 +440,21 @@ We welcome you to join our community.
 There are mailing lists for discussion about groonga.
 .INDENT 0.0
 .TP
-.B For Japanese developers
+.B For English speaker
+\fI\%groonga-talk@lists.sourceforge.net\fP
+.TP
+.B For Japanese speaker
 \fI\%groonga-dev@lists.sourceforge.jp\fP
 .UNINDENT
-.SH チュートリアル
-.SS Fundamental operation
+.SH TUTORIAL
+.SS Basic operations
 .sp
-You can use groonga as a library of programming language C or an executable file.
-This tutorial explains how to use groonga as an executable file.
-Using its file, you can create and operate databases, start and connect to server, and so on.
-.SS Create database
+The groonga package provides a C library (libgroonga) and a command line tool (groonga). This tutorial explains how to use the groonga command, with which you can create/operate databases, start a server, establish a connection with a server, etc.
+.SS Create a database
 .sp
-You can create a new database in the following command.
+You can create a new database with the following command.
 .sp
-Form
+Form:
 .sp
 .nf
 .ft C
@@ -319,22 +462,22 @@ groonga \-n DB_PATH_NAME
 .ft P
 .fi
 .sp
-\(aq\-n\(aq option specifies to create a database. DB_PATH_NAME specifies full\-path of new database.
+The \(aq\-n\(aq option specifies to create a new database. DB_PATH_NAME specifies the path of the new database. Note that this command fails if the specified path already exists.
 .sp
-Groonga starts as interactive mode after you create a database with this command, and so groonga accepts commands from standard input. This mode is terminated with Ctrl\-d.
+This command creates a database and then enters into interactive mode in which groonga prompts you to enter commands for operating that database. You can terminate this mode with Ctrl\-d.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
 % groonga \-n /tmp/tutorial.db
-> ctrl\-d
+> Ctrl\-d
 %
 .ft P
 .fi
-.SS Operate database
+.SS Operate a database
 .sp
-Form
+Form:
 .sp
 .nf
 .ft C
@@ -342,139 +485,109 @@ groonga DB_PATH_NAME [COMMAND]
 .ft P
 .fi
 .sp
-DB_PATH_NAME specifies full\-path of existing database.
-If COMMAND is specified, result of COMMAND is returned.
+DB_PATH_NAME specifies the path of a target database.
 .sp
-With no COMMAND, this command starts groonga as interactive\-mode.
-Groonga of this mode reads a command from standard input evaluates it repeatedly.
-This tutorial uses interactive\-mode mainly.
+If COMMAND is specified, groonga executes COMMAND and returns the result. Otherwise, groonga starts in interactive mode that reads commands from the standard input and execute them one by one. This tutorial focuses on the interactive mode.
 .sp
-For example, we will run the \fIstatus\fP command.
-This command returns status of groonga\(aqs execution.
+Let\(aqs try to see the status of a groonga process by using a \fB/commands/status\fP command.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-> 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}]
 .ft P
 .fi
 .sp
-The mentioned above, results of executed commands are generally JSON style.
-The first element in a array of JSON has information of error\-code, execution time, and so on.
-The second element has a result of exectuted command.
-.SS Commands
+As shown in the above example, a command basically returns a JSON array. The first element contains an error code, execution time, etc. The second element is the result of an operation.
+.SS Command format
 .sp
-You can operate database with various commands via execution file of groonga or groonga server.
-There are forms of commands in the following:
+Commands for operating a database accept arguments as follows:
 .sp
 .nf
 .ft C
-Form1: COMMAND ARGUMENT1 ARGUMENT2 ..
+Form_1: COMMAND VALUE_1 VALUE_2 ..
 
-Form2: COMMAND \-\-ARAGUMENT1 VALUE1 \-\-ARGUMENT2 VALUE2 ..
+Form_2: COMMAND \-\-NAME_1 VALUE_1 \-\-NAME_2 VALUE_2 ..
 .ft P
 .fi
 .sp
-You can mix these forms in commands running.
+In the first form, arguments must be passed in order. This kind of arguments are called positional arguments because the position of each argument determines its meaning.
+.sp
+In the second form, you can specify a parameter name with its value. So, the order of arguments is not defined. This kind of arguments are known as named parameters or keyword arguments.
 .sp
-In Form2, if you want to specify a value including some spaces or symbols("\(aq()/), you should enclose its value with single\-quote or double\-quote.
+If you want to specify a value which contains white\-spaces or special characters, such as quotes and parentheses, please enclose the value with single\-quotes or double\-quotes.
 .sp
-For detail, you can see paragraph of "command" in \fB/executables/groonga\fP.
-.SS Basicaly commands
+For details, see also the paragraph of "command" in \fB/executables/groonga\fP.
+.SS Basic commands
 .INDENT 0.0
 .INDENT 3.5
 .INDENT 0.0
 .TP
 .B \fB/commands/status\fP
-Show status of groonga process.
+shows status of a groonga process.
 .TP
 .B \fB/commands/table_list\fP
-Show lists of tables defined in a database.
+shows a list of tables in a database.
 .TP
 .B \fB/commands/column_list\fP
-Show lists of columns defined in a table.
+shows a list of columns in a table.
 .TP
 .B \fB/commands/table_create\fP
-Add table to a database.
+adds a table to a database.
 .TP
 .B \fB/commands/column_create\fP
-Add column to a table.
+adds a column to a table.
 .TP
 .B \fB/commands/select\fP
-Search and show records included a table.
+searches records from a table and shows the result.
 .TP
 .B \fB/commands/load\fP
-Insert record to a table.
+inserts records to a table.
 .UNINDENT
 .UNINDENT
 .UNINDENT
-.SS Create table
+.SS Create a table
 .sp
-\fB/commands/table_create\fP creates table.
+A \fB/commands/table_create\fP command creates a table.
 .sp
-In using groonga, to creating tables generally needed master key.
-Master key should be specified the types and the way to store.
+In most cases, a table of groonga has a primary key which must be specified with its data type and index type.
 .sp
-We\(aqre going to explain the types in tutorial after.
-Please imagine it as expressing sort of data.
-How to store master key defines speed of search with master key and advisability of begins\-with\-match search. This is also explained in this tutorial later.
+There are various data types such as integers, floating\-point numbers, etc. The index type determines the search performance and the availability of prefix searches. We will explain the details later.
 .sp
-For example, we create \(aqSite\(aq table. This table has master key of ShortText type, and the way to store its key is HASH.
+Let\(aqs create a \(aqSite\(aq table which has a primary key of ShortText. In this example, the index type is HASH.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-> 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]
 .ft P
 .fi
-.SS Search
+.SS View a table
 .sp
-\fB/commands/select\fP shows contents of table.
+A \fB/commands/select\fP command shows contents of table.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-> 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"]]]]]
 .ft P
 .fi
 .sp
-With name of a table, \(aqselect\(aq command shows 10 contents of its table. [0] shows the number of searched records. ["_id","Uint32"] is column named "_id" and type of this column\(aqs value is UInt32. ["_key","ShortText"] is "_key" column, type of this column\(aqs value is ShortText.
+When only a table is specified, the \(aqselect\(aq command returns the first (at most) 10 records of that table. "[0]" in the result shows the number of records in the \(aqSite\(aq table. The next array is a list of columns. ["_id","Uint32"] is a column of UInt32, named "_id". ["_key","ShortText"] is a column of ShortText, named "_key".
 .sp
-\(aqtable_create\(aq command creates table including two columns, \(aq_id\(aq and \(aq_key\(aq first. \(aq_id\(aq has ID\-number given automatically by groonga. \(aq_key\(aq column is stored master key. You cannot modify this column\(aqs name.
-.SS Create columns
+The above two columns, \(aq_id\(aq and \(aq_key\(aq, are the necessary columns. The \(aq_id\(aq column stores IDs those are automatically allocated by groonga. The \(aq_key\(aq column is associated with the primary key. You are not allowed to rename these columns.
+.SS Create a column
 .sp
-\fB/commands/column_create\fP command create columns.
+A \fB/commands/column_create\fP command adds a column to a table.
 .sp
-We add a column named \(aqcomment\(aq that lets us store value whose type is ShortText.
+Let\(aqs add a column of ShortText to store titles. You may give a descriptive name \(aqtitle\(aq to the column.
 .sp
 Execution example:
 .sp
@@ -487,14 +600,14 @@ Execution example:
 .ft P
 .fi
 .sp
-COLUMN_SCALAR means this is normal column.
-.SS Create terminology table with fulltext\-searching
+The COLUMN_SCALAR flag specifies to add a regular column.
+.SS Create a lexicon table for full text searches
 .sp
-This tutorial explains fulltext searching with entried data in groonga table.
+Let\(aqs go on to how to make a full text search.
 .sp
-We need terminology table in fulltext\-searching.
-Terminology table is a table whose master key\(aqs values are words in text.
-We create \(aqTerms\(aq table, it has type of master key value is ShortText.
+Groonga uses an inverted index to provide fast full text search. So, the first step is to create a lexicon table which stores an inverted index, also known as postings lists. The primary key of this table is associated with a vocabulary made up of index terms and each record stores postings lists for one index term.
+.sp
+The following shows a command which creates a lexicon table named \(aqTerms\(aq. The data type of its primary key is ShortText.
 .sp
 Execution example:
 .sp
@@ -505,15 +618,14 @@ Execution example:
 .ft P
 .fi
 .sp
-Many parameters is specified in this execution example.
-You don\(aqt hove to understand all parameters.
-There are the simple explaination, but you can skipped.
+The table_create command takes many parameters but you don\(aqt need to understand all of them. Please skip the next paragraph if you are not interested in how it works.
+.sp
+The \(aqTABLE_PAT_KEY\(aq flag specifies to store index terms in a patricia trie. The \(aqKEY_NORMALIZE\(aq flag specifies to normalize index terms. In this example, both flags are validated by using a \(aq|\(aq. The \(aqdefault_tokenizer\(aq parameter specifies a method for tokenizing text. This example specifies \(aqTokenBigram\(aq that is generally called \(aqN\-gram\(aq.
+.SS Create an index column for full text search
 .sp
-In this examples, \(aqTABLE_PAT_KEY|KEY_NORMALIZE\(aq stores master key in patricia\-trie and entries each teminology after nomalized.
-The \(aqdefault_tokenizer\(aq parametar specifies the way to tokenize target texts. In this examples, we specifies \(aqTokenBigram\(aq as this parameter, and so we choose \(aqN\-gram\(aq generally called.
-.SS Create index\-column with fulltext search
+The second step is to create an index column, which allows you to search records from its associated column. That is to say this step specifies which column needs an index.
 .sp
-We will fulltext search \(aqtitle\(aq column in \(aqSite\(aq table. In this case, we create column whose type index in terminology table.
+Let\(aqs create an index column for the \(aqtitle\(aq column in the \(aqSite\(aq table.
 .sp
 Execution example:
 .sp
@@ -524,11 +636,12 @@ Execution example:
 .ft P
 .fi
 .sp
-This command creates index column \(aqblog_title\(aq in \(aqTerm\(aq table. \(aq\-\-type\(aq option specifies target indexed table, and \(aq\-\-source\(aq option does target index column.
-In execution example, \(aqCOLUMN_INDEX|WITH_POSITION\(aq for \(aq\-\-flags\(aq option specifies that this column is index column for storing information of terminology existing position. This option should be specified \(aqCOLUMN_INDEX|WITH_POSITION\(aq in generally fulltext searching. This tutorial does not deal with the reason why store information of terminology existing position.
+This command creates an index column \(aqblog_title\(aq in the \(aqTerms\(aq table. The \(aq\-\-type\(aq option specifies a target table and the \(aq\-\-source\(aq option specifies a target column. Then, the \(aqCOLUMN_INDEX\(aq flag specifies to create an index column and the \(aqWITH_POSITION\(aq flag specifies to create a full inverted index, which contains the positions of each index term. This combination \(aqCOLUMN_INDEX|WITH_POSITION\(aq is recommended for the general purpose.
 .SS Load data
 .sp
-\fB/commands/load\fP is used to load data for groonga database. This command stores json\-formatted data in a table.
+A \fB/commands/load\fP command loads JSON\-formatted records into a table.
+.sp
+The following adds nine records to the \(aqSite\(aq table.
 .sp
 Execution example:
 .sp
@@ -550,7 +663,7 @@ Execution example:
 .ft P
 .fi
 .sp
-Let\(aqs make sure that its table has data with \(aqselect\(aq command.
+Let\(aqs make sure that these records are correctly stored.
 .sp
 Execution example:
 .sp
@@ -562,9 +675,9 @@ Execution example:
 .fi
 .SS Search data
 .sp
-\(aq_id\(aq and \(aq_key\(aq columns are unique in groonga\(aqs table, so let\(aqs search data in table using these columns.
+Before a full text search, let\(aqs try to search data by \(aq_id\(aq and \(aq_key\(aq. These columns work as unique keys.
 .sp
-You can search data using \(aqselect\(aq command with \(aqquery\(aq parameter.
+You can search records by using a \(aqselect\(aq command with a \(aqquery\(aq parameter.
 .sp
 Execution example:
 .sp
@@ -575,9 +688,9 @@ Execution example:
 .ft P
 .fi
 .sp
-\(aq_id:1\(aq specified \(aqquery\(aq parameter means to search records whose \(aq_id\(aq column has \(aq1\(aq.
+\(aq_id:1\(aq specifies to search a record whose ID is 1.
 .sp
-Let\(aqs search records with \(aq_key\(aq column.
+Next, let\(aqs search a record by a primary key.
 .sp
 Execution example:
 .sp
@@ -588,10 +701,10 @@ Execution example:
 .ft P
 .fi
 .sp
-\(aq_key:"\fI\%http://example.org/\fP"\(aq specified \(aqquery\(aq parameter means to search records whose \(aq_key\(aq column has \(aq"\fI\%http://example.org/\fP"\(aq.
-.SS Fulltext searching
+\(aq_key:"\fI\%http://example.org/\fP"\(aq specifies to search a record whose primary key is "\fI\%http://example.org/\fP".
+.SS Full text search
 .sp
-Using \(aqquery\(aq parameter, you can fulltext search with index.
+It\(aqs time to make a full text search. You can make a full text search query with the same \(aqquery\(aq parameter.
 .sp
 Execution example:
 .sp
@@ -602,15 +715,11 @@ Execution example:
 .ft P
 .fi
 .sp
-This command shows result of fulltext searching by string \(aqthis\(aq for \(aqtitle\(aq column.
-.sp
-"title:@this" specified \(aqquery\(aq parameter means to search records whose \(aqtitle\(aq column including \(aqthis\(aq string.
+This command searches records whose \(aqtitle\(aq column contains a string \(aqthis\(aq. In this case, only one record matches this query. Note that the lower case query \(aqthis\(aq matches a capitalized \(aqThis\(aq in the 1st record because \(aqKEY_NORMALIZE\(aq was specified in lexicon column creation.
 .sp
-\(aqselect\(aq command has parameter \(aqmatch_columns\(aq.
+The \(aqselect\(aq command has an optional parameter \(aqmatch_columns\(aq. This parameter specifies default target columns and it is used when target columns are not specified in a query.[1]_
 .sp
-If this parameter is specified, it means to search in columns specified \(aqmatch_columns\(aq when \(aqquery\(aq parameter doesn\(aqt specify column\-name condition.[1]_
-.sp
-If you specify \(aqmatch_columns\(aq is \(aqtitle\(aq and \(aqquery\(aq is \(aqthis\(aq, you can take same result as above query.
+A combination of \(aq\-\-match_columns title\(aq and \(aq\-\-query this\(aq brings you the same result that \(aq\-\-query title:@this\(aq does.
 .sp
 Execution example:
 .sp
@@ -620,11 +729,9 @@ Execution example:
 [[0,1317212717.30596,0.000716439],[[[1],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[1,"http://example.org/","This is test record 1!"]]]]
 .ft P
 .fi
-.SS Specify output column
-.sp
-\(aqoutput_columns\(aq parameter in \(aqselect\(aq command specifies columns shown in result of search.
+.SS Specify output columns
 .sp
-If you want to specify some columns, you should separate column names by comma(,).
+An \(aqoutput_columns\(aq parameter in a \(aqselect\(aq command specifies columns to be shown in the search result. If you want to specify more than one columns, please separate column names by commas (,).
 .sp
 Execution example:
 .sp
@@ -635,14 +742,12 @@ Execution example:
 .ft P
 .fi
 .sp
-"_score" column is added to The groonga\(aqs result. This column has the higher number, the more condition of fulltext seaching matches text.
-.SS Ranges to display
-.sp
-\(aqselect\(aq command can display result in only specified ranges using \(aqoffset\(aq and \(aqlimit\(aq parameter. This parameters is useful when you want to show only a page in much result of searching.
+This command specifies three output columns including the \(aq_score\(aq column, which stores the relevance score of each record.
+.SS Specify output ranges
 .sp
-\(aqoffset\(aq parameter specifies starting point of result. If you want \(aqselect\(aq command to return from first records, this parameter specifies \(aq0\(aq.
+A \(aqselect\(aq command returns a part of its search result if \(aqoffset\(aq and/or \(aqlimit\(aq parameters are specified. These parameters are useful to paginate a search result, a widely\-used interface which shows a search result on a page by page basis.
 .sp
-\(aqlimit\(aq parameter specifies how many records of searching result.
+An \(aqoffset\(aq parameter specifies the starting point and a \(aqlimit\(aq parameter specifies the maximum number of records to be returned. If you need the first record in a search result, the offset parameter must be 0 or omitted.
 .sp
 Execution example:
 .sp
@@ -658,9 +763,9 @@ Execution example:
 .fi
 .SS Sort
 .sp
-If you use \(aqsortby\(aq parameter in \(aqselect\(aq command, this command sorts result of searching.
+A \(aqselect\(aq command sorts its result when used with a \(aqsortby\(aq parameter.
 .sp
-When \(aqsortby\(aq parameter specifies column name, result is sorted in ascending\-order to its column\(aqs value. This \(aqselect\(aq command also sort in descending\-order when you add hyphen(\-) before column name.
+A \(aqsortby\(aq parameter specifies a column as a sorting creteria. A search result is arranged in ascending order of the column values. If you want to sort a search result in reverse order, please add a leading hyphen (\-) to the column name of a parameter.
 .sp
 Execution example:
 .sp
@@ -671,7 +776,7 @@ Execution example:
 .ft P
 .fi
 .sp
-For condition of sort, you can use \(aq_score\(aq column introduced in the paragraph of "Specify output column".
+You can use the \(aq_score\(aq column as a sorting criteria for ranking a search result.
 .sp
 Execution example:
 .sp
@@ -682,7 +787,7 @@ Execution example:
 .ft P
 .fi
 .sp
-If you want to specify some column names, you should use comma(,) between these names. In this case, when same value of records is existed in first column, this command sorts result of searching to value of second column.
+If you want to specify more than one columns, please separate column names by commas. In such a case, a search result is sorted in order of the column values in the first column, and then records having the same values in the first column are sorted in order of the second column values.
 .sp
 Execution example:
 .sp
@@ -694,7 +799,7 @@ Execution example:
 .fi
 footnote
 .IP [1] 5
-In now groonga\(aqs version, you can only use \(aqmatch_columns\(aq parameter in the case of existing index of fulltext searching. This parameter cannot be use in searching for ordinary columns.
+Currently, a \(aqmatch_columns\(aq parameter is available iff there exists an inverted index for full text search. A \(aqmatch_columns\(aq parameter for a regular column is not supported.
 .SS How to use groonga with network
 .sp
 You can use groonga with network. When you run groonga by using the groonga original protocol or HTTP, groonga accepts connection for network.
@@ -821,20 +926,20 @@ Execution example:
 .nf
 .ft C
 > table_create \-\-name Type \-\-flags TABLE_HASH_KEY \-\-key_type ShortText
-[[0,1317212791.02322,0.03942904],true]
+[[0,1322616293.7274,0.012551106],true]
 > column_create \-\-table Type \-\-name number \-\-type Int32
-[[0,1317212791.26314,0.124383285],true]
+[[0,1322616293.94115,0.008619605],true]
 > column_create \-\-table Type \-\-name float \-\-type Float
-[[0,1317212791.58803,0.027924039],true]
+[[0,1322616294.15095,0.004959989],true]
 > column_create \-\-table Type \-\-name string \-\-type ShortText
-[[0,1317212791.81654,0.040399047],true]
+[[0,1322616294.35693,0.005551818],true]
 > column_create \-\-table Type \-\-name time \-\-type Time
-[[0,1317212792.05751,0.027354067],true]
+[[0,1322616294.56333,0.006356953],true]
 > load \-\-table Type
 > [{"_key":"sample","number":12345,"float":42.195,"string":"GROONGA","time":1234567890.12}]
-[[0,1317212792.28516,0.200775839],1]
+[[0,1322616294.77086,0.202357708],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]]]]
+[[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]]]]
 .ft P
 .fi
 .SS テーブル型
@@ -852,12 +957,12 @@ Execution example:
 .nf
 .ft C
 > column_create \-\-table Site \-\-name link \-\-type Site
-[[0,1317212792.88872,0.060705006],true]
+[[0,1322616295.37864,0.005674045],true]
 > load \-\-table Site
 > [{"_key":"http://example.org/","link":"http://example.net/"}]
-[[0,1317212793.14984,0.200481934],1]
+[[0,1322616295.5854,0.200879317],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."]]]]
+[[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."]]]]
 .ft P
 .fi
 .sp
@@ -877,12 +982,12 @@ Execution example:
 .nf
 .ft C
 > column_create \-\-table Site \-\-name links \-\-flags COLUMN_VECTOR \-\-type Site
-[[0,1317212793.75262,0.049658904],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,1317212794.00274,0.200473621],1]
+[[0,1322616296.40092,0.201036234],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."]]]]]
+[[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."]]]]]
 .ft P
 .fi
 .sp
@@ -1841,6 +1946,8 @@ groongaでは、 \fB/commands/select\fP コマンドにquery_expansionパラメ
 .sp
 クエリ拡張機能を使用するためには、検索対象となる文書を格納するテーブル(ここでは文書テーブルと呼びます)以外に、ユーザの指定した検索文字列を置換するためのテーブル(ここでは置換テーブルと呼びます)を準備します。置換テーブルでは、その主キーが置換前の文字列となり、文字列型(ShortText)のカラムの値が置換後の文字列となります。
 .sp
+TODO: 文字列型のベクターカラムでも可能であり、その場合は各要素をORでつなげたものに置換されるということを記述する。
+.sp
 実際に文書テーブルと置換テーブルを作成してみましょう。
 .sp
 Execution example:
@@ -1905,10 +2012,6 @@ Execution example:
 .sp
 どちらのクエリ文字列も、"(シークァーサー OR シークヮーサー)"という文字列に置換されてから検索されるため、表記の揺れを吸収して検索できるようになりました。
 .SH SUGGEST
-.IP Note
-The suggest feature specification isn\(aqt stable. The
-specification may be changed.
-.RE
 .sp
 Groonga has the suggest feature. This section describes how to use it and how it works.
 .SS Introduction
@@ -3463,6 +3566,214 @@ TODO
 \fB/suggest\fP
 .. : doc:\fIgroonga\-suggest\-httpd\fP
 .. : doc:\fIgroonga\-suggest\-learner\fP
+.SS Output
+.sp
+Groonga supports the following output format types:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fI\%JSON\fP
+.IP \(bu 2
+\fI\%XML\fP
+.IP \(bu 2
+TSV (Tab Separated Values)
+.IP \(bu 2
+\fI\%MessagePack\fP
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+JSON is the default output format.
+.SS Usage
+.sp
+Groonga has the following query interfaces:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+command line
+.IP \(bu 2
+HTTP
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+They provides different ways to change output format type.
+.SS Command line
+.sp
+You can use command line query interface by \fBgroonga
+DB_PATH\fP or \fBgroonga \-c\fP. Those groonga commands shows
+\fB> \(ga\(ga prompt. In this query interface, you can specify
+output format type by \(ga\(gaoutput_type\fP option.
+.sp
+If you don\(aqt specify \fBoutput_type\fP option, you will get
+a result in JSON format:
+.sp
+.nf
+.ft C
+> status
+[[0,1327721628.10738,0.000131845474243164],{"alloc_count":142,"starttime":1327721626,"uptime":2,"version":"1.2.9\-92\-gb87d9f8","n_queries":0,"cache_hit_rate":0.0,"command_version":1,"default_command_version":1,"max_command_version":2}]
+.ft P
+.fi
+.sp
+You can specify \fBjson\fP as \fBoutput_type\fP value to get a
+result in JSON format explicitly:
+.sp
+.nf
+.ft C
+> status \-\-output_type json
+[[0,1327721639.08321,7.93933868408203e\-05],{"alloc_count":144,"starttime":1327721626,"uptime":13,"version":"1.2.9\-92\-gb87d9f8","n_queries":0,"cache_hit_rate":0.0,"command_version":1,"default_command_version":1,"max_command_version":2}]
+.ft P
+.fi
+.sp
+You need to specify \fBxml\fP as \fBoutput_type\fP value to
+get a result in XML format:
+.sp
+.nf
+.ft C
+> status \-\-output_type xml
+<?xml version="1.0" encoding="utf\-8"?>
+<RESULT CODE="0" UP="1327721649.61095" ELAPSED="0.000126361846923828">
+<RESULT>
+<TEXT>alloc_count</TEXT>
+<INT>146</INT>
+<TEXT>starttime</TEXT>
+<INT>1327721626</INT>
+<TEXT>uptime</TEXT>
+<INT>23</INT>
+<TEXT>version</TEXT>
+<TEXT>1.2.9\-92\-gb87d9f8</TEXT>
+<TEXT>n_queries</TEXT>
+<INT>0</INT>
+<TEXT>cache_hit_rate</TEXT>
+<FLOAT>0.0</FLOAT>
+<TEXT>command_version</TEXT>
+<INT>1</INT>
+<TEXT>default_command_version</TEXT>
+<INT>1</INT>
+<TEXT>max_command_version</TEXT>
+<INT>2</INT></RESULT>
+</RESULT>
+.ft P
+.fi
+.sp
+You need to specify \fBtsv\fP as \fBoutput_type\fP value to
+get a result in TSV format:
+.sp
+.nf
+.ft C
+> status \-\-output_type tsv
+0     1327721664.82675        0.000113964080810547
+"alloc_count" 146
+"starttime"   1327721626
+"uptime"      38
+"version"     "1.2.9\-92\-gb87d9f8"
+"n_queries"   0
+"cache_hit_rate"      0.0
+"command_version"     1
+"default_command_version"     1
+"max_command_version" 2
+END
+.ft P
+.fi
+.sp
+You need to specify \fBmsgpack\fP as \fBoutput_type\fP value to
+get a result in MessagePack format:
+.sp
+.nf
+.ft C
+> status \-\-output_type msgpack
+(... omitted because MessagePack is binary data format. ...)
+.ft P
+.fi
+.SS HTTP
+.sp
+You can use HTTP query interface by \fBgroonga \-\-protocol
+http \-s DB_PATH\fP. Groonga HTTP server starts on port 10041
+by default. In this query interface, you can specify
+output format type by extension.
+.sp
+If you don\(aqt specify extension, you will get a result in
+JSON format:
+.sp
+.nf
+.ft C
+% curl http://localhost:10041/d/status
+[[0,1327809294.54311,0.00082087516784668],{"alloc_count":155,"starttime":1327809282,"uptime":12,"version":"1.2.9\-92\-gb87d9f8","n_queries":0,"cache_hit_rate":0.0,"command_version":1,"default_command_version":1,"max_command_version":2}]
+.ft P
+.fi
+.sp
+You can specify \fBjson\fP as extension to get a result in
+JSON format explicitly:
+.sp
+.nf
+.ft C
+% curl http://localhost:10041/d/status.json
+[[0,1327809319.01929,9.5367431640625e\-05],{"alloc_count":157,"starttime":1327809282,"uptime":37,"version":"1.2.9\-92\-gb87d9f8","n_queries":0,"cache_hit_rate":0.0,"command_version":1,"default_command_version":1,"max_command_version":2}]
+.ft P
+.fi
+.sp
+You need to specify \fBxml\fP as extension to get a result in
+XML format:
+.sp
+.nf
+.ft C
+% curl http://localhost:10041/d/status.xml
+<?xml version="1.0" encoding="utf\-8"?>
+<RESULT CODE="0" UP="1327809339.5782" ELAPSED="9.56058502197266e\-05">
+<RESULT>
+<TEXT>alloc_count</TEXT>
+<INT>159</INT>
+<TEXT>starttime</TEXT>
+<INT>1327809282</INT>
+<TEXT>uptime</TEXT>
+<INT>57</INT>
+<TEXT>version</TEXT>
+<TEXT>1.2.9\-92\-gb87d9f8</TEXT>
+<TEXT>n_queries</TEXT>
+<INT>0</INT>
+<TEXT>cache_hit_rate</TEXT>
+<FLOAT>0.0</FLOAT>
+<TEXT>command_version</TEXT>
+<INT>1</INT>
+<TEXT>default_command_version</TEXT>
+<INT>1</INT>
+<TEXT>max_command_version</TEXT>
+<INT>2</INT></RESULT>
+</RESULT>
+.ft P
+.fi
+.sp
+You need to specify \fBtsv\fP as extension to get a result in
+TSV format:
+.sp
+.nf
+.ft C
+% curl http://localhost:10041/d/status.tsv
+0     1327809366.84187        8.44001770019531e\-05
+"alloc_count" 159
+"starttime"   1327809282
+"uptime"      84
+"version"     "1.2.9\-92\-gb87d9f8"
+"n_queries"   0
+"cache_hit_rate"      0.0
+"command_version"     1
+"default_command_version"     1
+"max_command_version" 2
+END
+.ft P
+.fi
+.sp
+You need to specify \fBmsgpack\fP as extension to get a result
+in MessagePack format:
+.sp
+.nf
+.ft C
+% curl http://localhost:10041/d/status.msgpack
+(... omitted because MessagePack is binary data format. ...)
+.ft P
+.fi
 .SS コマンド
 .sp
 まず、すべてのコマンドに関係するコマンドバージョンについて説明します。その後、組み込みのコマンドを順に説明します。
@@ -4316,7 +4627,7 @@ delete \- 一件のレコードの削除
 .sp
 .nf
 .ft C
-delete table [key [id]]
+delete table [key [id [filter]]]
 .ft P
 .fi
 .SS 説明
@@ -4347,6 +4658,13 @@ deleteは、使用しているデータベースのテーブルに1件のレコ
 .UNINDENT
 .UNINDENT
 .sp
+\fBfilter\fP
+.INDENT 0.0
+.INDENT 3.5
+script形式のgrn_expr文字列によってレコードを指定します。filterパラメータを指定する場合は、id及びkeyパラメータを指定してはいけません。
+.UNINDENT
+.UNINDENT
+.sp
 返値
 \-\-\-
 .SS json形式
@@ -5608,10 +5926,13 @@ table_createコマンドは、使用しているデータベースに対して
 .INDENT 0.0
 .TP
 .B 0, \fBTABLE_HASH_KEY\fP
-主キー値をハッシュ表で管理するテーブルを作成します。ハッシュ表を使用したテーブルでは、主キー値に完全一致するレコードを高速に検索することができます。
+主キー値をハッシュ表で管理するテーブルを作成します。ハッシュ表を使用したテーブルでは、主キー値に完全一致するレコードを非常に高速に検索することができます。
 .TP
 .B 1, \fBTABLE_PAT_KEY\fP
-主キー値をパトリシア木で管理するテーブルを作成します。パトリシア木を使用したテーブルでは、主キー値に完全一致するレコード、前方一致するレコード、および最長共通接頭辞となるレコードを高速に検索することができます。また、キー値の昇降順でレコードを取り出したり、キー値の範囲での検索を行うことができます。また、flagsの値に64を加えることによって、後方一致検索も可能となります。
+主キー値をパトリシア木で管理するテーブルを作成します。パトリシア木を使用したテーブルでは、主キー値に完全一致するレコードを検索することができるとともに、前方一致するレコード、および最長共通接頭辞となるレコードを高速に検索することができます。また、キー値の昇降順でレコードを取り出したり、キー値の範囲での検索を行うことができます。また、flagsの値に64を加えることによって、後方一致検索も可能となります。
+.TP
+.B 2, \fBTABLE_DAT_KEY\fP
+主キー値をダブル配列で管理するテーブルを作成します。ダブル配列を使用したテーブルでは、主キー値に完全一致するレコードを高速に検索することができるとともに、前方一致するレコード、および最長共通接頭辞となるレコードを検索することができます。また、キー値の昇降順でレコードを取り出したり、キー値の範囲での検索を行うことができます。
 .TP
 .B 3, \fBTABLE_NO_KEY\fP
 主キーを持たないテーブルを作成します。各レコードはIDのみによって特定することができます。
@@ -6062,11 +6383,11 @@ ieee754形式の64bit浮動小数点数。
 .SS テーブルの主キーに指定できない型
 .sp
 Text型とLongText型については、テーブルの主キーに指定することはできません。
-.SS ベクトルとして格納できない型
+.SS ベクターとして格納できない型
 .sp
-groongaのカラムは、ある型のベクトルを保存することができます。しかし、ShortText, Text, LongTextの３つの型についてはベクトルとして保存することはできません。
+groongaのカラムは、ある型のベクターを保存することができます。しかし、ShortText, Text, LongTextの３つの型についてはベクターとして保存したり出力したりすることはできますが、検索条件やドリルダウン条件に指定することができません。
 .sp
-テーブル型は、ベクトルとして格納することができます。よって、ShortTextのベクトルを保存したい場合には、主キーがShortText型のテーブルを別途作成し、そのテーブルを型として利用します。
+テーブル型は、ベクターとして格納することができます。よって、ShortTextのベクターを検索条件やドリルダウン条件に使用したい場合には、主キーがShortText型のテーブルを別途作成し、そのテーブルを型として利用します。
 脚注
 .IP [1] 5
 Object型はv1.2でサポートされます。
@@ -6202,7 +6523,7 @@ geo_distance \- 指定した2点の距離を計算する
 .sp
 .nf
 .ft C
-geo_distance(point1, point2)
+geo_distance(point1, point2[, approximate_type])
 .ft P
 .fi
 .SS 説明
@@ -6210,7 +6531,14 @@ geo_distance(point1, point2)
 groonga組込関数の一つであるgeo_distanceについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
 .sp
 geo_distance() 関数は、point1に指定した座標とpoint2に指定した座標の間の距離(近似値)を求めます。
-geo_distance()の他に、距離計算アルゴリズムの異なる、geo_distance2()、geo_distance3()が使用できます。それぞれ、長方形近似、球面近似、ヒュベニの距離計算式によって距離を算出します。
+.sp
+... note:
+.sp
+.nf
+.ft C
+geo_distance()の他に、距離計算アルゴリズムの異なる、geo_distance2()、geo_distance3()がありましたが、1.2.9から非推奨になりました。 \(ga\(gageo_distance2()\(ga\(ga の代わりに \(ga\(gageo_distance(point1, point2, "sphere")\(ga\(ga を、 \(ga\(gageo_distance3()\(ga\(ga の代わりに \(ga\(gageo_distance(point1, point2, "ellipsoid")\(ga\(ga を使ってください。
+.ft P
+.fi
 .SS 引数
 .sp
 \fBpoint1\fP
@@ -6226,6 +6554,42 @@ geo_distance()の他に、距離計算アルゴリズムの異なる、geo_dista
 距離を求める2点のうちもう一つを指定します。GeoPoint型の値、あるいは座標を示す文字列を指定できます。
 .UNINDENT
 .UNINDENT
+.sp
+\fBapproximate_type\fP
+.INDENT 0.0
+.INDENT 3.5
+距離を求めるために地形をどのように近似するかを指定します。指定できる値は以下の通りです。
+.sp
+\fB"rectangle"\fP
+.INDENT 0.0
+.INDENT 3.5
+方形近似で近似します。単純な計算式で距離を求めることができるため高速ですが、極付近では誤差が大きくなります。
+.sp
+\fB"rect"\fP と省略して指定することもできます。
+.sp
+この近似方法がデフォルト値です。 \fBapproximate_type\fP を省略した場合は方形近似になります。
+.UNINDENT
+.UNINDENT
+.sp
+\fB"sphere"\fP
+.INDENT 0.0
+.INDENT 3.5
+球面近似で近似します。 \fB"rectangle"\fP よりも遅くなりますが、誤差は小さいです。
+.sp
+\fB"sphr"\fP と省略して指定することもできます。
+.UNINDENT
+.UNINDENT
+.sp
+\fB"ellipsoid"\fP
+.INDENT 0.0
+.INDENT 3.5
+楕円体近似で近似します。距離の計算にはヒュベニの距離計算式を用います。 \fB"sphere"\fP よりも遅くなりますが、誤差は小さくなります。
+.sp
+\fB"ellip"\fP と省略して指定することもできます。
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
 .SS 返値
 .sp
 指定した2点の距離をFloat型の値(単位:メートル)として返します。
@@ -6234,7 +6598,19 @@ geo_distance()の他に、距離計算アルゴリズムの異なる、geo_dista
 .nf
 .ft C
 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
 .ft P
 .fi
 脚注
@@ -6248,7 +6624,7 @@ geo_in_circle \- 座標が円の範囲内に存在するかどうかを調べま
 .sp
 .nf
 .ft C
-geo_in_circle(point, center, radious_or_point)
+geo_in_circle(point, center, radious_or_point[, approximate_type])
 .ft P
 .fi
 .SS 説明
@@ -6279,6 +6655,42 @@ geo_in_circle() 関数は、pointに指定した座標が、centerに指定し
 Point型の値、あるいは座標を示す文字列を指定した場合は、円周上の点の一つの座標が指定されたものとみなします。
 .UNINDENT
 .UNINDENT
+.sp
+\fBapproximate_type\fP
+.INDENT 0.0
+.INDENT 3.5
+半径からの距離を求めるために地形をどのように近似するかを指定します。指定できる値は以下の通りです。
+.sp
+\fB"rectangle"\fP
+.INDENT 0.0
+.INDENT 3.5
+方形近似で近似します。単純な計算式で距離を求めることができるため高速ですが、極付近では誤差が大きくなります。
+.sp
+\fB"rect"\fP と省略して指定することもできます。
+.sp
+この近似方法がデフォルト値です。 \fBapproximate_type\fP を省略した場合は方形近似になります。
+.UNINDENT
+.UNINDENT
+.sp
+\fB"sphere"\fP
+.INDENT 0.0
+.INDENT 3.5
+球面近似で近似します。 \fB"rectangle"\fP よりも遅くなりますが、誤差は小さいです。
+.sp
+\fB"sphr"\fP と省略して指定することもできます。
+.UNINDENT
+.UNINDENT
+.sp
+\fB"ellipsoid"\fP
+.INDENT 0.0
+.INDENT 3.5
+楕円体近似で近似します。距離の計算にはヒュベニの距離計算式を用います。 \fB"sphere"\fP よりも遅くなりますが、誤差は小さくなります。
+.sp
+\fB"ellip"\fP と省略して指定することもできます。
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
 .SS 返値
 .sp
 pointに指定した座標が円の範囲内にあるかどうかをBool型の値で返します。
@@ -6824,22 +7236,22 @@ select Shops \-\-filter \(aq"point > 3 && description @ \e"スープカレー\e"
 .fi
 .sp
 そのため、descriptionに「スープカレーライス」が含まれていても、「スープカレーライス」は「スープカレー」に完全一致しないのでヒットしません。
-.SH 制限事項
+.SH LIMITATIONS
 .sp
-groongaにはいくつか制限事項があります。
-.SS インデックス上限値
+Groonga has some limitations.
+.SS Limitations of indexing
 .sp
-1つのインデックスにおける論理上の上限値は以下のとおりです。
+A full\-text index has the following limitations.
 .INDENT 0.0
 .IP \(bu 2
-最大レコード数: 268,435,455 (約2億6千万)
+The maximum number of records: 268,435,455 (more than 26 million)
 .IP \(bu 2
-最大語彙数: 268,435,455 (約2億6千万)
+The maximum number of distinct terms: 268,435,455 (more than 26 million)
 .IP \(bu 2
-最大インデックスサイズ: 256GByte
+The maximum index size: 256GBytes
 .UNINDENT
 .sp
-(実際には他の諸条件の制約により上記の値まで到達しない場合もあります)
+Keep in mind that these limitations may vary depending on conditions.
 .SH トラブルシューティング
 .SS 同じ検索キーワードなのに全文検索結果が異なる
 .sp
@@ -7030,19 +7442,21 @@ TokenBigramIgnoreBlankSplitSymbolAlphaDigit: 記号・アルファベット・
 この場合も対策方法1同様、検索ノイズが上位に現れる可能性が高くなることに注意してください。検索ノイズが多くなった場合は指定する値を低くする必要があります。
 .SH HOW TO CONTRIBUTE TO GROONGA
 .sp
-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.
 .INDENT 0.0
 .TP
 .B Use:
-Please read this document.
+If you are interested in groonga, please read this document and try it.
 .TP
 .B Introduction:
-Please talk your friends about groonga.
+Please introduce groonga to your friends and colleagues.
 .TP
 .B Bug report, development and documentation:
-We describe about them in this section.
+This section describes the details.
 .UNINDENT
 .SS How to report a bug
 .sp
@@ -7672,7 +8086,7 @@ as \(aqja\(aq.
 .SH AUTHOR
 groonga project
 .SH COPYRIGHT
-2009-2011, Brazil, Inc
+2009-2012, Brazil, Inc
 .\" Generated by docutils manpage writer.
 .\" 
 .