# -*- 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.3\n"
"Report-Msgid-Bugs-To: \n"
"PO-Revision-Date: 2015-05-12 19:44+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"

# 750749a18ebf46508578e8aa1f78e28c
# b2db9d8d0da84b2eb683c1229827e34a
# 830387745cee453cb392dd77483184ae
# e9914e63e37544a6a1da57b2511f9238
# 09f1f5b4504f4f3f965030583525b5a5
# 0dedab424ccb459f88f8852f3d921dec
# 2db5522970a348228e07cd17ab4b9223
# d34baf0e361f43b0a815295c28303c91
# 7bbeeb18cc754cb2aa6e9543842cf1af
# 82ce36d7b03d4da4930835934e5d52a3
# b9a33686c65f46c0b13fca73ca982c2f
# bde989b8de0446d5ba177f4f4ab81ff3
# 56470f57008d4ecdb0dd38fa0bb84ed1
# 05ae174849be42558572aaa4e1e10e85
# 14a74b9dc2b943faa37cc0a3e42fa492
# e09164d9e3ee43abb0b008944a3a96c6
# 5247b739ab37404ba4dc890ec3f80000
# 687ccab374884684b12ea32cf8d1b09d
# 5e88ad6c11a14167b65afda4f4555d9f
# e911c640c6eb4782b45a1169e84e7bd4
# 016ff6330c4749a097abd61dde213aaa
# e9885a4f5bde43a68e812e34bf38036b
# 154b74546da641d28d4db26bce5ca600
# c7566c6b832c4a3db1a3130947bcfdbd
# 1bdf51106fd74f478246af482527e747
# 5f5f4cb46f294200989ef6f40cee1155
# d714e3db8d2f4c88bebd9b6ddad44fe4
# 62556ea7c4694dbd9e4c8fa3eeedaa1e
# f6482632d340477f929107ddb25e1800
# 6a86a0fde04847da9c6b6dc81eb6a4b3
# 45d9dd372e344a13a25efa9852e7d953
# 35d16a6f5ec54cfaa419f479292d2a89
# 1de596937b5347ad9203c287dc6619bc
# d2d2d6d140f446d1b96625241bf570be
# f398d5283ec14a0c9efc61b473f59ff9
# a8ed006c908246918acc3d6f6ff8dca8
# c879f51fad28499e82c2c2ec2d672ca0
# f9ba75dd6b964b1c8b9c318543521091
# 1aab23bf168f4da3b16eb83b392b3777
# 7c365f49304c46058f0dd9b65e3e5a95
# 1b7750c2c9144be0a799a76d681359bf
# aa9e3be57d944348821d63360336013c
# 7dac7aa979864970a6845b8ad9ad4ad0
# 7ce86a304d1b4006ab605e143cae2b28
# 8e6f6c4efed1447d813eeda895e46cdd
# 4c02a93741514de2923eb4dc106079de
# 88327579c3704745922282c15fe8478d
# 8e3d011cf80144b389a128d4be1923c0
# 724659dedba94ac5adbf00dbeb2feefc
# c9fd75f0febf4b5192546020dfd13c5c
# 6862ea772ca64b66a686f5519451abf7
# 6a65e1971c7f4e33ae19ffc69058ab8c
# fdf8fdc77ddf4a47bb0a0c8ce45368b3
# 362f1d1a604c4844a6a3cfb56fec83ae
# 573c094842da40578eed3d9471898361
# b2e61d6d89a14607948886705387ca73
# 673197c345674bdaa0eb02ec806109a4
# b967a9909c5646bbb92df640e802c852
# da711076e66a4c4eab01aad9df6092dc
# 95c6e348b69342f698ad4fc4ae4778aa
# fb0955333bb8422eb5c1fff17557e720
# a8996c90dcc2432cb1b2e92710be9222
# dba4c83867f54b4b98097d1854015e25
# a24e2a0b3dfb41c18b71dee121bc3e3a
# f1d115982659431b8f5d1da237fbace7
# aef89f8254c4411b81ab745e706d06b5
# 2a93067e65014cddaf2fbe39fb7461e0
# 22c0673b22004de4a5ab69462a279dca
# 8356ea8dc1404c98ad93333b7a98dd0b
# cfd82c23067c4c8795f4fd3ee979fba7
# 135f9b20e4b14af599879883762f4739
# 7d21d7bd961a4f54a9ca4a56ef7110c6
# 358625d0feb04968b42dad8ea49c50f9
# a6f80169683942b192693e68c0f9c930
msgid "Execution example::"
msgstr "Execution example::"

