# -*- 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.2\n"
"Report-Msgid-Bugs-To: \n"
"PO-Revision-Date: 2015-03-31 14:14+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"

# 8ffedcf77da94156a1a3d42329028921
# 79c987ca74124792bdee2ce4642d3a2e
# ea7a7631cfc24f85b3ae2cdfbfb83a09
# c42ec9ef1c634e4288373265e147c005
# 4a9bf09b5cfd4b65bfdf3a41a0a4acac
# b3ea98aec95a44308c8ba070d606a850
# 2245570fa2494141a19f69eda681a856
# 2008dc1df7b3462ea4b6dd7e30233e10
# 4f9764d5031e4dec86eb32494993829d
# be5e88ada1f94c13a9ab522f0d1c8e89
# 1751f1820fa841e09e3983da0ce58032
# 2f25bb4303ec49adbba56cba00289a99
# ef88ea0bbfd04c1da7dda9dcbd30aa75
# 321e36a234be4d0fbf7dabf5a9ed380d
# ce093daea176456496e4d09eae20e881
# f0d61ee02dd942b3ae9c79e50d37b41a
# 08a33f21c7d0452fb086682bf2895fe2
# 44d863ac9f88407d9b0d67b3dbe2422d
# c5a898d77d6d43f89eebe5c0e0a5657e
# 6929de89616d41fc8c9bcf0fbef39468
# 2b2e4dfb617a4f079c700b3b1f3b981d
# 6ffb310091a4498abb9fd181e9588d61
# e91a528072164e0288b5b6d0485e91d1
# b816d842c4444b108bbeef7a890373a5
# 86b2c11ae6964d63a5360d0b3e0573df
# d614eacbf15349359b50991f65c601bb
# e4ec77e42e544d059abf7876d9a1c9b2
# 680f11376ff84b6bba36247cdd19a1fd
# 3cb7b50af001471281d2d9737782b8d8
# ee3e949b4b0842beb624e7ddbcccaf46
# 2a7f0f694d0147c6853c3610dbd704c0
# 590d99c463ad4bc3aaff98c98b81572d
# 0ce349e3977547faab5985bbc22ca6e7
# 8fa3a7a06675475d90081dc4b881bc59
# 0739b358a75d4f2e9e17a31c32ce4745
# b4af1b7c5bb549d795902d1ad80a6461
# 679a646141ca4a5980f57eb0e881d86c
# 1c35120235dd444dbee2977230c94a15
# 6bed27fc76454e4d9ca8d46c80ee5799
# eb578f99193b4b16836582ad1611119c
# 3d1db01e06914791bcdde082312104b5
# 2110b7860d004049bc8cd35272ef8bd8
# 36c1a32af84b43619edeb467795e3066
# f87f9cfd4ffc4c7e87aa651c71895b9e
# 582adf628af0493d9eb70c57193d4868
# 1de931e64cf94be0a58aad9435396951
# a06f94bc641d48eb82537f0baa97754e
# cf735a3b7327484ea2ffe4a949bb54da
# 13787f8a292745b2afcada9e0a958663
# b54b981a96b74814bfdb839c499d7098
# 0671bbdbe1964916950d7b8caa0e946c
# 332649341d0347258c36b9133f7af4bc
# 2a3d330c35734ee38d67db67d61acd40
# 43dfdd4ceb6440bc8cf4f42f740f070a
# 872990e2700c447b85d50faaddbee624
# 7c8cb3c7cfd645cfaae919a65ac6d401
# e873e349783c4fd3b45c3f7e0afb5b97
# 7816d5984f8d4657bef880b4c7f5e242
# 1e62d6d20a4e498ea9be8ff7f5702aa0
# 86c804ee764b4194bf4fd608e2d4ed42
# 57cfe75bfcc540f7900945f42d77b31a
# 1e74cb35c9814355b89c72c0f144b20b
# 7fde3afed63142dca334254910f137b2
# 7abf128f5eb94c14ad5694001a378531
# 14ff04cf0fcd4ca792f10c1b28d37f55
# 9cf5fb041a9b4ec2b28948ea9eb57e69
# 8cadba196c614c6981fdc528ab5cf400
# 469e2860c02c4e3c8e8f4c3edb601031
# 7693bbed4852403c869520b205856bba
# 349fcb17003e4078a35e05170d98e4fc
# fef525f4f0a9466199ff33cd641ab12d
# f63380d77eeb46d2b034976483db3bc6
# cfc74c41619643c1b86f2737a32d0353
# fd4270e638c842fbacbb8ee30a8a57f3
msgid "Execution example::"
msgstr "Execution example::"

