# -*- 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.1\n"
"Report-Msgid-Bugs-To: \n"
"PO-Revision-Date: 2015-03-27 09:53+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"

# f48a3733c1a54829940f98806156e348
# 9ac3d63430224a8f83a860c0376f75ec
# 4ea279c9b79940e693d26ee3141ec13b
# b2860d4e4ffb470c9a3c38921f5f3a00
# c2eafeada7924c61a6c888ef3cf6b0ce
# 2e1996da314a40ac816c117a26103807
# a4b919138ce546998f11558436644ca0
# 7f1324441e88461191db1d97b777d22e
# 80877d5c52ed4e29a07b9e50a0bcaa8f
# e9088bd127a1459cb0343673aad58159
# 9691d24b9b924b0a8d191cdd7c03e126
# f667d286eea0410f868e93f4c3fff778
# a7c57f8faed74dc7a8feb4dc56891a3c
# 6ecf11505bcf4cdc883ab1ad30f9ecf4
# 2a89bb05e8904a179807abdf312bfe12
# f3e117dc1b274f4cb61cd4f59363171f
# b5d581b3da5244098a7d950ef1e3c957
# 513512b89e054e0fbe5845e038d0d147
# eb06ace3471d4d318bced66a538e90ae
# 7d364c837ed2488e847a8feb318aee9d
# 95ca9e0f9e9248e18832f19d8b9d83a2
# e4cb4de909e64c57aa43c23ae721174d
# 70bdc46ae66d410da937d2173ee15f16
# 4677d48b5dc4445d8a5f38553844a35e
# 3e7de23214cd4bafa33b5b0e1fe23f3c
# 09ea9ba2386340d5a25804268e595044
# a4d726f9b1b6421785dbf9586c13b57f
# f23846168be74ae68e00086e81a6706d
# 834c768c6d1640b486ab34dee586380f
# c010769a04b747858e6e7202718aa3fd
# 8ea5cbb72920411b960797f62d8679e5
# 6a4c615d16d54dbb9f13452623a45d55
# 9ffb71440e77490fbf6e8d0a40d7e1dd
# 55b5bcac81cb4305829d855fc449f65f
# 1ca0f9ca0ccd441695708bb98c226280
# 988b7fcd309a4425a2d4f083e81f8822
# 8484bae5172e4a43a7f6047ee80dd7a1
# 56528bfd65924baa845702c7ee95defd
# 64b04c005bc44e50822d6600ccd49fd8
# 980e75604b38475db1d1897b43bcc059
# 5fcc07e908354b9abf85ca11724f63ce
# d3bb8b3fd833415ea5a44d5b24547c08
# 3fd937d8cf4348f98151c87e1d72f624
# 328e30b926be4b7f825f52530bc98402
# 05ff39b746484f8d8da4959922e3498f
# 5931d7d6d91f4110ada2e94b155c792e
# 906737b2249d4c7184f57b07b64fc3ef
# cad2b5ccdf9645829de0cbb3c756ab4d
# b28470f6108b47598dc19c0b7af99f15
# 4afc5a0f5cbb4d3ebeac7e948912dd04
# 1da6adff58fc4a9282b3c1c439d1c12b
# dd743b6254014cc19a5a562c7af6d956
# b96906a3116645ec905280d60719bbf1
# 2541556590a2439e843714334f4c53be
# e2238a41fc2f44c29e3ad905e0849599
# 337fee0502f24f6fab83111208aacdc6
# 2cfb2697cebc418995d0185a84768571
# 72e14da927b541c6b98cf0d7a15d8385
# 6290752fdcb9445aa175438c990744ea
# 5f795bbd1ebe420d86169614369dcf1f
# 3611a192b60d4e3e89b63712972d7f3a
# 1376c4cf294842a092845d5b3c39f002
# cca599831f504a298896720d1fffb151
# 62a3b14772d04220a2ba5ead140df5df
# a779c944b08543d0a54a0200872a3140
# b7f9f60396be48dda35226da7895d327
# 79c9fe119ed4479885245786187f9acf
# 28f664fa2b4f48018d120045df823ebb
# 23772f4372a9498e985e9f7b5453cb1b
# 495ecb13e1104a51a7132fbd05bb74e2
# 174d614859e642179fd49487491c6874
# 7c85fb6cb6794a71b93ea04d5c71f61c
# 6d312743cd9049b6b9194f99a5e7b783
# f6bf805355bc4067a5779a5a15c9dd32
msgid "Execution example::"
msgstr "Execution example::"

# 1a1b9122894242d58d8acf9c234f620e
msgid "Tutorial"
msgstr "Tutorial"

# f7f3330fec8f4743bb47340513b1e938
msgid "Various data types"
msgstr "Various data types"

# daa5963c0c7f4c62af0d5193e51b7bef
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."

# 698c52c818434ee78c657d77c4110a39
msgid "Overview"
msgstr "Overview"

