# -*- po -*-
# English translations for Groonga package.
# Copyright (C) 2009-2015, Brazil, Inc
# This file is distributed under the same license as the Groonga package.
# Automatically generated, 2015.
#
msgid ""
msgstr ""
"Project-Id-Version: Groonga 5.0.5\n"
"Report-Msgid-Bugs-To: \n"
"PO-Revision-Date: 2015-06-24 14:55+0900\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
"Language: en\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

# 595a09ca042b4cfb8b420b2ad0aa0747
# f8ec0eabf0744079a5acb8b83b8f87e0
# a1993a44c7cd4b8ab09c003272a72710
# 8bf1c3ed9ab4476d9dacd54459a82861
# 753ca3ecff934adb9946edf591216207
# 704ca2aff8474617b69b43f3066c7b53
# a21f8a9dc97d4640926044c076b49985
# 83ec1990d86041ebb2e1c996067351e3
# fb92b53e213a44ee84f547cada72a741
# 8d8133b55fc54a6a879a4c7a5065e49e
# 2292eddbe1aa4626b015f5c468b2e379
# cfc1e640ac4945eeb275aedf1369ebe8
# 1e88efa3f46443b59b7cedcd6dac6caa
# af58986c0e2c43e9b0e16d84e63da12c
# e59c87db38904e6180e4c81d58fbc83b
# 696d282ae1524203bfa05e3b1d559a33
# 380b7a3527184148b2f0daf0692ddaa9
# 2b9f15b822ba46dfadc040d916202202
# c1dd629526214724b7da3ac9343de755
# 2f77f34f8722432fb9c11eca51f016c4
# 43a5e666a046477689670e0fee52c3d5
# 539f58f602b54ec581eb40c61e428792
# 0710462a9c954e0a88b0b7d0753808bf
# 984a51ff1eaa46f487ea8ed8a604e8c9
# 1fe9af19e4e7499baab3a0ccf97d3c62
# dcf8e7ab7ae641f4a53c668f9e6ab810
# 6075b94e87e344f28a04eb7fed3a7567
# e0fbb207d80a45afb52065610aa18d00
# 39a06e85fe974c729cc817942f6987c0
# be7fdca259c942aabcef79465337ebc7
# a7e719d8108645c98e60c4d0ec935807
# 1c96a84bdb8c4f58b7109ea0d7dae3da
# 082ff0e4162c42a2904af8f2e4960eeb
# 640442d94baa4b2e965e2e2052ee8cea
# 0efbc79c545a423bb8a39ae7d753581c
# 2e55e461e7b74f3c97f7196157e8c2f3
# c434db4ec0c646c4be0db4953e860c35
# 20a8954421894b349faacc034b50c28b
# 5a20f0b723e84ab7bff0a035ac702105
# 65451620e00f43f6864e3fb1974db634
# 80ad0de6b8d74549ab25221e87091933
# 04112ff283ec47f7ae4715b64a738202
# 15a0869e240f4f749506ab52b7a9ed34
# 920b222965ff49d0901d862bae184d8c
# ea1a747b880a4c2d80d5dae123d53fb9
# 9ff77ed11d3742cea7070daf18d15975
# 182260c4daec4e1aaa2726b4245a0ee4
# 21b53d0a0fb344f89b1f2639a270b379
# 30481b9f0ae546918c7440387f5211a5
# 0f0fbea57bd7487eaf0c0c23034dbfe7
# 53ef87f89d1745a59634c968af42db10
# f7facf4fbf4843ba8c17972562b55739
# e707ba1a7d2a4027938b313bc0f505c1
# 1bed5fc530b9475daf57296b94ad8833
# c64ad633a0a44801a0668557a8ae0c8f
# 6cd5e0c44e4b46ea9a647dee2cf02025
# 7706275aef864a86897517d760e9c4e4
# b5f61958d3e344c4ac2c0c85e2ce2499
# 924fecb5d12b40f6a8f86ba5237db542
# 6c3b9f20817740349dab870d135f52a2
# 27d9d2c4fe3e40818ed991ad805b920f
# b124aa929776417eb923ef1732c475f9
# 396745d5c1d94c15aff9e9e5f0b96387
# 1081049a275545af896846d6e8579c29
# f972ade1352745fb8c6ee46ec5fd6f4a
# 39aa8176c9194fc3a5b7cb51f1c99e5d
# bdb88d7318d2438aa517b485d2579dd7
# c3fb183474184324ad5e0dfadacf685b
# 4c2e91369a7a47dea0e10504dc3b3310
# 60de083b3d8742dcb65666a0d84e4aab
# e8b1004ba94340f8908d9540734dfd30
# 62fd5a0604ac40618f3517e77e204ed9
# 7f4356fd400d40868f7d2935e2458766
# 0e4bb84b497d481bb216b6a503fba51a
msgid "Execution example::"
msgstr "Execution example::"

# bea99d14b47d45f791f717cef98503ed
msgid "Tutorial"
msgstr "Tutorial"

# 52dfb8f16cd54df9b6cd5bf339ce7b89
msgid "Various data types"
msgstr "Various data types"

# 0a19d7339c9f4ec9b8298667daa89cf4
msgid ""
"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."
msgstr ""
"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."

# 54d1f252c2434855a467b60387075ae4
msgid "Overview"
msgstr "Overview"

# 6845448cdf86482d9802c7974c80463a
msgid ""
"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 :doc:`/"
"reference/types`."
msgstr ""
"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 :doc:`/"
"reference/types`."

# a337c1bfbe8f459bb29fed8868ba21f3
msgid ""
"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."
msgstr ""
"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."

# 826de4dfff5a4ab9af8248225c1deba7
msgid "First, let's create a table for this tutorial."
msgstr "First, let's create a table for this tutorial."

# d97ab9c1a55c46f385951cf962b62a89
msgid "Boolean type"
msgstr "Boolean type"

# c2326dd703384d65ab58d10c3cfd2530
msgid ""
"The boolean type is used to store true or false. To create a boolean type "
"column, specify Bool to the `type` parameter of :doc:`/reference/commands/"
"column_create` command. The default value of the boolean type is false."
msgstr ""
"The boolean type is used to store true or false. To create a boolean type "
"column, specify Bool to the `type` parameter of :doc:`/reference/commands/"
"column_create` command. The default value of the boolean type is false."

# f978ceb798ed49fca8fb787c8d62e1c5
msgid ""
"The following example creates a boolean type column and adds three records. "
"Note that the third record has the default value because no value is "
"specified."
msgstr ""
"The following example creates a boolean type column and adds three records. "
"Note that the third record has the default value because no value is "
"specified."

# e6b6c0873d65428f9758ed5ba133435c
msgid "Numeric types"
msgstr "Numeric types"

# f991b324378e43a0814af3d555fc59ac
msgid ""
"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 :doc:`/reference/types`. "
"The default value of the numeric types is 0."
msgstr ""
"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 :doc:`/reference/types`. "
"The default value of the numeric types is 0."

# 266f28bb9c954573810bbdee7b5d1272
msgid ""
"The following example creates an Int8 column and a Float column, and then "
"updates existing records. The :doc:`/reference/commands/load` 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."
msgstr ""
"The following example creates an Int8 column and a Float column, and then "
"updates existing records. The :doc:`/reference/commands/load` 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."

# 6003283fe74e4b009af7514982ac6644
msgid "String types"
msgstr "String types"

# b6756601b0a746cd9332c51cd816aa01
msgid ""
"The string types are divided according to the maximum length. For more "
"details, see :doc:`/reference/types`. The default value is the zero-length "
"string."
msgstr ""
"The string types are divided according to the maximum length. For more "
"details, see :doc:`/reference/types`. The default value is the zero-length "
"string."

# 583c96612e434580ac759be28908a437
msgid ""
"The following example creates a ShortText column and updates existing "
"records. The third record has the default value because not updated."
msgstr ""
"The following example creates a ShortText column and updates existing "
"records. The third record has the default value because not updated."

# 990f824da28f400e91fff28ca73ec2a4
msgid "Date and time type"
msgstr "Date and time type"

# 753eca8dbf4444aba7a449c1e78b3f9c
msgid ""
"The date and time type of Groonga is Time. Actually, a Time column stores a "
"date and time as the number of microseconds since the Epoch, 1970-01-01 "
"00:00:00. A Time value can represent a date and time before the Epoch "
"because the actual data type is a signed integer. Note that :doc:`/reference/"
"commands/load` and :doc:`/reference/commands/select` commands use a decimal "
"number to represent a data and time in seconds. The default value is 0.0, "
"which means the Epoch."
msgstr ""
"The date and time type of Groonga is Time. Actually, a Time column stores a "
"date and time as the number of microseconds since the Epoch, 1970-01-01 "
"00:00:00. A Time value can represent a date and time before the Epoch "
"because the actual data type is a signed integer. Note that :doc:`/reference/"
"commands/load` and :doc:`/reference/commands/select` commands use a decimal "
"number to represent a data and time in seconds. The default value is 0.0, "
"which means the Epoch."

# 3bd02ef6efda48668dc9e57fbd9043a5
msgid ""
"Groonga internally holds the value of Epoch as pair of integer. The first "
"integer represents the value of seconds, on the other hand, the second "
"integer represents the value of micro seconds. So, Groonga shows the value "
"of Epoch as floating point. Integral part means the value of seconds, "
"fraction part means the value of micro seconds."
msgstr ""
"Groonga internally holds the value of Epoch as pair of integer. The first "
"integer represents the value of seconds, on the other hand, the second "
"integer represents the value of micro seconds. So, Groonga shows the value "
"of Epoch as floating point. Integral part means the value of seconds, "
"fraction part means the value of micro seconds."

# 900bd108622b48759089ccf78b5b9f35
msgid ""
"The following example creates a Time column and updates existing records. "
"The first record has the default value because not updated."
msgstr ""
"The following example creates a Time column and updates existing records. "
"The first record has the default value because not updated."

# 978f6edbcfe94e118aebec44d9fbdd62
msgid "Longitude and latitude types"
msgstr "Longitude and latitude types"

# 6be016ebb1f74c94bd872d5c5ef7154f
msgid ""
"The longitude and latitude types are divided according to the geographic "
"coordinate system. For more details, see :doc:`/reference/types`. To "
"represent a longitude and latitude, Groonga uses a string formatted as "
"follows:"
msgstr ""
"The longitude and latitude types are divided according to the geographic "
"coordinate system. For more details, see :doc:`/reference/types`. To "
"represent a longitude and latitude, Groonga uses a string formatted as "
"follows:"

# 9cb6f4bf95af4f63a74fa37ac7fa3868
msgid ""
"\"longitude x latitude\" in milliseconds (e.g.: \"128452975x503157902\")"
msgstr ""
"\"longitude x latitude\" in milliseconds (e.g.: \"128452975x503157902\")"

# dd7597847c9d42c5aec01c475fe2d2fa
msgid "\"longitude x latitude\" in degrees (e.g.: \"35.6813819x139.7660839\")"
msgstr "\"longitude x latitude\" in degrees (e.g.: \"35.6813819x139.7660839\")"

# ac8476bdba554c62aa0c0f9e504580f8
msgid ""
"A number with/without a decimal point represents a longitude or latitude in "
"milliseconds/degrees respectively. Note that a combination of a number with "
"a decimal point and a number without a decimal point (e.g. 35.1x139) must "
"not be used. A comma (',') is also available as a delimiter. The default "
"value is \"0x0\"."
msgstr ""
"A number with/without a decimal point represents a longitude or latitude in "
"milliseconds/degrees respectively. Note that a combination of a number with "
"a decimal point and a number without a decimal point (e.g. 35.1x139) must "
"not be used. A comma (',') is also available as a delimiter. The default "
"value is \"0x0\"."

# 37bddea5da14488dbeb676bfcc64835f
msgid ""
"The following example creates a WGS84GeoPoint column and updates existing "
"records. The second record has the default value because not updated."
msgstr ""
"The following example creates a WGS84GeoPoint column and updates existing "
"records. The second record has the default value because not updated."

# 62703690b3394c3881b9e1f07140a4ef
msgid "Reference types"
msgstr "Reference types"

# fb64f39e86fe41e188b82184fa75d784
msgid ""
"Groonga supports a reference column, which stores references to records in "
"its associated table. In practice, a reference column stores the IDs of the "
"referred records in the associated table and enables access to those records."
msgstr ""
"Groonga supports a reference column, which stores references to records in "
"its associated table. In practice, a reference column stores the IDs of the "
"referred records in the associated table and enables access to those records."

# a7389768999c4e30a3d20f161fb45f97
msgid ""
"You can specify a column in the associated table to the `output_columns` "
"parameter of a :doc:`/reference/commands/select` command. The format is "
"\"Src.Dest\" where Src is the name of the reference column and Dest is the "
"name of the target column. If only the reference column is specified, it is "
"handled as \"Src._key\". Note that if a reference does not point to a valid "
"record, a :doc:`/reference/commands/select` command outputs the default "
"value of the target column."
msgstr ""
"You can specify a column in the associated table to the `output_columns` "
"parameter of a :doc:`/reference/commands/select` command. The format is "
"\"Src.Dest\" where Src is the name of the reference column and Dest is the "
"name of the target column. If only the reference column is specified, it is "
"handled as \"Src._key\". Note that if a reference does not point to a valid "
"record, a :doc:`/reference/commands/select` command outputs the default "
"value of the target column."

# 9fb3d14b15bd472d87cb7af2507fb465
msgid ""
"The following example adds a reference column to the Site table that was "
"created in the previous tutorial. The new column, named link, is designed "
"for storing links among records in the Site table."
msgstr ""
"The following example adds a reference column to the Site table that was "
"created in the previous tutorial. The new column, named link, is designed "
"for storing links among records in the Site table."

