# -*- 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.4\n"
"Report-Msgid-Bugs-To: \n"
"PO-Revision-Date: 2015-05-26 11:04+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"

# 8950c151864b479b9b5fb9f7163505fb
# 7a32b98b5fd243b3a546dfc9c1c84aec
# 273334f786d54840a3eb25f466dc95b1
# 91f298957f1b446eae0269e26dc61127
# bd757ab0f4e04f9e84388a9987a92786
# 49e98b4553d04fdd8381ca172fe6d08f
# 3cfce7ad9da143589237d4fc6b5967d7
# ff509a4e5d20472cb44be60d5a648ecc
# 4341269245ee4b0691f5cb714eb46d52
# 38133074b75d4cfa8c5c4e6d9558c682
# b9657f1bc4cc4c16aeb37f00efd1e3aa
# f384325109824dfbb2ad79aa465039f9
# 7e0e491ce73346148e7df4f842594a47
# 731f5d6765874d178765a6ca64bc6fbc
# ee70511048054287ace210b179a42bd2
# 480c956f7f954a79bbcb1e61e13c1f93
# 5a237787a3ef4b4f8bf93b934f4369c5
# 7fe92b8d52524cffb0fb2425a0c31f79
# 413d2c2f0882492aa508a70039aaa1ba
# 9f4685d1acc942eb8bf6db340b2cf195
# 05e22b4b994e4c269bfba90a39bd43bb
# e49e160fd4594a42bca36a2aa98fd00a
# ca03e6eeb3414bfb97a6bb0e0ded860a
# 6fca7f0c0e0e4346ab92660801b09312
# 853bbe88f82c4a9aa51d50f1418e483c
# 1fd795de9119481cb580eef11ef0375e
# 1cefdea1f3dc4b7ab9eeb4a41be8e38f
# 9d10ac77b3174b77810837de0100c977
# ae4cfdf69c584743ad4a51f3b58fe412
# 138e8c91aca343438e6290e87d8f46d8
# ad6a213fc87c425789d0ce9e0bd30ca9
# d262f5ddf97140c39991bcf2912513a5
# e59b782b20254af88d98020819f23f2a
# 26fb8cebfe0b4348a5828e511d0c27dd
# d44e75fbe231499cbd6090c7b13e6c53
# 769bfa51b72143c5b98e1dabfd92ff9b
# d3adf9745b5f4d8e9e6c11cd5bf0ba24
# d59d151f9e7144f1b7386f048bbd6b78
# 186fbc3d4ba24ee58e8068e25ae82c60
# bf58a17597804db28e3200001946ad61
# 4c886192534a4b878eb4a7951335448f
# 14e5c8ee9ca34a23a6e3fb6da378f051
# d77f83d130bf4e30aab03a96f3490e7e
# 2c4b66cf73ba4150b4f63655b8c9d830
# f22b109c28e04347a11d73b160dc054e
# 0ab3af2f9b8a427795ed86fc4b5a62f3
# 54a3ea6c32124d1cbebe61e2f84317bf
# edc0177af8ac45f882d5f92637cf6165
# 8db221627d0b44b8b69b2ef20a64ce2a
# cb60b503a9d74eb9b3b0d14f87e7137f
# f4ceb4a80d654bebbab0f58992d3a4a9
# fa02691db339458cb2b6685feded22ce
# f8ed868487074485b8e2ebb93efbd1e0
# f966e4446ced455493c147c779652d77
# 8f6e7789d2bc453d9f805552a126b83c
# 5b741884a1d94846b08499a31e84845e
# b6f0f013f97a445db26027040ff17aa9
# ef59031cd52a49f29369fda2b6cc464a
# 6c99e761d15a4a1386f31010571d3b90
# 9ce9abbc2a194f65990e098761bf7d77
# aed0f93f60f54d9c9892d52691fa7ed7
# 54344fa2b2b6471d8f6e2e5b2300bb9d
# 75925a1dea9a43798fc941f85edb02fc
# 4a611718cc234361a2e928837017c052
# 2b58f8523e324958b1dd1323c529273b
# 96c5922843f848278a50b3396234f653
# dda52e17093f444d87e61ce065da5440
# 6074b44c3bf64f14a350ec49b9d72ced
# 5c5f224099ef4ba593ddca71f2070704
# ae7af3b2c96a4b1a88aee695872e8c2b
# 0db339105b48493ca21266876d99b5b4
# 6e4715292fbf42d3a140293d603b2c0d
# 9be6e53e10834a978fafc3f973891ce9
# 26351fb9e55b4125a7285844ca65b6b0
msgid "Execution example::"
msgstr "Execution example::"