# faa46e62122b420c9fbe1d7581750b6b
msgid "Tutorial"
msgstr "Tutorial"

# 0f7c25e5bb75457c8f809db9a5fcd7ad
msgid "Various data types"
msgstr "Various data types"

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

# 0a6fb50aa02042b1bab64a5351af4908
msgid "Overview"
msgstr "Overview"

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

# 48264d88409642b18b49d739c85e5887
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."

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

# 2dbda310d3bb46e8bb8efe2721436a7b
msgid "Boolean type"
msgstr "Boolean type"

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

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

# 85cd030f0c28486a80a4c0448dc74d24
msgid "Numeric types"
msgstr "Numeric types"

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

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

# d121caad35f44ac2999dca822947847f
msgid "String types"
msgstr "String types"

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

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

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

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

# 515f1a2d62f141f2b56d1c50a2b7fc11
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."

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

# 6e2a017c3cdd4e2a8abd23932e218156
msgid "Longitude and latitude types"
msgstr "Longitude and latitude types"

# 36f4023263254f0c8481f566ce888281
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:"

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

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

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

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

# 11a95914555742a68d11c3fafe1b267b
msgid "Reference types"
msgstr "Reference types"

# 111ca9f952034335ae9177f217a362a2
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."

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

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

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

# ac2b5513522d4b8da1a0008e171e89df
msgid "Vector types"
msgstr "Vector types"

# 7927ad1384874b8d9dbcb349c8899a4f
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."

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

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

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

# 6ec376b78e034c2b926ffbcdb61ebdf9
msgid "Drilldown"
msgstr "Drilldown"

# 3308f56f74a04f0d9fbdf325552bc1f8
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?"

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

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

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

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

# 81757a59426f4d459f9e592e003cd27c
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."

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

# 393b3e1bcaf243cb8f4d85642ba5e57c
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."

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

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

# f64c4ae4339f48d7bfabe86057c95a27
msgid "Group by"
msgstr "Group by"

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

# 18f1ceb5e2484c16a9cf792f223a9b51
msgid "Group records means following records"
msgstr "Group records means following records"

# f27dcf17acb54881828528f9806d809f
msgid ".org"
msgstr ".org"

# 4c16307ed8f5478c9f23a06558a003fb
# 5ef48b43041842ee96bef761b5568642
# b473ecc2322445c49939add64bd19ddf
msgid "3"
msgstr "3"

# 8e3429b351cf48968ee1d2574a31f023
msgid "http://example.org/"
msgstr "http://example.org/"

# 84a5f6c94f5941dcadb523eb96073efc
msgid "http://example.org/aba"
msgstr "http://example.org/aba"

# 54cf2723bd1f4498a6590e795d986a50
msgid "http://example.org/gat"
msgstr "http://example.org/gat"

# 2093e3c08cc940a790be58c417d1593b
msgid ".net"
msgstr ".net"

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

# 482d8c6454dc49e490942625a9a96cb6
msgid "http://example.net/afr"
msgstr "http://example.net/afr"

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

# 463d93948ee34e94aba85341820ea29b
msgid ".com"
msgstr ".com"

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

# 376ea1813ca54b31a60a86fe87d21328
msgid "http://example.com/rab"
msgstr "http://example.com/rab"

# 134a2621c8664ffda4bb88716abdeb77
msgid "http://example.com/vdw"
msgstr "http://example.com/vdw"

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

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

# 721778cdfc504966ace590ccc4c71c93
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."

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

# 10a7eb682f904c9c9d635f369685e2a7
msgid "Drilldown with multiple column"
msgstr "Drilldown with multiple column"

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

# ff1c1cae984a43508f644ffbd4b82af6
msgid "Sorting drildown results"
msgstr "Sorting drildown results"

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

# 33e344c7741d47d38c22d0ef97c72855
msgid "limits drildown results"
msgstr "limits drildown results"

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

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

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

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

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

# 56fb6dc71ecb41e2a57896c751deadde
msgid "Tag search"
msgstr "Tag search"

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

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