# 060c9f1220e24d48a445cf719ae6f866
msgid ""
"The `type` parameter of the :doc:`/reference/commands/column_create` command "
"specifies the table to be associated with the reference column. In this "
"example, the reference column is associated with the own table. Then, the :"
"doc:`/reference/commands/load` command registers a link from \"http://"
"example.org\" to \"http://example.net\". Note that a reference column "
"requires the primary key, not the ID, of the record to be referred to. After "
"that, the link is confirmed by the :doc:`/reference/commands/select` "
"command. In this case, the primary key and the title of the referred record "
"are output because link._key and link.title are specified to the "
"`output_columns` parameter."
msgstr ""
"The `type` parameter of the :doc:`/reference/commands/column_create` command "
"specifies the table to be associated with the reference column. In this "
"example, the reference column is associated with the own table. Then, the :"
"doc:`/reference/commands/load` command registers a link from \"http://"
"example.org\" to \"http://example.net\". Note that a reference column "
"requires the primary key, not the ID, of the record to be referred to. After "
"that, the link is confirmed by the :doc:`/reference/commands/select` "
"command. In this case, the primary key and the title of the referred record "
"are output because link._key and link.title are specified to the "
"`output_columns` parameter."

# 2aa727a54ec844588ee36fc423a2794b
msgid "Vector types"
msgstr "Vector types"

# 4646c5a1c4254f68b03a16d0e319ab78
msgid ""
"Groonga supports a vector column, in which each element can store a variable "
"number of values. To create a vector column, specify the COLUMN_VECTOR flag "
"to the `flags` parameter of a :doc:`/reference/commands/column_create` "
"command. A vector column is useful to represent a many-to-many relationship."
msgstr ""
"Groonga supports a vector column, in which each element can store a variable "
"number of values. To create a vector column, specify the COLUMN_VECTOR flag "
"to the `flags` parameter of a :doc:`/reference/commands/column_create` "
"command. A vector column is useful to represent a many-to-many relationship."

# 6b2dc25d2901425a8bf94fcaf05fcd00
msgid ""
"The previous example used a regular column, so each record could have at "
"most one link. Obviously, the specification is insufficient because a site "
"usually has more than one links. To solve this problem, the following "
"example uses a vector column."
msgstr ""
"The previous example used a regular column, so each record could have at "
"most one link. Obviously, the specification is insufficient because a site "
"usually has more than one links. To solve this problem, the following "
"example uses a vector column."

# 996e940a24cf446082009cbb264ebe8c
msgid ""
"The only difference at the first step is the `flags` parameter that "
"specifies to create a vector column. The `type` parameter of the :doc:`/"
"reference/commands/column_create` command is the same as in the previous "
"example. Then, the :doc:`/reference/commands/load` command registers three "
"links from \"http://example.org/\" to \"http://example.net/\", \"http://"
"example.org/\" and \"http://example.com/\". After that, the links are "
"confirmed by the :doc:`/reference/commands/select` command. In this case, "
"the primary keys and the titles are output as arrays because links._key and "
"links.title are specified to the `output_columns` parameter."
msgstr ""
"The only difference at the first step is the `flags` parameter that "
"specifies to create a vector column. The `type` parameter of the :doc:`/"
"reference/commands/column_create` command is the same as in the previous "
"example. Then, the :doc:`/reference/commands/load` command registers three "
"links from \"http://example.org/\" to \"http://example.net/\", \"http://"
"example.org/\" and \"http://example.com/\". After that, the links are "
"confirmed by the :doc:`/reference/commands/select` command. In this case, "
"the primary keys and the titles are output as arrays because links._key and "
"links.title are specified to the `output_columns` parameter."

# cd1c407866004932b64355c4ada33bd3
msgid "Drilldown by ``domain`` column"
msgstr "Drilldown by ``domain`` column"

# 25b500c5b9a6460e8312d41a3e690350
msgid "Drilldown"
msgstr "Drilldown"

# b3974516c71543dc9408867b95e99ad3
msgid ""
"You learned how to search and sort searched results in the previous "
"sections. Now that you can search as you likes, but how do you summarize the "
"number of records which has specific value in the column?"
msgstr ""
"You learned how to search and sort searched results in the previous "
"sections. Now that you can search as you likes, but how do you summarize the "
"number of records which has specific value in the column?"

# 73a1d7188b0c4c20a476eb518b47446e
msgid ""
"As you know, there is a naive solution to execute query by every the value "
"of column, then you can get the number of records as a result. It is a "
"simple way, but it is not reasonable to many records."
msgstr ""
"As you know, there is a naive solution to execute query by every the value "
"of column, then you can get the number of records as a result. It is a "
"simple way, but it is not reasonable to many records."

# 8bec56fb5bc941c08d2c5e24dac77606
msgid ""
"If you are familiar with SQL, you will doubt with \"Is there a similar SQL "
"functionality to ``GROUP BY`` in Groonga?\"."
msgstr ""
"If you are familiar with SQL, you will doubt with \"Is there a similar SQL "
"functionality to ``GROUP BY`` in Groonga?\"."

# da4e449420cf4230a89fe85132c2e988
msgid ""
"Of course, Groonga provides such a functionality. It's called as "
"``drilldown``."
msgstr ""
"Of course, Groonga provides such a functionality. It's called as "
"``drilldown``."

# 1f96477a5e46414cb1b39fbc494d63b6
msgid ""
"``drilldown`` enables you to get the number of records which belongs to "
"specific the value of column at once."
msgstr ""
"``drilldown`` enables you to get the number of records which belongs to "
"specific the value of column at once."

# 06e8809b910949e191ea886568611b22
msgid ""
"To illustrate this feature, imagine the case that classification by domain "
"and grouping by country that domain belongs to."
msgstr ""
"To illustrate this feature, imagine the case that classification by domain "
"and grouping by country that domain belongs to."

# b4492cae159042b6a53ee6b243aaadf2
msgid "Here is the concrete examples how to use this feature."
msgstr "Here is the concrete examples how to use this feature."

# e639f552965946d4873255c676194009
msgid ""
"In this example, we add two columns to ``Site`` table. ``domain`` column is "
"used for TLD (top level domain). ``country`` column is used for country "
"name. The type of these columns are ``SiteDomain`` table which uses domain "
"name as a primary key and ``SiteCountry`` table which uses country name as a "
"primary key."
msgstr ""
"In this example, we add two columns to ``Site`` table. ``domain`` column is "
"used for TLD (top level domain). ``country`` column is used for country "
"name. The type of these columns are ``SiteDomain`` table which uses domain "
"name as a primary key and ``SiteCountry`` table which uses country name as a "
"primary key."

# b632305a78fe4a829dcdd6914895998e
msgid ""
"Here is a example of drilldown with ``domain`` column. Three kind of values "
"are used in ``domain`` column - \".org\", \".net\" and \".com\"."
msgstr ""
"Here is a example of drilldown with ``domain`` column. Three kind of values "
"are used in ``domain`` column - \".org\", \".net\" and \".com\"."

# 9f5e2a16ac3440c7be30644e63904c8d
msgid "Here is a summary of above query."
msgstr "Here is a summary of above query."

# 289217d9dfdb448ba44cb310971a63c2
msgid "Group by"
msgstr "Group by"

# a8faa1943349495ab8d1c70c53f92c1d
msgid "The number of group records"
msgstr "The number of group records"

# ee098782c5994d17b48d1f813fb17323
msgid "Group records means following records"
msgstr "Group records means following records"

# 99a162d2ee97488c8071b07d01844eb0
msgid ".org"
msgstr ".org"

# c22cf4809fe043deb8da5f4a9228e7d5
# 43d3843a289c4baebdf57f0a740f6ebe
# e60885777db74795917b86c2268716fb
msgid "3"
msgstr "3"

# 8140619fbb85494fab6422c86f8f4bb6
msgid "http://example.org/"
msgstr "http://example.org/"

# 5eb033870564444a860e11e9efe8f32b
msgid "http://example.org/aba"
msgstr "http://example.org/aba"

# 76f99c31d5c64261948b3b88c75d9f61
msgid "http://example.org/gat"
msgstr "http://example.org/gat"

# 2c40b6c951f1427ab100c107aebccead
msgid ".net"
msgstr ".net"

# 84f3957d42b549efa23f00bc8e214973
msgid "http://example.net/"
msgstr "http://example.net/"

# 87222f657f1b4d01b86fdeeb4b16f34b
msgid "http://example.net/afr"
msgstr "http://example.net/afr"

# 0d8274f3ea5743e5a34caef400afff93
msgid "http://example.net/atv"
msgstr "http://example.net/atv"

# 4a85af2bcdc84df6a681ea7387396398
msgid ".com"
msgstr ".com"

# ba5c6f4d09d147148383d9d8642612da
msgid "http://example.com/"
msgstr "http://example.com/"

# 660cb80a344a4c8bb0324a475dea4516
msgid "http://example.com/rab"
msgstr "http://example.com/rab"

# 124ce63a81fc4a4cbfa1fb536e6e431d
msgid "http://example.com/vdw"
msgstr "http://example.com/vdw"

# 4c849baead6443ac9d6bff795507f344
msgid ""
"The value of drilldown are returned as the value of ``_nsubrecs`` column. In "
"this case, ``Site`` table is grouped by \".org\", \".net\", \".com\" domain. "
"``_nsubrecs`` shows that each three domain has three records."
msgstr ""
"The value of drilldown are returned as the value of ``_nsubrecs`` column. In "
"this case, ``Site`` table is grouped by \".org\", \".net\", \".com\" domain. "
"``_nsubrecs`` shows that each three domain has three records."

# 87622b0e9bf64a909524a3c8b25649a7
msgid ""
"If you execute drildown to the column which has table as a type, you can get "
"the value of column which is stored in referenced table. ``_nsubrecs`` "
"pseudo column is added to the table which is used for drilldown. this pseudo "
"column stores the number of records which is grouped by."
msgstr ""
"If you execute drildown to the column which has table as a type, you can get "
"the value of column which is stored in referenced table. ``_nsubrecs`` "
"pseudo column is added to the table which is used for drilldown. this pseudo "
"column stores the number of records which is grouped by."

# 17d7ad5aa9a643da8af3d407901e9cd7
msgid ""
"Then, investigate referenced table in detail. As ``Site`` table use "
"``SiteDomain`` table as column type of ``domain``, you can use ``--"
"drilldown_output_columns`` to know detail of referenced column."
msgstr ""
"Then, investigate referenced table in detail. As ``Site`` table use "
"``SiteDomain`` table as column type of ``domain``, you can use ``--"
"drilldown_output_columns`` to know detail of referenced column."

# eebf10c9bb3d4f62952a870e9896dbe2
msgid ""
"Now, you can see detail of each grouped domain, drilldown by ``country`` "
"column which has \".org\" as column value."
msgstr ""
"Now, you can see detail of each grouped domain, drilldown by ``country`` "
"column which has \".org\" as column value."

# 9fba31fb0e5344d4bea75db2ba3e047c
msgid "Drilldown with multiple column"
msgstr "Drilldown with multiple column"

# b159f3654a9240f482877e6e26629e56
msgid ""
"Drilldown feature supports multiple column. Use comma separated multiple "
"column names as ``drildown`` parameter. You can get the each result of "
"drilldown at once."
msgstr ""
"Drilldown feature supports multiple column. Use comma separated multiple "
"column names as ``drildown`` parameter. You can get the each result of "
"drilldown at once."

# 42e00ac98222473cbbb8b93893a11c20
msgid "Sorting drildown results"
msgstr "Sorting drildown results"

# a3ac6835c8fe428f94419430e4418893
msgid ""
"Use ``--drilldown_sortby`` if you want to sort the result of drilldown. For "
"example, specify ``_nsubrecs`` as ascending order."
msgstr ""
"Use ``--drilldown_sortby`` if you want to sort the result of drilldown. For "
"example, specify ``_nsubrecs`` as ascending order."

# 1305d33f01134466bbf2a723a0fe2c9f
msgid "limits drildown results"
msgstr "limits drildown results"

# 4cd3657c1cd540bfa4c568f629181553
msgid ""
"The number of drilldown results is limited to 10 as a default. Use "
"``drilldown_limit`` and ``drilldown_offset`` parameter to customize "
"orilldown results."
msgstr ""
"The number of drilldown results is limited to 10 as a default. Use "
"``drilldown_limit`` and ``drilldown_offset`` parameter to customize "
"orilldown results."

# 4a1c332aff254b6ca9f7fb1393eb0ec4
msgid ""
"Note that drilldown to the column which stores string is slower than the "
"columns which stores the other types. If you drilldown to string type of "
"column, create the table that type of primary key is string, then create the "
"column which refers that table."
msgstr ""
"Note that drilldown to the column which stores string is slower than the "
"columns which stores the other types. If you drilldown to string type of "
"column, create the table that type of primary key is string, then create the "
"column which refers that table."

# 974cdb686de7419a9bce160ebee98cb6
msgid "Tag search and reverse resolution of reference relationships"
msgstr "Tag search and reverse resolution of reference relationships"

# 06c0c8ad66c84694889dbde919a8be41
msgid ""
"As you know, Groonga supports to store array in column which refers other "
"table. In fact, you can do tag search by using array data which refers other "
"table."
msgstr ""
"As you know, Groonga supports to store array in column which refers other "
"table. In fact, you can do tag search by using array data which refers other "
"table."

# 7bbbb103525e4dc1887f03683ffcf64d
msgid ""
"Tag search is very fast because Groonga use inverted index as data structure."
msgstr ""
"Tag search is very fast because Groonga use inverted index as data structure."

# beccc80be4ce43aabea843fc833c6128
msgid "Tag search"
msgstr "Tag search"

# 7d7b09c74b4947f4a77c0c8ebcc86be9
msgid ""
"Let's consider to create a search engine for an web site to share movies. "
"Each movie may be associated with multiple keywords which represents the "
"content of movie."
msgstr ""
"Let's consider to create a search engine for an web site to share movies. "
"Each movie may be associated with multiple keywords which represents the "
"content of movie."