# 46f1325170b64ac98aae7724b2ab2ea6
msgid "Tutorial"
msgstr "Tutorial"

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

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

# 509949cf43024339838a75e9abcb5f6d
msgid "Overview"
msgstr "Overview"

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

# 19385e00500d4e9c8f3f5d95319fd681
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."

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

# eaad9957817b4a1db95bb872c54cbb1e
msgid "Boolean type"
msgstr "Boolean type"

# 8687f565b22c4f659814e947baf05d3d
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."

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

# 5d2ae9400c93498b852013fb3b85be5c
msgid "Numeric types"
msgstr "Numeric types"

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

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

# 8471435368204fd0806009729dbcfc0e
msgid "String types"
msgstr "String types"

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

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

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

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

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

# 8559a3c4e4334bbfaf0c74320ff5f292
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."

# 4886ccff146946b6aafc41480e94c44b
msgid "Longitude and latitude types"
msgstr "Longitude and latitude types"

# 1b5352c0592844ed8102b00e1e6cbc20
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:"

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

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

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

# 040df12fcca3473f85490012aa6f8d76
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."

# 1273f0101f194e34949ef65585fdd28b
msgid "Reference types"
msgstr "Reference types"

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

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

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

# 487eb6167e01485898e9ce4560fc356f
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."

# c732bbfdca084b86aa617bae110531d3
msgid "Vector types"
msgstr "Vector types"

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

# 5884c833418b4afe8cc4637f80febc47
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."

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

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

# 2c54c40456754db394fa3ca2816174c8
msgid "Drilldown"
msgstr "Drilldown"

# 8dd8d99ac57347809eb99c9cb2a521d9
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?"

# 16b4988bb8744435a89d7e5e0a12fc22
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."

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

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

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

# 37b2f5e1096a4e739d84f276c7cef02d
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."

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

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

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

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

# 71bc3f6b98204451a73e8e34fdfb683e
msgid "Group by"
msgstr "Group by"

# 7a4cbca1202c44d79e2330209d188f63
msgid "The number of group records"
msgstr "The number of group records"

# 5c92fee83d3e4cd99b1fab66160bf3fe
msgid "Group records means following records"
msgstr "Group records means following records"

# c5d8df6b1360404caa47135cd3faba45
msgid ".org"
msgstr ".org"

# fde6e67f7f76464fa343e06d5f159be5
# 7361349f5ca14ec8b14b29dc1682eaf0
# 5835eaeefff048469fa07a5a781c6d01
msgid "3"
msgstr "3"

# 33f3cd50afd549c9bfcb41d0ef4545a6
msgid "http://example.org/"
msgstr "http://example.org/"

# 3f70c948c2694758a5146412e1ba5ce2
msgid "http://example.org/aba"
msgstr "http://example.org/aba"

# 10c920355b8c486d9d20709acf7d21c1
msgid "http://example.org/gat"
msgstr "http://example.org/gat"

# 741973cd91324115a8d6a23a65ffbadf
msgid ".net"
msgstr ".net"

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

# 9d704256414747818845804e0443a6e0
msgid "http://example.net/afr"
msgstr "http://example.net/afr"

# 3887e96b083147f4bc1f30cfa5bb65ef
msgid "http://example.net/atv"
msgstr "http://example.net/atv"

# 42364faed7ca470eba633434555e6e5c
msgid ".com"
msgstr ".com"

# 7948dbc6d4f943438fb99897d0ef389d
msgid "http://example.com/"
msgstr "http://example.com/"

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

