# -*- 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-31 13:38+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"

# e1b76f8779e04b47b6cc24c2408ebb8f
# 317af2e197a848b9b32e00438b00631b
# 84f4848bf6d7400e83aabf8fe46ad1d8
# 6e4d87f8c23f4a8099eb7d4b84bd689b
# bb131331cba5488fb80510045b216fb6
# 495ae40235324c08a442d07f2f193ba7
# c687d2491df84da2af8dc54ca1ae9332
# 81e695f24c0c4ac2af5262fdfddfa434
# 289961bac4944a44aa9e0e91b2b02158
# 298d11020f4e4e6591f47fb5655a2c89
# 8bb2417fd183453896dacd54c5261f26
# 3ba8afd799124fb599793c59937cfda1
# 33491429f5d7491e8491ca59d0d8f264
# 45f713b808f446688e66918fe34364db
# f6c85e9b515d44ec90829f346051252d
# 7751f4ea37a947eab7d010b9bff833e0
# d2a3f87178b848b6abbd14fb79636cac
# ae7b67cfb6804d409f1a156d025ba170
# 3d4147eb224f40c49cec45975f49749a
# 8f80eeb503bd4acb8a75a47cb1fac16a
# d95596d801bb40cab08a81015ff0e1f4
# 24fe3102ea1142da8c607d545def12ca
# 03dfb4d24d164b04b09a6e19d7f16fa4
# 0c806a78456849279f3f280fadb71225
# 012a6aeb9a21478ab204760da3c99644
# f1113ac6649c46abba160cf6f9ae36bc
# 5a76fcc675044fefabeabae8e3cc38ec
# 91740013c4cc4143b333e7587692ccf9
# c14b933b9c524a51adf0ff3fafb957c7
# 38ef7aae43b54cebad1ee4016ac42f36
# 5c182a1f07b849c7ac7fedf5205ba088
# 3b06a7c22c0247e3b21e5e4e5e35cae3
# 0f618b07308b4ea4a2cc4e28815f2824
# c8cda156b57644469b5f79dc9266bcaa
# 12ae74abe5f14e87bfaf9dfdefbd81f3
# f9c4d50e2a464546adec3212fa40b71f
# 31c12c4e70b54ed9b60ff0c9b4b73af2
# 9c6c5cc94c1546898a9525b7aea843f1
# 1e45a56b3a4c4595af0ec443cb894101
# 3c7ef453211241c5ac52ae44e014d7ee
# f2b5abcaad0b4b82bb8c187998a0462a
# edab7b4a3bb746f5b03e0169b55071ab
# 85174e01caad4585bd3630bbb4d5c64a
# a283466caf7f45e684c7176812aec693
# 2679a01812b84587bff5e59c438b1d5f
# 933cde47b7434579814b5d14ea32bafc
# a1a5d66d17fc4a80b59c3c8b19b01c4a
# 26a129883a4e4b9083a1a8b37b278a48
# cb22c655e4ec4c81be44113735ee0aaf
# b86977b577b949f8bac70853ed01ce64
# a82bc318101f449baea5bea687fd69be
# 28655aa09a6949249a1f81abfe0548e3
# 1a061e3eb6d24551968605681cb5aa03
# 351aaeca41b64ef0a376be281fe1083f
# a20ad07fce8f4ee486ca4d05651524d3
# 7dbe8794be66480f93a9bb9e3601c2b6
# c4c1cb7efdd248399ef63c3c98549633
# 9bbd950403084d588c3504cc3ce12dd4
# 8fb36d3c39e14f85889df832f5339fb7
# 8077b49bf3fe45cab6d206fabfdf9e0d
# 63b3379744f547268dec7eb18df4c8c2
# 10fb677339194a34a3aa050448d61122
# 5b66cbbbfeab4ddbad58a107bdf09dc6
# 7c4d0a1c34cf44b5b4a5f3759ea7a0d8
# 1c39c7f7b4f94173af04e54cdc5d2e58
# 9a883119934f4ec1b42b262aa21ac4d4
# 65fa035295cd42b4b5c4d7bea5de08a8
# c44590c1083a44e2b5ed7b5cbbcae5ac
# 1a31b1fcf70f4e10bad415ddb3244093
# ba292576e7264d7d81e04345055add22
# c2532eafc76247e79985b11a937546cc
# a52fb582a5a1446cb3ec385a72c56092
# 387e6c614d3d484191869de2fceb5e7a
# aa5bbb47d17149738346be29004344d4
msgid "Execution example::"
msgstr "Execution example::"