# 0fffb4e4e777467e89f49a109ca74ea8
msgid "Let's create tables for movie information, then search the movies."
msgstr "Let's create tables for movie information, then search the movies."

# cd2f4b80c14745acb2b77786f411aa97
msgid ""
"First, create the ``Video`` table which stores movie information. the "
"``Video`` table has two columns. the ``title`` column stores title of the "
"movie. the ``tags`` column stores multiple tag information in reference Tag "
"table."
msgstr ""
"First, create the ``Video`` table which stores movie information. the "
"``Video`` table has two columns. the ``title`` column stores title of the "
"movie. the ``tags`` column stores multiple tag information in reference Tag "
"table."

# 9c93eecfc285477fa1e0a2022b6a7e89
msgid ""
"Next, create the ``Tag`` table which stores tag information. the ``Tag`` "
"table has one column. The tag string is stored as primary key, then "
"``index_tags`` stores indexes for tags column of Video table."
msgstr ""
"Next, create the ``Tag`` table which stores tag information. the ``Tag`` "
"table has one column. The tag string is stored as primary key, then "
"``index_tags`` stores indexes for tags column of Video table."

# ac0f85f3fc93443fad140d52e6d53cd0
msgid ""
"After creating indexed column, you can do full-text search very fast. The "
"indexed column is also automatically updated when stored data is refreshed."
msgstr ""
"After creating indexed column, you can do full-text search very fast. The "
"indexed column is also automatically updated when stored data is refreshed."

# dee373de3f2c4c5c985d25185a9bb239
msgid "List up the movies that specific keywords are given."
msgstr "List up the movies that specific keywords are given."

# 8019f374b456482091b73e10f2e5523d
msgid ""
"You can search by tags such as \"Variety\", \"Sports\" and \"Animation\"."
msgstr ""
"You can search by tags such as \"Variety\", \"Sports\" and \"Animation\"."

# ddddf043ee9b46cda50cd79a4328dcda
msgid "Reverse resolution of reference relationships"
msgstr "Reverse resolution of reference relationships"

# 644ecb9fe9684fbabb4d86d7c59a1788
msgid ""
"Groonga supports indexes for reverse resolution among tables. Tag search is "
"one of concrete examples."
msgstr ""
"Groonga supports indexes for reverse resolution among tables. Tag search is "
"one of concrete examples."

# 72464ca450a04a38b6869d9302cd7336
msgid ""
"For example, you can search friendships by reverse resolution in social "
"networking site."
msgstr ""
"For example, you can search friendships by reverse resolution in social "
"networking site."

# 538b2a52544b4311a5eba2cce0f11bc6
msgid ""
"Following example shows how to create ``User`` table which stores user "
"information, ``username`` column which stores user name, ``friends`` column "
"which stores list of user's friends in array, ``index_friends`` column as "
"indexed column."
msgstr ""
"Following example shows how to create ``User`` table which stores user "
"information, ``username`` column which stores user name, ``friends`` column "
"which stores list of user's friends in array, ``index_friends`` column as "
"indexed column."

# 424672e62daf418688c1e225bba66d1f
msgid "Let's show list of users who contains specified user in friend list."
msgstr "Let's show list of users who contains specified user in friend list."

# fe38921dff9845fe8c233787dbc8018e
msgid "Then drilldown the count which shows user is listed as friend."
msgstr "Then drilldown the count which shows user is listed as friend."

# 6c140a9663c04d55af5a3a204f4b4bab
msgid ""
"As you can see, it shows the results which follows reverse resolution of "
"reference relationship."
msgstr ""
"As you can see, it shows the results which follows reverse resolution of "
"reference relationship."

# 34a6416eafe14c2aa88eeae553fd63b7
msgid "Geo location search with index"
msgstr "Geo location search with index"

# 67c5666809fd488e9259e04825c8b7b2
msgid ""
"Groonga supports to add indexes to the column which stores geo location "
"information. Groonga is very fast because it use such indexes against the "
"column which contains geo location information to search enormous number of "
"records."
msgstr ""
"Groonga supports to add indexes to the column which stores geo location "
"information. Groonga is very fast because it use such indexes against the "
"column which contains geo location information to search enormous number of "
"records."

# 16b48a10708c48c189521308cae1497e
msgid ""
"These indexes are also used when sorting the records with geo location "
"search."
msgstr ""
"These indexes are also used when sorting the records with geo location "
"search."

# cbee9f211df640b1a5c1b9cb3cfd92d0
msgid "Basic operations"
msgstr "Basic operations"

# 6db9b1ca9af04e05b5be25ba6c73a98f
msgid ""
"A Groonga package provides a C library (libgroonga) and a command line tool "
"(groonga). This tutorial explains how to use the command line tool, with "
"which you can create/operate databases, start a server, establish a "
"connection with a server, etc."
msgstr ""
"A Groonga package provides a C library (libgroonga) and a command line tool "
"(groonga). This tutorial explains how to use the command line tool, with "
"which you can create/operate databases, start a server, establish a "
"connection with a server, etc."

# 2b1ace1bee0c421e9c7b385d7485814a
msgid "Create a database"
msgstr "Create a database"

# b46201622dab4cea92802da0ceff54b8
msgid ""
"The first step to using Groonga is to create a new database. The following "
"shows how to do it."
msgstr ""
"The first step to using Groonga is to create a new database. The following "
"shows how to do it."

# e5996e03cc8e43e7a32affcccac5c6d7
# f9a18954ae0346a0aacd1df286c0d23d
# 85a191b2ce714c4892ffeb432d9eeb07
msgid "Form::"
msgstr "Form::"

# bd930b41552a41a8b3528625bc963703
msgid ""
"The `-n` option specifies to create a new database and DB_PATH specifies the "
"path of the new database. Actually, a database consists of a series of files "
"and DB_PATH specifies the file which will be the entrance to the new "
"database. DB_PATH also specifies the path prefix for other files. Note that "
"database creation fails if DB_PATH points to an existing file."
msgstr ""
"The `-n` option specifies to create a new database and DB_PATH specifies the "
"path of the new database. Actually, a database consists of a series of files "
"and DB_PATH specifies the file which will be the entrance to the new "
"database. DB_PATH also specifies the path prefix for other files. Note that "
"database creation fails if DB_PATH points to an existing file."

# 51140e88586448a281d0623bb8755ceb
msgid ""
"This command creates a new database and then enters into interactive mode in "
"which Groonga prompts you to enter commands for operating that database. You "
"can terminate this mode with Ctrl-d."
msgstr ""
"This command creates a new database and then enters into interactive mode in "
"which Groonga prompts you to enter commands for operating that database. You "
"can terminate this mode with Ctrl-d."

# b17a7d194c2b46638d2ba0557b11348a
msgid ""
"After this database creation, you can find a series of files in /tmp/groonga-"
"databases."
msgstr ""
"After this database creation, you can find a series of files in /tmp/groonga-"
"databases."

# 1c27718e18724d10a4374ee469ef50c8
msgid "Operate a database"
msgstr "Operate a database"

# bda128abdc36424a8d7ab77a5616fabb
msgid "The following shows how to operate an existing database."
msgstr "The following shows how to operate an existing database."

# 32d95096897642e9aa8947ec5276ec60
msgid ""
"DB_PATH specifies the path of a target database. This command fails if the "
"specified database does not exist."
msgstr ""
"DB_PATH specifies the path of a target database. This command fails if the "
"specified database does not exist."

# 28bfa96970d4469b924df09c6fe4e322
msgid ""
"If COMMAND is specified, Groonga executes COMMAND and returns the result. "
"Otherwise, Groonga starts in interactive mode that reads commands from the "
"standard input and executes them one by one. This tutorial focuses on the "
"interactive mode."
msgstr ""
"If COMMAND is specified, Groonga executes COMMAND and returns the result. "
"Otherwise, Groonga starts in interactive mode that reads commands from the "
"standard input and executes them one by one. This tutorial focuses on the "
"interactive mode."

# 0b2d58ab43bf49aa9013eb17bbed7af1
msgid ""
"Let's see the status of a Groonga process by using a :doc:`/reference/"
"commands/status` command."
msgstr ""
"Let's see the status of a Groonga process by using a :doc:`/reference/"
"commands/status` command."

# 70b61e62905142f882f56e40083e4000
msgid ""
"As shown in the above example, a command returns a JSON array. The first "
"element contains an error code, execution time, etc. The second element is "
"the result of an operation."
msgstr ""
"As shown in the above example, a command returns a JSON array. The first "
"element contains an error code, execution time, etc. The second element is "
"the result of an operation."

# f6b9c44b5dd848e1972290b8cd69a0a6
msgid "Command format"
msgstr "Command format"

# 9886cb20722748f89d8ac7b1388b9448
msgid "Commands for operating a database accept arguments as follows::"
msgstr "Commands for operating a database accept arguments as follows::"

# 83ea16685f5a4e149c7e908d6763b8bc
msgid ""
"In the first form, arguments must be passed in order. This kind of arguments "
"are called positional arguments because the position of each argument "
"determines its meaning."
msgstr ""
"In the first form, arguments must be passed in order. This kind of arguments "
"are called positional arguments because the position of each argument "
"determines its meaning."

# 54e85eddbbb4440985d5b6a5ffb972de
msgid ""
"In the second form, you can specify a parameter name with its value. So, the "
"order of arguments is not defined. This kind of arguments are known as named "
"parameters or keyword arguments."
msgstr ""
"In the second form, you can specify a parameter name with its value. So, the "
"order of arguments is not defined. This kind of arguments are known as named "
"parameters or keyword arguments."

# 2105ac3a3bbf4da484cdfe2bc4d10036
msgid ""
"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."
msgstr ""
"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."

# d124bb10fb0f49bbace9404ce6520e75
msgid ""
"For details, see also the paragraph of \"command\" in :doc:`/reference/"
"executables/groonga`."
msgstr ""
"For details, see also the paragraph of \"command\" in :doc:`/reference/"
"executables/groonga`."

# 8515492874f249b48e142eda5c5fa91c
msgid "Basic commands"
msgstr "Basic commands"

# 73903a3ee98a41c98fb2983765f6ad37
msgid ":doc:`/reference/commands/status`"
msgstr ":doc:`/reference/commands/status`"

# 6ce522ebbf3041a7af70991e4738d26e
msgid "shows status of a Groonga process."
msgstr "shows status of a Groonga process."

# 03d6c6a8f480400b917ea213dfcf8643
msgid ":doc:`/reference/commands/table_list`"
msgstr ":doc:`/reference/commands/table_list`"

# 9238c40fcdd1464289d8fffa3ed6a8bb
msgid "shows a list of tables in a database."
msgstr "shows a list of tables in a database."

# 0d993b3be81d4fa583f832c12ba7bb45
msgid ":doc:`/reference/commands/column_list`"
msgstr ":doc:`/reference/commands/column_list`"

# a5c9e75249c2458cb2d25eac8829524e
msgid "shows a list of columns in a table."
msgstr "shows a list of columns in a table."

# 5b444399de3b41d29615d18186bbb9a1
msgid ":doc:`/reference/commands/table_create`"
msgstr ":doc:`/reference/commands/table_create`"

# 2a2472abc6b7436ab4e1deb2b736f1b9
msgid "adds a table to a database."
msgstr "adds a table to a database."

# eebe57d029b344d5818222cf3d716304
msgid ":doc:`/reference/commands/column_create`"
msgstr ":doc:`/reference/commands/column_create`"

# 20cf780648ba4392ae40882878a2848d
msgid "adds a column to a table."
msgstr "adds a column to a table."

# ba42f357392b49b89130e8b104c982f7
msgid ":doc:`/reference/commands/select`"
msgstr ":doc:`/reference/commands/select`"

# e0a378004f054cefa0e75cbe4677a858
msgid "searches records from a table and shows the result."
msgstr "searches records from a table and shows the result."

# abd4a96b09364bcbb74b02d42e9773bd
msgid ":doc:`/reference/commands/load`"
msgstr ":doc:`/reference/commands/load`"

# 65eae0c3f5dc4985867c9207630d7503
msgid "inserts records to a table."
msgstr "inserts records to a table."

# 1c81075e2c884073b401918d29206a30
# 93baa40450e74209a36e5e48855f2316
msgid "Create a table"
msgstr "Create a table"

# 813ec6d2df7541d3b5aa03d6efeef2f7
msgid "A :doc:`/reference/commands/table_create` command creates a new table."
msgstr "A :doc:`/reference/commands/table_create` command creates a new table."

# 0bc333d947f340888a78b81a6e0f6dae
msgid ""
"In most cases, a table has a primary key which must be specified with its "
"data type and index type."
msgstr ""
"In most cases, a table has a primary key which must be specified with its "
"data type and index type."

# 03f7347b3f7f426585f90d7f7ad3ae09
msgid ""
"There are various data types such as integers, strings, etc. See also :doc:`/"
"reference/types` for more details. The index type determines the search "
"performance and the availability of prefix searches. The details will be "
"described later."
msgstr ""
"There are various data types such as integers, strings, etc. See also :doc:`/"
"reference/types` for more details. The index type determines the search "
"performance and the availability of prefix searches. The details will be "
"described later."

# e1f8c14ce7df43e0ab69c853606bf0c1
msgid ""
"Let's create a table. The following example creates a table with a primary "
"key. The `name` parameter specifies the name of the table. The `flags` "
"parameter specifies the index type for the primary key. The `key_type` "
"parameter specifies the data type of the primary key."
msgstr ""
"Let's create a table. The following example creates a table with a primary "
"key. The `name` parameter specifies the name of the table. The `flags` "
"parameter specifies the index type for the primary key. The `key_type` "
"parameter specifies the data type of the primary key."