# 2463e93985284a55b127341a42558b2d
msgid "http://example.com/vdw"
msgstr "http://example.com/vdw"

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

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

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

# 70fbd9d573ac40f1965a5c279af68ced
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."

# 2d3c0c91d7c84e74a565909f46295b02
msgid "Drilldown with multiple column"
msgstr "Drilldown with multiple column"

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

# 1dc785ce919946ca8ee8f4131abbcf16
msgid "Sorting drildown results"
msgstr "Sorting drildown results"

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

# 4c9527e6bc284096bb56157b66746065
msgid "limits drildown results"
msgstr "limits drildown results"

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

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

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

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

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

# 6a3d35d11e4d4415adff88b5a8c41f3a
msgid "Tag search"
msgstr "Tag search"

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

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

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

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

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

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

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

# 73e178c258784f0bb5f941b099357bde
msgid "Reverse resolution of reference relationships"
msgstr "Reverse resolution of reference relationships"

# 336b4738ac3d46fb9de82f1b7c910a6f
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."

# 9570c711b5d74059852185782639cc1c
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."

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

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

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

# 314dcd49d1a44775bdb79d70836bc722
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."

# 15962dc380af479ea8807675a2a9c4d8
msgid "Geo location search with index"
msgstr "Geo location search with index"

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

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

# 49a87c608607457ca329d1a4639aeaa1
msgid "Basic operations"
msgstr "Basic operations"

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

# 9e16fd6e1aef4cb28f988ff77fab259e
msgid "Create a database"
msgstr "Create a database"

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

# b80b10df3db14cd69a4053c3fe045d39
# adb1888f1f26488dbf14f72d39008340
# eb52bb5510044b97b76ca470ca57b853
msgid "Form::"
msgstr "Form::"

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

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

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

# 8daa5f236833444fba89d86357919e22
msgid "Operate a database"
msgstr "Operate a database"

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

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

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

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

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

# cf3ef7fb086a4dff86f81f5c5114d6cd
msgid "Command format"
msgstr "Command format"

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

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

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

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

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

# e256612d06844c4795a4ffa2dd6e8a8f
msgid "Basic commands"
msgstr "Basic commands"

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

# 600000315af94c42a6c1c9cc40543ae9
msgid "shows status of a Groonga process."
msgstr "shows status of a Groonga process."

# 55679f0b168e42459a1a4a0f1d1f05c1
msgid ":doc:`/reference/commands/table_list`"
msgstr ":doc:`/reference/commands/table_list`"

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

# 39f25f4e1a4c44bdabc0b93cc4a91c5e
msgid ":doc:`/reference/commands/column_list`"
msgstr ":doc:`/reference/commands/column_list`"

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

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

# 8494dce7ec9f4db99f51002def8cd6a3
msgid "adds a table to a database."
msgstr "adds a table to a database."

# 228eb7ff183746169770d845de471422
msgid ":doc:`/reference/commands/column_create`"
msgstr ":doc:`/reference/commands/column_create`"

# 3d788829645d4c79a10b22bf9319bcc4
msgid "adds a column to a table."
msgstr "adds a column to a table."

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

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

# 23b2a7a42e81481c9f56b11cf881caee
msgid ":doc:`/reference/commands/load`"
msgstr ":doc:`/reference/commands/load`"

# d9cb74f3c68142dfb39c0e01f76810d2
msgid "inserts records to a table."
msgstr "inserts records to a table."

# 3bd16eee5ecf486180c8210f716433be
# b80f29c560cc43ef96e5df24e1aec011
msgid "Create a table"
msgstr "Create a table"

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

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

# 25262229904b4f278c9a6ad430c3fedd
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."

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

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

# d1d6613caa854eaa98b2d93eb5594a86
msgid "View a table"
msgstr "View a table"

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

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

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

# 417fa56895694245b67a2efd6f372238
msgid "Create a column"
msgstr "Create a column"

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

# 337481cd1aa34ac9929be14321b938fb
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."

# d1ce173929e241fe9240e8daace50b7d
msgid "Load records"
msgstr "Load records"

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

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

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

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

# 8203a51697094d139164e5458a27976e
msgid "Get a record"
msgstr "Get a record"