# eb74273495d04e9f92e07d16d01ef042
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`."

# a781f056d4164497811a18e6657047bf
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."

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

# 8ca1d8ac80c44ba283e9203e25c0c7b9
msgid "Boolean type"
msgstr "Boolean type"

# bb712dc5f285429ab376a446c19759a2
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."

# 1b7b2f8e27fb4431affa2818bff0cf3b
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."

# c21d4c6eab6c4ff6977d50a2c04e61d9
msgid "Numeric types"
msgstr "Numeric types"

# 88f420c78ca14f99ae3f0307d78130a8
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."

# ab343f66cb964740a0bde91be451d255
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."

# f557cebac4114b9497e5d6ffa91a8bcd
msgid "String types"
msgstr "String types"

# 059daf3a27114b998fb86d5b5ca3cc54
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."

# 176fa874e02a4cdeaf3ba1ff5df48c22
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."

# cb38a9772d274f9fb21c79205d51f73f
msgid "Date and time type"
msgstr "Date and time type"

# 0ba2cdd77dbb4676a1d8904a2e83e3c9
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."

# c5d9768bdffd448a83da45f7bc718855
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."

# dae98c2aa8f2481c9f188753c3e091df
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."

# da32ef40e159464d96b5680e347d9abe
msgid "Longitude and latitude types"
msgstr "Longitude and latitude types"

# c48b7dd9f3584c798e54770c34db6797
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:"

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

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

# a97d9a1451fe47688277981e1d0f2193
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\"."

# c9cea0d688b4498e97969fc1c74786cb
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."

# ca38ebb4f0bd49798e91af8c676a1d38
msgid "Reference types"
msgstr "Reference types"

# 2b52cd646ec247aea0dbeedab969c2a1
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."

# bcf423c254884f578fbb5b247ddb3148
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."

# 48d857c6e6e04afc9c2b48144d6c45e1
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."

# 9b9d54579e49444ab0ef86a9e5bbc50a
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."

# 071b7e68e66d4e8eb257091e529a71dd
msgid "Vector types"
msgstr "Vector types"

# 3e19cf05f52b407eb136235afc8583a2
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."

# be6bc103a7384756873aef46d49ac5a8
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."

# 91686aca1f614d21b7ca8c1f34e263e4
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."

# 2e46fd19d0b14bea904d7019d0e251a2
msgid "Drilldown by ``domain`` column"
msgstr "Drilldown by ``domain`` column"

# 913813755b964e9e9a10d22991f90cfe
msgid "Drilldown"
msgstr "Drilldown"

# b258f16f164546c1ab2d37dbbd757529
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?"

# dbc840ed26b044cb8ccc781dc91360c8
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."

# 9125841d6e2a4e139044d62b6757bbd9
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?\"."

# 53054f01f73b45369c1afd77a43c1032
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``."

# 8d7ac2f33568499b9a4ca2f33abe04e7
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."

# f75ea9a793a54b5c9ddb6c0ece57c20f
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."

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

# cc78de3842d943fc9af95d41e8661442
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."

# 5b3dc89ffba8448a9df575273c61d43c
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\"."

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

# 89974419cc644e2f835e86347b7b1528
msgid "Group by"
msgstr "Group by"

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

# 1eff194ebd0e4b73be9385958b3111df
msgid "Group records means following records"
msgstr "Group records means following records"

# 8c77b3ea5bbe4a5fafd2a706ae10f438
msgid ".org"
msgstr ".org"

# 8155c2c9dd14455f9489754c7e41ae6a
# 1e896cd49dbf408a8aa9b5d93fd34cfb
# f1ddc6dd35fa4da2a5fca7bb0a73768a
msgid "3"
msgstr "3"

# 7328c682321d4f1bb27073faccfae973
msgid "http://example.org/"
msgstr "http://example.org/"

# fede1ff131594ff0ac72c4a29394e14f
msgid "http://example.org/aba"
msgstr "http://example.org/aba"

# ae1324848d93418e84a664816b6a1d5b
msgid "http://example.org/gat"
msgstr "http://example.org/gat"

# 686ffe4bac2249e9940d029cca863bf6
msgid ".net"
msgstr ".net"

# 917c104972ae4802a45b1f89a89d8ae5
msgid "http://example.net/"
msgstr "http://example.net/"

# a64a601e594241f68871f887cafc087f
msgid "http://example.net/afr"
msgstr "http://example.net/afr"

# bcbddffbe9c74982976bc85f16f92339
msgid "http://example.net/atv"
msgstr "http://example.net/atv"

# 02b221a8363d41d3b556591111b4aa5a
msgid ".com"
msgstr ".com"

# 734c978288f9435296fdf98841f7ed73
msgid "http://example.com/"
msgstr "http://example.com/"

# 791e1ff4169a479ebed001f9d7e9f07c
msgid "http://example.com/rab"
msgstr "http://example.com/rab"

# e1cb69a0e6694bd385624be4fdb8510f
msgid "http://example.com/vdw"
msgstr "http://example.com/vdw"

# 94169f43be8c432f8c7c3608d92927d6
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."

# cbbfd19c508f4872a0027d8a2a9ab877
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."

# bddbb6efab9d455bbb0deadf49d7cfab
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."

# 33f7d58af7a3467188d3beeca62eea4e
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."

# 71538c5d5cab43ce84216093d3b1c280
msgid "Drilldown with multiple column"
msgstr "Drilldown with multiple column"

# fe5ce93b64e44745bccdd0d39390bd1f
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."

# 49f1100fb81c4044ade4a73d9c22583f
msgid "Sorting drildown results"
msgstr "Sorting drildown results"

# 61639123a3674a7b85614e1c1b284435
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."

# 257908b6e29d41d8b7b8e2cc5ee2cda2
msgid "limits drildown results"
msgstr "limits drildown results"

# 076e3584fc804d24a5ec2d1665d8958d
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."

# c5d3d11d96494772b2adddc3d3ae20ef
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."

# 41c4c755d6a04739ad43d4a0dcd4b284
msgid "Tag search and reverse resolution of reference relationships"
msgstr "Tag search and reverse resolution of reference relationships"

# 0ebe97e264314747a92086bffcb8e7f9
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."

# e292c0a1ee744bea997e3dec606b1d1d
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."

# 128fcca967c740918f7c00a9c7cf2657
msgid "Tag search"
msgstr "Tag search"

# a2544b9459de4c95a53ec184beb88333
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."

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

# 7160bce6517b442eaa0bd24b513abfea
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."

# b623575b531342fdaa96d413381c981c
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."

# a7ad1b412b694e4487ab1bf1733aa9cd
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."

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

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

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

# 6eaba191a793464c9236de88e704aa14
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."

# 38ee509d59344ddf8d6812aa79fa1e5d
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."

# 87999533866e4d99a5138fe423cd72e9
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."

# 7febb0de4e304abf9c1cc86d9ed37cc5
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."

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

# 375afffaec304ffebda61b2fde4acc7e
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."

# bb8f44be54c54acb982fba749fdba0d0
msgid "Geo location search with index"
msgstr "Geo location search with index"

# 56aa06ed27284a98a88e90d5304ec1c6
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."

# 8c460ff8a0c4434f816c004d1ad3a9d6
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."

# 94c23e28c3db4b0d8a37012b0bc82e05
msgid "Basic operations"
msgstr "Basic operations"

# abaaedcd1d334f35b0e317cf2f19f049
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."

# 7a473f7182cd403f85af0c04461a3b64
msgid "Create a database"
msgstr "Create a database"

# 44922e247e4442df90cb2bdb1252f5ee
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."

# 146c8253a19b4ec8901983896f8635e5
# c5056f5afc094910bbf3b52e89398359
# 1e83f71e37234f5a888f12eaf0c30be4
msgid "Form::"
msgstr "Form::"

# c6f1ee6f654f449e88262e0fe2ddee0f
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."

# 9c3f4b0eb769466a928805ff557f4c0b
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."

# ede8aef7a92f4cd9a4a525c2fe3a1de4
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."

# 65fa49c99e7d440f8688b90f91e34de2
msgid "Operate a database"
msgstr "Operate a database"

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

# afbed6cb51b646b791015d8a0915ef82
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."

# b5b726403d6f4278af4074b872e7ec69
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."

# fe5cb8a8f29a4b7aa8ce06aeac1ba9c9
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."

# 20235c387be245f6884a4f1bd7ef4433
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."

# 8a733a3269074f78800756b719329a1a
msgid "Command format"
msgstr "Command format"

# 364868c2af84435e810289252b08a728
msgid "Commands for operating a database accept arguments as follows::"
msgstr "Commands for operating a database accept arguments as follows::"

# f3b2b777fabc430095a64fbf713a1767
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."

# b469d5e8629146bdadf69e1280443d11
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."

# b9cebeaee51c4c3397d4b0f451771aa2
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."

# 7408d1744fc64cb48e8c18412ec74e1a
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`."