# 309fb6eb5a354af3bf01d84120d17793
msgid ""
"The second element of the result indicates that the operation succeeded."
msgstr ""
"The second element of the result indicates that the operation succeeded."

# f162d8f3857349a28de580603b34062e
msgid "View a table"
msgstr "View a table"

# f76c8f54e648461ebb12d08d86dcf12b
msgid ""
"A :doc:`/reference/commands/select` command can enumerate records in a table."
msgstr ""
"A :doc:`/reference/commands/select` command can enumerate records in a table."

# 57bb44d899d54f40a9c26e0278e7aea7
msgid ""
"When only a table name is specified with a `table` parameter, a :doc:`/"
"reference/commands/select` command returns the first (at most) 10 records in "
"the table. [0] in the result shows the number of records in the table. The "
"next array is a list of columns. [\"_id\",\"Uint32\"] is a column of UInt32, "
"named _id. [\"_key\",\"ShortText\"] is a column of ShortText, named _key."
msgstr ""
"When only a table name is specified with a `table` parameter, a :doc:`/"
"reference/commands/select` command returns the first (at most) 10 records in "
"the table. [0] in the result shows the number of records in the table. The "
"next array is a list of columns. [\"_id\",\"Uint32\"] is a column of UInt32, "
"named _id. [\"_key\",\"ShortText\"] is a column of ShortText, named _key."

# 8366e8a6e4de40b89dda1e572977eac8
msgid ""
"The above two columns, _id and _key, are the necessary columns. The _id "
"column stores IDs those are automatically allocated by Groonga. The _key "
"column is associated with the primary key. You are not allowed to rename "
"these columns."
msgstr ""
"The above two columns, _id and _key, are the necessary columns. The _id "
"column stores IDs those are automatically allocated by Groonga. The _key "
"column is associated with the primary key. You are not allowed to rename "
"these columns."

# 962a6c87512343acb4351dad73edb47b
msgid "Create a column"
msgstr "Create a column"

# fdf4c7ae8e1d43aa9319b227313aab38
msgid ""
"A :doc:`/reference/commands/column_create` command creates a new column."
msgstr ""
"A :doc:`/reference/commands/column_create` command creates a new column."

# 0e52796076dd4f0e86ec508a4a45fc0e
msgid ""
"Let's add a column. The following example adds a column to the Site table. "
"The `table` parameter specifies the target table. The `name` parameter "
"specifies the name of the column. The `type` parameter specifies the data "
"type of the column."
msgstr ""
"Let's add a column. The following example adds a column to the Site table. "
"The `table` parameter specifies the target table. The `name` parameter "
"specifies the name of the column. The `type` parameter specifies the data "
"type of the column."

# 297ad9c95a3c4900b1d4be2ec83d29fe
msgid "Load records"
msgstr "Load records"

# 2683ed92bdc840aaa2141971d9069f05
msgid ""
"A :doc:`/reference/commands/load` command loads JSON-formatted records into "
"a table."
msgstr ""
"A :doc:`/reference/commands/load` command loads JSON-formatted records into "
"a table."

# 2a11affc6cf940778994c9a22cecb998
msgid "The following example loads nine records into the Site table."
msgstr "The following example loads nine records into the Site table."

# 0a50d4f2f9774db78fa04787ebf87b6a
msgid ""
"The second element of the result indicates how many records were "
"successfully loaded. In this case, all the records are successfully loaded."
msgstr ""
"The second element of the result indicates how many records were "
"successfully loaded. In this case, all the records are successfully loaded."

# 8b0a2fc21efe411396fb1e58c05f8982
msgid "Let's make sure that these records are correctly stored."
msgstr "Let's make sure that these records are correctly stored."

# a2af0bd849d34ce791731f0808ed7bae
msgid "Get a record"
msgstr "Get a record"

# 10198bf58de94b76a0b835c4ff131581
msgid ""
"A :doc:`/reference/commands/select` command can search records in a table."
msgstr ""
"A :doc:`/reference/commands/select` command can search records in a table."

# b539150ed5874feabfec2399fe7d0d0a
msgid ""
"If a search condition is specified with a `query` parameter, a :doc:`/"
"reference/commands/select` command searches records matching the search "
"condition and returns the matched records."
msgstr ""
"If a search condition is specified with a `query` parameter, a :doc:`/"
"reference/commands/select` command searches records matching the search "
"condition and returns the matched records."

# 0ed53cf901b54f1d809c97dcee2733ae
msgid ""
"Let's get a record having a specified record ID. The following example gets "
"the first record in the Site table. More precisely, the `query` parameter "
"specifies a record whose _id column stores 1."
msgstr ""
"Let's get a record having a specified record ID. The following example gets "
"the first record in the Site table. More precisely, the `query` parameter "
"specifies a record whose _id column stores 1."

# 1aafba2df7f54d618832eb02548c87de
msgid ""
"Next, let's get a record having a specified key. The following example gets "
"the record whose primary key is \"http://example.org/\". More precisely, the "
"`query` parameter specifies a record whose _key column stores \"http://"
"example.org/\"."
msgstr ""
"Next, let's get a record having a specified key. The following example gets "
"the record whose primary key is \"http://example.org/\". More precisely, the "
"`query` parameter specifies a record whose _key column stores \"http://"
"example.org/\"."

# f7a3588ef1e94148a68ac105bafb8507
msgid "Create a lexicon table for full text search"
msgstr "Create a lexicon table for full text search"

# 220c9dc8db2e4716b5493c7f3c69f596
msgid "Let's go on to how to make full text search."
msgstr "Let's go on to how to make full text search."

# a983068603764e7290933eed1f65e30d
msgid ""
"Groonga uses an inverted index to provide fast full text search. So, the "
"first step is to create a lexicon table which stores an inverted index, also "
"known as postings lists. The primary key of this table is associated with a "
"vocabulary made up of index terms and each record stores postings lists for "
"one index term."
msgstr ""
"Groonga uses an inverted index to provide fast full text search. So, the "
"first step is to create a lexicon table which stores an inverted index, also "
"known as postings lists. The primary key of this table is associated with a "
"vocabulary made up of index terms and each record stores postings lists for "
"one index term."

# 69bcfc7784774b6d8a3b32b2984582f9
msgid ""
"The following shows a command which creates a lexicon table named Terms. The "
"data type of its primary key is ShortText."
msgstr ""
"The following shows a command which creates a lexicon table named Terms. The "
"data type of its primary key is ShortText."

# 64f76f02b1a74effbd5887b7681bffee
msgid ""
"The :doc:`/reference/commands/table_create` command takes many parameters "
"but you don't need to understand all of them. Please skip the next paragraph "
"if you are not interested in how it works."
msgstr ""
"The :doc:`/reference/commands/table_create` command takes many parameters "
"but you don't need to understand all of them. Please skip the next paragraph "
"if you are not interested in how it works."

# f61e097b1bf7430cb553a7cb4d8e5dc7
msgid ""
"The TABLE_PAT_KEY flag specifies to store index terms in a patricia trie. "
"The KEY_NORMALIZE flag specifies to normalize index terms. In this example, "
"both flags are validated by using a '|'. The `default_tokenizer` parameter "
"specifies the method for tokenizing text. This example uses TokenBigram that "
"is generally called N-gram."
msgstr ""
"The TABLE_PAT_KEY flag specifies to store index terms in a patricia trie. "
"The KEY_NORMALIZE flag specifies to normalize index terms. In this example, "
"both flags are validated by using a '|'. The `default_tokenizer` parameter "
"specifies the method for tokenizing text. This example uses TokenBigram that "
"is generally called N-gram."

# ecd4d78fc556474ab7cd61e119a57a3a
msgid "Create an index column for full text search"
msgstr "Create an index column for full text search"

# 8bb360028ac8407a85a8b001152c8cb6
msgid ""
"The second step is to create an index column, which allows you to search "
"records from its associated column. That is to say this step specifies which "
"column needs an index."
msgstr ""
"The second step is to create an index column, which allows you to search "
"records from its associated column. That is to say this step specifies which "
"column needs an index."

# 4e261d7d58ad4d9c857fdb08064e1766
msgid ""
"Let's create an index column. The following example creates an index column "
"for a column in the Site table."
msgstr ""
"Let's create an index column. The following example creates an index column "
"for a column in the Site table."

# df1fc5cf1d85476baf22d186c92a36fa
msgid ""
"The `table` parameter specifies the index table and the `name` parameter "
"specifies the index column. The `type` parameter specifies the target table "
"and the `source` parameter specifies the target column. The COLUMN_INDEX "
"flag specifies to create an index column and the WITH_POSITION flag "
"specifies to create a full inverted index, which contains the positions of "
"each index term. This combination, COLUMN_INDEX|WITH_POSITION, is "
"recommended for the general purpose."
msgstr ""
"The `table` parameter specifies the index table and the `name` parameter "
"specifies the index column. The `type` parameter specifies the target table "
"and the `source` parameter specifies the target column. The COLUMN_INDEX "
"flag specifies to create an index column and the WITH_POSITION flag "
"specifies to create a full inverted index, which contains the positions of "
"each index term. This combination, COLUMN_INDEX|WITH_POSITION, is "
"recommended for the general purpose."

# fcd350ba13a64b4dbb540f736123fa88
msgid ""
"You can create a lexicon table and index columns before/during/after loading "
"records. If a target column already has records, Groonga creates an inverted "
"index in a static manner. In contrast, if you load records into an already "
"indexed column, Groonga updates the inverted index in a dynamic manner."
msgstr ""
"You can create a lexicon table and index columns before/during/after loading "
"records. If a target column already has records, Groonga creates an inverted "
"index in a static manner. In contrast, if you load records into an already "
"indexed column, Groonga updates the inverted index in a dynamic manner."

# 1ddfc2599a2a4eba82291ec57a48a57d
msgid "Full text search"
msgstr "Full text search"

# 9e29cc816a1c4451b9c5040bfedb0c54
msgid ""
"It's time. You can make full text search with a :doc:`/reference/commands/"
"select` command."
msgstr ""
"It's time. You can make full text search with a :doc:`/reference/commands/"
"select` command."

# 6cbeedbdafc24369b308ec7eaadc71a9
msgid ""
"A query for full text search is specified with a `query` parameter. The "
"following example searches records whose \"title\" column contains \"this\". "
"The '@' specifies to make full text search. Note that a lower case query "
"matches upper case and capitalized terms in a record if KEY_NORMALIZE was "
"specified when creating a lexcon table."
msgstr ""
"A query for full text search is specified with a `query` parameter. The "
"following example searches records whose \"title\" column contains \"this\". "
"The '@' specifies to make full text search. Note that a lower case query "
"matches upper case and capitalized terms in a record if KEY_NORMALIZE was "
"specified when creating a lexcon table."

# 7642a6c1985c404480a8fdbe0e376686
msgid ""
"In this example, the first record matches the query because its title "
"contains \"This\", that is the capitalized form of the query."
msgstr ""
"In this example, the first record matches the query because its title "
"contains \"This\", that is the capitalized form of the query."

# 39a47f507e5f4d73989a7b071c905416
msgid ""
"A :doc:`/reference/commands/select` command accepts an optional parameter, "
"named `match_columns`, that specifies the default target columns. This "
"parameter is used if target columns are not specified in a query. [#]_"
msgstr ""
"A :doc:`/reference/commands/select` command accepts an optional parameter, "
"named `match_columns`, that specifies the default target columns. This "
"parameter is used if target columns are not specified in a query. [#]_"

# 6d8985320ddb484090488ed81ac3fe27
msgid ""
"The combination of \"`--match_columns` title\" and \"`--query` this\" brings "
"you the same result that \"`--query` title:@this\" does."
msgstr ""
"The combination of \"`--match_columns` title\" and \"`--query` this\" brings "
"you the same result that \"`--query` title:@this\" does."

# 3d3323e835a7461cb080c3d7dd078bad
msgid "Specify output columns"
msgstr "Specify output columns"

# e70e13aa00554ec6a13413603ae3fcb5
msgid ""
"An `output_columns` parameter of a :doc:`/reference/commands/select` command "
"specifies columns to appear in the search result. If you want to specify "
"more than one columns, please separate column names by commas (',')."
msgstr ""
"An `output_columns` parameter of a :doc:`/reference/commands/select` command "
"specifies columns to appear in the search result. If you want to specify "
"more than one columns, please separate column names by commas (',')."

# d7f8153f2321402685b9e3e0a5fcfd59
msgid ""
"This example specifies three output columns including the _score column, "
"which stores the relevance score of each record."
msgstr ""
"This example specifies three output columns including the _score column, "
"which stores the relevance score of each record."

# e22e60ebdfb84696a297902fffa3f803
msgid "Specify output ranges"
msgstr "Specify output ranges"

# f20c57bcec9c4237a0265e145a3bd6a0
msgid ""
"A :doc:`/reference/commands/select` command returns a part of its search "
"result if `offset` and/or `limit` parameters are specified. These parameters "
"are useful to paginate a search result, a widely-used interface which shows "
"a search result on a page by page basis."
msgstr ""
"A :doc:`/reference/commands/select` command returns a part of its search "
"result if `offset` and/or `limit` parameters are specified. These parameters "
"are useful to paginate a search result, a widely-used interface which shows "
"a search result on a page by page basis."

# 018a2f75841540c18f48be384de7af7f
msgid ""
"An `offset` parameter specifies the starting point and a `limit` parameter "
"specifies the maximum number of records to be returned. If you need the "
"first record in a search result, the offset parameter must be 0 or omitted."
msgstr ""
"An `offset` parameter specifies the starting point and a `limit` parameter "
"specifies the maximum number of records to be returned. If you need the "
"first record in a search result, the offset parameter must be 0 or omitted."

# 889a7448796c478facdca7a157f03ea1
msgid "Sort a search result"
msgstr "Sort a search result"