# 43c26a5a50864235a6b0eea6d4ab170e
msgid "Tutorial"
msgstr "Tutorial"

# 881943afc86541009b85d0e5a6b46640
msgid "Various data types"
msgstr "Various data types"

# 338a0499af3f44088eb6b7a9ccd08a17
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."

# a954ef35bfc54d25b5cfc156f30ecdee
msgid "Overview"
msgstr "Overview"

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

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

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

# 556572650ee0440b853def2efbebe9f5
msgid "Boolean type"
msgstr "Boolean type"

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

# 07369c5711ca43b1b4f45226120657a7
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."

# 8ff5954c27d34338b08179e3eb7fa2cd
msgid "Numeric types"
msgstr "Numeric types"

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

# 11764489b7fe44fe8b146038fa73fef0
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."

# b6b90d2377204bf28f5ba6c4c5de19bb
msgid "String types"
msgstr "String types"

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

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

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

# 57a3df91f6524eba93ab62338a9968cc
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."

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

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

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

# 5afc44f94dba457b8024f6cb86f1c120
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:"

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

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

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

# 566e92ebdf9f427a9eca28b5ad7712a3
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."

# dbd6871348ae48ccb2664253f4e5ed1e
msgid "Reference types"
msgstr "Reference types"

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

# 230d687716254411a2f53aefe61ea429
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."

# 03b3ec08bb414725b8a65b1e858056fc
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."

# 30db6dc3d4ac404fbf100d8e61fe7842
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."

# f145bbb9438d48f78918d764ecefc995
msgid "Vector types"
msgstr "Vector types"

# 01a9c661c4104d798d06b4e824a5199a
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."

# 467808f0a6fe4299b61ed960ff202b7f
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."

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

# 026714e84a344cf89adc27f4052dd63d
msgid "Drilldown by ``domain`` column"
msgstr "Drilldown by ``domain`` column"

# 55687b9c1b76427cbc1c8ab9ccdb4110
msgid "Drilldown"
msgstr "Drilldown"

# 753afbb783c048d49463260cfef0cb2f
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?"

# 67df73d805c14a87adf071536cac0243
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."

# 3c6d3b25d90d45a2b81d99da9bd1ea08
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?\"."

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

# 02dd524296b24beb9e97681963a74190
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."

# 6618c2e2075c4324b44075bdbcfe587a
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."

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

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

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

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

# f4dc779792cf4ad5af3247b07fd1e1b5
msgid "Group by"
msgstr "Group by"

# 08594035da1c4720982820cd264db73b
msgid "The number of group records"
msgstr "The number of group records"

# 9e1b4848ee72450d9f7dbc6bbdf7a92d
msgid "Group records means following records"
msgstr "Group records means following records"

# 117d1a9589894669969abc8002bdac09
msgid ".org"
msgstr ".org"

# 46e77ffc89404947968392b7c1022200
# 64ae8aa36d0249cd8fe7f86c9f7e1113
# 72324b4678864f7cb86c0bec52ba37c5
msgid "3"
msgstr "3"

# fdc544b905e14222950009b43562f705
msgid "http://example.org/"
msgstr "http://example.org/"

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

# 78629df785604181878f51a3f6fc2960
msgid "http://example.org/gat"
msgstr "http://example.org/gat"

# 4fc73c2cfbcb47ba87bb49eb2c610be4
msgid ".net"
msgstr ".net"

# 788e991e06384d638bee9b6d20fa6468
msgid "http://example.net/"
msgstr "http://example.net/"

# 89ebdcfb3bd94022af2fbd34dba71edf
msgid "http://example.net/afr"
msgstr "http://example.net/afr"

# 3a5934847d1d422fbe4cb15c8f95016e
msgid "http://example.net/atv"
msgstr "http://example.net/atv"

# c9c5f3bd0e544162b0edd5a0961d92a7
msgid ".com"
msgstr ".com"

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