# 6573403a209e45dba0e28457f3a72ffc
msgid "Basic commands"
msgstr "Basic commands"

# 9ea4dc63cf21461a9439c74c1a0bda7d
msgid ":doc:`/reference/commands/status`"
msgstr ":doc:`/reference/commands/status`"

# ac51aa8ea49b4b81b11c10efc1f5f517
msgid "shows status of a Groonga process."
msgstr "shows status of a Groonga process."

# 96217a705c294ebfa657d4dbb26581ea
msgid ":doc:`/reference/commands/table_list`"
msgstr ":doc:`/reference/commands/table_list`"

# 3cbb29be4e934628b93bd67263d672c2
msgid "shows a list of tables in a database."
msgstr "shows a list of tables in a database."

# fab990599e40415c871fc9b4238bb433
msgid ":doc:`/reference/commands/column_list`"
msgstr ":doc:`/reference/commands/column_list`"

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

# 8f44f1a10e25452b808022f034fc6d65
msgid ":doc:`/reference/commands/table_create`"
msgstr ":doc:`/reference/commands/table_create`"

# 36c3c2eedba54ae5b096fdd63aade77a
msgid "adds a table to a database."
msgstr "adds a table to a database."

# 178c38268fcb49308a9d46ab6afc6a88
msgid ":doc:`/reference/commands/column_create`"
msgstr ":doc:`/reference/commands/column_create`"