# 37840b17f8904d14baee5353d20b0d95
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."

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

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

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

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

# 2c37f843458b460d98ababf15ca21d92
msgid "Reverse resolution of reference relationships"
msgstr "Reverse resolution of reference relationships"

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

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

# 3223ea4f1e0a4c8e9d3f35b803b87ddf
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."

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

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

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

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

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

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

# 0de1c8f35da44e23a8314b67acc9466a
msgid "Basic operations"
msgstr "Basic operations"

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

# fec46a22ffa84b469246933f06366227
msgid "Create a database"
msgstr "Create a database"

# 0612da385d35497cab1dac4c46e77a03
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."

# cac26861586246439a8862b63c9ff92d
# bec42afdfd3a4d4b90b40d0662339b59
# 1e61c88153de4c7091f6a98de4911dfb
msgid "Form::"
msgstr "Form::"

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

# 551bda4118bf483bbb8b15cadd332620
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."

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

# 9a6d7223b0764368abc73f6fd2a7a932
msgid "Operate a database"
msgstr "Operate a database"

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

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

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

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

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

# 7a7788af7a1f4ad68b8f2f762740fde6
msgid "Command format"
msgstr "Command format"

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

# 8209160d73554f599e6f86efed352934
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."

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

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

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

# 2540d7485f6a4db1b3d7bf7de360d749
msgid "Basic commands"
msgstr "Basic commands"

# 95e67c8fe7d74994bebaf3905c8a2fb3
msgid ":doc:`/reference/commands/status`"
msgstr ":doc:`/reference/commands/status`"

# 51b2d0cf6a274e35ba6d7a9b41eab524
msgid "shows status of a Groonga process."
msgstr "shows status of a Groonga process."

# 84cd43ee0e4d43eea66f10f722a35290
msgid ":doc:`/reference/commands/table_list`"
msgstr ":doc:`/reference/commands/table_list`"

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

# 6803dad77f654f208c8863a0f7169de3
msgid ":doc:`/reference/commands/column_list`"
msgstr ":doc:`/reference/commands/column_list`"

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

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

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

# 400970e8f5484ffdaebab11b782957ce
msgid ":doc:`/reference/commands/column_create`"
msgstr ":doc:`/reference/commands/column_create`"

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

# 5c09411a459f47e7895d528fe1e46efb
msgid ":doc:`/reference/commands/select`"
msgstr ":doc:`/reference/commands/select`"

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

# 2c870de61d584569b95b1235b8047ca8
msgid ":doc:`/reference/commands/load`"
msgstr ":doc:`/reference/commands/load`"

# 05daa78c79a54c66aee24b0f3aeccfbb
msgid "inserts records to a table."
msgstr "inserts records to a table."

# 8d6f6cb3197a4fb1894735e744493ab0
# 0ff759a33a0540b1a1f85c1eafcca717
msgid "Create a table"
msgstr "Create a table"

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

# 197824d1234e43be87f5f005484bb8d0
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."

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

# 89607bda9e664f4a906e235eeaf49647
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."

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

# 6f0f87b03e4b4e68a4c501f76595fdec
msgid "View a table"
msgstr "View a table"

# 40a133375ecc49c0b16cf5a6ae94199d
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."

# 18f2ed6032264f5b9a6a16d932e40a36
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."

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

# 4ca349b7cc094d08a4444916a6731ca2
msgid "Create a column"
msgstr "Create a column"

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

# 37599bc441c9418eb4ee350db5b54d53
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."

# 69a3a52c6f2b42bda77f226c292013ba
msgid "Load records"
msgstr "Load records"

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

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

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

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

# eddad64031af42a499b3e0d2202173e6
msgid "Get a record"
msgstr "Get a record"

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

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

# 41828a5b875b49929eb0f6623fa80775
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."

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

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

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

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

# 2655794dff4f4d19806999b98b8d1745
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."

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

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

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

# 4438b7e8ef8346dc868e71fb37d842a5
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."

# 767e6e491e2d44abb9e7b26d3742318f
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."

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

# 89fd50ebffb54ccca8a59b171c90ac81
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."

# 379083e65adb49788bee85a220f649b6
msgid "Full text search"
msgstr "Full text search"

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

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

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

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

# 50096864be484a76a072f350fad49f0f
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."