# 42a0cc59201f4fb9988e1631ee9c4ec4
msgid "http://example.com/rab"
msgstr "http://example.com/rab"

# 626a2b35afef4e16b991d11b288a3579
msgid "http://example.com/vdw"
msgstr "http://example.com/vdw"

# 420850cf9dd7405b92c7ee8a34032512
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."

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

# 42cada1f71834e899e082dd13ef78465
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."

# 58cca961726d474e830005d5396e0d1e
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."

# 3aa31ce628be4190a858aabaa26c76e3
msgid "Drilldown with multiple column"
msgstr "Drilldown with multiple column"

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

# ae30bd5232a540ea8de60ee81110af5c
msgid "Sorting drildown results"
msgstr "Sorting drildown results"

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

# 601f9249f60c4556961d397057120e64
msgid "limits drildown results"
msgstr "limits drildown results"

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

# 8059e7ad97b04fd49e0612db090fee34
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."

# 7ed929fb51d846e7aed3e54e9ce6117b
msgid "Tag search and reverse resolution of reference relationships"
msgstr "Tag search and reverse resolution of reference relationships"

# 325e76d94eee4c85834f38b3bec36816
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."

# 2060b681b3a341ac837e41e1a52bd4c0
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."

# 0a52d1a46c77421cb9e167fa12a717fe
msgid "Tag search"
msgstr "Tag search"

# 96150af374c64ed1b4a49facd52dc5cb
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."

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

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

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

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

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

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

# 01d12e6713dc485e9ea0a41c5a6d89ea
msgid "Reverse resolution of reference relationships"
msgstr "Reverse resolution of reference relationships"

# 277aeca0c91742708093e7f35b79a665
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."

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

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

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

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

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

# 6f30432500bd430baef9584ecf2910eb
msgid "Geo location search with index"
msgstr "Geo location search with index"

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

# 0694d02ce25f495496b17d8829aa204e
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."

# a939e77a4b1f4804ade78e7edb80166f
msgid "Basic operations"
msgstr "Basic operations"

# 28561ae120524dac94600bdeae07173e
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."

# c60e7b17b0414244b02fef1a323b649b
msgid "Create a database"
msgstr "Create a database"

# 32ca78414fe842beba92eb4e610c1722
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."

# c632696f637e4969b13ad506e129d6c7
# 2a349ae5896f43c78b02347e06fe6e42
# 0d60b5d32d9d497f8fe0e14ab051da5d
msgid "Form::"
msgstr "Form::"

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

# 8535312502a24bc48996e6c967a9eb24
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."

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

# 4a3bf984433b4107a767edd536d1c7a1
msgid "Operate a database"
msgstr "Operate a database"

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

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

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

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

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

# 92b227dd1b73446dbbaa63e69f827fd4
msgid "Command format"
msgstr "Command format"

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

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

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

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

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

# e95259ed8adc47b1af9ac1c1dca4f2e7
msgid "Basic commands"
msgstr "Basic commands"

# e1d0f9cf383f496d864c524c1965463a
msgid ":doc:`/reference/commands/status`"
msgstr ":doc:`/reference/commands/status`"

# 57dbdadabde64d99b355bcc32de17767
msgid "shows status of a Groonga process."
msgstr "shows status of a Groonga process."

# a563b455f1ed4a46b7df59b8e8d0bea7
msgid ":doc:`/reference/commands/table_list`"
msgstr ":doc:`/reference/commands/table_list`"

# 57d45aafd9dc4a4396af2e7ff155fc55
msgid "shows a list of tables in a database."
msgstr "shows a list of tables in a database."

# 0428737154c849e0ae6138138d9e1596
msgid ":doc:`/reference/commands/column_list`"
msgstr ":doc:`/reference/commands/column_list`"

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

# ea87ffa3b7fc4e5184fdd1173160f9e0
msgid ":doc:`/reference/commands/table_create`"
msgstr ":doc:`/reference/commands/table_create`"

# c0b8ca15fe25403dbeaab8f06b92e0df
msgid "adds a table to a database."
msgstr "adds a table to a database."

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

# 40788ca5761c486fb3e12cbba8e0d9f0
msgid "adds a column to a table."
msgstr "adds a column to a table."