# e24098cbe7064bf1a54312d307476421
msgid "adds a column to a table."
msgstr "adds a column to a table."

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

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

# 17aa04d00450474ab72b480a1270883c
msgid ":doc:`/reference/commands/load`"
msgstr ":doc:`/reference/commands/load`"

# 9145ded95b6c4a7ea1b85129af911453
msgid "inserts records to a table."
msgstr "inserts records to a table."

# 1028e6d8df824645ae2d16c68b8c2fca
# b05e8ba2d79b45ca884d393750109bd0
msgid "Create a table"
msgstr "Create a table"

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

# 216a7b0c7d2642e9a06fdfd6aa4c5206
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."

# 53fe078ba7e34b19a33ba4cc47248dff
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."

# c4511802fb9b49969f2a3cb123bcc05d
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."

# 2dd323d98aec4c30825086c2ede0512f
msgid ""
"The second element of the result indicates that the operation succeeded."
msgstr ""
"The second element of the result indicates that the operation succeeded."

# 4f29af1fbdf74c309655a186da1144ba
msgid "View a table"
msgstr "View a table"

# c113a48a8ed8471e93b6627a1693f08d
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."

# 0ff84354242747d2b119311f2a3a62d4
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."

# dd1a51e77eaa4f07b64e27361cbd165f
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."

# f45c89f0a97c4c6badb6be570b7c9ab4
msgid "Create a column"
msgstr "Create a column"

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

# 711d8bfbfbc34e40a5fc4ae3ac0846b6
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."

# 82484add0f9341adad495d00d0015265
msgid "Load records"
msgstr "Load records"

# a5f59457baf74623bbea951e2b7af633
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."

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

# cc50260fed6e4780b26908e8bfa9e5a1
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."

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

# f2734a92bc4744fcb412ae7731cf9faa
msgid "Get a record"
msgstr "Get a record"

# 81bd6c644b684011af0061566c80a677
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."

# d5737774ea264c989fbb8a482671e708
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."

# cef986838ddb4f12a298fae3c59ec1b9
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."

# 1ab655d694894fa9b368485a9bbbc6e4
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/\"."

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

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

# cd4313e9b02b41acb39ae884d43e0c76
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."

# 409211571c18420796e92ac6cd47e4c0
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."

# c322cdbbdc2f4d558056400e372eb235
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."

# 653af1666a4048c4ab57768d6a310fdd
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."

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

# b540680ae2604c6faab84c68a361e577
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."

# 641895f011ab4f68b0d28d7e12e647ce
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."

# cc5e9a897f214faf9513f5bd6affa578
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."

# a02e48c51f0c4d72be70135d8a0da80c
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."

# e8e9c21f4391467b97f66fe5ad74ecf5
msgid "Full text search"
msgstr "Full text search"

# 714f49d7cacf4c88bec05daaa29bc7d2
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."

# 940f7d162426440e83e96fc3b4f6fce5
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."

# 166e5a2bb4bc4a27b23e0d827618d610
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."