# 4928e02b170c4818961861dd3e2f74b7
msgid ""
"A :doc:`/reference/commands/select` command sorts its result when used with "
"a `sortby` parameter."
msgstr ""
"A :doc:`/reference/commands/select` command sorts its result when used with "
"a `sortby` parameter."

# 9c057e39fb554193a0a1419a7037285c
msgid ""
"A `sortby` parameter specifies a column as a sorting creteria. A search "
"result is arranged in ascending order of the column values. If you want to "
"sort a search result in reverse order, please add a leading hyphen ('-') to "
"the column name in a parameter."
msgstr ""
"A `sortby` parameter specifies a column as a sorting creteria. A search "
"result is arranged in ascending order of the column values. If you want to "
"sort a search result in reverse order, please add a leading hyphen ('-') to "
"the column name in a parameter."

# 434c3e4870b2461b89d214f3dbb097b0
msgid "The following example shows records in the Site table in reverse order."
msgstr ""
"The following example shows records in the Site table in reverse order."

# 4eb28ad83476485c8bd2be0df5d0e774
msgid ""
"The next example uses the _score column as the sorting criteria for ranking "
"the search result. The result is sorted in relevance order."
msgstr ""
"The next example uses the _score column as the sorting criteria for ranking "
"the search result. The result is sorted in relevance order."

# 2ce91ecb5e914304802dfb344bfd6f2b
msgid ""
"If you want to specify more than one columns, please separate column names "
"by commas (','). In such a case, a search result is sorted in order of the "
"values in the first column, and then records having the same values in the "
"first column are sorted in order of the second column values."
msgstr ""
"If you want to specify more than one columns, please separate column names "
"by commas (','). In such a case, a search result is sorted in order of the "
"values in the first column, and then records having the same values in the "
"first column are sorted in order of the second column values."

# 7a08187dc61c4ba7af759fc67f875d20
msgid "footnote"
msgstr "footnote"

# 2204ae21d6c648e5be271d56975ca3ff
msgid ""
"Currently, a `match_columns` parameter is available iff there exists an "
"inverted index for full text search. A `match_columns` parameter for a "
"regular column is not supported."
msgstr ""
"Currently, a `match_columns` parameter is available iff there exists an "
"inverted index for full text search. A `match_columns` parameter for a "
"regular column is not supported."

# 75ef873a308641549759c3ee365a65c2
msgid "Additional information about lexicon for full text search"
msgstr "Additional information about lexicon for full text search"

# 026b344817954d5eb8cc2453335f214f
msgid ""
"Groonga uses lexicon for full text search as a table. Thus, Groonga can hold "
"multiple information each lexicon. For example, Groonga holds frequency of "
"word, flags for stop word, importance of word and so on."
msgstr ""
"Groonga uses lexicon for full text search as a table. Thus, Groonga can hold "
"multiple information each lexicon. For example, Groonga holds frequency of "
"word, flags for stop word, importance of word and so on."

# 8e3a3bf33bd44a96be62ff0dd27f3c11
msgid "TODO: Write document."
msgstr "TODO: Write document."

# f800e675c29e40ab96da099ffcf71ba5
msgid "match_columns parameter"
msgstr "match_columns parameter"

# ec3f72cfb13a4a2fb8643d1494d48a3d
msgid "Full-text search against multiple columns"
msgstr "Full-text search against multiple columns"

# 2e1ba07b9ede490f844622ebc577a8b8
msgid ""
"Groonga supports full-text search against multiple columns. Let's consider "
"blog site. Usually, blog site has a table which contains title column and "
"content column. How do you search the blog entry which contains specified "
"keywords in title or content?"
msgstr ""
"Groonga supports full-text search against multiple columns. Let's consider "
"blog site. Usually, blog site has a table which contains title column and "
"content column. How do you search the blog entry which contains specified "
"keywords in title or content?"

# dfe96fdbe7d84cf1916a5035db72ea3d
msgid ""
"In such a case, there are two ways to create indexes. One way is creating "
"column index against each column. The other way is creating one column index "
"against multiple columns. Either way, Groonga supports similar full-text "
"search syntax."
msgstr ""
"In such a case, there are two ways to create indexes. One way is creating "
"column index against each column. The other way is creating one column index "
"against multiple columns. Either way, Groonga supports similar full-text "
"search syntax."

# 5fa1385a6fdd4b83b37cabe095e78209
msgid "Creating column index against each column"
msgstr "Creating column index against each column"

# 58981a0173384ca2864cd10d4b2f25b1
msgid "Here is the example which create column index against each column."
msgstr "Here is the example which create column index against each column."

# 2d2665127ef44222a7e419eeb815d21f
msgid ""
"First, create ``Blog1`` table, add ``title`` column which stores title "
"string, ``message`` column which stores content of blog entry."
msgstr ""
"First, create ``Blog1`` table, add ``title`` column which stores title "
"string, ``message`` column which stores content of blog entry."

# 053f28621a3347829fa87d41ca68224e
msgid ""
"Then create ``IndexBlog1`` table for column indexes, add ``index_title`` "
"column for ``title`` column, ``index_message`` column for ``message`` column."
msgstr ""
"Then create ``IndexBlog1`` table for column indexes, add ``index_title`` "
"column for ``title`` column, ``index_message`` column for ``message`` column."

# 4b9be74fb6304a27a8dd63368673442b
msgid ""
"``match_columns`` option of ``select`` command accepts multiple columns as "
"search target. Specify query string to ``query`` option. Then you can do "
"full-text search title and content of blog entries."
msgstr ""
"``match_columns`` option of ``select`` command accepts multiple columns as "
"search target. Specify query string to ``query`` option. Then you can do "
"full-text search title and content of blog entries."

# e4f2b853d03341259e1449ece007b81b
msgid "Let's try to search blog entries."
msgstr "Let's try to search blog entries."

# 2e9b28a28f224b089cc79884de26c388
msgid "Creating one column index against multiple columns"
msgstr "Creating one column index against multiple columns"

# 6d658b04b88b48d2867c2099dc7280ed
msgid "Groonga also supports one column index against multiple columns."
msgstr "Groonga also supports one column index against multiple columns."

# f0e09953cc5b4a8b85f851da40c0e32b
msgid ""
"The difference for previous example is only one column index exists. Thus, "
"There is one common column index against title and message column."
msgstr ""
"The difference for previous example is only one column index exists. Thus, "
"There is one common column index against title and message column."

# 5669ee42f0a246dd8c81e80ffe6ebeda
msgid ""
"Even though same column index is used, Groonga supports to search against "
"title column only, message column only and title or message column."
msgstr ""
"Even though same column index is used, Groonga supports to search against "
"title column only, message column only and title or message column."

# 5505b256e3b64686a02952adb62bd791
msgid ""
"Let's search same query in previous section. You can get same search results."
msgstr ""
"Let's search same query in previous section. You can get same search results."

# 0734d8c8c6a14f18aa913c4495ecfeda
msgid ""
"There may be a question that \"which is the better solution for indexing.\" "
"It depends on the case."
msgstr ""
"There may be a question that \"which is the better solution for indexing.\" "
"It depends on the case."

# f5ef326c817544b7a14913abc7b9f18c
msgid ""
"Indexes for each column - The update performance tends to be better than "
"multiple colum index because there is enough buffer for updating. On the "
"other hand, the efficiency of disk usage is not so good."
msgstr ""
"Indexes for each column - The update performance tends to be better than "
"multiple colum index because there is enough buffer for updating. On the "
"other hand, the efficiency of disk usage is not so good."

# 84bbb7d413ee4322b6535b59a217defe
msgid ""
"Indexes for multiple column - It saves disk usage because it shares common "
"buffer. On the other hand, the update performance is not so good."
msgstr ""
"Indexes for multiple column - It saves disk usage because it shares common "
"buffer. On the other hand, the update performance is not so good."

# 2d98880ef2dd4e83a71b3a6e87de524a
msgid "Full text search with specific index name"
msgstr "Full text search with specific index name"

# 514880c3999645ee95237bbbeeb11243
# c36604c3668c45dabfc74a5b9b10137f
msgid "TODO"
msgstr "TODO"

# d2ee6404afe24f35b71ab624643c2da2
msgid "Nested index search among related table by column index"
msgstr "Nested index search among related table by column index"

# aa661c41ed9e41dbb6a7b001c2b7759d
msgid ""
"If there are relationships among multiple table with column index, you can "
"search multiple table by specifying reference column name."
msgstr ""
"If there are relationships among multiple table with column index, you can "
"search multiple table by specifying reference column name."

# 8fecebdaf3ac49d0afa045b9803eb0c9
msgid "Here is the concrete example."
msgstr "Here is the concrete example."

# 8261b1b596f944219e3b4fa54dda6385
msgid ""
"There are tables which store blog articles, comments for articles. The table "
"which stores articles has columns for article and comment. And the comment "
"column refers Comments table. The table which stores comments has columns "
"for comment and column index to article table."
msgstr ""
"There are tables which store blog articles, comments for articles. The table "
"which stores articles has columns for article and comment. And the comment "
"column refers Comments table. The table which stores comments has columns "
"for comment and column index to article table."

# 350f14e4a86c45c792f916679fef0f8d
msgid ""
"if you want to search the articles which contain specified keyword in "
"comment, you need to execute fulltext search for table of comment, then "
"search the records which contains fulltext search results."
msgstr ""
"if you want to search the articles which contain specified keyword in "
"comment, you need to execute fulltext search for table of comment, then "
"search the records which contains fulltext search results."

# 47261fd88b40454191a9511a9ef04965
msgid ""
"But, you can search the records by specifying the reference column index at "
"once."
msgstr ""
"But, you can search the records by specifying the reference column index at "
"once."

# 423593147e7f470aaa13e6b1c0449750
msgid "Here is the sample schema."
msgstr "Here is the sample schema."

# f25e1687379c42d49b95f7c23b177f9d
# 80014feb16a04313ad2ba6aa0ab0acc7
msgid "Here is the sample data."
msgstr "Here is the sample data."

# f9f00802ffac4d778c0e236d11899658
msgid ""
"You can write the query that search the records which contains specified "
"keyword as a comment, then fetch the articles which refers to it."
msgstr ""
"You can write the query that search the records which contains specified "
"keyword as a comment, then fetch the articles which refers to it."

# 38b945253b9e452d808aec4120e2a423
# c7cfff4f48694c318ebdf2cd6db1d2e1
msgid "Query for searching the records described above::"
msgstr "Query for searching the records described above::"

# 93e1fe964d744cfabc3d8e1ae975cf5e
msgid ""
"You need to concatenate comment column of Articles table and content column "
"of Comments table with period( ``.`` ) as ``--match_columns`` arguments."
msgstr ""
"You need to concatenate comment column of Articles table and content column "
"of Comments table with period( ``.`` ) as ``--match_columns`` arguments."

# c5d20fd281b248128d5964143ddba14c
msgid ""
"At first, this query execute fulltext search from content of Comments table, "
"then fetch the records of Articles table which refers to already searched "
"records of Comments table. (Because of this, if you comment out the query "
"which creates index column ``article`` of Comments table, you can't get "
"intended search results.)"
msgstr ""
"At first, this query execute fulltext search from content of Comments table, "
"then fetch the records of Articles table which refers to already searched "
"records of Comments table. (Because of this, if you comment out the query "
"which creates index column ``article`` of Comments table, you can't get "
"intended search results.)"

# fe824c23dea44d19b42298527f7d1d56
msgid ""
"Now, you can search articles which contains specific keywords as a comment."
msgstr ""
"Now, you can search articles which contains specific keywords as a comment."

# 0b02ff8e45c7437d88aaf2a0c3b980b4
msgid ""
"The feature of nested index search is not limited to the relationship "
"between two table only."
msgstr ""
"The feature of nested index search is not limited to the relationship "
"between two table only."

# 68b783cd54384db99a61f08a35732927
msgid ""
"Here is the sample schema similar to previous one. The difference is added "
"table which express 'Reply' and relationship is extended to three tables."
msgstr ""
"Here is the sample schema similar to previous one. The difference is added "
"table which express 'Reply' and relationship is extended to three tables."

# c312ddafed174b168a084ab4e59a49df
msgid ""
"The first query searches 'mroonga' from Comments2 table, the second one "
"searches 'mroonga' from Replies2 and Comment2 table by using reference "
"column index."
msgstr ""
"The first query searches 'mroonga' from Comments2 table, the second one "
"searches 'mroonga' from Replies2 and Comment2 table by using reference "
"column index."

# e05bf035767944ee91fd37f88041b34c
msgid ""
"As a result, the first query matches two article because of Comments2 table "
"has two records which contains 'mroonga' as keyword."
msgstr ""
"As a result, the first query matches two article because of Comments2 table "
"has two records which contains 'mroonga' as keyword."

# 5f42c31814384c38b8638565fc4fc861
msgid ""
"On the other hand, the second one matches one article only because of "
"Replies2 table has only one record which contains 'mroonga' as keyword, and "
"there is one record which contains same keyword and refers to the record in "
"Comments2 table."
msgstr ""
"On the other hand, the second one matches one article only because of "
"Replies2 table has only one record which contains 'mroonga' as keyword, and "
"there is one record which contains same keyword and refers to the record in "
"Comments2 table."

# 9e7955ff4b5548b39d4dc4984eff9f05
msgid "Indexes with Weight"
msgstr "Indexes with Weight"

# d27c998c86f047c78e8c1dc936dc781e
msgid "Let's create micro-blog"
msgstr "Let's create micro-blog"

# 9c432700ada94944958a00e869670b90
msgid ""
"Let's create micro-blog with full text search by Groonga. Micro-blog is one "
"of the broadcast medium in the forms of blog. It is mainly used to post "
"small messages like a Twitter."
msgstr ""
"Let's create micro-blog with full text search by Groonga. Micro-blog is one "
"of the broadcast medium in the forms of blog. It is mainly used to post "
"small messages like a Twitter."