# 28e50b1ff5694800bc3f0f12a4e7e7ca
msgid ":doc:`/reference/commands/select`"
msgstr ":doc:`/reference/commands/select`"

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

# 7c62610e40894a3ab25dfeb33b9244ae
msgid ":doc:`/reference/commands/load`"
msgstr ":doc:`/reference/commands/load`"

# 1a7141a9a61948bbbbe15845b48cde2f
msgid "inserts records to a table."
msgstr "inserts records to a table."

# 05d0cc4b22aa4b1e893252cd8e746b7f
# 373eed08ad3c4606840c7e54bfb305f3
msgid "Create a table"
msgstr "Create a table"

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

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

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

# 3278ca269f26402c9e72f159a93ce2b2
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."

# 916a0139d17147c38b5959dfe84f8f36
msgid ""
"The second element of the result indicates that the operation succeeded."
msgstr ""
"The second element of the result indicates that the operation succeeded."

# 5c7d42ed831e42eb88258613ec65c6b7
msgid "View a table"
msgstr "View a table"

# 911daa09c7bd4299b4725628983b0c37
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."

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

# 964d89e93416492e8bdfde3994001869
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."

# b3f6b199fbac49ab939cf140b2b1ac12
msgid "Create a column"
msgstr "Create a column"

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

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

# dfe814bc164b4e7f9570acdcafcde2a6
msgid "Load records"
msgstr "Load records"

# 44f42f68f2ce4711a7e231d0392fc71c
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."

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

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

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

# 97166e4e3deb44b6b31861ffc036e626
msgid "Get a record"
msgstr "Get a record"

# 60c5c89ad33c4016aab0acdf70f7a308
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."

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

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

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

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

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

# 962cb28340df4a6da262083404ebbdcb
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."

# 91be1a0c478348e6960e299b07dd3405
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."

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

# 563321d835f34a7ab7cf6732a2c143f1
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."

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

# 078b870ea8244525a675a7b6565e7baa
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."

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

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

# 4242737f1dd34ebcac1968ef312833f6
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."

# 8e478605ae81447ca281f28a00abd2b3
msgid "Full text search"
msgstr "Full text search"

# 3139786e5d174d34b59fe364ddac59a4
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."

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

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

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

# 13e40b3f02424b819226029077e168f2
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."

# 5cf881f28af1456ea512f50073656c92
msgid "Specify output columns"
msgstr "Specify output columns"

# 59e12bcaca574394976fd9ab675cdc55
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 (',')."

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

# 9205e38f967b487ab1b69f702798d0d5
msgid "Specify output ranges"
msgstr "Specify output ranges"

# 54e8caa3b04d4559bd4023526d417a77
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."

# 41792875988741a4a707b5329aea6497
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."

# de8c6cef404f4a999be77717ac6785b4
msgid "Sort a search result"
msgstr "Sort a search result"

# 5557fab192b4435ab10bf5a125924e80
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."

# 678cbbfeeb964861b735a5ee8b9d5235
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."

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

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

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

# 08cde3213bca4e2095604b1ab01d44ec
msgid "footnote"
msgstr "footnote"

# 19047d83ee9f4571b076add28b310c8e
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."

# 2b94ba4c12614e22bf5795e2914ed572
msgid "Additional information about lexicon for full text search"
msgstr "Additional information about lexicon for full text search"

# 72d231c32dc848948c67cebd610b6dd6
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."

# b2688d950da94acfa3569ce58d460aeb
msgid "TODO: Write document."
msgstr "TODO: Write document."

# 0e9dcb7cafb045d6955e14eb6b922687
msgid "match_columns parameter"
msgstr "match_columns parameter"

# 9aa5daaac2af4126924097613c8ba16c
msgid "Full-text search against multiple columns"
msgstr "Full-text search against multiple columns"

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

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

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

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

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

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

# 345dafc3fb0349d4b8f912020ec27db4
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."

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

# 1cc8adc5021846f093a5e68a2f513f28
msgid "Creating one column index against multiple columns"
msgstr "Creating one column index against multiple columns"

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

# 5710917ddbe84b22833ae03f8ddd3d7c
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."