# 970d42d5ddbe43aa9e9e185dd716948d
msgid "Specify output columns"
msgstr "Specify output columns"

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

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

# fdfe353afab9458bbf03b221a40cd9a3
msgid "Specify output ranges"
msgstr "Specify output ranges"

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

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

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

# 69ca538fe9ba4103b48ccac1a1a3540e
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."

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

# 342791003de34e4a8974292e2b58c2bf
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."

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

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

# b6e1b309c0d84ed4867762ccef0a1e80
msgid "footnote"
msgstr "footnote"

# 3135eb3387914202b324c26ba6dd3923
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."

# 28f4859ee5314707ba16362a6c51065f
msgid "Additional information about lexicon for full text search"
msgstr "Additional information about lexicon for full text search"

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

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

# 14e140489efc46f4964a4e336ef57895
msgid "match_columns parameter"
msgstr "match_columns parameter"

# 72b7f928ef294bec98f8610b4f033d38
msgid "Full-text search against multiple columns"
msgstr "Full-text search against multiple columns"

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

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

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

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

# 91901cb744214534afd11fd166cdf258
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."

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

# 9873abffaa0a4574848c9036f708cbb8
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."

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

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

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

# 091918c84a214afab8395f4496ee290a
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."

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

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

# 2781653a794b463298d8e37c62536919
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."

# 525d26a35f894eb786fcfe6ec69bac88
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."

# 14ee43a23e174eb488e9d494fd153116
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."

# 94b0557cc5864834b8c6762d59846408
msgid "Full text search with specific index name"
msgstr "Full text search with specific index name"

# 9651ccf759db4bf997c54f0687cbc601
# 2cbcb2464e574440892a3190e8b49b44
msgid "TODO"
msgstr "TODO"

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

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

# 3f73e2e4ff724e99b8a6a0b6fbd03024
msgid "Here is the concrete example."
msgstr "Here is the concrete example."

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

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

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

# 947ff15fb94c4eb69106a00b448b2f96
msgid "Here is the sample schema."
msgstr "Here is the sample schema."

# 75c609566e1047a18e632e2b9ede17ad
# 74a1139fa6d44bdd99013ebe4388f7ab
msgid "Here is the sample data."
msgstr "Here is the sample data."

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

# dc0fb261f8be44949318b851f4d87b20
# e2f2f19b16684bdeb888b37e433430ba
msgid "Query for searching the records described above::"
msgstr "Query for searching the records described above::"

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

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

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

# 14070d9745de47599faa4bc371a442f5
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."

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

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

# 03111cd3915b4c03809e85ea70ce9e1b
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."

# 270c564199b94263a29ff0a8e6f14b2a
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."

# cd265ee024ea40829aa6373cf154fdb0
msgid "Indexes with Weight"
msgstr "Indexes with Weight"

# 30579e87c35941e29ecf6fde67a3e85c
msgid "Let's create micro-blog"
msgstr "Let's create micro-blog"

# 82538fd761714dc5a6d71208476cb543
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."

# 7cf077f6c830432cb86c9016b1a7fb19
msgid "Let's create table."
msgstr "Let's create table."

# 2fdea3077c8340f593f477bab8758ed2
msgid "Users table"
msgstr "Users table"

# 94804e58c7d54e8b95058310993ec48d
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."

# 8aef1acc489f476ab7e1c48b8177911d
msgid "User ID"
msgstr "User ID"

# a3583bfbb55b4c78bd6c0a12ee09bd47
# 98272c5fd3c94e9cad06e3ace4bfdca4
# 06e1f95383e44291b9f30fc7f52c41a7
# fbf5829e367d4a1c8896c4293bdaa05f
msgid "``_key``"
msgstr "``_key``"

# 71ba1b80a4ee4df0a9f745a1d2859572
msgid "User name"
msgstr "User name"

# 85a95288c0094596b8f8aa7bd05b240e
msgid "``name``"
msgstr "``name``"

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

# 144702e95b204a12b55c8af8314b0031
msgid "``follower``"
msgstr "``follower``"

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

# d7649230e98a4eb29589892c15639930
msgid "``favorites``"
msgstr "``favorites``"

# 65697d6c4702481d8cb4bc3f31be59a7
msgid "Current location of user (geolocation)"
msgstr "Current location of user (geolocation)"