# 1508a6a11c95466b9b1e80eec4a74a97
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."

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

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

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

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

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

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

# 2183d1d510c346e1b1fe73692811c388
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."

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

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

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

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

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

# 25ffe340ef1b492789a3468d7e65c0b2
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."

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

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

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

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

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

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

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

# dbf537d67aa94a1290a8fc9852d68326
msgid "Specify output columns"
msgstr "Specify output columns"

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

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

# f5f6ca4c1da7423e9878f193b67e4145
msgid "Specify output ranges"
msgstr "Specify output ranges"

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

# 19c3acec9be34a64ac526c3423d76e7b
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."

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

# 677c209a6a5f4555b7b75ed958872699
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."

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

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

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

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

# 753ae29064d84fb893c8f0e68a9b3f7d
msgid "footnote"
msgstr "footnote"

# 76571839b3f44501a7a0119b0df04280
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."

# 80b2a613205b455f9241ff9b74660e7c
msgid "Additional information about lexicon for full text search"
msgstr "Additional information about lexicon for full text search"

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

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

# a54ffd4309f94e28accff06be649212a
msgid "match_columns parameter"
msgstr "match_columns parameter"

# 50dbcfe0cd2a41eea7daecf5d48c9ae7
msgid "Full-text search against multiple columns"
msgstr "Full-text search against multiple columns"

# 63afa443da3d4abab79d97b34a61b430
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?"

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

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

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

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

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

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

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

# 0030f6f61505453690900f1c71821c82
msgid "Creating one column index against multiple columns"
msgstr "Creating one column index against multiple columns"

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

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

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

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

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

# 001f51eca748453a8ee8d8142a43b204
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."

# 861cc1741d66451f8bc05b5cc9bc2ae5
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."

# 699f9040822147dcaaebcded18e04a0a
msgid "Full text search with specific index name"
msgstr "Full text search with specific index name"

# eb3e1093e33d416bb85c723d3d1e04db
# 8cc4781dca5b4e8088490853653da560
msgid "TODO"
msgstr "TODO"

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

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

# 57c28f8f57034d329db72178bebb759a
msgid "Here is the concrete example."
msgstr "Here is the concrete example."

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

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

# 3487ab413dd0443faeda8ad336d14fb7
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."

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

# 220462e248924298b1975d297a04d6b8
# cda173e0e8574f11974bad114b282876
msgid "Here is the sample data."
msgstr "Here is the sample data."

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

# 22fb6239a5a64971b58f51846f55ec73
# 229c58c6dfb248f6a3b7649b53fd5fd3
msgid "Query for searching the records described above::"
msgstr "Query for searching the records described above::"

# 3481de7f90e0428384da4c9b283ffacc
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."

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

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

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

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

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

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

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

# bede87a7550841a79b300c5d211c4c58
msgid "Indexes with Weight"
msgstr "Indexes with Weight"

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

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

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

# ad2e1e74bd7d4bc192d0cbf393c06d0c
msgid "Users table"
msgstr "Users table"

# 660693d1267b4f87821ca8e4ad66ccb0
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."

# accbd01a598d47b886a429ac7776e4d0
msgid "User ID"
msgstr "User ID"

# d3ff61103fa54dc2b649197d7256df69
# 7adbcb88c277417fb869fb20334dab3d
# 7b955cd502d441d2b4b8be02048d0ccd
# 605e577a0ef9463a9606e06d6a95f918
msgid "``_key``"
msgstr "``_key``"

# 41944b87986c4c599fca2073639dac79
msgid "User name"
msgstr "User name"

# 8af095fa62344190a03e2dc24785f08f
msgid "``name``"
msgstr "``name``"

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

# 2fd3229a37584e389f85d213d38cdb0f
msgid "``follower``"
msgstr "``follower``"

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

# 30946142a05a4ed6860c39666ac76bef
msgid "``favorites``"
msgstr "``favorites``"

# 44ea085f72ca4eb0ad77b9738ee426ef
msgid "Current location of user (geolocation)"
msgstr "Current location of user (geolocation)"