# a6e611f110a344a887c65130692e111d
msgid "Tutorial"
msgstr "Tutorial"

# 6b9bfb11cc834e12bf719e5fbcd94e3d
msgid "Various data types"
msgstr "Various data types"

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

# 876de8a824a949a5bb86388e7c8265a7
msgid "Overview"
msgstr "Overview"

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

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

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

# eae2edb1ba70407e86574741dfaee5a8
msgid "Boolean type"
msgstr "Boolean type"

# 06727b090acc4e3185a7c135f7dc74a7
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."

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

# 0f290d7434d34bfdafd68139b43a48f9
msgid "Numeric types"
msgstr "Numeric types"

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

# 071058d9c23d44b684cb4cb0335d78ad
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."

# 6657581ec78c497ab4bcd80f093b91a6
msgid "String types"
msgstr "String types"

# 488da3d133104860b3cfe25ca567fa6c
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."

# e97ec33cbaef42e19455620771b1ef17
#, fuzzy
msgid ""
"The following example creates a ``ShortText`` column and updates existing "
"records. The third record (``\"Block\"`` key record) has the default value "
"(zero-length string) because it's not updated."
msgstr ""
"The following example creates a ShortText column and updates existing "
"records. The third record has the default value because not updated."

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

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

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

# dd4f8eecd04747f693759fd8134b08ff
#, fuzzy
msgid ""
"The following example creates a ``Time`` column and updates existing "
"records. The first record (``\"Monkey\"`` key record) has the default value "
"(``0.0``) because it's not updated."
msgstr ""
"The following example creates a Time column and updates existing records. "
"The first record has the default value because not updated."

# 49c1ecacb7974f349a1d018d4d8659d4
msgid "Longitude and latitude types"
msgstr "Longitude and latitude types"

# 16ae16b187344b90bcf66081770c3e56
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:"

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

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

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

# b85a64fcb2bf4c0e92be5e9cba4550cb
#, fuzzy
msgid ""
"The following example creates a ``WGS84GeoPoint`` column and updates "
"existing records. The second record (``\"Flower\"`` key record) has the "
"default value (``\"0x0\"``) because it's not updated."
msgstr ""
"The following example creates a WGS84GeoPoint column and updates existing "
"records. The second record has the default value because not updated."

# a596f989b50b48098f5db1ab11e42511
msgid "Reference types"
msgstr "Reference types"

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

# 0cbe6f6b32164b4a9662de3d57496b90
#, fuzzy
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."

# 5d5d88d87bc54eca9847147bc5e7183c
#, fuzzy
msgid ""
"The following example adds a reference column to the ``Site`` table that was "
"created in :ref:`tutorial-introduction-create-table`. 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."

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

# d17352280f1341d8bffc7a49022f3000
msgid "Vector types"
msgstr "Vector types"

# 95a3a84703f84f34aea29577a2e0d5e6
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."

# 61f5f9c8da1b481f9764673f8ebb02c3
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."

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

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

# 3c76af3dec5a4677b3ba53b37152a725
msgid "Drilldown"
msgstr "Drilldown"

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

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

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

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

# 7415ba8a44aa4027995f3739b2cca0b3
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."

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

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

# 070de6b4c4a3484aa704f35298b60d21
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."

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

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

# ac658996932d4cebbc178b39c047d8b2
msgid "Group by"
msgstr "Group by"

# 0dc3cbe9fa6849cf877664f840c063d9
msgid "The number of group records"
msgstr "The number of group records"

# 31c0461668284cc5b34ff4550843cfbc
msgid "Group records means following records"
msgstr "Group records means following records"

# 8ba61b48a8bd4882939565f39eea7f87
msgid ".org"
msgstr ".org"

# 0acfe44648b7499bab0573010da98ecc
# 867e19a6ded3402d81e912fb5db93701
# 7260ca63bbc94cfcb4de8e2ccd6c24ee
msgid "3"
msgstr "3"

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

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

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

# b32187cae67a49068232712ee063d003
msgid ".net"
msgstr ".net"

# e94910e776424fb0980faeec1260f4f0
msgid "http://example.net/"
msgstr "http://example.net/"

# 041c3a575a794954aa51a231799b4e24
msgid "http://example.net/afr"
msgstr "http://example.net/afr"