# ae496bee35fc484390ffa142c0f2ce79
# bc4d1724648a467e971425b99c261a0f
msgid "``location``"
msgstr "``location``"

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

# 1abd304acbf94817a6ccb7ccdcba2ef2
msgid "``location_str``"
msgstr "``location_str``"

# 6113839256624d1297646a7603cd3a3e
msgid "User profile"
msgstr "User profile"

# 50e8f4e97f1e4b30b8bd0aa769518cdd
msgid "``description``"
msgstr "``description``"

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

# f10d091f6d64465dbb66e1cb5dc1d25f
msgid "``followee``"
msgstr "``followee``"

# cba6cc5e481e4980a03908d520742337
msgid "Comments table"
msgstr "Comments table"

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

# c89ef6bdf29749ac97af69ebf974a599
msgid "Comment ID"
msgstr "Comment ID"

# 30e653c0ba1d4867868965bec1ef7cf4
msgid "Content of comment"
msgstr "Content of comment"

# 2a1b8b1149cb4f60907ea188034bcdb7
msgid "``comment``"
msgstr "``comment``"

# 9b062973151a43a497685e05d9edf6d8
msgid "Posted date"
msgstr "Posted date"

# 20c1d5ca9b1a4b04813b831fde6fc700
msgid "``last_modified``"
msgstr "``last_modified``"

# 8a4aa4de8ef248ef82383e14d8f1bd76
msgid "Comment which you reply to someone"
msgstr "Comment which you reply to someone"

# f44e3e607c2c420cad13824711fe31a0
msgid "``replied_to``"
msgstr "``replied_to``"

# 420accb0d3f0482fa5fb524599e50a7f
msgid "List of users who you reply to"
msgstr "List of users who you reply to"

# e7dbd6fc52534acb902f0d6f43a31399
msgid "``replied_users``"
msgstr "``replied_users``"

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

# 0a75cf0e187d4d1ea14ef321a19ad613
msgid "``hash_tags``"
msgstr "``hash_tags``"

# 891ef72012dd447992db656fcd29c650
msgid "Posted place (for geolocation)"
msgstr "Posted place (for geolocation)"

# 535201b5a9c94a479ee3a5a537a44bfe
msgid "Person who write comment"
msgstr "Person who write comment"

# fc31b58037ca4c979045e68c5e9bcef5
msgid "``posted_by``"
msgstr "``posted_by``"

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

# 9180e5bcdc6b41808b075a21fe9e6196
msgid "``favorited_by``"
msgstr "``favorited_by``"

# 1d15b840dfe24a118076e394f664ac41
msgid "HashTags table"
msgstr "HashTags table"

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

# cac2933418aa4eb79779f7847081ea96
msgid "Hash tag"
msgstr "Hash tag"

# 09e13f04b078477486392cd8c042757c
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."

# a9414ad2d2c74962b8576dca33fd20b9
msgid "``hash_index``"
msgstr "``hash_index``"

# 46e2f608ef024ab19a0d71cc8003a625
msgid "Bigram table"
msgstr "Bigram table"

# 791743d1b69745f096f94aecbd6c7002
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."

# e387db9d5621485083b6f4eaa1a59065
msgid "Word"
msgstr "Word"

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

# 136b63c8a3ce452e9ae6cb05e2a4f918
msgid "``users_index``"
msgstr "``users_index``"

# 3b977f910e184864ba7eaafd74dc141e
msgid "Indexes about content of comments (``Comments.comment``)."
msgstr "Indexes about content of comments (``Comments.comment``)."

# fc327b3ee4bf4398b8431815217793d0
msgid "``comment_index``"
msgstr "``comment_index``"

# 31678633a9b54a6d9d9804ad0e56334d
msgid "GeoIndex table"
msgstr "GeoIndex table"

# 221f3893d6c34838b4faa590bab8616a
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."

# 4555f5e34b8349a1a4cc1455c302a1b9
msgid "Indexes of location column for Users table"
msgstr "Indexes of location column for Users table"

# 8fd703660ad0405a9afa9a322374ab65
msgid "``users_location``"
msgstr "``users_location``"

# 5ece3265d70548eba1dcd5cd385c803f
msgid "Indexes of location column for Comments table"
msgstr "Indexes of location column for Comments table"