# 977f201b25a6470890df7645ace66027
# 4c987d0c672b47449d20b17afc3be406
msgid "``location``"
msgstr "``location``"

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

# 94dd381cdd7949b5a4db12df06fc6878
msgid "``location_str``"
msgstr "``location_str``"

# ec68b019a61f42a983f681681860b2e0
msgid "User profile"
msgstr "User profile"

# 955a090d30ec4ae09cbf5a2247f204ed
msgid "``description``"
msgstr "``description``"

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

# 9756b5c1567a4f0db8c5e8f748fbf48d
msgid "``followee``"
msgstr "``followee``"

# 314e31758394456496f4911e5fecb621
msgid "Comments table"
msgstr "Comments table"

# 784b9d5184a347a9ad81c0ec6f5afa9a
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."

# f9b7644a7aba4a74b7149ac9587b282e
msgid "Comment ID"
msgstr "Comment ID"

# fc23035f6bec45449fffdd9795e0c5bf
msgid "Content of comment"
msgstr "Content of comment"

# 81905aedacf94eaab625fd8d622b9885
msgid "``comment``"
msgstr "``comment``"

# 10a7fc48a704449c93a480556c1af2c7
msgid "Posted date"
msgstr "Posted date"

# a50f953b3f6f4f8d9900d550a21b7bd7
msgid "``last_modified``"
msgstr "``last_modified``"

# 2e8637188348401c980dc1aaff2b03a1
msgid "Comment which you reply to someone"
msgstr "Comment which you reply to someone"

# e1b3033bd1ef4a55938c77676c7228c5
msgid "``replied_to``"
msgstr "``replied_to``"

# 8f685d31563b4144984b91ce6a6d655a
msgid "List of users who you reply to"
msgstr "List of users who you reply to"

# f43aba97e0ea4a9f9456ab790dc3d788
msgid "``replied_users``"
msgstr "``replied_users``"

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

# e6f7b0dcd4224db08885de869db48578
msgid "``hash_tags``"
msgstr "``hash_tags``"

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

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

# d51e8f09d7ef473b88c0ff9868f899b4
msgid "``posted_by``"
msgstr "``posted_by``"

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

# b5e5f6b76a6f417eb7263d92f1d4ccd4
msgid "``favorited_by``"
msgstr "``favorited_by``"

# 31a3693fd5ef4fe791be88eb08e9a40d
msgid "HashTags table"
msgstr "HashTags table"

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

# b94dcf53af35480783604d8105383055
msgid "Hash tag"
msgstr "Hash tag"

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

# 2c9bf1e3e68e4ae083c8bad3d6e38ed4
msgid "``hash_index``"
msgstr "``hash_index``"

# 87d968fcae05485d90439fb868456f87
msgid "Bigram table"
msgstr "Bigram table"

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

# d1b3bde1240e42b89c2db1821c13f17c
msgid "Word"
msgstr "Word"

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

# a0fcf56f8074444c99a49231f3bc26e5
msgid "``users_index``"
msgstr "``users_index``"

# 15b221ee46dd449fab859c80a443fe1e
msgid "Indexes about content of comments (``Comments.comment``)."
msgstr "Indexes about content of comments (``Comments.comment``)."

# 755209af91b94d6db8dce11498076736
msgid "``comment_index``"
msgstr "``comment_index``"

# 8f0066fc86714008b048777e1eee3e79
msgid "GeoIndex table"
msgstr "GeoIndex table"

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

# 4dde1139d81844988df8276edcbaf7e6
msgid "Indexes of location column for Users table"
msgstr "Indexes of location column for Users table"

# a213d1c0edad4dc19190b5f56c3811c2
msgid "``users_location``"
msgstr "``users_location``"

# 998e4fa1b1e74ac39e9e7670783690c9
msgid "Indexes of location column for Comments table"
msgstr "Indexes of location column for Comments table"

# 4221e1444bc74e1f8f472ae666bd1a18
msgid "``comments_location``"
msgstr "``comments_location``"

# 5f95736d58eb4de8b638a955c553c12d
msgid "Loading data"
msgstr "Loading data"