# 477368d678bf4c29a82dac6b043b99d7
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. [#]_"

# 78e4273bde75422eaccc4a6ce4f9fb5e
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."

# d2071e73d85e4be480cedf1a0df3e6c2
msgid "Specify output columns"
msgstr "Specify output columns"

# 3a7bce22af30455f910a18c7d75a25f0
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 (',')."

# ad5de8f1b7fe46379638f2908284d4a5
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."

# afa076c372794c248ec35b6678b617e4
msgid "Specify output ranges"
msgstr "Specify output ranges"

# 3080c4a176ca414c99bacaeabf02d7e7
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."

# 0c83737b21cc4af8a593bc0e86e4d448
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."

# 7498f6bb35a546ee944f32e317630b89
msgid "Sort a search result"
msgstr "Sort a search result"

# 632b2718e6534bf9951429f51d5c3e0d
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."

# b7fbbf3750a84868b4f7b0aad0d3b2f5
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."

# e22c92556077412fb7b48622f50554a6
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."

# 486ceb52c48246d291c08e514a1dba6e
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."

# 83180099cba94c65b9cce452ed64c0b7
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."

# 63c125dc15b3420690f5a0c7a73259b4
msgid "footnote"
msgstr "footnote"

# 1c772cc1a2784af287d9d4357ef13ef9
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."

# 5c4dbdd8bd4548f2ad4191803917f4f3
msgid "Additional information about lexicon for full text search"
msgstr "Additional information about lexicon for full text search"

# b1ba1534a70444288b0af8c6712d2c61
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."

# 1470e75151734b40bcc18272a4436ec1
msgid "TODO: Write document."
msgstr "TODO: Write document."

# c68d25b2aa5045ec9b127fc8051f7238
msgid "match_columns parameter"
msgstr "match_columns parameter"

# 0c0bb68022a04307823002b8d64e7d0d
msgid "Full-text search against multiple columns"
msgstr "Full-text search against multiple columns"

# b5245599444c4237add3979f4b1f10aa
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?"

# e62f2a9262f048d788f373686417afb5
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."

# cd318a685cd54788b361f560a1726289
msgid "Creating column index against each column"
msgstr "Creating column index against each column"

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

# 99b7483224fd46fb8802287646f3dc47
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."

# 929e37522a3a417f96e23e9d74f2d74e
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."

# 5f839319ef504ade81e29f6f85cd9877
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."

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

# ce61520f544b4135b3cb2d9fea7175ee
msgid "Creating one column index against multiple columns"
msgstr "Creating one column index against multiple columns"

# 5d0ee21ae94d4e5eb7308d00d8c8f869
msgid "Groonga also supports one column index against multiple columns."
msgstr "Groonga also supports one column index against multiple columns."

# 71c47ac58e8843e49ac38c4470f59ad4
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."

# 68b704686a3e4e4bac73b0acb1a4a2d1
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."

# 0ad1d8d6e7f2498db2edb27b0b9a9169
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."

# c041ef785de24d6e85f3bb9be73672b7
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."

# 19926e82c279426ba60048a75ddd7f3f
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."

# 6ba59b0530984aaa85ce49a21b1cc2e9
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."

# 20548573a50540b08a1abe8b66ba1504
msgid "Full text search with specific index name"
msgstr "Full text search with specific index name"

# 240702345fc34edb9abbee294b58fba3
# 0a0a775fa59c4ea59b34904d40e2ed6a
msgid "TODO"
msgstr "TODO"

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

# 21a6fb2e992848b18f3855b6cb2236eb
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."

# c2400e8f30704f918ad3ac3957ba1445
msgid "Here is the concrete example."
msgstr "Here is the concrete example."

# 9be720c6ec4d4be0919ee94dfbfe1d5c
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."

# 89507047b5a1438a9ff8c85a974b3047
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."

# 6de090767a3c45da8438fa8844c1347c
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."

# dbab788a105148f0a80e500bb44fc1c1
msgid "Here is the sample schema."
msgstr "Here is the sample schema."

# f8063e1ac8d1437fa8c501ce209f168d
# 02807b5bac124cd197e1a721640cdfcf
msgid "Here is the sample data."
msgstr "Here is the sample data."

# 99e64df23bb541cdaa9b0bdbedfb52f1
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."

# 09b077ff718144a39d8eac7bc11c9af0
# 1241baf6230e4a5ca4c28ec6b3fefaaa
msgid "Query for searching the records described above::"
msgstr "Query for searching the records described above::"

# 455a292cde774c0384d5783786ebbdae
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."

# e327f6b33dcf4d8cb9d407a9ec95dd96
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 create column index '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 create column index 'article' of Comments table, you can't get "
"intended search results.)"

# 7a2a9df194434d0f9ba21ebe87b92f0d
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."

# 3822acf06e244e48a5307bdd789a4874
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."

# 4719d3f6189d48b8b7933473dba28b35
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."

# a4a6bc0fad264d92969a940de1891720
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."

# f4ba7498457e42a0bab295f7da2143f0
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."

# cff312d4d73e4f1a966ba655de683e29
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."

# 26ebf95329c14631ad1164447a166522
msgid "Indexes with Weight"
msgstr "Indexes with Weight"

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

# d492976e228b4fd2ac0f14ba8b7d099d
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."

# 59126620c69f490baab2217e2fc21fb4
msgid "Let's create table."
msgstr "Let's create table."

# 0ca50faebc884b55bc7b135e317b63f5
msgid "Users table"
msgstr "Users table"

# a3e07dfadd7441ec8c096fbef645b880
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."

# edeb87ce55834f8289c35fba469899d1
msgid "User ID"
msgstr "User ID"

# a59e14c3fd0747afbc90d4db1230aca0
# a1756e6dd4a7422c80002b1228195115
# 027360f3eff74135b5128631d46cd5eb
# 618d26da57274ce4ae2b540a99e98d7c
msgid "``_key``"
msgstr "``_key``"

# 436dfad4a80c47909c3ed5882ef76c13
msgid "User name"
msgstr "User name"

# 65296b3fd46c4b74a00377a5a9d38474
msgid "``name``"
msgstr "``name``"

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

# 61d702cebb8b4b0d96dec1d154ef688e
msgid "``follower``"
msgstr "``follower``"

# 8be9852b253f47f98cbf6a3fa84fce77
msgid "List of favorite comments"
msgstr "List of favorite comments"

# 7b1df77cd346454a9a039d85b2d64254
msgid "``favorites``"
msgstr "``favorites``"

# c84e0baaa3354450bb13832de250f9aa
msgid "Current location of user (geolocation)"
msgstr "Current location of user (geolocation)"

# a5c315e81eef431fbe9e2d100e213d5c
# b3b86c31929a4cae9c7d2b0d4017ab80
msgid "``location``"
msgstr "``location``"

# 31e02da7ec4c47659fa37fd4d8665177
msgid "Current location of user (string)"
msgstr "Current location of user (string)"

# e786ee7796a64f3692a49f4bd1520354
msgid "``location_str``"
msgstr "``location_str``"

# d507a8b638e34eea914a071b10352980
msgid "User profile"
msgstr "User profile"

# 83355845cc5e4a38a28532da3ad1e8d5
msgid "``description``"
msgstr "``description``"

# 7909e8e2baea422b8bcd1d01acb28829
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."

# 5d9a5e38495d47558256ef702124d4b5
msgid "``followee``"
msgstr "``followee``"

# bb54d2ba5b1842ec9a355fd620f2805e
msgid "Comments table"
msgstr "Comments table"

# 6865dd8729764b318a9a66449b434d47
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."

# ae700e1178ec435ca163ed93092bbf07
msgid "Comment ID"
msgstr "Comment ID"

# 2d006882e6d54391ae67dedba196c2cb
msgid "Content of comment"
msgstr "Content of comment"

# f749f143f9784ea3882c1461a9463aed
msgid "``comment``"
msgstr "``comment``"

# 55e4ff6bbd7a4d3c8bcf1e41b05a5dc6
msgid "Posted date"
msgstr "Posted date"

# a528b8822d2a423b849629a171fac67d
msgid "``last_modified``"
msgstr "``last_modified``"

# 466004512ebe44f885bf2bb3c0e515ae
msgid "Comment which you reply to someone"
msgstr "Comment which you reply to someone"

# a08bd4e019a5434483d0260b7d690d23
msgid "``replied_to``"
msgstr "``replied_to``"

# 35088902a9bb42bdb65a2742e10cce8e
msgid "List of users who you reply to"
msgstr "List of users who you reply to"

# a01c679683a0454abe8e7a07205112dc
msgid "``replied_users``"
msgstr "``replied_users``"

# 4226e9970a8a4379a8476d1a34d0f443
msgid "List of hash tags about comment"
msgstr "List of hash tags about comment"

# e934368f77844ed49d3926c006e9ebce
msgid "``hash_tags``"
msgstr "``hash_tags``"

# 4630bdcb7e674583843829d8d463803b
msgid "Posted place (for geolocation)"
msgstr "Posted place (for geolocation)"

# 8b16e45ac69d459e806ed445d00273ab
msgid "Person who write comment"
msgstr "Person who write comment"

# 4ce7d16406d74c1b98ddda2947a01a46
msgid "``posted_by``"
msgstr "``posted_by``"

# ecc89fa313fa4a76bdb258e315eaf839
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."

# 7f437863dc9942a390fbedbdf2f56323
msgid "``favorited_by``"
msgstr "``favorited_by``"

# efcd5336538249139c41db7a71ec3147
msgid "HashTags table"
msgstr "HashTags table"

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

# 7d4fad0c25df46e78eeb505db93044cf
msgid "Hash tag"
msgstr "Hash tag"

# 522574578dba4bbc8e7c37b2e54aecaf
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."

# 8201a44c48a94b93a11f5b60f8597b34
msgid "``hash_index``"
msgstr "``hash_index``"

# 7676fffde1d34556a8399e184700800a
msgid "Bigram table"
msgstr "Bigram table"

# 82c43fb12dd5469c8ccd731e19c31034
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."

# a45e1e8037674c88a8804e4b8694dd34
msgid "Word"
msgstr "Word"

# 1962aaba5f9246df8215df7caaf7e80b
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``)."