# 46aff8317da143ddb8028f54c3a44b4e
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."

# 6173c940edae477abb46bd96e2110210
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."

# 87e8ef07626f4a16bf415bcbf2f5d9b2
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."

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

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

# 9fd4ab3315614e889a7705e3eaf83df4
msgid "Full text search with specific index name"
msgstr "Full text search with specific index name"

# 142ad55039d24589a33887377993c91c
# 75e47fa1178d4d7a8c1c677eee722ceb
msgid "TODO"
msgstr "TODO"

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

# 40677568b3e446028ec1c70c158241cc
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."

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

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

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

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

# 2317b50198914b75b7e5cd2528c9bf72
msgid "Here is the sample schema."
msgstr "Here is the sample schema."

# bfa5147e591c4bad9c91afa190a8a330
# d305615eeea846e2a429608ddff01289
msgid "Here is the sample data."
msgstr "Here is the sample data."

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

# 510a945aa2634e77920dbfc3565b55f6
# 1170d39f1b584fe78714db270ef7dc0f
msgid "Query for searching the records described above::"
msgstr "Query for searching the records described above::"

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

# 171cf8e928c8453db71fe09e595f4b87
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.)"

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

# 77382664a0c34993af29aad84030d7e2
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."

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

# 152ff8eae208457f9e4c668415fc4ecd
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."

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

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

# a6e4de1d2210451da8777f63ccd882ca
msgid "Indexes with Weight"
msgstr "Indexes with Weight"

# 285c9bea6b694e10baff85b4eeefe606
msgid "Let's create micro-blog"
msgstr "Let's create micro-blog"

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

# 495705f2216c47f19a2878a73359d3bc
msgid "Let's create table."
msgstr "Let's create table."

# 16b2a7653cfa4503b4d29761765b23c7
msgid "Users table"
msgstr "Users table"

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

# c0544d73b7cb41cdaa649829a0168d35
msgid "User ID"
msgstr "User ID"

# 2b7cebd03b694726b7f8d76516e1005c
# 7a4598b527184707a8c49f6353db91a6
# 93ce8b8b12eb4075829cc375ee569d4c
# ab3fe034c6ac4e8ab5ea7c6e6c633532
msgid "``_key``"
msgstr "``_key``"

# 9665ed972a1143db97971cf6f779abc4
msgid "User name"
msgstr "User name"

# ae6899905f49480db1dca8642a5bbf6d
msgid "``name``"
msgstr "``name``"

# 6391d412ad71491e9720037b9b8d496a
msgid "List of following users"
msgstr "List of following users"

# 9b90cbb82a4447068202095c04e19ed2
msgid "``follower``"
msgstr "``follower``"

# 3cb485d221334c4a907d3722a08ba202
msgid "List of favorite comments"
msgstr "List of favorite comments"

# d920a755ed634e95b8b16ebc5ea12f42
msgid "``favorites``"
msgstr "``favorites``"

# 3aa7c6f6fdc8429186ac23e554b1b5c3
msgid "Current location of user (geolocation)"
msgstr "Current location of user (geolocation)"

# b76fb6c7dd0048bb8479cd8cb032ecc2
# 2d208ebb84ca43f891c7c5b1b68ffbc5
msgid "``location``"
msgstr "``location``"

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

# a4aeb096bb184d41a1adb39ab23100d6
msgid "``location_str``"
msgstr "``location_str``"

# 7134b57405244c38a43bbc643471fa65
msgid "User profile"
msgstr "User profile"

# a83f3fbad7bd495d8e52480299197301
msgid "``description``"
msgstr "``description``"

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

# d729528d11454995976c6237cebd7f4c
msgid "``followee``"
msgstr "``followee``"

# dde4a980fb8e4d8c80fefb6e8034cf29
msgid "Comments table"
msgstr "Comments table"

# 47b01537f9c1483aa73680bc4fcda50b
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."

# fa880815a1764b809f091977ea3ba3b1
msgid "Comment ID"
msgstr "Comment ID"

# 093e4fb469904909bf88cdcfa018d878
msgid "Content of comment"
msgstr "Content of comment"

# ebba96c687ec4f76a3e65e570f0e1915
msgid "``comment``"
msgstr "``comment``"

