rroonga 3.1.1-x86-mingw32 → 3.1.2-x86-mingw32

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

@@ -1,4 +1,6 @@
-.TH "GROONGA" "1" "December 27, 2013" "3.1.1" "Groonga"
+.\" Man page generated from reStructuredText.
+.
+.TH "GROONGA" "1" "January 27, 2014" "3.1.2" "Groonga"
 .SH NAME
 groonga \- Groonga documentation
 .
@@ -28,8 +30,6 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
 ..
-.\" Man page generated from reStructuredText.
-.
 .INDENT 0.0
 .IP \(bu 2
 \fBnews\fP
@@ -41,7 +41,7 @@ Groonga is a fast and accurate full text search engine based on inverted index.
 .sp
 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
-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.
+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
 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.
@@ -110,7 +110,7 @@ packages.groonga.org:
 .INDENT 3.5
 .INDENT 0.0
 .IP \(bu 2
-\fI\%http://packages.groonga.org/windows/groonga/groonga\-3.1.1\-x86.exe\fP
+\fI\%http://packages.groonga.org/windows/groonga/groonga\-3.1.2\-x86.exe\fP
 .UNINDENT
 .UNINDENT
 .UNINDENT
@@ -123,7 +123,7 @@ packages.goronga.org:
 .INDENT 3.5
 .INDENT 0.0
 .IP \(bu 2
-\fI\%http://packages.groonga.org/windows/groonga/groonga\-3.1.1\-x64.exe\fP
+\fI\%http://packages.groonga.org/windows/groonga/groonga\-3.1.2\-x64.exe\fP
 .UNINDENT
 .UNINDENT
 .UNINDENT
@@ -131,7 +131,7 @@ packages.goronga.org:
 Then run it.
 .sp
 Use command prompt in start menu to run
-\fB/reference/executables/groonga\fP.
+\fB/reference/executables/groonga\fP\&.
 .SS zip
 .sp
 For 32\-bit environment, download x86 zip archive from
@@ -140,7 +140,7 @@ packages.groonga.org:
 .INDENT 3.5
 .INDENT 0.0
 .IP \(bu 2
-\fI\%http://packages.groonga.org/windows/groonga/groonga\-3.1.1\-x86.zip\fP
+\fI\%http://packages.groonga.org/windows/groonga/groonga\-3.1.2\-x86.zip\fP
 .UNINDENT
 .UNINDENT
 .UNINDENT
@@ -153,7 +153,7 @@ packages.groonga.org:
 .INDENT 3.5
 .INDENT 0.0
 .IP \(bu 2
-\fI\%http://packages.groonga.org/windows/groonga/groonga\-3.1.1\-x64.zip\fP
+\fI\%http://packages.groonga.org/windows/groonga/groonga\-3.1.2\-x64.zip\fP
 .UNINDENT
 .UNINDENT
 .UNINDENT
@@ -181,7 +181,7 @@ Download zipped source from packages.groonga.org:
 .INDENT 3.5
 .INDENT 0.0
 .IP \(bu 2
-\fI\%http://packages.groonga.org/source/groonga/groonga\-3.1.1.zip\fP
+\fI\%http://packages.groonga.org/source/groonga/groonga\-3.1.2.zip\fP
 .UNINDENT
 .UNINDENT
 .UNINDENT
@@ -194,13 +194,13 @@ Move to the Groonga\(aqs source folder:
 .sp
 .nf
 .ft C
-> cd c:\eUsers\e%USERNAME%\eDownloads\egroonga\-3.1.1
+> cd c:\eUsers\e%USERNAME%\eDownloads\egroonga\-3.1.2
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-Configure by \fBcmake\fP. The following commnad line is for 64\-bit
+Configure by \fBcmake\fP\&. The following commnad line is for 64\-bit
 version. To build 32\-bit version, use \fB\-G "Visual Studio 10"\fP
 parameter instead:
 .INDENT 0.0
@@ -208,7 +208,7 @@ parameter instead:
 .sp
 .nf
 .ft C
-groonga\-3.1.1> cmake . \-G "Visual Studio 10 Win64" \-DCMAKE_INSTALL_PREFIX=C:\egroonga
+groonga\-3.1.2> cmake . \-G "Visual Studio 10 Win64" \-DCMAKE_INSTALL_PREFIX=C:\egroonga
 .ft P
 .fi
 .UNINDENT
@@ -220,7 +220,7 @@ Build:
 .sp
 .nf
 .ft C
-groonga\-3.1.1> cmake \-\-build . \-\-config Release
+groonga\-3.1.2> cmake \-\-build . \-\-config Release
 .ft P
 .fi
 .UNINDENT
@@ -232,18 +232,18 @@ Install:
 .sp
 .nf
 .ft C
-groonga\-3.1.1> cmake \-\-build . \-\-config Release \-\-target Install
+groonga\-3.1.2> cmake \-\-build . \-\-config Release \-\-target Install
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
 After the above steps, \fB/reference/executables/groonga\fP is found in
-\fBc:\egroonga\ebin\egroonga.exe\fP.
+\fBc:\egroonga\ebin\egroonga.exe\fP\&.
 .SS Mac OS X
 .sp
 This section describes how to install groonga on Mac OS X. You can
-install groonga by \fI\%MacPorts\fP or \fI\%Homebrew\fP.
+install groonga by \fI\%MacPorts\fP or \fI\%Homebrew\fP\&.
 .sp
 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
@@ -278,7 +278,7 @@ Install:
 .UNINDENT
 .SS Build from source
 .sp
-Install \fI\%Xcode\fP.
+Install \fI\%Xcode\fP\&.
 .sp
 Download source:
 .INDENT 0.0
@@ -286,9 +286,9 @@ Download source:
 .sp
 .nf
 .ft C
-% curl \-O http://packages.groonga.org/source/groonga/groonga\-3.1.1.tar.gz
-% tar xvzf groonga\-3.1.1.tar.gz
-% cd groonga\-3.1.1
+% curl \-O http://packages.groonga.org/source/groonga/groonga\-3.1.2.tar.gz
+% tar xvzf groonga\-3.1.2.tar.gz
+% cd groonga\-3.1.2
 .ft P
 .fi
 .UNINDENT
@@ -331,8 +331,8 @@ Install:
 .UNINDENT
 .SS Debian GNU/Linux
 .sp
-This section describes how to install groonga related deb packages on
-Debian GNU/Linux. You can install them by \fBapt\fP.
+This section describes how to install Groonga related deb packages on
+Debian GNU/Linux. You can install them by \fBapt\fP\&.
 .sp
 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
@@ -362,7 +362,7 @@ See \fB/server\fP section about details.
 .UNINDENT
 .SS wheezy
 .sp
-Add the groonga apt repository.
+Add the Groonga apt repository.
 .sp
 /etc/apt/sources.list.d/groonga.list:
 .INDENT 0.0
@@ -500,7 +500,7 @@ Install groonga\-munin\-plugins package:
 .UNINDENT
 .sp
 There is a package that provides MySQL compatible normalizer as
-groonga plugins.
+Groonga plugins.
 If you want to use that one, install groonga\-normalizer\-mysql package.
 .sp
 Install groonga\-normalizer\-mysql package:
@@ -611,9 +611,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-3.1.1.tar.gz
-% tar xvzf groonga\-3.1.1.tar.gz
-% cd groonga\-3.1.1
+% wget http://packages.groonga.org/source/groonga/groonga\-3.1.2.tar.gz
+% tar xvzf groonga\-3.1.2.tar.gz
+% cd groonga\-3.1.2
 .ft P
 .fi
 .UNINDENT
@@ -656,8 +656,8 @@ Install:
 .UNINDENT
 .SS Ubuntu
 .sp
-This section describes how to install groonga related deb packages on
-Ubuntu. You can install them by \fBapt\fP.
+This section describes how to install Groonga related deb packages on
+Ubuntu. You can install them by \fBapt\fP\&.
 .sp
 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
@@ -705,7 +705,7 @@ Enable the universe repository to install groonga:
 .UNINDENT
 .UNINDENT
 .sp
-Add the groonga apt repository.
+Add the Groonga apt repository.
 .sp
 /etc/apt/sources.list.d/groonga.list:
 .INDENT 0.0
@@ -766,7 +766,7 @@ Install groonga\-munin\-plugins package:
 .UNINDENT
 .sp
 There is a package that provides MySQL compatible normalizer as
-groonga plugins.
+Groonga plugins.
 If you want to use that one, install groonga\-normalizer\-mysql package.
 .sp
 Install groonga\-normalizer\-mysql package:
@@ -800,7 +800,7 @@ Enable the universe repository to install groonga:
 .UNINDENT
 .UNINDENT
 .sp
-Add the groonga apt repository.
+Add the Groonga apt repository.
 .sp
 /etc/apt/sources.list.d/groonga.list:
 .INDENT 0.0
@@ -846,7 +846,7 @@ Install groonga\-tokenizer\-mecab package:
 .UNINDENT
 .sp
 There is a package that provides \fI\%Munin\fP plugins. If you want to monitor
-groonga status by Munin, install groonga\-munin\-plugins package.
+Groonga status by Munin, install groonga\-munin\-plugins package.
 .sp
 Install groonga\-munin\-plugins package:
 .INDENT 0.0
@@ -861,7 +861,7 @@ Install groonga\-munin\-plugins package:
 .UNINDENT
 .sp
 There is a package that provides MySQL compatible normalizer as
-groonga plugins.
+Groonga plugins.
 If you want to use that one, install groonga\-normalizer\-mysql package.
 .sp
 Install groonga\-normalizer\-mysql package:
@@ -895,7 +895,7 @@ Enable the universe repository to install groonga:
 .UNINDENT
 .UNINDENT
 .sp
-Add the groonga apt repository.
+Add the Groonga apt repository.
 .sp
 /etc/apt/sources.list.d/groonga.list:
 .INDENT 0.0
@@ -1067,9 +1067,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-3.1.1.tar.gz
-% tar xvzf groonga\-3.1.1.tar.gz
-% cd groonga\-3.1.1
+% wget http://packages.groonga.org/source/groonga/groonga\-3.1.2.tar.gz
+% tar xvzf groonga\-3.1.2.tar.gz
+% cd groonga\-3.1.2
 .ft P
 .fi
 .UNINDENT
@@ -1113,7 +1113,7 @@ Install:
 .SS CentOS
 .sp
 This section describes how to install groonga related RPM packages on
-CentOS. You can install them by \fByum\fP.
+CentOS. You can install them by \fByum\fP\&.
 .sp
 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
@@ -1199,7 +1199,7 @@ Or install Juman dictionary:
 .UNINDENT
 .sp
 There is a package that provides \fI\%Munin\fP plugins. If you want to monitor
-groonga status by Munin, install groonga\-munin\-plugins package.
+Groonga status by Munin, install groonga\-munin\-plugins package.
 .sp
 \fBNOTE:\fP
 .INDENT 0.0
@@ -1208,7 +1208,7 @@ Groonga\-munin\-plugins package requires munin\-node package that
 isn\(aqt included in the official CentOS repository. You need to
 enable \fI\%Repoforge (RPMforge)\fP repository
 or \fI\%EPEL\fP repository to
-install it by \fByum\fP.
+install it by \fByum\fP\&.
 .sp
 Enable Repoforge (RPMforge) repository on i386 environment:
 .INDENT 0.0
@@ -1264,7 +1264,7 @@ Install groonga\-munin\-plugins package:
 .UNINDENT
 .sp
 There is a package that provides MySQL compatible normalizer as
-groonga plugins.
+Groonga plugins.
 If you want to use that one, install groonga\-normalizer\-mysql package.
 .sp
 Install groonga\-normalizer\-mysql package:
@@ -1336,7 +1336,7 @@ Or install Juman dictionary:
 .UNINDENT
 .sp
 There is a package that provides \fI\%Munin\fP plugins. If you want to monitor
-groonga status by Munin, install groonga\-munin\-plugins package.
+Groonga status by Munin, install groonga\-munin\-plugins package.
 .sp
 \fBNOTE:\fP
 .INDENT 0.0
@@ -1344,7 +1344,7 @@ groonga status by Munin, install groonga\-munin\-plugins package.
 Groonga\-munin\-plugins package requires munin\-node package that
 isn\(aqt included in the official CentOS repository. You need to
 enable \fI\%EPEL\fP repository to
-install it by \fByum\fP.
+install it by \fByum\fP\&.
 .sp
 Enable EPEL repository on any environment:
 .INDENT 0.0
@@ -1373,7 +1373,7 @@ Install groonga\-munin\-plugins package:
 .UNINDENT
 .sp
 There is a package that provides MySQL compatible normalizer as
-groonga plugins.
+Groonga plugins.
 If you want to use that one, install groonga\-normalizer\-mysql package.
 .sp
 Install groonga\-normalizer\-mysql package:
@@ -1407,9 +1407,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-3.1.1.tar.gz
-% tar xvzf groonga\-3.1.1.tar.gz
-% cd groonga\-3.1.1
+% wget http://packages.groonga.org/source/groonga/groonga\-3.1.2.tar.gz
+% tar xvzf groonga\-3.1.2.tar.gz
+% cd groonga\-3.1.2
 .ft P
 .fi
 .UNINDENT
@@ -1453,12 +1453,12 @@ Install:
 .SS Fedora
 .sp
 This section describes how to install groonga related RPM packages on
-Fedora. You can install them by \fByum\fP.
+Fedora. You can install them by \fByum\fP\&.
 .sp
 \fBNOTE:\fP
 .INDENT 0.0
 .INDENT 3.5
-Since groonga 3.0.2 release, Groonga related RPM pakcages are in the official
+Since Groonga 3.0.2 release, Groonga related RPM pakcages are in the official
 Fedora yum repository (Fedora 18). So you can use them instead of the groonga yum
 repository now. There is some exceptions to use the groonga yum
 repository because \fBgroonga\-normalizer\-mysql\fP and mecab dictionaries
@@ -1565,7 +1565,7 @@ Or install Juman dictionary:
 .UNINDENT
 .sp
 There is a package that provides \fI\%Munin\fP plugins. If you want to monitor
-groonga status by Munin, install groonga\-munin\-plugins package.
+Groonga status by Munin, install groonga\-munin\-plugins package.
 .sp
 Install groonga\-munin\-plugins package:
 .INDENT 0.0
@@ -1580,7 +1580,7 @@ Install groonga\-munin\-plugins package:
 .UNINDENT
 .sp
 There is a package that provides MySQL compatible normalizer as
-groonga plugins.
+Groonga plugins.
 If you want to use that one, install groonga\-normalizer\-mysql package.
 .sp
 Install groonga\-normalizer\-mysql package:
@@ -1614,9 +1614,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-3.1.1.tar.gz
-% tar xvzf groonga\-3.1.1.tar.gz
-% cd groonga\-3.1.1
+% wget http://packages.groonga.org/source/groonga/groonga\-3.1.2.tar.gz
+% tar xvzf groonga\-3.1.2.tar.gz
+% cd groonga\-3.1.2
 .ft P
 .fi
 .UNINDENT
@@ -1659,7 +1659,7 @@ Install:
 .UNINDENT
 .SS Oracle Solaris
 .sp
-This section describes how to install groonga from source on Oracle
+This section describes how to install Groonga from source on Oracle
 Solaris.
 .SS Oracle Solaris 11
 .sp
@@ -1681,9 +1681,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-3.1.1.tar.gz
-% gtar xvzf groonga\-3.1.1.tar.gz
-% cd groonga\-3.1.1
+% wget http://packages.groonga.org/source/groonga/groonga\-3.1.2.tar.gz
+% gtar xvzf groonga\-3.1.2.tar.gz
+% cd groonga\-3.1.2
 .ft P
 .fi
 .UNINDENT
@@ -1734,7 +1734,7 @@ environment.
 .sp
 To get more detail about installing groonga from source on the
 specific environment, find the document for the specific environment
-from \fB/install\fP.
+from \fB/install\fP\&.
 .SS Dependencies
 .sp
 Groonga doesn\(aqt require any special libraries but requires some tools
@@ -1823,9 +1823,9 @@ steps:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-3.1.1.tar.gz
-% tar xvzf groonga\-3.1.1.tar.gz
-% cd groonga\-3.1.1
+% wget http://packages.groonga.org/source/groonga/groonga\-3.1.2.tar.gz
+% tar xvzf groonga\-3.1.2.tar.gz
+% cd groonga\-3.1.2
 % ./configure
 % make
 % sudo make install
@@ -1835,7 +1835,7 @@ steps:
 .UNINDENT
 .sp
 After the above steps, \fB/reference/executables/groonga\fP is found in
-\fB/usr/local/bin/groonga\fP.
+\fB/usr/local/bin/groonga\fP\&.
 .sp
 The default build will work well but you can customize groonga at
 \fBconfigure\fP step.
@@ -1843,15 +1843,15 @@ The default build will work well but you can customize groonga at
 The following describes details about each step.
 .SS \fBconfigure\fP
 .sp
-First, you need to run \fBconfigure\fP. Here are important \fBconfigure\fP
+First, you need to run \fBconfigure\fP\&. Here are important \fBconfigure\fP
 options:
 .SS \fB\-\-prefix=PATH\fP
 .sp
 Specifies the install base directory. Groonga related files are
 installed under \fB${PATH}/\fP directory.
 .sp
-The default is \fB/usr/local\fP. In this case, \fB/reference/executables/groonga\fP is
-installed into \fB/usr/local/bin/groonga\fP.
+The default is \fB/usr/local\fP\&. In this case, \fB/reference/executables/groonga\fP is
+installed into \fB/usr/local/bin/groonga\fP\&.
 .sp
 Here is an example that installs groonga into \fB~/local\fP for an user
 use instead of system wide use:
@@ -1869,9 +1869,9 @@ use instead of system wide use:
 .sp
 Specifies the base directory to place modifiable file such as log
 file, PID file and database files. For example, log file is placed at
-\fB${PATH}/log/groonga.log\fP.
+\fB${PATH}/log/groonga.log\fP\&.
 .sp
-The default is \fB/usr/local/var\fP.
+The default is \fB/usr/local/var\fP\&.
 .sp
 Here is an example that system wide \fB/var\fP is used for modifiable
 files:
@@ -1892,7 +1892,7 @@ path is \fB/reference/executables/groonga\fP command\(aqs \fB\-\-log\-path\fP
 command line option. So this option is not critical build option. It\(aqs
 just for convenient.
 .sp
-The default is \fB/usr/local/var/log/groonga.log\fP. The
+The default is \fB/usr/local/var/log/groonga.log\fP\&. The
 \fB/usr/local/var\fP part is changed by \fB\-\-localestatedir\fP option.
 .sp
 Here is an example that log file is placed into shared NFS directory
@@ -1910,9 +1910,9 @@ Here is an example that log file is placed into shared NFS directory
 .SS \fB\-\-with\-default\-encoding=ENCODING\fP
 .sp
 Specifies the default encoding. Available encodings are \fBeuc_jp\fP,
-\fBsjis\fP, \fButf8\fP, \fBlatin1\fP, \fBkoi8r\fP and \fBnone\fP.
+\fBsjis\fP, \fButf8\fP, \fBlatin1\fP, \fBkoi8r\fP and \fBnone\fP\&.
 .sp
-The default is \fButf\-8\fP.
+The default is \fButf\-8\fP\&.
 .sp
 Here is an example that Shift_JIS is used as the default encoding:
 .INDENT 0.0
@@ -1966,7 +1966,7 @@ Here is an example that enables column value compression by zlib:
 .INDENT 0.0
 .INDENT 3.5
 The disabled reason is that memory leak occurs when it refers column value.
-This is already known issue as \fI\%GitHub#6\fP.
+This is already known issue as \fI\%GitHub#6\fP\&.
 This issue is not nothing to do with updating column value.
 .UNINDENT
 .UNINDENT
@@ -1992,7 +1992,7 @@ Here is an example that enables column value compression by LZO:
 .INDENT 0.0
 .INDENT 3.5
 The disabled reason is that memory leak occurs when it refers column value.
-This is already known issue as \fI\%GitHub#6\fP.
+This is already known issue as \fI\%GitHub#6\fP\&.
 This issue is not nothing to do with updating column value.
 .UNINDENT
 .UNINDENT
@@ -2004,9 +2004,9 @@ path that you use for building MessagePack.
 .sp
 If you installed MessagePack with \fB\-\-prefix=$HOME/local\fP option, you
 sholud specify \fB\-\-with\-message\-pack=$HOME/local\fP to groonga\(aqs
-\fBconfigure\fP.
+\fBconfigure\fP\&.
 .sp
-The default is \fB/usr\fP.
+The default is \fB/usr\fP\&.
 .sp
 Here is an example that uses MessagePack built with
 \fB\-\-prefix=$HOME/local\fP option:
@@ -2023,7 +2023,7 @@ Here is an example that uses MessagePack built with
 .SS \fB\-\-with\-munin\-plugins\fP
 .sp
 Installs Munin plugins for groonga. They are installed into
-\fB${PREFIX}/share/groonga/munin/plugins/\fP.
+\fB${PREFIX}/share/groonga/munin/plugins/\fP\&.
 .sp
 Those plugins are not installed by default.
 .sp
@@ -2041,7 +2041,7 @@ Here is an example that installs Munin plugins for groonga:
 .SS \fB\-\-with\-package\-platform=PLATFORM\fP
 .sp
 Installs platform specific system management files such as init
-script. Available platforms are \fBredhat\fP and \fBfedora\fP. \fBredhat\fP
+script. Available platforms are \fBredhat\fP and \fBfedora\fP\&. \fBredhat\fP
 is for Red Hat and Red Hat clone distributions such as
 CentOS. \fBfedora\fP is for Fedora.
 .sp
@@ -2106,7 +2106,7 @@ Now, you can install built groonga!:
 .UNINDENT
 .sp
 If you have write permission for \fB${PREFIX}\fP, you don\(aqt need to use
-\fBsudo\fP. e.g. \fB\-\-prefix=$HOME/local\fP case. In this case, use \fBmake
+\fBsudo\fP\&. e.g. \fB\-\-prefix=$HOME/local\fP case. In this case, use \fBmake
 install\fP:
 .INDENT 0.0
 .INDENT 3.5
@@ -2259,7 +2259,7 @@ In the second form, you can specify a parameter name with its value. So, the ord
 .sp
 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 details, see also the paragraph of "command" in \fB/reference/executables/groonga\fP.
+For details, see also the paragraph of "command" in \fB/reference/executables/groonga\fP\&.
 .SS Basic commands
 .INDENT 0.0
 .INDENT 3.5
@@ -3572,7 +3572,7 @@ select \-\-table Site \-\-query title:@this
 .UNINDENT
 .SS Administration tool (HTTP)
 .sp
-An HTTP server of Groonga provides a browser based administration tool that makes database management easy. After starting an HTTP server, you can use the administration tool by accessing \fI\%http://HOST_NAME_OR_IP_ADDRESS[:PORT_NUMBER]/\fP. Note that Javascript must be enabled for the tool to work properly.
+An HTTP server of Groonga provides a browser based administration tool that makes database management easy. After starting an HTTP server, you can use the administration tool by accessing \fI\%http://HOST_NAME_OR_IP_ADDRESS[:PORT_NUMBER]/\fP\&. Note that Javascript must be enabled for the tool to work properly.
 .SS Security issues
 .sp
 Groonga servers don\(aqt support user authentication. Everyone can view and modify databases hosted by Groonga servers. You are recommended to restrict IP addresses that can access Groonga servers. You can use iptables or similar for this purpose.
@@ -3581,7 +3581,7 @@ Groonga servers don\(aqt support user authentication. Everyone can view and modi
 Groonga is a full text search engine but also serves as a column\-oriented data store. Groonga supports various data types, such as numeric types, string types, date and time type, longitude and latitude types, etc. This tutorial shows a list of data types and explains how to use them.
 .SS Overview
 .sp
-The basic data types of Groonga are roughly divided into 5 groups \-\-\- boolean type, numeric types, string types, date/time type and longitude/latitude types. The numeric types are further divided according to whether integer or floating point number, signed or unsigned and the number of bits allocated to each integer. The string types are further divided according to the maximum length. The longitude/latitude types are further divided according to the geographic coordinate system. For more details, see \fB/reference/types\fP.
+The basic data types of Groonga are roughly divided into 5 groups \-\-\- boolean type, numeric types, string types, date/time type and longitude/latitude types. The numeric types are further divided according to whether integer or floating point number, signed or unsigned and the number of bits allocated to each integer. The string types are further divided according to the maximum length. The longitude/latitude types are further divided according to the geographic coordinate system. For more details, see \fB/reference/types\fP\&.
 .sp
 In addition, Groonga supports reference types and vector types. Reference types are designed for accessing other tables. Vector types are designed for storing a variable number of values in one element.
 .sp
@@ -3663,7 +3663,7 @@ select \-\-table ToyBox \-\-output_columns _key,is_animal
 .UNINDENT
 .SS Numeric types
 .sp
-The numeric types are divided into integer types and a floating point number type. The integer types are further divided into the signed integer types and unsigned integer types. In addition, you can choose the number of bits allocated to each integer. For more details, see \fB/reference/types\fP. The default value of the numeric types is 0.
+The numeric types are divided into integer types and a floating point number type. The integer types are further divided into the signed integer types and unsigned integer types. In addition, you can choose the number of bits allocated to each integer. For more details, see \fB/reference/types\fP\&. The default value of the numeric types is 0.
 .sp
 The following example creates an Int8 column and a Float column, and then updates existing records. The \fB/reference/commands/load\fP command updates the weight column as expected. On the other hand, the price column values are different from the specified values because 15.9 is not an integer and 200 is too large. 15.9 is converted to 15 by removing the fractional part. 200 causes an overflow and the result becomes \-56. Note that the result of an overflow/underflow is undefined.
 .sp
@@ -3734,7 +3734,7 @@ select \-\-table ToyBox \-\-output_columns _key,price,weight
 .UNINDENT
 .SS String types
 .sp
-The string types are divided according to the maximum length. For more details, see \fB/reference/types\fP. The default value is the zero\-length string.
+The string types are divided according to the maximum length. For more details, see \fB/reference/types\fP\&. The default value is the zero\-length string.
 .sp
 The following example creates a ShortText column and updates existing records. The third record has the default value because not updated.
 .sp
@@ -3864,7 +3864,7 @@ select \-\-table ToyBox \-\-output_columns _key,time
 .UNINDENT
 .SS Longitude and latitude types
 .sp
-The longitude and latitude types are divided according to the geographic coordinate system. For more details, see \fB/reference/types\fP. To represent a longitude and latitude, Groonga uses a string formatted as follows:
+The longitude and latitude types are divided according to the geographic coordinate system. For more details, see \fB/reference/types\fP\&. To represent a longitude and latitude, Groonga uses a string formatted as follows:
 .INDENT 0.0
 .IP \(bu 2
 "longitude x latitude" in milliseconds (e.g.: "128452975x503157902")
@@ -4641,7 +4641,7 @@ As you know, there is a naive solution to execute query by every the value of co
 .sp
 If you are familiar with SQL, you will doubt with "Is there a similar SQL functionality to \fBGROUP BY\fP in Groonga?".
 .sp
-Of course, Groonga provides such a functionality. It\(aqs called as \fBdrilldown\fP.
+Of course, Groonga provides such a functionality. It\(aqs called as \fBdrilldown\fP\&.
 .sp
 \fBdrilldown\fP enables you to get the number of records which belongs to specific the value of column at once.
 .sp
@@ -4787,7 +4787,7 @@ Group records means following records
 T}
 _
 T{
-.org
+\&.org
 T}	T{
 3
 T}	T{
@@ -4802,7 +4802,7 @@ T}	T{
 T}
 _
 T{
-.net
+\&.net
 T}	T{
 3
 T}	T{
@@ -4817,7 +4817,7 @@ T}	T{
 T}
 _
 T{
-.com
+\&.com
 T}	T{
 3
 T}	T{
@@ -7951,7 +7951,7 @@ select Doc \-\-match_columns body \-\-query "シークヮーサー" \-\-query_ex
 Groonga has the suggest feature. This section describes how to use it and how it works.
 .SS Introduction
 .sp
-The suggest feature in groonga provides the following features:
+The suggest feature in Groonga provides the following features:
 .INDENT 0.0
 .IP \(bu 2
 Completion
@@ -7963,7 +7963,7 @@ Suggestion
 .SS Completion
 .sp
 Completion helps user input. If user inputs a partial word,
-groonga can return complete words from registered
+Groonga can return complete words from registered
 words.
 .sp
 For example, there are registered words:
@@ -9165,7 +9165,7 @@ If you use \fBgroonga\-httpd\fP package, you can also take benefits of nginx fun
 .sp
 We recommend to use \fBgroonga\-server\-http\fP at first, then if you want to use more
 fullfilling functionality, use \fBgroonga\-httpd\fP package. If you have performance issues which
-is derived from protocol overheads, consider to use \fBgroonga\-server\-gqtp\fP.
+is derived from protocol overheads, consider to use \fBgroonga\-server\-gqtp\fP\&.
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -9580,7 +9580,7 @@ Restarting groonga HTTP server(Fedora):
 .sp
 TODO
 .sp
-See \fB/reference/executables/groonga\fP.
+See \fB/reference/executables/groonga\fP\&.
 .SS HTTP
 .sp
 Groonga provides two HTTP server implementations.
@@ -9607,7 +9607,7 @@ implementation. It is also fast and has many HTTP features.
 .SS Comparison
 .sp
 There are many differences between \fBgroonga\fP and
-\fBgroonga\-httpd\fP. Here is a comparison table.
+\fBgroonga\-httpd\fP\&. Here is a comparison table.
 .TS
 center;
 |l|l|l|.
@@ -9795,8 +9795,8 @@ http {
 .SS Custom prefix path
 .sp
 \fBgroonga\fP accepts a path that starts with \fB/d/\fP as command URL
-such as \fBhttp://localhost:10041/d/status\fP. You cannot change the
-prefix path \fB/d/\fP.
+such as \fBhttp://localhost:10041/d/status\fP\&. You cannot change the
+prefix path \fB/d/\fP\&.
 .sp
 \fBgroonga\-httpd\fP can custom prefix path. For example, you can use
 \fBhttp://localhost:10041/api/status\fP as command URL. Here is a sample
@@ -9915,7 +9915,7 @@ http {
 .sp
 HTTP supports authentications such as basic authentication and digest
 authentication. It can be used for restricting use of danger command such
-as \fB/reference/commands/shutdown\fP.
+as \fB/reference/commands/shutdown\fP\&.
 .sp
 \fBgroonga\fP doesn\(aqt support any authentications. To restrict use of
 danger command, other tools such as iptables and reverse proxy are
@@ -9994,7 +9994,7 @@ Note that \fIgzip_types *\fP is specified. It\(aqs one of the important
 configuration. \fIgzip_types\fP specifies gzip target data formats by MIME
 types. \fBgroonga\-httpd\fP returns one of JSON, XML or MessagePack
 format data. But those formats aren\(aqt included in the default value of
-\fIgzip_types\fP. The default value of \fIgzip_types\fP is \fItext/html\fP.
+\fIgzip_types\fP\&. The default value of \fIgzip_types\fP is \fItext/html\fP\&.
 .sp
 To compress response data from \fBgroonga\-httpd\fP by gzip, you need
 to specify \fIgzip_types *\fP or \fIgzip_types application/json text/xml
@@ -10008,11 +10008,11 @@ You can load your data by POST JSON data. You need follow the
 following rules to use loading by POST.
 .INDENT 0.0
 .IP \(bu 2
-\fIContent\-Type\fP header value must be \fIapplication/json\fP.
+\fIContent\-Type\fP header value must be \fIapplication/json\fP\&.
 .IP \(bu 2
 JSON data is sent as body.
 .IP \(bu 2
-Table name is specified by query parameter such as \fBtable=NAME\fP.
+Table name is specified by query parameter such as \fBtable=NAME\fP\&.
 .UNINDENT
 .sp
 Here is an example curl command line that loads two users \fIalice\fP and
@@ -10065,7 +10065,7 @@ grnslap [options] [dest]
 .sp
 grnslapは、groongaプロセスに対してリクエストを多重に行い、パフォーマンスをチェックするためのツールです。
 .sp
-groonga独自プロトコルであるgqtpと、httpの両プロトコルでリクエストを行うことができます。また、リクエストの多重度を指定することができます。
+Groonga独自プロトコルであるGQTPと、httpの両プロトコルでリクエストを行うことができます。また、リクエストの多重度を指定することができます。
 .sp
 クエリの内容を標準入力から与えることができます。実稼動環境でのクエリパタンに近いクエリを標準入力に与えることによって、実稼動環境に近い状態での検証を行うことができます。
 .sp
@@ -10133,8 +10133,8 @@ groonga [options] [dest] [command [args]]
 .UNINDENT
 .SS 説明
 .sp
-groongaは列指向のデータベース機能を持つ高速でスケーラブルな全文検索エンジンです。
-groongaのデータベースは、groongaコマンドかCライブラリインタフェースを通して操作することができます。このマニュアルページでは、groongaコマンドの使い方について説明します。
+Groongaは列指向のデータベース機能を持つ高速でスケーラブルな全文検索エンジンです。
+Groongaのデータベースは、groongaコマンドかCライブラリインタフェースを通して操作することができます。このマニュアルページでは、groongaコマンドの使い方について説明します。
 .SS オプション
 .INDENT 0.0
 .TP
@@ -10777,13 +10777,13 @@ groonga サーバが動作していないか？　groonga\-benchmarkは、\-i, \
 .sp
 groonga\-httpd is a program to communicate with a groonga server using
 the HTTP protocol. It functions as same as
-\fBgroonga\-server\-http\fP. Although \fBgroonga\-server\-http\fP has
+\fBgroonga\-server\-http\fP\&. Although \fBgroonga\-server\-http\fP has
 limited support for HTTP with a minimal built\-in HTTP server,
-groonga\-httpd has full support for HTTP with an embedded \fI\%nginx\fP. All standards\-compliance and features provided
+groonga\-httpd has full support for HTTP with an embedded \fI\%nginx\fP\&. All standards\-compliance and features provided
 by nginx is also available in groonga\-httpd.
 .sp
 groonga\-httpd has an Web\-based administration tool implemented with HTML and
-JavaScript. You can access to it from \fI\%http://hostname:port/\fP.
+JavaScript. You can access to it from \fI\%http://hostname:port/\fP\&.
 .SS Synopsis
 .INDENT 0.0
 .INDENT 3.5
@@ -10873,7 +10873,7 @@ Execution example:
 .UNINDENT
 .SS Browse the administration tool
 .sp
-Also, you can browse Web\-based administration tool at \fI\%http://localhost:10041/\fP.
+Also, you can browse Web\-based administration tool at \fI\%http://localhost:10041/\fP\&.
 .SS Shut down
 .sp
 Finally, to terminate the running groonga\-httpd daemon, run this:
@@ -10921,7 +10921,7 @@ groonga on | off;
 .UNINDENT
 .sp
 Specifies whether groonga is enabled in the \fBlocation\fP block. The
-default is \fBoff\fP. You need to specify \fBon\fP to enable groonga.
+default is \fBoff\fP\&. You need to specify \fBon\fP to enable groonga.
 .sp
 Examples:
 .INDENT 0.0
@@ -10995,7 +10995,7 @@ nothing.
 If parent directory doesn\(aqt exist, parent directory is also created
 recursively.
 .sp
-The default value is \fBon\fP. Normally, the value doesn\(aqt need to be
+The default value is \fBon\fP\&. Normally, the value doesn\(aqt need to be
 changed.
 .SS \fBgroonga_base_path\fP
 .sp
@@ -11020,7 +11020,7 @@ The same value as \fBlocation\fP name.
 .UNINDENT
 .sp
 Specifies the base path in URI. groonga uses
-\fB/d/command?parameter1=value1&...\fP path to run \fBcommand\fP. The form
+\fB/d/command?parameter1=value1&...\fP path to run \fBcommand\fP\&. The form
 of path in used in groonga\-httpd but groonga\-httpd also supports
 \fB/other\-prefix/command?parameter1=value1&...\fP form. To support the
 form, groonga\-httpd removes the base path from the head of request URI
@@ -11083,8 +11083,8 @@ groonga_log_path path | off;
 .UNINDENT
 .sp
 Specifies groonga log path in the \fBhttp\fP, \fBserver\fP or \fBlocation\fP block. The
-default is \fB/var/log/groonga/httpd/groonga.log\fP.
-You can disable logging to specify \fBoff\fP.
+default is \fB/var/log/groonga/httpd/groonga.log\fP\&.
+You can disable logging to specify \fBoff\fP\&.
 .sp
 Examples:
 .INDENT 0.0
@@ -11124,7 +11124,7 @@ groonga_log_level none | emergency | alert | ciritical | error | warning | notic
 .UNINDENT
 .sp
 Specifies groonga log level in the \fBhttp\fP, \fBserver\fP or \fBlocation\fP block. The
-default is \fBnotice\fP. You can disable logging by specifying \fBnone\fP as log level.
+default is \fBnotice\fP\&. You can disable logging by specifying \fBnone\fP as log level.
 .sp
 Examples:
 .INDENT 0.0
@@ -11165,8 +11165,8 @@ groonga_query_log_path path | off;
 .sp
 Specifies groonga\(aqs query log path in the \fBhttp\fP, \fBserver\fP or
 \fBlocation\fP block. The default is
-\fB/var/log/groonga/httpd/groonga\-query.log\fP.  You can disable logging
-to specify \fBoff\fP.
+\fB/var/log/groonga/httpd/groonga\-query.log\fP\&.  You can disable logging
+to specify \fBoff\fP\&.
 .sp
 Examples:
 .INDENT 0.0
@@ -11196,7 +11196,7 @@ Debugging.
 .UNINDENT
 .UNINDENT
 .sp
-You can analyze your query log by \fI\%groonga\-query\-log package\fP. The package provides
+You can analyze your query log by \fI\%groonga\-query\-log package\fP\&. The package provides
 useful tools.
 .sp
 For example, there is a tool that analyzing your query log. It can
@@ -11213,7 +11213,7 @@ many cases, groonga queries may be CPU\-intensive work, so to fully utilize
 multi\-CPU/core systems, it\(aqs essential to set this accordingly.
 .sp
 This isn\(aqt a groonga\-httpd specific directive, but an nginx\(aqs one. For details,
-see \fI\%http://wiki.nginx.org/CoreModule#worker_processes\fP.
+see \fI\%http://wiki.nginx.org/CoreModule#worker_processes\fP\&.
 .sp
 By default, this is set to 1. It is nginx\(aqs default.
 .SS \fBgroonga_cache_limit\fP
@@ -11432,7 +11432,7 @@ cache by hand. It is done automatically.
 All standard HTTP modules are available. HttpRewriteModule is
 disabled when you don\(aqt have PCRE (Perl Compatible Regular
 Expressions). For the list of standard HTTP modules, see
-\fI\%http://wiki.nginx.org/Modules\fP.
+\fI\%http://wiki.nginx.org/Modules\fP\&.
 .SS groonga HTTPサーバー
 .SS 名前
 .sp
@@ -11509,9 +11509,9 @@ groonga\-suggest\-create\-dataset [options] DATABASE DATASET
 .UNINDENT
 .SS DESCTIPION
 .sp
-groonga\-suggest\-create\-dataset creates a dataset for \fB/suggest\fP. A database has many datasets. This command just defines schema for a suggestion dataset.
+groonga\-suggest\-create\-dataset creates a dataset for \fB/suggest\fP\&. A database has many datasets. This command just defines schema for a suggestion dataset.
 .sp
-This command generates some tables and columns for \fB/suggest\fP.
+This command generates some tables and columns for \fB/suggest\fP\&.
 .sp
 Here is the list of such tables. If you specify \(aqquery\(aq as dataset name, following \(aq_DATASET\(aq suffix are replaced. Thus, \(aqitem_query\(aq, \(aqpair_query\(aq, \(aqsequence_query\(aq, \(aqevent_query\(aq tables are generated.
 .INDENT 0.0
@@ -11610,7 +11610,7 @@ Specify this option to disable checking max fd on start.
 .UNINDENT
 .SS Parameters
 .sp
-There is one required parameter \- \fBdatabase_path\fP.
+There is one required parameter \- \fBdatabase_path\fP\&.
 .SS \fBdatabase_path\fP
 .sp
 Specifies the path to a groonga database.
@@ -11637,7 +11637,7 @@ TODO
 TODO
 .SS Parameters
 .sp
-There is one required parameter \- \fBdatabase_path\fP.
+There is one required parameter \- \fBdatabase_path\fP\&.
 .SS \fBdatabase_path\fP
 .sp
 Specifies the path to a groonga database.
@@ -11678,7 +11678,7 @@ 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
+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
@@ -11785,7 +11785,7 @@ get a result in MessagePack format:
 .SS HTTP
 .sp
 You can use HTTP query interface by \fBgroonga \-\-protocol
-http \-s DB_PATH\fP. Groonga HTTP server starts on port 10041
+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
@@ -12133,7 +12133,7 @@ The following part is \fBBODY\fP:
 .UNINDENT
 .UNINDENT
 .sp
-The first element is always \fB0\fP.
+The first element is always \fB0\fP\&.
 .sp
 \fBUNIX_TIME_WHEN_COMMAND_IS_STARTED\fP is the number of seconds
 since 1970\-01\-01 00:00:00 UTC when the command is started
@@ -12242,7 +12242,7 @@ array. \fBLOCATION_IN_GROONGA\fP has three elements:
 is occurred.
 .sp
 \fBLINE_CONTENT\fP is the content at \fBLINE_NUMBER\fP in
-\fBINPUT_FILE_NAME\fP.
+\fBINPUT_FILE_NAME\fP\&.
 .SS \fBBODY\fP
 .sp
 \fBBODY\fP content depends on the executed command. It may be omitted.
@@ -12525,7 +12525,7 @@ max number of query cache entries.
 \fBHEADER\fP
 .INDENT 0.0
 .INDENT 3.5
-See \fB/reference/command/output_format\fP about \fBHEADER\fP.
+See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
 .UNINDENT
 .UNINDENT
 .sp
@@ -12941,10 +12941,10 @@ There are two flags to compress the value of column, but you can\(aqt specify th
 .INDENT 0.0
 .TP
 .B 16, \fBCOMPRESS_ZLIB\fP
-Reserved. Compress the value of column by using zlib. This flag is disabled feature even if you build groonga with \fB\-\-with\-zlib\fP.
+Reserved. Compress the value of column by using zlib. This flag is disabled feature even if you build groonga with \fB\-\-with\-zlib\fP\&.
 .TP
 .B 32, \fBCOMPRESS_LZO\fP
-Reserved. Compress the value of column by using lzo. This flag is disabled feature even if you build groonga with \fB\-\-with\-lzo\fP.
+Reserved. Compress the value of column by using lzo. This flag is disabled feature even if you build groonga with \fB\-\-with\-lzo\fP\&.
 .UNINDENT
 .sp
 インデックス型のカラムについては、flagsの値に以下の値を加えることによって、追加の属
@@ -13372,10 +13372,10 @@ select Users
 .UNINDENT
 .SS Parameters
 .sp
-This section describes parameters of \fBcolumn_rename\fP.
+This section describes parameters of \fBcolumn_rename\fP\&.
 .SS Required parameter
 .sp
-There are required parameters, \fBtable_name\fP and \fBcolumn_name\fP.
+There are required parameters, \fBtable_name\fP and \fBcolumn_name\fP\&.
 .SS \fBtable_name\fP
 .sp
 It specifies the name of table.
@@ -14044,7 +14044,7 @@ If you specify "json" as \fBinput_type\fP, you can choose a format from below:
 .sp
 \fB[COLUMN_NAME1, COLUMN_NAME2,..]\fP format in \fBFormat 1\fP is effective only when \fBcolumn\fP parameter isn\(aqt specified.
 .sp
-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.
+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
 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.
@@ -14081,7 +14081,7 @@ column) columns is updated.
 \fBinput_type\fP
 .INDENT 0.0
 .INDENT 3.5
-It specifies an input format for \fBvalues\fP. It supports JSON only.
+It specifies an input format for \fBvalues\fP\&. It supports JSON only.
 .UNINDENT
 .UNINDENT
 .SS Usage
@@ -14383,7 +14383,7 @@ It is useful for you to check the results of normalizer.
 .SS Syntax
 .sp
 \fBnormalize\fP commands has two required parameters. They are
-\fBnormalizer\fP and \fBstring\fP.
+\fBnormalizer\fP and \fBstring\fP\&.
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -14424,14 +14424,14 @@ normalize NormalizerAuto "aBcDe 123"
 .UNINDENT
 .SS Parameters
 .sp
-This section describes parameters of \fBnormalizer\fP.
+This section describes parameters of \fBnormalizer\fP\&.
 .SS Required parameter
 .sp
-There are required parameters, \fBnormalizer\fP and \fBstring\fP.
+There are required parameters, \fBnormalizer\fP and \fBstring\fP\&.
 .SS \fBnormalizer\fP
 .sp
 It specifies the normalizer name. \fBnormalize\fP command uses the
-normalizer that is named \fBnormalizer\fP.
+normalizer that is named \fBnormalizer\fP\&.
 .sp
 See \fB/reference/normalizers\fP about built\-in normalizers.
 .sp
@@ -14441,7 +14441,7 @@ TODO
 .sp
 If you want to use other normalizers, you need to register additional
 normalizer plugin by \fBregister\fP command. For example, you can use
-MySQL compatible normalizer by registering \fI\%groonga\-normalizer\-mysql\fP.
+MySQL compatible normalizer by registering \fI\%groonga\-normalizer\-mysql\fP\&.
 .SS \fBstring\fP
 .sp
 It specifies any string which you want to normalize.
@@ -14449,7 +14449,7 @@ It specifies any string which you want to normalize.
 If you want to include spaces in \fBstring\fP, you need to quote
 \fBstring\fP by single quotation (\fB\(aq\fP) or double quotation (\fB"\fP).
 .sp
-Here is an example to use spaces in \fBstring\fP.
+Here is an example to use spaces in \fBstring\fP\&.
 .sp
 TODO
 .SS Optional parameters
@@ -14459,7 +14459,7 @@ There are optional parameters.
 .sp
 It specifies a normalization customize options. You can specify
 multiple options separated by "\fB|\fP". For example,
-\fBREMOVE_BLANK|WITH_TYPES\fP.
+\fBREMOVE_BLANK|WITH_TYPES\fP\&.
 .sp
 Here are available flags.
 .TS
@@ -14504,15 +14504,15 @@ T}
 _
 .TE
 .sp
-Here is an example that uses \fBREMOVE_BLANK\fP.
+Here is an example that uses \fBREMOVE_BLANK\fP\&.
 .sp
 TODO
 .sp
-Here is an example that uses \fBWITH_TYPES\fP.
+Here is an example that uses \fBWITH_TYPES\fP\&.
 .sp
 TODO
 .sp
-Here is an example that uses \fBREMOVE_TOKENIZED_DELIMITER\fP.
+Here is an example that uses \fBREMOVE_TOKENIZED_DELIMITER\fP\&.
 .sp
 TODO
 .SS Return value
@@ -14559,7 +14559,7 @@ T{
 \fBtypes\fP
 T}	T{
 An array of types of the normalized text. The N\-th \fBtypes\fP shows
-the type of the N\-th character in \fBnormalized\fP.
+the type of the N\-th character in \fBnormalized\fP\&.
 T}
 _
 .TE
@@ -14626,7 +14626,7 @@ Registered plugins can\(aqt be removed for now.
 .UNINDENT
 .SS Syntax
 .sp
-\fBregister\fP has a parameter \fBpath\fP. It is required parameter:
+\fBregister\fP has a parameter \fBpath\fP\&. It is required parameter:
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -14641,7 +14641,7 @@ register path
 .sp
 Here is a sample that registers \fBQueryExpanderTSV\fP query expander
 that is included in
-\fB${PREFIX}/lib/groonga/plugins/query_expanders/tsv.so\fP.
+\fB${PREFIX}/lib/groonga/plugins/query_expanders/tsv.so\fP\&.
 .sp
 Execution example:
 .INDENT 0.0
@@ -14656,11 +14656,11 @@ register query_expanders/tsv
 .UNINDENT
 .UNINDENT
 .sp
-You can omit \fB${PREFIX}/lib/groonga/plugins/\fP and suffix (\fB.so\fP).
+You can omit \fB${PREFIX}/lib/groonga/plugins/\fP and suffix (\fB\&.so\fP).
 They are completed automatically.
 .sp
 You can specify absolute path such as \fBregister
-/usr/lib/groonga/plugins/query_expanders/tsv.so\fP.
+/usr/lib/groonga/plugins/query_expanders/tsv.so\fP\&.
 .SS Return value
 .sp
 \fBregister\fP returns \fBtrue\fP as body on success such as:
@@ -14675,9 +14675,9 @@ You can specify absolute path such as \fBregister
 .UNINDENT
 .UNINDENT
 .sp
-If \fBregister\fP fails, error details are in \fBHEADER\fP.
+If \fBregister\fP fails, error details are in \fBHEADER\fP\&.
 .sp
-See \fB/reference/command/output_format\fP for \fBHEADER\fP.
+See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
 .SS \fBruby_eval\fP
 .SS Summary
 .sp
@@ -14697,7 +14697,7 @@ ruby_eval script
 .UNINDENT
 .SS Usage
 .sp
-You can execute any scripts which mruby supports by calling \fBruby_eval\fP.
+You can execute any scripts which mruby supports by calling \fBruby_eval\fP\&.
 .sp
 Here is an example that just calculate \fB1 + 2\fP as Ruby script.
 .sp
@@ -14744,14 +14744,14 @@ exception information (Including metadata isn\(aqt implemented yet):
 \fBHEADER\fP
 .INDENT 0.0
 .INDENT 3.5
-See \fB/reference/command/output_format\fP about \fBHEADER\fP.
+See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
 .UNINDENT
 .UNINDENT
 .sp
 \fBEVALUATED_VALUE\fP
 .INDENT 0.0
 .INDENT 3.5
-\fBEVALUATED_VALUE\fP is the evaludated value of \fBruby_script\fP.
+\fBEVALUATED_VALUE\fP is the evaludated value of \fBruby_script\fP\&.
 .sp
 \fBruby_eval\fP supports only a number for evaluated value for now.
 Supported types will be increased in the future.
@@ -14777,7 +14777,7 @@ ruby_load path
 .UNINDENT
 .SS Usage
 .sp
-You can load any script file which mruby supports by calling \fBruby_load\fP.
+You can load any script file which mruby supports by calling \fBruby_load\fP\&.
 .sp
 Here is an example that just load \fBexpression.rb\fP as Ruby script.
 .sp
@@ -14824,7 +14824,7 @@ exception information (Including metadata isn\(aqt implemented yet):
 \fBHEADER\fP
 .INDENT 0.0
 .INDENT 3.5
-See \fB/reference/command/output_format\fP about \fBHEADER\fP.
+See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
 .UNINDENT
 .UNINDENT
 .sp
@@ -14930,7 +14930,7 @@ load \-\-table Entries
 .sp
 There is a table, \fBEntries\fP, for blog entries. An entry has title,
 content and the number of likes for the entry. Title is key of
-\fBEntries\fP. Content is value of \fBEntries.content\fP column. The
+\fBEntries\fP\&. Content is value of \fBEntries.content\fP column. The
 number of likes is value of \fBEntries.n_likes\fP column.
 .sp
 \fBEntries._key\fP column and \fBEntries.content\fP column are indexed
@@ -15025,15 +15025,15 @@ command outputs 10 records at a maximum by default. There are only 5
 records. It is less than 10. So the command outputs all records.
 .SS Search conditions
 .sp
-Search conditions are specified by \fBquery\fP or \fBfilter\fP. You can
-also specify both \fBquery\fP and \fBfilter\fP. It means that selected
-records must be matched against both \fBquery\fP and \fBfilter\fP.
+Search conditions are specified by \fBquery\fP or \fBfilter\fP\&. You can
+also specify both \fBquery\fP and \fBfilter\fP\&. It means that selected
+records must be matched against both \fBquery\fP and \fBfilter\fP\&.
 .SS Search condition: \fBquery\fP
 .sp
 \fBquery\fP is designed for search box in Web page. Imagine a search box
 in google.com. You specify search conditions for \fBquery\fP as space
 separated keywords. For example, \fBsearch engine\fP means a matched
-record should contain two words, \fBsearch\fP and \fBengine\fP.
+record should contain two words, \fBsearch\fP and \fBengine\fP\&.
 .sp
 Normally, \fBquery\fP parameter is used for specifying fulltext search
 conditions. It can be used for non fulltext search conditions but
@@ -15042,7 +15042,7 @@ conditions. It can be used for non fulltext search conditions but
 \fBquery\fP parameter is used with \fBmatch_columns\fP parameter when
 \fBquery\fP parameter is used for specifying fulltext search
 conditions. \fBmatch_columns\fP specifies which columnes and indexes are
-matched against \fBquery\fP.
+matched against \fBquery\fP\&.
 .sp
 Here is a simple \fBquery\fP usage example.
 .sp
@@ -15167,7 +15167,7 @@ select Entries \-\-filter \(aqcontent @ "fast" && _key == "Groonga"\(aq
 The \fBselect\fP command searches records that contain a word \fBfast\fP
 in \fBcontent\fP column value and has \fBGroonga\fP as \fB_key\fP from
 \fBEntries\fP table. There are three operators in the command, \fB@\fP,
-\fB&&\fP and \fB==\fP. \fB@\fP is fulltext search operator. \fB&&\fP and
+\fB&&\fP and \fB==\fP\&. \fB@\fP is fulltext search operator. \fB&&\fP and
 \fB==\fP are the same as ECMAScript. \fB&&\fP is logical AND operator and
 \fB==\fP is equality operator.
 .sp
@@ -15176,7 +15176,7 @@ its deatils aren\(aqt described here. See \fB/reference/grn_expr/script_syntax\f
 datails.
 .SS Paging
 .sp
-You can specify range of outputted records by \fBoffset\fP and \fBlimit\fP.
+You can specify range of outputted records by \fBoffset\fP and \fBlimit\fP\&.
 Here is an example to output only the 2nd record.
 .sp
 Execution example:
@@ -15291,7 +15291,7 @@ records.
 This section describes all parameters. Parameters are categorized.
 .SS Required parameter
 .sp
-There is a required parameter, \fBtable\fP.
+There is a required parameter, \fBtable\fP\&.
 .SS \fBtable\fP
 .sp
 It specifies a table to be searched. \fBtable\fP must be specified.
@@ -15332,7 +15332,7 @@ box. \fBfilter\fP parameters is used for implementing complex search
 feature.
 .sp
 If both \fBquery\fP and \fBfilter\fP are specified, selected records must
-be matched against both \fBquery\fP and \fBfilter\fP. If both \fBquery\fP
+be matched against both \fBquery\fP and \fBfilter\fP\&. If both \fBquery\fP
 and \fBfilter\fP aren\(aqt specified, all records are selected.
 .SS \fBmatch_columns\fP
 .sp
@@ -15400,7 +15400,7 @@ records.
 .sp
 Pay attention to \fB_score\fP value. \fB_score\fP value is the number of
 matched counts against \fBquery\fP parameter value. In the example,
-\fBquery\fP parameter value is \fBfast\fP. The fact that \fB_score\fP value
+\fBquery\fP parameter value is \fBfast\fP\&. The fact that \fB_score\fP value
 is 1 means that \fBfast\fP appers in \fBcontent\fP column only once.  The
 fact that \fB_score\fP value is 2 means that \fBfast\fP appears in
 \fBcontent\fP column twice.
@@ -15520,11 +15520,11 @@ of blog entry is more important rather thatn content of blog entry.
 It specifies the query text. Normally, it is used for fulltext search
 with \fBmatch_columns\fP parameter. \fBquery\fP parameter is designed for
 a fulltext search form in a Web page. A query text should be formatted
-in \fB/reference/grn_expr/query_syntax\fP. The syntax is similar to common search
+in \fB/reference/grn_expr/query_syntax\fP\&. The syntax is similar to common search
 form like Google\(aqs search form. For example, \fBword1 word2\fP means
 that groonga searches records that contain both \fBword1\fP and
-\fBword2\fP. \fBword1 OR word2\fP means that groogna searches records that
-contain either \fBword1\fP or \fBword2\fP.
+\fBword2\fP\&. \fBword1 OR word2\fP means that groogna searches records that
+contain either \fBword1\fP or \fBword2\fP\&.
 .sp
 Here is a simple logical and search example.
 .sp
@@ -15648,8 +15648,8 @@ See \fB/reference/grn_expr/query_syntax\fP for other syntax.
 .sp
 It can be used for not only fulltext search but also other
 conditions. For example, \fBcolumn:value\fP means the value of
-\fBcolumn\fP column is equal to \fBvalue\fP. \fBcolumn:<value\fP means the
-value of \fBcolumn\fP column is less than \fBvalue\fP.
+\fBcolumn\fP column is equal to \fBvalue\fP\&. \fBcolumn:<value\fP means the
+value of \fBcolumn\fP column is less than \fBvalue\fP\&.
 .sp
 Here is a simple equality operator search example.
 .sp
@@ -15786,14 +15786,14 @@ It specifies the filter text. Normally, it is used for complex search
 conditions. \fBfilter\fP can be used with \fBquery\fP parameter. If both
 \fBfilter\fP and \fBquery\fP are specified, there are conbined with
 logical and. It means that matched records should be matched against
-both \fBfilter\fP and \fBquery\fP.
+both \fBfilter\fP and \fBquery\fP\&.
 .sp
 \fBfilter\fP parameter is designed for complex conditions. A filter text
-should be formated in \fB/reference/grn_expr/script_syntax\fP. The syntax is
+should be formated in \fB/reference/grn_expr/script_syntax\fP\&. The syntax is
 similar to ECMAScript. For example, \fBcolumn == "value"\fP means that
-the value of \fBcolumn\fP column is equal to \fB"value"\fP. \fBcolumn <
+the value of \fBcolumn\fP column is equal to \fB"value"\fP\&. \fBcolumn <
 value\fP means that the value of \fBcolumn\fP column is less than
-\fBvalue\fP.
+\fBvalue\fP\&.
 .sp
 Here is a simple equality operator search example.
 .sp
@@ -16042,9 +16042,9 @@ select Entries \-\-match_columns content \-\-query groo \-\-match_escalation_thr
 The first \fBselect\fP command searches records that contain a word
 \fBgroo\fP in \fBcontent\fP column value from \fBEntries\fP table. But no
 records are matched because the \fBTokenBigram\fP tokenizer tokenizes
-\fBgroonga\fP to \fBgroonga\fP not \fBgr|ro|oo|on|ng|ga\fP. (The
+\fBgroonga\fP to \fBgroonga\fP not \fBgr|ro|oo|on|ng|ga\fP\&. (The
 \fBTokenBigramSplitSymbolAlpha\fP tokenizer tokenizes \fBgroonga\fP to
-\fBgr|ro|oo|on|ng|ga\fP. See \fB/reference/tokenizers\fP for details.)
+\fBgr|ro|oo|on|ng|ga\fP\&. See \fB/reference/tokenizers\fP for details.)
 It means that \fBgroonga\fP is indexed but \fBgroo\fP isn\(aqt indexed. So no
 records are matched against \fBgroo\fP by exact match. In the case, the
 search storategy escalation is used because the number of matched
@@ -16065,7 +16065,7 @@ Deprecated. Use \fIquery\-expander\fP instead.
 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.
+column value by \fBquery\fP\&.
 .sp
 Here are available values:
 .INDENT 0.0
@@ -16081,11 +16081,11 @@ Here are available values:
 \fBNONE\fP
 .UNINDENT
 .sp
-\fBALLOW_PRAGMA\fP enables pragma at the head of \fBquery\fP. This is not
+\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
+in \fBmatch_columns\fP\&. To specify column, there are \fBCOLUMN:...\fP
 syntaxes.
 .sp
 \fBALLOW_UPDATE\fP enables column update by \fBquery\fP with
@@ -16094,18 +16094,18 @@ 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
+\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.
+\fBALLOW_COLUMN|ALLOW_UPDATE\fP\&.
 .sp
-The default value is \fBALLOW_PRAGMA|ALLOW_COLUMN\fP.
+The default value is \fBALLOW_PRAGMA|ALLOW_COLUMN\fP\&.
 .sp
-Here is a usage example of \fBALLOW_COLUMN\fP.
+Here is a usage example of \fBALLOW_COLUMN\fP\&.
 .sp
 Execution example:
 .INDENT 0.0
@@ -16160,7 +16160,7 @@ select Entries \-\-query content:@mroonga \-\-query_flags ALLOW_COLUMN
 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.
+Here is a usage example of \fBALLOW_UPDATE\fP\&.
 .sp
 Execution example:
 .INDENT 0.0
@@ -16262,10 +16262,10 @@ select Users
 .UNINDENT
 .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
+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.
+Here is a usage example of \fBALLOW_LEADING_NOT\fP\&.
 .sp
 Execution example:
 .INDENT 0.0
@@ -16338,7 +16338,7 @@ select Entries \-\-match_columns content \-\-query \-mroonga \-\-query_flags ALL
 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 \fBNONE\fP.
+Here is a usage example of \fBNONE\fP\&.
 .sp
 Execution example:
 .INDENT 0.0
@@ -16393,10 +16393,10 @@ select Entries \-\-match_columns content \-\-query \(aqmroonga OR _key:Groonga\(
 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
+column is equal to \fBGroonga\fP\&. Because \fBALLOW_COLUMN\fP flag is not
 specified.
 .sp
-See also \fB/reference/grn_expr/query_syntax\fP.
+See also \fB/reference/grn_expr/query_syntax\fP\&.
 .SS \fBquery_expander\fP
 .sp
 It\(aqs for query expansion. Query expansion substitutes specific words
@@ -16408,13 +16408,13 @@ value. The format of this parameter value is
 \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)
+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).
+\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
@@ -16448,15 +16448,15 @@ load \-\-table Thesaurus
 .UNINDENT
 .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
+\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 searches with \fB"((groonga)
-OR (senna))"\fP. Nomrally, it\(aqs good idea that substitution table has
+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
+\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
@@ -16613,7 +16613,7 @@ 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
+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.
@@ -16679,8 +16679,8 @@ select Entries \-\-match_columns content \-\-query "popular" \-\-query_expander
 .UNINDENT
 .UNINDENT
 .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
+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
@@ -16689,7 +16689,7 @@ is equal to or more than \fB10\fP from \fBEntries\fP table.
 .SS Output related parameters
 .SS \fBoutput_columns\fP
 .sp
-It specifies output columns separated by \fB,\fP.
+It specifies output columns separated by \fB,\fP\&.
 .sp
 Here is a simple \fBoutput_columns\fP usage example.
 .sp
@@ -16737,7 +16737,7 @@ The \fBselect\fP command just outputs \fB_id\fP and \fB_key\fP column
 values.
 .sp
 \fB*\fP is a special value. It means that all columns that are not
-\fB/reference/pseudo_column\fP.
+\fB/reference/pseudo_column\fP\&.
 .sp
 Here is a \fB*\fP usage example.
 .sp
@@ -16790,11 +16790,11 @@ The \fBselect\fP command outputs \fB_key\fP pseudo column, \fBcontent\fP
 column and \fBn_likes\fP column values but doesn\(aqt output \fB_id\fP pseudo
 column value.
 .sp
-The default value is \fB_id, _key, *\fP. It means that all column
+The default value is \fB_id, _key, *\fP\&. It means that all column
 values except \fB_score\fP are outputted.
 .SS \fBsortby\fP
 .sp
-It specifies sort keys separated by \fB,\fP. Each sort key is column
+It specifies sort keys separated by \fB,\fP\&. Each sort key is column
 name.
 .sp
 Here is a simple \fBsortby\fP usage example.
@@ -16957,7 +16957,7 @@ select Entries \-\-sortby \(aq\-n_likes, _id\(aq
 .UNINDENT
 .sp
 The \fBselect\fP command sorts by \fBn_likes\fP column value in descending
-order. But ascending order is used for sorting by \fB_id\fP.
+order. But ascending order is used for sorting by \fB_id\fP\&.
 .sp
 You can use \fB_score\fP pseudo column in \fBsortby\fP if you use
 \fBquery\fP or \fBfilter\fP parameter.
@@ -17058,7 +17058,7 @@ select Entries \-\-sortby _id \-\-offset 3 \-\-output_columns _key
 The \fBselect\fP command outputs from the 4th record.
 .sp
 You can specify negative value. It means that \fBthe number of matched
-records + offset\fP. If you have 3 matched records and specify
+records + offset\fP\&. If you have 3 matched records and specify
 \fB\-\-offset \-2\fP, you get records from the 1st (\fB3 + \-2 = 1\fP) record
 to the 3rd record.
 .sp
@@ -17101,9 +17101,9 @@ select Entries \-\-sortby _id \-\-offset \-2 \-\-output_columns _key
 .UNINDENT
 .sp
 The \fBselect\fP command outputs from the 4th record because the total
-number of records is \fB5\fP.
+number of records is \fB5\fP\&.
 .sp
-The default value is \fB0\fP.
+The default value is \fB0\fP\&.
 .SS \fBlimit\fP
 .sp
 It specifies the max number of output records. If the number of
@@ -17155,7 +17155,7 @@ select Entries \-\-sortby _id \-\-offset 2 \-\-limit 3 \-\-output_columns _key
 The \fBselect\fP command outputs the 3rd, the 4th and the 5th records.
 .sp
 You can specify negative value. It means that \fBthe number of matched
-records + limit + 1\fP. For example, \fB\-\-limit \-1\fP outputs all
+records + limit + 1\fP\&. For example, \fB\-\-limit \-1\fP outputs all
 records. It\(aqs very useful value to show all records.
 .sp
 Here is a simple negative \fBlimit\fP value usage example.
@@ -17236,7 +17236,7 @@ select Entries \-\-limit \-1
 .sp
 The \fBselect\fP command outputs all records.
 .sp
-The default value is \fB10\fP.
+The default value is \fB10\fP\&.
 .SS \fBscorer\fP
 .sp
 TODO: write in English and add example.
@@ -17599,7 +17599,7 @@ The suggest command does suggestion.
 .UNINDENT
 .UNINDENT
 .sp
-You can specify one or more types separated by \fB|\fP.
+You can specify one or more types separated by \fB|\fP\&.
 Here are examples:
 .INDENT 7.0
 .INDENT 3.5
@@ -17698,7 +17698,7 @@ It specifies number of returned records.
 .TP
 .B \fBfrequency_threshold\fP
 It specifies threshold for item frequency. Returned records must have
-\fB_score\fP that is greater than or equal to \fBfrequency_threshold\fP.
+\fB_score\fP that is greater than or equal to \fBfrequency_threshold\fP\&.
 .INDENT 7.0
 .TP
 .B Default:
@@ -17714,7 +17714,7 @@ probability. Conditional probability is used for learned
 data. It is probability of query submission when \fBquery\fP
 is occurred. Returned records must have conditional
 probability that is greater than or equal to
-\fBconditional_probability_threshold\fP.
+\fBconditional_probability_threshold\fP\&.
 .INDENT 0.0
 .TP
 .B Default:
@@ -17802,7 +17802,7 @@ Here is a returned JSON format:
 \fBtype\fP
 .INDENT 0.0
 .INDENT 3.5
-A type specified by \fBtypes\fP.
+A type specified by \fBtypes\fP\&.
 .UNINDENT
 .UNINDENT
 .sp
@@ -17816,7 +17816,7 @@ A candidate for completion, correction or suggestion.
 \fBscore of candidate\fP
 .INDENT 0.0
 .INDENT 3.5
-A score of corresponding \fBcandidate\fP. It means that
+A score of corresponding \fBcandidate\fP\&. It means that
 higher score candidate is more likely candidate for
 completion, correction or suggestion. Returned candidates
 are sorted by \fBscore of candidate\fP descending by
@@ -18200,7 +18200,7 @@ table_create Lexicon TABLE_PAT_KEY ShortText \-\-default_tokenizer TokenBigram \
 The \fBtable_create\fP command creates the following table:
 .INDENT 0.0
 .IP \(bu 2
-The table is named \fBLexicon\fP.
+The table is named \fBLexicon\fP\&.
 .IP \(bu 2
 The table is \fBTABLE_PAT_KEY\fP type table.
 .IP \(bu 2
@@ -18217,14 +18217,14 @@ table is used for fulltext search.
 .sp
 In fulltext search, predictive search may be used for fuzzy
 search. Predictive search is supported by \fBTABLE_PAT_KEY\fP and
-\fBTABLE_DAT_KEY\fP.
+\fBTABLE_DAT_KEY\fP\&.
 .sp
 Lexicon table has many keys because a fulltext target text has many
 tokens. Table that has many keys should consider table size because
 large table requires large memory. Requiring large memory causes disk
 I/O. It blocks fast search. So table size is important for a table
 that has many keys. \fBTABLE_PAT_KEY\fP is less table size than
-\fBTABLE_DAT_KEY\fP.
+\fBTABLE_DAT_KEY\fP\&.
 .sp
 Because of the above reasons, \fBTABLE_PAT_KEY\fP is suitable table type
 for lexicon table.
@@ -18294,7 +18294,7 @@ suitable. Index for age is the case in the above example. Index for
 age will have only 0\-100 items because human doesn\(aqt live so long.
 .sp
 If you have many indexed items, \fBTABLE_PAT_KEY\fP is suitable. Because
-\fBTABLE_PAT_KEY\fP is smaller than \fBTABLE_DAT_KEY\fP.
+\fBTABLE_PAT_KEY\fP is smaller than \fBTABLE_DAT_KEY\fP\&.
 .SS Parameters
 .sp
 This section describes all parameters.
@@ -18323,7 +18323,7 @@ character.)
 .sp
 You need to create a name with one or more the above chracters. Note
 that you cannot use \fB_\fP as the first character such as
-\fB_name\fP.
+\fB_name\fP\&.
 .SS \fBflags\fP
 .sp
 It specifies a table type and table customize options.
@@ -18367,7 +18367,7 @@ T{
 \fBKEY_WITH_SIS\fP
 T}	T{
 Enable Semi Infinite String.
-Require \fBTABLE_PAT_KEY\fP.
+Require \fBTABLE_PAT_KEY\fP\&.
 T}
 _
 .TE
@@ -18385,11 +18385,11 @@ or more \fBTABLE_${TYPE}\fP flags. For example,
 \fBTABLE_NO_KEY|TABLE_HASH_KEY\fP is invalid.
 .sp
 You can combine flags with \fB|\fP (vertical bar) such as
-\fBTABLE_PAT_KEY|KEY_WITH_SIS\fP.
+\fBTABLE_PAT_KEY|KEY_WITH_SIS\fP\&.
 .sp
 See \fB/reference/tables\fP for difference between table types.
 .sp
-The default flags are \fBTABLE_HASH_KEY\fP.
+The default flags are \fBTABLE_HASH_KEY\fP\&.
 .SS \fBkey_type\fP
 .sp
 It specifies key type.
@@ -18449,9 +18449,9 @@ The default value is none.
 .UNINDENT
 .UNINDENT
 .sp
-If \fBtable_create\fP fails, error details are in \fBHEADER\fP.
+If \fBtable_create\fP fails, error details are in \fBHEADER\fP\&.
 .sp
-See \fB/reference/command/output_format\fP for \fBHEADER\fP.
+See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
 .SS See also
 .INDENT 0.0
 .IP \(bu 2
@@ -18829,19 +18829,19 @@ tokenize TokenBigram "Fulltext Search"
 .UNINDENT
 .sp
 It has only required parameters. \fBtokenizer\fP is \fBTokenBigram\fP and
-\fBstring\fP is \fB"Fulltext Search"\fP. It returns tokens that is
+\fBstring\fP is \fB"Fulltext Search"\fP\&. It returns tokens that is
 generated by tokenizing \fB"Fulltext Search"\fP with \fBTokenBigram\fP
-tokenizer. It doesn\(aqt normalize \fB"Fulltext Search"\fP.
+tokenizer. It doesn\(aqt normalize \fB"Fulltext Search"\fP\&.
 .SS Parameters
 .sp
 This section describes all parameters. Parameters are categorized.
 .SS Required parameters
 .sp
-There are required parameters, \fBtokenizer\fP and \fBstring\fP.
+There are required parameters, \fBtokenizer\fP and \fBstring\fP\&.
 .SS \fBtokenizer\fP
 .sp
 It specifies the tokenizer name. \fBtokenize\fP command uses the
-tokenizer that is named \fBtokenizer\fP.
+tokenizer that is named \fBtokenizer\fP\&.
 .sp
 See \fB/reference/tokenizers\fP about built\-in tokenizers.
 .sp
@@ -18931,7 +18931,7 @@ tokenize TokenTrigram "Fulltext Search"
 If you want to use other tokenizers, you need to register additional
 tokenizer plugin by \fBregister\fP command. For example, you can use
 \fI\%KyTea\fP based tokenizer by
-registering \fBtokenizers/kytea\fP.
+registering \fBtokenizers/kytea\fP\&.
 .SS \fBstring\fP
 .sp
 It specifies any string which you want to tokenize.
@@ -18939,7 +18939,7 @@ It specifies any string which you want to tokenize.
 If you want to include spaces in \fBstring\fP, you need to quote
 \fBstring\fP by single quotation (\fB\(aq\fP) or double quotation (\fB"\fP).
 .sp
-Here is an example to use spaces in \fBstring\fP.
+Here is an example to use spaces in \fBstring\fP\&.
 .sp
 Execution example:
 .INDENT 0.0
@@ -19127,8 +19127,8 @@ There are optional parameters.
 .SS \fBnormalizer\fP
 .sp
 It specifies the normalizer name. \fBtokenize\fP command uses the
-normalizer that is named \fBnormalizer\fP. Normalizer is important for
-N\-gram family tokenizers such as \fBTokenBigram\fP.
+normalizer that is named \fBnormalizer\fP\&. Normalizer is important for
+N\-gram family tokenizers such as \fBTokenBigram\fP\&.
 .sp
 Normalizer detects character type for each character while
 normalizing. N\-gram family tokenizers use character types while
@@ -19255,7 +19255,7 @@ Continuous alphabets are tokenized as one token. For example,
 \fBfulltext\fP is a token.
 .sp
 If you want to tokenize by two characters with noramlizer, use
-\fBTokenBigramSplitSymbolAlpha\fP.
+\fBTokenBigramSplitSymbolAlpha\fP\&.
 .sp
 Execution example:
 .INDENT 0.0
@@ -19340,7 +19340,7 @@ to lower case characters. For example, \fBfu\fP is a token.
 .sp
 It specifies a tokenization customize options. You can specify
 multiple options separated by "\fB|\fP". For example,
-\fBNONE|ENABLE_TOKENIZED_DELIMITER\fP.
+\fBNONE|ENABLE_TOKENIZED_DELIMITER\fP\&.
 .sp
 Here are available flags.
 .TS
@@ -19368,7 +19368,7 @@ T}
 _
 .TE
 .sp
-Here is an example that uses \fBENABLE_TOKENIZED_DELIMITER\fP.
+Here is an example that uses \fBENABLE_TOKENIZED_DELIMITER\fP\&.
 .sp
 Execution example:
 .INDENT 0.0
@@ -19406,7 +19406,7 @@ tokenize TokenDelimit "Full
 \fBTokenDelimit\fP tokenizer is one of tokenized delimiter supported
 tokenizer. \fBENABLE_TOKENIZED_DELIMITER\fP enables tokenized delimiter.
 Tokenized delimiter is special character that indicates token
-border. It is \fBU+FFFE\fP. The character is not assigned any
+border. It is \fBU+FFFE\fP\&. The character is not assigned any
 character. It means that the character is not appeared in normal
 string. So the character is good character for this puropose. If
 \fBENABLE_TOKENIZED_DELIMITER\fP is enabled, the target string is
@@ -19431,7 +19431,7 @@ the feature:
 \fBHEADER\fP
 .INDENT 0.0
 .INDENT 3.5
-See \fB/reference/command/output_format\fP about \fBHEADER\fP.
+See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
 .UNINDENT
 .UNINDENT
 .sp
@@ -19578,10 +19578,10 @@ select Users
 .UNINDENT
 .SS Parameters
 .sp
-This section describes parameters of \fBtruncate\fP.
+This section describes parameters of \fBtruncate\fP\&.
 .SS Required parameter
 .sp
-There is required parameter, \fBtable_name\fP.
+There is required parameter, \fBtable_name\fP\&.
 .SS \fBtable_name\fP
 .sp
 It specifies the name of table.
@@ -19776,9 +19776,9 @@ Object型はv1.2でサポートされます。
 .SS Tables
 .SS Summary
 .sp
-Table in groonga manages relation between ID and key. Groonga provides
+Table in Groonga manages relation between ID and key. Groonga provides
 four table types. They are \fBTABLE_NO_KEY\fP, \fBTABLE_HASH_KEY\fP,
-\fBTABLE_PAT_KEY\fP and \fBTABLE_DAT_KEY\fP.
+\fBTABLE_PAT_KEY\fP and \fBTABLE_DAT_KEY\fP\&.
 .sp
 All tables except \fBTABLE_NO_KEY\fP provides both fast ID search by key
 and fast key search by ID. \fBTABLE_NO_KEY\fP doesn\(aqt support
@@ -19786,7 +19786,7 @@ key. \fBTABLE_NO_KEY\fP only manages ID. So \fBTABLE_NO_KEY\fP doesn\(aqt
 provides ID search and key search.
 .SS Characteristics
 .sp
-Here is a chracteristic table of all tables in groonga. (\fBTABLE_\fP
+Here is a chracteristic table of all tables in Groonga. (\fBTABLE_\fP
 prefix is omitted in the table.)
 .TS
 center;
@@ -19994,10 +19994,10 @@ index for range search.
 is not suitable for storing many records. \fBTABLE_DAT_KEY\fP is a only
 table that supports key update.
 .sp
-\fBTABLE_DAT_KEY\fP is used in groonga database. Groonga database needs
+\fBTABLE_DAT_KEY\fP is used in Groonga database. Groonga database needs
 to convert object name such as \fBShortText\fP, \fBTokenBigram\fP and
-table names to object ID. And groonga database needs to rename object
-name. Those features are implemented by \fBTABLE_DAT_KEY\fP. The number
+table names to object ID. And Groonga database needs to rename object
+name. Those features are implemented by \fBTABLE_DAT_KEY\fP\&. The number
 of objects is small. So large data size demerit of \fBTABLE_DAT_KEY\fP
 can be ignored.
 .SS Record ID
@@ -20057,7 +20057,7 @@ normalization by registering your normalizer plugins to Groonga.
 A normalizer module is attached to a table. A table can have zero or
 one normalizer module. You can attach a normalizer module to a table
 by \fItable\-create\-normalizer\fP option in
-\fB/reference/commands/table_create\fP.
+\fB/reference/commands/table_create\fP\&.
 .sp
 Here is an example \fBtable_create\fP that uses \fBNormalizerAuto\fP
 normalizer module:
@@ -20079,7 +20079,7 @@ table_create Dictionary TABLE_HASH_KEY ShortText \-\-normalizer NormalizerAuto
 .INDENT 0.0
 .INDENT 3.5
 Groonga 2.0.9 or earlier doesn\(aqt have \fB\-\-normalizer\fP option in
-\fBtable_create\fP. \fBKEY_NORMALIZE\fP flag was used instead.
+\fBtable_create\fP\&. \fBKEY_NORMALIZE\fP flag was used instead.
 .sp
 You can open an old database by Groonga 2.1.0 or later. An old
 database means that the database is created by Groonga 2.0.9 or
@@ -20152,7 +20152,7 @@ select Dictionary
 \fBNormalizerAuto\fP normalizer normalizes a text as a downcased text.
 For example, \fB"Apple"\fP is normalized to \fB"apple"\fP, \fB"black"\fP is
 normalized to \fB"blank"\fP and \fB"COLOR"\fP is normalized to
-\fB"color"\fP.
+\fB"color"\fP\&.
 .sp
 If a table is a lexicon for fulltext search, tokenized tokens are
 normalized. Because tokens are stored as table keys. Table keys are
@@ -20245,7 +20245,7 @@ Here is a list of additional normalizers provided by \fBgroonga\-normalizer\-mys
 .sp
 \fBgroonga\-normalizer\-mysql\fP is a Groonga plugin.
 It provides MySQL compatible normalizers to Groonga.
-\fBNormalizerMySQLGeneralCI\fP corresponds to \fButf8mb4_general_ci\fP.
+\fBNormalizerMySQLGeneralCI\fP corresponds to \fButf8mb4_general_ci\fP\&.
 .sp
 You need to register \fBnormalizers/mysql\fP plugin in advance.
 .sp
@@ -20322,7 +20322,7 @@ feature than the embedded query expansion feature. For example, it
 doesn\(aqt support word normalization. But it may be easy to use because
 you can manage your synonyms by TSV file. You can edit your synonyms
 by spreadsheet application such as Excel. With the embedded query
-expansion feature, you manage your synonyms by groonga\(aqs table.
+expansion feature, you manage your synonyms by Groonga\(aqs table.
 .SS Install
 .sp
 You need to register \fBquery_expanders/tsv\fP as a plugin before you
@@ -20385,9 +20385,9 @@ _
 .TE
 .sp
 The table means that \fBsynonym 1\fP and \fBsynonym 2\fP are synonyms of
-\fBword\fP. For example, \fBgroonga\fP and \fBSenna\fP are synonyms of
-\fBgroonga\fP. And \fBmroonga\fP and \fBgroonga MySQL\fP are synonyms of
-\fBmroonga\fP.
+\fBword\fP\&. For example, \fBgroonga\fP and \fBSenna\fP are synonyms of
+\fBgroonga\fP\&. And \fBmroonga\fP and \fBgroonga MySQL\fP are synonyms of
+\fBmroonga\fP\&.
 .sp
 Here is an example of query expnasion that uses \fBgroonga\fP as query:
 .INDENT 0.0
@@ -20526,12 +20526,12 @@ With the above command, \fB/tmp/synonyms.tsv\fP file is used.
 You can define zero or more synonyms in a TSV file. You define a
 \fBword\fP and \fBsynonyms\fP pair by a line. \fBword\fP is expanded to
 \fBsynonyms\fP in \fB\-\-query\fP value. \fBSynonyms\fP are combined by
-\fBOR\fP. For example, \fBgroonga\fP and \fBSenna\fP synonyms are expanded
-as \fBgroonga OR Senna\fP.
+\fBOR\fP\&. For example, \fBgroonga\fP and \fBSenna\fP synonyms are expanded
+as \fBgroonga OR Senna\fP\&.
 .sp
 The first column is \fBword\fP and the rest columns are \fBsynonyms\fP of
-the \fBword\fP. Here is a sample line for \fBword\fP is \fBgroonga\fP and
-\fBsynonyms\fP are \fBgroonga\fP and \fBSenna\fP. \fB(TAB)\fP means a tab
+the \fBword\fP\&. Here is a sample line for \fBword\fP is \fBgroonga\fP and
+\fBsynonyms\fP are \fBgroonga\fP and \fBSenna\fP\&. \fB(TAB)\fP means a tab
 character (\fBU+0009\fP):
 .INDENT 0.0
 .INDENT 3.5
@@ -20577,7 +20577,7 @@ loaded only at the plugin load time.
 疑似カラム
 .SS 説明
 .sp
-groongaのデータベースで作成したテーブルには、いくつかのカラムが自動的に定義されます。
+Groongaのデータベースで作成したテーブルには、いくつかのカラムが自動的に定義されます。
 .sp
 これらのカラムはいずれもアンダースコア(\(aq_\(aq)で始まる名前が付与されます。定義される疑似カラムは、テーブルの種類によって異なります。
 .sp
@@ -20620,12 +20620,12 @@ groongaのデータベースで作成したテーブルには、いくつかの
 .SS grn_expr
 .sp
 Grn_expr is an object that searches records with specified conditions
-and manipulates a database. It\(aqs pronounced as \fBgurun expression\fP.
+and manipulates a database. It\(aqs pronounced as \fBgurun expression\fP\&.
 .sp
 Conditions for searching records from a database can be represented by
 conbining condition expressions such as \fBequal condition expression\fP
 and \fBless than condition expression\fP with set operations such as
-\fBAND\fP, \fBOR\fP and \fBNOT\fP. Grn_expr executes those conditions to
+\fBAND\fP, \fBOR\fP and \fBNOT\fP\&. Grn_expr executes those conditions to
 search records. You can also use advanced searches such as similar
 search and near search by grn_expr. You can also use flexible full
 text search. For example, you can control hit scores for specified
@@ -20650,40 +20650,40 @@ Calling grn_expr related APIs.
 \fB/reference/grn_expr/query_syntax\fP is for common search form in
 Internet search site. It\(aqs simple and easy to use but it has a
 limitation. You can not use all condition expressions and set
-operations in \fB/reference/grn_expr/query_syntax\fP. You can use
+operations in \fB/reference/grn_expr/query_syntax\fP\&. You can use
 \fB/reference/grn_expr/query_syntax\fP with \fBquery\fP option in
-\fB/reference/commands/select\fP.
+\fB/reference/commands/select\fP\&.
 .sp
 \fB/reference/grn_expr/script_syntax\fP is ECMAScript like
 syntax. You can use all condition expresssions and set operations in
-\fB/reference/grn_expr/script_syntax\fP. You can use
+\fB/reference/grn_expr/script_syntax\fP\&. You can use
 \fB/reference/grn_expr/script_syntax\fP with \fBfilter\fP option and
-\fBscorer\fP option in \fB/reference/commands/select\fP.
+\fBscorer\fP option in \fB/reference/commands/select\fP\&.
 .sp
 You can use groonga as a library and create a grn_expr by calling
 grn_expr related APIs. You can use full features with calling APIs
-like \fB/reference/grn_expr/script_syntax\fP. Calling APIs is useful
+like \fB/reference/grn_expr/script_syntax\fP\&. Calling APIs is useful
 creating a custom syntax to create grn_expr. They are used in \fI\%rroonga\fP that is Ruby bindings
-of groonga. Rroonga can create a grn_expr by Ruby\(aqs syntax instead of
+of Groonga. Rroonga can create a grn_expr by Ruby\(aqs syntax instead of
 parsing string.
 .SS Query syntax
 .sp
 Query syntax is a syntax to specify search condition for common Web
 search form. It is similar to the syntax of Google\(aqs search form. For
 example, \fBword1 word2\fP means that groonga searches records that
-contain both \fBword1\fP and \fBword2\fP. \fBword1 OR word2\fP means that
-groogna searches records that contain either \fBword1\fP or \fBword2\fP.
+contain both \fBword1\fP and \fBword2\fP\&. \fBword1 OR word2\fP means that
+groogna searches records that contain either \fBword1\fP or \fBword2\fP\&.
 .sp
 Query syntax consists of \fBconditional expression\fP, \fBcombind
-expression\fP and \fBassignment expression\fP. Nomrally \fBassignment
+expression\fP and \fBassignment expression\fP\&. Nomrally \fBassignment
 expression\fP can be ignored. Because \fBassignment expression\fP is
-disabled in \fB\-\-query\fP option of \fB/reference/commands/select\fP. You can use
+disabled in \fB\-\-query\fP option of \fB/reference/commands/select\fP\&. You can use
 it if you use groonga as library and customize query syntax parser
 options.
 .sp
 \fBConditinal expression\fP specifies an condition. \fBCombinded
 expression\fP consists of one or more \fBconditional expression\fP,
-\fBcombined expression\fP or \fBassignment expression\fP. \fBAssignment
+\fBcombined expression\fP or \fBassignment expression\fP\&. \fBAssignment
 expression\fP can assigns a column to a value.
 .SS Sample data
 .sp
@@ -20733,7 +20733,7 @@ load \-\-table Entries
 .sp
 There is a table, \fBEntries\fP, for blog entries. An entry has title,
 content and the number of likes for the entry. Title is key of
-\fBEntries\fP. Content is value of \fBEntries.content\fP column. The
+\fBEntries\fP\&. Content is value of \fBEntries.content\fP column. The
 number of likes is value of \fBEntries.n_likes\fP column.
 .sp
 \fBEntries._key\fP column and \fBEntries.content\fP column are indexed
@@ -20744,8 +20744,8 @@ OK. The schema and data for examples are ready.
 .SS Escape
 .sp
 There are special characters in query syntax. To use a special
-character as itself, it should be escaped by prepending \fB\e\fP. For
-example, \fB"\fP is a special character. It is escaped as \fB\e"\fP.
+character as itself, it should be escaped by prepending \fB\e\fP\&. For
+example, \fB"\fP is a special character. It is escaped as \fB\e"\fP\&.
 .sp
 Here is a special character list:
 .INDENT 0.0
@@ -20754,7 +20754,7 @@ Here is a special character list:
 .IP \(bu 2
 \fB[space]\fP (escaped as \fB[backslash][space]\fP) (You should
 substitute \fB[space]\fP with a white space character that is 0x20
-in ASCII and \fB[backslash]\fP with \fB\e\e\fP.)
+in ASCII and \fB[backslash]\fP with \fB\e\e\fP\&.)
 .IP \(bu 2
 \fB"\fP (escaped as \fB\e"\fP)
 .IP \(bu 2
@@ -20770,10 +20770,10 @@ in ASCII and \fB[backslash]\fP with \fB\e\e\fP.)
 .UNINDENT
 .sp
 You can use quote instead of escape. Quote syntax is \fB"..."\fP or
-\fB\(aq...\(aq\fP. You need escape \fB"\fP as \fB\e"\fP in \fB"..."\fP quote syntax.
+\fB\(aq...\(aq\fP\&. You need escape \fB"\fP as \fB\e"\fP in \fB"..."\fP quote syntax.
 You need escape \fB\(aq\fP as \fB\e\(aq\fP in \fB\(aq...\(aq\fP quote syntax. For
 example, \fBAlice\(aqs brother (Bob)\fP can be quoted \fB"Alice\(aqs brother
-(Bob)"\fP or \fB\(aqAlice\e\(aqs brother (Bob)\(aq\fP.
+(Bob)"\fP or \fB\(aqAlice\e\(aqs brother (Bob)\(aq\fP\&.
 .sp
 \fBNOTE:\fP
 .INDENT 0.0
@@ -20792,7 +20792,7 @@ special character is escaped properly.
 Here is available conditional expression list.
 .SS Full text search condition
 .sp
-Its syntax is \fBkeyword\fP.
+Its syntax is \fBkeyword\fP\&.
 .sp
 \fBFull text search condition\fP specifies a full text search condition
 against the default match columns. Match columns are full text search
@@ -20800,13 +20800,13 @@ target columns.
 .sp
 You should specify the default match columns for full text
 search. They can be specified by \fB\-\-match_columns\fP option of
-\fB/reference/commands/select\fP. If you don\(aqt specify the default match
+\fB/reference/commands/select\fP\&. If you don\(aqt specify the default match
 columns, this conditional expression fails.
 .sp
 This conditional expression does full text search with
-\fBkeyword\fP. \fBkeyword\fP should not contain any spaces. If \fBkeyword\fP
+\fBkeyword\fP\&. \fBkeyword\fP should not contain any spaces. If \fBkeyword\fP
 contains a space such as \fBsearch keyword\fP, it means two full text
-search conditions; \fBsearch\fP and \fBkeyword\fP. If you want to
+search conditions; \fBsearch\fP and \fBkeyword\fP\&. If you want to
 specifies a keyword that contains one or more spaces, you can use
 \fBphrase search condition\fP that is described below.
 .sp
@@ -20874,18 +20874,18 @@ The expression matches records that contain a word \fBfast\fP in
 \fBcontent\fP column is the default match column.
 .SS Phrase search condition
 .sp
-Its syntax is \fB"search keyword"\fP.
+Its syntax is \fB"search keyword"\fP\&.
 .sp
 \fBPhrase search condition\fP specifies a phrase search condition
 against the default match columns.
 .sp
 You should specify the default match columns for full text
 search. They can be specified by \fB\-\-match_columns\fP option of
-\fB/reference/commands/select\fP. If you don\(aqt specify the default match
+\fB/reference/commands/select\fP\&. If you don\(aqt specify the default match
 columns, this conditional expression fails.
 .sp
 This conditional expression does phrase search with \fBsearch
-keyword\fP. Phrase search searches records that contain \fBsearch\fP and
+keyword\fP\&. Phrase search searches records that contain \fBsearch\fP and
 \fBkeyword\fP and those terms are appeared in the same order and
 adjacent. Thus, \fBPut a search keyword in the form\fP is matched but
 \fBSearch by the keyword\fP and \fBThere is a keyword. Search by it!\fP
@@ -20950,12 +20950,12 @@ The expression matches records that contain a phrase \fBI started\fP in
 \fBcontent\fP column is the default match column.
 .SS Full text search condition (with explicit match column)
 .sp
-Its syntax is \fBcolumn:@keyword\fP.
+Its syntax is \fBcolumn:@keyword\fP\&.
 .sp
 It\(aqs similar to \fBfull text search condition\fP but it doesn\(aqt require
 the default match columns. You need to specify match column for the
 full text search condition by \fBcolumn:\fP instead of
-\fB\-\-match_columns\fP option of \fB/reference/commands/select\fP.
+\fB\-\-match_columns\fP option of \fB/reference/commands/select\fP\&.
 .sp
 This condtional expression is useful when you want to use two or more
 full text search against different columns. The default match columns
@@ -21047,17 +21047,17 @@ The expression matches records that contain a word \fBfast\fP in
 \fBcontent\fP column value.
 .SS Phrase search condition (with explicit match column)
 .sp
-Its syntax is \fBcolumn:@"search keyword"\fP.
+Its syntax is \fBcolumn:@"search keyword"\fP\&.
 .sp
 It\(aqs similar to \fBphrase search condition\fP but it doesn\(aqt require the
 default match columns. You need to specify match column for the phrase
 search condition by \fBcolumn:\fP instead of \fB\-\-match_columns\fP option
-of \fB/reference/commands/select\fP.
+of \fB/reference/commands/select\fP\&.
 .sp
 The different between \fBphrase search condition\fP and \fBphrase search
 condition (with explicit match column)\fP is similar to between \fBfull
 text search condition\fP and \fBfull text search condition (with
-explicit match column)\fP. \fBPhrase search condition\fP supports
+explicit match column)\fP\&. \fBPhrase search condition\fP supports
 advanced match columns but \fBphrase search condition (with explicit
 match column)\fP isn\(aqt supported. See description of \fBfull text search
 condition (with explicit match column)\fP about advanced match columns.
@@ -21119,24 +21119,24 @@ The expression matches records that contain a phrase \fBI started\fP in
 \fBI\fP and \fBstarted\fP aren\(aqt adjacent.
 .SS Prefix search condition
 .sp
-Its syntax is \fBcolumn:^value\fP or \fBvalue*\fP.
+Its syntax is \fBcolumn:^value\fP or \fBvalue*\fP\&.
 .sp
-This conditional expression does prefix search with \fBvalue\fP. Prefix
-search searches records that contain a word that starts with \fBvalue\fP.
+This conditional expression does prefix search with \fBvalue\fP\&. Prefix
+search searches records that contain a word that starts with \fBvalue\fP\&.
 .sp
 You can use fast prefix search against a column. The column must be
 indexed and index table must be patricia trie table
 (\fBTABLE_PAT_KEY\fP) or double array trie table
 (\fBTABLE_DAT_KEY\fP). You can also use fast prefix search against
 \fB_key\fP pseudo column of patricia trie table or double array trie
-table. You don\(aqt need to index \fB_key\fP.
+table. You don\(aqt need to index \fB_key\fP\&.
 .sp
 Prefix search can be used with other table types but it causes all
 records scan. It\(aqs not problem for small records but it spends more
 time for large records.
 .sp
 It doesn\(aqt require the default match columns such as \fBfull text
-search condition\fP and \fBphrase search condition\fP.
+search condition\fP and \fBphrase search condition\fP\&.
 .sp
 Here is a simple exmaple.
 .sp
@@ -21201,17 +21201,17 @@ The expression matches records that contain a word that starts with
 \fBGood\-bye Tritonn\fP are matched with the expression.
 .SS Suffix search condition
 .sp
-Its syntax is \fBcolumn:$value\fP.
+Its syntax is \fBcolumn:$value\fP\&.
 .sp
-This conditional expression does suffix search with \fBvalue\fP. Suffix
-search searches records that contain a word that ends with \fBvalue\fP.
+This conditional expression does suffix search with \fBvalue\fP\&. Suffix
+search searches records that contain a word that ends with \fBvalue\fP\&.
 .sp
 You can use fast suffix search against a column. The column must be
 indexed and index table must be patricia trie table
 (\fBTABLE_PAT_KEY\fP) with \fBKEY_WITH_SIS\fP flag. You can also use fast
 suffix search against \fB_key\fP pseudo column of patricia trie table
 (\fBTABLE_PAT_KEY\fP) with \fBKEY_WITH_SIS\fP flag. You don\(aqt need to
-index \fB_key\fP. We recommended that you use index column based fast
+index \fB_key\fP\&. We recommended that you use index column based fast
 suffix search instead of \fB_key\fP based fast suffix search. \fB_key\fP
 based fast suffix search returns automatically registered
 substrings. (TODO: write document about suffix search and link to it
@@ -21232,7 +21232,7 @@ scan. It\(aqs not problem for small records but it spends more time for
 large records.
 .sp
 It doesn\(aqt require the default match columns such as \fBfull text
-search condition\fP and \fBphrase search condition\fP.
+search condition\fP and \fBphrase search condition\fP\&.
 .sp
 Here is a simple exmaple. It uses fast suffix search for hiragana in
 Japanese that is one of non\-ASCII characters.
@@ -21302,12 +21302,12 @@ in \fBcontent\fP column value. \fBぐるんが\fP and \fBむるんが\fP are mat
 with the expression.
 .SS Equal condition
 .sp
-Its syntax is \fBcolumn:value\fP.
+Its syntax is \fBcolumn:value\fP\&.
 .sp
-It matches records that \fBcolumn\fP value is equal to \fBvalue\fP.
+It matches records that \fBcolumn\fP value is equal to \fBvalue\fP\&.
 .sp
 It doesn\(aqt require the default match columns such as \fBfull text
-search condition\fP and \fBphrase search condition\fP.
+search condition\fP and \fBphrase search condition\fP\&.
 .sp
 Here is a simple exmaple.
 .sp
@@ -21362,15 +21362,15 @@ select Entries \-\-query _key:Groonga
 .UNINDENT
 .sp
 The expression matches records that \fB_key\fP column value is
-equal to \fBGroonga\fP.
+equal to \fBGroonga\fP\&.
 .SS Not equal condition
 .sp
-Its syntax is \fBcolumn:!value\fP.
+Its syntax is \fBcolumn:!value\fP\&.
 .sp
-It matches records that \fBcolumn\fP value isn\(aqt equal to \fBvalue\fP.
+It matches records that \fBcolumn\fP value isn\(aqt equal to \fBvalue\fP\&.
 .sp
 It doesn\(aqt require the default match columns such as \fBfull text
-search condition\fP and \fBphrase search condition\fP.
+search condition\fP and \fBphrase search condition\fP\&.
 .sp
 Here is a simple exmaple.
 .sp
@@ -21443,12 +21443,12 @@ select Entries \-\-query _key:!Groonga
 .UNINDENT
 .sp
 The expression matches records that \fB_key\fP column value is not equal
-to \fBGroonga\fP.
+to \fBGroonga\fP\&.
 .SS Less than condition
 .sp
-Its syntax is \fBcolumn:<value\fP.
+Its syntax is \fBcolumn:<value\fP\&.
 .sp
-It matches records that \fBcolumn\fP value is less than \fBvalue\fP.
+It matches records that \fBcolumn\fP value is less than \fBvalue\fP\&.
 .sp
 If \fBcolumn\fP type is numerical type such as \fBInt32\fP, \fBcolumn\fP
 value and \fBvalue\fP are compared as number. If \fBcolumn\fP type is text
@@ -21456,7 +21456,7 @@ type such as \fBShortText\fP, \fBcolumn\fP value and \fBvalue\fP are
 compared as bit sequence.
 .sp
 It doesn\(aqt require the default match columns such as \fBfull text
-search condition\fP and \fBphrase search condition\fP.
+search condition\fP and \fBphrase search condition\fP\&.
 .sp
 Here is a simple exmaple.
 .sp
@@ -21523,12 +21523,12 @@ select Entries \-\-query n_likes:<10
 .UNINDENT
 .sp
 The expression matches records that \fBn_likes\fP column value is less
-than \fB10\fP.
+than \fB10\fP\&.
 .SS Greater than condition
 .sp
-Its syntax is \fBcolumn:>value\fP.
+Its syntax is \fBcolumn:>value\fP\&.
 .sp
-It matches records that \fBcolumn\fP value is greater than \fBvalue\fP.
+It matches records that \fBcolumn\fP value is greater than \fBvalue\fP\&.
 .sp
 If \fBcolumn\fP type is numerical type such as \fBInt32\fP, \fBcolumn\fP
 value and \fBvalue\fP are compared as number. If \fBcolumn\fP type is text
@@ -21536,7 +21536,7 @@ type such as \fBShortText\fP, \fBcolumn\fP value and \fBvalue\fP are
 compared as bit sequence.
 .sp
 It doesn\(aqt require the default match columns such as \fBfull text
-search condition\fP and \fBphrase search condition\fP.
+search condition\fP and \fBphrase search condition\fP\&.
 .sp
 Here is a simple exmaple.
 .sp
@@ -21591,13 +21591,13 @@ select Entries \-\-query n_likes:>10
 .UNINDENT
 .sp
 The expression matches records that \fBn_likes\fP column value is greater
-than \fB10\fP.
+than \fB10\fP\&.
 .SS Less than or equal to condition
 .sp
-Its syntax is \fBcolumn:<=value\fP.
+Its syntax is \fBcolumn:<=value\fP\&.
 .sp
 It matches records that \fBcolumn\fP value is less than or equal to
-\fBvalue\fP.
+\fBvalue\fP\&.
 .sp
 If \fBcolumn\fP type is numerical type such as \fBInt32\fP, \fBcolumn\fP
 value and \fBvalue\fP are compared as number. If \fBcolumn\fP type is text
@@ -21605,7 +21605,7 @@ type such as \fBShortText\fP, \fBcolumn\fP value and \fBvalue\fP are
 compared as bit sequence.
 .sp
 It doesn\(aqt require the default match columns such as \fBfull text
-search condition\fP and \fBphrase search condition\fP.
+search condition\fP and \fBphrase search condition\fP\&.
 .sp
 Here is a simple exmaple.
 .sp
@@ -21678,13 +21678,13 @@ select Entries \-\-query n_likes:<=10
 .UNINDENT
 .sp
 The expression matches records that \fBn_likes\fP column value is less
-than or equal to \fB10\fP.
+than or equal to \fB10\fP\&.
 .SS Greater than or equal to condition
 .sp
-Its syntax is \fBcolumn:>=value\fP.
+Its syntax is \fBcolumn:>=value\fP\&.
 .sp
 It matches records that \fBcolumn\fP value is greater than or equal to
-\fBvalue\fP.
+\fBvalue\fP\&.
 .sp
 If \fBcolumn\fP type is numerical type such as \fBInt32\fP, \fBcolumn\fP
 value and \fBvalue\fP are compared as number. If \fBcolumn\fP type is text
@@ -21692,7 +21692,7 @@ type such as \fBShortText\fP, \fBcolumn\fP value and \fBvalue\fP are
 compared as bit sequence.
 .sp
 It doesn\(aqt require the default match columns such as \fBfull text
-search condition\fP and \fBphrase search condition\fP.
+search condition\fP and \fBphrase search condition\fP\&.
 .sp
 Here is a simple exmaple.
 .sp
@@ -21753,13 +21753,13 @@ select Entries \-\-query n_likes:>=10
 .UNINDENT
 .sp
 The expression matches records that \fBn_likes\fP column value is
-greater than or equal to \fB10\fP.
+greater than or equal to \fB10\fP\&.
 .SS Combined expression
 .sp
 Here is available combined expression list.
 .SS Logical OR
 .sp
-Its syntax is \fBa OR b\fP.
+Its syntax is \fBa OR b\fP\&.
 .sp
 \fBa\fP and \fBb\fP are conditional expressions, conbinded expressions or
 assignment expressions.
@@ -21829,14 +21829,14 @@ greater than \fB10\fP or contain a word \fBsenna\fP in \fBcontent\fP column
 value.
 .SS Logical AND
 .sp
-Its syntax is \fBa + b\fP or just \fBa b\fP.
+Its syntax is \fBa + b\fP or just \fBa b\fP\&.
 .sp
 \fBa\fP and \fBb\fP are conditional expressions, conbinded expressions or
 assignment expressions.
 .sp
 If both \fBa\fP and \fBb\fP are matched, \fBa + b\fP is matched.
 .sp
-You can specify \fB+\fP the first expression such as \fB+a\fP. The \fB+\fP
+You can specify \fB+\fP the first expression such as \fB+a\fP\&. The \fB+\fP
 is just ignored.
 .sp
 Here is a simple exmaple.
@@ -21896,14 +21896,14 @@ greater than or equal to \fB10\fP and contain a word \fBgroonga\fP in
 \fBcontent\fP column value.
 .SS Logical NOT
 .sp
-Its syntax is \fBa \- b\fP.
+Its syntax is \fBa \- b\fP\&.
 .sp
 \fBa\fP and \fBb\fP are conditional expressions, conbinded expressions or
 assignment expressions.
 .sp
 If \fBa\fP is matched and \fBb\fP is not matched, \fBa \- b\fP is matched.
 .sp
-You can not specify \fB\-\fP the first expression such as \fB\-a\fP. It\(aqs
+You can not specify \fB\-\fP the first expression such as \fB\-a\fP\&. It\(aqs
 syntax error.
 .sp
 Here is a simple exmaple.
@@ -21963,7 +21963,7 @@ greater than or equal to \fB10\fP and don\(aqt contain a word \fBgroonga\fP in
 \fBcontent\fP column value.
 .SS Grouping
 .sp
-Its syntax is \fB(...)\fP. \fB...\fP is space separated expression list.
+Its syntax is \fB(...)\fP\&. \fB\&...\fP is space separated expression list.
 .sp
 \fB(...)\fP groups one ore more expressions and they can be
 processed as an expression. \fBa b OR c\fP means that \fBa\fP and \fBb\fP
@@ -22091,9 +22091,9 @@ Assignment expression in query syntax has some limitations. So you
 should use \fB/reference/grn_expr/script_syntax\fP instead of query syntax for
 assignment.
 .sp
-There is only one syntax for assignment expression. It\(aqs \fBcolumn:=value\fP.
+There is only one syntax for assignment expression. It\(aqs \fBcolumn:=value\fP\&.
 .sp
-\fBvalue\fP is assigend to \fBcolumn\fP. \fBvalue\fP is always processed as
+\fBvalue\fP is assigend to \fBcolumn\fP\&. \fBvalue\fP is always processed as
 string in query syntax. \fBvalue\fP is casted to the type of \fBcolumn\fP
 automatically. It causes some limitations. For example, you cannot use
 boolean literal such as \fBtrue\fP and \fBfalse\fP for \fBBool\fP type
@@ -22105,7 +22105,7 @@ See \fB/reference/cast\fP about cast.
 .sp
 Script syntax is a syntax to specify complex search condition. It is
 similar to ECMAScript. For example, \fB_key == "book"\fP means that
-groonga searches records that \fB_key\fP value is \fB"book"\fP. All values
+groonga searches records that \fB_key\fP value is \fB"book"\fP\&. All values
 are string in \fBquery_syntax\fP but its own type in script
 syntax. For example, \fB"book"\fP is string, \fB1\fP is integer,
 \fBTokenBigram\fP is the object whose name is \fBTokenBigram\fP and so on.
@@ -22164,7 +22164,7 @@ load \-\-table Entries
 .sp
 There is a table, \fBEntries\fP, for blog entries. An entry has title,
 content and the number of likes for the entry. Title is key of
-\fBEntries\fP. Content is value of \fBEntries.content\fP column. The
+\fBEntries\fP\&. Content is value of \fBEntries.content\fP column. The
 number of likes is value of \fBEntries.n_likes\fP column.
 .sp
 \fBEntries._key\fP column and \fBEntries.content\fP column are indexed
@@ -22176,8 +22176,8 @@ OK. The schema and data for examples are ready.
 .SS Integer
 .sp
 Integer literal is sequence of \fB0\fP to \fB9\fP such as
-\fB1234567890\fP. \fB+\fP or \fB\-\fP can be prepended as sign such as
-\fB+29\fP and \fB\-29\fP. Integer literal must be decimal. Octal notation,
+\fB1234567890\fP\&. \fB+\fP or \fB\-\fP can be prepended as sign such as
+\fB+29\fP and \fB\-29\fP\&. Integer literal must be decimal. Octal notation,
 hex and so on can\(aqt be used.
 .sp
 The maximum value of integer literal is \fB9223372036854775807\fP (\fB= 2
@@ -22185,15 +22185,15 @@ The maximum value of integer literal is \fB9223372036854775807\fP (\fB= 2
 \fB\-9223372036854775808\fP (\fB= \-(2 ** 63)\fP).
 .SS Float
 .sp
-Float literal is sequence of \fB0\fP to \fB9\fP, \fB.\fP and \fB0\fP to \fB9\fP
-such as \fB3.14\fP. \fB+\fP or \fB\-\fP can be prepended as sign such as
-\fB+3.14\fP and \fB\-3.14\fP. \fB${RADIX}e${EXPORNENTIAL}\fP and
+Float literal is sequence of \fB0\fP to \fB9\fP, \fB\&.\fP and \fB0\fP to \fB9\fP
+such as \fB3.14\fP\&. \fB+\fP or \fB\-\fP can be prepended as sign such as
+\fB+3.14\fP and \fB\-3.14\fP\&. \fB${RADIX}e${EXPORNENTIAL}\fP and
 \fB${RADIX}E${EXPORNENTIAL}\fP formats are also supported. For example,
-\fB314e\-2\fP is the same as \fB3.14\fP.
+\fB314e\-2\fP is the same as \fB3.14\fP\&.
 .SS String
 .sp
-String literal is \fB"..."\fP. You need to escape \fB"\fP in literal by
-prepending \fB\e\e\(aq\(aq such as \(ga\(ga\e"\fP. For example, \fB"Say \e"Hello!\e"."\fP is
+String literal is \fB"..."\fP\&. You need to escape \fB"\fP in literal by
+prepending \fB\e\e\(aq\(aq such as \(ga\(ga\e"\fP\&. For example, \fB"Say \e"Hello!\e"."\fP is
 a literal for \fBSay "Hello!".\fP string.
 .sp
 String encoding must be the same as encoding of database. The default
@@ -22202,11 +22202,11 @@ configure option, \fB\-\-encodiong\fP \fB/reference/executables/groonga\fP optio
 and so on.
 .SS Boolean
 .sp
-Boolean literal is \fBtrue\fP and \fBfalse\fP. \fBtrue\fP means true and
+Boolean literal is \fBtrue\fP and \fBfalse\fP\&. \fBtrue\fP means true and
 \fBfalse\fP means false.
 .SS Null
 .sp
-Null literal is \fBnull\fP. Groonga doesn\(aqt support null value but null
+Null literal is \fBnull\fP\&. Groonga doesn\(aqt support null value but null
 literal is supported.
 .SS Time
 .sp
@@ -22221,7 +22221,7 @@ Time literal doesn\(aqt exit. There are string time notation, integer
 time notation and float time notation.
 .sp
 String time notation is \fB"YYYY/MM/DD hh:mm:ss.uuuuuu"\fP or
-\fB"YYYY\-MM\-DD hh:mm:ss.uuuuuu"\fP. \fBYYYY\fP is year, \fBMM\fP is month,
+\fB"YYYY\-MM\-DD hh:mm:ss.uuuuuu"\fP\&. \fBYYYY\fP is year, \fBMM\fP is month,
 \fBDD\fP is day, \fBhh\fP is hour, \fBmm\fP is minute, \fBss\fP is second and
 \fBuuuuuu\fP is micro second. It is local time. For example,
 \fB"2012/07/23 02:41:10.436218"\fP is \fB2012\-07\-23T02:41:10.436218\fP in
@@ -22266,15 +22266,15 @@ String geo point notation has the following patterns:
 be represented in milliseconds or degree.
 .SS Array
 .sp
-Array literal is \fB[element1, element2, ...]\fP.
+Array literal is \fB[element1, element2, ...]\fP\&.
 .SS Object literal
 .sp
-Object literal is \fB{name1: value1, name2: value2, ...}\fP. Groonga
+Object literal is \fB{name1: value1, name2: value2, ...}\fP\&. Groonga
 doesn\(aqt support object literal yet.
 .SS Control syntaxes
 .sp
 Script syntax doesn\(aqt support statement. So you cannot use control
-statement such as \fBif\fP. You can only use \fBA ? B : C\fP expression as
+statement such as \fBif\fP\&. You can only use \fBA ? B : C\fP expression as
 control syntax.
 .sp
 \fBA ? B : C\fP returns \fBB\fP if \fBA\fP is true, \fBC\fP otherwise.
@@ -22345,10 +22345,10 @@ select Entries \-\-filter \(aqn_likes == (_id == 1 ? 5 : 3)\(aq
 .sp
 The expression matches records that \fB_id\fP column value is equal to \fB1\fP
 and \fBn_likes\fP column value is equal to \fB5\fP or \fB_id\fP column value is
-not equal to 1 and \fBn_likes\fP column value is equal to \fB3\fP.
+not equal to 1 and \fBn_likes\fP column value is equal to \fB3\fP\&.
 .SS Grouping
 .sp
-Its syntax is \fB(...)\fP. \fB...\fP is comma separated expression list.
+Its syntax is \fB(...)\fP\&. \fB\&...\fP is comma separated expression list.
 .sp
 \fB(...)\fP groups one ore more expressions and they can be processed as
 an expression. \fBa && b || c\fP means that \fBa\fP and \fBb\fP are matched
@@ -22467,10 +22467,10 @@ The second expression uses grouping. It matches records that \fBn_likes
 matched.
 .SS Function call
 .sp
-Its syntax is \fBname(arugment1, argument2, ...)\fP.
+Its syntax is \fBname(arugment1, argument2, ...)\fP\&.
 .sp
 \fBname(argument1, argument2, ...)\fP calls a function that is named
-\fBname\fP with arguments \fBargument1\fP, \fBargument2\fP and \fB...\fP.
+\fBname\fP with arguments \fBargument1\fP, \fBargument2\fP and \fB\&...\fP\&.
 .sp
 See \fB/reference/function\fP for available functin list.
 .sp
@@ -22532,9 +22532,9 @@ select Entries \-\-filter \(aqedit_distance(_key, "Groonga") <= 1\(aq
 .UNINDENT
 .UNINDENT
 .sp
-The expression uses \fB/reference/functions/edit_distance\fP. It
+The expression uses \fB/reference/functions/edit_distance\fP\&. It
 matches records that \fB_key\fP column value is similar to
-\fB"Groonga"\fP. Similality of \fB"Groonga"\fP is computed as edit
+\fB"Groonga"\fP\&. Similality of \fB"Groonga"\fP is computed as edit
 distance. If edit distance is less than or equal to 1, the value is
 treated as similar. In this case, \fB"Groonga"\fP and \fB"Mroonga"\fP are
 treated as similar.
@@ -22546,7 +22546,7 @@ Groonga supports operators defined in ECMAScript.
 Here are arithmetic operators.
 .SS Addition operator
 .sp
-Its syntax is \fBnumber1 + number2\fP.
+Its syntax is \fBnumber1 + number2\fP\&.
 .sp
 The operator adds \fBnumber1\fP and \fBnumber2\fP and returns the result.
 .sp
@@ -22606,7 +22606,7 @@ The expression matches records that \fBn_likes\fP column value is equal
 to \fB15\fP (= \fB10 + 5\fP).
 .SS Subtraction operator
 .sp
-Its syntax is \fBnumber1 \- number2\fP.
+Its syntax is \fBnumber1 \- number2\fP\&.
 .sp
 The operator subtracts \fBnumber2\fP from \fBnumber1\fP and returns the result.
 .sp
@@ -22666,7 +22666,7 @@ The expression matches records that \fBn_likes\fP column value is equal
 to \fB15\fP (= \fB20 \- 5\fP).
 .SS Multiplication operator
 .sp
-Its syntax is \fBnumber1 * number2\fP.
+Its syntax is \fBnumber1 * number2\fP\&.
 .sp
 The operator multiplies \fBnumber1\fP and \fBnumber2\fP and returns the result.
 .sp
@@ -22726,9 +22726,9 @@ The expression matches records that \fBn_likes\fP column value is equal
 to \fB15\fP (= \fB3 * 5\fP).
 .SS Division operator
 .sp
-Its syntax is \fBnumber1 / number2\fP and \fBnumber1 % number2\fP.
+Its syntax is \fBnumber1 / number2\fP and \fBnumber1 % number2\fP\&.
 .sp
-The operator divides \fBnumber2\fP by \fBnumber1\fP. \fB/\fP returns the
+The operator divides \fBnumber2\fP by \fBnumber1\fP\&. \fB/\fP returns the
 quotient of result. \fB%\fP returns the remainder of result.
 .sp
 Here is simple examples.
@@ -22849,9 +22849,9 @@ to \fB5\fP (= \fB26 % 7\fP).
 Here are logical operators.
 .SS Logical NOT operator
 .sp
-Its syntax is \fB!condition\fP.
+Its syntax is \fB!condition\fP\&.
 .sp
-The operator inverts boolean value of \fBcondition\fP.
+The operator inverts boolean value of \fBcondition\fP\&.
 .sp
 Here is a simple example.
 .sp
@@ -22924,10 +22924,10 @@ select Entries \-\-filter \(aq!(n_likes == 5)\(aq
 .UNINDENT
 .sp
 The expression matches records that \fBn_likes\fP column value is not
-equal to \fB5\fP.
+equal to \fB5\fP\&.
 .SS Logical AND operator
 .sp
-Its syntax is \fBcondition1 && condition2\fP.
+Its syntax is \fBcondition1 && condition2\fP\&.
 .sp
 The operator returns true if both of \fBcondition1\fP and
 \fBcondition2\fP are true, false otherwise.
@@ -22992,10 +22992,10 @@ select Entries \-\-filter \(aqcontent @ "fast" && n_likes >= 10\(aq
 .sp
 The expression matches records that \fBcontent\fP column value has the
 word \fBfast\fP and \fBn_likes\fP column value is greater or equal to
-\fB10\fP.
+\fB10\fP\&.
 .SS Logical OR operator
 .sp
-Its syntax is \fBcondition1 || condition2\fP.
+Its syntax is \fBcondition1 || condition2\fP\&.
 .sp
 The operator returns true if either \fBcondition1\fP or \fBcondition2\fP is
 true, false otherwise.
@@ -23059,10 +23059,10 @@ select Entries \-\-filter \(aqn_likes == 5 || n_likes == 10\(aq
 .UNINDENT
 .sp
 The expression matches records that \fBn_likes\fP column value is equal
-to \fB5\fP or \fB10\fP.
+to \fB5\fP or \fB10\fP\&.
 .SS Logical AND NOT operator
 .sp
-Its syntax is \fBcondition1 &! condition2\fP.
+Its syntax is \fBcondition1 &! condition2\fP\&.
 .sp
 The operator returns true if \fBcondition1\fP is true but \fBcondition2\fP
 is false, false otherwise. It returns difference set.
@@ -23120,15 +23120,15 @@ select Entries \-\-filter \(aqcontent @ "fast" &! content @ "mroonga"\(aq
 .UNINDENT
 .sp
 The expression matches records that \fBcontent\fP column value has the
-word \fBfast\fP but doesn\(aqt have the word \fBmroonga\fP.
+word \fBfast\fP but doesn\(aqt have the word \fBmroonga\fP\&.
 .SS Bitwise operators
 .sp
 Here are bitwise operators.
 .SS Bitwise NOT operator
 .sp
-Its syntax is \fB~number\fP.
+Its syntax is \fB~number\fP\&.
 .sp
-The operator returns bitwise NOT of \fBnumber\fP.
+The operator returns bitwise NOT of \fBnumber\fP\&.
 .sp
 Here is a simple example.
 .sp
@@ -23183,12 +23183,12 @@ select Entries \-\-filter \(aq~n_likes == \-6\(aq
 .UNINDENT
 .sp
 The expression matches records that \fBn_likes\fP column value is equal
-to \fB5\fP because bitwise NOT of \fB5\fP is equal to \fB\-6\fP.
+to \fB5\fP because bitwise NOT of \fB5\fP is equal to \fB\-6\fP\&.
 .SS Bitwise AND operator
 .sp
-Its syntax is \fBnumber1 & number2\fP.
+Its syntax is \fBnumber1 & number2\fP\&.
 .sp
-The operator returns bitwise AND between \fBnumber1\fP and \fBnumber2\fP.
+The operator returns bitwise AND between \fBnumber1\fP and \fBnumber2\fP\&.
 .sp
 Here is a simple example.
 .sp
@@ -23263,12 +23263,12 @@ select Entries \-\-filter \(aq(n_likes & 1) == 1\(aq
 The expression matches records that \fBn_likes\fP column value is even
 number because bitwise AND between an even number and \fB1\fP is equal
 to \fB1\fP and bitwise AND between an odd number and \fB1\fP is equal to
-\fB0\fP.
+\fB0\fP\&.
 .SS Bitwise OR operator
 .sp
-Its syntax is \fBnumber1 | number2\fP.
+Its syntax is \fBnumber1 | number2\fP\&.
 .sp
-The operator returns bitwise OR between \fBnumber1\fP and \fBnumber2\fP.
+The operator returns bitwise OR between \fBnumber1\fP and \fBnumber2\fP\&.
 .sp
 Here is a simple example.
 .sp
@@ -23326,9 +23326,9 @@ The expression matches records that \fBn_likes\fP column value is equal
 to \fB5\fP (= \fB1 | 4\fP).
 .SS Bitwise XOR operator
 .sp
-Its syntax is \fBnumber1 ^ number2\fP.
+Its syntax is \fBnumber1 ^ number2\fP\&.
 .sp
-The operator returns bitwise XOR between \fBnumber1\fP and \fBnumber2\fP.
+The operator returns bitwise XOR between \fBnumber1\fP and \fBnumber2\fP\&.
 .sp
 Here is a simple example.
 .sp
@@ -23389,10 +23389,10 @@ to \fB5\fP (= \fB10 ^ 15\fP).
 Here are shift operators.
 .SS Left shift operator
 .sp
-Its syntax is \fBnumber1 << number2\fP.
+Its syntax is \fBnumber1 << number2\fP\&.
 .sp
 The operator performs a bitwise left shift operation on \fBnumber1\fP by
-\fBnumber2\fP.
+\fBnumber2\fP\&.
 .sp
 Here is a simple example.
 .sp
@@ -23450,10 +23450,10 @@ The expression matches records that \fBn_likes\fP column value is equal
 to \fB10\fP (= \fB5 << 1\fP).
 .SS Signed right shift operator
 .sp
-Its syntax is \fBnumber1 >> number2\fP.
+Its syntax is \fBnumber1 >> number2\fP\&.
 .sp
-The operator shifts bits of \fBnumber1\fP to right by \fBnumber2\fP. The sign
-of the result is the same as \fBnumber1\fP.
+The operator shifts bits of \fBnumber1\fP to right by \fBnumber2\fP\&. The sign
+of the result is the same as \fBnumber1\fP\&.
 .sp
 Here is a simple example.
 .sp
@@ -23511,10 +23511,10 @@ The expression matches records that \fBn_likes\fP column value is equal
 to \fB5\fP (= \fB\-(\-10 >> 1)\fP = \fB\-(\-5)\fP).
 .SS Unsigned right shift operator
 .sp
-Its syntax is \fBnumber1 >>> number2\fP.
+Its syntax is \fBnumber1 >>> number2\fP\&.
 .sp
-The operator shifts bits of \fBnumber1\fP to right by \fBnumber2\fP. The
-leftmost \fBnumber2\fP bits are filled by \fB0\fP.
+The operator shifts bits of \fBnumber1\fP to right by \fBnumber2\fP\&. The
+leftmost \fBnumber2\fP bits are filled by \fB0\fP\&.
 .sp
 Here is a simple example.
 .sp
@@ -23575,7 +23575,7 @@ to \fB5\fP (= \fB2147483648 \- (\-10 >>> 1)\fP = \fB2147483648 \- 2147483643\fP)
 Here are comparison operators.
 .SS Equal operator
 .sp
-Its syntax is \fBobject1 == object2\fP.
+Its syntax is \fBobject1 == object2\fP\&.
 .sp
 The operator returns true if \fBobject1\fP equals to \fBobject2\fP, false
 otherwise.
@@ -23633,10 +23633,10 @@ select Entries \-\-filter \(aqn_likes == 5\(aq
 .UNINDENT
 .sp
 The expression matches records that \fBn_likes\fP column value is equal
-to \fB5\fP.
+to \fB5\fP\&.
 .SS Not equal operator
 .sp
-Its syntax is \fBobject1 != object2\fP.
+Its syntax is \fBobject1 != object2\fP\&.
 .sp
 The operator returns true if \fBobject1\fP does not equal to
 \fBobject2\fP, false otherwise.
@@ -23712,7 +23712,7 @@ select Entries \-\-filter \(aqn_likes != 5\(aq
 .UNINDENT
 .sp
 The expression matches records that \fBn_likes\fP column value is not
-equal to \fB5\fP.
+equal to \fB5\fP\&.
 .SS Less than operator
 .sp
 TODO: ...
@@ -23728,7 +23728,7 @@ TODO: ...
 .SS Assignment operators
 .SS Addition assignment operator
 .sp
-Its syntax is \fBcolumn1 += column2\fP.
+Its syntax is \fBcolumn1 += column2\fP\&.
 .sp
 The operator performs addition assginment operation on column1 by column2.
 .sp
@@ -23806,7 +23806,7 @@ is 3.
 So the expression \fB1 + 3\fP is evaluated and stored to \fB_score\fP column as the execution result.
 .SS Subtraction assignment operator
 .sp
-Its syntax is \fBcolumn1 \-= column2\fP.
+Its syntax is \fBcolumn1 \-= column2\fP\&.
 .sp
 The operator performs subtraction assginment operation on column1 by column2.
 .sp
@@ -23884,7 +23884,7 @@ is 3.
 So the expression \fB1 \- 3\fP is evaluated and stored to \fB_score\fP column as the execution result.
 .SS Multiplication assignment operator
 .sp
-Its syntax is \fBcolumn1 *= column2\fP.
+Its syntax is \fBcolumn1 *= column2\fP\&.
 .sp
 The operator performs multiplication assginment operation on column1 by column2.
 .sp
@@ -23962,7 +23962,7 @@ is 3.
 So the expression \fB1 * 3\fP is evaluated and stored to \fB_score\fP column as the execution result.
 .SS Division assignment operator
 .sp
-Its syntax is \fBcolumn1 /= column2\fP.
+Its syntax is \fBcolumn1 /= column2\fP\&.
 .sp
 The operator performs division assginment operation on column1 by column2.
 .sp
@@ -24040,7 +24040,7 @@ is 3.
 So the expression \fB1 / 3\fP is evaluated and stored to \fB_score\fP column as the execution result.
 .SS Modulo assignment operator
 .sp
-Its syntax is \fBcolumn1 %= column2\fP.
+Its syntax is \fBcolumn1 %= column2\fP\&.
 .sp
 The operator performs modulo assginment operation on column1 by column2.
 .sp
@@ -24118,7 +24118,7 @@ is 3.
 So the expression \fB1 % 3\fP is evaluated and stored to \fB_score\fP column as the execution result.
 .SS Bitwise left shift assignment operator
 .sp
-Its syntax is \fBcolumn1 <<= column2\fP.
+Its syntax is \fBcolumn1 <<= column2\fP\&.
 .sp
 The operator performs left shift assginment operation on column1 by column2.
 .sp
@@ -24196,17 +24196,17 @@ is 3.
 So the expression \fB1 << 3\fP is evaluated and stored to \fB_score\fP column as the execution result.
 .SS Bitwise signed right shift assignment operator
 .sp
-Its syntax is \fBcolumn2 >>= column2\fP.
+Its syntax is \fBcolumn2 >>= column2\fP\&.
 .sp
 The operator performs signed right shift assginment operation on column1 by column2.
 .SS Bitwise unsigned right shift assignment operator
 .sp
-Its syntax is \fBcolumn1 >>>= column2\fP.
+Its syntax is \fBcolumn1 >>>= column2\fP\&.
 .sp
 The operator performs unsigned right shift assginment operation on column1 by column2.
 .SS Bitwise AND assignment operator
 .sp
-Its syntax is \fBcolumn1 &= column2\fP.
+Its syntax is \fBcolumn1 &= column2\fP\&.
 .sp
 The operator performs bitwise AND assignment operation on column1 by column2.
 .sp
@@ -24284,7 +24284,7 @@ is 10.
 So the expression \fB1 & 10\fP is evaluated and stored to \fB_score\fP column as the execution result.
 .SS Bitwise OR assignment operator
 .sp
-Its syntax is \fBcolumn1 |= column2\fP.
+Its syntax is \fBcolumn1 |= column2\fP\&.
 .sp
 The operator performs bitwise OR assignment operation on column1 by column2.
 .sp
@@ -24362,7 +24362,7 @@ is 10.
 So the expression \fB1 | 10\fP is evaluated and stored to \fB_score\fP column as the execution result.
 .SS Bitwise XOR assignment operator
 .sp
-Its syntax is \fBcolumn1 ^= column2\fP.
+Its syntax is \fBcolumn1 ^= column2\fP\&.
 .sp
 The operator performs bitwise XOR assginment operation on column1 by column2.
 .sp
@@ -24442,12 +24442,12 @@ So the expression \fB1 ^ 3\fP is evaluated and stored to \fB_score\fP column as
 .sp
 Script syntax adds the original binary opearators to ECMAScript
 syntax. They operate search specific operations. They are starts with
-\fB@\fP or \fB*\fP.
+\fB@\fP or \fB*\fP\&.
 .SS Match operator
 .sp
-Its syntax is \fBcolumn @ value\fP.
+Its syntax is \fBcolumn @ value\fP\&.
 .sp
-The operator searches \fBvalue\fP by inverted index of \fBcolumn\fP.
+The operator searches \fBvalue\fP by inverted index of \fBcolumn\fP\&.
 Normally, full text search is operated but tag search can be operated.
 Because tag search is also implemented by inverted index.
 .sp
@@ -24497,17 +24497,17 @@ The expression matches records that contain a word \fBfast\fP in
 \fBcontent\fP column value.
 .SS Prefix search operator
 .sp
-Its syntax is \fBcolumn @^ value\fP.
+Its syntax is \fBcolumn @^ value\fP\&.
 .sp
-The operator does prefix search with \fBvalue\fP. Prefix search searches
-records that contain a word that starts with \fBvalue\fP.
+The operator does prefix search with \fBvalue\fP\&. Prefix search searches
+records that contain a word that starts with \fBvalue\fP\&.
 .sp
 You can use fast prefix search against a column. The column must be
 indexed and index table must be patricia trie table
 (\fBTABLE_PAT_KEY\fP) or double array trie table
 (\fBTABLE_DAT_KEY\fP). You can also use fast prefix search against
 \fB_key\fP pseudo column of patricia trie table or double array trie
-table. You don\(aqt need to index \fB_key\fP.
+table. You don\(aqt need to index \fB_key\fP\&.
 .sp
 Prefix search can be used with other table types but it causes all
 records scan. It\(aqs not problem for small records but it spends more
@@ -24558,17 +24558,17 @@ The expression matches records that contain a word that starts with
 \fBGood\-bye Tritonn\fP are matched with the expression.
 .SS Suffix search operator
 .sp
-Its syntax is \fBcolumn @$ value\fP.
+Its syntax is \fBcolumn @$ value\fP\&.
 .sp
-This operator does suffix search with \fBvalue\fP. Suffix search
-searches records that contain a word that ends with \fBvalue\fP.
+This operator does suffix search with \fBvalue\fP\&. Suffix search
+searches records that contain a word that ends with \fBvalue\fP\&.
 .sp
 You can use fast suffix search against a column. The column must be
 indexed and index table must be patricia trie table
 (\fBTABLE_PAT_KEY\fP) with \fBKEY_WITH_SIS\fP flag. You can also use fast
 suffix search against \fB_key\fP pseudo column of patricia trie table
 (\fBTABLE_PAT_KEY\fP) with \fBKEY_WITH_SIS\fP flag. You don\(aqt need to
-index \fB_key\fP. We recommended that you use index column based fast
+index \fB_key\fP\&. We recommended that you use index column based fast
 suffix search instead of \fB_key\fP based fast suffix search. \fB_key\fP
 based fast suffix search returns automatically registered
 substrings. (TODO: write document about suffix search and link to it
@@ -24656,9 +24656,9 @@ in \fBcontent\fP column value. \fBぐるんが\fP and \fBむるんが\fP are mat
 with the expression.
 .SS Near search operator
 .sp
-Its syntax is \fBcolumn *N "word1 word2 ..."\fP.
+Its syntax is \fBcolumn *N "word1 word2 ..."\fP\&.
 .sp
-The operator does near search with words \fBword1 word2 ...\fP. Near
+The operator does near search with words \fBword1 word2 ...\fP\&. Near
 search searches records that contain the words and the words are
 appeared in the near distance. Near distance is always \fB10\fP for
 now. The unit of near distance is the number of characters in N\-gram
@@ -24671,7 +24671,7 @@ only word into tokens. So the unit for ASCII words with
 N\-gram family tokenizer.)
 .sp
 Note that an index column for full text search must be defined for
-\fBcolumn\fP.
+\fBcolumn\fP\&.
 .sp
 Here is a simple exmaple.
 .sp
@@ -24755,14 +24755,14 @@ also very fast! Really fast!\fP is matched. The number of words between
 \fBalso\fP and \fBReally\fP is 10.
 .SS Similar search
 .sp
-Its syntax is \fBcolumn *S "document"\fP.
+Its syntax is \fBcolumn *S "document"\fP\&.
 .sp
-The operator does similar search with document \fBdocument\fP. Similar
+The operator does similar search with document \fBdocument\fP\&. Similar
 search searches records that have similar content to
-\fBdocument\fP.
+\fBdocument\fP\&.
 .sp
 Note that an index column for full text search must be defined for
-\fBcolumn\fP.
+\fBcolumn\fP\&.
 .sp
 Here is a simple exmaple.
 .sp
@@ -24805,14 +24805,14 @@ select Entries \-\-filter \(aqcontent *S "I migrated all Solr system!"\(aq \-\-o
 .UNINDENT
 .sp
 The expression matches records that have similar content to \fBI
-migrated all Solr system!\fP. In this case, records that have \fBI
+migrated all Solr system!\fP\&. In this case, records that have \fBI
 migrated all XXX system!\fP content are matched.
 .SS Term extract operator
 .sp
-Its syntax is \fB_key *T "document"\fP.
+Its syntax is \fB_key *T "document"\fP\&.
 .sp
-The operator extracts terms from \fBdocument\fP. Terms must be
-registered as keys of the table of \fB_key\fP.
+The operator extracts terms from \fBdocument\fP\&. Terms must be
+registered as keys of the table of \fB_key\fP\&.
 .sp
 Note that the table must be patricia trie (\fBTABLE_PAT_KEY\fP) or
 double array trie (\fBTABLE_DAT_KEY\fP). You can\(aqt use hash table
@@ -24871,9 +24871,9 @@ select Words \-\-filter \(aq_key *T "Groonga is the successor project to Senna."
 .UNINDENT
 .sp
 The expression extrcts terms that included in document \fBGroonga is
-the successor project to Senna.\fP. In this case, \fBKEY_NORMALIZE\fP
-flag is specified to \fBWords\fP. So \fBGroonga\fP can be extracted even
-if it is loaded as \fBgroonga\fP into \fBWords\fP. All of extracted terms
+the successor project to Senna.\fP\&. In this case, \fBKEY_NORMALIZE\fP
+flag is specified to \fBWords\fP\&. So \fBGroonga\fP can be extracted even
+if it is loaded as \fBgroonga\fP into \fBWords\fP\&. All of extracted terms
 are also normalized.
 .SS See also
 .INDENT 0.0
@@ -24888,7 +24888,7 @@ are also normalized.
 .sp
 Function can be used in some commands. For example, you can use
 function in \fB\-\-filter\fP, \fB\-\-scorer\fP and \fBoutput_columns\fP
-options of \fBcommands/select\fP.
+options of \fBcommands/select\fP\&.
 .sp
 This section describes about function and built\-in functions.
 .sp
@@ -24897,7 +24897,7 @@ TODO: Add documentations about function.
 .SS Summary
 .sp
 \fBbetween\fP is used for checking the specified value exists in the specific range.
-It is often used for combination with \fIselect\-filter\fP option in \fB/reference/commands/select\fP.
+It is often used for combination with \fIselect\-filter\fP option in \fB/reference/commands/select\fP\&.
 .SS Syntax
 .sp
 \fBbetween\fP has five parameters:
@@ -25076,7 +25076,7 @@ In the above case, it returns all the records, because 14 exists in between 13 a
 This behavior is used for checking the specified value exists or not in the table.
 .SS Parameters
 .sp
-There are five required parameters, \fBcolumn_or_value\fP, and \fBmin\fP, \fBmin_border\fP, \fBmax\fP and \fBmax_border\fP.
+There are five required parameters, \fBcolumn_or_value\fP, and \fBmin\fP, \fBmin_border\fP, \fBmax\fP and \fBmax_border\fP\&.
 .SS \fBcolumn_or_value\fP
 .sp
 It specifies a column of the table or the value.
@@ -25116,7 +25116,7 @@ edit_distance(string1, string2)
 .UNINDENT
 .SS 説明
 .sp
-groonga組込関数の一つであるedit_distanceについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
+Groonga組込関数の一つであるedit_distanceについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
 .sp
 edit_distance() 関数は、string1に指定した文字列とstring2に指定した文字列の間の編集距離を求めます。
 .SS 引数
@@ -25169,27 +25169,27 @@ geo_distance(point1, point2, approximate_type)
 .UNINDENT
 .UNINDENT
 .sp
-The default value of \fBapproximate_type\fP is \fB"rectangle"\fP.
+The default value of \fBapproximate_type\fP is \fB"rectangle"\fP\&.
 If you omit \fBapproximate_type\fP, \fBgeo_distance\fP calculates the value of
 distance as if \fB"rectangle"\fP was specified.
 .SS Usage
 .sp
-\fBgeo_distance\fP is one of the groonga builtin functions.
+\fBgeo_distance\fP is one of the Groonga builtin functions.
 .sp
 You can call a builtin function in \fB/reference/grn_expr\fP
 .sp
 \fBgeo_distance\fP function calculates the value of distance (approximate value)
-between the coordinate of \fBpoint1\fP and the coordinate of \fBpoint2\fP.
+between the coordinate of \fBpoint1\fP and the coordinate of \fBpoint2\fP\&.
 .sp
 \fBNOTE:\fP
 .INDENT 0.0
 .INDENT 3.5
-groonga provides three built in functions for calculating the value of distance.
-There are \fBgeo_distance()\fP, \fBgeo_distance2()\fP and \fBgeo_distance3()\fP.
+Groonga provides three built in functions for calculating the value of distance.
+There are \fBgeo_distance()\fP, \fBgeo_distance2()\fP and \fBgeo_distance3()\fP\&.
 The difference of them is the algorithm of calculating distance.
 \fBgeo_distance2()\fP and \fBgeo_distance3()\fP were deprecated since version 1.2.9.
-Use \fBgeo_distance(point1, point2, "sphere")\fP instead of \fBgeo_distance2(point1, point2)\fP.
-Use \fBgeo_distance(point1, point2, "ellipsoid")\fP instead of \fBgeo_distance3(point1, point2)\fP.
+Use \fBgeo_distance(point1, point2, "sphere")\fP instead of \fBgeo_distance2(point1, point2)\fP\&.
+Use \fBgeo_distance(point1, point2, "ellipsoid")\fP instead of \fBgeo_distance3(point1, point2)\fP\&.
 .UNINDENT
 .UNINDENT
 .sp
@@ -25253,7 +25253,7 @@ load \-\-table Cities
 .UNINDENT
 .UNINDENT
 .sp
-This execution example creates a table named \fBCities\fP which has one column named \fBlocation\fP.
+This execution example creates a table named \fBCities\fP which has one column named \fBlocation\fP\&.
 \fBlocation\fP column stores the value of coordinate.
 The coordinate of Tokyo is stored as sample data.
 .sp
@@ -25340,7 +25340,7 @@ load \-\-table Geo
 .UNINDENT
 .UNINDENT
 .sp
-This execution example creates a table named \fBGeo\fP which has one column named \fBdistance\fP.
+This execution example creates a table named \fBGeo\fP which has one column named \fBdistance\fP\&.
 \fBdistance\fP column stores the value of distance.
 .sp
 Execution example:
@@ -25383,7 +25383,7 @@ and the coordinate of New York to calculate distance.
 .SS Parameters
 .SS Required parameter
 .sp
-There are two required parameter, \fBpoint1\fP and \fBpoint2\fP.
+There are two required parameter, \fBpoint1\fP and \fBpoint2\fP\&.
 .SS \fBpoint1\fP
 .sp
 It specifies the start point that
@@ -25403,7 +25403,7 @@ the string indicating the coordinate.
 See \fB/reference/types\fP about GeoPoint and the coordinate.
 .SS Optional parameter
 .sp
-There is a optional parameter, \fBapproximate_type\fP.
+There is a optional parameter, \fBapproximate_type\fP\&.
 .SS \fBapproximate_type\fP
 .sp
 It specifies how to approximate the geographical features for calculating
@@ -25426,11 +25426,11 @@ You can specify the value of \fBapproximate_type\fP by one of the followings.
 \fBNOTE:\fP
 .INDENT 0.0
 .INDENT 3.5
-There is a limitation about \fBgeo_distance\fP. \fBgeo_distance\fP can not
+There is a limitation about \fBgeo_distance\fP\&. \fBgeo_distance\fP can not
 calculate the value of distance between two points across meridian,
 equator or the date line if you use \fBsphere\fP or \fBellipsoid\fP as
-approximate type. There is not such a limitation for \fBrectangle\fP.
-This is temporary limitation according to the implementation of groonga,
+approximate type. There is not such a limitation for \fBrectangle\fP\&.
+This is temporary limitation according to the implementation of Groonga,
 but it will be fixed in the future release.
 .UNINDENT
 .UNINDENT
@@ -25647,7 +25647,7 @@ The return value of \fBgeo_distance("143660000x419009000", "135960000x\-44076000
 .INDENT 3.5
 \fBgeo_distance\fP accepts the string indicating the coordinate as
 the value of \fBpoint1\fP when the value of \fBapproximate_type\fP is
-\fB"rectangle"\fP.
+\fB"rectangle"\fP\&.
 If you specified the string indicating the coordinate as the value
 of \fBpoint1\fP with \fBsphere\fP or \fBellipsoid\fP, \fBgeo_distance\fP
 returns 0 as the value of distance.
@@ -25659,7 +25659,7 @@ This parameter require to approximate the geographical features
 by spherical approximation for calculating the distance.
 .sp
 It is slower than \fBrectangle\fP, but the error of distance becomes
-smaller than \fBrectangle\fP.
+smaller than \fBrectangle\fP\&.
 .sp
 You can also specify \fBsphr\fP as abbrev expression.
 .sp
@@ -25706,7 +25706,7 @@ by ellipsoid approximation for calculating the distance.
 .sp
 It uses the calculation of distance by the formula of Hubeny.
 It is slower than \fBsphere\fP, but the error of distance becomes
-smaller than \fBsphere\fP.
+smaller than \fBsphere\fP\&.
 .sp
 You can also specify \fBellip\fP as abbrev expression.
 .sp
@@ -25770,7 +25770,7 @@ geo_in_circle(point, center, radious_or_point[, approximate_type])
 .UNINDENT
 .SS 説明
 .sp
-groonga組込関数の一つであるgeo_in_circleについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
+Groonga組込関数の一つであるgeo_in_circleについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
 .sp
 geo_in_circle() 関数は、pointに指定した座標が、centerに指定した座標を中心とする円の範囲内にあるかどうかを調べます。
 .SS 引数
@@ -25867,7 +25867,7 @@ geo_in_rectangle(point, top_left, bottom_right)
 .UNINDENT
 .SS 説明
 .sp
-groonga組込関数の一つであるgeo_in_rectangleについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
+Groonga組込関数の一つであるgeo_in_rectangleについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
 .sp
 geo_in_rectangle() 関数は、pointに指定した座標が、top_leftとbottom_rightがなす矩形の範囲内にあるかどうかを調べます。
 .SS 引数
@@ -25915,10 +25915,10 @@ TokyoGeoPoint(日本測地系座標)かWGS84GeoPoint(世界測地系座標)の
 .sp
 \fBhtml_untag\fP strips HTML tags from HTML and outputs plain text.
 .sp
-\fBhtml_untag\fP is used in \fB\-\-output_columns\fP described at \fIoutput_columns\fP.
+\fBhtml_untag\fP is used in \fB\-\-output_columns\fP described at \fIoutput_columns\fP\&.
 .SS Syntax
 .sp
-\fBhtml_untag\fP requires only one argument. It is \fBhtml\fP.
+\fBhtml_untag\fP requires only one argument. It is \fBhtml\fP\&.
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -25931,7 +25931,7 @@ html_untag(html)
 .UNINDENT
 .SS Requirements
 .sp
-\fBhtml_untag\fP requires groonga 3.0.5 or later.
+\fBhtml_untag\fP requires Groonga 3.0.5 or later.
 .sp
 \fBhtml_untag\fP requires \fB/reference/command/command_version\fP 2 or
 later.
@@ -26019,7 +26019,7 @@ When executing the above query, you can see "span" tag with "class" attribute is
 Note that you must specify \fB\-\-command_version 2\fP to use \fBhtml_untag\fP function.
 .SS Parameters
 .sp
-There is one required parameter, \fBhtml\fP.
+There is one required parameter, \fBhtml\fP\&.
 .SS \fBhtml\fP
 .sp
 It specifies HTML text to be untagged.
@@ -26043,7 +26043,7 @@ now()
 .UNINDENT
 .SS 説明
 .sp
-groonga組込関数の一つであるnowについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
+Groonga組込関数の一つであるnowについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
 .sp
 now() 関数は現在時刻に対応するTime型の値を返します。
 .SS 返値
@@ -26067,16 +26067,16 @@ now()
 \fBquery\fP provides \fB\-\-match_columns\fP and \fB\-\-query\fP parameters of
 \fB/reference/commands/select\fP feature as function. You can specify
 multiple \fBquery\fP functions in \fB\-\-filter\fP parameter in
-\fB/reference/commands/select\fP.
+\fB/reference/commands/select\fP\&.
 .sp
 Because of such flexibility, you can control full text search behavior
 by combination of multiple \fBquery\fP functions.
 .sp
 \fBquery\fP can be used in only \fB\-\-filter\fP in
-\fB/reference/commands/select\fP.
+\fB/reference/commands/select\fP\&.
 .SS Syntax
 .sp
-\fBquery\fP requires two arguments \- \fBmatch_columns\fP and \fBquery_string\fP.
+\fBquery\fP requires two arguments \- \fBmatch_columns\fP and \fBquery_string\fP\&.
 .sp
 The parameter \fBquery_expander\fP or \fBsubstitution_table\fP is optional.
 .INDENT 0.0
@@ -26154,7 +26154,7 @@ load \-\-table Users
 .sp
 Here is the simple usage of \fBquery\fP function which execute full text
 search by keyword \(aqalice\(aq without using \fB\-\-match_columns\fP and
-\fB\-\-query\fP arguments in \fB\-\-filter\fP.
+\fB\-\-query\fP arguments in \fB\-\-filter\fP\&.
 .sp
 Execution example:
 .INDENT 0.0
@@ -26199,7 +26199,7 @@ select Users \-\-output_columns name,_score \-\-filter \(aqquery("name * 10", "a
 When executing above query, the keyword \(aqalice\(aq is weighted to the value \-
 \(aq10\(aq.
 .sp
-Here are the contrasting examples with/without \fBquery\fP.
+Here are the contrasting examples with/without \fBquery\fP\&.
 .sp
 Execution example:
 .INDENT 0.0
@@ -26343,20 +26343,20 @@ keywords on your purpose.
 .SS Parameters
 .SS Required parameter
 .sp
-There are two required parameter, \fBmatch_columns\fP and \fBquery_string\fP.
+There are two required parameter, \fBmatch_columns\fP and \fBquery_string\fP\&.
 .SS \fBmatch_columns\fP
 .sp
 It specifies the default target column for fulltext search by
 \fBquery_string\fP parameter value. It is the same role as
-\fIselect\-match\-columns\fP parameter in \fBselect\fP.
+\fIselect\-match\-columns\fP parameter in \fBselect\fP\&.
 .SS \fBquery_string\fP
 .sp
 It specifies the search condition in
-\fB/reference/grn_expr/query_syntax\fP. It is the same role as
-\fBquery\fP parameter in \fBselect\fP.
+\fB/reference/grn_expr/query_syntax\fP\&. It is the same role as
+\fBquery\fP parameter in \fBselect\fP\&.
 .sp
 See \fIselect\-match\-columns\fP about \fBquery\fP parameter in
-\fBselect\fP.
+\fBselect\fP\&.
 .SS Optional parameter
 .sp
 There are some optional parameters.
@@ -26364,7 +26364,7 @@ There are some optional parameters.
 .sp
 It specifies the plugin name for query expansion.
 .sp
-There is one plugin bundled in official release \- \fB/reference/query_expanders/tsv\fP.
+There is one plugin bundled in official release \- \fB/reference/query_expanders/tsv\fP\&.
 .sp
 See \fB/reference/query_expanders/tsv\fP about details.
 .SS \fBsubstitution_table\fP
@@ -26376,8 +26376,8 @@ See \fIquery\-expander\fP about details.
 .SS Return value
 .sp
 \fBquery\fP returns whether any record is matched or not. If one or more
-records are matched, it returns \fBtrue\fP. Otherwise, it returns
-\fBfalse\fP.
+records are matched, it returns \fBtrue\fP\&. Otherwise, it returns
+\fBfalse\fP\&.
 .SS TODO
 .INDENT 0.0
 .IP \(bu 2
@@ -26405,7 +26405,7 @@ rand([max])
 .UNINDENT
 .SS 説明
 .sp
-groonga組込関数の一つであるrandについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
+Groonga組込関数の一つであるrandについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
 .sp
 rand() 関数は 0 から max の間の疑似乱数整数を返します。
 .SS 引数
@@ -26442,12 +26442,12 @@ This feature is experimental. API will be changed.
 .SS Summary
 .sp
 \fBsnippet_html\fP extracts snippets of target text around search
-keywords (\fBKWIC\fP. \fBKeyWord In Context\fP). The snippets are prepared
+keywords (\fBKWIC\fP\&. \fBKeyWord In Context\fP). The snippets are prepared
 for embedding HTML. Special characters such as \fB<\fP and \fB>\fP are
-escapsed as \fB&lt;\fP and \fB&gt;\fP. Keyword is surrounded with \fB<span
-class="keyword">\fP and \fB</span>\fP. For example, a snippet of \fBI am a
+escapsed as \fB&lt;\fP and \fB&gt;\fP\&. Keyword is surrounded with \fB<span
+class="keyword">\fP and \fB</span>\fP\&. For example, a snippet of \fBI am a
 groonga user. <3\fP for keyword \fBgroonga\fP is \fBI am a <span
-class="keyword">groonga</span> user. &lt;3\fP.
+class="keyword">groonga</span> user. &lt;3\fP\&.
 .SS Syntax
 .sp
 \fBsnippet_html\fP has only one parameter:
@@ -26495,16 +26495,16 @@ load \-\-table Documents
 .UNINDENT
 .sp
 \fBsnippet_html\fP can be used in only \fB\-\-output_columns\fP in
-\fB/reference/commands/select\fP.
+\fB/reference/commands/select\fP\&.
 .sp
 You need to specify \fB\-\-command_version 2\fP argument explicitly
 because function call in \fB\-\-output_columns\fP is experimental feature
-in groonga 2.0.9. It will be enabled by default soon.
+in Groonga 2.0.9. It will be enabled by default soon.
 .sp
-You also need to specify \fB\-\-query\fP and/or \fB\-\-filter\fP. Keywords are
+You also need to specify \fB\-\-query\fP and/or \fB\-\-filter\fP\&. Keywords are
 extracted from \fB\-\-query\fP and \fB\-\-filter\fP arguments.
 .sp
-The following example uses \fB\-\-query "fast performance"\fP. In this
+The following example uses \fB\-\-query "fast performance"\fP\&. In this
 case, \fBfast\fP and \fBperformance\fP are used as keywords.
 .sp
 Execution example:
@@ -26548,14 +26548,14 @@ select Documents \-\-output_columns "snippet_html(content)" \-\-command_version
 \fB\-\-query "fast performance"\fP matches to only the first record\(aqs
 content. \fBsnippet_html(content)\fP extracts two text parts that
 include the keywords \fBfast\fP or \fBperformance\fP and surronds the
-keywords with \fB<span class="keyword">\fP and \fB</span>\fP.
+keywords with \fB<span class="keyword">\fP and \fB</span>\fP\&.
 .sp
 The max number of text parts is 3. If there are 4 or more text parts
 that include the keywords, only the leading 3 parts are only used.
 .sp
 The max size of a text part is 200byte. The unit is bytes not
 chracters. The size doesn\(aqt include inserted \fB<span keyword="keyword">\fP
-and \fB</span>\fP.
+and \fB</span>\fP\&.
 .sp
 Both the max number of text parts and the max size of a text part
 aren\(aqt customizable.
@@ -26600,8 +26600,10 @@ select Documents \-\-output_columns \(aqsnippet_html("Groonga is very fast fullt
 .UNINDENT
 .SS Return value
 .sp
-\fBsnippet_html\fP returns an array of string. An element of array is a
-snippet:
+\fBsnippet_html\fP returns an array of string or \fBnull\fP\&. If
+\fBsnippet_html\fP can\(aqt find any snippets, it returns \fBnull\fP\&.
+.sp
+An element of array is a snippet:
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -26645,11 +26647,11 @@ Support options by object literal.
 \fBsub_filter\fP evaluates \fBfilter_string\fP in \fBscope\fP context.
 .sp
 \fBsub_filter\fP can be used in only \fB\-\-filter\fP in
-\fB/reference/commands/select\fP.
+\fB/reference/commands/select\fP\&.
 .SS Syntax
 .sp
 \fBsub_filter\fP requires two arguments. They are \fBscope\fP and
-\fBfilter_string\fP.
+\fBfilter_string\fP\&.
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -26828,32 +26830,32 @@ There are the records that user "A" mentions about "groonga".
 .UNINDENT
 .SS Parameters
 .sp
-There are two required parameter, \fBscope\fP and \fBfilter_string\fP.
+There are two required parameter, \fBscope\fP and \fBfilter_string\fP\&.
 .SS \fBscope\fP
 .sp
 It specifies a column of the table that is specified by \fBtable\fP
-parameter in \fBselect\fP. The column has a limitation. The limitation
+parameter in \fBselect\fP\&. The column has a limitation. The limitation
 is described later. \fBfilter_string\fP is evaluated in the column
 context. It means that \fBfilter_string\fP is evaluated like
-\fBselect \-\-table TYPE_OF_THE_COLUMN \-\-filter FILTER_STRING\fP.
+\fBselect \-\-table TYPE_OF_THE_COLUMN \-\-filter FILTER_STRING\fP\&.
 .sp
 The specified column type must be a table. In other words, the column
 type must be reference type.
 .sp
 You can chain columns by \fBCOLUMN_1.COLUMN_2.COLUMN_3...COLUMN_N\fP
-syntax. For example, \fBuser.group.name\fP.
+syntax. For example, \fBuser.group.name\fP\&.
 .sp
-See \fIselect\-table\fP about \fBtable\fP parameter in \fBselect\fP.
+See \fIselect\-table\fP about \fBtable\fP parameter in \fBselect\fP\&.
 .SS \fBfilter_string\fP
 .sp
 It specifies a search condition in
-\fB/reference/grn_expr/script_syntax\fP. It is evaluated in \fBscope\fP
+\fB/reference/grn_expr/script_syntax\fP\&. It is evaluated in \fBscope\fP
 context.
 .SS Return value
 .sp
 \fBsub_filter\fP returns whether any record is matched or not. If one or
-more records are matched, it returns \fBtrue\fP. Otherwise, it returns
-\fBfalse\fP.
+more records are matched, it returns \fBtrue\fP\&. Otherwise, it returns
+\fBfalse\fP\&.
 .SS See also
 .INDENT 0.0
 .IP \(bu 2
@@ -26977,7 +26979,7 @@ select Tweets \-\-match_columns content \-\-query \(aqgood nice\(aq
 .UNINDENT
 .UNINDENT
 .sp
-We create index for \fBTweets.content\fP. Already registered
+We create index for \fBTweets.content\fP\&. Already registered
 data in \fBTweets.content\fP are indexed by offline index
 construction:
 .sp
@@ -27112,7 +27114,7 @@ Process log is enabled by default. Log path can be
 customized by \fI\-\-log\-path\fP option.  Each log has its
 log level. If a log is smaller than groonga process\(aq log
 level, it\(aqs not logged. Log level can be customized by
-\fI\-l\fP or \fBcommands/log_level\fP.
+\fI\-l\fP or \fBcommands/log_level\fP\&.
 .SS Format
 .sp
 Process log uses the following format:
@@ -27449,7 +27451,7 @@ Example:
 .SS Tuning
 .SS Summary
 .sp
-There are some tuning parameters for improving groonga performance or
+There are some tuning parameters for improving Groonga performance or
 handling a large database.
 .SS Parameters
 .sp
@@ -27570,7 +27572,7 @@ or re\-login as your groonga user.
 .sp
 This is \fItuning\-memory\-usage\fP related parameter. You can handle a
 database that is larger than your memory and swap by setting
-\fBvm.overcommit_memory\fP kernel parameter to 1. 1 means that groonga
+\fBvm.overcommit_memory\fP kernel parameter to 1. 1 means that Groonga
 can always map database files onto memory. It is no problem until
 groonga touch mapped database files that their size is larger than
 memory and swap. Groonga recommends the configuration.
@@ -27615,7 +27617,7 @@ than 16GiB, groonga reaches the limitation. (\fB256KiB * 65536 = 16GiB\fP)
 .sp
 You needs to increase the value of the kernel parameter to handle
 16GiB or more larger size database. For example, you can handle almost
-32GiB size database by \fB65536 * 2 = 131072\fP. You can set the
+32GiB size database by \fB65536 * 2 = 131072\fP\&. You can set the
 configuration by putting a configuration file
 \fB/etc/sysctl.d/groonga.conf\fP that has the following content:
 .INDENT 0.0
@@ -27665,6 +27667,69 @@ TODO
 .sp
 Groonga can be used as a fulltext search library. This section
 describes APIs that are provided by groonga.
+.SS Global configurations
+.SS Summary
+.sp
+Groonga has the global configurations. You can access them by API.
+.SS Reference
+.INDENT 0.0
+.TP
+.B int grn_get_lock_timeout(void)
+Returns the lock timeout.
+.sp
+\fBgrn_ctx\fP acquires a lock for updating a shared value. If
+other \fBgrn_ctx\fP is already updating the same value,
+\fBgrn_ctx\fP that try to acquire a lock can\(aqt acquires a lock.
+The \fBgrn_ctx\fP that can\(aqt acquires a lock waits 1
+millisecond and try to acquire a lock again. The try is done
+\fBtimeout\fP times. If the \fBgrn_ctx\fP that can\(aqt acquires a
+lock until \fBtimeout\fP times, the tries are failed.
+.sp
+The default lock timeout is \fB10000000\fP\&. It means that Groonga
+doesn\(aqt report a lock failure until about 3 hours.  (1 * 10000000
+[msec] = 10000 [sec] = 166.666... [min] = 2.777... [hour])
+.INDENT 7.0
+.TP
+.B Returns
+The lock timeout.
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B grn_rc grn_set_lock_timeout(int\fI\ timeout\fP)
+Sets the lock timeout.
+.sp
+See 
+.nf
+:c:function:\(gagrn_get_lock_timeout\(ga
+.fi
+ about lock timeout.
+.sp
+There are some special values for \fBtimeout\fP\&.
+.INDENT 7.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fB0\fP: It means that Groonga doesn\(aqt retry acquiring a lock.
+Groonga reports a failure after one lock acquirement failure.
+.IP \(bu 2
+negative value: It means that Groonga retries acquiring a lock
+until Groonga can acquire a lock.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 7.0
+.TP
+.B Parameters
+.INDENT 7.0
+.IP \(bu 2
+\fBtimeuot\fP \-\- The new lock timeout.
+.UNINDENT
+.TP
+.B Returns
+\fBGRN_SUCCESS\fP\&. It doesn\(aqt fail.
+.UNINDENT
+.UNINDENT
 .SS \fBgrn_cache\fP
 .SS Summary
 .sp
@@ -27680,7 +27745,7 @@ This API is experimental.
 object. It is only for \fB/reference/commands/select\fP command.
 .sp
 You can just change the current cache object by
-\fBgrn_cache_current_set()\fP. \fB/reference/commands/select\fP
+\fBgrn_cache_current_set()\fP\&. \fB/reference/commands/select\fP
 command response cache is done internally.
 .sp
 \fB/reference/commands/select\fP command uses one global cache
@@ -27718,7 +27783,7 @@ grn_cache_current_set(ctx, cache_previous);
 .B grn_cache
 It is an opaque cache object. You can create a \fBgrn_cache\fP by
 \fBgrn_cache_open()\fP and free the created object by
-\fBgrn_cache_close()\fP.
+\fBgrn_cache_close()\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -27726,7 +27791,7 @@ It is an opaque cache object. You can create a \fBgrn_cache\fP by
 Creates a new cache object.
 .sp
 If memory allocation for the new cache object is failed, \fBNULL\fP
-is returned. Error information is stored into the \fBctx\fP.
+is returned. Error information is stored into the \fBctx\fP\&.
 .INDENT 7.0
 .TP
 .B Parameters
@@ -27738,13 +27803,13 @@ is returned. Error information is stored into the \fBctx\fP.
 .B Returns
 A newly allocated cache object on success, \fBNULL\fP
 otherwise. The returned cache object must be freed by
-\fBgrn_cache_close()\fP.
+\fBgrn_cache_close()\fP\&.
 .UNINDENT
 .UNINDENT
 .INDENT 0.0
 .TP
 .B grn_rc grn_cache_close(grn_ctx\fI\ *ctx\fP, grn_cache\fI\ *cache\fP)
-Frees resourses of the \fBcache\fP.
+Frees resourses of the \fBcache\fP\&.
 .INDENT 7.0
 .TP
 .B Parameters
@@ -27794,7 +27859,7 @@ Gets the cache object that is used in
 .TP
 .B Returns
 The cache object that is used in
-\fB/reference/commands/select\fP command. It may be \fBNULL\fP.
+\fB/reference/commands/select\fP command. It may be \fBNULL\fP\&.
 .UNINDENT
 .UNINDENT
 .INDENT 0.0
@@ -27846,7 +27911,7 @@ TODO...
 .INDENT 0.0
 .TP
 .B GRN_COLUMN_NAME_ID
-It returns the name of \fB/reference/pseudo_column\fP \fB_id\fP.
+It returns the name of \fB/reference/pseudo_column\fP \fB_id\fP\&.
 .sp
 It is useful to use with \fBGRN_COLUMN_NAME_ID_LEN\fP like
 the following:
@@ -27867,14 +27932,14 @@ Since 3.1.1.
 .INDENT 0.0
 .TP
 .B GRN_COLUMN_NAME_ID_LEN
-It returns the byte size of \fBGRN_COLUMN_NAME_ID\fP.
+It returns the byte size of \fBGRN_COLUMN_NAME_ID\fP\&.
 .sp
 Since 3.1.1.
 .UNINDENT
 .INDENT 0.0
 .TP
 .B GRN_COLUMN_NAME_KEY
-It returns the name of \fB/reference/pseudo_column\fP \fB_key\fP.
+It returns the name of \fB/reference/pseudo_column\fP \fB_key\fP\&.
 .sp
 It is useful to use with \fBGRN_COLUMN_NAME_KEY_LEN\fP like
 the following:
@@ -27895,14 +27960,14 @@ Since 3.1.1.
 .INDENT 0.0
 .TP
 .B GRN_COLUMN_NAME_KEY_LEN
-It returns the byte size of \fBGRN_COLUMN_NAME_KEY\fP.
+It returns the byte size of \fBGRN_COLUMN_NAME_KEY\fP\&.
 .sp
 Since 3.1.1.
 .UNINDENT
 .INDENT 0.0
 .TP
 .B GRN_COLUMN_NAME_VALUE
-It returns the name of \fB/reference/pseudo_column\fP \fB_value\fP.
+It returns the name of \fB/reference/pseudo_column\fP \fB_value\fP\&.
 .sp
 It is useful to use with \fBGRN_COLUMN_NAME_VALUE_LEN\fP like
 the following:
@@ -27923,14 +27988,14 @@ Since 3.1.1.
 .INDENT 0.0
 .TP
 .B GRN_COLUMN_NAME_VALUE_LEN
-It returns the byte size of \fBGRN_COLUMN_NAME_VALUE\fP.
+It returns the byte size of \fBGRN_COLUMN_NAME_VALUE\fP\&.
 .sp
 Since 3.1.1.
 .UNINDENT
 .INDENT 0.0
 .TP
 .B GRN_COLUMN_NAME_SCORE
-It returns the name of \fB/reference/pseudo_column\fP \fB_score\fP.
+It returns the name of \fB/reference/pseudo_column\fP \fB_score\fP\&.
 .sp
 It is useful to use with \fBGRN_COLUMN_NAME_SCORE_LEN\fP like
 the following:
@@ -27951,14 +28016,14 @@ Since 3.1.1.
 .INDENT 0.0
 .TP
 .B GRN_COLUMN_NAME_SCORE_LEN
-It returns the byte size of \fBGRN_COLUMN_NAME_SCORE\fP.
+It returns the byte size of \fBGRN_COLUMN_NAME_SCORE\fP\&.
 .sp
 Since 3.1.1.
 .UNINDENT
 .INDENT 0.0
 .TP
 .B GRN_COLUMN_NAME_NSUBRECS
-It returns the name of \fB/reference/pseudo_column\fP \fB_nsubrecs\fP.
+It returns the name of \fB/reference/pseudo_column\fP \fB_nsubrecs\fP\&.
 .sp
 It is useful to use with \fBGRN_COLUMN_NAME_NSUBRECS_LEN\fP like
 the following:
@@ -27979,7 +28044,7 @@ Since 3.1.1.
 .INDENT 0.0
 .TP
 .B GRN_COLUMN_NAME_NSUBRECS_LEN
-It returns the byte size of \fBGRN_COLUMN_NAME_NSUBRECS\fP.
+It returns the byte size of \fBGRN_COLUMN_NAME_NSUBRECS\fP\&.
 .sp
 Since 3.1.1.
 .UNINDENT
@@ -28220,7 +28285,7 @@ ctxを初期化します。
 .B grn_rc grn_ctx_fin(grn_ctx\fI\ *ctx\fP)
 ctxの管理するメモリを解放し、使用を終了します。
 .sp
-If \fBctx\fP is initialized by \fBgrn_ctx_open()\fP not \fBgrn_ctx_init()\fP. You need also to call \fBgrn_ctx_close()\fP.
+If \fBctx\fP is initialized by \fBgrn_ctx_open()\fP not \fBgrn_ctx_init()\fP\&. You need also to call \fBgrn_ctx_close()\fP\&.
 .INDENT 7.0
 .TP
 .B Parameters
@@ -28256,13 +28321,13 @@ If \fBctx\fP is initialized by \fBgrn_ctx_open()\fP not \fBgrn_ctx_init()\fP. Yo
 .INDENT 0.0
 .TP
 .B grn_rc grn_ctx_close(grn_ctx\fI\ *ctx\fP)
-It calls \fBgrn_ctx_fin()\fP and frees allocated memory for \fBctx\fP by \fBgrn_ctx_open()\fP.
+It calls \fBgrn_ctx_fin()\fP and frees allocated memory for \fBctx\fP by \fBgrn_ctx_open()\fP\&.
 .INDENT 7.0
 .TP
 .B Parameters
 .INDENT 7.0
 .IP \(bu 2
-\fBctx\fP \-\- no longer needed \fBgrn_ctx\fP.
+\fBctx\fP \-\- no longer needed \fBgrn_ctx\fP\&.
 .UNINDENT
 .TP
 .B Returns
@@ -28371,7 +28436,7 @@ TODO...
 .INDENT 0.0
 .TP
 .B grn_db_create_optarg
-It is used for specifying options for \fBgrn_db_create()\fP.
+It is used for specifying options for \fBgrn_db_create()\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -28519,7 +28584,7 @@ is a list of what expression can do:
 .INDENT 0.0
 .IP \(bu 2
 Expression can apply some operations to a record by
-\fBgrn_expr_exec()\fP.
+\fBgrn_expr_exec()\fP\&.
 .IP \(bu 2
 Expression can represents search condition. \fBgrn_table_select()\fP
 can select records that match against the search condition represented
@@ -28585,31 +28650,31 @@ TODO...
 .INDENT 0.0
 .TP
 .B grn_rc grn_expr_syntax_escape(grn_ctx\fI\ *ctx\fP, const char\fI\ *string\fP, int\fI\ string_size\fP, const char\fI\ *target_characters\fP, char\fI\ escape_character\fP, grn_obj\fI\ *escaped_string\fP)
-Escapes \fBtarget_characters\fP in \fBstring\fP by \fBescape_character\fP.
+Escapes \fBtarget_characters\fP in \fBstring\fP by \fBescape_character\fP\&.
 .INDENT 7.0
 .TP
 .B Parameters
 .INDENT 7.0
 .IP \(bu 2
-\fBctx\fP \-\- Its encoding must be the same encoding of \fBstring\fP.
-It is used for allocating buffer for \fBescaped_string\fP.
+\fBctx\fP \-\- Its encoding must be the same encoding of \fBstring\fP\&.
+It is used for allocating buffer for \fBescaped_string\fP\&.
 .IP \(bu 2
 \fBstring\fP \-\- String expression representation.
 .IP \(bu 2
-\fBstring_size\fP \-\- The byte size of \fBstring\fP. \fB\-1\fP means \fBstring\fP
+\fBstring_size\fP \-\- The byte size of \fBstring\fP\&. \fB\-1\fP means \fBstring\fP
 is NULL terminated string.
 .IP \(bu 2
 \fBtarget_characters\fP \-\- NULL terminated escape target characters.
 For example, \fB"+\-><~*()\e"\e\e:"\fP is
 \fBtarget_characters\fP for
-\fB/reference/grn_expr/query_syntax\fP.
+\fB/reference/grn_expr/query_syntax\fP\&.
 .IP \(bu 2
 \fBescape_character\fP \-\- The character to use escape a character in
-\fBtarget_characters\fP. For example, \fB\e\e\fP
+\fBtarget_characters\fP\&. For example, \fB\e\e\fP
 (backslash) is \fBescaped_character\fP for
-\fB/reference/grn_expr/query_syntax\fP.
+\fB/reference/grn_expr/query_syntax\fP\&.
 .IP \(bu 2
-\fBescaped_string\fP \-\- The output of escaped \fBstring\fP. It should be
+\fBescaped_string\fP \-\- The output of escaped \fBstring\fP\&. It should be
 text typed bulk.
 .UNINDENT
 .TP
@@ -28621,22 +28686,22 @@ text typed bulk.
 .TP
 .B grn_rc grn_expr_syntax_escape_query(grn_ctx\fI\ *ctx\fP, const char\fI\ *query\fP, int\fI\ query_size\fP, grn_obj\fI\ *escaped_query\fP)
 Escapes special characters in
-\fB/reference/grn_expr/query_syntax\fP.
+\fB/reference/grn_expr/query_syntax\fP\&.
 .INDENT 7.0
 .TP
 .B Parameters
 .INDENT 7.0
 .IP \(bu 2
-\fBctx\fP \-\- Its encoding must be the same encoding of \fBquery\fP.
-It is used for allocating buffer for \fBescaped_query\fP.
+\fBctx\fP \-\- Its encoding must be the same encoding of \fBquery\fP\&.
+It is used for allocating buffer for \fBescaped_query\fP\&.
 .IP \(bu 2
 \fBquery\fP \-\- String expression representation in
-\fB/reference/grn_expr/query_syntax\fP.
+\fB/reference/grn_expr/query_syntax\fP\&.
 .IP \(bu 2
-\fBquery_size\fP \-\- The byte size of \fBquery\fP. \fB\-1\fP means \fBquery\fP
+\fBquery_size\fP \-\- The byte size of \fBquery\fP\&. \fB\-1\fP means \fBquery\fP
 is NULL terminated string.
 .IP \(bu 2
-\fBescaped_query\fP \-\- The output of escaped \fBquery\fP. It should be
+\fBescaped_query\fP \-\- The output of escaped \fBquery\fP\&. It should be
 text typed bulk.
 .UNINDENT
 .TP
@@ -31075,37 +31140,37 @@ Then save the configuration value to /etc/sysctl.conf or /etc/sysctl.d/
 .nf
 *
 .fi
-.conf.
+\&.conf.
 .sp
 See \fB/reference/tuning\fP documentation about tuning related parameters.
 .SH DEVELOPMENT
 .sp
-This section describes about developing with groonga. You may develop
-an application that uses groonga as its database, a library that uses
+This section describes about developing with Groonga. You may develop
+an application that uses Groonga as its database, a library that uses
 libgroonga, language bindings of libgroonga and so on.
 .SS Travis CI
 .sp
-This section describes about using groonga on \fI\%Travis CI\fP. Travis CI is a hosted continuous
+This section describes about using Groonga on \fI\%Travis CI\fP\&. Travis CI is a hosted continuous
 integration service for the open source community.
 .sp
 You can use Travis CI for your open source software. This section only
-describes about groonga related configuration. See \fI\%Travis CI:
+describes about Groonga related configuration. See \fI\%Travis CI:
 Documentation\fP about general
 Travis CI.
 .SS Configuration
 .sp
 Travis CI is running on 64\-bit Ubuntu 12.04 LTS Server Edition. (See \fI\%Travis CI: About
-Travis CI Environment\fP.)  You can
-use apt\-line for Ubuntu 12.04 LTS provided by groonga project to install
-groonga on Travis CI.
+Travis CI Environment\fP\&.)  You can
+use apt\-line for Ubuntu 12.04 LTS provided by Groonga project to install
+Groonga on Travis CI.
 .sp
-You can custom build lifecycle by \fB.travis.yml\fP. (See \fI\%Travis CI:
-Conifugration your Travis CI build with .travis.yml\fP.) You
+You can custom build lifecycle by \fB\&.travis.yml\fP\&. (See \fI\%Travis CI:
+Conifugration your Travis CI build with .travis.yml\fP\&.) You
 can use \fBbefore_install\fP hook or \fBinstall\fP hook. You should use
 \fBbefore_install\fP if your software uses a language that is supported
 by Travis CI such as Ruby. You should use \fBinstall\fP otherwise.
 .sp
-Add the following \fBbefore_install\fP configuration to \fB.travis.yml\fP:
+Add the following \fBbefore_install\fP configuration to \fB\&.travis.yml\fP:
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -31119,12 +31184,12 @@ before_install:
 .UNINDENT
 .sp
 If you need to use \fBinstall\fP hook instead of \fBbefore_install\fP, you
-just substitute \fBbefore_install:\fP with \fBinstall:\fP.
+just substitute \fBbefore_install:\fP with \fBinstall:\fP\&.
 .sp
-With the above configuration, you can use groonga for your build.
+With the above configuration, you can use Groonga for your build.
 .SS Examples
 .sp
-Here are open source softwares that use groonga on Travis CI:
+Here are open source softwares that use Groonga on Travis CI:
 .INDENT 0.0
 .INDENT 3.5
 .INDENT 0.0
@@ -31134,7 +31199,7 @@ Here are open source softwares that use groonga on Travis CI:
 .IP \(bu 2
 \fI\%rroonga on Travis CI\fP
 .IP \(bu 2
-\fI\%.travis.yml for rroonga\fP
+\fI\%\&.travis.yml for rroonga\fP
 .UNINDENT
 .IP \(bu 2
 \fI\%nroonga\fP (node.js bindings)
@@ -31142,7 +31207,7 @@ Here are open source softwares that use groonga on Travis CI:
 .IP \(bu 2
 \fI\%nroonga on Travis CI\fP
 .IP \(bu 2
-\fI\%.travis.yml for nroonga\fP
+\fI\%\&.travis.yml for nroonga\fP
 .UNINDENT
 .IP \(bu 2
 \fI\%logaling\-command\fP (A glossary management command line tool)
@@ -31150,7 +31215,7 @@ Here are open source softwares that use groonga on Travis CI:
 .IP \(bu 2
 \fI\%logaling\-command on Travis CI\fP
 .IP \(bu 2
-\fI\%.travis.yml for logaling\-command\fP
+\fI\%\&.travis.yml for logaling\-command\fP
 .UNINDENT
 .UNINDENT
 .UNINDENT
@@ -31191,7 +31256,7 @@ You can use either way It makes no difference to us.
 .SS Submit a bug to the issue tracker
 .sp
 Groonga project has two issue tracking systems, \fI\%Redmine\fP and \fI\%GitHub
-issue tracker\fP.  Redmine
+issue tracker\fP\&.  Redmine
 is for Japanese and GitHub issue tracker is for English. You can use
 one of them to report a bug.
 .SS Report a bug to the mailing list
@@ -31211,7 +31276,7 @@ We will use \fI\%the C domain markup\fP of Sphinx.
 .SS I18N
 .sp
 We only had documentation in Japanese.  We start to support
-I18N documentation by gettext based \fI\%Sphinx I18N feature\fP.
+I18N documentation by gettext based \fI\%Sphinx I18N feature\fP\&.
 We\(aqll use English as base language and translate
 English into other languages such as Japanese. We\(aqll put
 all documentations into doc/source/ and process them by
@@ -31368,7 +31433,7 @@ running \fImake html\fP on doc/locale:
 \fBNOTE:\fP
 .INDENT 0.0
 .INDENT 3.5
-.mo files are updated automatically by \fImake html\fP. So
+\&.mo files are updated automatically by \fImake html\fP\&. So
 you don\(aqt care about .mo files.
 .UNINDENT
 .UNINDENT
@@ -31415,7 +31480,7 @@ button.
 \fBSEE ALSO:\fP
 .INDENT 0.0
 .INDENT 3.5
-\fI\%Help.GitHub \- Sending pull requests\fP.
+\fI\%Help.GitHub \- Sending pull requests\fP\&.
 .UNINDENT
 .UNINDENT
 .SS How to send patch
@@ -31477,13 +31542,13 @@ as \(aqja\(aq.
 \fBSEE ALSO:\fP
 .INDENT 0.0
 .INDENT 3.5
-\fI\%Codes for the Representation of Names of Languages\fP.
+\fI\%Codes for the Representation of Names of Languages\fP\&.
 .UNINDENT
 .UNINDENT
 .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:
+There is \fI\%the repository of groonga on GitHub\fP\&. If you want to check\-out groonga, type the below command:
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -33143,6 +33208,6 @@ configureは１度のみ実行する必要があります。
 .SH AUTHOR
 Groonga Project
 .SH COPYRIGHT
-2009-2013, Brazil, Inc
+2009-2014, Brazil, Inc
 .\" Generated by docutils manpage writer.
 .