# e07c6b022ae544fbae6da94d035e8676
msgid "``users_index``"
msgstr "``users_index``"

# 67a9c5fbf6d24acfa30705c810921fc2
msgid "Indexes about content of comments (``Comments.comment``)."
msgstr "Indexes about content of comments (``Comments.comment``)."

# e2170dcd9c4e4a57854b017a1692dc66
msgid "``comment_index``"
msgstr "``comment_index``"

# 3295caecf6c84014b25f7831026ac511
msgid "GeoIndex table"
msgstr "GeoIndex table"

# f10af06769c74420b63fd0e66f55905c
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."

# d88ded5e8add4005b9d40ccc3faef59c
msgid "Indexes of location column for Users table"
msgstr "Indexes of location column for Users table"

# 9a70f8d0c47c46faa7cc70b3a3c4d055
msgid "``users_location``"
msgstr "``users_location``"

# cc17c58dd38d49b8b29a77e8811b8cc9
msgid "Indexes of location column for Comments table"
msgstr "Indexes of location column for Comments table"

# ea55f361444f4d668f404b635b560e42
msgid "``comments_location``"
msgstr "``comments_location``"

# a631855dc1e840efb89477913263c3bc
msgid "Loading data"
msgstr "Loading data"

# c220ce102ad3401bb8853c69a33e7d79
msgid "Then, load example data."
msgstr "Then, load example data."

# 7ba70a83ecd04532801e957b4516bfc1
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."

# b3663b7a7b2d47618de298c517e66ca7
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]\"."

# 6892d7139a4c488fbeee254df092402f
msgid "``last_modified`` column in ``Comments`` table use Time type."
msgstr "``last_modified`` column in ``Comments`` table use Time type."

# 230727a8388f4de1ad7f6c954e6a478a
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."

# 320a68cbc88f4120943319605812f726
# 1b73892e72f34e70a99394e58285d80f
msgid "Search"
msgstr "Search"

# 5e9dae4307d844b8b5946f5369b2a125
msgid "Let's search micro-blog."
msgstr "Let's search micro-blog."