# 46eb36d086a1404ca71063672c712278
msgid "Posted date"
msgstr "Posted date"

# c5ab5663679d4f899ed58431a5b63e94
msgid "``last_modified``"
msgstr "``last_modified``"

# c801a594a04143eca7f584a7d039a813
msgid "Comment which you reply to someone"
msgstr "Comment which you reply to someone"

# 2a8623cbb5574153a644ab24e6b5bd3a
msgid "``replied_to``"
msgstr "``replied_to``"

# 85b41ebd84e441b5af5b2dc86025ad3b
msgid "List of users who you reply to"
msgstr "List of users who you reply to"

# a9060548f6234d9aab0446e72e5c8cdb
msgid "``replied_users``"
msgstr "``replied_users``"

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

# f343a6456c9b4595ad362e5a5fa53cc5
msgid "``hash_tags``"
msgstr "``hash_tags``"

# 0af1e1b71f914b3ea8216d642dc37e98
msgid "Posted place (for geolocation)"
msgstr "Posted place (for geolocation)"

# f4389fa0bbfb435abfbfd2c2f92690e9
msgid "Person who write comment"
msgstr "Person who write comment"

# e9302f3f47c440098155404c97cf3db6
msgid "``posted_by``"
msgstr "``posted_by``"

# 91384d73224540ceb3080bb6b7d6fa77
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."

# fd496a7339ac41518f72906c911bdb2d
msgid "``favorited_by``"
msgstr "``favorited_by``"

# 9529cea776f64d8eaf111c4a87adc6c4
msgid "HashTags table"
msgstr "HashTags table"

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

# 32a7b72685014afea47746b48b0f1d07
msgid "Hash tag"
msgstr "Hash tag"

# 6185f3056b054a9383a602883e350e6c
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."

# f40decc433c742678262187839573529
msgid "``hash_index``"
msgstr "``hash_index``"

# f3d83b6dde164271b10dcb74551ae988
msgid "Bigram table"
msgstr "Bigram table"

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

# ba79f33e73d74d33b35f6ceca294736c
msgid "Word"
msgstr "Word"

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

# 18ae4dd9a8ad419d8ff6c87f48125799
msgid "``users_index``"
msgstr "``users_index``"

# 10642c74b8434ea58b07294330224d3b
msgid "Indexes about content of comments (``Comments.comment``)."
msgstr "Indexes about content of comments (``Comments.comment``)."

# 5a09288ca5c043ca961f7b46b920bf96
msgid "``comment_index``"
msgstr "``comment_index``"

# 7b1bccd9b933482ba4aec3966e0ec663
msgid "GeoIndex table"
msgstr "GeoIndex table"

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

# 35d5a7fba83e4bf0adcfb49a54167e47
msgid "Indexes of location column for Users table"
msgstr "Indexes of location column for Users table"

# 3032505d78594770a9ee94f75314be15
msgid "``users_location``"
msgstr "``users_location``"

# 2bcd3ea4e5c34f4ab8d711110e7bb030
msgid "Indexes of location column for Comments table"
msgstr "Indexes of location column for Comments table"

# c92c99ecdecd41d6914a0844280cdb84
msgid "``comments_location``"
msgstr "``comments_location``"

# 193176c0cfcb4684b28b955647522d8e
msgid "Loading data"
msgstr "Loading data"

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

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

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

# 52eaf877fc7943278c6bd3d4cc9684a3
msgid "``last_modified`` column in ``Comments`` table use Time type."
msgstr "``last_modified`` column in ``Comments`` table use Time type."

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

# 806ee5b83c8c4e86896161e137c8f5ab
# 443579d1d6b04fc8a8cf68e50a65edf8
msgid "Search"
msgstr "Search"

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

# 8b2c30c4a31b4395b7451ce0de885a52
msgid "Search users by keyword"
msgstr "Search users by keyword"

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

# 91493f3cff0e485c90a4fcaaa9821b82
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."

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

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

# 434968ee728747baaf4db0dc83f02fff
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."

# 91361eae0e2e4bb28c6823c094e29991
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."

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

# 5ffff84738c84dadbbbbe5737c0ca63e
msgid "Search users who follows specific user"
msgstr "Search users who follows specific user"

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

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

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