# 326ee6b8b9764ee2a5e2ea4ea29d19e1
msgid "Let's create table."
msgstr "Let's create table."

# dd78badfeb75455ea195461927c0ee0f
msgid "Users table"
msgstr "Users table"

# 3c7a690d14f04bc3aab07ff9cbdcd039
msgid ""
"This is the table which stores user information. It stores name of user, "
"profile, list of follower and so on."
msgstr ""
"This is the table which stores user information. It stores name of user, "
"profile, list of follower and so on."

# e25d3ce03a5f4186a93771765372e9f5
msgid "User ID"
msgstr "User ID"

# 9abad7b20be14cf4945634eca1fbb454
# 8a96affd94144031aff824bbe5ea3adf
# 0e452a3b21b4473a8ee386e0553172fe
# 07bcb3257169449d9b6c49a90fda6168
msgid "``_key``"
msgstr "``_key``"

# 71dff477883d4a069444cb09dfc8df70
msgid "User name"
msgstr "User name"

# 81fa90c9fb3e41a2a90869c874570cd5
msgid "``name``"
msgstr "``name``"

# daf522a3fbe8482a87cb6c42a1dcb4ed
msgid "List of following users"
msgstr "List of following users"

# 04d38b07e5eb4610bf9f69ad1245aabb
msgid "``follower``"
msgstr "``follower``"

# dca7c3433c8549288e3436f1cec7aae1
msgid "List of favorite comments"
msgstr "List of favorite comments"

# 6bcd067b09dd455e986be1ef8836328f
msgid "``favorites``"
msgstr "``favorites``"

# 85aee1b3119344ceaafb61c6d24535ea
msgid "Current location of user (geolocation)"
msgstr "Current location of user (geolocation)"

# f47154bccf494cf5ae748c7da67efd89
# e117f7dd3a7b4f9782f79c2a1106048c
msgid "``location``"
msgstr "``location``"

# c7a6f47197e14a1a86c7e734971cb1e8
msgid "Current location of user (string)"
msgstr "Current location of user (string)"

# e87be98c65154437ad8ba565e0401e8a
msgid "``location_str``"
msgstr "``location_str``"

# e4281333f74841c59070da5293d8fd2c
msgid "User profile"
msgstr "User profile"

# 4e8caf528e59497ba2b7c4becad32992
msgid "``description``"
msgstr "``description``"

# ca33a903e0db49bf8ef2182c76020e85
msgid ""
"Indexes for ``follower`` column in ``Users`` table. With this indexes, you "
"can search users who follows the person."
msgstr ""
"Indexes for ``follower`` column in ``Users`` table. With this indexes, you "
"can search users who follows the person."

# 19d0eea32ef14dc887608c7ae8bb8958
msgid "``followee``"
msgstr "``followee``"

# 6823a0d86c3a4946bcd3b05e89a3d180
msgid "Comments table"
msgstr "Comments table"

# 955488101e8e4e51b962079e155a4564
msgid ""
"This is the table which stores comments and its metadata. It stores content "
"of comment, posted date, comment which reply to, and so on."
msgstr ""
"This is the table which stores comments and its metadata. It stores content "
"of comment, posted date, comment which reply to, and so on."

# bfacee3d4c4148bb929bad5fa8de5919
msgid "Comment ID"
msgstr "Comment ID"

# ecc3f07097c6462cba294235edd590ba
msgid "Content of comment"
msgstr "Content of comment"

# c1200be5df034141863517c56cd3d05e
msgid "``comment``"
msgstr "``comment``"

# e6e3f8558d974840926689b245cff873
msgid "Posted date"
msgstr "Posted date"

# c26bae67d9b04ca2b2944e7d5a8a5432
msgid "``last_modified``"
msgstr "``last_modified``"

# 6d95062d2e0f439bbad2a6f995910294
msgid "Comment which you reply to someone"
msgstr "Comment which you reply to someone"

# 3f8da584bf6b4ea991e54daeb823f557
msgid "``replied_to``"
msgstr "``replied_to``"

# 61cccba1225745ec979bb7c573b55e03
msgid "List of users who you reply to"
msgstr "List of users who you reply to"

# 4940d844112f40109edb07bcbdba173d
msgid "``replied_users``"
msgstr "``replied_users``"

# bb80055cc8eb46be88f9d23d322be189
msgid "List of hash tags about comment"
msgstr "List of hash tags about comment"

# 5562d8602dcf42a697a560d7301e6fc4
msgid "``hash_tags``"
msgstr "``hash_tags``"

# 83b8d25483564b368e8e3ff7c685db56
msgid "Posted place (for geolocation)"
msgstr "Posted place (for geolocation)"

# 6b7dc0034a4c4a6e97502e1956ff1f04
msgid "Person who write comment"
msgstr "Person who write comment"

# b600e58eac7c4212a7cf031361478759
msgid "``posted_by``"
msgstr "``posted_by``"

# 90c3a2e89499415e942b2672008a69f0
msgid ""
"Indexes for ``favorites`` column in ``Users`` table. With this indexes, you "
"can search the person who mark comment as favorite one."
msgstr ""
"Indexes for ``favorites`` column in ``Users`` table. With this indexes, you "
"can search the person who mark comment as favorite one."

# c0017bb8db744a3f8a538bafa0e702a2
msgid "``favorited_by``"
msgstr "``favorited_by``"

# ee955c84e7674fb1bd109b7cf10531c2
msgid "HashTags table"
msgstr "HashTags table"

# fd045dba252a422994b62503ec302502
msgid "This is the table which stores hash tags for comments."
msgstr "This is the table which stores hash tags for comments."

# 02cfad3ba6a24c5398181d8e93a01edc
msgid "Hash tag"
msgstr "Hash tag"

# 0ee18cce21e740e2b5b67d1c9b1f147a
msgid ""
"Indexes for ``Comments.hash_tags``. With this indexes, you can search list "
"of comments with specified hash tags."
msgstr ""
"Indexes for ``Comments.hash_tags``. With this indexes, you can search list "
"of comments with specified hash tags."

# 71368a8f65dc4998af32c18c67ce4fb8
msgid "``hash_index``"
msgstr "``hash_index``"

# 4a087b87e8574af5b1b52e1926296edf
msgid "Bigram table"
msgstr "Bigram table"

# 9751969566f445f4ac25f56e20be0c8c
msgid ""
"This is the table which stores indexes for full text search by user "
"information or comments."
msgstr ""
"This is the table which stores indexes for full text search by user "
"information or comments."

# 913c02b40d554dd2a52753879338c042
msgid "Word"
msgstr "Word"

# 9f916941816247b4837442e4a0b5bdf8
msgid ""
"Indexes of user information. This column contains indexes of user name "
"(``Users.name``), current location (``Users.location_str``), profile "
"(``Users.description``)."
msgstr ""
"Indexes of user information. This column contains indexes of user name "
"(``Users.name``), current location (``Users.location_str``), profile "
"(``Users.description``)."

# 7530a32eccd747058a514f9f7795fda4
msgid "``users_index``"
msgstr "``users_index``"

# 07866fbfa28e4d8ca17894ad18f72b9f
msgid "Indexes about content of comments (``Comments.comment``)."
msgstr "Indexes about content of comments (``Comments.comment``)."

# da73e6b33c4b4dd1a99fd56b89a12509
msgid "``comment_index``"
msgstr "``comment_index``"

# a0316c9815894b5cb67885386f94b43d
msgid "GeoIndex table"
msgstr "GeoIndex table"

# 3ab754ec5248465f94c1a0f5c578ee12
msgid ""
"This is the table which stores indexes of location column to search geo "
"location effectively."
msgstr ""
"This is the table which stores indexes of location column to search geo "
"location effectively."

# 6b1d274d655045f8a4e9ac5fa3ced007
msgid "Indexes of location column for Users table"
msgstr "Indexes of location column for Users table"

# ee28a0b8e1ce481e8ef8b46ff6b731a9
msgid "``users_location``"
msgstr "``users_location``"

# 7e9580de5f4d46519de29bc2f5ada006
msgid "Indexes of location column for Comments table"
msgstr "Indexes of location column for Comments table"

# 6a4a98d400bd47189a96273e771d25e5
msgid "``comments_location``"
msgstr "``comments_location``"

# 22479244354642438b3cbe355f529171
msgid "Loading data"
msgstr "Loading data"

# 91dbf1599fe54b3db3aab4e3c58d7e8c
msgid "Then, load example data."
msgstr "Then, load example data."

# 40a58501552445e5b7d526643905fc7f
msgid ""
"``follower`` column and ``favorites`` column in ``Users`` table and "
"``replied_users`` column in ``Comments`` table are vector column, so specify "
"the value as an array."
msgstr ""
"``follower`` column and ``favorites`` column in ``Users`` table and "
"``replied_users`` column in ``Comments`` table are vector column, so specify "
"the value as an array."

# a4be711203704a978d10231ebe007fc9
msgid ""
"``location`` column in ``Users`` table, ``location`` column in ``Comments`` "
"table use GeoPoint type. This type accepts \"[latitude]x[longitude]\"."
msgstr ""
"``location`` column in ``Users`` table, ``location`` column in ``Comments`` "
"table use GeoPoint type. This type accepts \"[latitude]x[longitude]\"."

# 2d3f1767d1cc40c49ea05925534c8e20
msgid "``last_modified`` column in ``Comments`` table use Time type."
msgstr "``last_modified`` column in ``Comments`` table use Time type."

# 2bf8b8358e5e4c69955e8d1aeca706d0
msgid ""
"There are two way to specify the value. First, specify epoch (seconds since "
"Jan, 1, 1970 AM 00:00:00) directly. In this case, you can specify micro "
"seconds as fractional part. The value is converted from factional part to "
"the time which is micro seconds based one when data is loaded. The second, "
"specify the timestamp as string in following format: \"(YEAR)/(MONTH)/(DAY) "
"(HOUR):(MINUTE):(SECOND)\". In this way, the string is casted to proper "
"micro seconds when data is loaded."
msgstr ""
"There are two way to specify the value. First, specify epoch (seconds since "
"Jan, 1, 1970 AM 00:00:00) directly. In this case, you can specify micro "
"seconds as fractional part. The value is converted from factional part to "
"the time which is micro seconds based one when data is loaded. The second, "
"specify the timestamp as string in following format: \"(YEAR)/(MONTH)/(DAY) "
"(HOUR):(MINUTE):(SECOND)\". In this way, the string is casted to proper "
"micro seconds when data is loaded."

# d71c2e7e87294ca1b4b541ca51befc57
# 1ef3dbfdda304cdcbf653f5984d7b3b9
msgid "Search"
msgstr "Search"

# 71fadca1e3cd4e40b3339bffa1691d07
msgid "Let's search micro-blog."
msgstr "Let's search micro-blog."

# a9980550a52f4f1889c0414d12d86731
msgid "Search users by keyword"
msgstr "Search users by keyword"

# f8bbfd5fab224c33aa41cd6a55c7dda8
msgid ""
"In this section, we search micro-blog against multiple column by keyword. "
"See :doc:`match_columns` to search multiple column at once."
msgstr ""
"In this section, we search micro-blog against multiple column by keyword. "
"See :doc:`match_columns` to search multiple column at once."

# 2dabff6aab69438c813b59dd4510e240
msgid ""
"Let's search user from micro-blog's user name, location, description entries."
msgstr ""
"Let's search user from micro-blog's user name, location, description entries."

# 5296568500df44e199e81eeaa0a56a57
msgid ""
"By using \"New York\" as searching keyword for user, \"Bob\" who lives in "
"\"New York\" is listed in search result."
msgstr ""
"By using \"New York\" as searching keyword for user, \"Bob\" who lives in "
"\"New York\" is listed in search result."

# 118a492287e44b969a8ab65837ba05a5
msgid "Search users by geolocation data (GeoPoint)"
msgstr "Search users by geolocation data (GeoPoint)"

# 93f2440e61f44ff9b392821dde7618a7
msgid ""
"In this section, we search users by column data which use type of GeoPoint. "
"See :doc:`search` about GeoPoint column."
msgstr ""
"In this section, we search users by column data which use type of GeoPoint. "
"See :doc:`search` about GeoPoint column."

# d0fc50b76d8741e8b9f3bc03a803a616
msgid ""
"Following example searches users who live in within 20km from specified "
"location."
msgstr ""
"Following example searches users who live in within 20km from specified "
"location."

# 33807a8104324f41ae091fd519e4335a
msgid ""
"It shows that \"Bob\" and \"Charlie\" lives in within 20 km from station of "
"\"Grand Central Terminal\"."
msgstr ""
"It shows that \"Bob\" and \"Charlie\" lives in within 20 km from station of "
"\"Grand Central Terminal\"."

# 029e0cd452484694a97c98cb05b1acc4
msgid "Search users who follows specific user"
msgstr "Search users who follows specific user"

# 04efcc9286ef4d9da36163e39899bde5
msgid ""
"In this section, we do reverse resolution of reference relationships which "
"is described at :doc:`index`."
msgstr ""
"In this section, we do reverse resolution of reference relationships which "
"is described at :doc:`index`."

# c5d5db2d76d34c0bae709f2e4c79e4db
msgid ""
"Following examples shows reverse resolution about ``follower`` column of "
"``Users`` table."
msgstr ""
"Following examples shows reverse resolution about ``follower`` column of "
"``Users`` table."

# 392344caf752493b9af848395f6dd2e9
msgid "It shows that \"Alice\" and \"Charlie\" follows \"Bob\"."
msgstr "It shows that \"Alice\" and \"Charlie\" follows \"Bob\"."

# 6404e933b78145ea8a629fcc2a86eb10
msgid "Search comments by using the value of GeoPoint type"
msgstr "Search comments by using the value of GeoPoint type"