# 2a16e7e8924146b7ad41225511e6ab48
msgid "http://example.net/atv"
msgstr "http://example.net/atv"

# 46d43b5f66bb4534b153a7cdd34a49bd
msgid ".com"
msgstr ".com"

# 62a94bdce86341e0937715e56591fd95
msgid "http://example.com/"
msgstr "http://example.com/"

# ed5353d0e4724d31a5ea21389bd83c7b
msgid "http://example.com/rab"
msgstr "http://example.com/rab"

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

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

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

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

# 85695f328d6442d6814d1a5a24320631
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."

# 010c43e7c4a54ea491a6b400bc0d8ab4
msgid "Drilldown with multiple column"
msgstr "Drilldown with multiple column"

# 782b745cb2604e398212368c61925d6e
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."

# d596269c9f2d4edfa2bc326d6ce3408a
msgid "Sorting drildown results"
msgstr "Sorting drildown results"

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

# 498e5a790e4f4ef1b9886293005b61a2
msgid "limits drildown results"
msgstr "limits drildown results"

# 6923f26f17304bac9134ab134f4b978f
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."

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

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

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

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

# 5eec362f7fea4fc38677302d31d23814
msgid "Tag search"
msgstr "Tag search"

# 5856e439588747b29abf4640db8e51a7
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."

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

# 55a5b3a83fe04ce29d6aa135f711a547
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."

# 557ac5b458a94bc79d3ba649be9a8a87
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."

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

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

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

# 8977910176fa48abb8b21846751c292c
msgid "Reverse resolution of reference relationships"
msgstr "Reverse resolution of reference relationships"

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

# 967dea9b0e074555a01f6e05023d6f72
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."

# 9496900614e34f9bb288e3fa54a6c162
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."

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

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

# 23f9324b79694d91853215b16b62e5de
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."

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

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

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

# a4534aa5be63479c891c96fc6e86b7da
msgid "Basic operations"
msgstr "Basic operations"

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

# 0d9305dffe624cd1857e10912f9dcdb4
msgid "Create a database"
msgstr "Create a database"

# 258ae6f2e40b41c1b59bb618a13a5a5e
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."

# 83032dfc8e8d4ca998b453b0a4ce33c9
# c29b6ba4b8914c68916951bae16c9afc
# 127e5962d9c6462eb364472b430ad6b6
msgid "Form::"
msgstr "Form::"