# 49536a3702154c86a505778f624eb200
msgid "Search comments by using the value of GeoPoint type"
msgstr "Search comments by using the value of GeoPoint type"

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

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

# 94f05dff24864366a680c7b69773ed3f
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."

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

# 0ee6ad3b2d464bd1a208f5a88228baba
msgid "Search comments by keyword"
msgstr "Search comments by keyword"

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

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

# 4de5ae7b419140ff906450eeb0e15eb4
msgid "Search comments by keyword and geolocation"
msgstr "Search comments by keyword and geolocation"

# 60dabb0033524da0a6ff23607cde50bb
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."

# 1195cb08ab4249ce8a14bbac7eb9456a
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."

# 8660e8bb16e64350a1880f17297cde76
msgid "Search comments by hash tags"
msgstr "Search comments by hash tags"

# 231be7cdae534a488f32e8970e0e9c9c
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."

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

# 68413a8e9ef04148b2893023329a233f
msgid "Search comments by user id"
msgstr "Search comments by user id"

# 4858fca354c84d10840cb92b3b579be6
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."

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

# 16196ad876b04a65a9c322d1a667c2bf
msgid "Search user's favorite comments"
msgstr "Search user's favorite comments"

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

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

# 994a6de70fb04fc8a47b74d5cc931ffb
msgid "Search comments by posted time"
msgstr "Search comments by posted time"

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

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

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

# f3df4532d28a46fd8c11b358efec3844
msgid "Remote access"
msgstr "Remote access"

# 975994f0603f486a9aa1721ef1866bc3
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."

# 2077a3aa7c1b48148c80f0fbb3af1af0
msgid "Hypertext transfer protocol (HTTP)"
msgstr "Hypertext transfer protocol (HTTP)"

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

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

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

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

# 116155d852334f65b34e79334b31d9c1
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."

# 5f1de51fea3841e08cde8fa6849f7c99
msgid "How to send a command to an HTTP server"
msgstr "How to send a command to an HTTP server"

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

# 59e0ff90a02949f99c7ebe4d04fd8f06
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."

# 1f0d303f87df422e9e34dabe89e0cd9c
msgid "Administration tool (HTTP)"
msgstr "Administration tool (HTTP)"

# 16229c0b965e4083baab8037dfc166b7
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."

# 54d47b3abad84bf98134b8710cb0b909
msgid "Security issues"
msgstr "Security issues"

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

# 8e98d512bcf648ac9afe7afede4f75a2
msgid "Prefix search with patricia trie"
msgstr "Prefix search with patricia trie"

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

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

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

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

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

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

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

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

# f136208d781a44e1ad8ed12fd2f6d161
msgid "Query expansion"
msgstr "Query expansion"

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

# 473e5432ff524629bde6a84321511a50
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."

# 522588aace4146f89f3df45ebc6d123e
msgid "Preparation"
msgstr "Preparation"

# 1232a03c3dce4382956c686f43e617ff
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."

# 7c31f09d434b43aaaa9d9641c46fbe91
msgid "Let's create document table and synonym table."
msgstr "Let's create document table and synonym table."

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

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

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

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

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

# 7137828800454891b21ceb64cef185f3
msgid "Various search conditions"
msgstr "Various search conditions"

# 34c49b908eec409e89908a76ed06d858
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)."

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

# 4773780a2a194839980ada28d4a997ed
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."

# 8d71f85d00c84a69b61920a616759485
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::"

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

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

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

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

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

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

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

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

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

# 89a189a5b8c74718ad521c9ac1974f80
msgid "The condition of ``sortby`` parameter is::"
msgstr "The condition of ``sortby`` parameter is::"

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

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

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

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

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

# 8f8d9b93f1b24efcb61b40dbc58e0cfc
msgid "Specify longitude and latitude as follows:"
msgstr "Specify longitude and latitude as follows:"

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

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

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

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

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

# 13260980159c4608b3396fe72eceb1a6
msgid "Let's register location information in milliseconds."
msgstr "Let's register location information in milliseconds."

# 053a1ad992684ddf8c8129a14fd4e877
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."

# 15344c87b6db4a54880efa255cc73b51
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."

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

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

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

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

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

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