# 861ec5c9b4cf443cb90ce44a529f6eb0
msgid "Search users by keyword"
msgstr "Search users by keyword"

# 696a73c7e76c4cb79cb6bc3298348606
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."

# ee51b5258ccd41e7bf71529d9c444914
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."

# d5061119b2d84b8a88bc75161764c742
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."

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

# 8cf4ec681d7c469cb775d97adb98c825
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."

# f521abc1f0544153971024fe953930c6
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."

# aeaa0466c39d4fa1a1f2f6b531ed3761
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\"."

# 713323686cbd4daf8a63eb882e4cf0c0
msgid "Search users who follows specific user"
msgstr "Search users who follows specific user"

# 0eb39696732e45a7805773d1f0fdc579
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`."

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

# 34da3a193be34a3ea5dbeb0283f800ea
msgid "It shows that \"Alice\" and \"Charlie\" follows \"Bob\"."
msgstr "It shows that \"Alice\" and \"Charlie\" follows \"Bob\"."

# 4b34d9cd1ab745dba4075b67ab1d624e
msgid "Search comments by using the value of GeoPoint type"
msgstr "Search comments by using the value of GeoPoint type"

# fcdc6bd27bd2410991a0998073c1b669
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."

# 0634fc14be25416780fc63e2dea032b1
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."

# 67905a9a16764fc78bfff9f4e161425e
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."

# 1846826c2f364bd6b79dd827da07fa2f
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."

# 171eb4dfef9a444d86f348df433dcdea
msgid "Search comments by keyword"
msgstr "Search comments by keyword"

# bd8d11bfab514e5f94e1286afc01abf2
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`."

# 17644d818a534972b6cf84aa45bff0c7
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`."

# 0bd2a292caca438d85386f9f0500876f
msgid "Search comments by keyword and geolocation"
msgstr "Search comments by keyword and geolocation"

# 7b4b37379bda4d14a8ffab147001f81e
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."

# f488433d2de749a1a72b959ebaa60e43
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."

# 3d98364ca7e84844bf0c76cdb6cf00b5
msgid "Search comments by hash tags"
msgstr "Search comments by hash tags"

# 2079cb597d8e4757a15f6b07ccc176ed
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."

# ede58e55963a46208cbc3ccfe6fdea6a
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."

# 720e0400351f47739c02f1a2f6a6d7a0
msgid "Search comments by user id"
msgstr "Search comments by user id"

# 51264beff5354cfd8068e957f88bc9a7
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."

# b3082f9337324cb2af88395b73dc9360
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."

# 5f639d00a7414fc7809d858c3bfb6ec7
msgid "Search user's favorite comments"
msgstr "Search user's favorite comments"

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

# 61c2ffeebe8f4eaabd6dc1c380945800
msgid "Above query returns Bob's favorite comments."
msgstr "Above query returns Bob's favorite comments."

# d77a5eb6f01541ee91d0f717408ac59c
msgid "Search comments by posted time"
msgstr "Search comments by posted time"

# 6d9da1e9adfa4c5e90448cd53bffc30f
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`."

# db34816b1b0340ceb891a13218f709b5
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."

# be1c92a639554a398fe7372f9a4f1f6c
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."

# 39c57d19d58e468594d59c7e23229d0d
msgid "Remote access"
msgstr "Remote access"

# d2d0759bec0e409baa0a40b9abe7483e
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."

# b2ddf3ebfda8401fa4252dbe96b36f7a
msgid "Hypertext transfer protocol (HTTP)"
msgstr "Hypertext transfer protocol (HTTP)"

# 85cdc34e0748431396bb2b8e22787a17
msgid "How to run an HTTP server"
msgstr "How to run an HTTP server"

# e6423d8ee1d14e558aed88b6eb19ff84
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."

# 3fbb4f62f9264c17b3e759b2f8bfc276
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."

# 99916fe2afc14c4780feac244a568cd9
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."

# 0651d2598bc84a93ae420ade90181c12
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."

# 57cbdbd45b6d4044a6181c97c9234309
msgid "How to send a command to an HTTP server"
msgstr "How to send a command to an HTTP server"

# 5ef3895032654e5ab84c2e4f46b281c4
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&...\"."

# c0708c7befb0410aa200086eca19f5ab
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."

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

# e79f63bc792e48c8aa8b1489f1b2fdc2
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."

# 749bdedd79614bb59804af669107ae58
msgid "Security issues"
msgstr "Security issues"

# e1af229f37fb41e89998738a38a30ba7
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."

# d967dbef047344568b519c3ff00dd8d8
msgid "Prefix search with patricia trie"
msgstr "Prefix search with patricia trie"

# 12cca1e001ab4927b0dce0e59f16e426
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."

# fa2f8636a31e439c90a2475f1e1a5600
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."

# 16c0d12a4c434c9db9b0c65333125ece
msgid "Prefix search by primary key"
msgstr "Prefix search by primary key"

# 20d306a279414808ade8a0757cc9327b
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."

# d1d2a002f80749e4a5801069faedcf2b
msgid "主キーによる後方一致検索"
msgstr "主キーによる後方一致検索"