# 091549d05357479e93c1dab82e1b1eb3
msgid "Then, load example data."
msgstr "Then, load example data."

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

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

# 8f7795312cd64a8cadd35d1478bc8b12
msgid "``last_modified`` column in ``Comments`` table use Time type."
msgstr "``last_modified`` column in ``Comments`` table use Time type."

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

# da204c6ec5f5491fb607f5b19da0eecb
# 5a8b7c09cf4f473d8d8666aad4e7bbd6
msgid "Search"
msgstr "Search"

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

# 795137d23b1747e88238027671bfad84
msgid "Search users by keyword"
msgstr "Search users by keyword"

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

# 99753fdd10d34a25acfa614b0a4753d8
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."

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

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

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

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

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

# 90cc5fbd3d604c8a9883a96e5c5ff91e
msgid "Search users who follows specific user"
msgstr "Search users who follows specific user"

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

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

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

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

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

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

# 5163a8f284454d0994ef8bbb0afcd24f
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."

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

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

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

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

# c5121522093d44c99598d24ce0b0bd1d
msgid "Search comments by keyword and geolocation"
msgstr "Search comments by keyword and geolocation"

# 49950fab6f354753b7e2825d8f51bc92
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."

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

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

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

# 232a0f0257f547b1b6954fd33543e8e5
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."

# 9218414084b249c386a2ca0bb9cc6842
msgid "Search comments by user id"
msgstr "Search comments by user id"

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

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

# 86f3efcb90af46a291debadd499d449d
msgid "Search user's favorite comments"
msgstr "Search user's favorite comments"

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

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

# 23d3ca3e639048719d5872ba398a58d5
msgid "Search comments by posted time"
msgstr "Search comments by posted time"

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

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

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

# dcdb32f6ab0b48be9982cc049002af61
msgid "Remote access"
msgstr "Remote access"

# 6439c046001b4148a44347addd4fae81
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."

# 94806c371a3146be9e6723e28924fa88
msgid "Hypertext transfer protocol (HTTP)"
msgstr "Hypertext transfer protocol (HTTP)"

# 4f0b27971dc84d38b33d877b325151d9
msgid "How to run an HTTP server"
msgstr "How to run an HTTP server"

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

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

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

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

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

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

# 8610316ecd1e49679978b647c6d886b6
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."

# 7761778942ca4875affc55bf88a1beb7
msgid "Administration tool (HTTP)"
msgstr "Administration tool (HTTP)"

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

# 851e9e9d0e1c422dbd2c9c0e7bcf9647
msgid "Security issues"
msgstr "Security issues"

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

# 4ad67ca007db410a9df085b592cff3bb
msgid "Prefix search with patricia trie"
msgstr "Prefix search with patricia trie"

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

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

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

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

# 67dc5ab6b0fd45adb875730af420c1eb
msgid "Suffix search by primary key"
msgstr "Suffix search by primary key"

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

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

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

# b86f54ddbfe345b0a0fb48383bc5fcc7
msgid "Query expansion"
msgstr "Query expansion"

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

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

# 99665e2928e740fdaa7b4c47147b8b13
msgid "Preparation"
msgstr "Preparation"

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

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

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

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

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

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

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

# f25c2ee64041488a89321225530baa6c
msgid "Various search conditions"
msgstr "Various search conditions"

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

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

# 150c16a8fb9646629b263b49c13a4d85
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."

# 9aafd033725a46e596b72dbe1f0375a8
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::"

# 60057428085649a2a51ff1def56d9c79
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."

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

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

# 1e684ba7a833475b803a32e457197926
msgid "Sort by using ``scorer``"
msgstr "Sort by using ``scorer``"

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

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

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

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

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

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

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

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

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

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

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

# 0ccb0ef994b747ffa3b9ad009d7b6bf4
msgid "Specify longitude and latitude as follows:"
msgstr "Specify longitude and latitude as follows:"

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

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

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

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

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

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

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

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

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

# 3516a8d124cb4be5a0e2ce230c4d4ad4
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."

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

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

# 093bb521596841d49d799e8b8925cb5d
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."

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