# 10c57e35c250409c8dba5f55a3c87e12
msgid ""
"In this section, we search comments which are written within specific "
"location."
msgstr ""
"In this section, we search comments which are written within specific "
"location."

# 25a07ee748084bf88bc37b9a94d0c915
msgid ""
"Then, we also use drill down which is described at :doc:`drilldown`. "
"Following example shows how to drill down against search results. As a "
"result, we get the value of count which is grouped by user, and hash tags "
"respectively."
msgstr ""
"Then, we also use drill down which is described at :doc:`drilldown`. "
"Following example shows how to drill down against search results. As a "
"result, we get the value of count which is grouped by user, and hash tags "
"respectively."

# 9032c9dd01d5476f9ecb0538a7139e7f
msgid ""
"Above query searches comments which are posted within 20 km from Central "
"Park in city of New York."
msgstr ""
"Above query searches comments which are posted within 20 km from Central "
"Park in city of New York."

# 4d6c571758ed4f65822cadfb12febd1c
msgid ""
"As specified range is 20 km, all comments with location are collected. You "
"know that search results contain 2 #groonga hash tags and one #travel hash "
"tag, and bob and charlie posted 2 comments."
msgstr ""
"As specified range is 20 km, all comments with location are collected. You "
"know that search results contain 2 #groonga hash tags and one #travel hash "
"tag, and bob and charlie posted 2 comments."

# be1c6afc3f77431eaf4af7e291d40f83
msgid "Search comments by keyword"
msgstr "Search comments by keyword"

# 021dfd6793084a3ba210ab4d889cd930
msgid ""
"In this section, we search comments which contains specific keyword. And "
"more, Let's calculate the value of `_score` which is described at :doc:"
"`search`."
msgstr ""
"In this section, we search comments which contains specific keyword. And "
"more, Let's calculate the value of `_score` which is described at :doc:"
"`search`."

# 35c5e77a00bd4e1cb199cdf087b3db72
msgid ""
"By using 'Now' as a keyword, above query returns 2 comments. It also "
"contains count of 'Now' as the value of `_score`."
msgstr ""
"By using 'Now' as a keyword, above query returns 2 comments. It also "
"contains count of 'Now' as the value of `_score`."

# 57e9a10f1b1a490091148d2d51c9441b
msgid "Search comments by keyword and geolocation"
msgstr "Search comments by keyword and geolocation"

# ff09c932f9804b5288c60f1471e1c37a
msgid ""
"In this section, we search comments by specific keyword and geolocation. By "
"using `--query` and `--filter` option, following query returns records which "
"are matched to both conditions."
msgstr ""
"In this section, we search comments by specific keyword and geolocation. By "
"using `--query` and `--filter` option, following query returns records which "
"are matched to both conditions."

# 9af91e54caae4d64b19428f7ae23331c
msgid ""
"It returns 1 comment which meets both condition. It also returns result of "
"drilldown. There is 1 comment which is commented by Bob."
msgstr ""
"It returns 1 comment which meets both condition. It also returns result of "
"drilldown. There is 1 comment which is commented by Bob."

# 14f9c57a568c4fdca17884b81d7c78ef
msgid "Search comments by hash tags"
msgstr "Search comments by hash tags"

# 1db077a1097340a2bbce2690184f93d2
msgid ""
"In this section, we search comments which contains specific hash tags. Let's "
"use reverse resolution of reference relationships."
msgstr ""
"In this section, we search comments which contains specific hash tags. Let's "
"use reverse resolution of reference relationships."

# 2a72be343abb47cba249b54aa19640d1
msgid ""
"Above query returns 2 comments which contains #groonga hash tag. It also "
"returns result of drilldown grouped by person who posted it. It shows that "
"there are 2 comments. Bob commented it."
msgstr ""
"Above query returns 2 comments which contains #groonga hash tag. It also "
"returns result of drilldown grouped by person who posted it. It shows that "
"there are 2 comments. Bob commented it."

# 9cdb69a20a63471da55861e361e3f14a
msgid "Search comments by user id"
msgstr "Search comments by user id"

# f5b6c3c40b3f4aefb6cde4cbb69e31e7
msgid "In this section, we search comments which are posted by specific user."
msgstr "In this section, we search comments which are posted by specific user."

# 3a3c760137ce4549b294ca8a59b24d50
msgid ""
"Above query returns 4 comments which are posted by Bob. It also returns "
"result of drilldown by hash tags. There are 2 comments which contains "
"#groonga, and 1 comment which contains #travel as hash tag."
msgstr ""
"Above query returns 4 comments which are posted by Bob. It also returns "
"result of drilldown by hash tags. There are 2 comments which contains "
"#groonga, and 1 comment which contains #travel as hash tag."

# 14d7c72cffb74fd195b7bc3e66283c6b
msgid "Search user's favorite comments"
msgstr "Search user's favorite comments"

# afd30c913d804a56ad5bcb4e717229ad
msgid "In this section, we search user's favorite comments."
msgstr "In this section, we search user's favorite comments."

# 873b2cbf1f644da9a01399f5960aa30e
msgid "Above query returns Bob's favorite comments."
msgstr "Above query returns Bob's favorite comments."

# 7536d78f1e2f4348bef940ddeaf6734a
msgid "Search comments by posted time"
msgstr "Search comments by posted time"

# ca0cb4007b2a4978bbe1fad4366438db
msgid ""
"In this section, we search comments by posted time. See type of `Time` in :"
"doc:`data`."
msgstr ""
"In this section, we search comments by posted time. See type of `Time` in :"
"doc:`data`."

# e1f35a1c517e4d22afbde1503b028e02
msgid "Let's search comments that posted time are older than specified time."
msgstr "Let's search comments that posted time are older than specified time."

# 621e5467602542eea4008deb371aba69
msgid ""
"Above query returns 5 comments which are older than 2010/03/17 14:00:00. It "
"also returns result of drilldown by posted person. There are 2 comments by "
"Alice, 3 comments by Bob."
msgstr ""
"Above query returns 5 comments which are older than 2010/03/17 14:00:00. It "
"also returns result of drilldown by posted person. There are 2 comments by "
"Alice, 3 comments by Bob."

# 0a5cde38c32f45c99fcc05777396b6ed
msgid "Remote access"
msgstr "Remote access"

# 2c9d7e5bf94e4a5e99dbad176d9fd780
msgid ""
"You can use Groonga as a server which allows remote access. Groonga supports "
"the original protocol (GQTP), the memcached binary protocol and HTTP."
msgstr ""
"You can use Groonga as a server which allows remote access. Groonga supports "
"the original protocol (GQTP), the memcached binary protocol and HTTP."

# 1ef5505b08e241b7a7499d3585c32651
msgid "Hypertext transfer protocol (HTTP)"
msgstr "Hypertext transfer protocol (HTTP)"

# a927f7591d7844e8aaf0372a96188589
msgid "How to run an HTTP server"
msgstr "How to run an HTTP server"

# d3359b95caa3446db011cf8fb4b97f0f
msgid ""
"Groonga supports the hypertext transfer protocol (HTTP). The following form "
"shows how to run Groonga as an HTTP server daemon."
msgstr ""
"Groonga supports the hypertext transfer protocol (HTTP). The following form "
"shows how to run Groonga as an HTTP server daemon."

# e0ed43d594504a379e0a284cec7e2945
msgid ""
"The `--protocol` option and its argument specify the protocol of the server. "
"\"http\" specifies to use HTTP. If the `-p` option is not specified, Groonga "
"uses the default port number 10041."
msgstr ""
"The `--protocol` option and its argument specify the protocol of the server. "
"\"http\" specifies to use HTTP. If the `-p` option is not specified, Groonga "
"uses the default port number 10041."

# f499f151ffaf4c9fa64fb07485fc9e13
msgid ""
"The following command runs an HTTP server that listens on the port number 80."
msgstr ""
"The following command runs an HTTP server that listens on the port number 80."

# dc11b4638246486aaef8d2cda7761341
msgid ""
"You must have root privileges if you listen on the port number 80 (well "
"known port). There is no such a limitation about the port number 1024 or "
"over."
msgstr ""
"You must have root privileges if you listen on the port number 80 (well "
"known port). There is no such a limitation about the port number 1024 or "
"over."

# 76030707371c4c948469a36523cc3c6f
msgid "How to send a command to an HTTP server"
msgstr "How to send a command to an HTTP server"

# 5ef5cff8f035405ea961309f3e6ee937
msgid ""
"You can send a command to an HTTP server by sending a GET request to /d/"
"COMMAND_NAME. Command parameters can be passed as parameters of the GET "
"request. The format is \"?NAME_1=VALUE_1&NAME_2=VALUE_2&...\"."
msgstr ""
"You can send a command to an HTTP server by sending a GET request to /d/"
"COMMAND_NAME. Command parameters can be passed as parameters of the GET "
"request. The format is \"?NAME_1=VALUE_1&NAME_2=VALUE_2&...\"."

# c99eb3579a0b4ca681bf4ca1d743a281
msgid "The following example shows how to send commands to an HTTP server."
msgstr "The following example shows how to send commands to an HTTP server."

# a94fda1abdaa4f5f971a471f7efdb6fe
msgid "Administration tool (HTTP)"
msgstr "Administration tool (HTTP)"

# fad6d7e6c9be4094b94db96e9affb43c
msgid ""
"An HTTP server of Groonga provides a browser based administration tool that "
"makes database management easy. After starting an HTTP server, you can use "
"the administration tool by accessing http://HOST_NAME_OR_IP_ADDRESS[:"
"PORT_NUMBER]/. Note that Javascript must be enabled for the tool to work "
"properly."
msgstr ""
"An HTTP server of Groonga provides a browser based administration tool that "
"makes database management easy. After starting an HTTP server, you can use "
"the administration tool by accessing http://HOST_NAME_OR_IP_ADDRESS[:"
"PORT_NUMBER]/. Note that Javascript must be enabled for the tool to work "
"properly."

# d8a53d55dfdb475395ffba41a08ca9cf
msgid "Security issues"
msgstr "Security issues"

# 62750303d27440639d10cc9e01387374
msgid ""
"Groonga servers don't support user authentication. Everyone can view and "
"modify databases hosted by Groonga servers. You are recommended to restrict "
"IP addresses that can access Groonga servers. You can use iptables or "
"similar for this purpose."
msgstr ""
"Groonga servers don't support user authentication. Everyone can view and "
"modify databases hosted by Groonga servers. You are recommended to restrict "
"IP addresses that can access Groonga servers. You can use iptables or "
"similar for this purpose."

# 954ea60359f547b090393c32cda9ec70
msgid "Prefix search with patricia trie"
msgstr "Prefix search with patricia trie"

# 9b5a45b823474dc78aab12400a519925
msgid ""
"Groonga supports to create a table with patricia trie option. By specifying "
"it, You can do prefix search."
msgstr ""
"Groonga supports to create a table with patricia trie option. By specifying "
"it, You can do prefix search."

# 925875a054e240478558b170569ef5f7
msgid ""
"And more, you can do suffix search against primary key by specifying "
"additional option."
msgstr ""
"And more, you can do suffix search against primary key by specifying "
"additional option."

# cb6b6faed5f34d74946a15279dc28f72
msgid "Prefix search by primary key"
msgstr "Prefix search by primary key"

# a016607ddecb483f862e1ed5f43d9464
msgid ""
"table_create command which uses TABLE_PAT_KEY for flags option supports "
"prefix search by primary key."
msgstr ""
"table_create command which uses TABLE_PAT_KEY for flags option supports "
"prefix search by primary key."

# 1ec777e70c954833950430eb022992df
msgid "Suffix search by primary key"
msgstr "Suffix search by primary key"

# 30cd33c04f2e4ccdac790942767caf90
msgid ""
"table_create command which uses TABLE_PAT_KEY and KEY_WITH_SIS for flags "
"option supports prefix search and suffix search by primary key."
msgstr ""
"table_create command which uses TABLE_PAT_KEY and KEY_WITH_SIS for flags "
"option supports prefix search and suffix search by primary key."

# 6a87584093f649a68c742d02b9b02d1a
msgid ""
"If you set KEY_WITH_SIS flag, suffix search records also are added when you "
"add the data. So if you search simply, the automatically added records are "
"hit in addition to the original records. In order to search only the "
"original records, you need a plan."
msgstr ""
"If you set KEY_WITH_SIS flag, suffix search records also are added when you "
"add the data. So if you search simply, the automatically added records are "
"hit in addition to the original records. In order to search only the "
"original records, you need a plan."

# 56b1b263cae64758a958757d9043771f
msgid ""
"For example, in order to make this distinction between the original records "
"and automatically added records, add the original column indicating that it "
"is the original record, and add original column is ``true`` to the search "
"condition. For attention, use ``--filter`` option because ``--query`` option "
"is not specify ``Bool`` type value intuitively."
msgstr ""
"For example, in order to make this distinction between the original records "
"and automatically added records, add the original column indicating that it "
"is the original record, and add original column is ``true`` to the search "
"condition. For attention, use ``--filter`` option because ``--query`` option "
"is not specify ``Bool`` type value intuitively."

# b1d5654a765b4cd58cb0f38bef72b58a
msgid "Query expansion"
msgstr "Query expansion"

# 26c391639152425aab59a76eb0f9633f
msgid ""
"Groonga accepts ``query_expander`` parameter for :doc:`/reference/commands/"
"select` command. It enables you to extend your query string."
msgstr ""
"Groonga accepts ``query_expander`` parameter for :doc:`/reference/commands/"
"select` command. It enables you to extend your query string."

