rroonga 2.1.3-x86-mingw32 → 3.0.0-x86-mingw32

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

@@ -1,4 +1,4 @@
-.TH "GROONGA" "1" "January 28, 2013" "2.1.2" "groonga"
+.TH "GROONGA" "1" "March 28, 2013" "3.0.2" "groonga"
 .SH NAME
 groonga \- groonga documentation
 .
@@ -112,7 +112,7 @@ Start command prompt \fBcmd.exe\fP and download x86 executable binary by default
 .sp
 .nf
 .ft C
-> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/windows/groonga/groonga\-2.1.2\-x86.exe
+> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/windows/groonga/groonga\-3.0.2\-x86.exe
 .ft P
 .fi
 .sp
@@ -124,7 +124,7 @@ Start command prompt \fBcmd.exe\fP and download x64 executable binary by default
 .sp
 .nf
 .ft C
-> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/windows/groonga/groonga\-2.1.2\-x64.exe
+> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/windows/groonga/groonga\-3.0.2\-x64.exe
 .ft P
 .fi
 .sp
@@ -141,7 +141,7 @@ Start command prompt \fBcmd.exe\fP and download x86 zip archive by default brows
 .sp
 .nf
 .ft C
-> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/windows/groonga/groonga\-2.1.2\-x86.zip
+> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/windows/groonga/groonga\-3.0.2\-x86.zip
 .ft P
 .fi
 .sp
@@ -153,7 +153,7 @@ Start command prompt \fBcmd.exe\fP and download x64 zip archive by default brows
 .sp
 .nf
 .ft C
-> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/windows/groonga/groonga\-2.1.2\-x64.zip
+> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/windows/groonga/groonga\-3.0.2\-x64.zip
 .ft P
 .fi
 .sp
@@ -185,7 +185,7 @@ Visual Studio 2010 Express and download it by default browser:
 .nf
 .ft C
 > cd c:\eUsers\e%USERNAME%\eDownloads
-> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/source/groonga/groonga\-2.1.2.zip
+> "c:\e\eProgram Files\e\eInternet Explorer\e\eiexplore.exe" http://packages.groonga.org/source/groonga/groonga\-3.0.2.zip
 .ft P
 .fi
 .sp