# 36992a97ab3c408f8a5d4b94593a761e
msgid "``comments_location``"
msgstr "``comments_location``"

# 48f6f75f9d4d4648a21655038b14b987
msgid "Loading data"
msgstr "Loading data"

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

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

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

# 33a1d0f66f73431abcc0cf3126b8e53c
msgid "``last_modified`` column in ``Comments`` table use Time type."
msgstr "``last_modified`` column in ``Comments`` table use Time type."

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

# 3cfda92a75864bfb9236b6ead0ed2be9
# a2e121a4fefb432b977093e2b32949b1
msgid "Search"
msgstr "Search"

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

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

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

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

# 820eedeb71f0494d8e3c6dface2d1a71
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."

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

# 11906789f8744a1f93dee4116d6d6d57
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."

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

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

# 54587fdc225040d98edd0d6ef14084e5
msgid "Search users who follows specific user"
msgstr "Search users who follows specific user"

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

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

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

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

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

# 457caf3c4443426282ddcae7db5aa2cc
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."

# 27262c636e624fdeaa08d882f3adfc47
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."

# 6948ae702ede4f839d3d54aa8f5a2cba
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."

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

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

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

# 1ad40af690724ef29f847d2040475bf3
msgid "Search comments by keyword and geolocation"
msgstr "Search comments by keyword and geolocation"

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

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

# c78754700e0e46bea2efbb5027cb764b
msgid "Search comments by hash tags"
msgstr "Search comments by hash tags"

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

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

# da17a19b78de4ce6991d0da28380a83f
msgid "Search comments by user id"
msgstr "Search comments by user id"

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

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

# 2616d3de739a4d43b9314fe8e2863fa1
msgid "Search user's favorite comments"
msgstr "Search user's favorite comments"

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

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

# 7f5e123ed58c47dfa1a06f9bc8c33830
msgid "Search comments by posted time"
msgstr "Search comments by posted time"

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

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

# 26e37de5dcd3488e98dbdbca1a6c3b33
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."

# c52a58fd40694927870ed13520457333
msgid "Remote access"
msgstr "Remote access"

# 6251c23e06be4e3c9f68769545d1c9ab
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."

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

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

# 65f77d2c9e684babaf27067b2e1dfd9b
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."

# 29d93261422e417d9c1c88b0e19afc4e
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."

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

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

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

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

# 747fa3e85d8e41dc91aae34c56b76d30
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."

# 6f0c2d4c45864f7b90708647af3f3043
msgid "Administration tool (HTTP)"
msgstr "Administration tool (HTTP)"

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

# 381c2547221e465286ca9e0f9b520154
msgid "Security issues"
msgstr "Security issues"

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

# 9c0c9c0586b245bdb10f91f17e82cbc9
msgid "Prefix search with patricia trie"
msgstr "Prefix search with patricia trie"

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

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

# 2e170a9a560b4ee2ae84544729e52351
msgid "Prefix search by primary key"
msgstr "Prefix search by primary key"

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

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

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

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

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

# db72f2eaacd24e7da173c858fea77333
msgid "Query expansion"
msgstr "Query expansion"

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

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

# 7c4c3aed886f4e84a4214b5bf377e20d
msgid "Preparation"
msgstr "Preparation"

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

# 015ef50ada484e43831c2a05fce241ef
msgid "Let's create document table and synonym table."
msgstr "Let's create document table and synonym table."

# 333595ba0e7444988d2f0aa3989e7605
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."

# 3536900c6acb4118945a7c077ceabef1
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."

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

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

# 815e9f17729a4fee9039c08df17bbd43
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."

# b3c15d8b85ec43fdbb482cdea9d9014a
msgid "Various search conditions"
msgstr "Various search conditions"

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

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

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

# 51083b61c12545ee83a87350e5759bb0
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::"

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

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

# 732ccc863e5b4c9a93fb529d2e803c21
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."

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

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

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

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

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

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

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

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

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

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

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

# 05088bc587ec4a68b0e41d9f7c2a18d1
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."

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

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

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

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

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

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

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

# 8070a7c251a94a399b10665e76252d34
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."

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

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

# 29383cb764244688a6b29067e36efdd6
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."

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

# 442255ad61bc401aa5aeae4bcd3ec9bd
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."

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

# 83002cff03494137be1678c83dfced6e
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."