# 5b2baeb5404046f38380aa221f1efb51
msgid ""
"For example, if user searches \"theatre\" instead of \"theater\", query "
"expansion enables to return search results of \"theatre OR theater\". This "
"kind of way reduces search leakages. This is what really user wants."
msgstr ""
"For example, if user searches \"theatre\" instead of \"theater\", query "
"expansion enables to return search results of \"theatre OR theater\". This "
"kind of way reduces search leakages. This is what really user wants."

# 7dba7218bdc3447c835df889b7446b9e
msgid "Preparation"
msgstr "Preparation"

# 790ae5aacdae4f5d855063a2311f05fd
msgid ""
"To use query expansion, you need to create table which stores documents, "
"synonym table which stores query string and replacement string. In synonym "
"table, primary key represents original string, the column of ShortText "
"represents modified string."
msgstr ""
"To use query expansion, you need to create table which stores documents, "
"synonym table which stores query string and replacement string. In synonym "
"table, primary key represents original string, the column of ShortText "
"represents modified string."

# 8ea1161752df493897333e5be97ad687
msgid "Let's create document table and synonym table."
msgstr "Let's create document table and synonym table."

# 5a71ec7136b44665a57f75c45eaa33da
msgid ""
"In this case, it doesn't occur search leakage because it creates synonym "
"table which accepts \"theatre\" and \"theater\" as query string."
msgstr ""
"In this case, it doesn't occur search leakage because it creates synonym "
"table which accepts \"theatre\" and \"theater\" as query string."

# 37bee1c4e62543ffa4724a6a3025b941
msgid ""
"Then, let's use prepared synonym table. First, use select command without "
"``query_expander`` parameter."
msgstr ""
"Then, let's use prepared synonym table. First, use select command without "
"``query_expander`` parameter."

# 388ef22b13b140c8a78bc9fa892684bd
msgid "Above query returns the record which completely equal to query string."
msgstr "Above query returns the record which completely equal to query string."

# 002779531f3d4e18b798c21cb5003a77
msgid ""
"Then, use ``query_expander`` parameter against ``body`` column of "
"``Synonym`` table."
msgstr ""
"Then, use ``query_expander`` parameter against ``body`` column of "
"``Synonym`` table."

# 08495912a5b847b1a106d8b1059808c9
msgid ""
"In which cases, query string is replaced to \"(theater OR theatre)\", thus "
"synonym is considered for full text search."
msgstr ""
"In which cases, query string is replaced to \"(theater OR theatre)\", thus "
"synonym is considered for full text search."

# eba9b0597ca8407f88cc488837f69444
msgid "Various search conditions"
msgstr "Various search conditions"

# 0ec37424659f4359a2339c952a226637
msgid ""
"Groonga supports to narrow down by using syntax like JavaScript, sort by the "
"calculated value. Additionally, Groonga also supports to narrow down & sort "
"search results by using location information (latitude & longitude)."
msgstr ""
"Groonga supports to narrow down by using syntax like JavaScript, sort by the "
"calculated value. Additionally, Groonga also supports to narrow down & sort "
"search results by using location information (latitude & longitude)."

# ad567462c01d405db977c3e440e0e8c9
msgid "Narrow down & Full-text search by using syntax like JavaScript"
msgstr "Narrow down & Full-text search by using syntax like JavaScript"

# 8a2e1103e7e049b0b3ea08461ba31ae4
msgid ""
"The ``filter`` parameter of ``select`` command accepts the search condition. "
"There is one difference between ``filter`` parameter and ``query`` "
"parameter, you need to specify the condition by syntax like JavaScript for "
"``filter`` parameter."
msgstr ""
"The ``filter`` parameter of ``select`` command accepts the search condition. "
"There is one difference between ``filter`` parameter and ``query`` "
"parameter, you need to specify the condition by syntax like JavaScript for "
"``filter`` parameter."

# a6797e5fee8843a7bf692711e6fa6523
msgid ""
"See the detail of above query. Here is the condition which is specified as "
"``filter`` parameter::"
msgstr ""
"See the detail of above query. Here is the condition which is specified as "
"``filter`` parameter::"

# c582c6de5358470abafda27924048ce0
msgid ""
"In this case, this query returns the records which meets the condition that "
"the value of ``_id`` is equal to 1."
msgstr ""
"In this case, this query returns the records which meets the condition that "
"the value of ``_id`` is equal to 1."

# 2d578e1fcae4452e8f5728ad88b3cc4c
msgid "Moreover, you can use ``&&`` for AND search, ``||`` for OR search."
msgstr "Moreover, you can use ``&&`` for AND search, ``||`` for OR search."

# 1abb5d614df04546bb243114a1a5135a
msgid ""
"If you specify ``query`` parameter and ``filter`` parameter at the same "
"time, you can get the records which meets both of the condition as a result."
msgstr ""
"If you specify ``query`` parameter and ``filter`` parameter at the same "
"time, you can get the records which meets both of the condition as a result."

# 34334a33bb1f4c3395e0dc4c88dd188b
msgid "Sort by using ``scorer``"
msgstr "Sort by using ``scorer``"

# dbca33d8d10449a3b7409384e8fdbc2e
msgid ""
"``select`` command accepts ``scorer`` parameter which is used to process "
"each record of full-text search results."
msgstr ""
"``select`` command accepts ``scorer`` parameter which is used to process "
"each record of full-text search results."

# 9aec135727734ca586cebe9e80496ebb
msgid ""
"This parameter accepts the conditions which is specified by syntax like "
"JavaScript as same as ``filter`` parameter."
msgstr ""
"This parameter accepts the conditions which is specified by syntax like "
"JavaScript as same as ``filter`` parameter."

# ba5d2476ba704016a105e8333f25366d
msgid ""
"'_score' is one of a pseudo column. The score of full-text search is "
"assigned to it. See :doc:`/reference/columns/pseudo` about '_score' column."
msgstr ""
"'_score' is one of a pseudo column. The score of full-text search is "
"assigned to it. See :doc:`/reference/columns/pseudo` about '_score' column."

# 67bba30be09f42d79b44dbbeb04468fd
msgid "In the above query, the condition of ``scorer`` parameter is::"
msgstr "In the above query, the condition of ``scorer`` parameter is::"

# 0b75f4bb75ec443c999ab10e7cf221e0
msgid ""
"In this case, the score of full-text search is overwritten by the value of "
"rand() function."
msgstr ""
"In this case, the score of full-text search is overwritten by the value of "
"rand() function."

# 2e792abac9484d8ca436cace28002528
msgid "The condition of ``sortby`` parameter is::"
msgstr "The condition of ``sortby`` parameter is::"

# c89d8f46160c478c9f9a5b78b6857eca
msgid "This means that sorting the search result by ascending order."
msgstr "This means that sorting the search result by ascending order."

# c44651e2181241debb01c16d9990b396
msgid "As a result, the order of search result is randomized."
msgstr "As a result, the order of search result is randomized."

# dd6ba467a3144198ae96628c9dfb42e4
msgid "Narrow down & sort by using location information"
msgstr "Narrow down & sort by using location information"

# c7598bca15ce42ea904338c2950b4f16
msgid ""
"Groonga supports to store location information (Longitude & Latitude) and "
"not only narrow down but also sort by using it."
msgstr ""
"Groonga supports to store location information (Longitude & Latitude) and "
"not only narrow down but also sort by using it."

# 532cab006b054ea0a16561eb80f6e896
msgid ""
"Groonga supports two kind of column types to store location information. One "
"is ``TokyoGeoPoint``, the other is ``WGS84GeoPoint``. ``TokyoGeoPoint`` is "
"used for Japan geodetic system. ``WGS84GeoPoint`` is used for world geodetic "
"system."
msgstr ""
"Groonga supports two kind of column types to store location information. One "
"is ``TokyoGeoPoint``, the other is ``WGS84GeoPoint``. ``TokyoGeoPoint`` is "
"used for Japan geodetic system. ``WGS84GeoPoint`` is used for world geodetic "
"system."

# 6d6c6a4a4af7459685152ed29a26cc1b
msgid "Specify longitude and latitude as follows:"
msgstr "Specify longitude and latitude as follows:"

# 7100e40613764f51a6d9478a400f3c38
msgid ""
"\"[latitude in milliseconds]x[longitude in milliseconds]\"（e.g.: "
"\"128452975x503157902\"）"
msgstr ""
"\"[latitude in milliseconds]x[longitude in milliseconds]\"（e.g.: "
"\"128452975x503157902\"）"

# c1e633d9aff747e7bc19cea387e87d7f
msgid ""
"\"[latitude in milliseconds],[longitude in milliseconds]\"（e.g.: "
"\"128452975,503157902\"）"
msgstr ""
"\"[latitude in milliseconds],[longitude in milliseconds]\"（e.g.: "
"\"128452975,503157902\"）"

# 436b8a49601d47f9be51c29ee2a44a25
msgid ""
"\"[latitude in degrees]x[longitude in degrees]\"（e.g.: "
"\"35.6813819x139.7660839\"）"
msgstr ""
"\"[latitude in degrees]x[longitude in degrees]\"（e.g.: "
"\"35.6813819x139.7660839\"）"

# f33c545143d646f999ac86f7a684d966
msgid ""
"\"[latitude in degrees],[longitude in degrees]\"（e.g.: "
"\"35.6813819,139.7660839\"）"
msgstr ""
"\"[latitude in degrees],[longitude in degrees]\"（e.g.: "
"\"35.6813819,139.7660839\"）"

# 867c25a5d6084cc3b6ee63453d2632d3
msgid ""
"Let's store two location information about station in Japan by WGS. One is "
"Tokyo station, the other is Shinjyuku station. Both of them are station in "
"Japan. The latitude of Tokyo station is 35 degrees 40 minutes 52.975 "
"seconds, the longitude of Tokyo station is 139 degrees 45 minutes 57.902 "
"seconds. The latitude of Shinjyuku station is  35 degrees 41 minutes  27.316 "
"seconds, the longitude of Shinjyuku station is 139 degrees 42 minutes 0.929 "
"seconds. Thus, location information in milliseconds are "
"\"128452975x503157902\" and \"128487316x502920929\" respectively. location "
"information in degrees are  \"35.6813819x139.7660839\" and "
"\"35.6909211x139.7002581\" respectively."
msgstr ""
"Let's store two location information about station in Japan by WGS. One is "
"Tokyo station, the other is Shinjyuku station. Both of them are station in "
"Japan. The latitude of Tokyo station is 35 degrees 40 minutes 52.975 "
"seconds, the longitude of Tokyo station is 139 degrees 45 minutes 57.902 "
"seconds. The latitude of Shinjyuku station is  35 degrees 41 minutes  27.316 "
"seconds, the longitude of Shinjyuku station is 139 degrees 42 minutes 0.929 "
"seconds. Thus, location information in milliseconds are "
"\"128452975x503157902\" and \"128487316x502920929\" respectively. location "
"information in degrees are  \"35.6813819x139.7660839\" and "
"\"35.6909211x139.7002581\" respectively."

# 4e5bcde539b64cf7a939d56d1846132f
msgid "Let's register location information in milliseconds."
msgstr "Let's register location information in milliseconds."

# cea12b63e1014f1c9a3cff5c7bd00238
msgid ""
"Then assign the value of geo distance which is calculated by :doc:`/"
"reference/functions/geo_distance` function to ``scorer`` parameter."
msgstr ""
"Then assign the value of geo distance which is calculated by :doc:`/"
"reference/functions/geo_distance` function to ``scorer`` parameter."

# a41f9c4fad8d430b880336731f4e276a
msgid ""
"Let's show geo distance from Akihabara station in Japan. In world geodetic "
"system, the latitude of Akihabara station is  35 degrees 41 minutes 55.259 "
"seconds, the longitude of Akihabara station is 139 degrees 46 minutes 27.188 "
"seconds. Specify \"128515259x503187188\" for geo_distance function."
msgstr ""
"Let's show geo distance from Akihabara station in Japan. In world geodetic "
"system, the latitude of Akihabara station is  35 degrees 41 minutes 55.259 "
"seconds, the longitude of Akihabara station is 139 degrees 46 minutes 27.188 "
"seconds. Specify \"128515259x503187188\" for geo_distance function."

# 12d247d364ac42ba9b8283b5f0b84509
msgid ""
"As you can see, the geo distance between Tokyo station and Akihabara station "
"is 2054 meters, the geo distance between Akihabara station and Shinjyuku "
"station is 6720 meters."
msgstr ""
"As you can see, the geo distance between Tokyo station and Akihabara station "
"is 2054 meters, the geo distance between Akihabara station and Shinjyuku "
"station is 6720 meters."

# 807bcdb347d74045997b7e7282919337
msgid ""
"The return value of geo_distance function is also used for sorting by "
"specifying pseudo ``_score`` column to ``sortby`` parameter."
msgstr ""
"The return value of geo_distance function is also used for sorting by "
"specifying pseudo ``_score`` column to ``sortby`` parameter."

# 3abca13171404e808a6f976f9e832cd7
msgid ""
"Groonga also supports to narrow down by \"a certain point within specified "
"meters\"."
msgstr ""
"Groonga also supports to narrow down by \"a certain point within specified "
"meters\"."

# b43b62e0ab5c42e985739092d32e568a
msgid ""
"In such a case, use :doc:`/reference/functions/geo_in_circle` function in "
"``filter`` parameter."
msgstr ""
"In such a case, use :doc:`/reference/functions/geo_in_circle` function in "
"``filter`` parameter."

# 517ac80dc8894fbbb4c54320c24355d4
msgid ""
"For example, search the records which exists within 5000 meters from "
"Akihabara station."
msgstr ""
"For example, search the records which exists within 5000 meters from "
"Akihabara station."

# 22f866ea69d7441aac1e1a8e5b2e976f
msgid ""
"There is :doc:`/reference/functions/geo_in_rectangle` function which is used "
"to search a certain point within specified region."
msgstr ""
"There is :doc:`/reference/functions/geo_in_rectangle` function which is used "
"to search a certain point within specified region."