# 33602045e4ee452c81956fef69f01f7a
#, fuzzy
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 (For example, "
"``db open failed (DB_PATH): syscall error 'DB_PATH' (File exists)``. You can "
"operate an existing database in a way that is in the next chapter)."
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."

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

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

# 664f706b226b4e3a8496f0a2c6c8373e
msgid "Operate a database"
msgstr "Operate a database"

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

# 41dacbbf30aa4c7a81f58b6d6de71997
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."

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

# 28ad9e0b0c1d42508b15b577406faf4d
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."

# 88628fe0059d4e7eb2a29ee200f35138
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."

# c4faeada5b6948e583c0d239785cc7f8
msgid ""
"You can format a JSON using additional tools. For example, `grnwrap <https://"
"github.com/michisu/grnwrap>`_, `Grnline <https://github.com/yoshihara/"
"grnline>`_, `jq <http://stedolan.github.io/jq/>`_ and so on."
msgstr ""

# f076b5c825334670bf90dbdcbb974444
msgid "Command format"
msgstr "Command format"

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

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

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

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

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

# fec7c74811d04a989174cd4289470af4
msgid "Basic commands"
msgstr "Basic commands"

# 8568626664234c41b18b8ed640f585b5
msgid ":doc:`/reference/commands/status`"
msgstr ":doc:`/reference/commands/status`"

# 15adcba2120a4f40b7e330197149faf6
msgid "shows status of a Groonga process."
msgstr "shows status of a Groonga process."

# 18418494a3924eef8c8fd9cc2d15f0d9
msgid ":doc:`/reference/commands/table_list`"
msgstr ":doc:`/reference/commands/table_list`"

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

# 3e149cf4b40448a7856d915fde0e75c8
msgid ":doc:`/reference/commands/column_list`"
msgstr ":doc:`/reference/commands/column_list`"

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

# 6a14730b398e4543ace6cf36aac6fe45
msgid ":doc:`/reference/commands/table_create`"
msgstr ":doc:`/reference/commands/table_create`"

# 3d74063e01714b5c9bcc8e5af4903054
msgid "adds a table to a database."
msgstr "adds a table to a database."

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

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

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

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

# 1d090c92fb6e4bca83ff14ceb2dd6906
msgid ":doc:`/reference/commands/load`"
msgstr ":doc:`/reference/commands/load`"

# 7166be21c57e4ecfb28f1d195486241e
msgid "inserts records to a table."
msgstr "inserts records to a table."

# 08f87bd8b33a4706980f6898eac4813b
# 9012dde91ee145159e830eba4bcc62ad
msgid "Create a table"
msgstr "Create a table"

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

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

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

# a858de1dc5984586819e5d8416bd98f1
#, fuzzy
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."

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

# e906cb2fab88416295c1bce3b36224a0
msgid "View a table"
msgstr "View a table"

# 843c7aadd22a48a48afc9972d2c0f82a
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."

# 1eda9cf0a5f741869f5dc3d7ec854e89
#, fuzzy
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."

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

# 461eb17135334b7d863b32e14872c278
msgid "Create a column"
msgstr "Create a column"

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

# 7b200542ca834543b8520f28dec33e1e
#, fuzzy
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."

# 3263e2c22e21456c8912dae1657f30db
msgid "Load records"
msgstr "Load records"

# 1731de0fa4b24cd6bbc83ac96bc480ee
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."

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

# 0951ca7b68a643d0954f6c97fc2e819d
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."

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

# f73e3b88ea55482ab81c3e24b3521440
msgid "Get a record"
msgstr "Get a record"

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

# abf763e242c742f0893f4d45061cd0b7
#, fuzzy
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."

# fe2386b4233448cc90a7f75e1376db23
#, fuzzy
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."

# 6d87aa6213f0498ebd0474b3a4f735bd
#, fuzzy
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/\"."

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

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

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

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

# 339b3979601e4d2faae62f87287fa3fe
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."

# 279f092b4a9241c481925b6ebf9dcedb
#, fuzzy
msgid ""
"The TABLE_PAT_KEY flag specifies to store index terms in a patricia trie. "
"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."

msgid "The ``normalizer`` parameter specifies to normalize index terms."
msgstr ""

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

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

# 7752088ba3d04a3c8a93c5003fe69f5e
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."

# b7b8c541f633422faf77e1863e042ff4
#, fuzzy
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."

# 8449b555accd49a0b334e885c19e21ed
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."

# f1aab69d26104881aa3a719d59a698eb
msgid "Full text search"
msgstr "Full text search"

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

# 590f4ef9c77a400fbeecbf8414ad13cf
#, fuzzy
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 NormalizerAuto 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."

# 3640b83900cd46f4881772e062f1fd25
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."

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

# 13810764ea774434a1f66e1423e2fa2f
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."

# adf6ee5b59914ac7842a78f6200ed9fb
msgid "Specify output columns"
msgstr "Specify output columns"

# 6936a82d1e9a43c3810412a8de0de3ff
#, fuzzy
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 (',')."

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

# d61977c6b7c1435c991d5ee2863f0f6b
msgid "Specify output ranges"
msgstr "Specify output ranges"

# 1aab7ae3520c4626b56eec40e262de62
#, fuzzy
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."

# 1dcbcf1d78524a158d8d060813e2122b
#, fuzzy
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."

# 39504ebce65e439d9b93ba2248688220
msgid "Sort a search result"
msgstr "Sort a search result"

# 2fa60b1d4f3749bca6ab94b79021135f
#, fuzzy
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."

# 31c8277c57824d7baecf8de631b825fb
#, fuzzy
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."

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

# 814867c204d840c7ac4883a766ef9e48
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."

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

# 5b9ef9836ca84693b13ed65309b27225
msgid "footnote"
msgstr "footnote"

# 559f0ab4cd6641c081776d1e125e0513
#, fuzzy
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."

# 8ec2805638f5453395a0b062462efd49
msgid "Additional information about lexicon for full text search"
msgstr "Additional information about lexicon for full text search"

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

# 7a3ad7bcd59541528dcb079970d53905
msgid "TODO: Write document."
msgstr "TODO: Write document."

# 7ffcba1e3ca4421cb7f7421bfa701fbb
msgid "match_columns parameter"
msgstr "match_columns parameter"

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

# 9ab8b8b12d6d413db9fe5a8facf74767
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?"

# 66f2250ec7314e65b90215b26c7c8d66
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."

# 46e00b93003941679a75c2173d841ea6
msgid "Creating column index against each column"
msgstr "Creating column index against each column"

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

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

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

# 0888367e71a049a9ac1c15bb151bfd15
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."

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

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

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

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

# 693af9966f674fbf89997fe37558cc40
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."

# 945725480b7b45aeb2757ed9a60c2ec3
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."

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

# 45794336a2a1454d8606d936d3a3c306
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."

# 646ea4bf88494fc3800898344f40af2b
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."

# 5e4c7509c2af465b9868695ab2f6eb0b
msgid "Full text search with specific index name"
msgstr "Full text search with specific index name"

# 019e51a6973947dc8125f7420c53b5d5
# 1e67d3d8adc24ca984720171af5bf040
msgid "TODO"
msgstr "TODO"

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

# 93fc73335e094a21abea7a1e5ffe9e8d
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."

# 427f12dcbff945809144d437af4a8c13
msgid "Here is the concrete example."
msgstr "Here is the concrete example."

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

# 63c70b2e0d0c4bb8a75e5148a6a2ca3c
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."

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

# 0089dce7edd04357a0996a3ff541cb21
msgid "Here is the sample schema."
msgstr "Here is the sample schema."

# eeb5130b35cd408abd3ab6fb428000be
# 29a91d09403a405ca70411538e0be8e4
msgid "Here is the sample data."
msgstr "Here is the sample data."

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

# a0bbac010e1744ca991a2022e77712a9
# 8d509ebefe23489ba531fae0e78932e5
msgid "Query for searching the records described above::"
msgstr "Query for searching the records described above::"

# 0f6320b94d624a749ba0a7f19ce277c5
#, fuzzy
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."

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

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

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

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

# c44cd17abf924a86bbd151d2d1c7709e
#, fuzzy
msgid ""
"The first query searches ``mroonga`` from ``Comments2`` table, the second "
"one searches ``mroonga`` from ``Replies2`` and ``Comments2`` 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."

# 21dc9ac191b7471282aba58e077c6c55
#, fuzzy
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."

# 72f626bdb20c466b914aa43772e535d8
#, fuzzy
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."

# b9dcfdbca4e646afbf75b661464ec7ae
msgid "Indexes with Weight"
msgstr "Indexes with Weight"

# 34745aa7da0a4ebd906a2729027dc0f6
msgid "Let's create micro-blog"
msgstr "Let's create micro-blog"

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

# de496e98ad7b4294b0e695ad9fa052db
msgid "Let's create table."
msgstr "Let's create table."

# 8fb259c1793e4ceb9bf013c9e7e2082a
msgid "Users table"
msgstr "Users table"

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

# 491f5d6848774f6e8690c4841d7b07d2
msgid "User ID"
msgstr "User ID"

# 992455a4b3574c33a361c8ed6a7eaa68
# 8e41fcbd0bc04eb198e71b777f4ebebd
# 92bae0666b764f948afcdaa411ac9d56
# d289e65723b94f60b7320060a0e8bea7
msgid "``_key``"
msgstr "``_key``"

# 094d288197674de38b2d4483d27b8328
msgid "User name"
msgstr "User name"

# d78f2987414f4273923def230a17d2a3
msgid "``name``"
msgstr "``name``"

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

# e32b78ebdd564e7c8021328353169d1b
msgid "``follower``"
msgstr "``follower``"

# 73530d04a3704140a8fbfc97271e3b5a
msgid "List of favorite comments"
msgstr "List of favorite comments"

# d04014bb0a9343908c5eef7c9a4490d5
msgid "``favorites``"
msgstr "``favorites``"

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

# 38ab442b64674709bddc5da49baebe1d
# 3805527e00d848b7acdd3de4eb9b18cf
msgid "``location``"
msgstr "``location``"

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

# 4f59652df9384b02900c5997afbf5095
msgid "``location_str``"
msgstr "``location_str``"

# d0a1c4a5ff3846488b377b089de25fee
msgid "User profile"
msgstr "User profile"

# 26a113a61edd4001bce061691ba9e7a1
msgid "``description``"
msgstr "``description``"

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

# 96b32a121e4245dda1ee7e1f87be1a60
msgid "``followee``"
msgstr "``followee``"

# 057b806bf8a0451bb58ac5292a84593f
msgid "Comments table"
msgstr "Comments table"

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

# 96b20f31c1dd45979285310e3bf118fb
msgid "Comment ID"
msgstr "Comment ID"

# d73293b31fbb4c82a1dd454de81759c0
msgid "Content of comment"
msgstr "Content of comment"

# 052733e448534548be186cb8924a27d8
msgid "``comment``"
msgstr "``comment``"

# 08de7a3650cd46a189a1293ac380eb8c
msgid "Posted date"
msgstr "Posted date"

# a30509b38e6a4d6b80355604d20f9421
msgid "``last_modified``"
msgstr "``last_modified``"

# 53afd8bbbc1644599a51fa791e132f4f
msgid "Comment which you reply to someone"
msgstr "Comment which you reply to someone"

# c633d15bd1884b54a8ead0ae71c08c6f
msgid "``replied_to``"
msgstr "``replied_to``"

# 846dd1da87e0476d9341fd9c03dafea7
msgid "List of users who you reply to"
msgstr "List of users who you reply to"

# ee348b4b3ad8451f87f5d4b7c29c795f
msgid "``replied_users``"
msgstr "``replied_users``"

# 3b4ea6021e0043c486d8f53591ed19cb
msgid "List of hash tags about comment"
msgstr "List of hash tags about comment"

# 38e7e22fb9034397a216a7da1c5b2efe
msgid "``hash_tags``"
msgstr "``hash_tags``"

# b1a522feb9d849e8adab1174d7458217
msgid "Posted place (for geolocation)"
msgstr "Posted place (for geolocation)"

# 045eec67f95640b49a2f73da31b8f470
msgid "Person who write comment"
msgstr "Person who write comment"

# ef5c2c70da644849b7b79f73b4203a79
msgid "``posted_by``"
msgstr "``posted_by``"

# 165b399d06854c4b879a6141493538ae
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."

# 66e046d1643c4580bee6382c5c8c28ca
msgid "``favorited_by``"
msgstr "``favorited_by``"

# 71cc2ac2418c411a9a6197560ce994e8
msgid "HashTags table"
msgstr "HashTags table"

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

# 8c3edf1e816f4f5b856679dae7cf8165
msgid "Hash tag"
msgstr "Hash tag"

# 05c49af0bf334cd3a3dd239b3c052434
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."

# 1f1866681fff4684a8364086e91ace30
msgid "``hash_index``"
msgstr "``hash_index``"

# 6ae5db05341840fbbeb553f7423f990f
msgid "Bigram table"
msgstr "Bigram table"

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

# 85038d1e51bd4516913697c17f6bd731
msgid "Word"
msgstr "Word"

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

# 7efe47aed9df482092db96b19c698d0c
msgid "``users_index``"
msgstr "``users_index``"

# 664deb08a17c4a598d49b706e8f176a5
msgid "Indexes about content of comments (``Comments.comment``)."
msgstr "Indexes about content of comments (``Comments.comment``)."

# 228708b8e76748faa92cdb0a3f9001c6
msgid "``comment_index``"
msgstr "``comment_index``"

# 7b52721e52aa43b188a61d9afffe5f6c
msgid "GeoIndex table"
msgstr "GeoIndex table"

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

# 2bee84166edb45d39ae0f69941be389a
msgid "Indexes of location column for Users table"
msgstr "Indexes of location column for Users table"

# 546d7b85a5d24d9d9fb42eb3900133cc
msgid "``users_location``"
msgstr "``users_location``"

# 08e58dab5b3544faa9bccf6f39ac2ba1
msgid "Indexes of location column for Comments table"
msgstr "Indexes of location column for Comments table"

# c99a619ea91741408b6015f15db89e31
msgid "``comments_location``"
msgstr "``comments_location``"

# c1dc521fc92d41eaa1b05bd82e1e29df
msgid "Loading data"
msgstr "Loading data"

# 88bb2b26fbc2403cb5cd15dda30bc437
msgid "Then, load example data."
msgstr "Then, load example data."

# 043173779d1147b9946cd59bcb0cc403
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."

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

# 9a0513593111490c9015828bcb10df8d
msgid "``last_modified`` column in ``Comments`` table use Time type."
msgstr "``last_modified`` column in ``Comments`` table use Time type."

# 609c35e768e943b08f908a9b458218ea
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."

# 543bf9abac4b470cb4fa34cc1312c26f
# 2e14c485b6bb4640bc33d5f7456f1d8c
msgid "Search"
msgstr "Search"

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

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

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

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

# 254fb08a1fe540d3bb695bbdb7e3b5f7
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."

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

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

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

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

# 866a574a926c4bcbbd40dce2dbcb77d2
msgid "Search users who follows specific user"
msgstr "Search users who follows specific user"

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

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

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

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

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

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

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

# 02065f09b2ce433db53c13298bda4b7d
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."

# 558c577b64e84979a686528b3b86a544
msgid "Search comments by keyword"
msgstr "Search comments by keyword"

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

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

# 135986dca68441588fccd9c7649729d3
msgid "Search comments by keyword and geolocation"
msgstr "Search comments by keyword and geolocation"

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

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

# 92ff0df9ac1f485192750586cc13a486
msgid "Search comments by hash tags"
msgstr "Search comments by hash tags"

# 497e8672bee74f11b7eb48aa0f8352e7
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."

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

# 79645e255bbc485e88ba67c81d0da28c
msgid "Search comments by user id"
msgstr "Search comments by user id"

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

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

# ec6104f9be8b4a17b75fe07a56d9612c
msgid "Search user's favorite comments"
msgstr "Search user's favorite comments"

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

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

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

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

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

# 74c6a8a8b19f4cd28261bb6324e645ed
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."

# 331dac92eb974f049cb47d57f8adda6a
msgid "Remote access"
msgstr "Remote access"

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

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

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

# 481f5b53c4b247bc9af2c712a5844196
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."

# 617bec8b45dd47b5843866825c54d1e0
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."

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

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

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

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

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

# 78cb985296254ee48345da6d84ef8c25
msgid "Administration tool (HTTP)"
msgstr "Administration tool (HTTP)"

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

# 440ef5ae7e204f4bba3ad0f10f748170
msgid "Security issues"
msgstr "Security issues"

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

# 72bb77f95aa742169d7d7bdad5eb6a64
msgid "Prefix search with patricia trie"
msgstr "Prefix search with patricia trie"

# 697c62e8922f4d62a07d4fcfb7136121
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."

# 11a0508ec22b483c9377a39a0fc76010
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."

# 0330cd8376df459f81de3bc3b755e60b
msgid "Prefix search by primary key"
msgstr "Prefix search by primary key"

# 24d59b86ad274aa68fcdfdfbea86f52b
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."

# 0330cd8376df459f81de3bc3b755e60b
#, fuzzy
msgid "Suffix search by primary key"
msgstr "Prefix search by primary key"

# 24d59b86ad274aa68fcdfdfbea86f52b
#, fuzzy
msgid ""
"table_create command which uses TABLE_PAT_KEY and KEY_WITH_SIS for flags "
"option supports prefix search and suffix search by primary key."
msgstr ""
"table_create command which uses TABLE_PAT_KEY for flags option supports "
"prefix search by primary key."

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

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

# b35c7fc5f0c64a1f8fe25d5365ce38ec
msgid "Query expansion"
msgstr "Query expansion"

# 0482de2fe40f4e6ca89166b2194d411c
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."

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

# c04c5bd083274b45ab41b6bf054919bc
msgid "Preparation"
msgstr "Preparation"

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

# 26ee3f9388c744c3b2ece53b01de7e19
msgid "Let's create document table and synonym table."
msgstr "Let's create document table and synonym table."

# 330c84ec743b4910b34ae02b024ee41e
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."

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

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

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

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

# 8a2ddd5340de408fbf0baeb1d745a3e8
msgid "Various search conditions"
msgstr "Various search conditions"

# 492abbed3f7a45f0b0673bea396a1c8c
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)."

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

# 723ea100eb684d3abbb9472c22ced11b
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."

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

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

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

# 7690275c16264eb8b6945882534778fa
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."

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

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

# 332f0f08841c46a680be85a081416c85
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."

# 5105be9b54a649cfa3bb6201e63a6ab3
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."

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

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

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

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

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

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

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

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

# 9c3e4d80303f426da35033dcd4faef44
msgid "Specify longitude and latitude as follows:"
msgstr "Specify longitude and latitude as follows:"

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

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

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

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

# 24ff87e44a2947dcb68ac8d473e4ea5a
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."

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

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

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

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

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

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

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

# 4708ea4a4cef4de0be881ca34a37d38c
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."

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

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

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

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

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