@@ -195,7 +195,7 @@ Move to the groonga\(aqs source folder:
 .sp
 .nf
 .ft C
-> cd c:\eUsers\e%USERNAME%\eDownloads\egroonga\-2.1.2
+> cd c:\eUsers\e%USERNAME%\eDownloads\egroonga\-3.0.2
 .ft P
 .fi
 .sp
@@ -205,7 +205,7 @@ parameter instead:
 .sp
 .nf
 .ft C
-groonga\-2.1.2> cmake . \-G "Visual Studio 10 Win64" \-DCMAKE_INSTALL_PREFIX=C:\egroonga
+groonga\-3.0.2> cmake . \-G "Visual Studio 10 Win64" \-DCMAKE_INSTALL_PREFIX=C:\egroonga
 .ft P
 .fi
 .sp
@@ -213,7 +213,7 @@ Build by Visual C++ 2010 Express:
 .sp
 .nf
 .ft C
-groonga\-2.1.2> msbuild groonga.sln /p:Configuration=Release
+groonga\-3.0.2> msbuild groonga.sln /p:Configuration=Release
 .ft P
 .fi
 .sp
@@ -221,7 +221,7 @@ Install by Visual C++ 2010 Express:
 .sp
 .nf
 .ft C
-groonga\-2.1.2> msbuild groonga.sln /p:Configuration=Release /t:Install
+groonga\-3.0.2> msbuild groonga.sln /p:Configuration=Release /t:Install
 .ft P
 .fi
 .sp
@@ -231,7 +231,7 @@ Build by Visual Studio 2010:
 .sp
 .nf
 .ft C
-groonga\-2.1.2> devenv groonga.sln /Build Release
+groonga\-3.0.2> devenv groonga.sln /Build Release
 .ft P
 .fi
 .sp
@@ -239,7 +239,7 @@ Install by Visual Studio 2010:
 .sp
 .nf
 .ft C
-groonga\-2.1.2> devenv groonga.sln /Build Release /Project Install
+groonga\-3.0.2> devenv groonga.sln /Build Release /Project Install
 .ft P
 .fi
 .sp
@@ -281,9 +281,9 @@ Download source:
 .sp
 .nf
 .ft C
-% curl \-O http://packages.groonga.org/source/groonga/groonga\-2.1.2.tar.gz
-% tar xvzf groonga\-2.1.2.tar.gz
-% cd groonga\-2.1.2
+% curl \-O http://packages.groonga.org/source/groonga/groonga\-3.0.2.tar.gz
+% tar xvzf groonga\-3.0.2.tar.gz
+% cd groonga\-3.0.2
 .ft P
 .fi
 .sp
@@ -307,7 +307,7 @@ Install:
 .sp
 .nf
 .ft C
-% sudo make intall
+% sudo make install
 .ft P
 .fi
 .SS Debian GNU/Linux
@@ -382,6 +382,18 @@ Install groonga\-munin\-plugins package:
 % sudo aptitude \-V \-D \-y install groonga\-munin\-plugins
 .ft P
 .fi
+.sp
+There is a package that provides MySQL compatible normalizer as
+groonga plugins.
+If you want to use that one, install groonga\-normalizer\-mysql package.
+.sp
+Install groonga\-normalizer\-mysql package:
+.sp
+.nf
+.ft C
+% sudo aptitude \-V \-D \-y install groonga\-normalizer\-mysql
+.ft P
+.fi
 .SS wheezy
 .sp
 Add the groonga apt repository.
@@ -427,6 +439,18 @@ Install groonga\-munin\-plugins package:
 % sudo aptitude \-V \-D \-y install groonga\-munin\-plugins
 .ft P
 .fi
+.sp
+There is a package that provides MySQL compatible normalizer as
+groonga plugins.
+If you want to use that one, install groonga\-normalizer\-mysql package.
+.sp
+Install groonga\-normalizer\-mysql package:
+.sp
+.nf
+.ft C
+% sudo aptitude \-V \-D \-y install groonga\-normalizer\-mysql
+.ft P
+.fi
 .SS sid
 .sp
 Add the groonga apt repository.
@@ -472,6 +496,18 @@ Install groonga\-munin\-plugins package:
 % sudo aptitude \-V \-D \-y install groonga\-munin\-plugins
 .ft P
 .fi
+.sp
+There is a package that provides MySQL compatible normalizer as
+groonga plugins.
+If you want to use that one, install groonga\-normalizer\-mysql package.
+.sp
+Install groonga\-normalizer\-mysql package:
+.sp
+.nf
+.ft C
+% sudo aptitude \-V \-D \-y install groonga\-normalizer\-mysql
+.ft P
+.fi
 .SS Build from source
 .sp
 Install required packages to build groonga:
@@ -486,9 +522,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-2.1.2.tar.gz
-% tar xvzf groonga\-2.1.2.tar.gz
-% cd groonga\-2.1.2
+% wget http://packages.groonga.org/source/groonga/groonga\-3.0.2.tar.gz
+% tar xvzf groonga\-3.0.2.tar.gz
+% cd groonga\-3.0.2
 .ft P
 .fi
 .sp
@@ -512,7 +548,7 @@ Install:
 .sp
 .nf
 .ft C
-% sudo make intall
+% sudo make install
 .ft P
 .fi
 .SS Ubuntu
@@ -597,6 +633,18 @@ Install groonga\-munin\-plugins package:
 % sudo apt\-get \-y install groonga\-munin\-plugins
 .ft P
 .fi
+.sp
+There is a package that provides MySQL compatible normalizer as
+groonga plugins.
+If you want to use that one, install groonga\-normalizer\-mysql package.
+.sp
+Install groonga\-normalizer\-mysql package:
+.sp
+.nf
+.ft C
+% sudo apt\-get \-y install groonga\-normalizer\-mysql
+.ft P
+.fi
 .SS 11.10 Oneiric Ocelot
 .IP Note
 Enable the universe repository to install groonga:
@@ -652,6 +700,18 @@ Install groonga\-munin\-plugins package:
 % sudo apt\-get \-y install groonga\-munin\-plugins
 .ft P
 .fi
+.sp
+There is a package that provides MySQL compatible normalizer as
+groonga plugins.
+If you want to use that one, install groonga\-normalizer\-mysql package.
+.sp
+Install groonga\-normalizer\-mysql package:
+.sp
+.nf
+.ft C
+% sudo apt\-get \-y install groonga\-normalizer\-mysql
+.ft P
+.fi
 .SS 12.04 LTS Precise Pangolin
 .IP Note
 Enable the universe repository to install groonga:
@@ -707,6 +767,18 @@ Install groonga\-munin\-plugins package:
 % sudo apt\-get \-y install groonga\-munin\-plugins
 .ft P
 .fi
+.sp
+There is a package that provides MySQL compatible normalizer as
+groonga plugins.
+If you want to use that one, install groonga\-normalizer\-mysql package.
+.sp
+Install groonga\-normalizer\-mysql package:
+.sp
+.nf
+.ft C
+% sudo apt\-get \-y install groonga\-normalizer\-mysql
+.ft P
+.fi
 .SS 12.10 Quantal Quetzal
 .IP Note
 Enable the universe repository to install groonga:
@@ -762,6 +834,18 @@ Install groonga\-munin\-plugins package:
 % sudo apt\-get \-y install groonga\-munin\-plugins
 .ft P
 .fi
+.sp
+There is a package that provides MySQL compatible normalizer as
+groonga plugins.
+If you want to use that one, install groonga\-normalizer\-mysql package.
+.sp
+Install groonga\-normalizer\-mysql package:
+.sp
+.nf
+.ft C
+% sudo apt\-get \-y install groonga\-normalizer\-mysql
+.ft P
+.fi
 .SS Build from source
 .sp
 Install required packages to build groonga:
@@ -776,9 +860,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-2.1.2.tar.gz
-% tar xvzf groonga\-2.1.2.tar.gz
-% cd groonga\-2.1.2
+% wget http://packages.groonga.org/source/groonga/groonga\-3.0.2.tar.gz
+% tar xvzf groonga\-3.0.2.tar.gz
+% cd groonga\-3.0.2
 .ft P
 .fi
 .sp
@@ -802,7 +886,7 @@ Install:
 .sp
 .nf
 .ft C
-% sudo make intall
+% sudo make install
 .ft P
 .fi
 .SS CentOS
@@ -917,6 +1001,18 @@ Install groonga\-munin\-plugins package:
 % sudo yum install \-y groonga\-munin\-plugins
 .ft P
 .fi
+.sp
+There is a package that provides MySQL compatible normalizer as
+groonga plugins.
+If you want to use that one, install groonga\-normalizer\-mysql package.
+.sp
+Install groonga\-normalizer\-mysql package:
+.sp
+.nf
+.ft C
+% sudo yum install \-y install groonga\-normalizer\-mysql
+.ft P
+.fi
 .SS CentOS 6
 .sp
 Install:
@@ -982,6 +1078,18 @@ Install groonga\-munin\-plugins package:
 % sudo yum install \-y groonga\-munin\-plugins
 .ft P
 .fi
+.sp
+There is a package that provides MySQL compatible normalizer as
+groonga plugins.
+If you want to use that one, install groonga\-normalizer\-mysql package.
+.sp
+Install groonga\-normalizer\-mysql package:
+.sp
+.nf
+.ft C
+% sudo yum install \-y install groonga\-normalizer\-mysql
+.ft P
+.fi
 .SS Build from source
 .sp
 Install required packages to build groonga:
@@ -996,9 +1104,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-2.1.2.tar.gz
-% tar xvzf groonga\-2.1.2.tar.gz
-% cd groonga\-2.1.2
+% wget http://packages.groonga.org/source/groonga/groonga\-3.0.2.tar.gz
+% tar xvzf groonga\-3.0.2.tar.gz
+% cd groonga\-3.0.2
 .ft P
 .fi
 .sp
@@ -1022,7 +1130,7 @@ Install:
 .sp
 .nf
 .ft C
-% sudo make intall
+% sudo make install
 .ft P
 .fi
 .SS Fedora
@@ -1111,6 +1219,18 @@ Install groonga\-munin\-plugins package:
 % sudo yum install \-y groonga\-munin\-plugins
 .ft P
 .fi
+.sp
+There is a package that provides MySQL compatible normalizer as
+groonga plugins.
+If you want to use that one, install groonga\-normalizer\-mysql package.
+.sp
+Install groonga\-normalizer\-mysql package:
+.sp
+.nf
+.ft C
+% sudo yum install \-y install groonga\-normalizer\-mysql
+.ft P
+.fi
 .SS Build from source
 .sp
 Install required packages to build groonga:
@@ -1125,9 +1245,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-2.1.2.tar.gz
-% tar xvzf groonga\-2.1.2.tar.gz
-% cd groonga\-2.1.2
+% wget http://packages.groonga.org/source/groonga/groonga\-3.0.2.tar.gz
+% tar xvzf groonga\-3.0.2.tar.gz
+% cd groonga\-3.0.2
 .ft P
 .fi
 .sp
@@ -1151,7 +1271,7 @@ Install:
 .sp
 .nf
 .ft C
-% sudo make intall
+% sudo make install
 .ft P
 .fi
 .SS Oracle Solaris
@@ -1172,9 +1292,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-2.1.2.tar.gz
-% gtar xvzf groonga\-2.1.2.tar.gz
-% cd groonga\-2.1.2
+% wget http://packages.groonga.org/source/groonga/groonga\-3.0.2.tar.gz
+% gtar xvzf groonga\-3.0.2.tar.gz
+% cd groonga\-3.0.2
 .ft P
 .fi
 .sp
@@ -1298,9 +1418,9 @@ steps:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-2.1.2.tar.gz
-% tar xvzf groonga\-2.1.2.tar.gz
-% cd groonga\-2.1.2
+% wget http://packages.groonga.org/source/groonga/groonga\-3.0.2.tar.gz
+% tar xvzf groonga\-3.0.2.tar.gz
+% cd groonga\-3.0.2
 % ./configure
 % make
 % sudo make install
@@ -6601,7 +6721,7 @@ load \-\-table Synonym
 この例では、ユーザが"シークァーサー"と入力しても、"シークヮーサー"と入力しても、それぞれの異なる表記の文書をもれなく検索するための置換テーブルを作成しています。
 .SS 検索
 .sp
-それでは実際に、準備した置換テーブルを使ってみましょう。まずは、query_expansionパラメータを指定せずにselectコマンドを使って検索してみます。
+それでは実際に、準備した置換テーブルを使ってみましょう。まずは、query_expanderパラメータを指定せずにselectコマンドを使って検索してみます。
 .sp
 Execution example:
 .sp
@@ -6678,13 +6798,13 @@ select Doc \-\-match_columns body \-\-query "シークヮーサー"
 .ft P
 .fi
 .sp
-指定された文字列に完全に一致するレコードのみがそれぞれヒットします。次に、query_expansionパラメータに、準備したSynonymテーブルのbodyカラムを指定してみましょう。
+指定された文字列に完全に一致するレコードのみがそれぞれヒットします。次に、query_expanderパラメータに、準備したSynonymテーブルのbodyカラムを指定してみましょう。
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-select Doc \-\-match_columns body \-\-query "シークァーサー" \-\-query_expansion Synonym.body
+select Doc \-\-match_columns body \-\-query "シークァーサー" \-\-query_expander Synonym.body
 # [
 #   [
 #     0,
@@ -6723,7 +6843,7 @@ select Doc \-\-match_columns body \-\-query "シークァーサー" \-\-query_ex
 #     ]
 #   ]
 # ]
-select Doc \-\-match_columns body \-\-query "シークヮーサー" \-\-query_expansion Synonym.body
+select Doc \-\-match_columns body \-\-query "シークヮーサー" \-\-query_expander Synonym.body
 # [
 #   [
 #     0,
@@ -8859,11 +8979,13 @@ groongaのデータベースは、groongaコマンドかCライブラリイン
 .TP
 .B \-a, \-\-address <ip/hostname>
 Deprecated since version 1.2.2: Use \fI\-\-bind\-address\fP instead.
+
 .UNINDENT
 .INDENT 0.0
 .TP
 .B \-\-bind\-address <ip/hostname>
 New in version 1.2.2.
+
 .sp
 サーバモードかデーモンモードで実行するとき、listenするアドレスを指定します。(デフォルトは \fIhostname\fP の返すホスト名)
 .UNINDENT
@@ -10148,12 +10270,15 @@ maxが指定されなかった場合には、クエリキャッシュの最大
 .nf
 .ft C
 [以前の設定値]
-
-\(ga\(ga以前の設定値\(ga\(ga
-
-  すでに設定されていたクエリキャッシュの最大件数を返す。
 .ft P
 .fi
+.sp
+\fB以前の設定値\fP
+.INDENT 0.0
+.INDENT 3.5
+すでに設定されていたクエリキャッシュの最大件数を返す。
+.UNINDENT
+.UNINDENT
 .SS 例
 .sp
 .nf
@@ -10198,90 +10323,156 @@ checkコマンドは、groongaプロセス内の指定したオブジェクト
 下記のような配列が出力されます。
 
   [インデックスの状態, バッファの状態1, バッファの状態2, ...]
-
-\(ga\(gaインデックスの状態\(ga\(gaには下記の項目がハッシュ形式で出力されます。
-
-\(ga\(gaflags\(ga\(ga
-
-  指定されているフラグ値です。16進数で表現されています。
-
-\(ga\(gamax sid\(ga\(ga
-
-  セグメントのうち最も大きなIDです。
-
-\(ga\(ganumber of garbage segments\(ga\(ga
-
-  ゴミセグメントの数です。
-
-\(ga\(ganumber of array segments\(ga\(ga
-
-  配列セグメントの数です。
-
-\(ga\(gamax id of array segment\(ga\(ga
-
-  配列セグメントのうち最も大きなIDです。
-
-\(ga\(ganumber of buffer segments\(ga\(ga
-
-  バッファセグメントの数です。
-
-\(ga\(gamax id of buffer segment\(ga\(ga
-
-  バッファセグメントのうち最も大きなIDです。
-
-\(ga\(gamax id of physical segment in use\(ga\(ga
-
-  使用中の論理セグメントのうち最も大きなIDです。
-
-\(ga\(ganumber of unmanaged segments\(ga\(ga
-
-  管理されていないセグメントの数です。
-
-\(ga\(gatotal chunk size\(ga\(ga
-
-  チャンクサイズの合計です。
-
-\(ga\(gamax id of chunk segments in use\(ga\(ga
-
-  使用中のチャンクセグメントのうち最も大きなIDです。
-
-\(ga\(ganumber of garbage chunk\(ga\(ga
-
-  各チャンク毎のゴミの数です。
-
-\(ga\(gaバッファの状態\(ga\(gaには下記の項目がハッシュ形式で出力されます。
-
-\(ga\(gabuffer id\(ga\(ga
-
-  バッファIDです。
-
-\(ga\(gachunk size\(ga\(ga
-
-  チャンクのサイズです。
-
-\(ga\(gabuffer term\(ga\(ga
-
-  バッファ内にある語の一覧です。各語の状態は以下のような配列となっています。
-
-    [語, バッファに登録されている語のID, 用語集に登録されている語のID, バッファ内でのサイズ, チャンク内でのサイズ]
-
-\(ga\(gabuffer free\(ga\(ga
-
-  バッファの空き容量です。
-
-\(ga\(gasize in buffer\(ga\(ga
-
-  バッファの使用量です。
-
-\(ga\(ganterms\(ga\(ga
-
-  バッファ内にある語の数です。
-
-\(ga\(ganterms with chunk\(ga\(ga
-
-  バッファ内にある語のうち、チャンクを使っている語の数です。
 .ft P
 .fi
+.sp
+\fBインデックスの状態\fP には下記の項目がハッシュ形式で出力されます。
+.INDENT 0.0
+.INDENT 3.5
+\fBflags\fP
+.INDENT 0.0
+.INDENT 3.5
+指定されているフラグ値です。16進数で表現されています。
+.UNINDENT
+.UNINDENT
+.sp
+\fBmax sid\fP
+.INDENT 0.0
+.INDENT 3.5
+セグメントのうち最も大きなIDです。
+.UNINDENT
+.UNINDENT
+.sp
+\fBnumber of garbage segments\fP
+.INDENT 0.0
+.INDENT 3.5
+ゴミセグメントの数です。
+.UNINDENT
+.UNINDENT
+.sp
+\fBnumber of array segments\fP
+.INDENT 0.0
+.INDENT 3.5
+配列セグメントの数です。
+.UNINDENT
+.UNINDENT
+.sp
+\fBmax id of array segment\fP
+.INDENT 0.0
+.INDENT 3.5
+配列セグメントのうち最も大きなIDです。
+.UNINDENT
+.UNINDENT
+.sp
+\fBnumber of buffer segments\fP
+.INDENT 0.0
+.INDENT 3.5
+バッファセグメントの数です。
+.UNINDENT
+.UNINDENT
+.sp
+\fBmax id of buffer segment\fP
+.INDENT 0.0
+.INDENT 3.5
+バッファセグメントのうち最も大きなIDです。
+.UNINDENT
+.UNINDENT
+.sp
+\fBmax id of physical segment in use\fP
+.INDENT 0.0
+.INDENT 3.5
+使用中の論理セグメントのうち最も大きなIDです。
+.UNINDENT
+.UNINDENT
+.sp
+\fBnumber of unmanaged segments\fP
+.INDENT 0.0
+.INDENT 3.5
+管理されていないセグメントの数です。
+.UNINDENT
+.UNINDENT
+.sp
+\fBtotal chunk size\fP
+.INDENT 0.0
+.INDENT 3.5
+チャンクサイズの合計です。
+.UNINDENT
+.UNINDENT
+.sp
+\fBmax id of chunk segments in use\fP
+.INDENT 0.0
+.INDENT 3.5
+使用中のチャンクセグメントのうち最も大きなIDです。
+.UNINDENT
+.UNINDENT
+.sp
+\fBnumber of garbage chunk\fP
+.INDENT 0.0
+.INDENT 3.5
+各チャンク毎のゴミの数です。
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+\fBバッファの状態\fP には下記の項目がハッシュ形式で出力されます。
+.INDENT 0.0
+.INDENT 3.5
+\fBbuffer id\fP
+.INDENT 0.0
+.INDENT 3.5
+バッファIDです。
+.UNINDENT
+.UNINDENT
+.sp
+\fBchunk size\fP
+.INDENT 0.0
+.INDENT 3.5
+チャンクのサイズです。
+.UNINDENT
+.UNINDENT
+.sp
+\fBbuffer term\fP
+.INDENT 0.0
+.INDENT 3.5
+バッファ内にある語の一覧です。各語の状態は以下のような配列となっています。
+.INDENT 0.0
+.INDENT 3.5
+[語, バッファに登録されている語のID, 用語集に登録されている語のID, バッファ内でのサイズ, チャンク内でのサイズ]
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+\fBbuffer free\fP
+.INDENT 0.0
+.INDENT 3.5
+バッファの空き容量です。
+.UNINDENT
+.UNINDENT
+.sp
+\fBsize in buffer\fP
+.INDENT 0.0
+.INDENT 3.5
+バッファの使用量です。
+.UNINDENT
+.UNINDENT
+.sp
+\fBnterms\fP
+.INDENT 0.0
+.INDENT 3.5
+バッファ内にある語の数です。
+.UNINDENT
+.UNINDENT
+.sp
+\fBnterms with chunk\fP
+.INDENT 0.0
+.INDENT 3.5
+バッファ内にある語のうち、チャンクを使っている語の数です。
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
 .SS 例
 .sp
 テーブルTermsのインデックスカラムnameの状態を表示します。:
@@ -10353,12 +10544,15 @@ clearlockは、対象となるオブジェクト(データベース,テーブル
 .nf
 .ft C
 [成功かどうかのフラグ]
-
-\(ga\(ga成功かどうかのフラグ\(ga\(ga
-
-  エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
 .ft P
 .fi
+.sp
+\fB成功かどうかのフラグ\fP
+.INDENT 0.0
+.INDENT 3.5
+エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
+.UNINDENT
+.UNINDENT
 .SS 例
 .sp
 開いているデータベースのロックをすべて解除する:
@@ -10466,12 +10660,15 @@ column_createは、使用しているデータベースのテーブルに対し
 .nf
 .ft C
 [成功かどうかのフラグ]
-
-\(ga\(ga成功かどうかのフラグ\(ga\(ga
-
-  エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
 .ft P
 .fi
+.sp
+\fB成功かどうかのフラグ\fP
+.INDENT 0.0
+.INDENT 3.5
+エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
+.UNINDENT
+.UNINDENT
 .SS 例
 .sp
 テーブルEntryに、ShortText型の値を格納するカラム、bodyを作成します。:
@@ -10660,12 +10857,15 @@ column_removeはテーブルに定義されているカラムを削除します
 .nf
 .ft C
 [成功かどうかのフラグ]
-
-\(ga\(ga成功かどうかのフラグ\(ga\(ga
-
-  エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
 .ft P
 .fi
+.sp
+\fB成功かどうかのフラグ\fP
+.INDENT 0.0
+.INDENT 3.5
+エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
+.UNINDENT
+.UNINDENT
 .SS 例
 .sp
 .nf
@@ -10678,8 +10878,188 @@ column_remove Entry body
 脚注
 .IP [1] 5
 マルチセクションインデックスの一部である場合も、インデックスが削除されます。
-.SS define_selector
-.SS 名前
+.SS \fBcolumn_rename\fP
+.SS Summary
+.sp
+\fBcolumn_rename\fP command renames specified column name of table.
+.SS Syntax
+.sp
+\fBcolumn_rename\fP command takes two parameters.
+.sp
+The required parameter is \fBtable\fP and \fBcolumn_name\fP:
+.sp
+.nf
+.ft C
+column_rename table column
+.ft P
+.fi
+.SS Usage
+.sp
+Here is a simple example of \fBcolumn_rename\fP command.
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+table_create Users TABLE_PAT_KEY ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Users score COLUMN_SCALAR Int32
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+load \-\-table Users
+[
+{"_key": "Alice",  "score": 2},
+{"_key": "Bob",    "score": 0},
+{"_key": "Carlos", "score": \-1}
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 3]
+column_rename Users score point
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_list Users
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   [
+#     [
+#       [
+#         "id",
+#         "UInt32"
+#       ],
+#       [
+#         "name",
+#         "ShortText"
+#       ],
+#       [
+#         "path",
+#         "ShortText"
+#       ],
+#       [
+#         "type",
+#         "ShortText"
+#       ],
+#       [
+#         "flags",
+#         "ShortText"
+#       ],
+#       [
+#         "domain",
+#         "ShortText"
+#       ],
+#       [
+#         "range",
+#         "ShortText"
+#       ],
+#       [
+#         "source",
+#         "ShortText"
+#       ]
+#     ],
+#     [
+#       256,
+#       "_key",
+#       "",
+#       "",
+#       "COLUMN_SCALAR",
+#       "Users",
+#       "ShortText",
+#       []
+#     ],
+#     [
+#       257,
+#       "point",
+#       "/tmp/groonga\-databases/commands_column_rename.0000101",
+#       "fix",
+#       "COLUMN_SCALAR|PERSISTENT",
+#       "Users",
+#       "Int32",
+#       []
+#     ]
+#   ]
+# ]
+select Users
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   [
+#     [
+#       [
+#         3
+#       ],
+#       [
+#         [
+#           "_id",
+#           "UInt32"
+#         ],
+#         [
+#           "_key",
+#           "ShortText"
+#         ],
+#         [
+#           "point",
+#           "Int32"
+#         ]
+#       ],
+#       [
+#         1,
+#         "Alice",
+#         2
+#       ],
+#       [
+#         2,
+#         "Bob",
+#         0
+#       ],
+#       [
+#         3,
+#         "Carlos",
+#         \-1
+#       ]
+#     ]
+#   ]
+# ]
+.ft P
+.fi
+.SS Parameters
+.sp
+This section describes parameters of \fBcolumn_rename\fP.
+.SS Required parameter
+.sp
+There are required parameters, \fBtable_name\fP and \fBcolumn_name\fP.
+.SS \fBtable_name\fP
+.sp
+It specifies the name of table.
+.SS \fBcolumn_name\fP
+.sp
+It specifies the name of column.
+.SS Return value
+.sp
+.nf
+.ft C
+[HEADER, SUCCEEDED_OR_NOT]
+.ft P
+.fi
+.sp
+\fBHEADER\fP
+.INDENT 0.0
+.INDENT 3.5
+The format of HEADER is [0, UNIX_TIME_WHEN_COMMAND_IS_STARTED, ELAPSED_TIME].
+See \fB/reference/command/output_format\fP about HEADER.
+.UNINDENT
+.UNINDENT
+.sp
+\fBSUCCEEDED_OR_NOT\fP
+.INDENT 0.0
+.INDENT 3.5
+If command succeeded, it returns true, otherwise it returns false on error.
+.UNINDENT
+.UNINDENT
+.SS define_selector
+.SS 名前
 .sp
 define_selector \- 検索コマンドを定義
 .SS 書式
@@ -10808,12 +11188,15 @@ define_selectorは、検索条件をカスタマイズした新たな検索コ
 .nf
 .ft C
 [成功かどうかのフラグ]
-
-\(ga\(ga成功かどうかのフラグ\(ga\(ga
-
-  エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
 .ft P
 .fi
+.sp
+\fB成功かどうかのフラグ\fP
+.INDENT 0.0
+.INDENT 3.5
+エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
+.UNINDENT
+.UNINDENT
 .SS 例
 .sp
 テーブルEntryの全レコード・全カラムの値を出力するselectorコマンドを定義します。:
@@ -10857,12 +11240,15 @@ defragは、対象となるオブジェクト(データベースか可変長サ
 .nf
 .ft C
 [フラグメンテーション解消を実行したセグメントの数]
-
-\(ga\(gaフラグメンテーション解消を実行したセグメントの数\(ga\(ga
-
-  フラグメンテーション解消を実行したセグメントの数を返す。
 .ft P
 .fi
+.sp
+\fBフラグメンテーション解消を実行したセグメントの数\fP
+.INDENT 0.0
+.INDENT 3.5
+フラグメンテーション解消を実行したセグメントの数を返す。
+.UNINDENT
+.UNINDENT
 .SS 例
 .sp
 開いているデータベースのフラグメンテーションを解消する:
@@ -10935,12 +11321,15 @@ script形式のgrn_expr文字列によってレコードを指定します。fil
 .nf
 .ft C
 [成功かどうかのフラグ]
-
-\(ga\(ga成功かどうかのフラグ\(ga\(ga
-
-  エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
 .ft P
 .fi
+.sp
+\fB成功かどうかのフラグ\fP
+.INDENT 0.0
+.INDENT 3.5
+エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
+.UNINDENT
+.UNINDENT
 .SS 例
 .sp
 テーブルEntryからレコードを削除します。:
@@ -11042,116 +11431,116 @@ load \-\-table Sites
 ]
 .ft P
 .fi
-.SS load
-.SS 名前
+.SS \fBload\fP
+.SS Summary
 .sp
-load \- データのロード
-.SS 書式
+\fBload\fP loads data as records in the current database and updates values of each columns.
+.SS Syntax
 .sp
 .nf
 .ft C
 load values table [columns [ifexists [input_type]]]
 .ft P
 .fi
-.SS 説明
-.sp
-groonga組込コマンドの一つであるloadについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
+.SS Parameters
 .sp
-loadは、使用しているデータベースのテーブルにレコードを登録し、カラムの値を更新します。
-.SS 引数
+This section describes all parameters.
 .sp
 \fBvalues\fP
 .INDENT 0.0
 .INDENT 3.5
-input_typeに指定する形式で登録するレコードの値を表現した文字列を渡します。
-.sp
-input_typeがjsonである場合には、以下のいずれかの形式が使用できます。
+It specifies values loaded to records.
+Values should satisfy \fBinput_type\fP format.
+If you specify "json" as \fBinput_type\fP, you can choose a format from below:
 .INDENT 0.0
 .TP
-.B \fB形式1\fP
-[[カラム名1, カラム名2,..], [カラム値1, カラム値2,..], [カラム値1, カラム値2,..],..]
+.B \fBFormat 1:\fP
+[[COLUMN_NAME1, COLUMN_NAME2,..], [VALUE1, VALUE2,..], [VALUE1, VALUE2,..],..]
 .TP
-.B \fB形式2\fP
-[{カラム名1: カラム値1, カラム名2: カラム値2}, {カラム名1: カラム値1, カラム名2: カラム値2},..]
+.B \fBFormat 2:\fP
+[{COLUMN_NAME1: VALUE1, COLUMN_NAME2: VALUE2}, {COLUMN_NAME1: VALUE1, COLUMN_NAME2: VALUE2},..]
 .UNINDENT
 .sp
-形式1の[カラム名1, カラム名2,..]の要素はcolumns引数が省略された場合のみ有効です。
+\fB[COLUMN_NAME1, COLUMN_NAME2,..]\fP format in \fBFormat 1\fP is effective only when \fBcolumn\fP parameter isn\(aqt specified.
 .sp
-対象のテーブルが主キーを持つテーブルであった場合は、カラム名の中に\(aq_key\(aq(主キーを示す疑似カラム名)が含まれていなければなりません。
+When a target table contains primary key, you must specify \fB_key\fP column (pseudo column associated primary key) as the one of \fBCOLUMN_NAME\fP.
 .sp
-values引数が省略された場合には、括弧の対応が取れるまで標準入力からvaluesの値を読み取ります。引数として値を指定する場合は、文字列のエスケープが必要ですが、標準入力から与える文字列はエスケープする必要がありません。
+If \fBvalues\fP isn\(aqt specified any values, they are read from the standard input until all opened parenthes match their closed ones.
+You don\(aqt have to enclose them with single\-quotes or double\-quotes, but if you specified values with \fBvalues\fP parameter, you should do.
 .sp
-続きの文字列については、空白文字(\(aq \(aq)をエスケープする必要はありません。
+In following values, you also don\(aqt have to enclose any spaces (\(aq \(aq) with single\-quotes or double\-quotes.
 .UNINDENT
 .UNINDENT
 .sp
 \fBtable\fP
 .INDENT 0.0
 .INDENT 3.5
-レコードを追加しようとするテーブルの名前を指定します。
+It specifies a table name you want to add records.
 .UNINDENT
 .UNINDENT
 .sp
 \fBcolumns\fP
 .INDENT 0.0
 .INDENT 3.5
-テーブルに登録するレコードに値を設定するカラム名のリストを、カンマ区切りで指定します。
+It specifies column names in added records with comma separations.
 .UNINDENT
 .UNINDENT
 .sp
 \fBifexists\fP
 .INDENT 0.0
 .INDENT 3.5
-指定した主キーに対応するレコードが既にテーブルに登録済みであった場合に実行するscript形式のgrn_expr文字列を指定します。ifexistsにgrn_exprが指定された場合は、式の値が真である場合に限り、その他のカラムの値が更新されます。(デフォルトはtrue)
+It specifies executed \fBgrn_expr\fP string when the same primary key
+as added records already exists in your table.
+If \fBifexists\fP specifies \fBgrn_expr\fP string (default: true) and
+its value is true, values in other (all columns excluding \fB_key\fP
+column) columns is updated.
 .UNINDENT
 .UNINDENT
 .sp
 \fBinput_type\fP
 .INDENT 0.0
 .INDENT 3.5
-入力形式を指定します。JSONのみに対応しています。
-.UNINDENT
-.UNINDENT
-.SS 返値
-.SS JSON形式
-.sp
-.nf
-.ft C
-[登録件数]
-.ft P
-.fi
-.sp
-\fB登録件数\fP
-.INDENT 0.0
-.INDENT 3.5
-テーブルに登録されたレコードの件数が返されます。
+It specifies an input format for \fBvalues\fP. It supports JSON only.
 .UNINDENT
 .UNINDENT
-.SS 例
+.SS Usage
 .sp
-テーブルEntryにレコードを登録します。:
+Here is an example to add records to "Entry" table.
 .sp
 .nf
 .ft C
-load \-\-table Entry \-\-input_type json \-\-values [{\e"_key\e":\e"abandon\e",\e"body\e":\e"放棄する\e"}]
+load \-\-table Entry \-\-input_type json \-\-values [{\e"_key\e":\e"Groonga\e",\e"body\e":\e"It\(aqs very fast!!\e"}]
 
 [1]
 .ft P
 .fi
 .sp
-標準入力からvaluesの値を与えます。:
+This example shows how to add values from standard input.
 .sp
 .nf
 .ft C
 load \-\-table Entry \-\-input_type json
 [
-{"_key": "abbreviate", "body": "短縮する"}
+{"_key": "Groonga", "body": "It\(aqs very fast!!"}
 ]
 
 [1]
 .ft P
 .fi
-.SS 関連項目
+.SS Return value
+.SS JSON format
+.INDENT 0.0
+.INDENT 3.5
+\fBload\fP returns the number of added records such as
+.sp
+.nf
+.ft C
+[NUMBER]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS See also
 .sp
 \fB/reference/grn_expr\fP
 .SS log_level
@@ -11196,12 +11585,15 @@ debug
 .nf
 .ft C
 [成功かどうかのフラグ]
-
-\(ga\(ga成功かどうかのフラグ\(ga\(ga
-
-  エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
 .ft P
 .fi
+.sp
+\fB成功かどうかのフラグ\fP
+.INDENT 0.0
+.INDENT 3.5
+エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
+.UNINDENT
+.UNINDENT
 .SS 例
 .sp
 .nf
@@ -11263,12 +11655,15 @@ debug
 .nf
 .ft C
 [成功かどうかのフラグ]
-
-\(ga\(ga成功かどうかのフラグ\(ga\(ga
-
-  エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
 .ft P
 .fi
+.sp
+\fB成功かどうかのフラグ\fP
+.INDENT 0.0
+.INDENT 3.5
+エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
+.UNINDENT
+.UNINDENT
 .SS 例
 .sp
 .nf
@@ -11308,12 +11703,15 @@ log_reopenは、ログファイルを再読み込みします。
 .nf
 .ft C
 [成功かどうかのフラグ]
-
-\(ga\(ga成功かどうかのフラグ\(ga\(ga
-
-  エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
 .ft P
 .fi
+.sp
+\fB成功かどうかのフラグ\fP
+.INDENT 0.0
+.INDENT 3.5
+エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
+.UNINDENT
+.UNINDENT
 .SS 例
 .sp
 .nf
@@ -11338,49 +11736,123 @@ log_reopenコマンドを実行する。
 .sp
 \fBlog_level\fP
 \fBlog_put\fP
-.SS quit
-.SS 名前
+.SS \fBnormalize\fP
+.IP Caution
+\fBnormalize\fP command is the experimental feature.
+This command may be changed in the future.
+.RE
+.SS Summary
 .sp
-quit \- セッション終了
-.SS 書式
+\fBnormalize\fP command normalizes text by the specified normalizer.
+.sp
+There is no need to create table to use \fBnormalize\fP command.
+It is usefull for you to check the results of normalizer.
+.SS Syntax
+.sp
+\fBnormalize\fP commands takes two parameters \- \fBnormalizer\fP and \fBstring\fP.
+Both of them are required.
 .sp
 .nf
 .ft C
-quit
+normalize normalizer string
 .ft P
 .fi
-.SS 説明
-.sp
-groonga組込コマンドの一つであるquitについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
-.sp
-quitは、groongaプロセスとのセッションを終了します。クライアントプロセスならばgroongaプロセスとの接続を切ります。
-.SS 引数
+.SS Usage
 .sp
-ありません。
-.SS 返値
+Here is a simple example of \fBnormalize\fP command.
 .sp
-ありません。
-.SS 例
+Execution example:
 .sp
 .nf
 .ft C
-quit
+normalize NormalizerAuto "aBcDe 123"
+# [[0, 1337566253.89858, 0.000355720520019531], "abcde 123"]
 .ft P
 .fi
-.SS register
-.SS Summary
+.SS Parameters
 .sp
-\fBregister\fP command registers a plugin. You need to register a plugin
-before you use a plugin.
+This section describes parameters of \fBnormalizer\fP.
+.SS Required parameter
 .sp
-You need just one \fBregister\fP command for a plugin in the same
-database because registered plugin information is written into the
-database.  When you restart your \fBgroonga\fP process, \fBgroonga\fP
-process loads all registered plugins without \fBregister\fP command.
-.IP Note
-Registered plugins can\(aqt be removed for now.
-.RE
-.SS Syntax
+There are required parameters, \fBnormalizer\fP and \fBstring\fP.
+.SS \fBnormalizer\fP
+.sp
+It specifies the name of normalizer.
+Currently, \fBnormalize\fP command accepts \fBNormalizerAuto\fP or \fBNormalizerNFKC51\fP as built\-in normalizer.
+If you want to try another normalizer, you need to register additional normalizer plugin by \fBregister\fP command.
+.SS \fBstring\fP
+.sp
+It specifies any string which you want to normalize.
+.SS Return value
+.sp
+.nf
+.ft C
+[HEADER, normalized]
+.ft P
+.fi
+.sp
+\fBHEADER\fP
+.INDENT 0.0
+.INDENT 3.5
+The format of HEADER is [0, UNIX_TIME_WHEN_COMMAND_IS_STARTED, ELAPSED_TIME].
+See \fB/reference/command/output_format\fP about HEADER.
+.UNINDENT
+.UNINDENT
+.sp
+\fBnormalized\fP
+.INDENT 0.0
+.INDENT 3.5
+normalized is the normalized text by the specified normalizer.
+.UNINDENT
+.UNINDENT
+.SS See also
+.INDENT 0.0
+.IP \(bu 2
+\fB/reference/normalizers\fP
+.UNINDENT
+.SS quit
+.SS 名前
+.sp
+quit \- セッション終了
+.SS 書式
+.sp
+.nf
+.ft C
+quit
+.ft P
+.fi
+.SS 説明
+.sp
+groonga組込コマンドの一つであるquitについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
+.sp
+quitは、groongaプロセスとのセッションを終了します。クライアントプロセスならばgroongaプロセスとの接続を切ります。
+.SS 引数
+.sp
+ありません。
+.SS 返値
+.sp
+ありません。
+.SS 例
+.sp
+.nf
+.ft C
+quit
+.ft P
+.fi
+.SS register
+.SS Summary
+.sp
+\fBregister\fP command registers a plugin. You need to register a plugin
+before you use a plugin.
+.sp
+You need just one \fBregister\fP command for a plugin in the same
+database because registered plugin information is written into the
+database.  When you restart your \fBgroonga\fP process, \fBgroonga\fP
+process loads all registered plugins without \fBregister\fP command.
+.IP Note
+Registered plugins can\(aqt be removed for now.
+.RE
+.SS Syntax
 .sp
 \fBregister\fP has a parameter \fBpath\fP. It is required parameter:
 .sp
@@ -11455,6 +11927,7 @@ select table
        [match_escalation_threshold=0]
        [query_expansion=null]
        [query_flags=ALLOW_PRAGMA|ALLOW_COLUMN|ALLOW_UPDATE|ALLOW_LEADING_NOT|NONE]
+       [query_expander=null]
 .ft P
 .fi
 .SS Usage
@@ -12569,74 +13042,59 @@ records (0) is larger than \fBmatch_escalation_threshold\fP (\-1). So no
 more searches aren\(aqt executed. And no records are matched.
 .SS \fBquery_expansion\fP
 .sp
-It\(aqs for query expansion. Query expansion substitutes specific words
-to another words in query. Nomally, it\(aqs used for synonym search.
+Deprecated. Use \fIquery\-expander\fP instead.
+.SS \fBquery_flags\fP
 .sp
-It specifies a column that is used to substitute \fBquery\fP parameter
-value. The format of this parameter value is
-"\fB${TABLE}.${COLUMN}\fP". For example, "\fBTerms.synonym\fP" specifies
-\fBsynonym\fP column in \fBTerms\fP table.
+It customs \fBquery\fP parameter syntax. You cannot update column value
+by \fBquery\fP parameter by default. But if you specify
+\fBALLOW_COLUMN|ALLOW_UPDATE\fP as \fBquery_flags\fP, you can update
+column value by \fBquery\fP.
 .sp
-Table for query expansion is called "substitution table". Substitution
-table\(aqs key must be \fBShortText\fP. So array table (\fBTABLE_NO_KEY\fP)
-can\(aqt be used for query expansion. Because array table doesn\(aqt have
-key.
+Here are available values:
+.INDENT 0.0
+.IP \(bu 2
+\fBALLOW_PRAGMA\fP
+.IP \(bu 2
+\fBALLOW_COLUMN\fP
+.IP \(bu 2
+\fBALLOW_UPDATE\fP
+.IP \(bu 2
+\fBALLOW_LEADING_NOT\fP
+.IP \(bu 2
+\fBNONE\fP
+.UNINDENT
 .sp
-Column for query expansion is called "substitution
-column". Substitution column\(aqs value type must be
-\fBShortText\fP. Column type must be vector (\fBCOLUMN_VECTOR\fP).
+\fBALLOW_PRAGMA\fP enables pragma at the head of \fBquery\fP. This is not
+implemented yet.
 .sp
-Query expansion substitutes key of substitution table in query with
-values in substitution column. If a word in \fBquery\fP is a key of
-substitution table, the word is substituted with substitution column
-value that is associated with the key. Substition isn\(aqt performed
-recursively. It means that substitution target words in substituted
-query aren\(aqt substituted.
+\fBALLOW_COLUMN\fP enables search againt columns that are not included
+in \fBmatch_columns\fP. To specify column, there are \fBCOLUMN:...\fP
+syntaxes.
 .sp
-Here is a sample substitution table to show a simple
-\fBquery_expansion\fP usage example.
+\fBALLOW_UPDATE\fP enables column update by \fBquery\fP with
+\fBCOLUMN:=NEW_VALUE\fP syntax. \fBALLOW_COLUMN\fP is also required to
+update column because the column update syntax specifies column.
 .sp
-Execution example:
+\fBALLOW_LEADING_NOT\fP enables leading NOT condition with \fB\-WORD\fP
+syntax. The query searches records that doesn\(aqt match
+\fBWORD\fP. Leading NOT condition query is heavy query in many cases
+because it matches many records. So this flag is disabled by
+default. Be careful about it when you use the flag.
 .sp
-.nf
-.ft C
-table_create Thesaurus TABLE_PAT_KEY|KEY_NORMALIZE ShortText
-# [[0, 1337566253.89858, 0.000355720520019531], true]
-column_create Thesaurus synonym COLUMN_VECTOR ShortText
-# [[0, 1337566253.89858, 0.000355720520019531], true]
-load \-\-table Thesaurus
-[
-{"_key": "mroonga", "synonym": ["mroonga", "tritonn", "groonga mysql"]},
-{"_key": "groonga", "synonym": ["groonga", "senna"]}
-]
-# [[0, 1337566253.89858, 0.000355720520019531], 2]
-.ft P
-.fi
+\fBNONE\fP is just ignores. You can use \fBNONE\fP for specifying no flags.
 .sp
-\fBThesaurus\fP substitution table has two synonyms, \fB"mroonga"\fP and
-\fB"groonga"\fP. If an user searches with \fB"mroonga"\fP, groonga
-searches with \fB"((mroonga) OR (tritonn) OR (groonga mysql))"\fP. If an
-user searches with \fB"groonga"\fP, groonga searchs with \fB"((groonga)
-OR (senna))"\fP. Nomrally, it\(aqs good idea that substitution table has
-\fBKEY_NORMALIZE\fP flag. If the flag is used, substitute target word is
-matched in case insensitive manner.
+They can be combined by separated \fB|\fP such as
+\fBALLOW_COLUMN|ALLOW_UPDATE\fP.
 .sp
-Note that those synonym values include the key value such as
-\fB"mroonga"\fP and \fB"groonga"\fP. It\(aqs recommended that you include the
-key value. If you don\(aqt include key value, substituted value doesn\(aqt
-include the original substitute target value. Normally, including the
-original value is better search result. If you have a word that you
-don\(aqt want to be searched, you should not include the original
-word. For example, you can implement "stop words" by an empty vector
-value.
+The default value is \fBALLOW_PRAGMA|ALLOW_COLUMN\fP.
 .sp
-Here is a simple \fBquery_expansion\fP usage example.
+Here is a usage example of \fBALLOW_COLUMN\fP.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-select Entries \-\-match_columns content \-\-query "mroonga"
+select Entries \-\-query content:@mroonga \-\-query_flags ALLOW_COLUMN
 # [
 #   [
 #     0,
@@ -12675,7 +13133,29 @@ select Entries \-\-match_columns content \-\-query "mroonga"
 #     ]
 #   ]
 # ]
-select Entries \-\-match_columns content \-\-query "mroonga" \-\-query_expansion Thesaurus.synonym
+.ft P
+.fi
+.sp
+The \fBselect\fP command searches records that contain \fBmroonga\fP in
+\fBcontent\fP column value from \fBEntries\fP table.
+.sp
+Here is a usage example of \fBALLOW_UPDATE\fP.
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+table_create Users TABLE_HASH_KEY ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Users age COLUMN_SCALAR UInt32
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+load \-\-table Users
+[
+{"_key": "alice", "age": 18},
+{"_key": "bob",   "age": 20}
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 2]
+select Users \-\-query age:=19 \-\-query_flags ALLOW_COLUMN|ALLOW_UPDATE
 # [
 #   [
 #     0,
@@ -12697,30 +13177,24 @@ select Entries \-\-match_columns content \-\-query "mroonga" \-\-query_expansion
 #           "ShortText"
 #         ],
 #         [
-#           "content",
-#           "Text"
-#         ],
-#         [
-#           "n_likes",
+#           "age",
 #           "UInt32"
 #         ]
 #       ],
 #       [
-#         3,
-#         "Mroonga",
-#         "I also started to use mroonga. It\(aqs also very fast! Really fast!",
-#         15
+#         1,
+#         "alice",
+#         19
 #       ],
 #       [
-#         5,
-#         "Good\-bye Tritonn",
-#         "I also migrated all Tritonn system!",
-#         3
+#         2,
+#         "bob",
+#         19
 #       ]
 #     ]
 #   ]
 # ]
-select Entries \-\-match_columns content \-\-query "((mroonga) OR (tritonn) OR (groonga mysql))"
+select Users
 # [
 #   [
 #     0,
@@ -12742,25 +13216,19 @@ select Entries \-\-match_columns content \-\-query "((mroonga) OR (tritonn) OR (
 #           "ShortText"
 #         ],
 #         [
-#           "content",
-#           "Text"
-#         ],
-#         [
-#           "n_likes",
+#           "age",
 #           "UInt32"
 #         ]
 #       ],
 #       [
-#         3,
-#         "Mroonga",
-#         "I also started to use mroonga. It\(aqs also very fast! Really fast!",
-#         15
+#         1,
+#         "alice",
+#         19
 #       ],
 #       [
-#         5,
-#         "Good\-bye Tritonn",
-#         "I also migrated all Tritonn system!",
-#         3
+#         2,
+#         "bob",
+#         19
 #       ]
 #     ]
 #   ]
@@ -12768,28 +13236,17 @@ select Entries \-\-match_columns content \-\-query "((mroonga) OR (tritonn) OR (
 .ft P
 .fi
 .sp
-The first \fBselect\fP command doesn\(aqt use query expansion. So a record
-that has \fB"tritonn"\fP isn\(aqt found. The second \fBselect\fP command uses
-query expansion. So a record that has \fB"tritonn"\fP is found. The
-third \fBselect\fP command doesn\(aqt use query expansion but it is same as
-the second \fBselect\fP command. The third one uses expanded query.
-.sp
-Each substitute value can contain any \fB/reference/grn_expr/query_syntax\fP syntax
-such as \fB(...)\fP and \fBOR\fP. You can use complex substitution by
-using those syntax.
+The first \fBselect\fP command sets \fBage\fP column value of all records
+to \fB19\fP. The second \fBselect\fP command outputs updated \fBage\fP
+column values.
 .sp
-Here is a complex substitution usage example that uses query syntax.
+Here is a usage example of \fBALLOW_LEADING_NOT\fP.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-load \-\-table Thesaurus
-[
-{"_key": "popular", "synonym": ["popular", "n_likes:>=10"]}
-]
-# [[0, 1337566253.89858, 0.000355720520019531], 1]
-select Entries \-\-match_columns content \-\-query "popular" \-\-query_expansion Thesaurus.synonym
+select Entries \-\-match_columns content \-\-query \-mroonga \-\-query_flags ALLOW_LEADING_NOT
 # [
 #   [
 #     0,
@@ -12799,7 +13256,7 @@ select Entries \-\-match_columns content \-\-query "popular" \-\-query_expansion
 #   [
 #     [
 #       [
-#         2
+#         4
 #       ],
 #       [
 #         [
@@ -12820,16 +13277,28 @@ select Entries \-\-match_columns content \-\-query "popular" \-\-query_expansion
 #         ]
 #       ],
 #       [
+#         1,
+#         "The first post!",
+#         "Welcome! This is my first post!",
+#         5
+#       ],
+#       [
 #         2,
 #         "Groonga",
 #         "I started to use groonga. It\(aqs very fast!",
 #         10
 #       ],
 #       [
-#         3,
-#         "Mroonga",
-#         "I also started to use mroonga. It\(aqs also very fast! Really fast!",
-#         15
+#         4,
+#         "Good\-bye Senna",
+#         "I migrated all Senna system!",
+#         3
+#       ],
+#       [
+#         5,
+#         "Good\-bye Tritonn",
+#         "I also migrated all Tritonn system!",
+#         3
 #       ]
 #     ]
 #   ]
@@ -12837,65 +13306,16 @@ select Entries \-\-match_columns content \-\-query "popular" \-\-query_expansion
 .ft P
 .fi
 .sp
-The \fBload\fP command registers a new synonym \fB"popular"\fP. It is
-substituted with \fB((popular) OR (n_likes:>=10))\fP. The substituted
-query means that "popular" is containing the word "popular" or 10 or
-more liked entries.
-.sp
-The \fBselect\fP command outputs records that \fBn_likes\fP column value
-is equal to or more than \fB10\fP from \fBEntries\fP table.
-.SS \fBquery_flags\fP
-.sp
-It customs \fBquery\fP parameter syntax. You cannot update column value
-by \fBquery\fP parameter by default. But if you specify
-\fBALLOW_COLUMN|ALLOW_UPDATE\fP as \fBquery_flags\fP, you can update
-column value by \fBquery\fP.
-.sp
-Here are available values:
-.INDENT 0.0
-.IP \(bu 2
-\fBALLOW_PRAGMA\fP
-.IP \(bu 2
-\fBALLOW_COLUMN\fP
-.IP \(bu 2
-\fBALLOW_UPDATE\fP
-.IP \(bu 2
-\fBALLOW_LEADING_NOT\fP
-.IP \(bu 2
-\fBNONE\fP
-.UNINDENT
-.sp
-\fBALLOW_PRAGMA\fP enables pragma at the head of \fBquery\fP. This is not
-implemented yet.
-.sp
-\fBALLOW_COLUMN\fP enables search againt columns that are not included
-in \fBmatch_columns\fP. To specify column, there are \fBCOLUMN:...\fP
-syntaxes.
-.sp
-\fBALLOW_UPDATE\fP enables column update by \fBquery\fP with
-\fBCOLUMN:=NEW_VALUE\fP syntax. \fBALLOW_COLUMN\fP is also required to
-update column because the column update syntax specifies column.
-.sp
-\fBALLOW_LEADING_NOT\fP enables leading NOT condition with \fB\-WORD\fP
-syntax. The query searches records that doesn\(aqt match
-\fBWORD\fP. Leading NOT condition query is heavy query in many cases
-because it matches many records. So this flag is disabled by
-default. Be careful about it when you use the flag.
-.sp
-\fBNONE\fP is just ignores. You can use \fBNONE\fP for specifying no flags.
-.sp
-They can be combined by separated \fB|\fP such as
-\fBALLOW_COLUMN|ALLOW_UPDATE\fP.
-.sp
-The default value is \fBALLOW_PRAGMA|ALLOW_COLUMN\fP.
+The \fBselect\fP command searches records that don\(aqt contain \fBmroonga\fP
+in \fBcontent\fP column value from \fBEntries\fP table.
 .sp
-Here is a usage example of \fBALLOW_COLUMN\fP.
+Here is a usage example of \fBNONE\fP.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-select Entries \-\-query content:@mroonga \-\-query_flags ALLOW_COLUMN
+select Entries \-\-match_columns content \-\-query \(aqmroonga OR _key:Groonga\(aq \-\-query_flags NONE
 # [
 #   [
 #     0,
@@ -12937,26 +13357,83 @@ select Entries \-\-query content:@mroonga \-\-query_flags ALLOW_COLUMN
 .ft P
 .fi
 .sp
-The \fBselect\fP command searches records that contain \fBmroonga\fP in
-\fBcontent\fP column value from \fBEntries\fP table.
+The \fBselect\fP command searches records that contain one of two words
+\fBmroonga\fP or \fB_key:Groonga\fP in \fBcontent\fP from \fBEntries\fP table.
+Note that \fB_key:Groonga\fP doesn\(aqt mean that the value of \fB_key\fP
+column is equal to \fBGroonga\fP. Because \fBALLOW_COLUMN\fP flag is not
+specified.
+.sp
+See also \fB/reference/grn_expr/query_syntax\fP.
+.SS \fBquery_expander\fP
+.sp
+It\(aqs for query expansion. Query expansion substitutes specific words
+to another words in query. Nomally, it\(aqs used for synonym search.
+.sp
+It specifies a column that is used to substitute \fBquery\fP parameter
+value. The format of this parameter value is
+"\fB${TABLE}.${COLUMN}\fP". For example, "\fBTerms.synonym\fP" specifies
+\fBsynonym\fP column in \fBTerms\fP table.
+.sp
+Table for query expansion is called "substitution table". Substitution
+table\(aqs key must be \fBShortText\fP. So array table (\fBTABLE_NO_KEY\fP)
+can\(aqt be used for query expansion. Because array table doesn\(aqt have
+key.
+.sp
+Column for query expansion is called "substitution
+column". Substitution column\(aqs value type must be
+\fBShortText\fP. Column type must be vector (\fBCOLUMN_VECTOR\fP).
+.sp
+Query expansion substitutes key of substitution table in query with
+values in substitution column. If a word in \fBquery\fP is a key of
+substitution table, the word is substituted with substitution column
+value that is associated with the key. Substition isn\(aqt performed
+recursively. It means that substitution target words in substituted
+query aren\(aqt substituted.
+.sp
+Here is a sample substitution table to show a simple
+\fBquery_expander\fP usage example.
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+table_create Thesaurus TABLE_PAT_KEY|KEY_NORMALIZE ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Thesaurus synonym COLUMN_VECTOR ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+load \-\-table Thesaurus
+[
+{"_key": "mroonga", "synonym": ["mroonga", "tritonn", "groonga mysql"]},
+{"_key": "groonga", "synonym": ["groonga", "senna"]}
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 2]
+.ft P
+.fi
+.sp
+\fBThesaurus\fP substitution table has two synonyms, \fB"mroonga"\fP and
+\fB"groonga"\fP. If an user searches with \fB"mroonga"\fP, groonga
+searches with \fB"((mroonga) OR (tritonn) OR (groonga mysql))"\fP. If an
+user searches with \fB"groonga"\fP, groonga searchs with \fB"((groonga)
+OR (senna))"\fP. Nomrally, it\(aqs good idea that substitution table has
+\fBKEY_NORMALIZE\fP flag. If the flag is used, substitute target word is
+matched in case insensitive manner.
+.sp
+Note that those synonym values include the key value such as
+\fB"mroonga"\fP and \fB"groonga"\fP. It\(aqs recommended that you include the
+key value. If you don\(aqt include key value, substituted value doesn\(aqt
+include the original substitute target value. Normally, including the
+original value is better search result. If you have a word that you
+don\(aqt want to be searched, you should not include the original
+word. For example, you can implement "stop words" by an empty vector
+value.
 .sp
-Here is a usage example of \fBALLOW_UPDATE\fP.
+Here is a simple \fBquery_expander\fP usage example.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-table_create Users TABLE_HASH_KEY ShortText
-# [[0, 1337566253.89858, 0.000355720520019531], true]
-column_create Users age COLUMN_SCALAR UInt32
-# [[0, 1337566253.89858, 0.000355720520019531], true]
-load \-\-table Users
-[
-{"_key": "alice", "age": 18},
-{"_key": "bob",   "age": 20}
-]
-# [[0, 1337566253.89858, 0.000355720520019531], 2]
-select Users \-\-query age:=19 \-\-query_flags ALLOW_COLUMN|ALLOW_UPDATE
+select Entries \-\-match_columns content \-\-query "mroonga"
 # [
 #   [
 #     0,
@@ -12966,7 +13443,7 @@ select Users \-\-query age:=19 \-\-query_flags ALLOW_COLUMN|ALLOW_UPDATE
 #   [
 #     [
 #       [
-#         2
+#         1
 #       ],
 #       [
 #         [
@@ -12978,24 +13455,24 @@ select Users \-\-query age:=19 \-\-query_flags ALLOW_COLUMN|ALLOW_UPDATE
 #           "ShortText"
 #         ],
 #         [
-#           "age",
+#           "content",
+#           "Text"
+#         ],
+#         [
+#           "n_likes",
 #           "UInt32"
 #         ]
 #       ],
 #       [
-#         1,
-#         "alice",
-#         19
-#       ],
-#       [
-#         2,
-#         "bob",
-#         19
+#         3,
+#         "Mroonga",
+#         "I also started to use mroonga. It\(aqs also very fast! Really fast!",
+#         15
 #       ]
 #     ]
 #   ]
 # ]
-select Users
+select Entries \-\-match_columns content \-\-query "mroonga" \-\-query_expander Thesaurus.synonym
 # [
 #   [
 #     0,
@@ -13017,37 +13494,30 @@ select Users
 #           "ShortText"
 #         ],
 #         [
-#           "age",
+#           "content",
+#           "Text"
+#         ],
+#         [
+#           "n_likes",
 #           "UInt32"
 #         ]
 #       ],
 #       [
-#         1,
-#         "alice",
-#         19
+#         3,
+#         "Mroonga",
+#         "I also started to use mroonga. It\(aqs also very fast! Really fast!",
+#         15
 #       ],
 #       [
-#         2,
-#         "bob",
-#         19
+#         5,
+#         "Good\-bye Tritonn",
+#         "I also migrated all Tritonn system!",
+#         3
 #       ]
 #     ]
 #   ]
 # ]
-.ft P
-.fi
-.sp
-The first \fBselect\fP command sets \fBage\fP column value of all records
-to \fB19\fP. The second \fBselect\fP command outputs updated \fBage\fP
-column values.
-.sp
-Here is a usage example of \fBALLOW_LEADING_NOT\fP.
-.sp
-Execution example:
-.sp
-.nf
-.ft C
-select Entries \-\-match_columns content \-\-query \-mroonga \-\-query_flags ALLOW_LEADING_NOT
+select Entries \-\-match_columns content \-\-query "((mroonga) OR (tritonn) OR (groonga mysql))"
 # [
 #   [
 #     0,
@@ -13057,7 +13527,7 @@ select Entries \-\-match_columns content \-\-query \-mroonga \-\-query_flags ALL
 #   [
 #     [
 #       [
-#         4
+#         2
 #       ],
 #       [
 #         [
@@ -13078,22 +13548,10 @@ select Entries \-\-match_columns content \-\-query \-mroonga \-\-query_flags ALL
 #         ]
 #       ],
 #       [
-#         1,
-#         "The first post!",
-#         "Welcome! This is my first post!",
-#         5
-#       ],
-#       [
-#         2,
-#         "Groonga",
-#         "I started to use groonga. It\(aqs very fast!",
-#         10
-#       ],
-#       [
-#         4,
-#         "Good\-bye Senna",
-#         "I migrated all Senna system!",
-#         3
+#         3,
+#         "Mroonga",
+#         "I also started to use mroonga. It\(aqs also very fast! Really fast!",
+#         15
 #       ],
 #       [
 #         5,
@@ -13107,16 +13565,28 @@ select Entries \-\-match_columns content \-\-query \-mroonga \-\-query_flags ALL
 .ft P
 .fi
 .sp
-The \fBselect\fP command searches records that don\(aqt contain \fBmroonga\fP
-in \fBcontent\fP column value from \fBEntries\fP table.
+The first \fBselect\fP command doesn\(aqt use query expansion. So a record
+that has \fB"tritonn"\fP isn\(aqt found. The second \fBselect\fP command uses
+query expansion. So a record that has \fB"tritonn"\fP is found. The
+third \fBselect\fP command doesn\(aqt use query expansion but it is same as
+the second \fBselect\fP command. The third one uses expanded query.
 .sp
-Here is a usage example of \fBNONE\fP.
+Each substitute value can contain any \fB/reference/grn_expr/query_syntax\fP syntax
+such as \fB(...)\fP and \fBOR\fP. You can use complex substitution by
+using those syntax.
+.sp
+Here is a complex substitution usage example that uses query syntax.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-select Entries \-\-match_columns content \-\-query \(aqmroonga OR _key:Groonga\(aq \-\-query_flags NONE
+load \-\-table Thesaurus
+[
+{"_key": "popular", "synonym": ["popular", "n_likes:>=10"]}
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 1]
+select Entries \-\-match_columns content \-\-query "popular" \-\-query_expander Thesaurus.synonym
 # [
 #   [
 #     0,
@@ -13126,7 +13596,7 @@ select Entries \-\-match_columns content \-\-query \(aqmroonga OR _key:Groonga\(
 #   [
 #     [
 #       [
-#         1
+#         2
 #       ],
 #       [
 #         [
@@ -13147,6 +13617,12 @@ select Entries \-\-match_columns content \-\-query \(aqmroonga OR _key:Groonga\(
 #         ]
 #       ],
 #       [
+#         2,
+#         "Groonga",
+#         "I started to use groonga. It\(aqs very fast!",
+#         10
+#       ],
+#       [
 #         3,
 #         "Mroonga",
 #         "I also started to use mroonga. It\(aqs also very fast! Really fast!",
@@ -13158,13 +13634,13 @@ select Entries \-\-match_columns content \-\-query \(aqmroonga OR _key:Groonga\(
 .ft P
 .fi
 .sp
-The \fBselect\fP command searches records that contain one of two words
-\fBmroonga\fP or \fB_key:Groonga\fP in \fBcontent\fP from \fBEntries\fP table.
-Note that \fB_key:Groonga\fP doesn\(aqt mean that the value of \fB_key\fP
-column is equal to \fBGroonga\fP. Because \fBALLOW_COLUMN\fP flag is not
-specified.
+The \fBload\fP command registers a new synonym \fB"popular"\fP. It is
+substituted with \fB((popular) OR (n_likes:>=10))\fP. The substituted
+query means that "popular" is containing the word "popular" or 10 or
+more liked entries.
 .sp
-See also \fB/reference/grn_expr/query_syntax\fP.
+The \fBselect\fP command outputs records that \fBn_likes\fP column value
+is equal to or more than \fB10\fP from \fBEntries\fP table.
 .SS Output related parameters
 .SS \fBoutput_columns\fP
 .sp
@@ -13906,20 +14382,29 @@ statusコマンドは、groongaプロセスの状態を表示します。主にg
 .nf
 .ft C
 下記の項目がハッシュ形式で出力されます。
-
-\(ga\(gaalloc_count\(ga\(ga
-
-  groongaプロセスの内部でアロケートされ、まだ解放されてないメモリブロックの数を示します。groongaをbuildする際に、configureオプションで \-\-enable\-exact\-alloc\-countが指定されていたならば、正確な値を返します。それ以外の場合は不正確な値を返す場合があります。
-
-\(ga\(gastarttime\(ga\(ga
-
-  groongaプロセスが起動した時刻のtvsec値を返します。
-
-\(ga\(gauptime\(ga\(ga
-
-  groongaプロセスが起動してから経過した秒数を返します。
 .ft P
 .fi
+.sp
+\fBalloc_count\fP
+.INDENT 0.0
+.INDENT 3.5
+groongaプロセスの内部でアロケートされ、まだ解放されてないメモリブロックの数を示します。groongaをbuildする際に、configureオプションで \-\-enable\-exact\-alloc\-countが指定されていたならば、正確な値を返します。それ以外の場合は不正確な値を返す場合があります。
+.UNINDENT
+.UNINDENT
+.sp
+\fBstarttime\fP
+.INDENT 0.0
+.INDENT 3.5
+groongaプロセスが起動した時刻のtvsec値を返します。
+.UNINDENT
+.UNINDENT
+.sp
+\fBuptime\fP
+.INDENT 0.0
+.INDENT 3.5
+groongaプロセスが起動してから経過した秒数を返します。
+.UNINDENT
+.UNINDENT
 .SS 例
 .sp
 Execution example:
@@ -14955,62 +15440,194 @@ table_list
 #       null
 #     ],
 #     [
-#       258,
-#       "Tags",
-#       "/tmp/groonga\-databases/commands_table_create.0000102",
-#       "TABLE_HASH_KEY|PERSISTENT",
-#       "ShortText",
-#       null,
-#       null,
-#       null
+#       258,
+#       "Tags",
+#       "/tmp/groonga\-databases/commands_table_create.0000102",
+#       "TABLE_HASH_KEY|PERSISTENT",
+#       "ShortText",
+#       null,
+#       null,
+#       null
+#     ]
+#   ]
+# ]
+.ft P
+.fi
+.SS table_remove
+.SS 名前
+.sp
+table_remove \- テーブルの削除
+.SS 書式
+.sp
+.nf
+.ft C
+table_remove name
+.ft P
+.fi
+.SS 説明
+.sp
+groonga組込コマンドの一つであるtable_removeについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
+.sp
+table_removeはテーブルと定義されているカラムを削除します。カラムに付随するインデックスも再帰的に削除されます。
+.SS 引数
+.INDENT 0.0
+.TP
+.B \fBname\fP
+削除対象のカラムが定義されているテーブルの名前を指定します。
+.UNINDENT
+.SS 返値
+.SS json形式
+.sp
+.nf
+.ft C
+[成功かどうかのフラグ]
+.ft P
+.fi
+.sp
+\fB成功かどうかのフラグ\fP
+.INDENT 0.0
+.INDENT 3.5
+エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
+.UNINDENT
+.UNINDENT
+.SS 例
+.sp
+.nf
+.ft C
+table_remove Entry
+
+[true]
+.ft P
+.fi
+.SS \fBtruncate\fP
+.SS Summary
+.sp
+\fBtruncate\fP command deletes all records from specified table.
+.SS Syntax
+.sp
+\fBtruncate\fP command takes only one parameter.
+.sp
+The required parameter is only \fBtable\fP:
+.sp
+.nf
+.ft C
+truncate table
+.ft P
+.fi
+.SS Usage
+.sp
+Here is a simple example of \fBtruncate\fP command.
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+table_create Users TABLE_PAT_KEY ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+load \-\-table Users
+[
+{"_key": "Alice",  "score": 2},
+{"_key": "Bob",    "score": 0},
+{"_key": "Carlos", "score": \-1}
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 3]
+select Users
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   [
+#     [
+#       [
+#         3
+#       ],
+#       [
+#         [
+#           "_id",
+#           "UInt32"
+#         ],
+#         [
+#           "_key",
+#           "ShortText"
+#         ]
+#       ],
+#       [
+#         1,
+#         "Alice"
+#       ],
+#       [
+#         2,
+#         "Bob"
+#       ],
+#       [
+#         3,
+#         "Carlos"
+#       ]
+#     ]
+#   ]
+# ]
+truncate Users
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+select Users
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   [
+#     [
+#       [
+#         0
+#       ],
+#       [
+#         [
+#           "_id",
+#           "UInt32"
+#         ],
+#         [
+#           "_key",
+#           "ShortText"
+#         ]
+#       ]
 #     ]
 #   ]
 # ]
 .ft P
 .fi
-.SS table_remove
-.SS 名前
+.SS Parameters
 .sp
-table_remove \- テーブルの削除
-.SS 書式
+This section describes parameters of \fBtruncate\fP.
+.SS Required parameter
+.sp
+There is required parameter, \fBtable_name\fP.
+.SS \fBtable_name\fP
+.sp
+It specifies the name of table.
+.SS Return value
 .sp
 .nf
 .ft C
-table_remove name
+[HEADER, SUCCEEDED_OR_NOT]
 .ft P
 .fi
-.SS 説明
-.sp
-groonga組込コマンドの一つであるtable_removeについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
 .sp
-table_removeはテーブルと定義されているカラムを削除します。カラムに付随するインデックスも再帰的に削除されます。
-.SS 引数
+\fBHEADER\fP
 .INDENT 0.0
-.TP
-.B \fBname\fP
-削除対象のカラムが定義されているテーブルの名前を指定します。
+.INDENT 3.5
+The format of HEADER is [0, UNIX_TIME_WHEN_COMMAND_IS_STARTED, ELAPSED_TIME].
+See \fB/reference/command/output_format\fP about HEADER.
+.UNINDENT
 .UNINDENT
-.SS 返値
-.SS json形式
-.sp
-.nf
-.ft C
-[成功かどうかのフラグ]
-
-\(ga\(ga成功かどうかのフラグ\(ga\(ga
-
-  エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
-.ft P
-.fi
-.SS 例
 .sp
-.nf
-.ft C
-table_remove Entry
-
-[true]
-.ft P
-.fi
+\fBSUCCEEDED_OR_NOT\fP
+.INDENT 0.0
+.INDENT 3.5
+If command succeeded, it returns true, otherwise it returns false on error.
+.UNINDENT
+.UNINDENT
 .SS データ型
 .SS 名前
 .sp
@@ -15607,6 +16224,43 @@ table_create NFKC51Lexicon TABLE_HASH_KEY ShortText \-\-normalizer NormalizerNFK
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 .ft P
 .fi
+.SS Additional normalizers
+.sp
+Here is a list of additional normalizers provided by \fBgroonga\-normalizer\-mysql\fP plugins:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fBNormalizerMySQLGeneralCI\fP
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+\fBgroonga\-normalizer\-mysql\fP is a groonga plugin.
+It provides MySQL compatible normalizers to groonga.
+\fBNormalizerMySQLGeneralCI\fP corresponds to \fButf8mb4_general_ci\fP.
+.sp
+You need to register \fBnormalizers/mysql\fP plugin in advance.
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+register normalizers/mysql
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.sp
+Here is an example that uses \fBNormalizerMySQLGeneralCI\fP normalizer:
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+table_create MySQLGeneralLexicon TABLE_HASH_KEY ShortText \-\-normalizer NormalizerMySQLGeneralCI
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
 .SS See also
 .INDENT 0.0
 .IP \(bu 2
@@ -20479,6 +21133,177 @@ Support options by object literal.
 .IP \(bu 2
 \fB/reference/commands/select\fP
 .UNINDENT
+.SS sub_filter
+.SS Summary
+.sp
+\fBsub_filter\fP evaluates \fBquery_string\fP in \fBmatch_column\fP context.
+.sp
+\fBsub_filter\fP can be used in only \fB\-\-filter\fP in \fB/reference/commands/select\fP.
+.SS Syntax
+.sp
+\fBsub_filter\fP requires two arguments \- \fBmatch_column\fP and \fBquery_string\fP.
+.sp
+.nf
+.ft C
+sub_filter(match_column, query_string)
+.ft P
+.fi
+.SS Usage
+.sp
+Here are a schema definition and sample data to show usage.
+.sp
+Sample schema:
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+table_create Comment TABLE_PAT_KEY UInt32
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Comment name COLUMN_SCALAR ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Comment content COLUMN_SCALAR ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+table_create Blog TABLE_PAT_KEY ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Blog title COLUMN_SCALAR ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Blog content COLUMN_SCALAR ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Blog comments COLUMN_VECTOR Comment
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Comment blog_comment_index COLUMN_INDEX Blog comments
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+table_create Lexicon TABLE_PAT_KEY ShortText \-\-default_tokenizer TokenBigram
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Lexicon comment_content COLUMN_INDEX|WITH_POSITION Comment content
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Lexicon comment_name COLUMN_INDEX|WITH_POSITION Comment name
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Lexicon blog_content COLUMN_INDEX|WITH_POSITION Blog content
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.sp
+Sample data:
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+load \-\-table Comment
+[
+{"_key": 1, "name": "A", "content": "groonga"},
+{"_key": 2, "name": "B", "content": "groonga"},
+{"_key": 3, "name": "C", "content": "rroonga"},
+{"_key": 4, "name": "A", "content": "mroonga"},
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 4]
+load \-\-table Blog
+[
+{"_key": "groonga\(aqs blog", "content": "content of groonga\(aqs blog", comments: [1, 2, 3]},
+{"_key": "mroonga\(aqs blog", "content": "content of mroonga\(aqs blog", comments: [2, 3, 4]},
+{"_key": "rroonga\(aqs blog", "content": "content of rroonga\(aqs blog", comments: [3]},
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 3]
+.ft P
+.fi
+.INDENT 0.0
+.TP
+.B Here is the simple usage of \fBsub_filter\fP function which extracts the blog entry
+user \(aqA\(aq commented out.
+.UNINDENT
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+select Blog \-\-output_columns _key \e
+  \-\-filter "comments.name @ \e"A\e" && comments.content @ \e"groonga\e""
+.ft P
+.fi
+.sp
+When executing above query, not only "groonga\(aqs blog", but also "mroonga\(aqs blog".
+This is not what you want because user "A" does not mention "groonga" to "mroonga\(aqs blog".
+.sp
+Without sub_filter, it means that following conditions are met.
+.INDENT 0.0
+.IP \(bu 2
+There is at least one record that user "A" commented out.
+.IP \(bu 2
+There is at least one record that mentioned about "groonga".
+.UNINDENT
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+select Blog \-\-output_columns _key \e
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   [
+#     [
+#       [
+#         2
+#       ],
+#       [
+#         [
+#           "_key",
+#           "ShortText"
+#         ]
+#       ],
+#       [
+#         "groonga\(aqs blog"
+#       ],
+#       [
+#         "mroonga\(aqs blog"
+#       ]
+#     ]
+#   ]
+# ]
+  \-\-filter \(aqsub_filter(comments, "name @ \e\e"A\e\e" && content @ \e\e"groonga\e\e"")\(aq
+.ft P
+.fi
+.sp
+On the other hand, executing above query returns the intended result.
+Because the arguments of sub_filter is evaluated in comments column\(aqs context.
+.sp
+It means that sub_filter requires following condition is met.
+.INDENT 0.0
+.IP \(bu 2
+There are the records that user "A" mentions about "groonga".
+.UNINDENT
+.SS Parameters
+.sp
+There are two required parameter, \fBmatch_column\fP and \fBquery_string\fP.
+.SS \fBmatch_column\fP
+.INDENT 0.0
+.INDENT 3.5
+It specifies \fBmatch_column\fP equivalent parameter.
+.UNINDENT
+.UNINDENT
+.sp
+See \fIselect\-match\-columns\fP about match_column.
+.SS \fBquery_string\fP
+.INDENT 0.0
+.INDENT 3.5
+It specifies \fBquery\fP equivalent parameter.
+.UNINDENT
+.UNINDENT
+.sp
+See \fIselect\-query\fP about query string.
+.SS Return value
+.sp
+\fBsub_filter\fP returns a value of boolean (true or false).
+.SS See also
+.INDENT 0.0
+.IP \(bu 2
+\fB/reference/commands/select\fP
+.UNINDENT
 .SS Indexing
 .sp
 Groonga supports both online index construction and offline
@@ -21853,6 +22678,17 @@ one of them to report a bug.
 Groonga project has \fB/community\fP for discussing about groonga.
 Please send a mail that describes a bug.
 .SS groonga開発者向け情報
+.SS Repository
+.sp
+There is \fI\%the repository of groonga on GitHub\fP. If you want to check\-out groonga, type the below command:
+.sp
+.nf
+.ft C
+% git clone git://github.com/groonga/groonga.git
+.ft P
+.fi
+.sp
+There is \fI\%the list of related projects of groonga\fP (grntest, fluent\-plugin\-groonga and so on).
 .SS groonga 通信アーキテクチャ
 .SS gqtpでのアーキテクチャ
 .INDENT 0.0
@@ -22957,6 +23793,17 @@ centosの場合、CENTOS_VERSIONSを指定することで特定のバージョ
 .sp
 パッケージの署名に必要な秘密鍵のパスフレーズについては
 リリース担当者向けの秘密鍵を復号したテキストの1行目に記載してあります。
+.SS バージョンを明示的に指定してドキュメントを生成したい
+.sp
+リリース後にドキュメントの一部を差し替えたい場合、特に何も指定しないと生成したHTMLに埋め込まれるバージョンが「v3.0.1\-xxxxxドキュメント」となってしまうことがあります。gitでのコミット時ハッシュの一部が使われるためです。
+.sp
+これを回避するには、以下のようにDOCUMENT_VERSIONやDOCUMENT_VERSION_FULLを明示的に指定します。:
+.sp
+.nf
+.ft C
+% make update\-document DOCUMENT_VERSION=3.0.1 DOCUMENT_VERSION_FULL=3.0.1
+.ft P
+.fi
 .SS テスト方法
 .SS テスト環境の構築
 .SS Cutterのインストール
@@ -23256,6 +24103,7 @@ Here are command lines to send pull request:
 Now you can send pull request on GitHub. You just access
 your repository page on GitHub and press \fIPull Request\fP
 button.
+.IP See also
 \fI\%Help.GitHub - Sending pull requests\fP.
 .RE
 .SS How to send patch
@@ -23291,6 +24139,7 @@ Here are command lines to add new translation language:
 .sp
 Please substitute \fI${LANGUAGE}\fP with your language code such
 as \(aqja\(aq.
+.IP See also
 \fI\%Codes for the Representation of Names of Languages\fP.
 .RE
 .INDENT 0.0