# 013976a2916a4a41bb237b538843d59d
msgid ""
"table_createコマンドのflagsオプションにTABLE_PAT_KEYとKEY_WITH_SISを指定する"
"ことで、主キーによる前方一致検索・後方一致検索の両方が可能となります。"
msgstr ""
"table_createコマンドのflagsオプションにTABLE_PAT_KEYとKEY_WITH_SISを指定する"
"ことで、主キーによる前方一致検索・後方一致検索の両方が可能となります。"

# ddba67d7bee74811bb78e587d9ab7a28
msgid ""
"KEY_WITH_SISフラグを付与すると、データを追加する際に後方一致用のレコードも追"
"加されてしまいます。そのため、単純に検索すると、元のレコードに加えて自動的に"
"追加されたレコードまでヒットしてしまいます。元のレコードのみ検索するために、"
"一工夫必要になります。"
msgstr ""
"KEY_WITH_SISフラグを付与すると、データを追加する際に後方一致用のレコードも追"
"加されてしまいます。そのため、単純に検索すると、元のレコードに加えて自動的に"
"追加されたレコードまでヒットしてしまいます。元のレコードのみ検索するために、"
"一工夫必要になります。"

# 348967a1247345fc885168f0658cf104
msgid ""
"例えば、元のレコードと自動的に追加されたレコードとの区別をつけるために、元の"
"レコードであることを示すoriginalカラムを追加して、検索時にはoriginalカラムが "
"``true`` も検索条件に加えます。 ``--query`` オプションでは ``Bool`` 型の値を"
"直感的に指定することができないので ``--filter`` オプションを使っていることに"
"注意してください。"
msgstr ""
"例えば、元のレコードと自動的に追加されたレコードとの区別をつけるために、元の"
"レコードであることを示すoriginalカラムを追加して、検索時にはoriginalカラムが "
"``true`` も検索条件に加えます。 ``--query`` オプションでは ``Bool`` 型の値を"
"直感的に指定することができないので ``--filter`` オプションを使っていることに"
"注意してください。"

# 4c2c80dd0aa944e8a9237dd73f9c9c79
msgid "Query expansion"
msgstr "Query expansion"

# 76d519d860a140c9976d042eec0985b8
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."

# ed92e842b71f4e9b84258d8bd128c9c3
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."

# 69d1d65c10014bc6a4a321142f47a712
msgid "Preparation"
msgstr "Preparation"

# 80f2dfd210b947678afe67a4ecc79ab2
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."

# 738c9e7d72b1461798db7facd57b8fd1
msgid "Let's create document table and synonym table."
msgstr "Let's create document table and synonym table."

# 6d623d551d9048588af195fffcb4351a
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."

# 98f441eb359c4e2b878f339e871dd5db
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."

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

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

# eebdcda322164f5ab2891e612260adc3
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."

# e4828e8c49544af89814d3270bd9d6a6
msgid "Various search conditions"
msgstr "Various search conditions"

# 6326efb3b4e74b0fbc899f609bb7fd9f
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)."

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

# 4dc733d594ac4dda87fc25b9c336ea26
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."

# c25e736f305f4236a665586f1a501563
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::"

# 73a04ab1c5574b328805305c7d6c7651
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."

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

# fc76a5d45f08469ba0bf50171b5b71d5
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."

# dcff148d105e4aca91858916dc4a7cfe
msgid "Sort by using ``scorer``"
msgstr "Sort by using ``scorer``"

# bb2073ed486448d88184ebcaa78156d1
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."

# 0338e459383c4acbacbcd2fbf51784ac
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."

# bfdad319e7254980b5e216ce78beb482
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."

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

# a521a29808dc475cb04445a3a9add523
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."

# 88d59075b78447eb8e9625288204117b
msgid "The condition of ``sortby`` parameter is::"
msgstr "The condition of ``sortby`` parameter is::"

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

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

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

# 4c48b3982edb4c5599326e31d4811e03
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."

# bf5fd4f28cd3439ba0c2e1a1f3f21754
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."

# acccab95fcfc4d5195fe2ffa18ea1fd5
msgid "Specify longitude and latitude as follows:"
msgstr "Specify longitude and latitude as follows:"

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

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

# 237047373569446ba47ce698d80c2611
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\"）"

# ff23a6ef5ad74078b67593c192a7d627
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\"）"

# 6ed9a7274d3341f59bc9a1fe722ff365
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."

# 22a17532c2474ac3b7838d9b08c6cd0e
msgid "Let's register location information in milliseconds."
msgstr "Let's register location information in milliseconds."

# ac36ae5edb9c416485ec06c2afec6c29
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."

# 9029e0cdbe054fb4bf55af9e2cd86adc
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."

# fc50b59659ae48ae812e579593f72dcd
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."

# 642a375a6cf349358dbb2b4e04059775
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."

# 2a6340e1a1a344d99f7f5bdab5fe4962
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\"."

# 8367961366654e63b8f5fde9ca07556d
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."

# c87f2c0302974a90b1978a4bb167c781
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."

# d9b7163fb19346d697a4f0e1fa6b1e9c
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."
