Kouhei Sutou
null+****@clear*****
Wed Mar 25 16:22:51 JST 2015
Kouhei Sutou 2015-03-25 16:22:51 +0900 (Wed, 25 Mar 2015) New Revision: 175f9cb927f7f0dfa583ad570c87e49e0e1e2462 https://github.com/groonga/groonga/commit/175f9cb927f7f0dfa583ad570c87e49e0e1e2462 Message: doc: remove auto generated files They should be generated dynamically. Removed files: doc/locale/en/LC_MESSAGES/characteristic.po doc/locale/en/LC_MESSAGES/client.po doc/locale/en/LC_MESSAGES/community.po doc/locale/en/LC_MESSAGES/conf.po doc/locale/en/LC_MESSAGES/contribution.po doc/locale/en/LC_MESSAGES/development.po doc/locale/en/LC_MESSAGES/index.po doc/locale/en/LC_MESSAGES/install.po doc/locale/en/LC_MESSAGES/limitations.po doc/locale/en/LC_MESSAGES/news.po doc/locale/en/LC_MESSAGES/reference.po doc/locale/en/LC_MESSAGES/server.po doc/locale/en/LC_MESSAGES/spec.po doc/locale/en/LC_MESSAGES/suggest.po doc/locale/en/LC_MESSAGES/troubleshooting.po doc/locale/en/LC_MESSAGES/tutorial.po Modified files: .gitignore Modified: .gitignore (+1 -0) =================================================================== --- .gitignore 2015-03-25 14:48:34 +0900 (30a40a3) +++ .gitignore 2015-03-25 16:22:51 +0900 (32e111e) @@ -81,6 +81,7 @@ CMakeFiles /doc/locale/*/LC_MESSAGES/doctrees/ /doc/locale/*/LC_MESSAGES/pot-build-stamp /doc/locale/*/LC_MESSAGES/edit-po-build-stamp +/doc/locale/en/LC_MESSAGES/*.po /doc/commands_not_implemented/ /doc/sphinx/ /lib/icudump Deleted: doc/locale/en/LC_MESSAGES/characteristic.po (+0 -310) 100644 =================================================================== --- doc/locale/en/LC_MESSAGES/characteristic.po 2015-03-25 14:48:34 +0900 (5d2231d) +++ /dev/null @@ -1,310 +0,0 @@ -# -*- po -*- -# English translations for Groonga package. -# Copyright (C) 2009-2014, Brazil, Inc -# This file is distributed under the same license as the Groonga package. -# Kouhei Sutou <kou �� clear-code.com>, 2014. -# -msgid "" -msgstr "" -"Project-Id-Version: Groonga 4.0.1\n" -"Report-Msgid-Bugs-To: \n" -"PO-Revision-Date: 2014-05-23 12:39+0900\n" -"Last-Translator: Kouhei Sutou <kou �� clear-code.com>\n" -"Language-Team: English\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" - -msgid "Characteristics of Groonga" -msgstr "Characteristics of Groonga" - -msgid "Groonga overview" -msgstr "Groonga overview" - -msgid "" -"Groonga is a fast and accurate full text search engine based on inverted " -"index. One of the characteristics of Groonga is that a newly registered " -"document instantly appears in search results. Also, Groonga allows updates " -"without read locks. These characteristics result in superior performance on " -"real-time applications." -msgstr "" -"Groonga is a fast and accurate full text search engine based on inverted " -"index. One of the characteristics of Groonga is that a newly registered " -"document instantly appears in search results. Also, Groonga allows updates " -"without read locks. These characteristics result in superior performance on " -"real-time applications." - -msgid "" -"Groonga is also a column-oriented database management system (DBMS). " -"Compared with well-known row-oriented systems, such as MySQL and PostgreSQL, " -"column-oriented systems are more suited for aggregate queries. Due to this " -"advantage, Groonga can cover weakness of row-oriented systems." -msgstr "" -"Groonga is also a column-oriented database management system (DBMS). " -"Compared with well-known row-oriented systems, such as MySQL and PostgreSQL, " -"column-oriented systems are more suited for aggregate queries. Due to this " -"advantage, Groonga can cover weakness of row-oriented systems." - -msgid "" -"The basic functions of Groonga are provided in a C library. Also, libraries " -"for using Groonga in other languages, such as Ruby, are provided by related " -"projects. In addition, groonga-based storage engines are provided for MySQL " -"and PostgreSQL. These libraries and storage engines allow any application to " -"use Groonga. See `usage examples <http://groonga.org/users/>`_." -msgstr "" -"The basic functions of Groonga are provided in a C library. Also, libraries " -"for using Groonga in other languages, such as Ruby, are provided by related " -"projects. In addition, groonga-based storage engines are provided for MySQL " -"and PostgreSQL. These libraries and storage engines allow any application to " -"use Groonga. See `usage examples <http://groonga.org/users/>`_." - -msgid "Full text search and Instant update" -msgstr "Full text search and Instant update" - -msgid "" -"In widely used DBMSs, updates are immediately processed, for example, a " -"newly registered record appears in the result of the next query. In " -"contrast, some full text search engines do not support instant updates, " -"because it is difficult to dynamically update inverted indexes, the " -"underlying data structure." -msgstr "" -"In widely used DBMSs, updates are immediately processed, for example, a " -"newly registered record appears in the result of the next query. In " -"contrast, some full text search engines do not support instant updates, " -"because it is difficult to dynamically update inverted indexes, the " -"underlying data structure." - -msgid "" -"Groonga also uses inverted indexes but supports instant updates. In " -"addition, Groonga allows you to search documents even when updating the " -"document collection. Due to these superior characteristics, Groonga is very " -"flexible as a full text search engine. Also, Groonga always shows good " -"performance because it divides a large task, inverted index merging, into " -"smaller tasks." -msgstr "" -"Groonga also uses inverted indexes but supports instant updates. In " -"addition, Groonga allows you to search documents even when updating the " -"document collection. Due to these superior characteristics, Groonga is very " -"flexible as a full text search engine. Also, Groonga always shows good " -"performance because it divides a large task, inverted index merging, into " -"smaller tasks." - -msgid "Column store and aggregate query" -msgstr "Column store and aggregate query" - -msgid "" -"People can collect more than enough data in the Internet era. However, it is " -"difficult to extract informative knowledge from a large database, and such a " -"task requires a many-sided analysis through trial and error. For example, " -"search refinement by date, time and location may reveal hidden patterns. " -"Aggregate queries are useful to perform this kind of tasks." -msgstr "" -"People can collect more than enough data in the Internet era. However, it is " -"difficult to extract informative knowledge from a large database, and such a " -"task requires a many-sided analysis through trial and error. For example, " -"search refinement by date, time and location may reveal hidden patterns. " -"Aggregate queries are useful to perform this kind of tasks." - -msgid "" -"An aggregate query groups search results by specified column values and then " -"counts the number of records in each group. For example, an aggregate query " -"in which a location column is specified counts the number of records per " -"location. Making a graph from the result of an aggregate query against a " -"date column is an easy way to visualize changes over time. Also, a " -"combination of refinement by location and an aggregate query against a date " -"column allows visualization of changes over time in specific location. Thus " -"refinement and aggregation are important to perform data mining." -msgstr "" -"An aggregate query groups search results by specified column values and then " -"counts the number of records in each group. For example, an aggregate query " -"in which a location column is specified counts the number of records per " -"location. Making a graph from the result of an aggregate query against a " -"date column is an easy way to visualize changes over time. Also, a " -"combination of refinement by location and an aggregate query against a date " -"column allows visualization of changes over time in specific location. Thus " -"refinement and aggregation are important to perform data mining." - -msgid "" -"A column-oriented architecture allows Groonga to efficiently process " -"aggregate queries because a column-oriented database, which stores records " -"by column, allows an aggregate query to access only a specified column. On " -"the other hand, an aggregate query on a row-oriented database, which stores " -"records by row, has to access neighbor columns, even though those columns " -"are not required." -msgstr "" -"A column-oriented architecture allows Groonga to efficiently process " -"aggregate queries because a column-oriented database, which stores records " -"by column, allows an aggregate query to access only a specified column. On " -"the other hand, an aggregate query on a row-oriented database, which stores " -"records by row, has to access neighbor columns, even though those columns " -"are not required." - -msgid "Inverted index and tokenizer" -msgstr "Inverted index and tokenizer" - -msgid "" -"An inverted index is a traditional data structure used for large-scale full " -"text search. A search engine based on inverted index extracts index terms " -"from a document when it is added. Then in retrieval, a query is divided into " -"index terms to find documents containing those index terms. In this way, " -"index terms play an important role in full text search and thus the way of " -"extracting index terms is a key to a better search engine." -msgstr "" -"An inverted index is a traditional data structure used for large-scale full " -"text search. A search engine based on inverted index extracts index terms " -"from a document when it is added. Then in retrieval, a query is divided into " -"index terms to find documents containing those index terms. In this way, " -"index terms play an important role in full text search and thus the way of " -"extracting index terms is a key to a better search engine." - -msgid "" -"A tokenizer is a module to extract index terms. A Japanese full text search " -"engine commonly uses a word-based tokenizer (hereafter referred to as a word " -"tokenizer) and/or a character-based n-gram tokenizer (hereafter referred to " -"as an n-gram tokenizer). A word tokenizer-based search engine is superior in " -"time, space and precision, which is the fraction of relevant documents in a " -"search result. On the other hand, an n-gram tokenizer-based search engine is " -"superior in recall, which is the fraction of retrieved documents in the " -"perfect search result. The best choice depends on the application in " -"practice." -msgstr "" -"A tokenizer is a module to extract index terms. A Japanese full text search " -"engine commonly uses a word-based tokenizer (hereafter referred to as a word " -"tokenizer) and/or a character-based n-gram tokenizer (hereafter referred to " -"as an n-gram tokenizer). A word tokenizer-based search engine is superior in " -"time, space and precision, which is the fraction of relevant documents in a " -"search result. On the other hand, an n-gram tokenizer-based search engine is " -"superior in recall, which is the fraction of retrieved documents in the " -"perfect search result. The best choice depends on the application in " -"practice." - -msgid "" -"Groonga supports both word and n-gram tokenizers. The simplest built-in " -"tokenizer uses spaces as word delimiters. Built-in n-gram tokenizers (n = 1, " -"2, 3) are also available by default. In addition, a yet another built-in " -"word tokenizer is available if MeCab, a part-of-speech and morphological " -"analyzer, is embedded. Note that a tokenizer is pluggable and you can " -"develop your own tokenizer, such as a tokenizer based on another part-of-" -"speech tagger or a named-entity recognizer." -msgstr "" -"Groonga supports both word and n-gram tokenizers. The simplest built-in " -"tokenizer uses spaces as word delimiters. Built-in n-gram tokenizers (n = 1, " -"2, 3) are also available by default. In addition, a yet another built-in " -"word tokenizer is available if MeCab, a part-of-speech and morphological " -"analyzer, is embedded. Note that a tokenizer is pluggable and you can " -"develop your own tokenizer, such as a tokenizer based on another part-of-" -"speech tagger or a named-entity recognizer." - -msgid "Sharable storage and read lock-free" -msgstr "Sharable storage and read lock-free" - -msgid "" -"Multi-core processors are mainstream today and the number of cores per " -"processor is increasing. In order to exploit multiple cores, executing " -"multiple queries in parallel or dividing a query into sub-queries for " -"parallel processing is becoming more important." -msgstr "" -"Multi-core processors are mainstream today and the number of cores per " -"processor is increasing. In order to exploit multiple cores, executing " -"multiple queries in parallel or dividing a query into sub-queries for " -"parallel processing is becoming more important." - -msgid "" -"A database of Groonga can be shared with multiple threads/processes. Also, " -"multiple threads/processes can execute read queries in parallel even when " -"another thread/process is executing an update query because Groonga uses " -"read lock-free data structures. This feature is suited to a real-time " -"application that needs to update a database while executing read queries. In " -"addition, Groonga allows you to build flexible systems. For example, a " -"database can receive read queries through the built-in HTTP server of " -"Groonga while accepting update queries through MySQL." -msgstr "" -"A database of Groonga can be shared with multiple threads/processes. Also, " -"multiple threads/processes can execute read queries in parallel even when " -"another thread/process is executing an update query because Groonga uses " -"read lock-free data structures. This feature is suited to a real-time " -"application that needs to update a database while executing read queries. In " -"addition, Groonga allows you to build flexible systems. For example, a " -"database can receive read queries through the built-in HTTP server of " -"Groonga while accepting update queries through MySQL." - -msgid "Geo-location (latitude and longitude) search" -msgstr "Geo-location (latitude and longitude) search" - -msgid "" -"Location services are getting more convenient because of mobile devices with " -"GPS. For example, if you are going to have lunch or dinner at a nearby " -"restaurant, a local search service for restaurants may be very useful, and " -"for such services, fast geo-location search is becoming more important." -msgstr "" -"Location services are getting more convenient because of mobile devices with " -"GPS. For example, if you are going to have lunch or dinner at a nearby " -"restaurant, a local search service for restaurants may be very useful, and " -"for such services, fast geo-location search is becoming more important." - -msgid "" -"Groonga provides inverted index-based fast geo-location search, which " -"supports a query to find points in a rectangle or circle. Groonga gives high " -"priority to points near the center of an area. Also, Groonga supports " -"distance measurement and you can sort points by distance from any point." -msgstr "" -"Groonga provides inverted index-based fast geo-location search, which " -"supports a query to find points in a rectangle or circle. Groonga gives high " -"priority to points near the center of an area. Also, Groonga supports " -"distance measurement and you can sort points by distance from any point." - -msgid "Groonga library" -msgstr "Groonga library" - -msgid "" -"The basic functions of Groonga are provided in a C library and any " -"application can use Groonga as a full text search engine or a column-" -"oriented database. Also, libraries for languages other than C/C++, such as " -"Ruby, are provided in related projects. See `related projects <http://" -"groonga.org/related-projects.html>`_ for details." -msgstr "" -"The basic functions of Groonga are provided in a C library and any " -"application can use Groonga as a full text search engine or a column-" -"oriented database. Also, libraries for languages other than C/C++, such as " -"Ruby, are provided in related projects. See `related projects <http://" -"groonga.org/related-projects.html>`_ for details." - -msgid "Groonga server" -msgstr "Groonga server" - -msgid "" -"Groonga provides a built-in server command which supports HTTP, the " -"memcached binary protocol and the Groonga Query Transfer Protocol (GQTP). " -"Also, a Groonga server supports query caching, which significantly reduces " -"response time for repeated read queries. Using this command, Groonga is " -"available even on a server that does not allow you to install new libraries." -msgstr "" -"Groonga provides a built-in server command which supports HTTP, the " -"memcached binary protocol and the Groonga Query Transfer Protocol (GQTP). " -"Also, a Groonga server supports query caching, which significantly reduces " -"response time for repeated read queries. Using this command, Groonga is " -"available even on a server that does not allow you to install new libraries." - -msgid "Mroonga storage engine" -msgstr "Mroonga storage engine" - -msgid "" -"Groonga works not only as an independent column-oriented DBMS but also as " -"storage engines of well-known DBMSs. For example, `Mroonga <http://mroonga." -"org/>`_ is a MySQL pluggable storage engine using Groonga. By using Mroonga, " -"you can use Groonga for column-oriented storage and full text search. A " -"combination of a built-in storage engine, MyISAM or InnoDB, and a Groonga-" -"based full text search engine is also available. All the combinations have " -"good and bad points and the best one depends on the application. See " -"`related projects <http://groonga.org/related-projects.html>`_ for details." -msgstr "" -"Groonga works not only as an independent column-oriented DBMS but also as " -"storage engines of well-known DBMSs. For example, `Mroonga <http://mroonga." -"org/>`_ is a MySQL pluggable storage engine using Groonga. By using Mroonga, " -"you can use Groonga for column-oriented storage and full text search. A " -"combination of a built-in storage engine, MyISAM or InnoDB, and a Groonga-" -"based full text search engine is also available. All the combinations have " -"good and bad points and the best one depends on the application. See " -"`related projects <http://groonga.org/related-projects.html>`_ for details." Deleted: doc/locale/en/LC_MESSAGES/client.po (+0 -44) 100644 =================================================================== --- doc/locale/en/LC_MESSAGES/client.po 2015-03-25 14:48:34 +0900 (d22f0ea) +++ /dev/null @@ -1,44 +0,0 @@ -# -*- po -*- -# English translations for Groonga package. -# Copyright (C) 2009-2014, Brazil, Inc -# This file is distributed under the same license as the Groonga package. -# Kouhei Sutou <kou �� clear-code.com>, 2014. -# -msgid "" -msgstr "" -"Project-Id-Version: Groonga 4.0.1\n" -"Report-Msgid-Bugs-To: \n" -"PO-Revision-Date: 2014-05-23 12:44+0900\n" -"Last-Translator: Kouhei Sutou <kou �� clear-code.com>\n" -"Language-Team: English\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" - -msgid "Client" -msgstr "Client" - -msgid "" -"Groonga supports the original protocol (:doc:`/spec/gqtp`), the memcached " -"binary protocol and HTTP." -msgstr "" -"Groonga supports the original protocol (:doc:`/spec/gqtp`), the memcached " -"binary protocol and HTTP." - -msgid "" -"As HTTP and memcached binary protocol is matured protocol, you can use " -"existing client libraries." -msgstr "" -"As HTTP and memcached binary protocol is matured protocol, you can use " -"existing client libraries." - -msgid "" -"There are some client libraries which provides convenient API to connect to " -"Groonga server in some program languages. See `Client libraries <http://" -"groonga.org/related-projects.html#libraries>`_ for details." -msgstr "" -"There are some client libraries which provides convenient API to connect to " -"Groonga server in some program languages. See `Client libraries <http://" -"groonga.org/related-projects.html#libraries>`_ for details." Deleted: doc/locale/en/LC_MESSAGES/community.po (+0 -82) 100644 =================================================================== --- doc/locale/en/LC_MESSAGES/community.po 2015-03-25 14:48:34 +0900 (bfe66ac) +++ /dev/null @@ -1,82 +0,0 @@ -# -*- po -*- -# English translations for Groonga package. -# Copyright (C) 2009-2014, Brazil, Inc -# This file is distributed under the same license as the Groonga package. -# Kouhei Sutou <kou �� clear-code.com>, 2014. -# -msgid "" -msgstr "" -"Project-Id-Version: Groonga 4.0.1\n" -"Report-Msgid-Bugs-To: \n" -"PO-Revision-Date: 2014-05-23 12:40+0900\n" -"Last-Translator: Kouhei Sutou <kou �� clear-code.com>\n" -"Language-Team: English\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" - -msgid "Community" -msgstr "Community" - -msgid "" -"There are some places for sharing Groonga information. We welcome you to " -"join our community." -msgstr "" -"There are some places for sharing Groonga information. We welcome you to " -"join our community." - -msgid "Mailing List" -msgstr "Mailing List" - -msgid "There are mailing lists for discussion about Groonga." -msgstr "There are mailing lists for discussion about Groonga." - -msgid "For English speakers" -msgstr "For English speakers" - -msgid "" -"`groonga-talk �� lists.sourceforge.net <http://lists.sourceforge.net/mailman/" -"listinfo/groonga-talk>`_" -msgstr "" -"`groonga-talk �� lists.sourceforge.net <http://lists.sourceforge.net/mailman/" -"listinfo/groonga-talk>`_" - -msgid "For Japanese speakers" -msgstr "For Japanese speakers" - -msgid "" -"`groonga-dev �� lists.sourceforge.jp <http://lists.sourceforge.jp/mailman/" -"listinfo/groonga-dev>`_" -msgstr "" -"`groonga-dev �� lists.sourceforge.jp <http://lists.sourceforge.jp/mailman/" -"listinfo/groonga-dev>`_" - -msgid "Twitter" -msgstr "Twitter" - -msgid "" -"`@groonga <https://twitter.com/groonga/>`_ tweets Groonga related " -"information." -msgstr "" -"`@groonga <https://twitter.com/groonga/>`_ tweets Groonga related " -"information." - -msgid "" -"Please follow the account to get the latest Groonga related information!" -msgstr "" -"Please follow the account to get the latest Groonga related information!" - -msgid "Facebook" -msgstr "Facebook" - -msgid "" -"`Groonga page on Facebook <http://www.facebook.com/groonga>`_ shares Groonga " -"related information." -msgstr "" -"`Groonga page on Facebook <http://www.facebook.com/groonga>`_ shares Groonga " -"related information." - -msgid "Please like the page to get the latest Groonga related information!" -msgstr "Please like the page to get the latest Groonga related information!" Deleted: doc/locale/en/LC_MESSAGES/conf.po (+0 -28) 100644 =================================================================== --- doc/locale/en/LC_MESSAGES/conf.po 2015-03-25 14:48:34 +0900 (ef83e20) +++ /dev/null @@ -1,28 +0,0 @@ -# -*- po -*- -# English translations for groonga package. -# Copyright (C) 2014 THE groonga'S COPYRIGHT HOLDER -# This file is distributed under the same license as the groonga package. -# Kouhei Sutou <kou �� clear-code.com>, 2014. -# -msgid "" -msgstr "" -"Project-Id-Version: groonga 4.0.1\n" -"Report-Msgid-Bugs-To: \n" -"PO-Revision-Date: 2014-05-23 12:44+0900\n" -"Last-Translator: Kouhei Sutou <kou �� clear-code.com>\n" -"Language-Team: English\n" -"Language: en\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=ASCII\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#, python-format -msgid "%(project)s v%(release)s documentation" -msgstr "%(project)s v%(release)s documentation" - -msgid "Groonga documentation" -msgstr "Groonga documentation" - -msgid "Groonga Project" -msgstr "Groonga Project" Deleted: doc/locale/en/LC_MESSAGES/contribution.po (+0 -2133) 100644 =================================================================== --- doc/locale/en/LC_MESSAGES/contribution.po 2015-03-25 14:48:34 +0900 (4039c18) +++ /dev/null @@ -1,2133 +0,0 @@ -# -*- po -*- -# English translations for Groonga package. -# Copyright (C) 2009-2014, Brazil, Inc -# This file is distributed under the same license as the Groonga package. -# Kouhei Sutou <kou �� clear-code.com>, 2014. -# -msgid "" -msgstr "" -"Project-Id-Version: Groonga 4.0.1\n" -"Report-Msgid-Bugs-To: \n" -"PO-Revision-Date: 2014-12-24 23:38+0900\n" -"Last-Translator: Kouhei Sutou <kou �� clear-code.com>\n" -"Language-Team: English\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" - -msgid "How to contribute to groonga" -msgstr "How to contribute to groonga" - -msgid "" -"We welcome your contributions to the groonga project. There are many ways to " -"contribute, such as using groonga, introduction to others, etc. For example, " -"if you find a bug when using groonga, you are welcome to report the bug. " -"Coding and documentation are also welcome for groonga and its related " -"projects." -msgstr "" -"We welcome your contributions to the groonga project. There are many ways to " -"contribute, such as using groonga, introduction to others, etc. For example, " -"if you find a bug when using groonga, you are welcome to report the bug. " -"Coding and documentation are also welcome for groonga and its related " -"projects." - -msgid "As a user:" -msgstr "As a user:" - -msgid "If you are interested in groonga, please read this document and try it." -msgstr "" -"If you are interested in groonga, please read this document and try it." - -msgid "As a spokesman:" -msgstr "As a spokesman:" - -msgid "Please introduce groonga to your friends and colleagues." -msgstr "Please introduce groonga to your friends and colleagues." - -msgid "As a developer: Bug report, development and documentation" -msgstr "As a developer: Bug report, development and documentation" - -msgid "This section describes the details." -msgstr "This section describes the details." - -msgid "Groonga開発者向け情報" -msgstr "Groonga開発者向け情報" - -msgid "Groonga 通信アーキテクチャ" -msgstr "Groonga 通信アーキテクチャ" - -msgid "GQTPでのアーキテクチャ" -msgstr "GQTPでのアーキテクチャ" - -msgid "comが外部からの接続を受け付ける。" -msgstr "comが外部からの接続を受け付ける。" - -msgid "comは1スレッド。" -msgstr "comは1スレッド。" - -msgid "comがedgeを作る。" -msgstr "comがedgeを作る。" - -msgid "edgeは接続と１対１対応。" -msgstr "edgeは接続と１対１対応。" - -msgid "edgeはctxを含む。" -msgstr "edgeはctxを含む。" - -msgid "workerはthreadと１対１対応。" -msgstr "workerはthreadと１対１対応。" - -msgid "workerは上限が個定数。" -msgstr "workerは上限が個定数。" - -msgid "workerは、１つのedgeと結びつくことができる。" -msgstr "workerは、１つのedgeと結びつくことができる。" - -msgid "edgeごとにqueueを持つ。" -msgstr "edgeごとにqueueを持つ。" - -msgid "" -"msgはcomによって、edgeのqueueにenqueueされる。 edgeがworkerに結びついていない" -"ときは、同時に、ctx_newというqueueに、msgをenqueueした対象のedgeをenqueueす" -"る。" -msgstr "" -"msgはcomによって、edgeのqueueにenqueueされる。 edgeがworkerに結びついていない" -"ときは、同時に、ctx_newというqueueに、msgをenqueueした対象のedgeをenqueueす" -"る。" - -msgid "ユーザーと協力して開発をうまく進めていくための指針" -msgstr "ユーザーと協力して開発をうまく進めていくための指針" - -msgid "" -"Groongaを使ってくれているユーザーと協力して 開発をうまく進めていくためにこう" -"するといい、という事柄をまとめました。 まとめておくと、新しく開発に加わる人と" -"も共有することができます。" -msgstr "" -"Groongaを使ってくれているユーザーと協力して 開発をうまく進めていくためにこう" -"するといい、という事柄をまとめました。 まとめておくと、新しく開発に加わる人と" -"も共有することができます。" - -msgid "twitter編" -msgstr "twitter編" - -msgid "" -"Groongaを使ってもらえるようにtwitterのアカウントGroongaを取得して 日々、リ" -"リースの案内をしたり、ユーザーサポートをしたりしています。" -msgstr "" -"Groongaを使ってもらえるようにtwitterのアカウントGroongaを取得して 日々、リ" -"リースの案内をしたり、ユーザーサポートをしたりしています。" - -msgid "" -"リリースの案内に利用する場合には、やりとりを考えなくて良いですが、 複数人によ" -"るサポートをGroongaで行う場合に、どうサポートするのが 良いのか/どうしてそうす" -"るのかという共通認識を持っていないと一貫性のないサポートとなってしま います。" -msgstr "" -"リリースの案内に利用する場合には、やりとりを考えなくて良いですが、 複数人によ" -"るサポートをGroongaで行う場合に、どうサポートするのが 良いのか/どうしてそうす" -"るのかという共通認識を持っていないと一貫性のないサポートとなってしま います。" - -msgid "" -"twitterでサポートされている安心感からGroongaユーザーの拡大に繋げる ことができ" -"るようにサポートの際に気をつけることをまとめます。" -msgstr "" -"twitterでサポートされている安心感からGroongaユーザーの拡大に繋げる ことができ" -"るようにサポートの際に気をつけることをまとめます。" - -msgid "過去のツイートはおさらいしておく" -msgstr "過去のツイートはおさらいしておく" - -msgid "理由" -msgstr "理由" - -msgid "" -"自分がツイートした内容を把握していない返信をされたら普通いい気はしません。" -msgstr "" -"自分がツイートした内容を把握していない返信をされたら普通いい気はしません。" - -msgid "対応" -msgstr "対応" - -msgid "" -"過去のツイートをおさらいし、こうすれば良いという提案をできるのが望ましいで" -"す。::" -msgstr "" -"過去のツイートをおさらいし、こうすれば良いという提案をできるのが望ましいで" -"す。::" - -msgid "こちらから情報を提供する" -msgstr "こちらから情報を提供する" - -msgid "" -"困っているユーザーが複数回ツイートして限られたなかで情報を提供してくれている" -"ことがあります。 その限られたツイートから解決方法が見つかればユーザーにとって" -"余計な手間が少なくて済みます。 あれこれ情報提供を要求すると、ユーザーはそのぶ" -"ん確認する作業が必要になります。" -msgstr "" -"困っているユーザーが複数回ツイートして限られたなかで情報を提供してくれている" -"ことがあります。 その限られたツイートから解決方法が見つかればユーザーにとって" -"余計な手間が少なくて済みます。 あれこれ情報提供を要求すると、ユーザーはそのぶ" -"ん確認する作業が必要になります。" - -msgid "" -"最初に声をかけるときに解決策を1つか2つ提案できると望ましいです。ユーザーにあ" -"まり負担を感じさせないようにすると良いです。::" -msgstr "" -"最初に声をかけるときに解決策を1つか2つ提案できると望ましいです。ユーザーにあ" -"まり負担を感じさせないようにすると良いです。::" - -msgid "twitterでのやりとりはできるだけ他の場所(例えばredmine)へと誘導しない" -msgstr "twitterでのやりとりはできるだけ他の場所(例えばredmine)へと誘導しない" - -msgid "" -"twitterは気軽につぶやけることが重要なので、気軽にできないことを相手に要求する" -"と萎縮されてしまう可能性があります。" -msgstr "" -"twitterは気軽につぶやけることが重要なので、気軽にできないことを相手に要求する" -"と萎縮されてしまう可能性があります。" - -msgid "" -"いきなりredmineでバグ報告をお願いすると、しりごみしてしまうかも知れません。::" -msgstr "" -"いきなりredmineでバグ報告をお願いすると、しりごみしてしまうかも知れません。::" - -msgid "" -"Groonga関連で気軽につぶやけないとなると開発者は困っている人を見つけられない" -"し、利用者は困ったままとなるので、双方にとって嬉しくない状態になっ てしまいま" -"す。" -msgstr "" -"Groonga関連で気軽につぶやけないとなると開発者は困っている人を見つけられない" -"し、利用者は困ったままとなるので、双方にとって嬉しくない状態になっ てしまいま" -"す。" - -msgid "twitterでやりとりを完結できるようにします。" -msgstr "twitterでやりとりを完結できるようにします。" - -msgid "クエリの実現" -msgstr "クエリの実現" - -msgid "" -"Groongaのデータベースには大量のデータを格納し、その中から必要な部分を高速に取" -"り出すことができます。必要な部分をGroongaのデータベースに問い合わせるためのク" -"エリの表現と実行に関して、Groongaは複数の手段を用意しています。" -msgstr "" -"Groongaのデータベースには大量のデータを格納し、その中から必要な部分を高速に取" -"り出すことができます。必要な部分をGroongaのデータベースに問い合わせるためのク" -"エリの表現と実行に関して、Groongaは複数の手段を用意しています。" - -msgid "クエリ実行のためのインタフェース" -msgstr "クエリ実行のためのインタフェース" - -msgid "" -"Groongaは低機能で単純なライブラリインタフェースから、高機能で複雑なコマンドイ" -"ンタフェースまでいくつかの階層的なインタフェースをユーザプログラムに提供して" -"います。" -msgstr "" -"Groongaは低機能で単純なライブラリインタフェースから、高機能で複雑なコマンドイ" -"ンタフェースまでいくつかの階層的なインタフェースをユーザプログラムに提供して" -"います。" - -msgid "" -"クエリ実行のためのインタフェースも階層的なインタフェースのそれぞれに対応する" -"形で用意されています。以下に低レイヤなインタフェースから順に説明します。" -msgstr "" -"クエリ実行のためのインタフェースも階層的なインタフェースのそれぞれに対応する" -"形で用意されています。以下に低レイヤなインタフェースから順に説明します。" - -msgid "DB_API" -msgstr "DB_API" - -msgid "" -"DB_APIは、Groongaデータベースを操作するための一群のC言語向けAPI関数を提供しま" -"す。DB_APIはデータベースを構成する個々の部分に対する単純な操作関数を提供しま" -"す。DB_APIの機能を組み合わせることによって複雑なクエリを実行することができま" -"す。後述のすべてのクエリインタフェースはDB_APIの機能を組み合わせることによっ" -"て実現されています。" -msgstr "" -"DB_APIは、Groongaデータベースを操作するための一群のC言語向けAPI関数を提供しま" -"す。DB_APIはデータベースを構成する個々の部分に対する単純な操作関数を提供しま" -"す。DB_APIの機能を組み合わせることによって複雑なクエリを実行することができま" -"す。後述のすべてのクエリインタフェースはDB_APIの機能を組み合わせることによっ" -"て実現されています。" - -msgid "grn_expr" -msgstr "grn_expr" - -msgid "" -"grn_exprは、Groongaデータベースに対する検索処理や更新処理のための条件を表現す" -"るためのデータ構造で、複数の条件を再帰的に組み合わせてより複雑な条件を表現す" -"ることができます。grn_exprによって表現されたクエリを実行するためには、" -"grn_table_select()関数を使用します。" -msgstr "" -"grn_exprは、Groongaデータベースに対する検索処理や更新処理のための条件を表現す" -"るためのデータ構造で、複数の条件を再帰的に組み合わせてより複雑な条件を表現す" -"ることができます。grn_exprによって表現されたクエリを実行するためには、" -"grn_table_select()関数を使用します。" - -msgid "Groonga実行ファイル" -msgstr "Groonga実行ファイル" - -msgid "" -"Groongaデータベースを操作するためのコマンドインタープリタです。渡されたコマン" -"ドを解釈し、実行結果を返します。コマンドの実処理はC言語で記述されます。ユーザ" -"がC言語で定義した関数を新たなコマンドとしてGroonga実行ファイルに組み込むこと" -"ができます。各コマンドはいくつかの文字列引数を受け取り、これをクエリとして解" -"釈して実行します。引数をgrn_exprとして解釈するか、別の形式として解釈して" -"DB_APIを使ってデータベースを操作するかはコマンド毎に自由に決めることができま" -"す。" -msgstr "" -"Groongaデータベースを操作するためのコマンドインタープリタです。渡されたコマン" -"ドを解釈し、実行結果を返します。コマンドの実処理はC言語で記述されます。ユーザ" -"がC言語で定義した関数を新たなコマンドとしてGroonga実行ファイルに組み込むこと" -"ができます。各コマンドはいくつかの文字列引数を受け取り、これをクエリとして解" -"釈して実行します。引数をgrn_exprとして解釈するか、別の形式として解釈して" -"DB_APIを使ってデータベースを操作するかはコマンド毎に自由に決めることができま" -"す。" - -msgid "grn_exprで表現できるクエリ" -msgstr "grn_exprで表現できるクエリ" - -msgid "" -"grn_exprは代入や関数呼び出しのような様々な操作を表現できますが、この中で検索" -"クエリを表現するgrn_exprのことを特に条件式とよびます。条件式を構成する個々の" -"要素を関係式と呼びます。条件式は一個以上の関係式か、あるいは条件式を論理演算" -"子で結合したものです。" -msgstr "" -"grn_exprは代入や関数呼び出しのような様々な操作を表現できますが、この中で検索" -"クエリを表現するgrn_exprのことを特に条件式とよびます。条件式を構成する個々の" -"要素を関係式と呼びます。条件式は一個以上の関係式か、あるいは条件式を論理演算" -"子で結合したものです。" - -msgid "論理演算子は、以下の3種類があります。 ::" -msgstr "論理演算子は、以下の3種類があります。 ::" - -msgid "" -"関係式は、下記の11種類が用意されています。また、ユーザが定義した関数を新たな" -"関係式として使うこともできます。 ::" -msgstr "" -"関係式は、下記の11種類が用意されています。また、ユーザが定義した関数を新たな" -"関係式として使うこともできます。 ::" - -msgid "grn_table_select()" -msgstr "grn_table_select()" - -msgid "" -"grn_table_select()関数は、grn_exprで表現された検索クエリを実行するときに使い" -"ます。引数として、検索対象となるテーブル、クエリを表すgrn_expr、検索結果を格" -"納するテーブル、それに検索にマッチしたレコードを検索結果にどのように反映する" -"かを指定する演算子を渡します。演算子と指定できるのは下記の4種類です。 ::" -msgstr "" -"grn_table_select()関数は、grn_exprで表現された検索クエリを実行するときに使い" -"ます。引数として、検索対象となるテーブル、クエリを表すgrn_expr、検索結果を格" -"納するテーブル、それに検索にマッチしたレコードを検索結果にどのように反映する" -"かを指定する演算子を渡します。演算子と指定できるのは下記の4種類です。 ::" - -msgid "" -"GRN_OP_ORは、検索対象テーブルの中からクエリにマッチするレコードを検索結果テー" -"ブルに加えます。GRN_OP_OR以外の演算子は、検索結果テーブルが空でない場合にだけ" -"意味を持ちます。GRN_OP_ANDは、検索結果テーブルの中からクエリにマッチしないレ" -"コードを取り除きます。GRN_OP_BUTは、検索結果テーブルの中からクエリにマッチす" -"るレコードを取り除きます。GRN_OP_ADJUSTは、検索結果テーブルの中でクエリにマッ" -"チするレコードに対してスコア値の更新のみを行います。" -msgstr "" -"GRN_OP_ORは、検索対象テーブルの中からクエリにマッチするレコードを検索結果テー" -"ブルに加えます。GRN_OP_OR以外の演算子は、検索結果テーブルが空でない場合にだけ" -"意味を持ちます。GRN_OP_ANDは、検索結果テーブルの中からクエリにマッチしないレ" -"コードを取り除きます。GRN_OP_BUTは、検索結果テーブルの中からクエリにマッチす" -"るレコードを取り除きます。GRN_OP_ADJUSTは、検索結果テーブルの中でクエリにマッ" -"チするレコードに対してスコア値の更新のみを行います。" - -msgid "" -"grn_table_select()は、データベース上に定義されたテーブルや索引などを組み合わ" -"せて可能な限り高速に指定されたクエリを実行しようとします。" -msgstr "" -"grn_table_select()は、データベース上に定義されたテーブルや索引などを組み合わ" -"せて可能な限り高速に指定されたクエリを実行しようとします。" - -msgid "関係式" -msgstr "関係式" - -msgid "" -"関係式は、検索しようとしているデータが満たすべき条件を、指定した値の間の関係" -"として表現します。いずれの関係式も、その関係が成り立ったときに評価される" -"callback、コールバック関数に渡されるargとを引数として指定することができます。" -"callbackが与えられず、argのみが数値で与えられた場合はスコア値の係数とみなされ" -"ます。主な関係式について説明します。" -msgstr "" -"関係式は、検索しようとしているデータが満たすべき条件を、指定した値の間の関係" -"として表現します。いずれの関係式も、その関係が成り立ったときに評価される" -"callback、コールバック関数に渡されるargとを引数として指定することができます。" -"callbackが与えられず、argのみが数値で与えられた場合はスコア値の係数とみなされ" -"ます。主な関係式について説明します。" - -msgid "equal(v1, v2, arg, callback)" -msgstr "equal(v1, v2, arg, callback)" - -msgid "v1の値とv2の値が等しいことを表します。" -msgstr "v1の値とv2の値が等しいことを表します。" - -msgid "not_equal(v1, v2, arg, callback)" -msgstr "not_equal(v1, v2, arg, callback)" - -msgid "v1の値とv2の値が等しくないことを表します。" -msgstr "v1の値とv2の値が等しくないことを表します。" - -msgid "less(v1, v2, arg, callback)" -msgstr "less(v1, v2, arg, callback)" - -msgid "v1の値がv2の値よりも小さいことを表します。" -msgstr "v1の値がv2の値よりも小さいことを表します。" - -msgid "greater(v1, v2, arg, callback)" -msgstr "greater(v1, v2, arg, callback)" - -msgid "v1の値がv2の値よりも大きいことを表します。" -msgstr "v1の値がv2の値よりも大きいことを表します。" - -msgid "less_equal(v1, v2, arg, callback)" -msgstr "less_equal(v1, v2, arg, callback)" - -msgid "v1の値がv2の値と等しいか小さいことを表します。" -msgstr "v1の値がv2の値と等しいか小さいことを表します。" - -msgid "greater_equal(v1, v2, arg, callback)" -msgstr "greater_equal(v1, v2, arg, callback)" - -msgid "v1の値がv2の値と等しいか大きいことを表します。" -msgstr "v1の値がv2の値と等しいか大きいことを表します。" - -msgid "contain(v1, v2, mode, arg, callback)" -msgstr "contain(v1, v2, mode, arg, callback)" - -msgid "" -"v1の値がv2の値を含んでいることを表します。また、v1の値が要素に分解されると" -"き、それぞれの要素に対して二つ目の要素が一致するためのmodeとして下記のいずれ" -"かを指定することができます。" -msgstr "" -"v1の値がv2の値を含んでいることを表します。また、v1の値が要素に分解されると" -"き、それぞれの要素に対して二つ目の要素が一致するためのmodeとして下記のいずれ" -"かを指定することができます。" - -msgid "near(v1, v2, arg, callback)" -msgstr "near(v1, v2, arg, callback)" - -msgid "" -"v1の値の中に、v2の値の要素が接近して含まれていることを表します。(v2には値の配" -"列を渡します)" -msgstr "" -"v1の値の中に、v2の値の要素が接近して含まれていることを表します。(v2には値の配" -"列を渡します)" - -msgid "similar(v1, v2, arg, callback)" -msgstr "similar(v1, v2, arg, callback)" - -msgid "v1の値とv2の値が類似していることを表します。" -msgstr "v1の値とv2の値が類似していることを表します。" - -msgid "prefix(v1, v2, arg, callback)" -msgstr "prefix(v1, v2, arg, callback)" - -msgid "v1の値がv2の値に対して前方一致することを表します。" -msgstr "v1の値がv2の値に対して前方一致することを表します。" - -msgid "suffix(v1, v2, arg, callback)" -msgstr "suffix(v1, v2, arg, callback)" - -msgid "v1の値がv2の値に対して後方一致することを表します。" -msgstr "v1の値がv2の値に対して後方一致することを表します。" - -msgid "クエリの実例" -msgstr "クエリの実例" - -msgid "grn_exprを使って様々な検索クエリを表現することができます。" -msgstr "grn_exprを使って様々な検索クエリを表現することができます。" - -msgid "検索例1" -msgstr "検索例1" - -msgid "" -"tableのcolumnの値がstringを含むレコードをresultに返します。columnの値" -"が'needle in haystack'であるレコードr1と、columnの値が'haystack'であるレコー" -"ドr2がtableに登録されていたとき、stringに'needle'を指定したなら、レコードr1の" -"みがヒットします。" -msgstr "" -"tableのcolumnの値がstringを含むレコードをresultに返します。columnの値" -"が'needle in haystack'であるレコードr1と、columnの値が'haystack'であるレコー" -"ドr2がtableに登録されていたとき、stringに'needle'を指定したなら、レコードr1の" -"みがヒットします。" - -msgid "検索例2" -msgstr "検索例2" - -msgid "" -"tableのcolumn1の値がstringにexactモードでヒットするレコードについて得られるス" -"コア値にscore1を積算してresultにセットします。次に、resultにセットされたレ" -"コードのうち、column2の値がstringにexactモードでヒットするレコードについて" -"は、得られたスコア値にscore2を積算したものを、元のスコア値に加えます。" -msgstr "" -"tableのcolumn1の値がstringにexactモードでヒットするレコードについて得られるス" -"コア値にscore1を積算してresultにセットします。次に、resultにセットされたレ" -"コードのうち、column2の値がstringにexactモードでヒットするレコードについて" -"は、得られたスコア値にscore2を積算したものを、元のスコア値に加えます。" - -msgid "検索例3" -msgstr "検索例3" - -msgid "" -"tableのcolumn1の値がstringにexactモードでヒットするレコードについて得られるス" -"コア値にscore1を積算してresultにセットします。得られた検索結果数がt1よりも小" -"さい場合は、partialモードで再度検索し、ヒットしたレコードについて得られるスコ" -"ア値にscore2を積算してresultに追加します。" -msgstr "" -"tableのcolumn1の値がstringにexactモードでヒットするレコードについて得られるス" -"コア値にscore1を積算してresultにセットします。得られた検索結果数がt1よりも小" -"さい場合は、partialモードで再度検索し、ヒットしたレコードについて得られるスコ" -"ア値にscore2を積算してresultに追加します。" - -msgid "検索例4" -msgstr "検索例4" - -msgid "" -"tableのcolumnの値がstringに含まれるレコードをresultに返します。 columnの値" -"が'needle'であるレコードr1と、columnの値が'haystack'であるレコードr2がtableに" -"登録されていたとき、stringに'hay in haystack'を指定したなら、レコードr2のみが" -"ヒットします。" -msgstr "" -"tableのcolumnの値がstringに含まれるレコードをresultに返します。 columnの値" -"が'needle'であるレコードr1と、columnの値が'haystack'であるレコードr2がtableに" -"登録されていたとき、stringに'hay in haystack'を指定したなら、レコードr2のみが" -"ヒットします。" - -msgid "リリース手順" -msgstr "リリース手順" - -msgid "前提条件" -msgstr "前提条件" - -msgid "リリース手順の前提条件は以下の通りです。" -msgstr "リリース手順の前提条件は以下の通りです。" - -msgid "ビルド環境は Ubuntu 12.04 LTS(Precise Pangolin)" -msgstr "ビルド環境は Ubuntu 12.04 LTS(Precise Pangolin)" - -msgid "コマンドラインの実行例はzsh" -msgstr "コマンドラインの実行例はzsh" - -msgid "作業ディレクトリ例は以下を使用します。" -msgstr "作業ディレクトリ例は以下を使用します。" - -msgid "GROONGA_DIR=$HOME/work/groonga" -msgstr "GROONGA_DIR=$HOME/work/groonga" - -msgid "GROONGA_CLONE_DIR=$HOME/work/groonga/groonga.clean" -msgstr "GROONGA_CLONE_DIR=$HOME/work/groonga/groonga.clean" - -msgid "GROONGA_GITHUB_COM_PATH=$HOME/work/groonga/groonga.github.com" -msgstr "GROONGA_GITHUB_COM_PATH=$HOME/work/groonga/groonga.github.com" - -msgid "CUTTER_DIR=$HOME/work/cutter" -msgstr "CUTTER_DIR=$HOME/work/cutter" - -msgid "CUTTER_SOURCE_PATH=$HOME/work/cutter/cutter" -msgstr "CUTTER_SOURCE_PATH=$HOME/work/cutter/cutter" - -msgid "ビルド環境の準備" -msgstr "ビルド環境の準備" - -msgid "" -"以下にGroongaのリリース作業を行うために事前にインストール しておくべきパッ" -"ケージを示します。" -msgstr "" -"以下にGroongaのリリース作業を行うために事前にインストール しておくべきパッ" -"ケージを示します。" - -msgid "" -"なお、ビルド環境としては Ubuntu 12.04 LTS(Precise Pangolin)を前提として説明し" -"ているため、その他の環境では適宜読み替えて下さい。::" -msgstr "" -"なお、ビルド環境としては Ubuntu 12.04 LTS(Precise Pangolin)を前提として説明し" -"ているため、その他の環境では適宜読み替えて下さい。::" - -msgid "" -"rinseのバージョンが古いとCentOS 5/6パッケージのビルドを行うことができませ" -"ん。 別途debパッケージを以下のコマンドを実行して最新版をインストールしま" -"す。::" -msgstr "" -"rinseのバージョンが古いとCentOS 5/6パッケージのビルドを行うことができませ" -"ん。 別途debパッケージを以下のコマンドを実行して最新版をインストールしま" -"す。::" - -msgid "また、rubyのrakeパッケージを以下のコマンドによりインストールします。::" -msgstr "また、rubyのrakeパッケージを以下のコマンドによりインストールします。::" - -msgid "パッケージ署名用秘密鍵のインポート" -msgstr "パッケージ署名用秘密鍵のインポート" - -msgid "" -"リリース作業ではRPMパッケージに対する署名を行います。 その際、パッケージ署名" -"用の鍵が必要です。" -msgstr "" -"リリース作業ではRPMパッケージに対する署名を行います。 その際、パッケージ署名" -"用の鍵が必要です。" - -msgid "" -"Groongaプロジェクトでは署名用の鍵をリリース担当者の公開鍵で暗号化してリポジト" -"リのpackages/ディレクトリ以下へと登録しています。" -msgstr "" -"Groongaプロジェクトでは署名用の鍵をリリース担当者の公開鍵で暗号化してリポジト" -"リのpackages/ディレクトリ以下へと登録しています。" - -msgid "" -"リリース担当者はリポジトリに登録された秘密鍵を復号した後に鍵のインポートを以" -"下のコマンドにて行います。::" -msgstr "" -"リリース担当者はリポジトリに登録された秘密鍵を復号した後に鍵のインポートを以" -"下のコマンドにて行います。::" - -msgid "" -"鍵のインポートが正常終了すると gpg --list-keys でGroongaの署名用の鍵を確認す" -"ることができます。::" -msgstr "" -"鍵のインポートが正常終了すると gpg --list-keys でGroongaの署名用の鍵を確認す" -"ることができます。::" - -msgid "" -"鍵をインポートしただけでは使用することができないため、インポートした鍵に対し" -"てtrust,signを行う必要があります。" -msgstr "" -"鍵をインポートしただけでは使用することができないため、インポートした鍵に対し" -"てtrust,signを行う必要があります。" - -msgid "以下のコマンドを実行して署名を行います。(途中の選択肢は省略)::" -msgstr "以下のコマンドを実行して署名を行います。(途中の選択肢は省略)::" - -msgid "" -"この作業は、新規にリリースを行うことになった担当者やパッケージに署名する鍵に" -"変更があった場合などに行います。" -msgstr "" -"この作業は、新規にリリースを行うことになった担当者やパッケージに署名する鍵に" -"変更があった場合などに行います。" - -msgid "リリース作業用ディレクトリの作成" -msgstr "リリース作業用ディレクトリの作成" - -msgid "" -"Groongaのリリース作業ではリリース専用の環境下(コンパイルフラグ)でビルドする必" -"要があります。" -msgstr "" -"Groongaのリリース作業ではリリース専用の環境下(コンパイルフラグ)でビルドする必" -"要があります。" - -msgid "" -"リリース時と開発時でディレクトリを分けずに作業することもできますが、誤ったコ" -"ンパイルフラグでリリースしてしまう危険があります。" -msgstr "" -"リリース時と開発時でディレクトリを分けずに作業することもできますが、誤ったコ" -"ンパイルフラグでリリースしてしまう危険があります。" - -msgid "" -"そのため、以降の説明では$GROONGA_DIR以下のディレクトリにリリース用の作業ディ" -"レクトリ(groonga.clean)としてソースコードをcloneしたものとして説明します。" -msgstr "" -"そのため、以降の説明では$GROONGA_DIR以下のディレクトリにリリース用の作業ディ" -"レクトリ(groonga.clean)としてソースコードをcloneしたものとして説明します。" - -msgid "" -"リリース用のクリーンな状態でソースコードを取得するために$GROONGA_DIRにて以下" -"のコマンドを実行します。::" -msgstr "" -"リリース用のクリーンな状態でソースコードを取得するために$GROONGA_DIRにて以下" -"のコマンドを実行します。::" - -msgid "この作業はリリース作業ごとに行います。" -msgstr "この作業はリリース作業ごとに行います。" - -msgid "変更点のまとめ" -msgstr "変更点のまとめ" - -msgid "" -"前回リリース時からの変更点を$GROONGA_CLONE_DIR/doc/source/news.txtにまとめま" -"す。 ここでまとめた内容についてはリリースアナウンスにも使用します。" -msgstr "" -"前回リリース時からの変更点を$GROONGA_CLONE_DIR/doc/source/news.txtにまとめま" -"す。 ここでまとめた内容についてはリリースアナウンスにも使用します。" - -msgid "前回リリースからの変更履歴を参照するには以下のコマンドを実行します。::" -msgstr "前回リリースからの変更履歴を参照するには以下のコマンドを実行します。::" - -msgid "" -"ログを^commitで検索しながら、以下の基準を目安として変更点を追記していきます。" -msgstr "" -"ログを^commitで検索しながら、以下の基準を目安として変更点を追記していきます。" - -msgid "含めるもの" -msgstr "含めるもの" - -msgid "ユーザへ影響するような変更" -msgstr "ユーザへ影響するような変更" - -msgid "互換性がなくなるような変更" -msgstr "互換性がなくなるような変更" - -msgid "含めないもの" -msgstr "含めないもの" - -msgid "内部的な変更(変数名の変更やらリファクタリング)" -msgstr "内部的な変更(変数名の変更やらリファクタリング)" - -msgid "Groongaのウェブサイトの取得" -msgstr "Groongaのウェブサイトの取得" - -msgid "" -"GroongaのウェブサイトのソースはGroonga同様にgithubにリポジトリを置いていま" -"す。" -msgstr "" -"GroongaのウェブサイトのソースはGroonga同様にgithubにリポジトリを置いていま" -"す。" - -msgid "" -"リリース作業では後述するコマンド(make update-latest-release)にてトップページ" -"のバージョンを置き換えることができるようになっています。" -msgstr "" -"リリース作業では後述するコマンド(make update-latest-release)にてトップページ" -"のバージョンを置き換えることができるようになっています。" - -msgid "" -"Groongaのウェブサイトのソースコードを$GROONGA_GITHUB_COM_PATHとして取得するた" -"めには、$GROONGA_DIRにて以下のコマンドを実行します。::" -msgstr "" -"Groongaのウェブサイトのソースコードを$GROONGA_GITHUB_COM_PATHとして取得するた" -"めには、$GROONGA_DIRにて以下のコマンドを実行します。::" - -msgid "" -"これで、$GROONGA_GITHUB_COM_PATHにgroonga.github.comのソースを取得できます。" -msgstr "" -"これで、$GROONGA_GITHUB_COM_PATHにgroonga.github.comのソースを取得できます。" - -msgid "cutterのソースコード取得" -msgstr "cutterのソースコード取得" - -msgid "Groongaのリリース作業では、cutterに含まれるスクリプトを使用しています。" -msgstr "" -"Groongaのリリース作業では、cutterに含まれるスクリプトを使用しています。" - -msgid "" -"そこであらかじめ用意しておいた$HOME/work/cutterディレクトリにてcutterのソース" -"コードを以下のコマンドにて取得します。::" -msgstr "" -"そこであらかじめ用意しておいた$HOME/work/cutterディレクトリにてcutterのソース" -"コードを以下のコマンドにて取得します。::" - -msgid "これで、$CUTTER_SOURCE_PATHディレクトリにcutterのソースを取得できます。" -msgstr "" -"これで、$CUTTER_SOURCE_PATHディレクトリにcutterのソースを取得できます。" - -msgid "configureスクリプトの生成" -msgstr "configureスクリプトの生成" - -msgid "" -"Groongaのソースコードをcloneした時点ではconfigureスクリプトが含まれておらず、" -"そのままmakeコマンドにてビルドすることができません。" -msgstr "" -"Groongaのソースコードをcloneした時点ではconfigureスクリプトが含まれておらず、" -"そのままmakeコマンドにてビルドすることができません。" - -msgid "$GROONGA_CLONE_DIRにてautogen.shを以下のように実行します。::" -msgstr "$GROONGA_CLONE_DIRにてautogen.shを以下のように実行します。::" - -msgid "このコマンドの実行により、configureスクリプトが生成されます。" -msgstr "このコマンドの実行により、configureスクリプトが生成されます。" - -msgid "configureスクリプトの実行" -msgstr "configureスクリプトの実行" - -msgid "Makefileを生成するためにconfigureスクリプトを実行します。" -msgstr "Makefileを生成するためにconfigureスクリプトを実行します。" - -msgid "" -"リリース用にビルドするためには以下のオプションを指定してconfigureを実行しま" -"す。::" -msgstr "" -"リリース用にビルドするためには以下のオプションを指定してconfigureを実行しま" -"す。::" - -msgid "" -"configureオプションである--with-groonga-github-com-pathにはGroongaのウェブサ" -"イトのリポジトリをcloneした場所を指定します。" -msgstr "" -"configureオプションである--with-groonga-github-com-pathにはGroongaのウェブサ" -"イトのリポジトリをcloneした場所を指定します。" - -msgid "" -"configureオプションである--with-cutter-source-pathにはcutterのソースをcloneし" -"た場所を指定します。" -msgstr "" -"configureオプションである--with-cutter-source-pathにはcutterのソースをcloneし" -"た場所を指定します。" - -msgid "" -"以下のようにGroongaのソースコードをcloneした先からの相対パスを指定することも" -"できます。::" -msgstr "" -"以下のようにGroongaのソースコードをcloneした先からの相対パスを指定することも" -"できます。::" - -msgid "" -"あらかじめpackagesユーザでpackages.groonga.orgにsshログインできることを確認し" -"ておいてください。" -msgstr "" -"あらかじめpackagesユーザでpackages.groonga.orgにsshログインできることを確認し" -"ておいてください。" - -msgid "ログイン可能であるかの確認は以下のようにコマンドを実行して行います。::" -msgstr "ログイン可能であるかの確認は以下のようにコマンドを実行して行います。::" - -msgid "make update-latest-releaseの実行" -msgstr "make update-latest-releaseの実行" - -msgid "" -"make update-latest-releaseコマンドでは、OLD_RELEASE_DATEに前回のリリースの日" -"付を、NEW_RELEASE_DATEに次回リリースの日付を指定します。" -msgstr "" -"make update-latest-releaseコマンドでは、OLD_RELEASE_DATEに前回のリリースの日" -"付を、NEW_RELEASE_DATEに次回リリースの日付を指定します。" - -msgid "2.0.2のリリースを行った際は以下のコマンドを実行しました。:: ::" -msgstr "2.0.2のリリースを行った際は以下のコマンドを実行しました。:: ::" - -msgid "" -"これにより、clone済みのGroongaのWebサイトのトップページのソース(index.html," -"ja/index.html)やRPMパッケージのspecファイルのバージョン表記などが更新されま" -"す。" -msgstr "" -"これにより、clone済みのGroongaのWebサイトのトップページのソース(index.html," -"ja/index.html)やRPMパッケージのspecファイルのバージョン表記などが更新されま" -"す。" - -msgid "make update-filesの実行" -msgstr "make update-filesの実行" - -msgid "" -"ロケールメッセージの更新や変更されたファイルのリスト等を更新するために以下の" -"コマンドを実行します。::" -msgstr "" -"ロケールメッセージの更新や変更されたファイルのリスト等を更新するために以下の" -"コマンドを実行します。::" - -msgid "" -"make update-filesを実行すると新規に追加されたファイルなどが各種.amファイルへ" -"とリストアップされます。" -msgstr "" -"make update-filesを実行すると新規に追加されたファイルなどが各種.amファイルへ" -"とリストアップされます。" - -msgid "リリースに必要なファイルですので漏れなくコミットします。" -msgstr "リリースに必要なファイルですので漏れなくコミットします。" - -msgid "make update-poの実行" -msgstr "make update-poの実行" - -msgid "" -"ドキュメントの最新版と各国語版の内容を同期するために、poファイルの更新を以下" -"のコマンドにて実行します。::" -msgstr "" -"ドキュメントの最新版と各国語版の内容を同期するために、poファイルの更新を以下" -"のコマンドにて実行します。::" - -msgid "" -"make update-poを実行すると、doc/locale/ja/LC_MESSAGES以下の各種.poファイルが" -"更新されます。" -msgstr "" -"make update-poを実行すると、doc/locale/ja/LC_MESSAGES以下の各種.poファイルが" -"更新されます。" - -msgid "poファイルの翻訳" -msgstr "poファイルの翻訳" - -msgid "make update-poコマンドの実行により更新した各種.poファイルを翻訳します。" -msgstr "" -"make update-poコマンドの実行により更新した各種.poファイルを翻訳します。" - -msgid "翻訳結果をHTMLで確認するために、以下のコマンドを実行します。::" -msgstr "翻訳結果をHTMLで確認するために、以下のコマンドを実行します。::" - -msgid "確認が完了したら、翻訳済みpoファイルをコミットします。" -msgstr "確認が完了したら、翻訳済みpoファイルをコミットします。" - -msgid "リリースタグの設定" -msgstr "リリースタグの設定" - -msgid "リリース用のタグを打つには以下のコマンドを実行します。::" -msgstr "リリース用のタグを打つには以下のコマンドを実行します。::" - -msgid "リリース用アーカイブファイルの作成" -msgstr "リリース用アーカイブファイルの作成" - -msgid "" -"リリース用のソースアーカイブファイルを作成するために以下のコマンドを" -"$GROONGA_CLONE_DIRにて実行します。::" -msgstr "" -"リリース用のソースアーカイブファイルを作成するために以下のコマンドを" -"$GROONGA_CLONE_DIRにて実行します。::" - -msgid "" -"これにより$GROONGA_CLONE_DIR/groonga-(バージョン).tar.gzが作成されます。" -msgstr "" -"これにより$GROONGA_CLONE_DIR/groonga-(バージョン).tar.gzが作成されます。" - -msgid "" -"タグを打つ前にmake distを行うとversionが古いままになることがあります。 すると" -"groonga --versionで表示されるバージョン表記が更新されないので注意が必要で" -"す。 make distで生成したtar.gzのversionおよびversion.shがタグと一致することを" -"確認するのが望ましいです。" -msgstr "" -"タグを打つ前にmake distを行うとversionが古いままになることがあります。 すると" -"groonga --versionで表示されるバージョン表記が更新されないので注意が必要で" -"す。 make distで生成したtar.gzのversionおよびversion.shがタグと一致することを" -"確認するのが望ましいです。" - -msgid "パッケージのビルド" -msgstr "パッケージのビルド" - -msgid "" -"リリース用のアーカイブファイルができたので、パッケージ化する作業を行います。" -msgstr "" -"リリース用のアーカイブファイルができたので、パッケージ化する作業を行います。" - -msgid "パッケージ化作業は以下の3種類を対象に行います。" -msgstr "パッケージ化作業は以下の3種類を対象に行います。" - -msgid "Debian系(.deb)" -msgstr "Debian系(.deb)" - -msgid "Red Hat系(.rpm)" -msgstr "Red Hat系(.rpm)" - -msgid "Windows系(.exe,.zip)" -msgstr "Windows系(.exe,.zip)" - -msgid "パッケージのビルドではいくつかのサブタスクから構成されています。" -msgstr "パッケージのビルドではいくつかのサブタスクから構成されています。" - -msgid "ビルド用パッケージのダウンロード" -msgstr "ビルド用パッケージのダウンロード" - -msgid "" -"debパッケージのビルドに必要なパッケージをダウンロードするには以下のコマンドを" -"実行します。::" -msgstr "" -"debパッケージのビルドに必要なパッケージをダウンロードするには以下のコマンドを" -"実行します。::" - -msgid "" -"これにより、lucid以降の関連する.debパッケージやソースアーカイブなどがカレント" -"ディレクトリ以下へとダウンロードされます。" -msgstr "" -"これにより、lucid以降の関連する.debパッケージやソースアーカイブなどがカレント" -"ディレクトリ以下へとダウンロードされます。" - -msgid "" -"rpmパッケージのビルドに必要なパッケージをダウンロードするには以下のコマンドを" -"実行します。::" -msgstr "" -"rpmパッケージのビルドに必要なパッケージをダウンロードするには以下のコマンドを" -"実行します。::" - -msgid "" -"これにより、GroongaやMySQLのRPM/SRPMパッケージなどがカレントディレクトリ以下" -"へとダウンロードされます。" -msgstr "" -"これにより、GroongaやMySQLのRPM/SRPMパッケージなどがカレントディレクトリ以下" -"へとダウンロードされます。" - -msgid "" -"windowsパッケージのビルドに必要なパッケージをダウンロードするには以下のコマン" -"ドを実行します。::" -msgstr "" -"windowsパッケージのビルドに必要なパッケージをダウンロードするには以下のコマン" -"ドを実行します。::" - -msgid "" -"これにより、Groongaのインストーラやzipアーカイブがカレントディレクトリ以下へ" -"とダウンロードされます。" -msgstr "" -"これにより、Groongaのインストーラやzipアーカイブがカレントディレクトリ以下へ" -"とダウンロードされます。" - -msgid "" -"sourceパッケージに必要なものをダウンロードするには以下のコマンドを実行しま" -"す。::" -msgstr "" -"sourceパッケージに必要なものをダウンロードするには以下のコマンドを実行しま" -"す。::" - -msgid "" -"これにより過去にリリースしたソースアーカイブ(.tar.gz)が packages/source/files" -"ディレクトリ以下へとダウンロードされます。" -msgstr "" -"これにより過去にリリースしたソースアーカイブ(.tar.gz)が packages/source/files" -"ディレクトリ以下へとダウンロードされます。" - -msgid "Debian系パッケージのビルド" -msgstr "Debian系パッケージのビルド" - -msgid "" -"Groongaのpackages/aptサブディレクトリに移動して、以下のコマンドを実行しま" -"す。::" -msgstr "" -"Groongaのpackages/aptサブディレクトリに移動して、以下のコマンドを実行しま" -"す。::" - -msgid "" -"make build PALALLEL=yesコマンドを実行すると、ディストリビューションのリリース" -"とアーキテクチャの組み合わせでビルドを平行して行うことができます。" -msgstr "" -"make build PALALLEL=yesコマンドを実行すると、ディストリビューションのリリース" -"とアーキテクチャの組み合わせでビルドを平行して行うことができます。" - -msgid "現在サポートされているのは以下の通りです。" -msgstr "現在サポートされているのは以下の通りです。" - -msgid "wheezy i386/amd64" -msgstr "wheezy i386/amd64" - -msgid "precise i386/amd64" -msgstr "precise i386/amd64" - -msgid "trusty i386/amd64" -msgstr "" - -msgid "utopic i386/amd64" -msgstr "" - -msgid "" -"正常にビルドが終了すると$GROONGA_CLONE_DIR/packages/apt/repositories配下に." -"debパッケージが生成されます。" -msgstr "" -"正常にビルドが終了すると$GROONGA_CLONE_DIR/packages/apt/repositories配下に." -"debパッケージが生成されます。" - -msgid "" -"make build ではまとめてビルドできないこともあります。 その場合にはディストリ" -"ビューションごとやアーキテクチャごとなど、個別にビルドすることで問題が発生し" -"ている箇所を切り分ける必要があります。" -msgstr "" -"make build ではまとめてビルドできないこともあります。 その場合にはディストリ" -"ビューションごとやアーキテクチャごとなど、個別にビルドすることで問題が発生し" -"ている箇所を切り分ける必要があります。" - -msgid "生成したパッケージへの署名を行うには以下のコマンドを実行します。::" -msgstr "生成したパッケージへの署名を行うには以下のコマンドを実行します。::" - -msgid "" -"リリース対象のファイルをリポジトリに反映するには以下のコマンドを実行しま" -"す。::" -msgstr "" -"リリース対象のファイルをリポジトリに反映するには以下のコマンドを実行しま" -"す。::" - -msgid "リポジトリにGnuPGで署名を行うために以下のコマンドを実行します。::" -msgstr "リポジトリにGnuPGで署名を行うために以下のコマンドを実行します。::" - -msgid "Red Hat系パッケージのビルド" -msgstr "Red Hat系パッケージのビルド" - -msgid "" -"Groongaのpackages/yumサブディレクトリに移動して、以下のコマンドを実行しま" -"す。::" -msgstr "" -"Groongaのpackages/yumサブディレクトリに移動して、以下のコマンドを実行しま" -"す。::" - -msgid "centos-5 i386/x86_64" -msgstr "centos-5 i386/x86_64" - -msgid "centos-6 i386/x86_64" -msgstr "centos-6 i386/x86_64" - -msgid "fedora-17 i386/x86_64" -msgstr "fedora-17 i386/x86_64" - -msgid "" -"ビルドが正常終了すると$GROONGA_CLONE_DIR/packages/yum/repositories配下にRPM" -"パッケージが生成されます。" -msgstr "" -"ビルドが正常終了すると$GROONGA_CLONE_DIR/packages/yum/repositories配下にRPM" -"パッケージが生成されます。" - -msgid "repositories/yum/centos/5/i386/Packages" -msgstr "repositories/yum/centos/5/i386/Packages" - -msgid "repositories/yum/centos/5/x86_64/Packages" -msgstr "repositories/yum/centos/5/x86_64/Packages" - -msgid "repositories/yum/centos/6/i386/Packages" -msgstr "repositories/yum/centos/6/i386/Packages" - -msgid "repositories/yum/centos/6/x86_64/Packages" -msgstr "repositories/yum/centos/6/x86_64/Packages" - -msgid "repositories/yum/fedora/17/i386/Packages" -msgstr "repositories/yum/fedora/17/i386/Packages" - -msgid "repositories/yum/fedora/17/x86_64/Packages" -msgstr "repositories/yum/fedora/17/x86_64/Packages" - -msgid "リリース対象のRPMに署名を行うには以下のコマンドを実行します。::" -msgstr "リリース対象のRPMに署名を行うには以下のコマンドを実行します。::" - -msgid "Windows用パッケージのビルド" -msgstr "Windows用パッケージのビルド" - -msgid "" -"packages/windowsサブディレクトリに移動して、以下のコマンドを実行します。::" -msgstr "" -"packages/windowsサブディレクトリに移動して、以下のコマンドを実行します。::" - -msgid "" -"make releaseを実行することでbuildからuploadまで一気に実行することができます" -"が、途中で失敗することもあるので順に実行することをおすすめします。" -msgstr "" -"make releaseを実行することでbuildからuploadまで一気に実行することができます" -"が、途中で失敗することもあるので順に実行することをおすすめします。" - -msgid "" -"make buildでクロスコンパイルを行います。 正常に終了するとdist-x64/dist-x86" -"ディレクトリ以下にx64/x86バイナリを作成します。" -msgstr "" -"make buildでクロスコンパイルを行います。 正常に終了するとdist-x64/dist-x86" -"ディレクトリ以下にx64/x86バイナリを作成します。" - -msgid "" -"make packageが正常に終了するとzipアーカイブをfilesディレクトリ以下に作成しま" -"す。" -msgstr "" -"make packageが正常に終了するとzipアーカイブをfilesディレクトリ以下に作成しま" -"す。" - -msgid "" -"make installerが正常に終了するとWindowsインストーラをfilesディレクトリ以下に" -"作成します。" -msgstr "" -"make installerが正常に終了するとWindowsインストーラをfilesディレクトリ以下に" -"作成します。" - -msgid "パッケージの動作確認" -msgstr "パッケージの動作確認" - -msgid "ビルドしたパッケージに対しリリース前の動作確認を行います。" -msgstr "ビルドしたパッケージに対しリリース前の動作確認を行います。" - -msgid "" -"Debian系もしくはRed Hat系の場合には本番環境へとアップロードする前にローカルの" -"aptないしyumのリポジトリを参照して正常に更新できることを確認します。" -msgstr "" -"Debian系もしくはRed Hat系の場合には本番環境へとアップロードする前にローカルの" -"aptないしyumのリポジトリを参照して正常に更新できることを確認します。" - -msgid "" -"ここでは以下のようにrubyを利用してリポジトリをwebサーバ経由で参照できるように" -"します。::" -msgstr "" -"ここでは以下のようにrubyを利用してリポジトリをwebサーバ経由で参照できるように" -"します。::" - -msgid "grntestの準備" -msgstr "grntestの準備" - -msgid "" -"grntestを実行するためにはGroongaのテストデータとgrntestのソースが必要です。" -msgstr "" -"grntestを実行するためにはGroongaのテストデータとgrntestのソースが必要です。" - -msgid "まずGroongaのソースを任意のディレクトリへと展開します。::" -msgstr "まずGroongaのソースを任意のディレクトリへと展開します。::" - -msgid "" -"次にGroongaのtest/functionディレクトリ以下にgrntestのソースを展開します。 つ" -"まりtest/function/grntestという名前でgrntestのソースを配置します。::" -msgstr "" -"次にGroongaのtest/functionディレクトリ以下にgrntestのソースを展開します。 つ" -"まりtest/function/grntestという名前でgrntestのソースを配置します。::" - -msgid "grntestの実行方法" -msgstr "grntestの実行方法" - -msgid "" -"grntestではGroongaコマンドを明示的にしていすることができます。 後述のパッケー" -"ジごとのgrntestによる動作確認では以下のようにして実行します。::" -msgstr "" -"grntestではGroongaコマンドを明示的にしていすることができます。 後述のパッケー" -"ジごとのgrntestによる動作確認では以下のようにして実行します。::" - -msgid "最後にgrntestによる実行結果が以下のようにまとめて表示されます。::" -msgstr "最後にgrntestによる実行結果が以下のようにまとめて表示されます。::" - -msgid "grntestでエラーが発生しないことを確認します。" -msgstr "grntestでエラーが発生しないことを確認します。" - -msgid "Debian系の場合" -msgstr "Debian系の場合" - -msgid "Debian系の場合の動作確認手順は以下の通りとなります。" -msgstr "Debian系の場合の動作確認手順は以下の通りとなります。" - -msgid "旧バージョンをchroot環境へとインストールする" -msgstr "旧バージョンをchroot環境へとインストールする" - -msgid "" -"chroot環境の/etc/hostsを書き換えてpackages.groonga.orgがホストを 参照するよう" -"に変更する" -msgstr "" -"chroot環境の/etc/hostsを書き換えてpackages.groonga.orgがホストを 参照するよう" -"に変更する" - -msgid "" -"ホストでwebサーバを起動してドキュメントルートをビルド環境のもの " -"(repositories/apt/packages)に設定する" -msgstr "" -"ホストでwebサーバを起動してドキュメントルートをビルド環境のもの " -"(repositories/apt/packages)に設定する" - -msgid "アップグレード手順を実行する" -msgstr "アップグレード手順を実行する" - -msgid "" -"grntestのアーカイブを展開してインストールしたバージョンでテストを実 行する" -msgstr "" -"grntestのアーカイブを展開してインストールしたバージョンでテストを実 行する" - -msgid "grntestの正常終了を確認する" -msgstr "grntestの正常終了を確認する" - -msgid "Red Hat系の場合" -msgstr "Red Hat系の場合" - -msgid "Red Hat系の場合の動作確認手順は以下の通りとなります。" -msgstr "Red Hat系の場合の動作確認手順は以下の通りとなります。" - -msgid "旧バージョンをchroot環境へとインストール" -msgstr "旧バージョンをchroot環境へとインストール" - -msgid "" -"chroot環境の/etc/hostsを書き換えてpackages.groonga.orgがホストを参照するよう" -"に変更する" -msgstr "" -"chroot環境の/etc/hostsを書き換えてpackages.groonga.orgがホストを参照するよう" -"に変更する" - -msgid "" -"ホストでwebサーバを起動してドキュメントルートをビルド環境のもの(packages/yum/" -"repositories)に設定する" -msgstr "" -"ホストでwebサーバを起動してドキュメントルートをビルド環境のもの(packages/yum/" -"repositories)に設定する" - -msgid "" -"grntestのアーカイブを展開してインストールしたバージョンでテストを実行する" -msgstr "" -"grntestのアーカイブを展開してインストールしたバージョンでテストを実行する" - -msgid "Windows向けの場合" -msgstr "Windows向けの場合" - -msgid "新規インストール/上書きインストールを行う" -msgstr "新規インストール/上書きインストールを行う" - -msgid "zipアーカイブも同様にしてgrntestを実行し動作確認を行います。" -msgstr "zipアーカイブも同様にしてgrntestを実行し動作確認を行います。" - -msgid "リリースアナウンスの作成" -msgstr "リリースアナウンスの作成" - -msgid "リリースの際にはリリースアナウンスを流して、Groongaを広く通知します。" -msgstr "リリースの際にはリリースアナウンスを流して、Groongaを広く通知します。" - -msgid "" -"news.txtに変更点をまとめましたが、それを元にリリースアナウンスを作成します。" -msgstr "" -"news.txtに変更点をまとめましたが、それを元にリリースアナウンスを作成します。" - -msgid "リリースアナウンスには以下を含めます。" -msgstr "リリースアナウンスには以下を含めます。" - -msgid "インストール方法へのリンク" -msgstr "インストール方法へのリンク" - -msgid "リリースのトピック紹介" -msgstr "リリースのトピック紹介" - -msgid "リリース変更点へのリンク" -msgstr "リリース変更点へのリンク" - -msgid "リリース変更点(news.txtの内容)" -msgstr "リリース変更点(news.txtの内容)" - -msgid "" -"リリースのトピック紹介では、これからGroongaを使う人へアピールする点や既存の" -"バージョンを利用している人がアップグレードする際に必要な情報を提供します。" -msgstr "" -"リリースのトピック紹介では、これからGroongaを使う人へアピールする点や既存の" -"バージョンを利用している人がアップグレードする際に必要な情報を提供します。" - -msgid "" -"非互換な変更が含まれるのであれば、回避方法等の案内を載せることも重要です。" -msgstr "" -"非互換な変更が含まれるのであれば、回避方法等の案内を載せることも重要です。" - -msgid "参考までに過去のリリースアナウンスへのリンクを以下に示します。" -msgstr "参考までに過去のリリースアナウンスへのリンクを以下に示します。" - -msgid "[Groonga-talk] [ANN] Groonga 2.0.2" -msgstr "[Groonga-talk] [ANN] Groonga 2.0.2" - -msgid "http://sourceforge.net/mailarchive/message.php?msg_id=29195195" -msgstr "http://sourceforge.net/mailarchive/message.php?msg_id=29195195" - -msgid "[groonga-dev,00794] [ANN] Groonga 2.0.2" -msgstr "[groonga-dev,00794] [ANN] Groonga 2.0.2" - -msgid "" -"http://sourceforge.jp/projects/groonga/lists/archive/dev/2012-April/000794." -"html" -msgstr "" -"http://sourceforge.jp/projects/groonga/lists/archive/dev/2012-April/000794." -"html" - -msgid "パッケージのアップロード" -msgstr "パッケージのアップロード" - -msgid "" -"動作確認が完了し、Debian系、Red Hat系、Windows向け、ソースコードそれぞれにお" -"いてパッケージやアーカイブのアップロードを行います。" -msgstr "" -"動作確認が完了し、Debian系、Red Hat系、Windows向け、ソースコードそれぞれにお" -"いてパッケージやアーカイブのアップロードを行います。" - -msgid "Debian系のパッケージのアップロードには以下のコマンドを実行します。::" -msgstr "Debian系のパッケージのアップロードには以下のコマンドを実行します。::" - -msgid "Red Hat系のパッケージのアップロードには以下のコマンドを実行します。::" -msgstr "Red Hat系のパッケージのアップロードには以下のコマンドを実行します。::" - -msgid "Windows向けのパッケージのアップロードには以下のコマンドを実行します。::" -msgstr "" -"Windows向けのパッケージのアップロードには以下のコマンドを実行します。::" - -msgid "ソースアーカイブのアップロードには以下のコマンドを実行します。::" -msgstr "ソースアーカイブのアップロードには以下のコマンドを実行します。::" - -msgid "" -"アップロードが正常終了すると、リリース対象のリポジトリデータやパッケージ、" -"アーカイブ等がpackages.groonga.orgへと反映されます。" -msgstr "" -"アップロードが正常終了すると、リリース対象のリポジトリデータやパッケージ、" -"アーカイブ等がpackages.groonga.orgへと反映されます。" - -msgid "blogroonga(ブログ)の更新" -msgstr "blogroonga(ブログ)の更新" - -msgid "" -"http://groonga.org/blog/ および http://groonga.org/blog/ にて公開されているリ" -"リース案内を作成します。" -msgstr "" -"http://groonga.org/blog/ および http://groonga.org/blog/ にて公開されているリ" -"リース案内を作成します。" - -msgid "基本的にはリリースアナウンスの内容をそのまま記載します。" -msgstr "基本的にはリリースアナウンスの内容をそのまま記載します。" - -msgid "cloneしたWebサイトのソースに対して以下のファイルを新規追加します。" -msgstr "cloneしたWebサイトのソースに対して以下のファイルを新規追加します。" - -msgid "groonga.github.com/en/_post/(リリース日)-release.textile" -msgstr "groonga.github.com/en/_post/(リリース日)-release.textile" - -msgid "groonga.github.com/ja/_post/(リリース日)-release.textile" -msgstr "groonga.github.com/ja/_post/(リリース日)-release.textile" - -msgid "" -"編集した内容をpushする前に確認したい場合にはjekyllおよびRedClothが必要です。 " -"インストールするには以下のコマンドを実行します。::" -msgstr "" -"編集した内容をpushする前に確認したい場合にはjekyllおよびRedClothが必要です。 " -"インストールするには以下のコマンドを実行します。::" - -msgid "" -"jekyllのインストールを行ったら、以下のコマンドでローカルにwebサーバを起動しま" -"す。::" -msgstr "" -"jekyllのインストールを行ったら、以下のコマンドでローカルにwebサーバを起動しま" -"す。::" - -msgid "" -"あとはブラウザにてhttp://localhost:4000にアクセスして内容に問題がないかを確認" -"します。" -msgstr "" -"あとはブラウザにてhttp://localhost:4000にアクセスして内容に問題がないかを確認" -"します。" - -msgid "" -"記事を非公開の状態でアップロードするには.textileファイルのpublished:をfalseに" -"設定します。::" -msgstr "" -"記事を非公開の状態でアップロードするには.textileファイルのpublished:をfalseに" -"設定します。::" - -msgid "ドキュメントのアップロード" -msgstr "ドキュメントのアップロード" - -msgid "" -"doc/source以下のドキュメントを更新、翻訳まで完了している状態で、ドキュメント" -"のアップロード作業を行います。" -msgstr "" -"doc/source以下のドキュメントを更新、翻訳まで完了している状態で、ドキュメント" -"のアップロード作業を行います。" - -msgid "そのためにはまず以下のコマンドを実行します。::" -msgstr "そのためにはまず以下のコマンドを実行します。::" - -msgid "" -"これによりcloneしておいたgroonga.github.comのdoc/locale以下に更新したドキュメ" -"ントがコピーされます。" -msgstr "" -"これによりcloneしておいたgroonga.github.comのdoc/locale以下に更新したドキュメ" -"ントがコピーされます。" - -msgid "" -"生成されているドキュメントに問題のないことを確認できたら、コミット、pushして" -"groonga.orgへと反映します。" -msgstr "" -"生成されているドキュメントに問題のないことを確認できたら、コミット、pushして" -"groonga.orgへと反映します。" - -msgid "Homebrewの更新" -msgstr "Homebrewの更新" - -msgid "" -"OS Xでのパッケージ管理方法として `Homebrew <http://brew.sh/>`_ があります。" -msgstr "" -"OS Xでのパッケージ管理方法として `Homebrew <http://brew.sh/>`_ があります。" - -msgid "" -"Groongaを簡単にインストールできるようにするために、Homebrewへpull requestを送" -"ります。" -msgstr "" -"Groongaを簡単にインストールできるようにするために、Homebrewへpull requestを送" -"ります。" - -msgid "https://github.com/mxcl/homebrew" -msgstr "https://github.com/mxcl/homebrew" - -msgid "" -"すでにGroongaのFormulaは取り込まれているので、リリースのたびにFormulaの内容を" -"更新する作業を実施します。" -msgstr "" -"すでにGroongaのFormulaは取り込まれているので、リリースのたびにFormulaの内容を" -"更新する作業を実施します。" - -msgid "Groonga 3.0.6のときは以下のように更新してpull requestを送りました。" -msgstr "Groonga 3.0.6のときは以下のように更新してpull requestを送りました。" - -msgid "https://github.com/mxcl/homebrew/pull/21456/files" -msgstr "https://github.com/mxcl/homebrew/pull/21456/files" - -msgid "" -"上記URLを参照するとわかるようにソースアーカイブのurlとsha1チェックサムを更新" -"します。" -msgstr "" -"上記URLを参照するとわかるようにソースアーカイブのurlとsha1チェックサムを更新" -"します。" - -msgid "リリースアナウンス" -msgstr "リリースアナウンス" - -msgid "作成したリリースアナウンスをメーリングリストへと流します。" -msgstr "作成したリリースアナウンスをメーリングリストへと流します。" - -msgid "groonga-dev groonga-dev �� lists.sourceforge.jp" -msgstr "groonga-dev groonga-dev �� lists.sourceforge.jp" - -msgid "Groonga-talk groonga-talk �� lists.sourceforge.net" -msgstr "Groonga-talk groonga-talk �� lists.sourceforge.net" - -msgid "Twitterでリリースアナウンスをする" -msgstr "Twitterでリリースアナウンスをする" - -msgid "" -"blogroongaのリリースエントリには「リンクをあなたのフォロワーに共有する」ため" -"のツイートボタンがあるので、そのボタンを使ってリリースアナウンスします。(画面" -"下部に配置されている)" -msgstr "" -"blogroongaのリリースエントリには「リンクをあなたのフォロワーに共有する」ため" -"のツイートボタンがあるので、そのボタンを使ってリリースアナウンスします。(画面" -"下部に配置されている)" - -msgid "" -"このボタンを経由する場合、ツイート内容に自動的にリリースタイトル(「groonga " -"2.0.8リリース」など)とblogroongaのリリースエントリのURLが挿入されます。" -msgstr "" -"このボタンを経由する場合、ツイート内容に自動的にリリースタイトル(「groonga " -"2.0.8リリース」など)とblogroongaのリリースエントリのURLが挿入されます。" - -msgid "" -"この作業はblogroongaの英語版、日本語版それぞれで行います。 あらかじめgroonga" -"アカウントでログインしておくとアナウンスを円滑に行うことができます。" -msgstr "" -"この作業はblogroongaの英語版、日本語版それぞれで行います。 あらかじめgroonga" -"アカウントでログインしておくとアナウンスを円滑に行うことができます。" - -msgid "以上でリリース作業は終了です。" -msgstr "以上でリリース作業は終了です。" - -msgid "リリース後にやること" -msgstr "リリース後にやること" - -msgid "リリースアナウンスを流し終えたら、次期バージョンの開発が始まります。" -msgstr "リリースアナウンスを流し終えたら、次期バージョンの開発が始まります。" - -msgid "Groonga プロジェクトの新規バージョン追加" -msgstr "Groonga プロジェクトの新規バージョン追加" - -msgid "Groonga のbase_versionの更新" -msgstr "Groonga のbase_versionの更新" - -msgid "" -"`Groonga プロジェクトの設定ページ <http://redmine.groonga.org/projects/" -"groonga/settings>`_ にて新規バージョンを追加します。(例: release-2.0.6)" -msgstr "" -"`Groonga プロジェクトの設定ページ <http://redmine.groonga.org/projects/" -"groonga/settings>`_ にて新規バージョンを追加します。(例: release-2.0.6)" - -msgid "Groonga バージョン更新" -msgstr "Groonga バージョン更新" - -msgid "$GROONGA_CLONE_DIRにて以下のコマンドを実行します。::" -msgstr "$GROONGA_CLONE_DIRにて以下のコマンドを実行します。::" - -msgid "" -"これにより$GROONGA_CLONE_DIR/base_versionが更新されるのでコミットしておきま" -"す。" -msgstr "" -"これにより$GROONGA_CLONE_DIR/base_versionが更新されるのでコミットしておきま" -"す。" - -msgid "base_versionはtar.gzなどのリリース用のファイル名で使用します。" -msgstr "base_versionはtar.gzなどのリリース用のファイル名で使用します。" - -msgid "ビルド時のTIPS" -msgstr "ビルド時のTIPS" - -msgid "ビルドを並列化したい" -msgstr "ビルドを並列化したい" - -msgid "" -"make build PALALLES=yesを指定するとchroot環境で並列にビルドを 実行できます。" -msgstr "" -"make build PALALLES=yesを指定するとchroot環境で並列にビルドを 実行できます。" - -msgid "特定の環境向けのみビルドしたい" -msgstr "特定の環境向けのみビルドしたい" - -msgid "" -"Debian系の場合、CODES,ARCHITECTURESオプションを明示的に指定することで、特定の" -"リリース、アーキテクチャのみビルドすることができます。" -msgstr "" -"Debian系の場合、CODES,ARCHITECTURESオプションを明示的に指定することで、特定の" -"リリース、アーキテクチャのみビルドすることができます。" - -msgid "squeezeのi386のみビルドしたい場合には以下のコマンドを実行します。::" -msgstr "squeezeのi386のみビルドしたい場合には以下のコマンドを実行します。::" - -msgid "" -"buildコマンド以外でも build-package-deb build-repository-debなどのサブタスク" -"でもARCHITECTURES,CODES指定は有効です。" -msgstr "" -"buildコマンド以外でも build-package-deb build-repository-debなどのサブタスク" -"でもARCHITECTURES,CODES指定は有効です。" - -msgid "" -"Red Hat系の場合、ARCHITECTURES,DISTRIBUTIONSオプションを明示的に指定すること" -"で、特定のリリース、アーキテクチャのみビルドすることができます。" -msgstr "" -"Red Hat系の場合、ARCHITECTURES,DISTRIBUTIONSオプションを明示的に指定すること" -"で、特定のリリース、アーキテクチャのみビルドすることができます。" - -msgid "fedoraのi386のみビルドしたい場合には以下のコマンドを実行します。::" -msgstr "fedoraのi386のみビルドしたい場合には以下のコマンドを実行します。::" - -msgid "" -"buildコマンド以外でも build-in-chroot build-repository-rpmなどのサブタスクで" -"もARCHITECTURES,DISTRIBUTIONSの指定は有効です。" -msgstr "" -"buildコマンド以外でも build-in-chroot build-repository-rpmなどのサブタスクで" -"もARCHITECTURES,DISTRIBUTIONSの指定は有効です。" - -msgid "" -"centosの場合、CENTOS_VERSIONSを指定することで特定のバージョンのみビルドするこ" -"とができます。" -msgstr "" -"centosの場合、CENTOS_VERSIONSを指定することで特定のバージョンのみビルドするこ" -"とができます。" - -msgid "パッケージの署名用のパスフレーズを知りたい" -msgstr "パッケージの署名用のパスフレーズを知りたい" - -msgid "" -"パッケージの署名に必要な秘密鍵のパスフレーズについては リリース担当者向けの秘" -"密鍵を復号したテキストの1行目に記載してあります。" -msgstr "" -"パッケージの署名に必要な秘密鍵のパスフレーズについては リリース担当者向けの秘" -"密鍵を復号したテキストの1行目に記載してあります。" - -msgid "バージョンを明示的に指定してドキュメントを生成したい" -msgstr "バージョンを明示的に指定してドキュメントを生成したい" - -msgid "" -"リリース後にドキュメントの一部を差し替えたい場合、特に何も指定しないと生成し" -"たHTMLに埋め込まれるバージョンが「v3.0.1-xxxxxドキュメント」となってしまうこ" -"とがあります。gitでのコミット時ハッシュの一部が使われるためです。" -msgstr "" -"リリース後にドキュメントの一部を差し替えたい場合、特に何も指定しないと生成し" -"たHTMLに埋め込まれるバージョンが「v3.0.1-xxxxxドキュメント」となってしまうこ" -"とがあります。gitでのコミット時ハッシュの一部が使われるためです。" - -msgid "" -"これを回避するには、以下のようにDOCUMENT_VERSIONやDOCUMENT_VERSION_FULLを明示" -"的に指定します。::" -msgstr "" -"これを回避するには、以下のようにDOCUMENT_VERSIONやDOCUMENT_VERSION_FULLを明示" -"的に指定します。::" - -msgid "Repository" -msgstr "Repository" - -msgid "" -"There is `the repository of groonga on GitHub <https://github.com/groonga/" -"groonga>`_. If you want to check-out groonga, type the below command::" -msgstr "" -"There is `the repository of groonga on GitHub <https://github.com/groonga/" -"groonga>`_. If you want to check-out groonga, type the below command::" - -msgid "" -"There is `the list of related projects of groonga <https://github.com/" -"groonga>`_ (grntest, fluent-plugin-groonga and so on)." -msgstr "" -"There is `the list of related projects of groonga <https://github.com/" -"groonga>`_ (grntest, fluent-plugin-groonga and so on)." - -msgid "テスト方法" -msgstr "テスト方法" - -msgid "テスト環境の構築" -msgstr "テスト環境の構築" - -msgid "Cutterのインストール" -msgstr "Cutterのインストール" - -msgid "Groongaは、テストのフレームワークとして Cutter_ を用いています。" -msgstr "Groongaは、テストのフレームワークとして Cutter_ を用いています。" - -msgid "" -"Cutterのインストール方法は プラットフォーム毎のCutterのインストール方法_ をご" -"覧下さい。" -msgstr "" -"Cutterのインストール方法は プラットフォーム毎のCutterのインストール方法_ をご" -"覧下さい。" - -msgid "lcovのインストール" -msgstr "lcovのインストール" - -msgid "" -"カバレッジ情報を計測するためには、lcov 1.6以上が必要です。DebianやUbuntuでは" -"以下のようにしてインストールできます。::" -msgstr "" -"カバレッジ情報を計測するためには、lcov 1.6以上が必要です。DebianやUbuntuでは" -"以下のようにしてインストールできます。::" - -msgid "clangのインストール" -msgstr "clangのインストール" - -msgid "" -"ソースコードの静的解析を行うためには、clang(scan-build)をインストールする必要" -"があります。DebianやUbuntuでは以下のようにしてインストールできます。::" -msgstr "" -"ソースコードの静的解析を行うためには、clang(scan-build)をインストールする必要" -"があります。DebianやUbuntuでは以下のようにしてインストールできます。::" - -msgid "libmemcachedのインストール" -msgstr "libmemcachedのインストール" - -msgid "" -"memcachedのバイナリプロトコルのテストを動作させるためには、libmemcachedの導入" -"が必要です。squeeze以降のDebianやKarmic以降のUubntuでは以下の用にしてインス" -"トールできます。::" -msgstr "" -"memcachedのバイナリプロトコルのテストを動作させるためには、libmemcachedの導入" -"が必要です。squeeze以降のDebianやKarmic以降のUubntuでは以下の用にしてインス" -"トールできます。::" - -msgid "テストの動作" -msgstr "テストの動作" - -msgid "Groongaのトップディレクトリで、以下のコマンドを実行します。::" -msgstr "Groongaのトップディレクトリで、以下のコマンドを実行します。::" - -msgid "カバレッジ情報" -msgstr "カバレッジ情報" - -msgid "" -"すると、coverageディレクトリ以下に、カバレッジ情報が入ったhtmlが出力されま" -"す。" -msgstr "" -"すると、coverageディレクトリ以下に、カバレッジ情報が入ったhtmlが出力されま" -"す。" - -msgid "" -"カバレッジには、Lines/Functions/Branchesの3つの対象があります。それぞれ、行／" -"関数／分岐に対応します。Functionsがもっとも重要な対象です。すべての関数がテス" -"トされるようになっていることを心がけてください。" -msgstr "" -"カバレッジには、Lines/Functions/Branchesの3つの対象があります。それぞれ、行／" -"関数／分岐に対応します。Functionsがもっとも重要な対象です。すべての関数がテス" -"トされるようになっていることを心がけてください。" - -msgid "" -"テストがカバーしていない部分の編集は慎重に行ってください。また、テストがカ" -"バーしている部分を増やすことも重要です。" -msgstr "" -"テストがカバーしていない部分の編集は慎重に行ってください。また、テストがカ" -"バーしている部分を増やすことも重要です。" - -msgid "様々なテスト" -msgstr "様々なテスト" - -msgid "" -"テストは、test/unitディレクトリにおいて、./run-test.shを実行することによって" -"も行えます。run-test.shはいくつかのオプションをとります。詳細は、./run-test." -"sh --helpを実行しヘルプをご覧ください。" -msgstr "" -"テストは、test/unitディレクトリにおいて、./run-test.shを実行することによって" -"も行えます。run-test.shはいくつかのオプションをとります。詳細は、./run-test." -"sh --helpを実行しヘルプをご覧ください。" - -msgid "特定のテスト関数のみテストする" -msgstr "特定のテスト関数のみテストする" - -msgid "" -"特定のテスト関数(Cutterではテストと呼ぶ)のみをテストすることができます。" -msgstr "" -"特定のテスト関数(Cutterではテストと呼ぶ)のみをテストすることができます。" - -msgid "実行例::" -msgstr "実行例::" - -msgid "特定のテストファイルのみテストする" -msgstr "特定のテストファイルのみテストする" - -msgid "" -"特定のテストファイル(Cutterではテストケースと呼ぶ)のみテストすることができま" -"す。" -msgstr "" -"特定のテストファイル(Cutterではテストケースと呼ぶ)のみテストすることができま" -"す。" - -msgid "不正メモリアクセス・メモリリーク検出" -msgstr "不正メモリアクセス・メモリリーク検出" - -msgid "" -"環境変数CUTTER_CHECK_LEAKをyesと設定すると、valgrindを用いて不正メモリアクセ" -"スやメモリリークを検出しつつ、テストを動作させることができます。" -msgstr "" -"環境変数CUTTER_CHECK_LEAKをyesと設定すると、valgrindを用いて不正メモリアクセ" -"スやメモリリークを検出しつつ、テストを動作させることができます。" - -msgid "run-test.shのみならず、make checkでも利用可能です。" -msgstr "run-test.shのみならず、make checkでも利用可能です。" - -msgid "デバッガ上でのテスト実行" -msgstr "デバッガ上でのテスト実行" - -msgid "" -"環境変数CUTTER_DEBUGをyesと設定すると、テストが実行できる環境が整ったgdbが実" -"行されます。gdb上でrunを行うと、テストの実行が開始されます。" -msgstr "" -"環境変数CUTTER_DEBUGをyesと設定すると、テストが実行できる環境が整ったgdbが実" -"行されます。gdb上でrunを行うと、テストの実行が開始されます。" - -msgid "静的解析" -msgstr "静的解析" - -msgid "" -"scan-buildを用いて、ソースコードの静的解析を行うことができます。scan_buildと" -"いうディレクトリに解析結果のhtmlが出力されます。::" -msgstr "" -"scan-buildを用いて、ソースコードの静的解析を行うことができます。scan_buildと" -"いうディレクトリに解析結果のhtmlが出力されます。::" - -msgid "configureは１度のみ実行する必要があります。" -msgstr "configureは１度のみ実行する必要があります。" - -msgid "How to contribute in documentation topics" -msgstr "How to contribute in documentation topics" - -msgid "We use Sphinx_ for documentation tool." -msgstr "We use Sphinx_ for documentation tool." - -msgid "C API" -msgstr "C API" - -msgid "" -"We still have C API documentation in include/groonga.h. But we want to move " -"them into doc/source/c-api/\\*.txt. We welcome to you help us by moving C " -"API documentation." -msgstr "" -"We still have C API documentation in include/groonga.h. But we want to move " -"them into doc/source/c-api/\\*.txt. We welcome to you help us by moving C " -"API documentation." - -msgid "We will use `the C domain markup`_ of Sphinx." -msgstr "We will use `the C domain markup`_ of Sphinx." - -msgid "I18N" -msgstr "I18N" - -msgid "" -"We only had documentation in Japanese. We start to support I18N " -"documentation by gettext based `Sphinx I18N feature`_. We'll use English as " -"base language and translate English into other languages such as Japanese. " -"We'll put all documentations into doc/source/ and process them by Sphinx." -msgstr "" -"We only had documentation in Japanese. We start to support I18N " -"documentation by gettext based `Sphinx I18N feature`_. We'll use English as " -"base language and translate English into other languages such as Japanese. " -"We'll put all documentations into doc/source/ and process them by Sphinx." - -msgid "" -"But we still use Japanese in doc/source/ for now. We need to translate " -"Japanese documentation in doc/source/ into English. We welcome to you help " -"us by translating documentation." -msgstr "" -"But we still use Japanese in doc/source/ for now. We need to translate " -"Japanese documentation in doc/source/ into English. We welcome to you help " -"us by translating documentation." - -msgid "Translation flow" -msgstr "Translation flow" - -msgid "After doc/source/\\*.txt are updated, we can start translation." -msgstr "After doc/source/\\*.txt are updated, we can start translation." - -msgid "Here is a translation flow:" -msgstr "Here is a translation flow:" - -msgid "Clone groonga repository." -msgstr "Clone groonga repository." - -msgid "Update .po files." -msgstr "Update .po files." - -msgid "Edit .po files." -msgstr "Edit .po files." - -msgid "Generate HTML files." -msgstr "Generate HTML files." - -msgid "Confirm HTML output." -msgstr "Confirm HTML output." - -msgid "Repeat 2.-4. until you get good result." -msgstr "Repeat 2.-4. until you get good result." - -msgid "Send your works to us!" -msgstr "Send your works to us!" - -msgid "" -"Here are command lines to do the above flow. Following sections describes " -"details." -msgstr "" -"Here are command lines to do the above flow. Following sections describes " -"details." - -msgid "How to clone groonga repository" -msgstr "How to clone groonga repository" - -msgid "" -"First, please fork groonga repository on GitHub. You just access https://" -"github.com/groonga/groonga and press `Fork` button. Now you can clone your " -"groonga repository::" -msgstr "" -"First, please fork groonga repository on GitHub. You just access https://" -"github.com/groonga/groonga and press `Fork` button. Now you can clone your " -"groonga repository::" - -msgid "Then you need to configure your cloned repository::" -msgstr "Then you need to configure your cloned repository::" - -msgid "The above steps are just needed at the first setup." -msgstr "The above steps are just needed at the first setup." - -msgid "" -"If you have troubles on the above steps, you can use source files available " -"on http://packages.groonga.org/source/groonga/ ." -msgstr "" -"If you have troubles on the above steps, you can use source files available " -"on http://packages.groonga.org/source/groonga/ ." - -msgid "How to update .po files" -msgstr "How to update .po files" - -msgid "" -"You can update .po files by running `make update` on doc/locale/${LANGUAGE}/" -"LC_MESSAGES. (Please substitute `${LANGUAGE}` with your language code such " -"as 'ja'.)::" -msgstr "" -"You can update .po files by running `make update` on doc/locale/${LANGUAGE}/" -"LC_MESSAGES. (Please substitute `${LANGUAGE}` with your language code such " -"as 'ja'.)::" - -msgid "How to edit .po" -msgstr "How to edit .po" - -msgid "" -"There are some tools to edit .po files. .po files are just text. So you can " -"use your favorite editor. Here is a specialized editor for .po file edit " -"list." -msgstr "" -"There are some tools to edit .po files. .po files are just text. So you can " -"use your favorite editor. Here is a specialized editor for .po file edit " -"list." - -msgid "Emacs's po-mode_" -msgstr "Emacs's po-mode_" - -msgid "It is bundled in gettext." -msgstr "It is bundled in gettext." - -msgid "It is a .po editor and works on many platform." -msgstr "It is a .po editor and works on many platform." - -msgid "Poedit_" -msgstr "Poedit_" - -msgid "It is also a .po editor and is implemented as Eclipse plugin." -msgstr "It is also a .po editor and is implemented as Eclipse plugin." - -msgid "gted" -msgstr "gted" - -msgid "How to generate HTML files" -msgstr "How to generate HTML files" - -msgid "" -"You can generate HTML files with updated .po files by running `make html` on " -"doc/locale/${LANGUAGE}. (Please substitute `${LANGUAGE}` with your language " -"code such as 'ja'.)::" -msgstr "" -"You can generate HTML files with updated .po files by running `make html` on " -"doc/locale/${LANGUAGE}. (Please substitute `${LANGUAGE}` with your language " -"code such as 'ja'.)::" - -msgid "" -"You can also generate HTML files for all languages by running `make html` on " -"doc/locale::" -msgstr "" -"You can also generate HTML files for all languages by running `make html` on " -"doc/locale::" - -msgid "" -".mo files are updated automatically by `make html`. So you don't care about ." -"mo files." -msgstr "" -".mo files are updated automatically by `make html`. So you don't care about ." -"mo files." - -msgid "How to confirm HTML output" -msgstr "How to confirm HTML output" - -msgid "" -"HTML files are generated in doc/locale/${LANGUAGE}/html/. (Please substitute " -"`${LANGUAGE}` with your language code such as 'ja'.) You can confirm HTML " -"output by your favorite browser::" -msgstr "" -"HTML files are generated in doc/locale/${LANGUAGE}/html/. (Please substitute " -"`${LANGUAGE}` with your language code such as 'ja'.) You can confirm HTML " -"output by your favorite browser::" - -msgid "How to send your works" -msgstr "How to send your works" - -msgid "" -"We can receive your works via pull request on GitHub or E-mail attachment " -"patch or .po files themselves." -msgstr "" -"We can receive your works via pull request on GitHub or E-mail attachment " -"patch or .po files themselves." - -msgid "How to send pull request" -msgstr "How to send pull request" - -msgid "Here are command lines to send pull request::" -msgstr "Here are command lines to send pull request::" - -msgid "" -"Now you can send pull request on GitHub. You just access your repository " -"page on GitHub and press `Pull Request` button." -msgstr "" -"Now you can send pull request on GitHub. You just access your repository " -"page on GitHub and press `Pull Request` button." - -msgid "" -"`Help.GitHub - Sending pull requests <http://help.github.com/pull-requests/" -">`_." -msgstr "" - -msgid "How to send patch" -msgstr "How to send patch" - -msgid "Here are command lines to create patch::" -msgstr "Here are command lines to create patch::" - -msgid "" -"You can find 000X-YYY.patch files in the current directory. Please send " -"those files to us!" -msgstr "" -"You can find 000X-YYY.patch files in the current directory. Please send " -"those files to us!" - -msgid ":doc:`/community` describes our contact information." -msgstr ":doc:`/community` describes our contact information." - -msgid "How to send .po files" -msgstr "How to send .po files" - -msgid "" -"Please archive doc/locale/${LANGUAGE}/LC_MESSAGES/ (Please substitute `" -"${LANGUAGE}` with your language code such as 'ja'.) and send it to us! We " -"extract and merge them to the groonga repository." -msgstr "" -"Please archive doc/locale/${LANGUAGE}/LC_MESSAGES/ (Please substitute `" -"${LANGUAGE}` with your language code such as 'ja'.) and send it to us! We " -"extract and merge them to the groonga repository." - -msgid "How to add new language" -msgstr "How to add new language" - -msgid "Here are command lines to add new translation language::" -msgstr "Here are command lines to add new translation language::" - -msgid "Please substitute `${LANGUAGE}` with your language code such as 'ja'." -msgstr "Please substitute `${LANGUAGE}` with your language code such as 'ja'." - -msgid "" -"`Codes for the Representation of Names of Languages <http://www.loc.gov/" -"standards/iso639-2/php/English_list.php>`_." -msgstr "" - -msgid "Introduction" -msgstr "Introduction" - -msgid "" -"This documentation describes about how to write, generate and manage Groonga " -"documentation." -msgstr "" -"This documentation describes about how to write, generate and manage Groonga " -"documentation." - -msgid "Install depended software" -msgstr "" - -msgid "Groonga uses Sphinx_ as documentation tool." -msgstr "" - -msgid "Here are command lines to install Sphinx." -msgstr "" - -msgid "Debian GNU/Linux, Ubuntu::" -msgstr "Debian GNU/Linux, Ubuntu::" - -msgid "CentOS, Fedora::" -msgstr "CentOS, Fedora::" - -msgid "OS X::" -msgstr "OS X::" - -msgid "Run ``configure`` with ``--enable-document``" -msgstr "Run ``configure`` with ``--enable-document``" - -msgid "" -"Groonga disables documentation generation by default. You need to enable it " -"explicitly by adding ``--enable-document`` option to ``configure``::" -msgstr "" -"Groonga disables documentation generation by default. You need to enable it " -"explicitly by adding ``--enable-document`` option to ``configure``::" - -msgid "Now, your Groonga build is documentation ready." -msgstr "Now, your Groonga build is documentation ready." - -msgid "Generate HTML" -msgstr "Generate HTML" - -msgid "You can generate HTML by the following command::" -msgstr "You can generate HTML by the following command::" - -msgid "You can find generated HTML documentation at ``doc/locale/en/html/``." -msgstr "You can find generated HTML documentation at ``doc/locale/en/html/``." - -msgid "Update" -msgstr "Update" - -msgid "" -"You can find sources of documentation at ``doc/source/``. The sources should " -"be written in English. See :doc:`i18n` about how to translate documentation." -msgstr "" -"You can find sources of documentation at ``doc/source/``. The sources should " -"be written in English. See :doc:`i18n` about how to translate documentation." - -msgid "" -"You can update the target file when you update the existing documentation " -"file." -msgstr "" -"You can update the target file when you update the existing documentation " -"file." - -msgid "" -"You need to update file list after you add a new file, change file path and " -"delete existing file. You can update file list by the following command::" -msgstr "" -"You need to update file list after you add a new file, change file path and " -"delete existing file. You can update file list by the following command::" - -msgid "The command updates ``doc/files.am``." -msgstr "The command updates ``doc/files.am``." - -msgid "How to report a bug" -msgstr "How to report a bug" - -msgid "There are two ways to report a bug:" -msgstr "There are two ways to report a bug:" - -msgid "Submit a bug to the issue tracker" -msgstr "Submit a bug to the issue tracker" - -msgid "Report a bug to the mailing list" -msgstr "Report a bug to the mailing list" - -msgid "You can use either way It makes no difference to us." -msgstr "You can use either way It makes no difference to us." - -msgid "" -"Groonga project uses `GitHub issue tracker <https://github.com/groonga/" -"groonga/issues>`_." -msgstr "" - -msgid "You can use English or Japanese to report a bug." -msgstr "" - -msgid "" -"Groonga project has :doc:`/community` for discussing about groonga. Please " -"send a mail that describes a bug." -msgstr "" -"Groonga project has :doc:`/community` for discussing about groonga. Please " -"send a mail that describes a bug." Deleted: doc/locale/en/LC_MESSAGES/development.po (+0 -147) 100644 =================================================================== --- doc/locale/en/LC_MESSAGES/development.po 2015-03-25 14:48:34 +0900 (a2049e3) +++ /dev/null @@ -1,147 +0,0 @@ -# -*- po -*- -# English translations for Groonga package. -# Copyright (C) 2009-2014, Brazil, Inc -# This file is distributed under the same license as the Groonga package. -# Kouhei Sutou <kou �� clear-code.com>, 2014. -# -msgid "" -msgstr "" -"Project-Id-Version: Groonga 4.0.1\n" -"Report-Msgid-Bugs-To: \n" -"PO-Revision-Date: 2014-11-26 19:03+0900\n" -"Last-Translator: Kouhei Sutou <kou �� clear-code.com>\n" -"Language-Team: English\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" - -msgid "Development" -msgstr "Development" - -msgid "" -"This section describes about developing with Groonga. You may develop an " -"application that uses Groonga as its database, a library that uses " -"libgroonga, language bindings of libgroonga and so on." -msgstr "" -"This section describes about developing with Groonga. You may develop an " -"application that uses Groonga as its database, a library that uses " -"libgroonga, language bindings of libgroonga and so on." - -msgid "Travis CI" -msgstr "Travis CI" - -msgid "" -"This section describes about using Groonga on `Travis CI <http://travis-ci." -"org/>`_. Travis CI is a hosted continuous integration service for the open " -"source community." -msgstr "" -"This section describes about using Groonga on `Travis CI <http://travis-ci." -"org/>`_. Travis CI is a hosted continuous integration service for the open " -"source community." - -msgid "" -"You can use Travis CI for your open source software. This section only " -"describes about Groonga related configuration. See `Travis CI: Documentation " -"<http://about.travis-ci.org/docs/>`_ about general Travis CI." -msgstr "" -"You can use Travis CI for your open source software. This section only " -"describes about Groonga related configuration. See `Travis CI: Documentation " -"<http://about.travis-ci.org/docs/>`_ about general Travis CI." - -msgid "Configuration" -msgstr "Configuration" - -msgid "" -"Travis CI is running on 64-bit Ubuntu 12.04 LTS Server Edition. (See `Travis " -"CI: About Travis CI Environment <http://about.travis-ci.org/docs/user/ci-" -"environment/>`_.) You can use apt-line for Ubuntu 12.04 LTS provided by " -"Groonga project to install Groonga on Travis CI." -msgstr "" -"Travis CI is running on 64-bit Ubuntu 12.04 LTS Server Edition. (See `Travis " -"CI: About Travis CI Environment <http://about.travis-ci.org/docs/user/ci-" -"environment/>`_.) You can use apt-line for Ubuntu 12.04 LTS provided by " -"Groonga project to install Groonga on Travis CI." - -msgid "" -"You can custom build lifecycle by ``.travis.yml``. (See `Travis CI: " -"Conifugration your Travis CI build with .travis.yml <http://about.travis-ci." -"org/docs/user/build-configuration/>`_.) You can use ``before_install`` hook " -"or ``install`` hook. You should use ``before_install`` if your software uses " -"a language that is supported by Travis CI such as Ruby. You should use " -"``install`` otherwise." -msgstr "" -"You can custom build lifecycle by ``.travis.yml``. (See `Travis CI: " -"Conifugration your Travis CI build with .travis.yml <http://about.travis-ci." -"org/docs/user/build-configuration/>`_.) You can use ``before_install`` hook " -"or ``install`` hook. You should use ``before_install`` if your software uses " -"a language that is supported by Travis CI such as Ruby. You should use " -"``install`` otherwise." - -msgid "Add the following ``before_install`` configuration to ``.travis.yml``::" -msgstr "" -"Add the following ``before_install`` configuration to ``.travis.yml``::" - -msgid "" -"If you need to use ``install`` hook instead of ``before_install``, you just " -"substitute ``before_install:`` with ``install:``." -msgstr "" -"If you need to use ``install`` hook instead of ``before_install``, you just " -"substitute ``before_install:`` with ``install:``." - -msgid "With the above configuration, you can use Groonga for your build." -msgstr "With the above configuration, you can use Groonga for your build." - -msgid "Examples" -msgstr "Examples" - -msgid "Here are open source software that use Groonga on Travis CI:" -msgstr "" - -msgid "`rroonga <http://ranguba.org/#about-rroonga>`_ (Ruby bindings)" -msgstr "`rroonga <http://ranguba.org/#about-rroonga>`_ (Ruby bindings)" - -msgid "`rroonga on Travis CI <http://travis-ci.org/#!/ranguba/rroonga>`_" -msgstr "`rroonga on Travis CI <http://travis-ci.org/#!/ranguba/rroonga>`_" - -msgid "" -"`.travis.yml for rroonga <https://github.com/ranguba/rroonga/blob/master/." -"travis.yml>`_" -msgstr "" -"`.travis.yml for rroonga <https://github.com/ranguba/rroonga/blob/master/." -"travis.yml>`_" - -msgid "`nroonga <http://nroonga.github.com/>`_ (node.js bindings)" -msgstr "`nroonga <http://nroonga.github.com/>`_ (node.js bindings)" - -msgid "`nroonga on Travis CI <http://travis-ci.org/#!/nroonga/nroonga>`_" -msgstr "`nroonga on Travis CI <http://travis-ci.org/#!/nroonga/nroonga>`_" - -msgid "" -"`.travis.yml for nroonga <https://github.com/nroonga/nroonga/blob/master/." -"travis.yml>`_" -msgstr "" -"`.travis.yml for nroonga <https://github.com/nroonga/nroonga/blob/master/." -"travis.yml>`_" - -msgid "" -"`logaling-command <http://logaling.github.com/>`_ (A glossary management " -"command line tool)" -msgstr "" -"`logaling-command <http://logaling.github.com/>`_ (A glossary management " -"command line tool)" - -msgid "" -"`logaling-command on Travis CI <http://travis-ci.org/#!/logaling/logaling-" -"command>`_" -msgstr "" -"`logaling-command on Travis CI <http://travis-ci.org/#!/logaling/logaling-" -"command>`_" - -msgid "" -"`.travis.yml for logaling-command <https://github.com/logaling/logaling-" -"command/blob/master/.travis.yml>`_" -msgstr "" -"`.travis.yml for logaling-command <https://github.com/logaling/logaling-" -"command/blob/master/.travis.yml>`_" Deleted: doc/locale/en/LC_MESSAGES/index.po (+0 -33) 100644 =================================================================== --- doc/locale/en/LC_MESSAGES/index.po 2015-03-25 14:48:34 +0900 (37c34c0) +++ /dev/null @@ -1,33 +0,0 @@ -# -*- po -*- -# English translations for Groonga package. -# Copyright (C) 2009-2014, Brazil, Inc -# This file is distributed under the same license as the Groonga package. -# Kouhei Sutou <kou �� clear-code.com>, 2014. -# -msgid "" -msgstr "" -"Project-Id-Version: Groonga 4.0.1\n" -"Report-Msgid-Bugs-To: \n" -"PO-Revision-Date: 2014-05-23 12:44+0900\n" -"Last-Translator: Kouhei Sutou <kou �� clear-code.com>\n" -"Language-Team: English\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" - -msgid "Groonga documentation" -msgstr "Groonga documentation" - -msgid ":doc:`news`" -msgstr ":doc:`news`" - -msgid ":ref:`genindex`" -msgstr ":ref:`genindex`" - -msgid ":ref:`modindex`" -msgstr ":ref:`modindex`" - -msgid ":ref:`search`" -msgstr ":ref:`search`" Deleted: doc/locale/en/LC_MESSAGES/install.po (+0 -835) 100644 =================================================================== --- doc/locale/en/LC_MESSAGES/install.po 2015-03-25 14:48:34 +0900 (1149d2c) +++ /dev/null @@ -1,835 +0,0 @@ -# -*- po -*- -# English translations for Groonga package. -# Copyright (C) 2009-2014, Brazil, Inc -# This file is distributed under the same license as the Groonga package. -# Kouhei Sutou <kou �� clear-code.com>, 2014. -# -msgid "" -msgstr "" -"Project-Id-Version: Groonga 4.0.3\n" -"Report-Msgid-Bugs-To: \n" -"PO-Revision-Date: 2015-01-28 13:21+0900\n" -"Last-Translator: Kouhei Sutou <kou �� clear-code.com>\n" -"Language-Team: English\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" - -msgid "Install" -msgstr "Install" - -msgid "" -"This section describes how to install Groonga on each environment. There are " -"packages for major platforms. It's recommended that you use package instead " -"of building Groonga by yourself. But don't warry. There is a document about " -"building Groonga from source." -msgstr "" -"This section describes how to install Groonga on each environment. There are " -"packages for major platforms. It's recommended that you use package instead " -"of building Groonga by yourself. But don't warry. There is a document about " -"building Groonga from source." - -msgid "" -"We distribute both 32-bit and 64-bit packages but we strongly recommend a 64-" -"bit package for server. You should use a 32-bit package just only for tests " -"or development. You will encounter an out of memory error with a 32-bit " -"package even if you just process medium size data." -msgstr "" -"We distribute both 32-bit and 64-bit packages but we strongly recommend a 64-" -"bit package for server. You should use a 32-bit package just only for tests " -"or development. You will encounter an out of memory error with a 32-bit " -"package even if you just process medium size data." - -msgid "CentOS" -msgstr "CentOS" - -msgid "" -"This section describes how to install Groonga related RPM packages on " -"CentOS. You can install them by ``yum``." -msgstr "" -"This section describes how to install Groonga related RPM packages on " -"CentOS. You can install them by ``yum``." - -msgid "CentOS 5" -msgstr "CentOS 5" - -msgid "Install::" -msgstr "Install::" - -msgid "" -"If you want to use `MeCab <http://mecab.sourceforge.net/>`_ as a tokenizer, " -"install groonga-tokenizer-mecab package." -msgstr "" -"If you want to use `MeCab <http://mecab.sourceforge.net/>`_ as a tokenizer, " -"install groonga-tokenizer-mecab package." - -msgid "Install groonga-tokenizer-mecab package::" -msgstr "Install groonga-tokenizer-mecab package::" - -msgid "" -"There is a package that provides `Munin <http://munin-monitoring.org/>`_ " -"plugins. If you want to monitor Groonga status by Munin, install groonga-" -"munin-plugins package." -msgstr "" -"There is a package that provides `Munin <http://munin-monitoring.org/>`_ " -"plugins. If you want to monitor Groonga status by Munin, install groonga-" -"munin-plugins package." - -msgid "" -"Groonga-munin-plugins package requires munin-node package that isn't " -"included in the official CentOS repository. You need to enable `Repoforge " -"(RPMforge) <http://repoforge.org/>`_ repository or `EPEL <http://" -"fedoraproject.org/wiki/EPEL>`_ repository to install it by ``yum``." -msgstr "" -"Groonga-munin-plugins package requires munin-node package that isn't " -"included in the official CentOS repository. You need to enable `Repoforge " -"(RPMforge) <http://repoforge.org/>`_ repository or `EPEL <http://" -"fedoraproject.org/wiki/EPEL>`_ repository to install it by ``yum``." - -msgid "Enable Repoforge (RPMforge) repository on i386 environment::" -msgstr "Enable Repoforge (RPMforge) repository on i386 environment::" - -msgid "Enable Repoforge (RPMforge) repository on x86_64 environment::" -msgstr "Enable Repoforge (RPMforge) repository on x86_64 environment::" - -msgid "Enable EPEL repository on any environment::" -msgstr "Enable EPEL repository on any environment::" - -msgid "Install groonga-munin-plugins package::" -msgstr "Install groonga-munin-plugins package::" - -msgid "" -"There is a package that provides MySQL compatible normalizer as Groonga " -"plugins. If you want to use that one, install groonga-normalizer-mysql " -"package." -msgstr "" -"There is a package that provides MySQL compatible normalizer as Groonga " -"plugins. If you want to use that one, install groonga-normalizer-mysql " -"package." - -msgid "Install groonga-normalizer-mysql package::" -msgstr "Install groonga-normalizer-mysql package::" - -msgid "CentOS 6" -msgstr "CentOS 6" - -msgid "" -"Groonga-munin-plugins package requires munin-node package that isn't " -"included in the official CentOS repository. You need to enable `EPEL <http://" -"fedoraproject.org/wiki/EPEL>`_ repository to install it by ``yum``." -msgstr "" -"Groonga-munin-plugins package requires munin-node package that isn't " -"included in the official CentOS repository. You need to enable `EPEL <http://" -"fedoraproject.org/wiki/EPEL>`_ repository to install it by ``yum``." - -msgid "CentOS 7" -msgstr "" - -msgid "Enable EPEL repository::" -msgstr "" - -msgid "Build from source" -msgstr "Build from source" - -msgid "Install required packages to build Groonga::" -msgstr "Install required packages to build Groonga::" - -msgid "Download source::" -msgstr "Download source::" - -msgid "Configure (see :ref:`source-configure` about ``configure`` options)::" -msgstr "Configure (see :ref:`source-configure` about ``configure`` options)::" - -msgid "Build::" -msgstr "Build::" - -msgid "Debian GNU/Linux" -msgstr "Debian GNU/Linux" - -msgid "" -"This section describes how to install Groonga related deb packages on Debian " -"GNU/Linux. You can install them by ``apt``." -msgstr "" -"This section describes how to install Groonga related deb packages on Debian " -"GNU/Linux. You can install them by ``apt``." - -msgid "wheezy" -msgstr "wheezy" - -msgid "Add the Groonga apt repository." -msgstr "Add the Groonga apt repository." - -msgid "/etc/apt/sources.list.d/groonga.list::" -msgstr "/etc/apt/sources.list.d/groonga.list::" - -msgid "" -"If you want to use ``TokenFilterStem`` as a token filter, install groonga-" -"token-filter-stem package." -msgstr "" - -msgid "Install groonga-token-filter-stem package::" -msgstr "" - -msgid "" -"There is a package that provides `Munin <http://munin-monitoring.org/>`_ " -"plugins. If you want to monitor groonga status by Munin, install groonga-" -"munin-plugins package." -msgstr "" -"There is a package that provides `Munin <http://munin-monitoring.org/>`_ " -"plugins. If you want to monitor groonga status by Munin, install groonga-" -"munin-plugins package." - -msgid "" -"There is a package that provides MySQL compatible normalizer as groonga " -"plugins. If you want to use that one, install groonga-normalizer-mysql " -"package." -msgstr "" -"There is a package that provides MySQL compatible normalizer as groonga " -"plugins. If you want to use that one, install groonga-normalizer-mysql " -"package." - -msgid "Fedora" -msgstr "Fedora" - -msgid "" -"This section describes how to install Groonga related RPM packages on " -"Fedora. You can install them by ``yum``." -msgstr "" -"This section describes how to install Groonga related RPM packages on " -"Fedora. You can install them by ``yum``." - -msgid "" -"Since Groonga 3.0.2 release, Groonga related RPM pakcages are in the " -"official Fedora yum repository (Fedora 18). So you can use them instead of " -"the Groonga yum repository now. There is some exceptions to use the Groonga " -"yum repository because mecab dictionaries (mecab-ipadic or mecab-jumandic) " -"are provided by the Groonga yum repository." -msgstr "" - -msgid "Fedora 20" -msgstr "Fedora 20" - -msgid "" -"Note that additional packages such as ``mecab-dic`` and ``mecab-jumandic`` " -"packages require to install ``groonga-release`` package which provides the " -"Groonga yum repository beforehand::" -msgstr "" - -msgid "Then install MeCab dictionary. (mecab-ipadic or mecab-jumandic)" -msgstr "Then install MeCab dictionary. (mecab-ipadic or mecab-jumandic)" - -msgid "Install IPA dictionary::" -msgstr "Install IPA dictionary::" - -msgid "Or install Juman dictionary::" -msgstr "Or install Juman dictionary::" - -msgid "Mac OS X" -msgstr "Mac OS X" - -msgid "" -"This section describes how to install Groonga on Mac OS X. You can install " -"Groonga by `MacPorts <http://www.macports.org/>`__ or `Homebrew <http://mxcl." -"github.com/homebrew/>`__." -msgstr "" - -msgid "MacPorts" -msgstr "MacPorts" - -msgid "Homebrew" -msgstr "Homebrew" - -msgid "" -"If you want to use `MeCab <http://mecab.sourceforge.net/>`_ as a tokenizer, " -"specify ``--with-mecab`` option::" -msgstr "" -"If you want to use `MeCab <http://mecab.sourceforge.net/>`_ as a tokenizer, " -"specify ``--with-mecab`` option::" - -msgid "Install `Xcode <https://developer.apple.com/xcode/>`_." -msgstr "Install `Xcode <https://developer.apple.com/xcode/>`_." - -msgid "Others" -msgstr "Others" - -msgid "" -"This section describes how to install Groonga from source on UNIX like " -"environment." -msgstr "" -"This section describes how to install Groonga from source on UNIX like " -"environment." - -msgid "" -"To get more detail about installing Groonga from source on the specific " -"environment, find the document for the specific environment from :doc:`/" -"install`." -msgstr "" -"To get more detail about installing Groonga from source on the specific " -"environment, find the document for the specific environment from :doc:`/" -"install`." - -msgid "Dependencies" -msgstr "Dependencies" - -msgid "" -"Groonga doesn't require any special libraries but requires some tools for " -"build." -msgstr "" -"Groonga doesn't require any special libraries but requires some tools for " -"build." - -msgid "Tools" -msgstr "Tools" - -msgid "Here are required tools:" -msgstr "Here are required tools:" - -msgid "``wget``, ``curl`` or Web browser for downloading source archive" -msgstr "``wget``, ``curl`` or Web browser for downloading source archive" - -msgid "``tar`` and ``gzip`` for extracting source archive" -msgstr "``tar`` and ``gzip`` for extracting source archive" - -msgid "shell (many shells such as ``dash``, ``bash`` and ``zsh`` will work)" -msgstr "shell (many shells such as ``dash``, ``bash`` and ``zsh`` will work)" - -msgid "" -"C compiler and C++ compiler (``gcc`` and ``g++`` are supported but other " -"compilers may work)" -msgstr "" -"C compiler and C++ compiler (``gcc`` and ``g++`` are supported but other " -"compilers may work)" - -msgid "``make`` (GNU make is supported but other make like BSD make will work)" -msgstr "" -"``make`` (GNU make is supported but other make like BSD make will work)" - -msgid "You must get them ready." -msgstr "You must get them ready." - -msgid "" -"You can use `CMake <http://www.cmake.org/>`_ instead of shell but this " -"document doesn't describe about building with CMake." -msgstr "" -"You can use `CMake <http://www.cmake.org/>`_ instead of shell but this " -"document doesn't describe about building with CMake." - -msgid "Here are optional tools:" -msgstr "Here are optional tools:" - -msgid "" -"`pkg-config <http://www.freedesktop.org/wiki/Software/pkg-config>`_ for " -"detecting libraries" -msgstr "" -"`pkg-config <http://www.freedesktop.org/wiki/Software/pkg-config>`_ for " -"detecting libraries" - -msgid "`sudo <http://www.gratisoft.us/sudo/>`_ for installing built groonga" -msgstr "`sudo <http://www.gratisoft.us/sudo/>`_ for installing built groonga" - -msgid "You must get them ready if you want to use optional libraries." -msgstr "You must get them ready if you want to use optional libraries." - -msgid "Libraries" -msgstr "Libraries" - -msgid "All libraries are optional. Here are optional libraries:" -msgstr "All libraries are optional. Here are optional libraries:" - -msgid "" -"`MeCab <http://mecab.sourceforge.net/>`_ for tokenizing full-text search " -"target document by morphological analysis" -msgstr "" -"`MeCab <http://mecab.sourceforge.net/>`_ for tokenizing full-text search " -"target document by morphological analysis" - -msgid "" -"`KyTea <http://www.phontron.com/kytea/>`_ for tokenizing full-text search " -"target document by morphological analysis" -msgstr "" -"`KyTea <http://www.phontron.com/kytea/>`_ for tokenizing full-text search " -"target document by morphological analysis" - -msgid "`ZeroMQ <http://www.zeromq.org/>`_ for :doc:`/reference/suggest`" -msgstr "`ZeroMQ <http://www.zeromq.org/>`_ for :doc:`/reference/suggest`" - -msgid "`libevent <http://libevent.org/>`_ for :doc:`/reference/suggest`" -msgstr "`libevent <http://libevent.org/>`_ for :doc:`/reference/suggest`" - -msgid "" -"`MessagePack <http://msgpack.org/>`_ for supporting MessagePack output and :" -"doc:`/reference/suggest`" -msgstr "" -"`MessagePack <http://msgpack.org/>`_ for supporting MessagePack output and :" -"doc:`/reference/suggest`" - -msgid "" -"`libedit <http://www.thrysoee.dk/editline/>`_ for command line editing in :" -"doc:`/reference/executables/groonga`" -msgstr "" -"`libedit <http://www.thrysoee.dk/editline/>`_ for command line editing in :" -"doc:`/reference/executables/groonga`" - -msgid "`zlib <http://zlib.net/>`_ for compressing column value" -msgstr "`zlib <http://zlib.net/>`_ for compressing column value" - -msgid "`LZ4 <https://code.google.com/p/lz4/>`_ for compressing column value" -msgstr "" - -msgid "" -"If you want to use those all or some libraries, you need to install them " -"before installing Groonga." -msgstr "" -"If you want to use those all or some libraries, you need to install them " -"before installing Groonga." - -msgid "" -"Groonga uses GNU build system. So the following is the simplest build steps::" -msgstr "" -"Groonga uses GNU build system. So the following is the simplest build steps::" - -msgid "" -"After the above steps, :doc:`/reference/executables/groonga` is found in ``/" -"usr/local/bin/groonga``." -msgstr "" -"After the above steps, :doc:`/reference/executables/groonga` is found in ``/" -"usr/local/bin/groonga``." - -msgid "" -"The default build will work well but you can customize groonga at " -"``configure`` step." -msgstr "" -"The default build will work well but you can customize groonga at " -"``configure`` step." - -msgid "The following describes details about each step." -msgstr "The following describes details about each step." - -msgid "``configure``" -msgstr "``configure``" - -msgid "" -"First, you need to run ``configure``. Here are important ``configure`` " -"options:" -msgstr "" -"First, you need to run ``configure``. Here are important ``configure`` " -"options:" - -msgid "``--prefix=PATH``" -msgstr "``--prefix=PATH``" - -msgid "" -"Specifies the install base directory. Groonga related files are installed " -"under ``${PATH}/`` directory." -msgstr "" -"Specifies the install base directory. Groonga related files are installed " -"under ``${PATH}/`` directory." - -msgid "" -"The default is ``/usr/local``. In this case, :doc:`/reference/executables/" -"groonga` is installed into ``/usr/local/bin/groonga``." -msgstr "" -"The default is ``/usr/local``. In this case, :doc:`/reference/executables/" -"groonga` is installed into ``/usr/local/bin/groonga``." - -msgid "" -"Here is an example that installs Groonga into ``~/local`` for an user use " -"instead of system wide use::" -msgstr "" -"Here is an example that installs Groonga into ``~/local`` for an user use " -"instead of system wide use::" - -msgid "``--localstatedir=PATH``" -msgstr "``--localstatedir=PATH``" - -msgid "" -"Specifies the base directory to place modifiable file such as log file, PID " -"file and database files. For example, log file is placed at ``${PATH}/log/" -"groonga.log``." -msgstr "" -"Specifies the base directory to place modifiable file such as log file, PID " -"file and database files. For example, log file is placed at ``${PATH}/log/" -"groonga.log``." - -msgid "The default is ``/usr/local/var``." -msgstr "The default is ``/usr/local/var``." - -msgid "" -"Here is an example that system wide ``/var`` is used for modifiable files::" -msgstr "" -"Here is an example that system wide ``/var`` is used for modifiable files::" - -msgid "``--with-log-path=PATH``" -msgstr "``--with-log-path=PATH``" - -msgid "" -"Specifies the default log file path. You can override the default log path " -"is :doc:`/reference/executables/groonga` command's ``--log-path`` command " -"line option. So this option is not critical build option. It's just for " -"convenient." -msgstr "" -"Specifies the default log file path. You can override the default log path " -"is :doc:`/reference/executables/groonga` command's ``--log-path`` command " -"line option. So this option is not critical build option. It's just for " -"convenient." - -msgid "" -"The default is ``/usr/local/var/log/groonga.log``. The ``/usr/local/var`` " -"part is changed by ``--localstatedir`` option." -msgstr "" - -msgid "" -"Here is an example that log file is placed into shared NFS directory ``/nfs/" -"log/groonga.log``::" -msgstr "" -"Here is an example that log file is placed into shared NFS directory ``/nfs/" -"log/groonga.log``::" - -msgid "``--with-default-encoding=ENCODING``" -msgstr "``--with-default-encoding=ENCODING``" - -msgid "" -"Specifies the default encoding. Available encodings are ``euc_jp``, " -"``sjis``, ``utf8``, ``latin1``, ``koi8r`` and ``none``." -msgstr "" -"Specifies the default encoding. Available encodings are ``euc_jp``, " -"``sjis``, ``utf8``, ``latin1``, ``koi8r`` and ``none``." - -msgid "The default is ``utf-8``." -msgstr "The default is ``utf-8``." - -msgid "Here is an example that Shift_JIS is used as the default encoding::" -msgstr "Here is an example that Shift_JIS is used as the default encoding::" - -msgid "``--with-match-escalation-threshold=NUMBER``" -msgstr "``--with-match-escalation-threshold=NUMBER``" - -msgid "" -"Specifies the default match escalation threshold. See :ref:`match-escalation-" -"threshold` about match escalation threshold. -1 means that match operation " -"never escalate." -msgstr "" -"Specifies the default match escalation threshold. See :ref:`match-escalation-" -"threshold` about match escalation threshold. -1 means that match operation " -"never escalate." - -msgid "The default is 0." -msgstr "The default is 0." - -msgid "Here is an example that match escalation isn't used by default::" -msgstr "Here is an example that match escalation isn't used by default::" - -msgid "``--with-zlib``" -msgstr "``--with-zlib``" - -msgid "Enables column value compression by zlib." -msgstr "Enables column value compression by zlib." - -msgid "The default is disabled." -msgstr "The default is disabled." - -msgid "Here is an example that enables column value compression by zlib::" -msgstr "Here is an example that enables column value compression by zlib::" - -msgid "``--with-lz4``" -msgstr "" - -msgid "Enables column value compression by LZ4." -msgstr "" - -msgid "Here is an example that enables column value compression by LZ4::" -msgstr "" - -msgid "``--with-message-pack=MESSAGE_PACK_INSTALL_PREFIX``" -msgstr "``--with-message-pack=MESSAGE_PACK_INSTALL_PREFIX``" - -msgid "" -"Specifies where MessagePack is installed. If MessagePack isn't installed " -"with ``--prefix=/usr``, you need to specify this option with path that you " -"use for building MessagePack." -msgstr "" -"Specifies where MessagePack is installed. If MessagePack isn't installed " -"with ``--prefix=/usr``, you need to specify this option with path that you " -"use for building MessagePack." - -msgid "" -"If you installed MessagePack with ``--prefix=$HOME/local`` option, you " -"sholud specify ``--with-message-pack=$HOME/local`` to groonga's " -"``configure``." -msgstr "" -"If you installed MessagePack with ``--prefix=$HOME/local`` option, you " -"sholud specify ``--with-message-pack=$HOME/local`` to groonga's " -"``configure``." - -msgid "The default is ``/usr``." -msgstr "The default is ``/usr``." - -msgid "" -"Here is an example that uses MessagePack built with ``--prefix=$HOME/local`` " -"option::" -msgstr "" -"Here is an example that uses MessagePack built with ``--prefix=$HOME/local`` " -"option::" - -msgid "``--with-munin-plugins``" -msgstr "``--with-munin-plugins``" - -msgid "" -"Installs Munin plugins for Groonga. They are installed into ``${PREFIX}/" -"share/groonga/munin/plugins/``." -msgstr "" -"Installs Munin plugins for Groonga. They are installed into ``${PREFIX}/" -"share/groonga/munin/plugins/``." - -msgid "Those plugins are not installed by default." -msgstr "Those plugins are not installed by default." - -msgid "Here is an example that installs Munin plugins for Groonga::" -msgstr "Here is an example that installs Munin plugins for Groonga::" - -msgid "``--with-package-platform=PLATFORM``" -msgstr "``--with-package-platform=PLATFORM``" - -msgid "" -"Installs platform specific system management files such as init script. " -"Available platforms are ``redhat`` and ``fedora``. ``redhat`` is for Red Hat " -"and Red Hat clone distributions such as CentOS. ``fedora`` is for Fedora." -msgstr "" -"Installs platform specific system management files such as init script. " -"Available platforms are ``redhat`` and ``fedora``. ``redhat`` is for Red Hat " -"and Red Hat clone distributions such as CentOS. ``fedora`` is for Fedora." - -msgid "Those system management files are not installed by default." -msgstr "Those system management files are not installed by default." - -msgid "" -"Here is an example that installs CentOS specific system management files::" -msgstr "" -"Here is an example that installs CentOS specific system management files::" - -msgid "``--help``" -msgstr "``--help``" - -msgid "Shows all ``configure`` options." -msgstr "Shows all ``configure`` options." - -msgid "``make``" -msgstr "``make``" - -msgid "``configure`` is succeeded, you can build groonga by ``make``::" -msgstr "``configure`` is succeeded, you can build groonga by ``make``::" - -msgid "" -"If you have multi cores CPU, you can make faster by using ``-j`` option. If " -"you have 4 cores CPU, it's good for using ``-j4`` option::" -msgstr "" -"If you have multi cores CPU, you can make faster by using ``-j`` option. If " -"you have 4 cores CPU, it's good for using ``-j4`` option::" - -msgid "" -"If you get some errors by ``make``, please report them to us: :doc:`/" -"contribution/report`" -msgstr "" -"If you get some errors by ``make``, please report them to us: :doc:`/" -"contribution/report`" - -msgid "``make install``" -msgstr "``make install``" - -msgid "Now, you can install built Groonga!::" -msgstr "Now, you can install built Groonga!::" - -msgid "" -"If you have write permission for ``${PREFIX}``, you don't need to use " -"``sudo``. e.g. ``--prefix=$HOME/local`` case. In this case, use ``make " -"install``::" -msgstr "" -"If you have write permission for ``${PREFIX}``, you don't need to use " -"``sudo``. e.g. ``--prefix=$HOME/local`` case. In this case, use ``make " -"install``::" - -msgid "" -"``groonga`` package is the minimum set of fulltext search engine. If you " -"want to use Groonga for server use, you can install additional preconfigured " -"packages." -msgstr "" - -msgid "There are two packages for server use." -msgstr "" - -msgid "groonga-httpd (nginx and HTTP protocol based server package)" -msgstr "groonga-httpd (nginx and HTTP protocol based server package)" - -msgid "groonga-server-gqtp (GQTP protocol based server package)" -msgstr "groonga-server-gqtp (GQTP protocol based server package)" - -msgid "See :doc:`/server` section about details." -msgstr "See :doc:`/server` section about details." - -msgid "Oracle Solaris" -msgstr "Oracle Solaris" - -msgid "" -"This section describes how to install Groonga from source on Oracle Solaris." -msgstr "" -"This section describes how to install Groonga from source on Oracle Solaris." - -msgid "Oracle Solaris 11" -msgstr "Oracle Solaris 11" - -msgid "" -"Configure with ``CFLAGS=\"-m64\" CXXFLAGS=\"-m64\"`` variables. They are " -"needed for building 64-bit version. To build 32-bit version, just remove " -"those variables. (see :ref:`source-configure` about ``configure`` options)::" -msgstr "" -"Configure with ``CFLAGS=\"-m64\" CXXFLAGS=\"-m64\"`` variables. They are " -"needed for building 64-bit version. To build 32-bit version, just remove " -"those variables. (see :ref:`source-configure` about ``configure`` options)::" - -msgid "Ubuntu" -msgstr "Ubuntu" - -msgid "" -"This section describes how to install Groonga related deb packages on " -"Ubuntu. You can install them by ``apt``." -msgstr "" -"This section describes how to install Groonga related deb packages on " -"Ubuntu. You can install them by ``apt``." - -msgid "PPA (Personal Package Archive)" -msgstr "PPA (Personal Package Archive)" - -msgid "" -"The Groonga APT repository for Ubuntu uses PPA (Personal Package Archive) on " -"Launchpad. You can install Groonga by APT from the PPA." -msgstr "" -"The Groonga APT repository for Ubuntu uses PPA (Personal Package Archive) on " -"Launchpad. You can install Groonga by APT from the PPA." - -msgid "Here are supported Ubuntu versions:" -msgstr "Here are supported Ubuntu versions:" - -msgid "12.04 LTS Precise Pangolin" -msgstr "12.04 LTS Precise Pangolin" - -msgid "14.04 LTS Trusty Tahr" -msgstr "14.04 LTS Trusty Tahr" - -msgid "14.10 Utopic Unicorn" -msgstr "" - -msgid "Enable the universe repository to install Groonga::" -msgstr "Enable the universe repository to install Groonga::" - -msgid "Add the ``ppa:groonga/ppa`` PPA to your system::" -msgstr "Add the ``ppa:groonga/ppa`` PPA to your system::" - -msgid "Windows" -msgstr "Windows" - -msgid "" -"This section describes how to install Groonga on Windows. You can install " -"Groogna by extracting a zip package or running an installer." -msgstr "" -"This section describes how to install Groonga on Windows. You can install " -"Groogna by extracting a zip package or running an installer." - -msgid "Installer" -msgstr "Installer" - -msgid "" -"For 32-bit environment, download x86 executable binary from packages.groonga." -"org:" -msgstr "" -"For 32-bit environment, download x86 executable binary from packages.groonga." -"org:" - -msgid "http://packages.groonga.org/windows/groonga/groonga-5.0.1-x86.exe" -msgstr "" - -msgid "Then run it." -msgstr "Then run it." - -msgid "" -"For 64-bit environment, download x64 executable binary from packages.goronga." -"org:" -msgstr "" -"For 64-bit environment, download x64 executable binary from packages.goronga." -"org:" - -msgid "http://packages.groonga.org/windows/groonga/groonga-5.0.1-x64.exe" -msgstr "" - -msgid "" -"Use command prompt in start menu to run :doc:`/reference/executables/" -"groonga`." -msgstr "" -"Use command prompt in start menu to run :doc:`/reference/executables/" -"groonga`." - -msgid "zip" -msgstr "zip" - -msgid "" -"For 32-bit environment, download x86 zip archive from packages.groonga.org:" -msgstr "" -"For 32-bit environment, download x86 zip archive from packages.groonga.org:" - -msgid "http://packages.groonga.org/windows/groonga/groonga-5.0.1-x86.zip" -msgstr "" - -msgid "Then extract it." -msgstr "Then extract it." - -msgid "" -"For 64-bit environment, download x64 zip archive from packages.groonga.org:" -msgstr "" -"For 64-bit environment, download x64 zip archive from packages.groonga.org:" - -msgid "http://packages.groonga.org/windows/groonga/groonga-5.0.1-x64.zip" -msgstr "" - -msgid "You can find :doc:`/reference/executables/groonga` in ``bin`` folder." -msgstr "You can find :doc:`/reference/executables/groonga` in ``bin`` folder." - -msgid "" -"First, you need to install required tools for building Groonga on Windows. " -"Here are required tools:" -msgstr "" -"First, you need to install required tools for building Groonga on Windows. " -"Here are required tools:" - -msgid "" -"`Microsoft Visual Studio 2010 Express <http://www.microsoft.com/japan/msdn/" -"vstudio/express/>`_" -msgstr "" -"`Microsoft Visual Studio 2010 Express <http://www.microsoft.com/japan/msdn/" -"vstudio/express/>`_" - -msgid "`CMake <http://www.cmake.org/>`_" -msgstr "`CMake <http://www.cmake.org/>`_" - -msgid "Download zipped source from packages.groonga.org:" -msgstr "Download zipped source from packages.groonga.org:" - -msgid "http://packages.groonga.org/source/groonga/groonga-5.0.1.zip" -msgstr "" - -msgid "Move to the Groonga's source folder::" -msgstr "Move to the Groonga's source folder::" - -msgid "" -"Configure by ``cmake``. The following commnad line is for 64-bit version. To " -"build 32-bit version, use ``-G \"Visual Studio 10\"`` parameter instead::" -msgstr "" -"Configure by ``cmake``. The following commnad line is for 64-bit version. To " -"build 32-bit version, use ``-G \"Visual Studio 10\"`` parameter instead::" - -msgid "" -"After the above steps, :doc:`/reference/executables/groonga` is found in ``c:" -"\\groonga\\bin\\groonga.exe``." -msgstr "" -"After the above steps, :doc:`/reference/executables/groonga` is found in ``c:" -"\\groonga\\bin\\groonga.exe``." Deleted: doc/locale/en/LC_MESSAGES/limitations.po (+0 -65) 100644 =================================================================== --- doc/locale/en/LC_MESSAGES/limitations.po 2015-03-25 14:48:34 +0900 (14c9d78) +++ /dev/null @@ -1,65 +0,0 @@ -# -*- po -*- -# English translations for Groonga package. -# Copyright (C) 2009-2014, Brazil, Inc -# This file is distributed under the same license as the Groonga package. -# Kouhei Sutou <kou �� clear-code.com>, 2014. -# -msgid "" -msgstr "" -"Project-Id-Version: Groonga 4.0.1\n" -"Report-Msgid-Bugs-To: \n" -"PO-Revision-Date: 2014-11-26 19:07+0900\n" -"Last-Translator: Kouhei Sutou <kou �� clear-code.com>\n" -"Language-Team: English\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" - -msgid "Limitations" -msgstr "Limitations" - -msgid "Groonga has some limitations." -msgstr "Groonga has some limitations." - -msgid "Limitations of table" -msgstr "Limitations of table" - -msgid "A table has the following limitations." -msgstr "A table has the following limitations." - -msgid "The maximum one key size: 4096Bytes" -msgstr "The maximum one key size: 4096Bytes" - -msgid "The maximum total size of keys: 4GBytes" -msgstr "The maximum total size of keys: 4GBytes" - -msgid "The maximum number of records: 268,435,455 (more than 268 million)" -msgstr "The maximum number of records: 268,435,455 (more than 268 million)" - -msgid "Keep in mind that these limitations may vary depending on conditions." -msgstr "Keep in mind that these limitations may vary depending on conditions." - -msgid "Limitations of indexing" -msgstr "Limitations of indexing" - -msgid "A full-text index has the following limitations." -msgstr "A full-text index has the following limitations." - -msgid "" -"The maximum number of distinct terms: 268,435,455 (more than 268 million)" -msgstr "" -"The maximum number of distinct terms: 268,435,455 (more than 268 million)" - -msgid "The maximum index size: 256GBytes" -msgstr "The maximum index size: 256GBytes" - -msgid "Limitations of column" -msgstr "Limitations of column" - -msgid "A column has the following limitation." -msgstr "A column has the following limitation." - -msgid "The maximum stored data size of a column: 256GiB" -msgstr "" Deleted: doc/locale/en/LC_MESSAGES/news.po (+0 -5201) 100644 =================================================================== --- doc/locale/en/LC_MESSAGES/news.po 2015-03-25 14:48:34 +0900 (ace2abe) +++ /dev/null @@ -1,5201 +0,0 @@ -# -*- po -*- -# English translations for Groonga package. -# Copyright (C) 2009-2014, Brazil, Inc -# This file is distributed under the same license as the Groonga package. -# Kouhei Sutou <kou �� clear-code.com>, 2014. -# -msgid "" -msgstr "" -"Project-Id-Version: Groonga 4.0.1\n" -"Report-Msgid-Bugs-To: \n" -"PO-Revision-Date: 2015-02-09 04:38+0900\n" -"Last-Translator: Kouhei Sutou <kou �� clear-code.com>\n" -"Language-Team: English\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" - -msgid "News" -msgstr "News" - -msgid "Release 5.0.0 - 2015/02/09" -msgstr "" - -msgid "Bump version to 5.0.0!" -msgstr "" - -msgid "Improvements" -msgstr "Improvements" - -msgid "" -"[doc] Added :ref:`script-syntax-security` about :doc:`/reference/grn_expr/" -"script_syntax`." -msgstr "" - -msgid "" -"[experimental] Added sharding plugin. Execute `register sharding` to enable " -"this feature in advance, then use :doc:`/reference/commands/logical_count` " -"to select records." -msgstr "" - -msgid "" -"[cmake] Supported embedded Groonga with Clang. It fixed compilation failure " -"on FreeBSD 10.1. `[MDEV-7293] <https://mariadb.atlassian.net/browse/" -"MDEV-7293>`_ [Reported by Bernard Spil]" -msgstr "" - -msgid "" -"Supported to customize plugins directory. Set `GRN_PLUGINS_DIR` environment " -"variable." -msgstr "" - -msgid "Fixes" -msgstr "Fixes" - -msgid "" -"Fixed build failure when system has an incompatible version of onigmo/" -"oniguruma headers installed. [GitHub#276] [Patch by Akinori MUSHA]" -msgstr "" - -msgid "Fixed time related build failure on MSVC [GitHub#237]" -msgstr "" - -msgid "Thanks" -msgstr "Thanks" - -msgid "Akinori MUSHA" -msgstr "" - -msgid "Bernard Spil" -msgstr "" - -msgid "The old releases" -msgstr "The old releases" - -msgid "バージョン0.xのお知らせ" -msgstr "バージョン0.xのお知らせ" - -msgid "0.7.7リリース - 2010/08/25" -msgstr "0.7.7リリース - 2010/08/25" - -msgid "改良" -msgstr "改良" - -msgid "" -"編集距離（レーベンシュタイン距離）を計算する :doc:`/reference/functions/" -"edit_distance` ()関数の追加。" -msgstr "" -"編集距離（レーベンシュタイン距離）を計算する :doc:`/reference/functions/" -"edit_distance` ()関数の追加。" - -msgid "manを追加。" -msgstr "manを追加。" - -msgid "" -":doc:`/reference/commands/delete` コマンドでデータの整合性が壊れる場合はエ" -"ラー を返すようにした。" -msgstr "" -":doc:`/reference/commands/delete` コマンドでデータの整合性が壊れる場合はエ" -"ラー を返すようにした。" - -msgid "MeCabの辞書のエンコーディング検出処理を改善。" -msgstr "MeCabの辞書のエンコーディング検出処理を改善。" - -msgid "デフォルトの設定ファイルを追加。" -msgstr "デフォルトの設定ファイルを追加。" - -msgid "修正" -msgstr "修正" - -msgid "" -":doc:`/reference/functions/geo_in_rectangle` ()関数が引数を「左上」と「右下」" -"で はなく、「左下」と「右上」と扱っていた問題を修正。" -msgstr "" -":doc:`/reference/functions/geo_in_rectangle` ()関数が引数を「左上」と「右下」" -"で はなく、「左下」と「右上」と扱っていた問題を修正。" - -msgid "前方一致検索がマッチしない問題を修正。" -msgstr "前方一致検索がマッチしない問題を修正。" - -msgid "0.7.6リリース - 2010/08/19" -msgstr "0.7.6リリース - 2010/08/19" - -msgid "デーモンになるときは標準出力を閉じるようにした。" -msgstr "デーモンになるときは標準出力を閉じるようにした。" - -msgid "PIDファイルを指定する``--pid-path``オプションを追加。" -msgstr "PIDファイルを指定する``--pid-path``オプションを追加。" - -msgid "設定ファイルを指定する``--config-path``オプションを追加。" -msgstr "設定ファイルを指定する``--config-path``オプションを追加。" - -msgid "最大キャッシュ数を指定する``--cache-limit``オプションを追加。" -msgstr "最大キャッシュ数を指定する``--cache-limit``オプションを追加。" - -msgid "設定値を表示する``--show-config``オプションを追加。" -msgstr "設定値を表示する``--show-config``オプションを追加。" - -msgid "指定したファイルからコマンドを読み込む``--file``オプションを追加。" -msgstr "指定したファイルからコマンドを読み込む``--file``オプションを追加。" - -msgid "" -"groongaとMeCabの辞書のエンコーディングが同じかどうかを確 認するようにした。" -msgstr "" -"groongaとMeCabの辞書のエンコーディングが同じかどうかを確 認するようにした。" - -msgid "Web管理画面:" -msgstr "Web管理画面:" - -msgid "データロード機能を追加。" -msgstr "データロード機能を追加。" - -msgid "uptimeの表示形式を読みやすい形式に変更。" -msgstr "uptimeの表示形式を読みやすい形式に変更。" - -msgid "Muninプラグインの追加。" -msgstr "Muninプラグインの追加。" - -msgid "クエリパフォーマンス計測用" -msgstr "クエリパフォーマンス計測用" - -msgid "ディスク使用量計測用" -msgstr "ディスク使用量計測用" - -msgid "libedit対応。" -msgstr "libedit対応。" - -msgid "存在しないデータベースを指定したときのエラーメッセージを改善。" -msgstr "存在しないデータベースを指定したときのエラーメッセージを改善。" - -msgid "loadコマンド:" -msgstr "loadコマンド:" - -msgid "不正な文字を見つけた場合はログに出力。" -msgstr "不正な文字を見つけた場合はログに出力。" - -msgid "必要な項目がない場合はログに出力。" -msgstr "必要な項目がない場合はログに出力。" - -msgid "true/false/nullリテラルをサポート。" -msgstr "true/false/nullリテラルをサポート。" - -msgid "" -"GeoPointの度での指定をサポート。 （例: " -"\"35.6954581363924,139.564207350021\"）" -msgstr "" -"GeoPointの度での指定をサポート。 （例: " -"\"35.6954581363924,139.564207350021\"）" - -msgid "NO_KEYテーブルを参照しているカラム値をサポート。" -msgstr "NO_KEYテーブルを参照しているカラム値をサポート。" - -msgid "数値のベクタをサポート。" -msgstr "数値のベクタをサポート。" - -msgid "selectコマンド" -msgstr "selectコマンド" - -msgid "索引を用いた高速なGeoPointの検索機能を追加。" -msgstr "索引を用いた高速なGeoPointの検索機能を追加。" - -msgid "" -"索引を用いた高速なGeoPointのソート機能を追加。 （ただし複数のソートキーと一緒" -"に使うことはできない。）" -msgstr "" -"索引を用いた高速なGeoPointのソート機能を追加。 （ただし複数のソートキーと一緒" -"に使うことはできない。）" - -msgid "ベクタのGeoPointの出力に対応。" -msgstr "ベクタのGeoPointの出力に対応。" - -msgid "不正な入力値に対してエラーを出力するようにした。" -msgstr "不正な入力値に対してエラーを出力するようにした。" - -msgid "dumpコマンド:" -msgstr "dumpコマンド:" - -msgid "フラグを数値ではなくキーワードで出力するように変更。" -msgstr "フラグを数値ではなくキーワードで出力するように変更。" - -msgid "column_listコマンド:" -msgstr "column_listコマンド:" - -msgid "_keyカラムの出力に対応。" -msgstr "_keyカラムの出力に対応。" - -msgid "deleteコマンド:" -msgstr "deleteコマンド:" - -msgid "データに不整合が発生する場合はデータを削除しないように変更。" -msgstr "データに不整合が発生する場合はデータを削除しないように変更。" - -msgid "statusコマンド:" -msgstr "statusコマンド:" - -msgid "キャッシュ情報を追加。" -msgstr "キャッシュ情報を追加。" - -msgid "データの整合性を確認するcheckコマンドの追加。" -msgstr "データの整合性を確認するcheckコマンドの追加。" - -msgid "強制的にロックを解除するclearlockコマンドの追加。" -msgstr "強制的にロックを解除するclearlockコマンドの追加。" - -msgid "最大キャッシュ数を指定するcache_limitコマンドの追加。" -msgstr "最大キャッシュ数を指定するcache_limitコマンドの追加。" - -msgid "フラグメンテーションを解消するdefragコマンドの追加。" -msgstr "フラグメンテーションを解消するdefragコマンドの追加。" - -msgid "データ投入後のインデックスカラム作成に対応。" -msgstr "データ投入後のインデックスカラム作成に対応。" - -msgid "不正なsortキーを指定された場合はSEGVする問題の修正。" -msgstr "不正なsortキーを指定された場合はSEGVする問題の修正。" - -msgid "selectの出力に不正なカラムを指定された時にSEGVする問題を修正。" -msgstr "selectの出力に不正なカラムを指定された時にSEGVする問題を修正。" - -msgid "空のベクタをloadするとSEGVする問題の修正。" -msgstr "空のベクタをloadするとSEGVする問題の修正。" - -msgid "メモリリークの修正。" -msgstr "メモリリークの修正。" - -msgid "drilldown時に参照先が存在しない場合にSEGVする問題の修正。" -msgstr "drilldown時に参照先が存在しない場合にSEGVする問題の修正。" - -msgid "感謝" -msgstr "感謝" - -msgid "おばたさん" -msgstr "おばたさん" - -msgid "バージョン1.0.xのお知らせ" -msgstr "バージョン1.0.xのお知らせ" - -msgid "1.0.8リリース - 2011/02/02" -msgstr "1.0.8リリース - 2011/02/02" - -msgid "" -"ShortText型カラムへデータ追加・削除を繰り返すとデータが壊れ ることがある問題" -"を修正。 （Mitsuhiro Shibuyaさんが報告）" -msgstr "" -"ShortText型カラムへデータ追加・削除を繰り返すとデータが壊れ ることがある問題" -"を修正。 （Mitsuhiro Shibuyaさんが報告）" - -msgid "Mitsuhiro Shibuyaさん" -msgstr "Mitsuhiro Shibuyaさん" - -msgid "1.0.7リリース - 2011/01/29" -msgstr "1.0.7リリース - 2011/01/29" - -msgid "automake 1.9.6でも動作するようにした。 #508" -msgstr "automake 1.9.6でも動作するようにした。 #508" - -msgid "configureの最後に検出したMeCabの情報も表示するようにした。" -msgstr "configureの最後に検出したMeCabの情報も表示するようにした。" - -msgid "エラーメッセージをわかりやすくした。" -msgstr "エラーメッセージをわかりやすくした。" - -msgid "" -"--enable-memory-debug付きでビルドしたときに終了時に未開放のメモリが 割り当て" -"られた場所を表示するようにした。" -msgstr "" -"--enable-memory-debug付きでビルドしたときに終了時に未開放のメモリが 割り当て" -"られた場所を表示するようにした。" - -msgid "" -"ベクタの値を :doc:`/reference/commands/load` するときにキャストに失敗したら、" -"そ のことを報告するようにした。" -msgstr "" -"ベクタの値を :doc:`/reference/commands/load` するときにキャストに失敗したら、" -"そ のことを報告するようにした。" - -msgid "" -"groongaのメモリリークを検出するユーティリティツール groonga-check-memory-" -"leak.rbを追加。（インストールはされない。）" -msgstr "" -"groongaのメモリリークを検出するユーティリティツール groonga-check-memory-" -"leak.rbを追加。（インストールはされない。）" - -msgid ":doc:`/reference/commands/dump` がテーブル単位のダンプに対応。" -msgstr ":doc:`/reference/commands/dump` がテーブル単位のダンプに対応。" - -msgid "" -"Mac OS Xでモジュールの拡張子の検出に失敗する問題を修正。 （ongaeshiさんが報" -"告）" -msgstr "" -"Mac OS Xでモジュールの拡張子の検出に失敗する問題を修正。 （ongaeshiさんが報" -"告）" - -msgid "Mac OS Xではrealloc(ptr, 0)ではなくfree()を使うように修正。" -msgstr "Mac OS Xではrealloc(ptr, 0)ではなくfree()を使うように修正。" - -msgid "grntestで結果の比較が常に失敗していた問題を修正。" -msgstr "grntestで結果の比較が常に失敗していた問題を修正。" - -msgid "groonga-suggest-learnerのメモリリークを修正。" -msgstr "groonga-suggest-learnerのメモリリークを修正。" - -msgid "" -":doc:`/reference/commands/load` 時のメモリリークを修正。 （Kenichi Aramakiさ" -"んが報告）" -msgstr "" -":doc:`/reference/commands/load` 時のメモリリークを修正。 （Kenichi Aramakiさ" -"んが報告）" - -msgid "ベクタの値を出力するときのメモリリークを修正。" -msgstr "ベクタの値を出力するときのメモリリークを修正。" - -msgid "ongaeshiさん" -msgstr "ongaeshiさん" - -msgid "Kenichi Aramakiさん" -msgstr "Kenichi Aramakiさん" - -msgid "1.0.6リリース - 2010/12/31" -msgstr "1.0.6リリース - 2010/12/31" - -msgid "\\*BSDでビルドできない問題を修正。（OBATA Akioさんが報告）" -msgstr "\\*BSDでビルドできない問題を修正。（OBATA Akioさんが報告）" - -msgid "OBATA Akioさん" -msgstr "OBATA Akioさん" - -msgid "1.0.5リリース - 2010/12/29" -msgstr "1.0.5リリース - 2010/12/29" - -msgid "サジェスト機能用の学習プログラムを追加。" -msgstr "サジェスト機能用の学習プログラムを追加。" - -msgid "groongaスクリプト内での行コメントに対応。（「#」以降を無視） #723" -msgstr "groongaスクリプト内での行コメントに対応。（「#」以降を無視） #723" - -msgid ":doc:`/reference/commands/column_list` のXML出力対応。 #748" -msgstr ":doc:`/reference/commands/column_list` のXML出力対応。 #748" - -msgid "主キーが数値のテーブルを参照しているカラムでの比較演算に対応。 #776" -msgstr "主キーが数値のテーブルを参照しているカラムでの比較演算に対応。 #776" - -msgid "grntestがmlockの情報出力に対応。" -msgstr "grntestがmlockの情報出力に対応。" - -msgid "NetBSDでのビルドに対応。 （OBATA Akioさんがパッチ作成）" -msgstr "NetBSDでのビルドに対応。 （OBATA Akioさんがパッチ作成）" - -msgid "" -"MeCabトークナイザーが見つからない時のエラーメッセージをより親切にした。 #790" -msgstr "" -"MeCabトークナイザーが見つからない時のエラーメッセージをより親切にした。 #790" - -msgid "" -"開いているファイルディスクリプタが多すぎてacceptできない状態の負荷を低減。 " -"#802" -msgstr "" -"開いているファイルディスクリプタが多すぎてacceptできない状態の負荷を低減。 " -"#802" - -msgid "DragonFlyでのビルドに対応。 （OBATA Akioさんが報告）" -msgstr "DragonFlyでのビルドに対応。 （OBATA Akioさんが報告）" - -msgid "変更" -msgstr "変更" - -msgid "" -":doc:`/reference/commands/table_list` のXML出力のタグ名をより適切な名前に変" -"更。 #757" -msgstr "" -":doc:`/reference/commands/table_list` のXML出力のタグ名をより適切な名前に変" -"更。 #757" - -msgid "" -":doc:`/reference/commands/load` で存在しないカラムを--columnsで指定するとク" -"ラッシュする問題を修正。 （Masahiro Tomitaさんが報告） #751" -msgstr "" -":doc:`/reference/commands/load` で存在しないカラムを--columnsで指定するとク" -"ラッシュする問題を修正。 （Masahiro Tomitaさんが報告） #751" - -msgid "" -":doc:`/reference/commands/load` で配列でTABLE_NO_KEYなテーブルにレコードを" -"ロードできない問題を修正。 （Masahiro Tomitaさんが報告） #750" -msgstr "" -":doc:`/reference/commands/load` で配列でTABLE_NO_KEYなテーブルにレコードを" -"ロードできない問題を修正。 （Masahiro Tomitaさんが報告） #750" - -msgid "" -":doc:`/reference/commands/delete` でTABLE_NO_KEYなテーブルのレコードを削除す" -"るとテーブルが壊れる 問題を修正。 （Masahiro Tomitaさんがパッチ作成） #794" -msgstr "" -":doc:`/reference/commands/delete` でTABLE_NO_KEYなテーブルのレコードを削除す" -"るとテーブルが壊れる 問題を修正。 （Masahiro Tomitaさんがパッチ作成） #794" - -msgid "" -":doc:`/reference/commands/load` で不正なJSONを指定した場合にそれ以降コマンド" -"を受け付けなくなる 問題を修正。 #807" -msgstr "" -":doc:`/reference/commands/load` で不正なJSONを指定した場合にそれ以降コマンド" -"を受け付けなくなる 問題を修正。 #807" - -msgid "Tomita Masahiroさん" -msgstr "Tomita Masahiroさん" - -msgid "1.0.4リリース - 2010/11/29" -msgstr "1.0.4リリース - 2010/11/29" - -msgid "すべてのモジュールで同じ名前の関数をエクスポートするようにした。#624" -msgstr "すべてのモジュールで同じ名前の関数をエクスポートするようにした。#624" - -msgid "不正な名前を指定したときに指定された名前も報告するようにした。" -msgstr "不正な名前を指定したときに指定された名前も報告するようにした。" - -msgid "" -":doc:`/reference/commands/select` の--filter内での数値比較演算をサポート。 " -"（@s3kiさんが報告）" -msgstr "" -":doc:`/reference/commands/select` の--filter内での数値比較演算をサポート。 " -"（@s3kiさんが報告）" - -msgid "``grntest`` の一行あたりの最大バイト数の制限を撤廃。 #608, #690" -msgstr "``grntest`` の一行あたりの最大バイト数の制限を撤廃。 #608, #690" - -msgid "Int8/UInt8/Int16/UInt16の等値比較にC言語の比較演算子を使用。 #660" -msgstr "Int8/UInt8/Int16/UInt16の等値比較にC言語の比較演算子を使用。 #660" - -msgid "" -"HTTP経由で存在しないパスにアクセスした時に存在しないパスを報告するように し" -"た。" -msgstr "" -"HTTP経由で存在しないパスにアクセスした時に存在しないパスを報告するように し" -"た。" - -msgid "grn_table_cursor_next()をGRN_CURSOR_COLUMN_INDEX対応にした。" -msgstr "grn_table_cursor_next()をGRN_CURSOR_COLUMN_INDEX対応にした。" - -msgid "右辺が式の演算代入演算子をサポート。 #669" -msgstr "右辺が式の演算代入演算子をサポート。 #669" - -msgid "zlib/LZOサポート付きでビルドされているかをチェックするAPIを追加。 #686" -msgstr "zlib/LZOサポート付きでビルドされているかをチェックするAPIを追加。 #686" - -msgid "grn_table_at()を公開。" -msgstr "grn_table_at()を公開。" - -msgid "grn_db_touch()を公開。 #703" -msgstr "grn_db_touch()を公開。 #703" - -msgid "コメント行に対応。 #723" -msgstr "コメント行に対応。 #723" - -msgid "grn_bool型を追加。 #713" -msgstr "grn_bool型を追加。 #713" - -msgid "" -"プラグインの置き場所を変更: lib/groonga/modules/ -> lib/groonga/plugins/ #624" -msgstr "" -"プラグインの置き場所を変更: lib/groonga/modules/ -> lib/groonga/plugins/ #624" - -msgid "ドキュメントの誤字を修正。（OBATA Akioさんが報告）" -msgstr "ドキュメントの誤字を修正。（OBATA Akioさんが報告）" - -msgid "GRN_CURSOR_PREFIXが動作しない問題を修正。" -msgstr "GRN_CURSOR_PREFIXが動作しない問題を修正。" - -msgid "索引が不正に大きくなる問題を修正。（Tomoatsu Shimadaさんが報告） #689" -msgstr "索引が不正に大きくなる問題を修正。（Tomoatsu Shimadaさんが報告） #689" - -msgid "@s3kiさん" -msgstr "@s3kiさん" - -msgid "Tomoatsu Shimadaさん" -msgstr "Tomoatsu Shimadaさん" - -msgid "1.0.3リリース - 2010/10/29" -msgstr "1.0.3リリース - 2010/10/29" - -msgid "" -"CentOS/Fedora用パッケージをディストリビューションのルールに従うように改良。 " -"（上野乃毅さん）" -msgstr "" -"CentOS/Fedora用パッケージをディストリビューションのルールに従うように改良。 " -"（上野乃毅さん）" - -msgid "Fedoraのオフィシャルリポジトリに登録。（Daiki Uenoさん）" -msgstr "Fedoraのオフィシャルリポジトリに登録。（Daiki Uenoさん）" - -msgid "GeoPointのキャストに対応。#515" -msgstr "GeoPointのキャストに対応。#515" - -msgid "groongaコマンドに、--defalt-command-versionオプションの追加。" -msgstr "groongaコマンドに、--defalt-command-versionオプションの追加。" - -msgid "statusの出力結果にコマンドバージョンを追加。" -msgstr "statusの出力結果にコマンドバージョンを追加。" - -msgid ":doc:`/spec/search` の仕様を追加。" -msgstr ":doc:`/spec/search` の仕様を追加。" - -msgid ":doc:`/troubleshooting` を追加。" -msgstr ":doc:`/troubleshooting` を追加。" - -msgid "辞書検索のサンプルアプリケーションを追加。" -msgstr "辞書検索のサンプルアプリケーションを追加。" - -msgid "pkg-configがない場合はlibeditを検出しないようにした。 #540" -msgstr "pkg-configがない場合はlibeditを検出しないようにした。 #540" - -msgid "メモリデバッグ用オプション--enable-memory-debugを追加。" -msgstr "メモリデバッグ用オプション--enable-memory-debugを追加。" - -msgid "不正な関数呼び出しをチェックするようにした。#596" -msgstr "不正な関数呼び出しをチェックするようにした。#596" - -msgid "" -"テキストから数値へのキャスト処理を強化。#612, #613 （Itagaki Takahiroさんが報" -"告）" -msgstr "" -"テキストから数値へのキャスト処理を強化。#612, #613 （Itagaki Takahiroさんが報" -"告）" - -msgid "クライアントモードでの--fileオプションのサポート。#578" -msgstr "クライアントモードでの--fileオプションのサポート。#578" - -msgid "" -":doc:`/spec/search` の挙動を動的に変更する``--match-escalation-threashold`` " -"起動オプションと``--match_escalation_threshold``selectオプションを追加。 #628" -msgstr "" -":doc:`/spec/search` の挙動を動的に変更する``--match-escalation-threashold`` " -"起動オプションと``--match_escalation_threshold``selectオプションを追加。 #628" - -msgid "記号でトークンを区切るTokenBigramSplitSymbolを使用。 #225" -msgstr "記号でトークンを区切るTokenBigramSplitSymbolを使用。 #225" - -msgid "時間の解像度をナノ秒に変更。" -msgstr "時間の解像度をナノ秒に変更。" - -msgid "" -"パッケージを提供するUbuntuのバージョンをHardy, Lucidから Lucid, Marverickに変" -"更。" -msgstr "" -"パッケージを提供するUbuntuのバージョンをHardy, Lucidから Lucid, Marverickに変" -"更。" - -msgid "grn_table_cursor_open()のドキュメントを修正。" -msgstr "grn_table_cursor_open()のドキュメントを修正。" - -msgid "メモリリークを修正。" -msgstr "メモリリークを修正。" - -msgid "" -"--disable-libeditオプションがヘルプメッセージと違う問題の修正。 （MATSUU " -"Takutoさんが報告）" -msgstr "" -"--disable-libeditオプションがヘルプメッセージと違う問題の修正。 （MATSUU " -"Takutoさんが報告）" - -msgid "警告を除去。（MATSUU Takutoさんが報告）" -msgstr "警告を除去。（MATSUU Takutoさんが報告）" - -msgid "" -"grn_pat_at()でエンコードされたキーが常にGRN_NILになってしまう問題を修正。#514" -msgstr "" -"grn_pat_at()でエンコードされたキーが常にGRN_NILになってしまう問題を修正。#514" - -msgid "" -"固定長カラムにカラム長より短いデータを設定するとゴミが残ってしまう問題を修" -"正。" -msgstr "" -"固定長カラムにカラム長より短いデータを設定するとゴミが残ってしまう問題を修" -"正。" - -msgid "不正なレコードがあるときにdumpすると落ちてしまう問題を修正。" -msgstr "不正なレコードがあるときにdumpすると落ちてしまう問題を修正。" - -msgid "geo_in_rectangle()が無限ループする問題を修正。#563" -msgstr "geo_in_rectangle()が無限ループする問題を修正。#563" - -msgid "" -"インデックスがついたカラムでソートすると結果がおかしくなる問題を修正。#571" -msgstr "" -"インデックスがついたカラムでソートすると結果がおかしくなる問題を修正。#571" - -msgid "deleteが常に失敗する問題を修正。#541" -msgstr "deleteが常に失敗する問題を修正。#541" - -msgid "" -"レコードを追加・削除したパトリシアトライからID順に取り出すカーソルが おかしな" -"結果を返す問題を修正。#538" -msgstr "" -"レコードを追加・削除したパトリシアトライからID順に取り出すカーソルが おかしな" -"結果を返す問題を修正。#538" - -msgid "値が存在しないレコードがあるカラムでソートすると落ちる問題を修正。" -msgstr "値が存在しないレコードがあるカラムでソートすると落ちる問題を修正。" - -msgid "モジュールの初期化関数が複数回呼ばれる問題を修正。#567" -msgstr "モジュールの初期化関数が複数回呼ばれる問題を修正。#567" - -msgid "shutdownで終了しない問題を修正。#114" -msgstr "shutdownで終了しない問題を修正。#114" - -msgid "全文検索時に削除したレコードが返る問題を修正。#617" -msgstr "全文検索時に削除したレコードが返る問題を修正。#617" - -msgid "必要な時以外にMeCabの辞書チェックをしてしまう問題を修正。#555" -msgstr "必要な時以外にMeCabの辞書チェックをしてしまう問題を修正。#555" - -msgid "存在しないパトリシアトライのレコードを参照すると落ちる問題を修正。#630" -msgstr "存在しないパトリシアトライのレコードを参照すると落ちる問題を修正。#630" - -msgid "インストールドキュメントの誤字を修正。（SHIMODA Hiroshiさんが報告）" -msgstr "インストールドキュメントの誤字を修正。（SHIMODA Hiroshiさんが報告）" - -msgid "Daiki Uenoさん" -msgstr "Daiki Uenoさん" - -msgid "MATSUU Takutoさん" -msgstr "MATSUU Takutoさん" - -msgid "Itagaki Takahiroさん" -msgstr "Itagaki Takahiroさん" - -msgid "SHIMODA Hiroshiさん" -msgstr "SHIMODA Hiroshiさん" - -msgid "1.0.2リリース - 2010/09/09" -msgstr "1.0.2リリース - 2010/09/09" - -msgid "" -":doc:`/reference/commands/suggest` コマンドのサンプルを追加。（examples/" -"dictionary/）" -msgstr "" -":doc:`/reference/commands/suggest` コマンドのサンプルを追加。（examples/" -"dictionary/）" - -msgid "" -"HTTPで公開するディレクトリを指定する--admin-html-pathを--document-rootに変" -"更。" -msgstr "" -"HTTPで公開するディレクトリを指定する--admin-html-pathを--document-rootに変" -"更。" - -msgid "" -":doc:`/reference/commands/select` コマンドのデフォルトの--output_columnsから" -"_valueを削除。" -msgstr "" -":doc:`/reference/commands/select` コマンドのデフォルトの--output_columnsから" -"_valueを削除。" - -msgid "パッケージミスを修正。 （OBATA Akioさんが報告）" -msgstr "パッケージミスを修正。 （OBATA Akioさんが報告）" - -msgid "GeoPointの度表記の解釈を修正。 #460" -msgstr "GeoPointの度表記の解釈を修正。 #460" - -msgid "1.0.1リリース - 2010/09/06" -msgstr "1.0.1リリース - 2010/09/06" - -msgid "CentOS 5/Fedora 13用RPMの提供。（Daiki Uenoさん作成のspecがベース）" -msgstr "CentOS 5/Fedora 13用RPMの提供。（Daiki Uenoさん作成のspecがベース）" - -msgid "ログパスのデフォルト値に--localstatedirを使用。（OBATA Akioさんが提案）" -msgstr "" -"ログパスのデフォルト値に--localstatedirを使用。（OBATA Akioさんが提案）" - -msgid "BOM付きUTF-8に対応。" -msgstr "BOM付きUTF-8に対応。" - -msgid "JSON JQueryプラグインが同梱されていない問題の修正。" -msgstr "JSON JQueryプラグインが同梱されていない問題の修正。" - -msgid "テストが失敗する問題の修正。（OBATA Akioさんが報告）" -msgstr "テストが失敗する問題の修正。（OBATA Akioさんが報告）" - -msgid "1.0.0リリース - 2010/08/29" -msgstr "1.0.0リリース - 2010/08/29" - -msgid "" -"指定したクエリに対する補完・修正・提案を行う :doc:`/reference/commands/" -"suggest` コマンドを追加。" -msgstr "" -"指定したクエリに対する補完・修正・提案を行う :doc:`/reference/commands/" -"suggest` コマンドを追加。" - -msgid "" -":doc:`/reference/commands/delete` コマンドが失敗したらfalseを返すように変更。" -"（Itagaki Takahiroさんが提案）" -msgstr "" -":doc:`/reference/commands/delete` コマンドが失敗したらfalseを返すように変更。" -"（Itagaki Takahiroさんが提案）" - -msgid "関数もコマンドとして呼び出してしまう問題を修正。#431" -msgstr "関数もコマンドとして呼び出してしまう問題を修正。#431" - -msgid "索引付きカラムを等価条件で検索できない問題を修正。" -msgstr "索引付きカラムを等価条件で検索できない問題を修正。" - -msgid "" -":doc:`/reference/commands/delete` コマンドでキーがShortText以外のレコードを削" -"除できない問題の修正。（Itagaki Takahiroさんが報告）" -msgstr "" -":doc:`/reference/commands/delete` コマンドでキーがShortText以外のレコードを削" -"除できない問題の修正。（Itagaki Takahiroさんが報告）" - -msgid "バージョン1.1.xのお知らせ" -msgstr "バージョン1.1.xのお知らせ" - -msgid "1.1.0リリース - 2011/02/09" -msgstr "1.1.0リリース - 2011/02/09" - -msgid "TokenDelimitNullトークナイザーを追加。" -msgstr "TokenDelimitNullトークナイザーを追加。" - -msgid "" -"プラグイン登録APIの名前を改良。 grn_db_register_by_name() -> " -"grn_plugin_register() #834" -msgstr "" -"プラグイン登録APIの名前を改良。 grn_db_register_by_name() -> " -"grn_plugin_register() #834" - -msgid "" -":doc:`/reference/commands/select` の--query内で前方一致検索構文\"キーワード*" -"\"対応。 #837" -msgstr "" -":doc:`/reference/commands/select` の--query内で前方一致検索構文\"キーワード*" -"\"対応。 #837" - -msgid "" -"groonga.pcにgroonga-suggest-create-datasetのパスが設定されている " -"groonga_suggest_create_dataset変数を追加。" -msgstr "" -"groonga.pcにgroonga-suggest-create-datasetのパスが設定されている " -"groonga_suggest_create_dataset変数を追加。" - -msgid "ログにタイムスタンプの秒より小さい値が常に0になる問題を修正。" -msgstr "ログにタイムスタンプの秒より小さい値が常に0になる問題を修正。" - -msgid "" -"サンプル内のスクリプトに実行属性がつかない問題を修正。 （Daiki Uenoさんが報" -"告）" -msgstr "" -"サンプル内のスクリプトに実行属性がつかない問題を修正。 （Daiki Uenoさんが報" -"告）" - -msgid "Release 1.2.9 - 2011/12/29" -msgstr "Release 1.2.9 - 2011/12/29" - -msgid "Supported Fedora 16." -msgstr "Supported Fedora 16." - -msgid "Dropped Fedora 15 support." -msgstr "Dropped Fedora 15 support." - -msgid "" -"[groonga] Improved the default server ID address to work on unresolved host " -"name environment. [Reported by @uzulla]" -msgstr "" -"[groonga] Improved the default server ID address to work on unresolved host " -"name environment. [Reported by @uzulla]" - -msgid "Supported MAP_HUGETLB." -msgstr "Supported MAP_HUGETLB." - -msgid "[admin] Supported throughput chart." -msgstr "[admin] Supported throughput chart." - -msgid "" -"Stopped adding nul character in ``grn_itoh()``. [#1194] [Reported by SHIDARA " -"Yoji]" -msgstr "" -"Stopped adding nul character in ``grn_itoh()``. [#1194] [Reported by SHIDARA " -"Yoji]" - -msgid "Added ``grn_obj_get_values()``." -msgstr "Added ``grn_obj_get_values()``." - -msgid "Added ``grn_obj_delete_by_id()``." -msgstr "Added ``grn_obj_delete_by_id()``." - -msgid "Supported string vector column for query expansion. [#1216]" -msgstr "Supported string vector column for query expansion. [#1216]" - -msgid "" -"Added ``--filter`` option to :doc:`/reference/commands/delete` to delete " -"many record at once. [#1225]" -msgstr "" -"Added ``--filter`` option to :doc:`/reference/commands/delete` to delete " -"many record at once. [#1225]" - -msgid "" -"Supported approximate type customization for :doc:`/reference/functions/" -"geo_in_circle` and :doc:`/reference/functions/geo_distance`. [#1226]" -msgstr "" -"Supported approximate type customization for :doc:`/reference/functions/" -"geo_in_circle` and :doc:`/reference/functions/geo_distance`. [#1226]" - -msgid "Made ``geo_distance2()`` and ``geo_distance3()`` are deprecated." -msgstr "Made ``geo_distance2()`` and ``geo_distance3()`` are deprecated." - -msgid "" -"Changed to use ``null`` instead of ``\"\"`` for empty geo point value in " -"JSON output." -msgstr "" -"Changed to use ``null`` instead of ``\"\"`` for empty geo point value in " -"JSON output." - -msgid "Almost supported MessagePack output. [#1215] [Worked by SHIDARA Yoji]" -msgstr "Almost supported MessagePack output. [#1215] [Worked by SHIDARA Yoji]" - -msgid "Added missing newlines after drilldown result tags in XML output." -msgstr "Added missing newlines after drilldown result tags in XML output." - -msgid "Supported truncate for grn_dat." -msgstr "Supported truncate for grn_dat." - -msgid "Supported longest common prefix search by grn_dat." -msgstr "Supported longest common prefix search by grn_dat." - -msgid "[windows] Fixed inverted map type." -msgstr "[windows] Fixed inverted map type." - -msgid "Fixed -Wno- compiler flag detection. [Patch by Arnaud Fontaine]" -msgstr "Fixed -Wno- compiler flag detection. [Patch by Arnaud Fontaine]" - -msgid "" -"Fixed a problem that ``groonga --version`` reports wrongly about MeCab. " -"[#1209] [Patch by SHIDARA Yoji]" -msgstr "" -"Fixed a problem that ``groonga --version`` reports wrongly about MeCab. " -"[#1209] [Patch by SHIDARA Yoji]" - -msgid "Added missing lock into ``grn_obj_remove()``." -msgstr "Added missing lock into ``grn_obj_remove()``." - -msgid "Fixed Content-Type on error. [#1220] [Patch by SHIDARA Yoji]" -msgstr "Fixed Content-Type on error. [#1220] [Patch by SHIDARA Yoji]" - -msgid "" -"Fixed a problem that deleting SIS (Semi Infinite String) may keep a garbage." -msgstr "" -"Fixed a problem that deleting SIS (Semi Infinite String) may keep a garbage." - -msgid "@uzulla" -msgstr "@uzulla" - -msgid "Arnaud Fontaine" -msgstr "Arnaud Fontaine" - -msgid "SHIDARA Yoji" -msgstr "SHIDARA Yoji" - -msgid "Release 1.2.8 - 2011/11/29" -msgstr "Release 1.2.8 - 2011/11/29" - -msgid "" -"Object, table and column renamings are supported! These features require " -"database re-creation. You can re-create your database by the following " -"command::" -msgstr "" -"Object, table and column renamings are supported! These features require " -"database re-creation. You can re-create your database by the following " -"command::" - -msgid "" -"Groonga 1.2.8 can open databases created by groonga 1.2.7 or earlier. But " -"groonga 1.2.7 or earlier can't open databases created by groonga 1.2.8 or " -"later." -msgstr "" -"Groonga 1.2.8 can open databases created by groonga 1.2.7 or earlier. But " -"groonga 1.2.7 or earlier can't open databases created by groonga 1.2.8 or " -"later." - -msgid "[grntest] Removed the upper limit to the number of bytes in one line." -msgstr "[grntest] Removed the upper limit to the number of bytes in one line." - -msgid "[grntest] Added ``--pid-path`` option." -msgstr "[grntest] Added ``--pid-path`` option." - -msgid "[deb] Enabled experimental zlib and lzo support." -msgstr "[deb] Enabled experimental zlib and lzo support." - -msgid "[rpm] Enabled experimental zlib and lzo support." -msgstr "[rpm] Enabled experimental zlib and lzo support." - -msgid "Supports truncation. [#892]" -msgstr "Supports truncation. [#892]" - -msgid "Enabled grn_dat that is a read lock free double array implementation." -msgstr "Enabled grn_dat that is a read lock free double array implementation." - -msgid "[pkg-config] Added groonga_version variable to groonga.pc." -msgstr "[pkg-config] Added groonga_version variable to groonga.pc." - -msgid "" -"Re-supported ``--disable-static``. [groonga-dev,00612] [Suggested by Kenichi " -"Aramaki]" -msgstr "" -"Re-supported ``--disable-static``. [groonga-dev,00612] [Suggested by Kenichi " -"Aramaki]" - -msgid "[munin] Stopped to install Munin plugins by default." -msgstr "[munin] Stopped to install Munin plugins by default." - -msgid "Stopped to install RedHat platform related files by default." -msgstr "Stopped to install RedHat platform related files by default." - -msgid "Supports object renaming. This requires DB re-creation. [#1167]" -msgstr "Supports object renaming. This requires DB re-creation. [#1167]" - -msgid "[munin] Added a Munin plugin that measures throughput. [#1171]" -msgstr "[munin] Added a Munin plugin that measures throughput. [#1171]" - -msgid "" -"[geo] Improved geo_in_rectangle performance. The new implementation will be " -"2x faster than the old implementation in many cases. [#1173]" -msgstr "" -"[geo] Improved geo_in_rectangle performance. The new implementation will be " -"2x faster than the old implementation in many cases. [#1173]" - -msgid "" -"[macports] Moved groonga's MacPorts to the official repository. [Imported by " -"Hiroshi Umemoto]" -msgstr "" -"[macports] Moved groonga's MacPorts to the official repository. [Imported by " -"Hiroshi Umemoto]" - -msgid "" -"[geo] Changed the geo literal degree-to-msec conversion algorithm to round-" -"off from truncation." -msgstr "" -"[geo] Changed the geo literal degree-to-msec conversion algorithm to round-" -"off from truncation." - -msgid "" -"Supports a table defrag. It defrags variable size value columns in the " -"table. [#1175]" -msgstr "" -"Supports a table defrag. It defrags variable size value columns in the " -"table. [#1175]" - -msgid "Removed associated path on remove. [#1180]" -msgstr "Removed associated path on remove. [#1180]" - -msgid "[deb] Supports i386." -msgstr "[deb] Supports i386." - -msgid "[rpm] Supports i386." -msgstr "[rpm] Supports i386." - -msgid "[windows] Supports x86." -msgstr "[windows] Supports x86." - -msgid "" -"Fixed a bug that groonga crashes when accessing a zlib/lzo compressed " -"column. Note that a compressed column access causes a memory leak. To " -"resolve this, we need to improve API. We will do it in the future. [GtiHub#5]" -"[GtiHub#6] [Reported by Takayuki Yamaguchi]" -msgstr "" -"Fixed a bug that groonga crashes when accessing a zlib/lzo compressed " -"column. Note that a compressed column access causes a memory leak. To " -"resolve this, we need to improve API. We will do it in the future. [GtiHub#5]" -"[GtiHub#6] [Reported by Takayuki Yamaguchi]" - -msgid "Fixed a bug that unrelated column values are cleared in deletion." -msgstr "Fixed a bug that unrelated column values are cleared in deletion." - -msgid "" -"Fixed a bug that a wrong index is used in sorting. [#766] [Reported by " -"Horikoshi Yuki]" -msgstr "" -"Fixed a bug that a wrong index is used in sorting. [#766] [Reported by " -"Horikoshi Yuki]" - -msgid "" -"[libedit] Fixed a bug that necessary initialization is omitted. [GitHub#7] " -"[Patch by SHIDARA Yoji]" -msgstr "" -"[libedit] Fixed a bug that necessary initialization is omitted. [GitHub#7] " -"[Patch by SHIDARA Yoji]" - -msgid "[doc] Fixed a typo in documentation. [GitHub#8] [Patch by zunda]" -msgstr "[doc] Fixed a typo in documentation. [GitHub#8] [Patch by zunda]" - -msgid "Takayuki Yamaguchi" -msgstr "Takayuki Yamaguchi" - -msgid "Horikoshi Yuki" -msgstr "Horikoshi Yuki" - -msgid "zunda" -msgstr "zunda" - -msgid "Hiroshi Umemoto" -msgstr "Hiroshi Umemoto" - -msgid "Release 1.2.7 - 2011/10/29" -msgstr "Release 1.2.7 - 2011/10/29" - -msgid "" -"[libedit] Added error check for wide character to multibyte sequence " -"conversion. [Reported by SHIDARA Yoji]" -msgstr "" -"[libedit] Added error check for wide character to multibyte sequence " -"conversion. [Reported by SHIDARA Yoji]" - -msgid "Added grn_geo_estimate_in_rectangle()." -msgstr "Added grn_geo_estimate_in_rectangle()." - -msgid "Added cursor API to geo search in rectangle." -msgstr "Added cursor API to geo search in rectangle." - -msgid "Improved geo search in rectangle speed." -msgstr "Improved geo search in rectangle speed." - -msgid "Added packages for Ubuntu 11.10 Oneiric Ocelot" -msgstr "Added packages for Ubuntu 11.10 Oneiric Ocelot" - -msgid "" -"[experimental] Supported Oracle Solaris 10 8/11. (just buildable with system " -"gcc.)" -msgstr "" -"[experimental] Supported Oracle Solaris 10 8/11. (just buildable with system " -"gcc.)" - -msgid "Fixed a typo in document. [Reported by @soundkitchen]" -msgstr "Fixed a typo in document. [Reported by @soundkitchen]" - -msgid "@soundkitchen" -msgstr "@soundkitchen" - -msgid "Release 1.2.6 - 2011/09/29" -msgstr "Release 1.2.6 - 2011/09/29" - -msgid "Improved error message on type cast." -msgstr "Improved error message on type cast." - -msgid "Added geo point value validation on type cast." -msgstr "Added geo point value validation on type cast." - -msgid "Supported :doc:`/tutorial/query_expansion`." -msgstr "Supported :doc:`/tutorial/query_expansion`." - -msgid "" -"Added `--query_expansion` option to :doc:`/reference/commands/select` for " -"query expansion." -msgstr "" -"Added `--query_expansion` option to :doc:`/reference/commands/select` for " -"query expansion." - -msgid "Added geometry conversion macro between degree and msec." -msgstr "Added geometry conversion macro between degree and msec." - -msgid "Supported type cast in :doc:`/reference/functions/geo_distance` ()." -msgstr "Supported type cast in :doc:`/reference/functions/geo_distance` ()." - -msgid "Don't split tokens with full width space in command line. #986" -msgstr "Don't split tokens with full width space in command line. #986" - -msgid "Supported conversion between TokyoGeoPoint and WGS84GeoPoint." -msgstr "Supported conversion between TokyoGeoPoint and WGS84GeoPoint." - -msgid "Exported grn_geo_select_in_circle() and grn_geo_select_in_rectangle()." -msgstr "Exported grn_geo_select_in_circle() and grn_geo_select_in_rectangle()." - -msgid "Supported CentOS 6." -msgstr "Supported CentOS 6." - -msgid "" -"Supported the current Debian GNU/Linux sid. Patch by SATOH Fumiyasu. GitHub#3" -msgstr "" -"Supported the current Debian GNU/Linux sid. Patch by SATOH Fumiyasu. GitHub#3" - -msgid "Fixed a bug that geo point is loaded as broken value." -msgstr "Fixed a bug that geo point is loaded as broken value." - -msgid "SATOH Fumiyasu" -msgstr "SATOH Fumiyasu" - -msgid "Release 1.2.5 - 2011/08/29" -msgstr "Release 1.2.5 - 2011/08/29" - -msgid "Added experimental Windows installer support." -msgstr "Added experimental Windows installer support." - -msgid "Accepted \"#\" and \"-\" as a valid name characters. #1043" -msgstr "Accepted \"#\" and \"-\" as a valid name characters. #1043" - -msgid "" -"Accepted all valid characters except \"_\" as the first character. #1043" -msgstr "" -"Accepted all valid characters except \"_\" as the first character. #1043" - -msgid "" -"Supported `--each` for `[...]` form :doc:`/reference/commands/load`. #1044" -msgstr "" -"Supported `--each` for `[...]` form :doc:`/reference/commands/load`. #1044" - -msgid "Added documentation for :doc:`/reference/suggest`." -msgstr "Added documentation for :doc:`/reference/suggest`." - -msgid "" -"Supported threshold as `--frequency_threshold` and `--" -"conditional_probability_threshold` options in all :doc:`/reference/commands/" -"suggest` types. #1042" -msgstr "" -"Supported threshold as `--frequency_threshold` and `--" -"conditional_probability_threshold` options in all :doc:`/reference/commands/" -"suggest` types. #1042" - -msgid "[groonga-suggest-httpd] Supported log reopen by SIGUSR1. #1048" -msgstr "[groonga-suggest-httpd] Supported log reopen by SIGUSR1. #1048" - -msgid "Supported string input for reference vector column value. #1051" -msgstr "Supported string input for reference vector column value. #1051" - -msgid "" -"[groonga-suggest-httpd] Added `--n-lines-per-log-file` option that changes " -"log line limitation for a file." -msgstr "" -"[groonga-suggest-httpd] Added `--n-lines-per-log-file` option that changes " -"log line limitation for a file." - -msgid "" -"[groonga-suggest-httpd] Added `p` parameter for `--" -"conditional_probability_threshold`." -msgstr "" -"[groonga-suggest-httpd] Added `p` parameter for `--" -"conditional_probability_threshold`." - -msgid "Added GRN_CTX_PER_DB flag for grn_ctx_init() and grn_ctx_open(). #1053" -msgstr "Added GRN_CTX_PER_DB flag for grn_ctx_init() and grn_ctx_open(). #1053" - -msgid "Exported grn_ctx_close(). #1035" -msgstr "Exported grn_ctx_close(). #1035" - -msgid "" -"Fixed a crash bug that invalid value is passed as match expression argument " -"in :doc:`/reference/commands/select`. #1047" -msgstr "" -"Fixed a crash bug that invalid value is passed as match expression argument " -"in :doc:`/reference/commands/select`. #1047" - -msgid "Fixed a bug that hash table cursor returns garbage records." -msgstr "Fixed a bug that hash table cursor returns garbage records." - -msgid "Release 1.2.4 - 2011/07/29" -msgstr "Release 1.2.4 - 2011/07/29" - -msgid "Re-supported ``*BSD``. (Reported by OBATA Akio)" -msgstr "Re-supported ``*BSD``. (Reported by OBATA Akio)" - -msgid "Improved sed related portability. (Suggested by OBATA Akio)" -msgstr "Improved sed related portability. (Suggested by OBATA Akio)" - -msgid "Re-supported Visual C++ 2008." -msgstr "Re-supported Visual C++ 2008." - -msgid "Supported :doc:`/reference/commands/check` for hash table." -msgstr "Supported :doc:`/reference/commands/check` for hash table." - -msgid "" -"Ignored invalid _score in --sortby of :doc:`/reference/commands/select` for " -"convenience. #1030" -msgstr "" -"Ignored invalid _score in --sortby of :doc:`/reference/commands/select` for " -"convenience. #1030" - -msgid "Added document about :doc:`/reference/log`." -msgstr "Added document about :doc:`/reference/log`." - -msgid "Supported ~/.editrc." -msgstr "Supported ~/.editrc." - -msgid "Supported ~/.groonga-history." -msgstr "Supported ~/.groonga-history." - -msgid "Fixed broken libedit support. (Reported by Daiki Ueno)" -msgstr "Fixed broken libedit support. (Reported by Daiki Ueno)" - -msgid "Fixed source URL in ``*.spec`` (Reported by Daiki Ueno)" -msgstr "Fixed source URL in ``*.spec`` (Reported by Daiki Ueno)" - -msgid "Fixed patricia trie cursor returns wrong records." -msgstr "Fixed patricia trie cursor returns wrong records." - -msgid "" -"Added missing database lock clear for grn_obj_clear_lock() for database." -msgstr "" -"Added missing database lock clear for grn_obj_clear_lock() for database." - -msgid "" -"Fixed wrong record's column values deletion possible on record deletion." -msgstr "" -"Fixed wrong record's column values deletion possible on record deletion." - -msgid "OBATA Akio" -msgstr "OBATA Akio" - -msgid "Daiki Ueno" -msgstr "Daiki Ueno" - -msgid "Release 1.2.3 - 2011/06/29" -msgstr "Release 1.2.3 - 2011/06/29" - -msgid "Added invalid table name check. #912" -msgstr "Added invalid table name check. #912" - -msgid "Added groonga-query-log-analyzer that analyze query log." -msgstr "Added groonga-query-log-analyzer that analyze query log." - -msgid "groonga command shows failed command on error." -msgstr "groonga command shows failed command on error." - -msgid "groonga command shows file name and line no on error." -msgstr "groonga command shows file name and line no on error." - -msgid "" -"Improved error message of :doc:`/reference/commands/column_create`. #952" -msgstr "" -"Improved error message of :doc:`/reference/commands/column_create`. #952" - -msgid "Added GRN_OBJ_TABLE_DAT_KEY, double array trie, table. (experimental)" -msgstr "Added GRN_OBJ_TABLE_DAT_KEY, double array trie, table. (experimental)" - -msgid "fix get command crash. (Reported by OBATA Akio)" -msgstr "fix get command crash. (Reported by OBATA Akio)" - -msgid "fix elapsed time overflow in query log. #944" -msgstr "fix elapsed time overflow in query log. #944" - -msgid "Release 1.2.2 - 2011/05/29" -msgstr "Release 1.2.2 - 2011/05/29" - -msgid "Added packages for Ubuntu 11.04 Natty Narwhal." -msgstr "Added packages for Ubuntu 11.04 Natty Narwhal." - -msgid "Removed packages for Ubuntu 10.10 Maverick Meerkat." -msgstr "Removed packages for Ubuntu 10.10 Maverick Meerkat." - -msgid "RPM: Split server related packages to groonga-server package." -msgstr "RPM: Split server related packages to groonga-server package." - -msgid "suggest: Added target object name into error messages." -msgstr "suggest: Added target object name into error messages." - -msgid "document: Started English support. (not completed yet.)" -msgstr "document: Started English support. (not completed yet.)" - -msgid "groonga-suggest-httpd: Added --disable-max-fd-check option." -msgstr "groonga-suggest-httpd: Added --disable-max-fd-check option." - -msgid "" -"groonga: Renamed :option:`--address <-a>` option to :option:`--bind-address`." -msgstr "" -"groonga: Renamed :option:`--address <-a>` option to :option:`--bind-address`." - -msgid "groonga-suggest-httpd: Renamed --address option to --bind-address." -msgstr "groonga-suggest-httpd: Renamed --address option to --bind-address." - -msgid "" -"Changed admin HTML install directory to $PREFIX/share/groonga/html/admin/ " -"from $PREFIX/share/groonga/admin_html/." -msgstr "" -"Changed admin HTML install directory to $PREFIX/share/groonga/html/admin/ " -"from $PREFIX/share/groonga/admin_html/." - -msgid "" -"groonga-suggest-httpd: Used \"application/json\" for JSON response instead " -"of \"text/javascript\"." -msgstr "" -"groonga-suggest-httpd: Used \"application/json\" for JSON response instead " -"of \"text/javascript\"." - -msgid "" -"Windows: Used DLL relative path instead of executable file relative path." -msgstr "" -"Windows: Used DLL relative path instead of executable file relative path." - -msgid "MeCab: Added error message from MeCab on MeCab initialize error." -msgstr "MeCab: Added error message from MeCab on MeCab initialize error." - -msgid "suggest: Added prefix_search parameter to suggest command. #909" -msgstr "suggest: Added prefix_search parameter to suggest command. #909" - -msgid "" -"plugin: Added grn_plugin_get_system_plugins_dir() and " -"grn_plugin_get_suffix() API." -msgstr "" -"plugin: Added grn_plugin_get_system_plugins_dir() and " -"grn_plugin_get_suffix() API." - -msgid "Added grn_obj_is_builtin() API." -msgstr "Added grn_obj_is_builtin() API." - -msgid ":doc:`/reference/commands/load`: Added table name check. #934" -msgstr ":doc:`/reference/commands/load`: Added table name check. #934" - -msgid "Showed invalid name context in error message. #935" -msgstr "Showed invalid name context in error message. #935" - -msgid "Fixed a data breaking bug on multi process update. #890" -msgstr "Fixed a data breaking bug on multi process update. #890" - -msgid "1.2.1リリース - 2011/04/29" -msgstr "1.2.1リリース - 2011/04/29" - -msgid "suggestコマンドにthresholdパラメーターを追加。#895" -msgstr "suggestコマンドにthresholdパラメーターを追加。#895" - -msgid "suggestのHTTPサーバにlimitパラメーターを追加。#899" -msgstr "suggestのHTTPサーバにlimitパラメーターを追加。#899" - -msgid "grntest: SIGINTでの中断に対応。" -msgstr "grntest: SIGINTでの中断に対応。" - -msgid "" -"同時に複数のデータベースを開いているとき、1つでもデータベー スを閉じると関連" -"するプラグインも閉じられてしまう問題を修正。 #894" -msgstr "" -"同時に複数のデータベースを開いているとき、1つでもデータベー スを閉じると関連" -"するプラグインも閉じられてしまう問題を修正。 #894" - -msgid "" -"configureの--helpで出力される--with-deafult-encodingの値が 間違っていた問題を" -"修正。（ICHII Takashiさんが報告）" -msgstr "" -"configureの--helpで出力される--with-deafult-encodingの値が 間違っていた問題を" -"修正。（ICHII Takashiさんが報告）" - -msgid "チュートリアル中のtypoを修正。（moozさんが修正）" -msgstr "チュートリアル中のtypoを修正。（moozさんが修正）" - -msgid "ICHII Takashiさん" -msgstr "ICHII Takashiさん" - -msgid "moozさん" -msgstr "moozさん" - -msgid "1.2.0リリース - 2011/03/29" -msgstr "1.2.0リリース - 2011/03/29" - -msgid "MacPortsでのインストールドキュメントを追加。" -msgstr "MacPortsでのインストールドキュメントを追加。" - -msgid "Homebrewでのインストールドキュメントを追加。" -msgstr "Homebrewでのインストールドキュメントを追加。" - -msgid "WindowsではMinGWでもpthreadを使わないようにした。" -msgstr "WindowsではMinGWでもpthreadを使わないようにした。" - -msgid "オーバーフローチェックを強化。" -msgstr "オーバーフローチェックを強化。" - -msgid "位置情報の入力値チェックを強化。" -msgstr "位置情報の入力値チェックを強化。" - -msgid "インデックスを用いたジオサーチの例をチュートリアルに追加。 #438" -msgstr "インデックスを用いたジオサーチの例をチュートリアルに追加。 #438" - -msgid "Debian GNU/Linux wheezyのパッケージを追加。" -msgstr "Debian GNU/Linux wheezyのパッケージを追加。" - -msgid "Debian GNU/Linux lennyのパッケージを削除。" -msgstr "Debian GNU/Linux lennyのパッケージを削除。" - -msgid "" -"Debianパッケージをcdbsベースからdebhelperベースへ移行。 パッケージ名の変更あ" -"り。 #887" -msgstr "" -"Debianパッケージをcdbsベースからdebhelperベースへ移行。 パッケージ名の変更あ" -"り。 #887" - -msgid "" -"MeCabトークナイザーの読み込みエラーを無視するようにした。た だし、ログには残" -"る。 #893" -msgstr "" -"MeCabトークナイザーの読み込みエラーを無視するようにした。た だし、ログには残" -"る。 #893" - -msgid "" -"autoconf 2.59環境において、ファイルシステムのルート直下に groongaディレクトリ" -"を作成しようとする問題を修正。 #833" -msgstr "" -"autoconf 2.59環境において、ファイルシステムのルート直下に groongaディレクトリ" -"を作成しようとする問題を修正。 #833" - -msgid "JSONPが動作しなくなっていた問題を修正。" -msgstr "JSONPが動作しなくなっていた問題を修正。" - -msgid "" -"MeCabトークナイザーの読み込みに失敗したときにクラッシュする問題を修正。 " -"（@tomotaka_itoさんが報告）" -msgstr "" -"MeCabトークナイザーの読み込みに失敗したときにクラッシュする問題を修正。 " -"（@tomotaka_itoさんが報告）" - -msgid "[非互換] 位置情報の小数表記からミリ秒への変換誤差が大きい問題を修正。" -msgstr "[非互換] 位置情報の小数表記からミリ秒への変換誤差が大きい問題を修正。" - -msgid "" -":doc:`/reference/functions/geo_in_rectangle` の ``top_left`` と " -"``bottom_right`` に同じ位置を指定するとクラッシュする問題を修正。" -msgstr "" -":doc:`/reference/functions/geo_in_rectangle` の ``top_left`` と " -"``bottom_right`` に同じ位置を指定するとクラッシュする問題を修正。" - -msgid "小数形式のTimeリテラルをロードするとミリ秒情報が落ちる問題を修正。 #880" -msgstr "" -"小数形式のTimeリテラルをロードするとミリ秒情報が落ちる問題を修正。 #880" - -msgid ":doc:`/reference/commands/column_list` のドキュメントを修正。 #758" -msgstr ":doc:`/reference/commands/column_list` のドキュメントを修正。 #758" - -msgid ":doc:`/reference/commands/table_list` のドキュメントを修正。" -msgstr ":doc:`/reference/commands/table_list` のドキュメントを修正。" - -msgid "" -":doc:`/reference/commands/load` で_valueを指定するとメモリリークする問題を修" -"正。 #878" -msgstr "" -":doc:`/reference/commands/load` で_valueを指定するとメモリリークする問題を修" -"正。 #878" - -msgid ":doc:`/reference/commands/load` でクラッシュする問題を修正。 #661" -msgstr ":doc:`/reference/commands/load` でクラッシュする問題を修正。 #661" - -msgid "実験的" -msgstr "実験的" - -msgid "grn_table_truncate()を追加。（実験的。問題あり）" -msgstr "grn_table_truncate()を追加。（実験的。問題あり）" - -msgid "truncateコマンドを追加。（実験的。問題あり） #888" -msgstr "truncateコマンドを追加。（実験的。問題あり） #888" - -msgid "@tomotaka_itoさん" -msgstr "@tomotaka_itoさん" - -msgid "Release 1.3.0 - 2012/01/29" -msgstr "Release 1.3.0 - 2012/01/29" - -msgid "" -"Supported dynamic DB key table change by GRN_DB_KEY=pat or GRN_DB_KEY=dat " -"environment variable value." -msgstr "" -"Supported dynamic DB key table change by GRN_DB_KEY=pat or GRN_DB_KEY=dat " -"environment variable value." - -msgid "" -"Added ``--with-default-db-key`` configure option that specifies the default " -"DB key table." -msgstr "" -"Added ``--with-default-db-key`` configure option that specifies the default " -"DB key table." - -msgid "" -"Supported \"\" value for geo point data types. It's interpreted as \"0x0\"." -msgstr "" -"Supported \"\" value for geo point data types. It's interpreted as \"0x0\"." - -msgid "Added column name to cast error message." -msgstr "Added column name to cast error message." - -msgid "Inhibit file information for stdin on load error." -msgstr "Inhibit file information for stdin on load error." - -msgid "" -"Enabled write-strings warnings and suppress those warnings. [Suggested by " -"montywi]" -msgstr "" -"Enabled write-strings warnings and suppress those warnings. [Suggested by " -"montywi]" - -msgid "Marked MessagePack output format as supported. [#1215]" -msgstr "Marked MessagePack output format as supported. [#1215]" - -msgid "Added ``const`` to ``void *`` of ``*_set_value()``." -msgstr "Added ``const`` to ``void *`` of ``*_set_value()``." - -msgid "Enabled warning flags on C and C++." -msgstr "Enabled warning flags on C and C++." - -msgid "Supported ``--with-libevent`` without value configure option." -msgstr "Supported ``--with-libevent`` without value configure option." - -msgid "``grn_table_get()`` supported grn_db. [#1242]" -msgstr "``grn_table_get()`` supported grn_db. [#1242]" - -msgid "" -"[rpm] Removed needless groogna-munin-plugins dependency from groonga-server. " -"[#1251] [Suggested by Masaharu IWAI]" -msgstr "" -"[rpm] Removed needless groogna-munin-plugins dependency from groonga-server. " -"[#1251] [Suggested by Masaharu IWAI]" - -msgid "" -"[rpm] Removed needless groogna-doc dependency from groonga. [#1251] " -"[Suggested by Masaharu IWAI]" -msgstr "" -"[rpm] Removed needless groogna-doc dependency from groonga. [#1251] " -"[Suggested by Masaharu IWAI]" - -msgid "[dat] Supported repair by ``grn_dat_repair()``." -msgstr "[dat] Supported repair by ``grn_dat_repair()``." - -msgid "``grn_table_at()`` supported grn_db." -msgstr "``grn_table_at()`` supported grn_db." - -msgid "[suggest] Removed unstable mark." -msgstr "[suggest] Removed unstable mark." - -msgid "[suggest][complete] Supported normalized value search in prefix-search." -msgstr "" -"[suggest][complete] Supported normalized value search in prefix-search." - -msgid "" -"Added experimental offline index build. It's disabled by default for now. " -"You can enable it by USE_OFFLINE_INDEXER=yes environment variable." -msgstr "" -"Added experimental offline index build. It's disabled by default for now. " -"You can enable it by USE_OFFLINE_INDEXER=yes environment variable." - -msgid "Added internal API ``grn_obj_path_by_id()`` for mroonga." -msgstr "Added internal API ``grn_obj_path_by_id()`` for mroonga." - -msgid "[suggest][httpd] Passed unknown parameters to groonga." -msgstr "[suggest][httpd] Passed unknown parameters to groonga." - -msgid "[output][xml] Added a newline before ``</RESULT>`` for readability." -msgstr "[output][xml] Added a newline before ``</RESULT>`` for readability." - -msgid "[doc][output] Added documentation about output format type." -msgstr "[doc][output] Added documentation about output format type." - -msgid "Added ``table_rename``. [#1234]" -msgstr "Added ``table_rename``. [#1234]" - -msgid "Added ``column_rename``. [#1234]" -msgstr "Added ``column_rename``. [#1234]" - -msgid "montywi" -msgstr "montywi" - -msgid "Masaharu IWAI" -msgstr "Masaharu IWAI" - -msgid "Release 2.1.2 - 2013/01/29" -msgstr "Release 2.1.2 - 2013/01/29" - -msgid "" -"Supported multiple ``query()`` in a select command. For example, you can " -"specify the keyword which has different weight such as 'query(\"column * " -"weight1\", keyword1) || query(\"column * weight2\", keyword2) || ...' for " -"``--filter``." -msgstr "" -"Supported multiple ``query()`` in a select command. For example, you can " -"specify the keyword which has different weight such as 'query(\"column * " -"weight1\", keyword1) || query(\"column * weight2\", keyword2) || ...' for " -"``--filter``." - -msgid "Dropped experimental view feature." -msgstr "Dropped experimental view feature." - -msgid "" -"Added ``grn_logger_reopen`` API for custom logger. Note that " -"``grn_logger_info`` API is deprecated, use ``grn_logger`` API instead." -msgstr "" -"Added ``grn_logger_reopen`` API for custom logger. Note that " -"``grn_logger_info`` API is deprecated, use ``grn_logger`` API instead." - -msgid "" -"Added ``grn_default_logger_set_path()`` and " -"``grn_default_logger_get_path()`` API. Note that global ``grn_log_path`` " -"variable was removed. Use above API." -msgstr "" -"Added ``grn_default_logger_set_path()`` and " -"``grn_default_logger_get_path()`` API. Note that global ``grn_log_path`` " -"variable was removed. Use above API." - -msgid "" -"Added ``grn_default_query_logger_set_path()`` and " -"``grn_default_query_logger_get_path()`` API. Note that global " -"``grn_qlog_path`` variable was removed. Use above API." -msgstr "" -"Added ``grn_default_query_logger_set_path()`` and " -"``grn_default_query_logger_get_path()`` API. Note that global " -"``grn_qlog_path`` variable was removed. Use above API." - -msgid "" -"Added translated documentation about :doc:`/reference/tables` and :doc:`/" -"reference/normalizers`." -msgstr "" -"Added translated documentation about :doc:`/reference/tables` and :doc:`/" -"reference/normalizers`." - -msgid "" -"[deb][rpm] Improved to install with missing dictionary when ``groonga-" -"tokenizer-mecab`` package is installed." -msgstr "" -"[deb][rpm] Improved to install with missing dictionary when ``groonga-" -"tokenizer-mecab`` package is installed." - -msgid "" -"Supported :ref:`nested-index-search` with range search. For example, you can " -"specify 'column1.column2...columnN <= \"1988-01-04 00:00:00\"' in ``--" -"filter``." -msgstr "" -"Supported :ref:`nested-index-search` with range search. For example, you can " -"specify 'column1.column2...columnN <= \"1988-01-04 00:00:00\"' in ``--" -"filter``." - -msgid "[rpm][fedora] Supported Fedora 18." -msgstr "[rpm][fedora] Supported Fedora 18." - -msgid "[rpm][fedora] Dropped Fedora 17 support." -msgstr "[rpm][fedora] Dropped Fedora 17 support." - -msgid "[doc] Added documentation for :doc:`/server/package`." -msgstr "[doc] Added documentation for :doc:`/server/package`." - -msgid "[doc] Added documentation for :doc:`/reference/functions/query`." -msgstr "[doc] Added documentation for :doc:`/reference/functions/query`." - -msgid "" -"Fixed not to report an error even though MeCab tokenizer shared object isn't " -"found. [groonga-dev,01174] [Reported by wing]" -msgstr "" -"Fixed not to report an error even though MeCab tokenizer shared object isn't " -"found. [groonga-dev,01174] [Reported by wing]" - -msgid "" -"[httpd] Fixed not to fail configure on CentOS 5.4 by setting ``SED`` " -"variable explicitly." -msgstr "" -"[httpd] Fixed not to fail configure on CentOS 5.4 by setting ``SED`` " -"variable explicitly." - -msgid "" -"Fixed a crash bug that not initialized vector column value is accessed by " -"select command." -msgstr "" -"Fixed a crash bug that not initialized vector column value is accessed by " -"select command." - -msgid "wing" -msgstr "wing" - -msgid "Release 2.1.1 - 2012/12/29" -msgstr "Release 2.1.1 - 2012/12/29" - -msgid "" -"This is bug fix release of 2.1.0. All of 2.1.0 users should use 2.1.1 " -"instead." -msgstr "" -"This is bug fix release of 2.1.0. All of 2.1.0 users should use 2.1.1 " -"instead." - -msgid "" -"Fixed a bug that ``KEY_NORMALIZE`` information in database that is created " -"by groonga 2.0.8 or ealier is dropped." -msgstr "" -"Fixed a bug that ``KEY_NORMALIZE`` information in database that is created " -"by groonga 2.0.8 or ealier is dropped." - -msgid "Release 2.1.0 - 2012/12/29" -msgstr "Release 2.1.0 - 2012/12/29" - -msgid "" -"Use 2.1.1 instead of 2.1.0. 2.1.0 has a serious bug related " -"``KEY_NORMALIZE``." -msgstr "" -"Use 2.1.1 instead of 2.1.0. 2.1.0 has a serious bug related " -"``KEY_NORMALIZE``." - -msgid "" -"This release has backward incompatible changes against ``table_list`` and " -"``column_list`` commands. If you use own program which depends on the output " -"results above commands, you need to support null instead of \"null\" string." -msgstr "" -"This release has backward incompatible changes against ``table_list`` and " -"``column_list`` commands. If you use own program which depends on the output " -"results above commands, you need to support null instead of \"null\" string." - -msgid "" -"This release has supported ``--normalizer`` option, but there is side effect " -"for this feature. If you open old version of groonga database at least once, " -"you can not open its database by old version of groonga." -msgstr "" -"This release has supported ``--normalizer`` option, but there is side effect " -"for this feature. If you open old version of groonga database at least once, " -"you can not open its database by old version of groonga." - -msgid "" -"There is also another backward incompatible change agaist plugin API for " -"tokenizer. The argument of ``grn_tokenizer_query_open`` API has changed. " -"This API change affects developer of tokenizer plugin." -msgstr "" -"There is also another backward incompatible change agaist plugin API for " -"tokenizer. The argument of ``grn_tokenizer_query_open`` API has changed. " -"This API change affects developer of tokenizer plugin." - -msgid "[doc] Added documentation about :ref:`nested-index-search`." -msgstr "[doc] Added documentation about :ref:`nested-index-search`." - -msgid "" -"Supported the expression as :doc:`/reference/functions/snippet_html` " -"arguments. This change enables you to use ``snippet_html(\"STRING\" + " -"\"STRING\")`` for example. You can specify column name or literal for " -"\"STRING\". [Reported by Tomoatsu Shimada]" -msgstr "" -"Supported the expression as :doc:`/reference/functions/snippet_html` " -"arguments. This change enables you to use ``snippet_html(\"STRING\" + " -"\"STRING\")`` for example. You can specify column name or literal for " -"\"STRING\". [Reported by Tomoatsu Shimada]" - -msgid "Supported to create own normalizer as a plugin." -msgstr "Supported to create own normalizer as a plugin." - -msgid "" -"Moved ``groonga-query-log-analyzer`` as `groonga-query-log <http://rubygems." -"org/gems/groonga-query-log>`_ RubyGems. It enables you to analyze query logs " -"without installing groonga package." -msgstr "" -"Moved ``groonga-query-log-analyzer`` as `groonga-query-log <http://rubygems." -"org/gems/groonga-query-log>`_ RubyGems. It enables you to analyze query logs " -"without installing groonga package." - -msgid "" -"Supported ``--normalizer`` option for :doc:`/reference/commands/" -"table_create` command. This change enables you to specify normalizer plugin." -msgstr "" -"Supported ``--normalizer`` option for :doc:`/reference/commands/" -"table_create` command. This change enables you to specify normalizer plugin." - -msgid "" -"Changed \"null\" string to null value as meaning for \"No Object\". This is " -"backward incompatible change and affects output results of introspection " -"related commands such as ``table_list`` and ``column_list``." -msgstr "" -"Changed \"null\" string to null value as meaning for \"No Object\". This is " -"backward incompatible change and affects output results of introspection " -"related commands such as ``table_list`` and ``column_list``." - -msgid "" -"Added a flag which controls behavior about normalizer as the last argument " -"of ``grn_tokenizer_query_open`` API." -msgstr "" -"Added a flag which controls behavior about normalizer as the last argument " -"of ``grn_tokenizer_query_open`` API." - -msgid "" -"Supported continuous line in :ref:`command-list-with-continuous-line` list." -msgstr "" -"Supported continuous line in :ref:`command-list-with-continuous-line` list." - -msgid "" -"Improved to support not only no key table, but also hash table, patricia " -"trie and double array trie for :ref:`nested-index-search`." -msgstr "" -"Improved to support not only no key table, but also hash table, patricia " -"trie and double array trie for :ref:`nested-index-search`." - -msgid "" -"[windows] Added missing ``O_BINARY`` flag to open file correctly. This " -"change fixes the infinite loop problem about groonga HTTP server. " -"[GitHub#47] [Patch by Shimomura Tatsuya]" -msgstr "" -"[windows] Added missing ``O_BINARY`` flag to open file correctly. This " -"change fixes the infinite loop problem about groonga HTTP server. " -"[GitHub#47] [Patch by Shimomura Tatsuya]" - -msgid "" -"Fixed a bug that ``--default-match-escalation-threshold`` doesn't accept " -"negative value to disable functionality that is used on :doc:`/spec/" -"search`. This fix enable you to disable search escalation. see :option:`--" -"default-match-escalation-threshold` about details." -msgstr "" - -msgid "" -"Fixed a bug that ``_score`` after \"*\" is ignored in ``--output_columns``." -msgstr "" -"Fixed a bug that ``_score`` after \"*\" is ignored in ``--output_columns``." - -msgid "Tomoatsu Shimada" -msgstr "Tomoatsu Shimada" - -msgid "Shimomura Tatsuya" -msgstr "Shimomura Tatsuya" - -msgid "Release 2.0.9 - 2012/11/29" -msgstr "Release 2.0.9 - 2012/11/29" - -msgid "" -"Supported to calculate the value of distance accross border in " -"``geo_distance`` with ``rectangle`` as approximate type. [#1534]" -msgstr "" -"Supported to calculate the value of distance accross border in " -"``geo_distance`` with ``rectangle`` as approximate type. [#1534]" - -msgid "[doc] Added the :doc:`/spec/gqtp` specification." -msgstr "[doc] Added the :doc:`/spec/gqtp` specification." - -msgid "" -"Improved to ignore non critical ``getaddrinfo()`` error which groonga " -"command emits on startup. This change does not affects nomal use of groonga " -"because it just checked whether default hostname is resolved in previous " -"version." -msgstr "" -"Improved to ignore non critical ``getaddrinfo()`` error which groonga " -"command emits on startup. This change does not affects nomal use of groonga " -"because it just checked whether default hostname is resolved in previous " -"version." - -msgid "" -"[experimental] Added ``snippet_html()`` function which extract keyword and " -"surrounding text. See :doc:`/reference/functions/snippet_html` about details." -msgstr "" -"[experimental] Added ``snippet_html()`` function which extract keyword and " -"surrounding text. See :doc:`/reference/functions/snippet_html` about details." - -msgid "" -"Supported to report error reason when error occured during reading table " -"record." -msgstr "" -"Supported to report error reason when error occured during reading table " -"record." - -msgid "" -"Supported to search with keyword by nested index notation ( concatinate " -"multiple indexed column name with dot character ) if there is a relationship " -"between multiple table with index." -msgstr "" -"Supported to search with keyword by nested index notation ( concatinate " -"multiple indexed column name with dot character ) if there is a relationship " -"between multiple table with index." - -msgid "" -"Supported to log \"[tokenizer][mecab]\" tag when using ``TokenMecab`` " -"tokenizer." -msgstr "" -"Supported to log \"[tokenizer][mecab]\" tag when using ``TokenMecab`` " -"tokenizer." - -msgid "" -"Supported to log \"[tokenizer][kytea]\" tag when using ``TokenKyTea`` " -"tokenizer." -msgstr "" -"Supported to log \"[tokenizer][kytea]\" tag when using ``TokenKyTea`` " -"tokenizer." - -msgid "" -"Improved to use separated array for command error location as output " -"results. This change is incompatibility change, but does not affects " -"existing program." -msgstr "" -"Improved to use separated array for command error location as output " -"results. This change is incompatibility change, but does not affects " -"existing program." - -msgid "Added documentation for :doc:`/reference/command/output_format`." -msgstr "Added documentation for :doc:`/reference/command/output_format`." - -msgid "" -"Added documentation for :doc:`/reference/command/return_code` of output " -"results." -msgstr "" -"Added documentation for :doc:`/reference/command/return_code` of output " -"results." - -msgid "Supported range search by using index." -msgstr "Supported range search by using index." - -msgid "" -"Fixed to use network byte order for status code of :ref:`gqtp-header-spec` " -"to follow the normal network protocol convention. This change affects that " -"groonga <= 2.0.8 client which connects to groonga server 2.0.9 or later can " -"not show status code properly when command failed." -msgstr "" -"Fixed to use network byte order for status code of :ref:`gqtp-header-spec` " -"to follow the normal network protocol convention. This change affects that " -"groonga <= 2.0.8 client which connects to groonga server 2.0.9 or later can " -"not show status code properly when command failed." - -msgid "" -"Fixed a bug that UTF-8 normalization computes wrong offset which affects to " -"return value of ``snippet_html()``. This change not to insert tag of snippet " -"into invalid location. [#1531] [Reported by Tomoatsu Shimada]" -msgstr "" -"Fixed a bug that UTF-8 normalization computes wrong offset which affects to " -"return value of ``snippet_html()``. This change not to insert tag of snippet " -"into invalid location. [#1531] [Reported by Tomoatsu Shimada]" - -msgid "" -"[windows] Fixed over allocated memory access which cause segmentation fault " -"on startup by groonga command. [#1532] [Patch by Akio Tajima]" -msgstr "" -"[windows] Fixed over allocated memory access which cause segmentation fault " -"on startup by groonga command. [#1532] [Patch by Akio Tajima]" - -msgid "" -"[windows] Fixed a bug that data stored in column couldn't be read when total " -"amount of data stored in column exceeds 128MB. [groonga-dev,01088] [Reported " -"by ongaeshi]" -msgstr "" -"[windows] Fixed a bug that data stored in column couldn't be read when total " -"amount of data stored in column exceeds 128MB. [groonga-dev,01088] [Reported " -"by ongaeshi]" - -msgid "" -"Fixed a bug that searching with indexed column for ``Int*`` and ``UInt*`` " -"except ``Int32/Uint32`` returns invalid results." -msgstr "" -"Fixed a bug that searching with indexed column for ``Int*`` and ``UInt*`` " -"except ``Int32/Uint32`` returns invalid results." - -msgid "Fixed a bug that deleting record can be found." -msgstr "Fixed a bug that deleting record can be found." - -msgid "" -"Fixed a bug that latin1 and koi8r normalizations could not process all " -"string data if given string contains NULL character on the way." -msgstr "" -"Fixed a bug that latin1 and koi8r normalizations could not process all " -"string data if given string contains NULL character on the way." - -msgid "" -"Fixed to return the correct default value of type when no data stored in " -"column is referenced by ``select`` command." -msgstr "" -"Fixed to return the correct default value of type when no data stored in " -"column is referenced by ``select`` command." - -msgid "" -"Fixed to exclude the value of vector column metadata in :ref:`offline-index-" -"construction`. This change not to contain such a metadata as search results." -msgstr "" -"Fixed to exclude the value of vector column metadata in :ref:`offline-index-" -"construction`. This change not to contain such a metadata as search results." - -msgid "Akio Tajima" -msgstr "Akio Tajima" - -msgid "ongaeshi" -msgstr "ongaeshi" - -msgid "Release 2.0.8 - 2012/10/29" -msgstr "Release 2.0.8 - 2012/10/29" - -msgid "" -"[rpm] Improved the description of server-http and httpd packages. [Suggested " -"by Daiki Ueno]" -msgstr "" -"[rpm] Improved the description of server-http and httpd packages. [Suggested " -"by Daiki Ueno]" - -msgid "Supported custom query expansion by plugin." -msgstr "Supported custom query expansion by plugin." - -msgid "[experimental] Added query expander ``QueryExpanderTSV`` plugin." -msgstr "[experimental] Added query expander ``QueryExpanderTSV`` plugin." - -msgid "Supported Ubuntu 12.10 Quantal Quetzal" -msgstr "Supported Ubuntu 12.10 Quantal Quetzal" - -msgid "[experimental] Supported function call in ``output_columns``." -msgstr "[experimental] Supported function call in ``output_columns``." - -msgid "" -"[doc][rpm] Add missing description about installing MeCab dictionary. " -"[Reported by serihiro]" -msgstr "" -"[doc][rpm] Add missing description about installing MeCab dictionary. " -"[Reported by serihiro]" - -msgid "" -"[rpm] Fixed to remove needless \"Requires\" from spec file. [Reported by " -"Daiki Ueno]" -msgstr "" -"[rpm] Fixed to remove needless \"Requires\" from spec file. [Reported by " -"Daiki Ueno]" - -msgid "" -"[rpm] Fixed inaccurate description about license of groonga-server-gqtp." -msgstr "" -"[rpm] Fixed inaccurate description about license of groonga-server-gqtp." - -msgid "" -"[admin] Fixed record edit button shows wrong record. [GitHub#34] [Reported " -"by firewood]" -msgstr "" -"[admin] Fixed record edit button shows wrong record. [GitHub#34] [Reported " -"by firewood]" - -msgid "[deb] Fixed to remove needless dependency to pcre." -msgstr "[deb] Fixed to remove needless dependency to pcre." - -msgid "[deb] Fixed to bundle missing table plugin." -msgstr "[deb] Fixed to bundle missing table plugin." - -msgid "firewood" -msgstr "firewood" - -msgid "serihiro" -msgstr "serihiro" - -msgid "Release 2.0.7 - 2012/09/29" -msgstr "Release 2.0.7 - 2012/09/29" - -msgid "[doc] Added more descriptions about ``--query_flags``." -msgstr "[doc] Added more descriptions about ``--query_flags``." - -msgid "[doc][httpd] Added sample configuration for gzip compression." -msgstr "[doc][httpd] Added sample configuration for gzip compression." - -msgid "[httpd][rpm][centos] Added groonga-httpd init script." -msgstr "[httpd][rpm][centos] Added groonga-httpd init script." - -msgid "[rpm] Added logrotate config files." -msgstr "[rpm] Added logrotate config files." - -msgid "Supported creating database during install process." -msgstr "Supported creating database during install process." - -msgid "[httpd] Supported ``groonga_database_auto_create`` directive." -msgstr "[httpd] Supported ``groonga_database_auto_create`` directive." - -msgid "Supported score respected merge by set operation. [GitHub#31]" -msgstr "Supported score respected merge by set operation. [GitHub#31]" - -msgid "[httpd] Supported ``load`` command by POST." -msgstr "[httpd] Supported ``load`` command by POST." - -msgid "Added error check for creating temporary result set. [GitHub#33]" -msgstr "Added error check for creating temporary result set. [GitHub#33]" - -msgid "Added GQTP server package." -msgstr "Added GQTP server package." - -msgid "Added ``max()`` function." -msgstr "Added ``max()`` function." - -msgid "Added ``min()`` function." -msgstr "Added ``min()`` function." - -msgid "Fixed to set domain to vector elements to ``load`` command. [GitHub#30]" -msgstr "" -"Fixed to set domain to vector elements to ``load`` command. [GitHub#30]" - -msgid "[httpd] Fixed missing NULL initialization. [Reported by @Kiske]" -msgstr "[httpd] Fixed missing NULL initialization. [Reported by @Kiske]" - -msgid "[httpd] Fixed missing size about ``content_type_len``." -msgstr "[httpd] Fixed missing size about ``content_type_len``." - -msgid "[rpm][fedora] Fixed to use ``--bind-address`` in ``groonga.service``." -msgstr "[rpm][fedora] Fixed to use ``--bind-address`` in ``groonga.service``." - -msgid "Fixed crash by invalid argument filter. [GitHub#32]" -msgstr "Fixed crash by invalid argument filter. [GitHub#32]" - -msgid "Fixed a bug that Time -> Time cast breaks value." -msgstr "Fixed a bug that Time -> Time cast breaks value." - -msgid "Fixed a bug that Time -> Float cast breaks value." -msgstr "Fixed a bug that Time -> Float cast breaks value." - -msgid "@Kiske" -msgstr "@Kiske" - -msgid "Release 2.0.6 - 2012/08/29" -msgstr "Release 2.0.6 - 2012/08/29" - -msgid "[deb][rpm] Added ``groonga-server-common`` meta package. [#1451]" -msgstr "[deb][rpm] Added ``groonga-server-common`` meta package. [#1451]" - -msgid "Supported ``--query_flags`` option to ``select`` command." -msgstr "Supported ``--query_flags`` option to ``select`` command." - -msgid "Supported PCRE auto detection for groonga-httpd." -msgstr "Supported PCRE auto detection for groonga-httpd." - -msgid "[doc] Added information about Twitter and Facebook." -msgstr "[doc] Added information about Twitter and Facebook." - -msgid "Improved to show error message from MeCab on ``mecab_new2()`` failure." -msgstr "Improved to show error message from MeCab on ``mecab_new2()`` failure." - -msgid "[doc] Added details about groonga for server use." -msgstr "[doc] Added details about groonga for server use." - -msgid "Improved to log details about ``vm.overcommit_memory``." -msgstr "Improved to log details about ``vm.overcommit_memory``." - -msgid "Supported custom selector definition." -msgstr "Supported custom selector definition." - -msgid "Supported ``--working-directory`` option for groonga." -msgstr "Supported ``--working-directory`` option for groonga." - -msgid "Supported ``dump`` command for groonga-httpd." -msgstr "Supported ``dump`` command for groonga-httpd." - -msgid "Improved to show not found target name for ``clearlock`` command." -msgstr "Improved to show not found target name for ``clearlock`` command." - -msgid "" -"Improved error messages about ``get`` command implemented by table plugin." -msgstr "" -"Improved error messages about ``get`` command implemented by table plugin." - -msgid "" -"[rpm][centos] Supported MeCab 0.994. [#1455] [Suggested by IWAI, Masaharu]" -msgstr "" -"[rpm][centos] Supported MeCab 0.994. [#1455] [Suggested by IWAI, Masaharu]" - -msgid "Supported changing default logger's max level before ``grn_init()``." -msgstr "Supported changing default logger's max level before ``grn_init()``." - -msgid "" -"Added ``all_records()`` function which copies all record IDs to the result " -"table." -msgstr "" -"Added ``all_records()`` function which copies all record IDs to the result " -"table." - -msgid "Supported '-WORD' in ``--query`` of the select command." -msgstr "Supported '-WORD' in ``--query`` of the select command." - -msgid "" -"[doc] Fixed the execution examples. [#1428] [Reported by IWAI, Masaharu]" -msgstr "" -"[doc] Fixed the execution examples. [#1428] [Reported by IWAI, Masaharu]" - -msgid "" -"[deb] Fixed not to force groonga user/group by init script for groonga-httpd." -msgstr "" -"[deb] Fixed not to force groonga user/group by init script for groonga-httpd." - -msgid "[rpm][fedora] Fixed missing stop parameter for groonga-httpd service." -msgstr "[rpm][fedora] Fixed missing stop parameter for groonga-httpd service." - -msgid "" -"Fixed a bug that the last 1 byte for cache key is ignored by ``select`` " -"command." -msgstr "" -"Fixed a bug that the last 1 byte for cache key is ignored by ``select`` " -"command." - -msgid "" -"Fixed detection of the number of arguments in the complex function call." -msgstr "" -"Fixed detection of the number of arguments in the complex function call." - -msgid "Fixed to suppress a warning by Clang." -msgstr "Fixed to suppress a warning by Clang." - -msgid "" -"Fixed backward incompatibility about missing ``add`` command related error " -"by executing ``clearlock`` command." -msgstr "" -"Fixed backward incompatibility about missing ``add`` command related error " -"by executing ``clearlock`` command." - -msgid "" -"[windows] Fixed database open failure which is related to binary data. " -"[Reported by @yito]" -msgstr "" -"[windows] Fixed database open failure which is related to binary data. " -"[Reported by @yito]" - -msgid "IWAI, Masaharu" -msgstr "IWAI, Masaharu" - -msgid "@yito" -msgstr "@yito" - -msgid "Release 2.0.5 - 2012/07/29" -msgstr "Release 2.0.5 - 2012/07/29" - -msgid "" -"Supported calculating the value of distance with \"rect\" or \"rectangle\" " -"argument in southern hemisphere. [#1418] [#1419] [#1420] [#1421]" -msgstr "" -"Supported calculating the value of distance with \"rect\" or \"rectangle\" " -"argument in southern hemisphere. [#1418] [#1419] [#1420] [#1421]" - -msgid "[doc] Added some literals description in script syntax." -msgstr "[doc] Added some literals description in script syntax." - -msgid "Supported other directory build for groonga-suggest and groonga-httpd." -msgstr "Supported other directory build for groonga-suggest and groonga-httpd." - -msgid "" -"Supported \";\" as a query parameter separator. [#1406] [Suggested by IWAI, " -"Masaharu]" -msgstr "" -"Supported \";\" as a query parameter separator. [#1406] [Suggested by IWAI, " -"Masaharu]" - -msgid "[doc] Added descriptions about script syntax." -msgstr "[doc] Added descriptions about script syntax." - -msgid "" -"Supported near search by ``'column *N \"word1 word2 ...\"'`` in script " -"syntax. [#1423]" -msgstr "" -"Supported near search by ``'column *N \"word1 word2 ...\"'`` in script " -"syntax. [#1423]" - -msgid "[doc] Added a description about limitation of suffix search." -msgstr "[doc] Added a description about limitation of suffix search." - -msgid "Supported near search for ``_key`` pseudo column. [GitHub#19]" -msgstr "Supported near search for ``_key`` pseudo column. [GitHub#19]" - -msgid "[doc] Added basic ECMAScript related syntaxes." -msgstr "[doc] Added basic ECMAScript related syntaxes." - -msgid "" -"[doc] Updated a description about :doc:`/reference/functions/geo_distance`." -msgstr "" -"[doc] Updated a description about :doc:`/reference/functions/geo_distance`." - -msgid "[rpm][fedora] Supported Fedora 17." -msgstr "[rpm][fedora] Supported Fedora 17." - -msgid "[rpm][fedora] Dropped Fedora 16 support." -msgstr "[rpm][fedora] Dropped Fedora 16 support." - -msgid "Supported logical not ``\"!\"`` operator. [GitHub#22]" -msgstr "Supported logical not ``\"!\"`` operator. [GitHub#22]" - -msgid "[httpd] Supported per location groonga database." -msgstr "[httpd] Supported per location groonga database." - -msgid "Improved to return error messages while load command is processing." -msgstr "Improved to return error messages while load command is processing." - -msgid "Improved to exit load command when an uncontinuable error occurred." -msgstr "Improved to exit load command when an uncontinuable error occurred." - -msgid "Improved to stop load command for invalid --columns value." -msgstr "Improved to stop load command for invalid --columns value." - -msgid "Supported to open locked database. [GitHub#21]" -msgstr "Supported to open locked database. [GitHub#21]" - -msgid "" -"Fixed a build problem about groonga-httpd on Mac OS X. [Reported by SHIMADA " -"Koji]" -msgstr "" -"Fixed a build problem about groonga-httpd on Mac OS X. [Reported by SHIMADA " -"Koji]" - -msgid "Fixed not to use installed groonga's header files for groonga-httpd." -msgstr "Fixed not to use installed groonga's header files for groonga-httpd." - -msgid "Fixed a build problem about groonga on Mac OS X Lion." -msgstr "Fixed a build problem about groonga on Mac OS X Lion." - -msgid "" -"[doc] Fixed a description of :doc:`/reference/commands/table_remove` command." -msgstr "" -"[doc] Fixed a description of :doc:`/reference/commands/table_remove` command." - -msgid "" -"Fixed infinite loop problem for not implemented operator without index. " -"[GitHub#20]" -msgstr "" -"Fixed infinite loop problem for not implemented operator without index. " -"[GitHub#20]" - -msgid "Fixed a wrong error code which causes memory leaks." -msgstr "Fixed a wrong error code which causes memory leaks." - -msgid "Fixed a wrong error code which collapse ja columns." -msgstr "Fixed a wrong error code which collapse ja columns." - -msgid "[admin] Fixed to escape error message." -msgstr "[admin] Fixed to escape error message." - -msgid "" -"Fixed to ignore unloadable objects which causes database incompatible. " -"[#1429] [Reported by IWAI, Masaharu]" -msgstr "" -"Fixed to ignore unloadable objects which causes database incompatible. " -"[#1429] [Reported by IWAI, Masaharu]" - -msgid "SHIMADA Koji" -msgstr "SHIMADA Koji" - -msgid "Release 2.0.4 - 2012/06/29" -msgstr "Release 2.0.4 - 2012/06/29" - -msgid "Supported only KyTea 0.4.2." -msgstr "Supported only KyTea 0.4.2." - -msgid "Dropped KyTea 0.4.1 or ealier support." -msgstr "Dropped KyTea 0.4.1 or ealier support." - -msgid "[experimental] Supported nginx based groonga HTTP interface." -msgstr "[experimental] Supported nginx based groonga HTTP interface." - -msgid "" -"Supported calculating the value of distance with \"rect\" or \"rectangle\" " -"argument in northern hemisphere. [#1386] [#1387] [#1388] [#1389]" -msgstr "" -"Supported calculating the value of distance with \"rect\" or \"rectangle\" " -"argument in northern hemisphere. [#1386] [#1387] [#1388] [#1389]" - -msgid "[doc] Added a document about :doc:`/development/travis-ci` integration." -msgstr "" -"[doc] Added a document about :doc:`/development/travis-ci` integration." - -msgid "" -"[doc] Added descriptions about full text search and phrase search. See :ref:" -"`full-text-search-condition` and :ref:`phrase-search-condition` about detail." -msgstr "" -"[doc] Added descriptions about full text search and phrase search. See :ref:" -"`full-text-search-condition` and :ref:`phrase-search-condition` about detail." - -msgid "" -"[doc] Added descriptions about comparison conditions. See :ref:`conditional-" -"expression` about detail." -msgstr "" -"[doc] Added descriptions about comparison conditions. See :ref:`conditional-" -"expression` about detail." - -msgid "[doc] Added examples for :doc:`/reference/grn_expr/query_syntax`." -msgstr "[doc] Added examples for :doc:`/reference/grn_expr/query_syntax`." - -msgid "[doc] Added descriptions about :ref:`combined-expression`." -msgstr "[doc] Added descriptions about :ref:`combined-expression`." - -msgid "" -"[doc] Added descriptions about :ref:`prefix-search-condition` and :ref:" -"`suffix-search-condition`." -msgstr "" -"[doc] Added descriptions about :ref:`prefix-search-condition` and :ref:" -"`suffix-search-condition`." - -msgid "Supported suffix search by index." -msgstr "Supported suffix search by index." - -msgid "[doc] Added a document about :doc:`/reference/grn_expr`." -msgstr "[doc] Added a document about :doc:`/reference/grn_expr`." - -msgid "" -"[munin] Supported JSON library installed by RubyGems [GitHub#17] [Patch by " -"IWAI, Masaharu]" -msgstr "" -"[munin] Supported JSON library installed by RubyGems [GitHub#17] [Patch by " -"IWAI, Masaharu]" - -msgid "" -"[doc] Updated the description of how to specify a value as Time in tutorial. " -"[#1405] [Reported by IWAI, Masaharu]" -msgstr "" -"[doc] Updated the description of how to specify a value as Time in tutorial. " -"[#1405] [Reported by IWAI, Masaharu]" - -msgid "" -"[rpm] Removed groonga-tokenizer-mecab dependency from groonga package. " -"[GitHub#18] [Patch by IWAI, Masaharu]" -msgstr "" -"[rpm] Removed groonga-tokenizer-mecab dependency from groonga package. " -"[GitHub#18] [Patch by IWAI, Masaharu]" - -msgid "" -"Fixed a problem that display of command prompt changes to not intended state " -"by using batch mode on Mac OS X. [Reported by @soundkitchen]" -msgstr "" -"Fixed a problem that display of command prompt changes to not intended state " -"by using batch mode on Mac OS X. [Reported by @soundkitchen]" - -msgid "Fixed not to terminate after an invalid command in client mode. [#1305]" -msgstr "" -"Fixed not to terminate after an invalid command in client mode. [#1305]" - -msgid "" -"Fixed a problem that '=R' is treated as 'OR' in ``--query`` syntax. [#1393]" -msgstr "" -"Fixed a problem that '=R' is treated as 'OR' in ``--query`` syntax. [#1393]" - -msgid "Release 2.0.3 - 2012/05/29" -msgstr "Release 2.0.3 - 2012/05/29" - -msgid "[doc] Added about release procedure." -msgstr "[doc] Added about release procedure." - -msgid "Removed restriction that the max number of opened files is 4096." -msgstr "Removed restriction that the max number of opened files is 4096." - -msgid "[experimental] Added table plugin." -msgstr "[experimental] Added table plugin." - -msgid "" -"[doc] Added more descriptions about :doc:`/reference/commands/select` " -"command." -msgstr "" -"[doc] Added more descriptions about :doc:`/reference/commands/select` " -"command." - -msgid "[doc] Made execution example copy & paste friendly." -msgstr "[doc] Made execution example copy & paste friendly." - -msgid "" -"[windows] Supported build with Visual Studio 2010 Express and CMake. See :" -"doc:`/install/windows` about details." -msgstr "" -"[windows] Supported build with Visual Studio 2010 Express and CMake. See :" -"doc:`/install/windows` about details." - -msgid "" -"[doc][solaris] Added a document about building on Solaris. See :doc:`/" -"install/solaris` about details." -msgstr "" -"[doc][solaris] Added a document about building on Solaris. See :doc:`/" -"install/solaris` about details." - -msgid "" -"[doc][yum] Updated epel-release package version. [Reported by IWAI, Masaharu]" -msgstr "" -"[doc][yum] Updated epel-release package version. [Reported by IWAI, Masaharu]" - -msgid "" -"[doc][cenos6] Disabled Repoforge for Munin for CentOS 6. [Reported by IWAI, " -"Masaharu]" -msgstr "" -"[doc][cenos6] Disabled Repoforge for Munin for CentOS 6. [Reported by IWAI, " -"Masaharu]" - -msgid "Started distributing source archive in zip format." -msgstr "Started distributing source archive in zip format." - -msgid "" -"[munin] groonga_dist Munin plugin supported an object that has separated " -"files." -msgstr "" -"[munin] groonga_dist Munin plugin supported an object that has separated " -"files." - -msgid "Started using Travis CI." -msgstr "Started using Travis CI." - -msgid "" -"[yum] Changed RPM package name that provides yum repository from groonga-" -"repository to groonga-release to follow RPM package name convension such as " -"centos-release and fedora-release." -msgstr "" -"[yum] Changed RPM package name that provides yum repository from groonga-" -"repository to groonga-release to follow RPM package name convension such as " -"centos-release and fedora-release." - -msgid "" -"[doc] Fixed a command to update yum repository. [Suggested by IWAI, Masaharu]" -msgstr "" -"[doc] Fixed a command to update yum repository. [Suggested by IWAI, Masaharu]" - -msgid "" -"[deb] Fixed a bug that log_repoen command in logrotate uses wrong protocol." -msgstr "" -"[deb] Fixed a bug that log_repoen command in logrotate uses wrong protocol." - -msgid "" -"Fixed broken ERROR tag in XML response. [#1363] [GitHub#13] [Patch by IWAI, " -"Masaharu]" -msgstr "" -"Fixed broken ERROR tag in XML response. [#1363] [GitHub#13] [Patch by IWAI, " -"Masaharu]" - -msgid "Fixed a bug that grn_ctx isn't fully cleared by grn_ctx_fin()." -msgstr "Fixed a bug that grn_ctx isn't fully cleared by grn_ctx_fin()." - -msgid "" -"Fixed a bug that ``&!`` set operation doesn't work with grouped expression. " -"[#1372]" -msgstr "" -"Fixed a bug that ``&!`` set operation doesn't work with grouped expression. " -"[#1372]" - -msgid "" -"Fixed a bug that a record key registered via index source isn't normalized." -msgstr "" -"Fixed a bug that a record key registered via index source isn't normalized." - -msgid "Release 2.0.2 - 2012/04/29" -msgstr "Release 2.0.2 - 2012/04/29" - -msgid "" -"The package sign key is changed since this release. Import the new package " -"sign key before updating groogna packages." -msgstr "" -"The package sign key is changed since this release. Import the new package " -"sign key before updating groogna packages." - -msgid "Debian/Ubuntu::" -msgstr "Debian/Ubuntu::" - -msgid "CentOS/Fedora::" -msgstr "CentOS/Fedora::" - -msgid "[pkg-config] Removed needless MessagePack dependency." -msgstr "[pkg-config] Removed needless MessagePack dependency." - -msgid "[rpm][fedora] Supported libedit. [#1325] [Suggested by IWAI, Masaharu]" -msgstr "[rpm][fedora] Supported libedit. [#1325] [Suggested by IWAI, Masaharu]" - -msgid "[rpm] Supported zlib and LZO. [#1324] [Patch by IWAI, Masaharu]" -msgstr "[rpm] Supported zlib and LZO. [#1324] [Patch by IWAI, Masaharu]" - -msgid "" -"[groonga] Improved daemoinzed timing. Groonga server daemonizes after socket " -"is listened. It means that groonga server is ready when groonga server is " -"daemonized. [#1326]" -msgstr "" -"[groonga] Improved daemoinzed timing. Groonga server daemonizes after socket " -"is listened. It means that groonga server is ready when groonga server is " -"daemonized. [#1326]" - -msgid "[admin] Supported suggest in groonga administration page." -msgstr "[admin] Supported suggest in groonga administration page." - -msgid "[dump] Ignored MeCab tokenizer load error." -msgstr "[dump] Ignored MeCab tokenizer load error." - -msgid "Supported CMake." -msgstr "Supported CMake." - -msgid "[load] Supported error report when a column value can't be set." -msgstr "[load] Supported error report when a column value can't be set." - -msgid "" -"Supported similar search. ``select --filter \"column *S 'TEXT'\"`` is the " -"similar search syntax. [#1342]" -msgstr "" -"Supported similar search. ``select --filter \"column *S 'TEXT'\"`` is the " -"similar search syntax. [#1342]" - -msgid "[apt][yum] Changed package sign key." -msgstr "[apt][yum] Changed package sign key." - -msgid "Supported Ubuntu Precise Pangolin." -msgstr "Supported Ubuntu Precise Pangolin." - -msgid "" -"[apt] Added a new groonga-keyring deb package for the groonga's package sign " -"key." -msgstr "" -"[apt] Added a new groonga-keyring deb package for the groonga's package sign " -"key." - -msgid "" -"[deb][rpm] Used ``--bind-address`` option instead of deprecated ``--" -"address`` option. [#1320] [Patch by IWAI, Masaharu]" -msgstr "" -"[deb][rpm] Used ``--bind-address`` option instead of deprecated ``--" -"address`` option. [#1320] [Patch by IWAI, Masaharu]" - -msgid "" -"[deb] Renamed groonga-server package's configuration file to /etc/default/" -"groonga-server from /etc/default/groonga." -msgstr "" -"[deb] Renamed groonga-server package's configuration file to /etc/default/" -"groonga-server from /etc/default/groonga." - -msgid "" -"[rpm][fedora] Fixed upgrade condition in %post server. [GitHub#11] [Patch by " -"Daiki Ueno]" -msgstr "" -"[rpm][fedora] Fixed upgrade condition in %post server. [GitHub#11] [Patch by " -"Daiki Ueno]" - -msgid "[rpm] Removed needless change logs. [#1328] [Patch by IWAI, Masaharu]" -msgstr "[rpm] Removed needless change logs. [#1328] [Patch by IWAI, Masaharu]" - -msgid "" -"[deb][rpm] Added missing curl dependency. [GitHub#12] [Patch by IWAI, " -"Masaharu]" -msgstr "" -"[deb][rpm] Added missing curl dependency. [GitHub#12] [Patch by IWAI, " -"Masaharu]" - -msgid "" -"[rpm] Removed needleess ruby package dependency from groonga package. " -"[#1330] [Suggested by IWAI, Masaharu]" -msgstr "" -"[rpm] Removed needleess ruby package dependency from groonga package. " -"[#1330] [Suggested by IWAI, Masaharu]" - -msgid "" -"[deb] Added missing default values to groonga-server's configuration file." -msgstr "" -"[deb] Added missing default values to groonga-server's configuration file." - -msgid "" -"Fixed a crash bug that is caused when searching with updaging very large " -"inverted index. [#1329]" -msgstr "" -"Fixed a crash bug that is caused when searching with updaging very large " -"inverted index. [#1329]" - -msgid "" -"Fixed a bug that strings are compared as characters instead of byte string. " -"[#1340] [Reported by Shinya Kawaji]" -msgstr "" -"Fixed a bug that strings are compared as characters instead of byte string. " -"[#1340] [Reported by Shinya Kawaji]" - -msgid "Shinya Kawaji" -msgstr "Shinya Kawaji" - -msgid "Release 2.0.1 - 2012/03/29" -msgstr "Release 2.0.1 - 2012/03/29" - -msgid "Supported build in other directory. [#1298] [Reported by Kazuhiko]" -msgstr "Supported build in other directory. [#1298] [Reported by Kazuhiko]" - -msgid "[solaris] Supported build on Solaris 11. [Reported by Kazuhiko]" -msgstr "[solaris] Supported build on Solaris 11. [Reported by Kazuhiko]" - -msgid "[test] Supported functional test." -msgstr "[test] Supported functional test." - -msgid "[test] Required ``--with-ruby19`` configure option for testing by Ruby." -msgstr "" -"[test] Required ``--with-ruby19`` configure option for testing by Ruby." - -msgid "[dump] Supported records dump for a table that has default tokenizer." -msgstr "[dump] Supported records dump for a table that has default tokenizer." - -msgid "[suggest] Added ``similar_search`` option." -msgstr "[suggest] Added ``similar_search`` option." - -msgid "" -"[groonga] Removed deprecated options, ``-a``, ``--address`` and ``--admin-" -"html-path``." -msgstr "" -"[groonga] Removed deprecated options, ``-a``, ``--address`` and ``--admin-" -"html-path``." - -msgid "Added more return value checks. [GitHub#9] [Reported by Markus Elfring]" -msgstr "" -"Added more return value checks. [GitHub#9] [Reported by Markus Elfring]" - -msgid "[dat] Supported term extract operation." -msgstr "[dat] Supported term extract operation." - -msgid "Added `logos <http://groonga.org/logo/>`_ ." -msgstr "Added `logos <http://groonga.org/logo/>`_ ." - -msgid "Updated HTML design." -msgstr "Updated HTML design." - -msgid "Renamed ``grntest`` to ``groonga-benchmark``." -msgstr "Renamed ``grntest`` to ``groonga-benchmark``." - -msgid "Supported ``autogen.sh`` on CentOS 5." -msgstr "Supported ``autogen.sh`` on CentOS 5." - -msgid "" -"[linux] Added ``vm.overcommit_memory`` kernel parameter value check. [#1289]" -msgstr "" -"[linux] Added ``vm.overcommit_memory`` kernel parameter value check. [#1289]" - -msgid "``grn_snip`` uses ``grn_obj`` mechanism. [#1054]" -msgstr "``grn_snip`` uses ``grn_obj`` mechanism. [#1054]" - -msgid "" -"Fixed a bug that uninstall task doesn't uninstall installed Ruby scripts. " -"[#1299] [Reported by Kazuhiko]" -msgstr "" -"Fixed a bug that uninstall task doesn't uninstall installed Ruby scripts. " -"[#1299] [Reported by Kazuhiko]" - -msgid "Added a missing Gemfile. [#1302] [Reported by Kazuhiko]" -msgstr "Added a missing Gemfile. [#1302] [Reported by Kazuhiko]" - -msgid "" -"Fixed a bug that some indexed records aren't found. The feature is only used " -"by mroonga. [#1303]" -msgstr "" -"Fixed a bug that some indexed records aren't found. The feature is only used " -"by mroonga. [#1303]" - -msgid "[groonga] Appended missing ``-id`` to ``--server-id`` option name." -msgstr "[groonga] Appended missing ``-id`` to ``--server-id`` option name." - -msgid "Fixed a bug that latin1 normalization may access unexpected memory." -msgstr "Fixed a bug that latin1 normalization may access unexpected memory." - -msgid "Kazuhiko" -msgstr "Kazuhiko" - -msgid "Markus Elfring" -msgstr "Markus Elfring" - -msgid "Release 2.0.0 - 2012/02/29" -msgstr "Release 2.0.0 - 2012/02/29" - -msgid "[dat] Added 0 length key check." -msgstr "[dat] Added 0 length key check." - -msgid "" -"[windows] Added missing GCC related DLLs. [groonga-dev,00686] [Reported by " -"Suzuki]" -msgstr "" -"[windows] Added missing GCC related DLLs. [groonga-dev,00686] [Reported by " -"Suzuki]" - -msgid "[php] Supported PHP 5.4. [Patch by Daiki Ueno]" -msgstr "[php] Supported PHP 5.4. [Patch by Daiki Ueno]" - -msgid "Updated FSF address. [Suggested by Daiki Ueno]" -msgstr "Updated FSF address. [Suggested by Daiki Ueno]" - -msgid "[fedora] Supported systemd. [Patch by Daiki Ueno]" -msgstr "[fedora] Supported systemd. [Patch by Daiki Ueno]" - -msgid "[rpm][debian] Changed the default protocol to HTTP from gqtp." -msgstr "[rpm][debian] Changed the default protocol to HTTP from gqtp." - -msgid "[rpm][centos] Supported status command." -msgstr "[rpm][centos] Supported status command." - -msgid "Removed needless ``:`` from log message." -msgstr "Removed needless ``:`` from log message." - -msgid "Removed deprecated grn_query. [#1247]" -msgstr "Removed deprecated grn_query. [#1247]" - -msgid "Reduced needless grn_ctx_at() calls on creating table." -msgstr "Reduced needless grn_ctx_at() calls on creating table." - -msgid "[pat] Supported cache." -msgstr "[pat] Supported cache." - -msgid "[tokenizer] Improved tokenizer API." -msgstr "[tokenizer] Improved tokenizer API." - -msgid "Accepted ``@`` as a valid name character." -msgstr "Accepted ``@`` as a valid name character." - -msgid "" -"[tokenizer] Added a tokenizer based on `KyTea <http://www.phontron.com/kytea/" -">`_." -msgstr "" -"[tokenizer] Added a tokenizer based on `KyTea <http://www.phontron.com/kytea/" -">`_." - -msgid "Supported :doc:`offline index construction </reference/indexing>`." -msgstr "Supported :doc:`offline index construction </reference/indexing>`." - -msgid "" -"[tokenizer] Supported MeCab 0.993. [groonga-dev,00703] [Reported by Masaharu " -"YOSHIOKA]" -msgstr "" -"[tokenizer] Supported MeCab 0.993. [groonga-dev,00703] [Reported by Masaharu " -"YOSHIOKA]" - -msgid "[windows] Supported MessagePack." -msgstr "[windows] Supported MessagePack." - -msgid "[pat] Fixed a bug that the last node can't be found. [#1258]" -msgstr "[pat] Fixed a bug that the last node can't be found. [#1258]" - -msgid "[doc] Fixed links in Japanese page. [Reported by @naoina]" -msgstr "[doc] Fixed links in Japanese page. [Reported by @naoina]" - -msgid "[doc] Fixed wrong the default value. [Reported by @naoina]" -msgstr "[doc] Fixed wrong the default value. [Reported by @naoina]" - -msgid "Fixed a typo. [Reported by Kazuhiko]" -msgstr "Fixed a typo. [Reported by Kazuhiko]" - -msgid "" -"[http] Fixed a bug that ``load`` command error isn't cleared. [Reported by " -"@wareohji]" -msgstr "" -"[http] Fixed a bug that ``load`` command error isn't cleared. [Reported by " -"@wareohji]" - -msgid "Suzuki" -msgstr "Suzuki" - -msgid "@naoina" -msgstr "@naoina" - -msgid "Masaharu YOSHIOKA" -msgstr "Masaharu YOSHIOKA" - -msgid "@wareohji" -msgstr "@wareohji" - -msgid "Release 3.1.2 - 2014/01/29" -msgstr "Release 3.1.2 - 2014/01/29" - -msgid "" -"[doc] Updated to caplitalized \"Groonga\" terms in documentation. [Patch by " -"cosmo0920] [GitHub#136, #137, #138, #139, #140, #141, #142, #143, #144, " -"#145, #146, #147, #148, #149, #150, #151]" -msgstr "" -"[doc] Updated to caplitalized \"Groonga\" terms in documentation. [Patch by " -"cosmo0920] [GitHub#136, #137, #138, #139, #140, #141, #142, #143, #144, " -"#145, #146, #147, #148, #149, #150, #151]" - -msgid "" -"Supported to customize the value of lock timeout. See :doc:`/reference/api/" -"global_configurations` about details. [groonga-dev,02017] [Suggested by yoku]" -msgstr "" -"Supported to customize the value of lock timeout. See :doc:`/reference/api/" -"global_configurations` about details. [groonga-dev,02017] [Suggested by yoku]" - -msgid "[doc] Added description about the value of lock timeout." -msgstr "[doc] Added description about the value of lock timeout." - -msgid "" -"Enabled ``GRN_JA_SKIP_SAME_VALUE_PUT`` by default. In the previous releases, " -"the value of this configuration is 'no'. This change affects reducing the " -"size of Groonga database." -msgstr "" -"Enabled ``GRN_JA_SKIP_SAME_VALUE_PUT`` by default. In the previous releases, " -"the value of this configuration is 'no'. This change affects reducing the " -"size of Groonga database." - -msgid "" -"Supported multiple indexes including a nested index and multiple keywords " -"query. This change improves missing search results isssue when narrowing " -"down by multiple keywords query." -msgstr "" -"Supported multiple indexes including a nested index and multiple keywords " -"query. This change improves missing search results isssue when narrowing " -"down by multiple keywords query." - -msgid "Added API to customize normalizer for snippet." -msgstr "Added API to customize normalizer for snippet." - -msgid "" -"Fixed not to use index for empty query. This change enables you to search " -"even though empty query. Note that this means that there is performance " -"penalty if many empty records exist. [groonga-dev,02052] [Reported by Naoya " -"Murakami]" -msgstr "" -"Fixed not to use index for empty query. This change enables you to search " -"even though empty query. Note that this means that there is performance " -"penalty if many empty records exist. [groonga-dev,02052] [Reported by Naoya " -"Murakami]" - -msgid "" -"Fixed the behaviour about return value of \"X || Y\" and \"X && Y\" for " -"adjusting to ECMAScript. In \"X || Y\" case, if either X or Y satisfy the " -"condition, it returns X itself or Y itself instead of 1 or 0." -msgstr "" -"Fixed the behaviour about return value of \"X || Y\" and \"X && Y\" for " -"adjusting to ECMAScript. In \"X || Y\" case, if either X or Y satisfy the " -"condition, it returns X itself or Y itself instead of 1 or 0." - -msgid "" -"In \"X && Y\" case, if X and Y satisfy the condition, it returns X itself " -"instead of 1. if X doesn't satisfy the condition, it returns false instead " -"of 0." -msgstr "" -"In \"X && Y\" case, if X and Y satisfy the condition, it returns X itself " -"instead of 1. if X doesn't satisfy the condition, it returns false instead " -"of 0." - -msgid "" -"Fixed to return null when no snippet is found. This change enables you to " -"set the default value of :doc:`/reference/functions/snippet_html`. In such a " -"purpose, use \"snippet_html(XXX) || 'default value'\"." -msgstr "" -"Fixed to return null when no snippet is found. This change enables you to " -"set the default value of :doc:`/reference/functions/snippet_html`. In such a " -"purpose, use \"snippet_html(XXX) || 'default value'\"." - -msgid "cosmo0920" -msgstr "cosmo0920" - -msgid "yoku" -msgstr "yoku" - -msgid "Naoya Murakami" -msgstr "Naoya Murakami" - -msgid "Release 3.1.1 - 2013/12/29" -msgstr "Release 3.1.1 - 2013/12/29" - -msgid "" -"[deb] Refined Groonga packages for Debian policy. [groonga-dev,01930] " -"[Suggested by Hideki Yamane]" -msgstr "" -"[deb] Refined Groonga packages for Debian policy. [groonga-dev,01930] " -"[Suggested by Hideki Yamane]" - -msgid "[deb] Dropped Debian 6.0 (squeeze) support." -msgstr "[deb] Dropped Debian 6.0 (squeeze) support." - -msgid "[deb] Dropped Ubuntu 10.04 (lucid) support." -msgstr "[deb] Dropped Ubuntu 10.04 (lucid) support." - -msgid "" -"Supported :doc:`/reference/functions/geo_in_rectangle` in the whole world." -msgstr "" -"Supported :doc:`/reference/functions/geo_in_rectangle` in the whole world." - -msgid "" -"Supported error report when failed to casting invalid value of geo point " -"type." -msgstr "" -"Supported error report when failed to casting invalid value of geo point " -"type." - -msgid "" -"Exported some macros which is used for accessing pseudo column names. " -"[groonga-dev,1999] [Suggested by whombx]" -msgstr "" -"Exported some macros which is used for accessing pseudo column names. " -"[groonga-dev,1999] [Suggested by whombx]" - -msgid "[doc] Refined drilldown documentation. [Reported by @Yahppo]" -msgstr "[doc] Refined drilldown documentation. [Reported by @Yahppo]" - -msgid "" -"Supported :doc:`/reference/functions/between` function which is used for " -"filtering the column value in specific range." -msgstr "" -"Supported :doc:`/reference/functions/between` function which is used for " -"filtering the column value in specific range." - -msgid "[doc] Updated Travis CI environment information. [Patch by cosmo0920]" -msgstr "[doc] Updated Travis CI environment information. [Patch by cosmo0920]" - -msgid "[rpm][fedora] Dropped Fedora 19." -msgstr "[rpm][fedora] Dropped Fedora 19." - -msgid "[rpm][fedora] Supported Fedora 20." -msgstr "[rpm][fedora] Supported Fedora 20." - -msgid "" -"[doc] Updated \"Groonga\" notation. [Patch by cosmo0920] [GitHub#122, #123, " -"#124, #125, #125, #126, #127, #128, #129, #130, #131, #131, #132, #133, #134]" -msgstr "" -"[doc] Updated \"Groonga\" notation. [Patch by cosmo0920] [GitHub#122, #123, " -"#124, #125, #125, #126, #127, #128, #129, #130, #131, #131, #132, #133, #134]" - -msgid "[munin] Fixed the wrong port number which is specified for GQTP." -msgstr "[munin] Fixed the wrong port number which is specified for GQTP." - -msgid "" -"[geo_in_circle] Fixed a bug that if you specify \"LONGITUDExLATITUDE\" as " -"the 3rd argument of :doc:`/reference/functions/geo_in_circle`, Groonga " -"crashes." -msgstr "" -"[geo_in_circle] Fixed a bug that if you specify \"LONGITUDExLATITUDE\" as " -"the 3rd argument of :doc:`/reference/functions/geo_in_circle`, Groonga " -"crashes." - -msgid "Hideki Yamane" -msgstr "Hideki Yamane" - -msgid "whombx" -msgstr "whombx" - -msgid "@Yappo" -msgstr "@Yappo" - -msgid "Release 3.1.0 - 2013/11/29" -msgstr "Release 3.1.0 - 2013/11/29" - -msgid "" -"[experimental] Supported an option to skip updating for the same value. It " -"is enabled by setting GRN_JA_SKIP_SAME_VALUE_PUT=yes as environment variable." -msgstr "" -"[experimental] Supported an option to skip updating for the same value. It " -"is enabled by setting GRN_JA_SKIP_SAME_VALUE_PUT=yes as environment variable." - -msgid "" -"Improved to show tokenizer and original text in empty token warning message. " -"It shows actual token, so it helps you to investigate token related issue." -msgstr "" -"Improved to show tokenizer and original text in empty token warning message. " -"It shows actual token, so it helps you to investigate token related issue." - -msgid "Dropped broken AIO support. [#2054] [Reported by sho MINAGAWA]" -msgstr "Dropped broken AIO support. [#2054] [Reported by sho MINAGAWA]" - -msgid "" -"[windows] Supported build with Visual Studio Express 2008. [#1964 the 21th " -"comment] It is aimed to promote bundling Mroonga with MariaDB in the future." -msgstr "" -"[windows] Supported build with Visual Studio Express 2008. [#1964 the 21th " -"comment] It is aimed to promote bundling Mroonga with MariaDB in the future." - -msgid "" -"Fixed a bug that type of \"_value\" column is treated as Int32. It causes " -"the case that the value of \"_value\" column is casted unexpectedly. " -"[Reported by Genki Takiuchi]" -msgstr "" -"Fixed a bug that type of \"_value\" column is treated as Int32. It causes " -"the case that the value of \"_value\" column is casted unexpectedly. " -"[Reported by Genki Takiuchi]" - -msgid "" -"Fixed to require GLib 2.14.0 or later for benchmark program. The benchmark " -"program is changed to use GRegex which requires GLib 2.14.0 or later. It " -"affects users who compile Groonga with '--enable-benchmark' configuration. " -"[groonga-dev,01890] [Reported by WING]" -msgstr "" -"Fixed to require GLib 2.14.0 or later for benchmark program. The benchmark " -"program is changed to use GRegex which requires GLib 2.14.0 or later. It " -"affects users who compile Groonga with '--enable-benchmark' configuration. " -"[groonga-dev,01890] [Reported by WING]" - -msgid "" -"Fixed a memory leak on updating an empty column vector with the same value." -msgstr "" -"Fixed a memory leak on updating an empty column vector with the same value." - -msgid "" -"Fixed a memory leak on updating index for column vector. It affects the case " -"if you store the value of column which has invalid UTF-8 byte sequence." -msgstr "" -"Fixed a memory leak on updating index for column vector. It affects the case " -"if you store the value of column which has invalid UTF-8 byte sequence." - -msgid "" -"[plugin][windows] Fixed the issue that register command fails without 'lib/" -"groonga/plugins'. [Reported by @yito]" -msgstr "" -"[plugin][windows] Fixed the issue that register command fails without 'lib/" -"groonga/plugins'. [Reported by @yito]" - -msgid "sho MINAGAWA" -msgstr "sho MINAGAWA" - -msgid "Genki Takiuchi" -msgstr "Genki Takiuchi" - -msgid "WING" -msgstr "WING" - -msgid "Release 3.0.9 - 2013/10/29" -msgstr "Release 3.0.9 - 2013/10/29" - -msgid "" -"[doc][httpd] Added documentation about :ref:`groonga-database-auto-create` " -"directive." -msgstr "" -"[doc][httpd] Added documentation about :ref:`groonga-database-auto-create` " -"directive." - -msgid "[httpd] Added :ref:`groonga-cache-limit` directive." -msgstr "[httpd] Added :ref:`groonga-cache-limit` directive." - -msgid "" -"[doc] Added description why zlib/lzo compression are disabled by default. " -"[groonga-dev, 01845] [Suggested by Naoya Murakami]" -msgstr "" -"[doc] Added description why zlib/lzo compression are disabled by default. " -"[groonga-dev, 01845] [Suggested by Naoya Murakami]" - -msgid "" -"Remove a restriction related to RLIMIT_NOFILE on HTTP server. It enables " -"HTTP server process to handle over 4096 files." -msgstr "" -"Remove a restriction related to RLIMIT_NOFILE on HTTP server. It enables " -"HTTP server process to handle over 4096 files." - -msgid "" -"[experimental] Added some API to integrate mruby into groonga. [GitHub#109, " -"#110, #111, #112, #113, #114, #115, #116, #117, #118] [Patch by wanabe]" -msgstr "" -"[experimental] Added some API to integrate mruby into groonga. [GitHub#109, " -"#110, #111, #112, #113, #114, #115, #116, #117, #118] [Patch by wanabe]" - -msgid "[travis] Supported CMake build on Travis-CI." -msgstr "[travis] Supported CMake build on Travis-CI." - -msgid "[doc] Added documentation about :doc:`reference/tuning`." -msgstr "[doc] Added documentation about :doc:`reference/tuning`." - -msgid "[experimental] Added :doc:`ruby_load` command." -msgstr "[experimental] Added :doc:`ruby_load` command." - -msgid "" -"[httpd] Supported multiple buffered body of POST request. The load command " -"caused timeout in such a case. [GitHub #120] [Patch by Motoi Washida]" -msgstr "" -"[httpd] Supported multiple buffered body of POST request. The load command " -"caused timeout in such a case. [GitHub #120] [Patch by Motoi Washida]" - -msgid "" -"[gqtp] Supported error message. The body is changed to return raw text " -"insted of double quoted text. This is incompatible changes." -msgstr "" -"[gqtp] Supported error message. The body is changed to return raw text " -"insted of double quoted text. This is incompatible changes." - -msgid "[http] Supported \"400 Bad request\" for invalid argument error." -msgstr "[http] Supported \"400 Bad request\" for invalid argument error." - -msgid "[doc] Added examples for :doc:`/reference/suggest/completion`" -msgstr "[doc] Added examples for :doc:`/reference/suggest/completion`" - -msgid "Supported Ubuntu 13.10 (Saucy Salamander)." -msgstr "Supported Ubuntu 13.10 (Saucy Salamander)." - -msgid "" -"Fixed a bug that it cause SEGV by arithmetic overflow. This problem occurs " -"when the size of indexes exceeds the size of virtual memory. [groonga-" -"dev,01661] [Reported by Naoya Murakami]" -msgstr "" -"Fixed a bug that it cause SEGV by arithmetic overflow. This problem occurs " -"when the size of indexes exceeds the size of virtual memory. [groonga-" -"dev,01661] [Reported by Naoya Murakami]" - -msgid "" -"Fixed needless lock for creating table. This change fixes a performance " -"regression instroduced at Groonga 3.0.5." -msgstr "" -"Fixed needless lock for creating table. This change fixes a performance " -"regression instroduced at Groonga 3.0.5." - -msgid "" -"Fixed a bug that database which has reference column can't be removed. It " -"affects the case that indexed tables/columns and referenced tables are " -"removed at first, then remove operation to index columns and reference " -"columns fails. [Reported by Eito Katagiri] [GitHub Rroonga #13]" -msgstr "" -"Fixed a bug that database which has reference column can't be removed. It " -"affects the case that indexed tables/columns and referenced tables are " -"removed at first, then remove operation to index columns and reference " -"columns fails. [Reported by Eito Katagiri] [GitHub Rroonga #13]" - -msgid "" -"Fixed a bug that removing database which uses DAT key may remain garbage." -msgstr "" -"Fixed a bug that removing database which uses DAT key may remain garbage." - -msgid "" -"[http] Fixed a small memory leak which is caused by shared HTTP header " -"buffer in the same worker thread." -msgstr "" -"[http] Fixed a small memory leak which is caused by shared HTTP header " -"buffer in the same worker thread." - -msgid "" -"[httpd] Fixed a bug that :ref:`groonga-database-auto-create` parameter isn't " -"inherited. It means that these parameters are just ignored in non location " -"blocks." -msgstr "" -"[httpd] Fixed a bug that :ref:`groonga-database-auto-create` parameter isn't " -"inherited. It means that these parameters are just ignored in non location " -"blocks." - -msgid "Fixed a bug that status command may returns invalid cache hit rate." -msgstr "Fixed a bug that status command may returns invalid cache hit rate." - -msgid "" -"Fix a bug that casting to Time may causes overflow issue. It affects the " -"case that assignment of the Time value which indicate over 32bit value." -msgstr "" -"Fix a bug that casting to Time may causes overflow issue. It affects the " -"case that assignment of the Time value which indicate over 32bit value." - -msgid "wanabe" -msgstr "wanabe" - -msgid "Motoi Washida" -msgstr "Motoi Washida" - -msgid "Eito Katagiri" -msgstr "Eito Katagiri" - -msgid "Release 3.0.8 - 2013/09/29" -msgstr "Release 3.0.8 - 2013/09/29" - -msgid "" -"[admin] Improved error handling of select functionality. This change shows " -"error message and hides loading dialog. [Patch by orangain]" -msgstr "" -"[admin] Improved error handling of select functionality. This change shows " -"error message and hides loading dialog. [Patch by orangain]" - -msgid "" -"[admin] Improved to submit search form with the enter key. [Patch by " -"orangain]" -msgstr "" -"[admin] Improved to submit search form with the enter key. [Patch by " -"orangain]" - -msgid "" -"[admin] Improved to show placeholder in search form. This change shows usage " -"examples. [Patch by orangain]" -msgstr "" -"[admin] Improved to show placeholder in search form. This change shows usage " -"examples. [Patch by orangain]" - -msgid "[httpd] Supported :ref:`groonga-query-log-path` directive" -msgstr "[httpd] Supported :ref:`groonga-query-log-path` directive" - -msgid "" -"[doc] Updated :doc:`/reference/commands/select` documentation about the " -"number of hits in select response." -msgstr "" -"[doc] Updated :doc:`/reference/commands/select` documentation about the " -"number of hits in select response." - -msgid "" -"Improved to ignore an empty token which is generated by continuous spaces " -"from tokenizer. [groonga-dev,01729] [Suggested by Naoya Murakami]" -msgstr "" -"Improved to ignore an empty token which is generated by continuous spaces " -"from tokenizer. [groonga-dev,01729] [Suggested by Naoya Murakami]" - -msgid "" -"[token delimit] Improved to treat continuous spaces as a space. The " -"tokenizer regards 2 or more spaces are valid input." -msgstr "" -"[token delimit] Improved to treat continuous spaces as a space. The " -"tokenizer regards 2 or more spaces are valid input." - -msgid "" -"[doc] Added note about indexes for each column vs indexes for multiple " -"column." -msgstr "" -"[doc] Added note about indexes for each column vs indexes for multiple " -"column." - -msgid "" -"[doc] Added language annotation to source label. [groonga-dev,01751] " -"[Suggested by Kazuhiro Isobe]" -msgstr "" -"[doc] Added language annotation to source label. [groonga-dev,01751] " -"[Suggested by Kazuhiro Isobe]" - -msgid "" -"Supported :ref:`cascade-delete` to referenced records. In previous version, " -"You got an error for the operation." -msgstr "" -"Supported :ref:`cascade-delete` to referenced records. In previous version, " -"You got an error for the operation." - -msgid "" -"[doc] Updated documentation location in README. [groonga-dev,01800] " -"[Reported by Kazuhiro Isobe]" -msgstr "" -"[doc] Updated documentation location in README. [groonga-dev,01800] " -"[Reported by Kazuhiro Isobe]" - -msgid "[experimental] Added :doc:`/reference/commands/ruby_eval` command." -msgstr "[experimental] Added :doc:`/reference/commands/ruby_eval` command." - -msgid "" -"[doc] Added note about GQTP and HTTP for server use. [groonga-dev,01810] " -"[Reported by Kazuhiro Isobe]" -msgstr "" -"[doc] Added note about GQTP and HTTP for server use. [groonga-dev,01810] " -"[Reported by Kazuhiro Isobe]" - -msgid "" -"[admin] Fixed a bug that add value button of COLUMN_VECTOR does not work." -msgstr "" -"[admin] Fixed a bug that add value button of COLUMN_VECTOR does not work." - -msgid "orangain" -msgstr "orangain" - -msgid "Kazuhiro Isobe" -msgstr "Kazuhiro Isobe" - -msgid "Release 3.0.7 - 2013/08/29" -msgstr "Release 3.0.7 - 2013/08/29" - -msgid "" -"[doc] Added API documentation. [groonga-dev,01593] [GitHub#79,#80,#81,#82," -"#83,#84,#85,#86,#87,#88,#89,#90,#91,#92,#93,#95,#96,#97,#98,#99,#100] [Patch " -"by whombx]" -msgstr "" -"[doc] Added API documentation. [groonga-dev,01593] [GitHub#79,#80,#81,#82," -"#83,#84,#85,#86,#87,#88,#89,#90,#91,#92,#93,#95,#96,#97,#98,#99,#100] [Patch " -"by whombx]" - -msgid "" -"[table_remove] Improved not to remove patricia trie table or hash table " -"which is still referenced. This change avoids that referenced table is " -"removed accidentally." -msgstr "" -"[table_remove] Improved not to remove patricia trie table or hash table " -"which is still referenced. This change avoids that referenced table is " -"removed accidentally." - -msgid "" -"Improved to just ignore too long token (4096 bytes or more). This change " -"affects when it is registered. In the previous version, it is treated as an " -"error instead of a warning. [groonga-dev,01571] [Suggested by Naoya Murakami]" -msgstr "" -"Improved to just ignore too long token (4096 bytes or more). This change " -"affects when it is registered. In the previous version, it is treated as an " -"error instead of a warning. [groonga-dev,01571] [Suggested by Naoya Murakami]" - -msgid "" -"Improved to show actual discarded posting term in log message. [groonga-" -"dev,01621] [Reported by Naoya Murakami]" -msgstr "" -"Improved to show actual discarded posting term in log message. [groonga-" -"dev,01621] [Reported by Naoya Murakami]" - -msgid "" -"[httpd] Supported loading data using POST method. [GitHub#101] [Patch by " -"Motoi Washida]" -msgstr "" -"[httpd] Supported loading data using POST method. [GitHub#101] [Patch by " -"Motoi Washida]" - -msgid "[httpd] Supported groonga log as ``groonga_log_path`` directive." -msgstr "[httpd] Supported groonga log as ``groonga_log_path`` directive." - -msgid "[httpd] Supported groonga log level as ``groonga_log_level`` directive." -msgstr "" -"[httpd] Supported groonga log level as ``groonga_log_level`` directive." - -msgid "" -"[httpd] Supported customizing cache limit as ``groonga_cache_limit`` " -"directive." -msgstr "" -"[httpd] Supported customizing cache limit as ``groonga_cache_limit`` " -"directive." - -msgid "" -"Fixed a bug that error in expression may cause stack overflow. This change " -"avoids that groonga crashes suddenly as a result of error accumlation." -msgstr "" -"Fixed a bug that error in expression may cause stack overflow. This change " -"avoids that groonga crashes suddenly as a result of error accumlation." - -msgid "" -"Fixed a crash bug that offline index construction for vector column which " -"has orphan reference causes." -msgstr "" -"Fixed a crash bug that offline index construction for vector column which " -"has orphan reference causes." - -msgid "" -"Fixed a bug that groonga doesn't exit on error while daemon mode starts. For " -"example, ``groonga -d /tmp/non-existence.db`` reproduce this bug." -msgstr "" -"Fixed a bug that groonga doesn't exit on error while daemon mode starts. For " -"example, ``groonga -d /tmp/non-existence.db`` reproduce this bug." - -msgid "" -"[dump] Fixed a bug that wrong table type is dumped. This bug occurs when " -"table type is TABLE_PAT_KEY and key is reference type." -msgstr "" -"[dump] Fixed a bug that wrong table type is dumped. This bug occurs when " -"table type is TABLE_PAT_KEY and key is reference type." - -msgid "" -"Fixed a bug that the default ``--cache-limit`` value is 0. The default value " -"is changed to '100'." -msgstr "" -"Fixed a bug that the default ``--cache-limit`` value is 0. The default value " -"is changed to '100'." - -msgid "" -"Fixed a memory leak when :doc:`/reference/functions/sub_filter` is used." -msgstr "" -"Fixed a memory leak when :doc:`/reference/functions/sub_filter` is used." - -msgid "[doc] Fixed description of defrag command. [Reported by @naoina]" -msgstr "[doc] Fixed description of defrag command. [Reported by @naoina]" - -msgid "" -"[doc] Fixed description about the way to contribute. [GitHub#77] [Patch by " -"Masafumi Yokoyama]" -msgstr "" -"[doc] Fixed description about the way to contribute. [GitHub#77] [Patch by " -"Masafumi Yokoyama]" - -msgid "" -"[plugin] Fixed a crash bug on multiple DB open case. This bug affects the " -"case that multiple plugin is used and the same database is opened from " -"multiple process. [groonga-dev,01596] [Reported by Naoya Murakami]" -msgstr "" -"[plugin] Fixed a crash bug on multiple DB open case. This bug affects the " -"case that multiple plugin is used and the same database is opened from " -"multiple process. [groonga-dev,01596] [Reported by Naoya Murakami]" - -msgid "" -"Fixed a bug that nested match operation after ``AND`` operator doesn't work. " -"The ``select ... --filter '... && nested.column @ \"keyword\"'`` query " -"reproduces this bug. [groonga-dev,01599] [Reported by Motoi Washida]" -msgstr "" -"Fixed a bug that nested match operation after ``AND`` operator doesn't work. " -"The ``select ... --filter '... && nested.column @ \"keyword\"'`` query " -"reproduces this bug. [groonga-dev,01599] [Reported by Motoi Washida]" - -msgid "" -"[doc] Fixed a typo about documentation of special characters. [Reported by " -"Genki Takiuchi]" -msgstr "" -"[doc] Fixed a typo about documentation of special characters. [Reported by " -"Genki Takiuchi]" - -msgid "" -"Fixed a typo in error message when invalid character is given. [Reported by " -"YOSHIDA Mitsuo]" -msgstr "" -"Fixed a typo in error message when invalid character is given. [Reported by " -"YOSHIDA Mitsuo]" - -msgid "Masafumi Yokoyama" -msgstr "Masafumi Yokoyama" - -msgid "YOSHIDA Mitsuo" -msgstr "YOSHIDA Mitsuo" - -msgid "Release 3.0.6 - 2013/07/29" -msgstr "Release 3.0.6 - 2013/07/29" - -msgid "" -"[doc] Added documentation about parameter of :doc:`/reference/functions/" -"sub_filter` function." -msgstr "" -"[doc] Added documentation about parameter of :doc:`/reference/functions/" -"sub_filter` function." - -msgid "[suggest] Supported 0MQ 3.x. [GitHub#63] [Reported by Naoya Inada]" -msgstr "[suggest] Supported 0MQ 3.x. [GitHub#63] [Reported by Naoya Inada]" - -msgid "" -"Added availability check for NetBSD about ``pthread_{mutex,cond}" -"attr_setpshared()`` [Reported by OBATA Akio]" -msgstr "" -"Added availability check for NetBSD about ``pthread_{mutex,cond}" -"attr_setpshared()`` [Reported by OBATA Akio]" - -msgid "" -"Supported backslash escape in query syntax. [groonga-dev,01520] [Reported by " -"Kouhei Tanabe]" -msgstr "" -"Supported backslash escape in query syntax. [groonga-dev,01520] [Reported by " -"Kouhei Tanabe]" - -msgid "[rpm][fedora] Supported Fedora 19." -msgstr "[rpm][fedora] Supported Fedora 19." - -msgid "[rpm][fedora] Dropped Fedora 18 support." -msgstr "[rpm][fedora] Dropped Fedora 18 support." - -msgid "[httpd] Updated bundled nginx version to 1.4.2." -msgstr "[httpd] Updated bundled nginx version to 1.4.2." - -msgid "" -"Fixed a crash bug when specific internal function (``grn_obj_path()``) is " -"called for built-in proc function such as ``select``. [Reported by Genki " -"Takiuchi]" -msgstr "" -"Fixed a crash bug when specific internal function (``grn_obj_path()``) is " -"called for built-in proc function such as ``select``. [Reported by Genki " -"Takiuchi]" - -msgid "Naoya Inada" -msgstr "Naoya Inada" - -msgid "Kouhei Tanabe" -msgstr "Kouhei Tanabe" - -msgid "Release 3.0.5 - 2013/06/29" -msgstr "Release 3.0.5 - 2013/06/29" - -msgid "" -"[doc] Added summary about ``match_columns`` and ``query_string`` parameters " -"in ``query()``." -msgstr "" -"[doc] Added summary about ``match_columns`` and ``query_string`` parameters " -"in ``query()``." - -msgid "Added subrecord information to table inspection." -msgstr "Added subrecord information to table inspection." - -msgid "" -"Supported single quoted string literal in ``output_columns`` expression. " -"This means that \"XXX, '...'\" expression is supported." -msgstr "" -"Supported single quoted string literal in ``output_columns`` expression. " -"This means that \"XXX, '...'\" expression is supported." - -msgid "" -"[doc] Added notification about root privileges and well known port when " -"starting groonga server. [Reported by Kosuke Asami]" -msgstr "" -"[doc] Added notification about root privileges and well known port when " -"starting groonga server. [Reported by Kosuke Asami]" - -msgid "[experimental] Added :doc:`/reference/functions/html_untag` function." -msgstr "[experimental] Added :doc:`/reference/functions/html_untag` function." - -msgid "" -"Fixed a crash bug of mroonga which is caused by missing lock for table " -"creation. [Reported by Y.Kentaro]" -msgstr "" -"Fixed a crash bug of mroonga which is caused by missing lock for table " -"creation. [Reported by Y.Kentaro]" - -msgid "Fixed a lot of compilation warnings by clang and gcc." -msgstr "Fixed a lot of compilation warnings by clang and gcc." - -msgid "" -"Fixed a bug that ``sub_filter(...)`` is ignored if you use \"XXX && " -"sub_filter(...)\" expression." -msgstr "" -"Fixed a bug that ``sub_filter(...)`` is ignored if you use \"XXX && " -"sub_filter(...)\" expression." - -msgid "" -"Fixed a bug that wrong tag name is used in XML output. This bug affects the " -"case if you use \"REFERENCE_VECTOR_COLUMN._key\" expression for " -"``output_columns``. Reference column isn't contained in XML ouput." -msgstr "" -"Fixed a bug that wrong tag name is used in XML output. This bug affects the " -"case if you use \"REFERENCE_VECTOR_COLUMN._key\" expression for " -"``output_columns``. Reference column isn't contained in XML ouput." - -msgid "[doc] Fixed wrong arguments in ``sub_filter()`` documentation." -msgstr "[doc] Fixed wrong arguments in ``sub_filter()`` documentation." - -msgid "" -"[deb] Fixed a bug that status action returns wrong exit code when services " -"are stopped. [GitHub#62] [Patch by @orangain]" -msgstr "" -"[deb] Fixed a bug that status action returns wrong exit code when services " -"are stopped. [GitHub#62] [Patch by @orangain]" - -msgid "" -"Fixed a bug that the value of arithmetic operation is broken. This bug " -"affects the case if you assign calculated value to ``_score`` pseudo column " -"for example." -msgstr "" -"Fixed a bug that the value of arithmetic operation is broken. This bug " -"affects the case if you assign calculated value to ``_score`` pseudo column " -"for example." - -msgid "Y.Kentaro" -msgstr "Y.Kentaro" - -msgid "Kosuke Asami" -msgstr "Kosuke Asami" - -msgid "@orangain" -msgstr "@orangain" - -msgid "Release 3.0.4 - 2013/05/29" -msgstr "Release 3.0.4 - 2013/05/29" - -msgid "" -"[tokenizer] Improved to show log message when normalized string is not given." -msgstr "" -"[tokenizer] Improved to show log message when normalized string is not given." - -msgid "" -"Supported ``_key`` as an argument of ``geo_in_circle``. [Reported by @ceekz]" -msgstr "" -"Supported ``_key`` as an argument of ``geo_in_circle``. [Reported by @ceekz]" - -msgid "Supported to cast vector elements when groonga is used as a library." -msgstr "Supported to cast vector elements when groonga is used as a library." - -msgid "Dropped Ubuntu 11.10 (Oneiric Ocelot) support." -msgstr "Dropped Ubuntu 11.10 (Oneiric Ocelot) support." - -msgid "Supported multiple index section in ``match_columns``." -msgstr "Supported multiple index section in ``match_columns``." - -msgid "Supported ``tokenize`` command." -msgstr "Supported ``tokenize`` command." - -msgid "Supported to show system error message when ``mmap()`` is failed." -msgstr "Supported to show system error message when ``mmap()`` is failed." - -msgid "[doc][windows] Simplified build procedures by \"cmake --build\"." -msgstr "[doc][windows] Simplified build procedures by \"cmake --build\"." - -msgid "" -"Improved to restrict max execution time to prevent hanging service script. " -"[GitHub#61] [Reported by firewood]" -msgstr "" -"Improved to restrict max execution time to prevent hanging service script. " -"[GitHub#61] [Reported by firewood]" - -msgid "" -"Supported to evaluate vector as boolean. By this change, empty vector is " -"evaluated as true." -msgstr "" -"Supported to evaluate vector as boolean. By this change, empty vector is " -"evaluated as true." - -msgid "" -"Improved not to log too many needless log messages. Too many log messages " -"are truncated as \"(N same messages are truncated)\"." -msgstr "" -"Improved not to log too many needless log messages. Too many log messages " -"are truncated as \"(N same messages are truncated)\"." - -msgid "" -"[munin][groonga_n_records] Added ``exclude_tables`` option. It supports to " -"exclude specific tables from monitoring results." -msgstr "" -"[munin][groonga_n_records] Added ``exclude_tables`` option. It supports to " -"exclude specific tables from monitoring results." - -msgid "Supported Debian 8.0 (jessie)." -msgstr "Supported Debian 8.0 (jessie)." - -msgid "" -"Improved database portability by eliminating directory path of system " -"plugins." -msgstr "" -"Improved database portability by eliminating directory path of system " -"plugins." - -msgid "[tokenizer] Fixed a memory leak on error." -msgstr "[tokenizer] Fixed a memory leak on error." - -msgid "" -"Fixed a bug that empty string for similar search causes SEGV. [groonga-" -"dev,01346] [Reported by Nakai Kanako]" -msgstr "" -"Fixed a bug that empty string for similar search causes SEGV. [groonga-" -"dev,01346] [Reported by Nakai Kanako]" - -msgid "" -"Fixed a memory leak when \"VECTOR_COLUMN != xxx\", \"VECTOR_COLUMN && xxx\" " -"expressions are used." -msgstr "" -"Fixed a memory leak when \"VECTOR_COLUMN != xxx\", \"VECTOR_COLUMN && xxx\" " -"expressions are used." - -msgid "Fixed a bug that SIGSTOP and SIGCONT stops groonga server." -msgstr "Fixed a bug that SIGSTOP and SIGCONT stops groonga server." - -msgid "" -"Fixed a crash bug when normalizer returns NULL as normalized string. " -"[Reported by Y.Kentaro]" -msgstr "" -"Fixed a crash bug when normalizer returns NULL as normalized string. " -"[Reported by Y.Kentaro]" - -msgid "" -"Fixed a bug that daemonize process doesn't work on OS X. [groonga-dev,01440] " -"[Reported by Masahiro KONISHI]" -msgstr "" -"Fixed a bug that daemonize process doesn't work on OS X. [groonga-dev,01440] " -"[Reported by Masahiro KONISHI]" - -msgid "[deb] Fixed a bug that HTTP/GQTP process is excuted as root user." -msgstr "[deb] Fixed a bug that HTTP/GQTP process is excuted as root user." - -msgid "@ceekz" -msgstr "@ceekz" - -msgid "Nakai Kanako" -msgstr "Nakai Kanako" - -msgid "Masahiro KONISHI" -msgstr "Masahiro KONISHI" - -msgid "Release 3.0.3 - 2013/04/29" -msgstr "Release 3.0.3 - 2013/04/29" - -msgid "" -"[suggest] Supported to learn with the value of customized weight by using " -"``configuration.weight`` configuration." -msgstr "" -"[suggest] Supported to learn with the value of customized weight by using " -"``configuration.weight`` configuration." - -msgid "" -"Improved performance of geo-location search. For example, " -"``geo_in_rectangle`` is executed about 10% faster than ever." -msgstr "" -"Improved performance of geo-location search. For example, " -"``geo_in_rectangle`` is executed about 10% faster than ever." - -msgid "" -"[rpm][centos] Added ``additional_configure_options`` parameter for building " -"customized groonga without changing spec file." -msgstr "" -"[rpm][centos] Added ``additional_configure_options`` parameter for building " -"customized groonga without changing spec file." - -msgid "Supported KyTea 0.4.5." -msgstr "Supported KyTea 0.4.5." - -msgid "Supported vector index access by \"vector[N]\" syntax." -msgstr "Supported vector index access by \"vector[N]\" syntax." - -msgid "" -"Added ``--default-tokenizer`` option to :doc:`/reference/executables/groonga-" -"suggest-create-dataset` command." -msgstr "" -"Added ``--default-tokenizer`` option to :doc:`/reference/executables/groonga-" -"suggest-create-dataset` command." - -msgid "" -"Added ``--help`` option to :doc:`/reference/executables/groonga-suggest-" -"create-dataset` command." -msgstr "" -"Added ``--help`` option to :doc:`/reference/executables/groonga-suggest-" -"create-dataset` command." - -msgid "Supported Ubuntu 13.04 Raring Ringtail." -msgstr "Supported Ubuntu 13.04 Raring Ringtail." - -msgid "Release 3.0.2 - 2013/03/29" -msgstr "Release 3.0.2 - 2013/03/29" - -msgid "" -"Supported two or more indexes for a table key. This change affects to " -"eliminate potential crash case when loading a new key to two or more indexed " -"key." -msgstr "" -"Supported two or more indexes for a table key. This change affects to " -"eliminate potential crash case when loading a new key to two or more indexed " -"key." - -msgid "" -"Supported binary operations such as ``X + Y``, ``X - Y``, ``X * Y``, ``X / " -"Y``, ``X % Y``, ``X >> Y``, ``X << Y``, ``X | Y``, ``X ^ Y``, ``X & Y`` and " -"``X >>> Y`` for Int8, UInt8, Int16, UInt16 and UInt64." -msgstr "" -"Supported binary operations such as ``X + Y``, ``X - Y``, ``X * Y``, ``X / " -"Y``, ``X % Y``, ``X >> Y``, ``X << Y``, ``X | Y``, ``X ^ Y``, ``X & Y`` and " -"``X >>> Y`` for Int8, UInt8, Int16, UInt16 and UInt64." - -msgid "" -"Added English documentation for :doc:`/reference/commands/load` command." -msgstr "" - -msgid "" -"Supported binary assign operations such as ``X += Y``, ``X -= Y``, ``X *= " -"Y``, ``X /= Y``, ``X %= Y``, ``X <<= Y``, ``X >>= Y``, ``X >>>= Y``, ``X &= " -"Y``, ``X |= Y`` and ``X ^= Y`` for Int8, UInt8, Int16, UInt16 and UInt64." -msgstr "" -"Supported binary assign operations such as ``X += Y``, ``X -= Y``, ``X *= " -"Y``, ``X /= Y``, ``X %= Y``, ``X <<= Y``, ``X >>= Y``, ``X >>>= Y``, ``X &= " -"Y``, ``X |= Y`` and ``X ^= Y`` for Int8, UInt8, Int16, UInt16 and UInt64." - -msgid "" -"Supported unary operations such as ``-X`` for Int8, UInt8, Int16, UInt16 and " -"UInt64." -msgstr "" -"Supported unary operations such as ``-X`` for Int8, UInt8, Int16, UInt16 and " -"UInt64." - -msgid "" -"Supported complex string concatination in ``--output_columns``. For example, " -"you can use a query such as ``--output_columns '\"<\" + title + \">\"'``." -msgstr "" -"Supported complex string concatination in ``--output_columns``. For example, " -"you can use a query such as ``--output_columns '\"<\" + title + \">\"'``." - -msgid "Added the information of the repository of groonga to development page." -msgstr "" -"Added the information of the repository of groonga to development page." - -msgid "Added ``sub_filter()`` function." -msgstr "Added ``sub_filter()`` function." - -msgid "" -"Supported query expander in ``query()`` function. This change supports the " -"query such as ``query(\"MATCH_COLUMNS\", \"QUERY\", \"QueryExpanderTSV\")``." -msgstr "" -"Supported query expander in ``query()`` function. This change supports the " -"query such as ``query(\"MATCH_COLUMNS\", \"QUERY\", \"QueryExpanderTSV\")``." - -msgid "" -"Renamed ``--query_expansion`` to ``--query_expander``. ``--query_expansion`` " -"is regarded as deprecated." -msgstr "" -"Renamed ``--query_expansion`` to ``--query_expander``. ``--query_expansion`` " -"is regarded as deprecated." - -msgid "" -"Fixed a bug that ``snippet_html(XXX), XXX`` fails with \"stack error\". This " -"bug affects a query such as ``--output_columns 'snippet_html(title), " -"content'``. [Groonga-talk (no subject)] [Reported by Hendro Wibowo]" -msgstr "" -"Fixed a bug that ``snippet_html(XXX), XXX`` fails with \"stack error\". This " -"bug affects a query such as ``--output_columns 'snippet_html(title), " -"content'``. [Groonga-talk (no subject)] [Reported by Hendro Wibowo]" - -msgid "Fixed a typo about install documentation. [Reported by hino]" -msgstr "Fixed a typo about install documentation. [Reported by hino]" - -msgid "" -"Fixed a bug that Travis-CI setup script fails. [groonga-dev,01248] [Reported " -"by ongaeshi]" -msgstr "" -"Fixed a bug that Travis-CI setup script fails. [groonga-dev,01248] [Reported " -"by ongaeshi]" - -msgid "" -"Fixed a memory leak. This bug affects the case which satisfy following three " -"conditions. Column is a reference column, Column is a vector column and " -"Reference key size is 25 byte or lager." -msgstr "" -"Fixed a memory leak. This bug affects the case which satisfy following three " -"conditions. Column is a reference column, Column is a vector column and " -"Reference key size is 25 byte or lager." - -msgid "" -"Fixed a crash bug by ``--output_columns _score.GARBAGE``. This affects the " -"case if GARBAGE does not exist." -msgstr "" -"Fixed a crash bug by ``--output_columns _score.GARBAGE``. This affects the " -"case if GARBAGE does not exist." - -msgid "Hendro Wibowo" -msgstr "Hendro Wibowo" - -msgid "hino" -msgstr "hino" - -msgid "Release 3.0.1 - 2013/02/28" -msgstr "Release 3.0.1 - 2013/02/28" - -msgid "" -"Supported to set Bool to reference column when loading dataset by load " -"command." -msgstr "" -"Supported to set Bool to reference column when loading dataset by load " -"command." - -msgid "" -"Supported AND operation for nested index. In this change, the expression " -"\"COLUMN1.COLUMN2 >= 1 && COLUMN1.COLUMN2 <=3\" works. Note that the order " -"is important for this expression. \"1 <= COLUMN1.COLUMN2\" is not supported " -"yet. It is regarded as \"COLUMN1.COLUMN2 <= 1\"." -msgstr "" -"Supported AND operation for nested index. In this change, the expression " -"\"COLUMN1.COLUMN2 >= 1 && COLUMN1.COLUMN2 <=3\" works. Note that the order " -"is important for this expression. \"1 <= COLUMN1.COLUMN2\" is not supported " -"yet. It is regarded as \"COLUMN1.COLUMN2 <= 1\"." - -msgid "" -"Supported sorting not indexed entries. This change affects the case such as " -"``--sortby geo_distance(...)`` drops not indexed entries." -msgstr "" -"Supported sorting not indexed entries. This change affects the case such as " -"``--sortby geo_distance(...)`` drops not indexed entries." - -msgid "" -"Supported range search for reference column by index. This change enable you " -"to search range by index which is TABLE_PAT_KEY or TABLE_DAT_KEY based " -"nested index of _key." -msgstr "" -"Supported range search for reference column by index. This change enable you " -"to search range by index which is TABLE_PAT_KEY or TABLE_DAT_KEY based " -"nested index of _key." - -msgid "[rpm][centos] Supported MeCab 0.995." -msgstr "[rpm][centos] Supported MeCab 0.995." - -msgid "" -"[doc] Added missing documentation of commands such as ``column_rename`` or " -"``truncate``." -msgstr "" -"[doc] Added missing documentation of commands such as ``column_rename`` or " -"``truncate``." - -msgid "" -"Fixed a bug that ``grn_index_cursor_next()`` returns NULL unexpectedly. It " -"causes that invalid index entry is returned after deleting entries. This bug " -"affects mroonga in storage mode. [groonga-dev,01192] [Reported by b senboku]" -msgstr "" -"Fixed a bug that ``grn_index_cursor_next()`` returns NULL unexpectedly. It " -"causes that invalid index entry is returned after deleting entries. This bug " -"affects mroonga in storage mode. [groonga-dev,01192] [Reported by b senboku]" - -msgid "" -"Fixed a crash bug that ``geo_distance()`` sort by index. This bug occurs by " -"wrong the number of found records." -msgstr "" -"Fixed a crash bug that ``geo_distance()`` sort by index. This bug occurs by " -"wrong the number of found records." - -msgid "" -"[httpd] Enabled default owner/group of database setting as groonga/groonga." -msgstr "" -"[httpd] Enabled default owner/group of database setting as groonga/groonga." - -msgid "b senboku" -msgstr "b senboku" - -msgid "Release 3.0.0 - 2013/02/09" -msgstr "Release 3.0.0 - 2013/02/09" - -msgid "Bump version to 3.0.0!" -msgstr "Bump version to 3.0.0!" - -msgid "" -"[deb] Fixed to install missing not EUC-JP, but UTF-8 encoding dictionary " -"when ``groonga-tokenizer-mecab`` package is installed." -msgstr "" -"[deb] Fixed to install missing not EUC-JP, but UTF-8 encoding dictionary " -"when ``groonga-tokenizer-mecab`` package is installed." - -msgid "" -"Fixed a bug that int64 literal is truncated to uint32 value. If you use " -"string literal for int64, this bug does not affects." -msgstr "" -"Fixed a bug that int64 literal is truncated to uint32 value. If you use " -"string literal for int64, this bug does not affects." - -msgid "" -"[rpm][centos] Fixed a bug that stopping ``groonga-server-http`` service by " -"init script is failed. [GitHub#53] [Patch by IWAI, Masaharu]" -msgstr "" -"[rpm][centos] Fixed a bug that stopping ``groonga-server-http`` service by " -"init script is failed. [GitHub#53] [Patch by IWAI, Masaharu]" - -msgid "Release 4.1.1 - 2015-01-29" -msgstr "" - -msgid "" -"[windows] Improved to show error message instead of error code. It's easy to " -"understand." -msgstr "" - -msgid "" -"[experimental][windows] Supported small start file size for database file. " -"In previous versions, Groonga consumed larger initial file size on windows " -"in contrast to UNIX like environment. To enable this feature, use " -"``GRN_IO_VERSION=1`` environment variable. This feature isn't enabled by " -"default because it is in experimental stage." -msgstr "" - -msgid "" -"Supported ``SUM``, ``MIN``, ``MAX``, ``AVG`` feature for drilldown. This " -"feature is supported by extending newer drilldown syntax which supports " -"label. Specify ``SUM``, ``MIN``, ``MAX`` or ``AVG`` for :ref:`select-" -"drilldown-calc-types` and target column for :ref:`select-drilldown-calc-" -"target`. The return value is calculated based on drilldown result in group." -msgstr "" - -msgid "" -"[experimental] Added ``--with-jemalloc`` option to use ``jemalloc`` for " -"``malloc()/free()``. It'll improve performance on multi-threading usage. For " -"example, the performance of :doc:`/reference/executables/groonga` or " -"`Mroonga <http://mroonga.org/>`__ will be improved. Note that this feature " -"doesn't affect to :doc:`/reference/executables/groonga-httpd` because " -"groonga-httpd uses multi-process model instead of multi-threading." -msgstr "" - -msgid "" -"groonga-httpd: Supported long error message over 2048 bytes. By this change, " -"long error message (>2048) is not truncated." -msgstr "" - -msgid "groonga-httpd: Supported streaming dump functionality." -msgstr "" - -msgid "" -"Fixed mismatch between error code and error message when ``strerror()`` is " -"failed. There was a case that Groonga shows incorrect error code as syscall " -"error." -msgstr "" - -msgid "Fixed to show errno in error message when unknow error is occurred." -msgstr "" - -msgid "[windows] Fixed to return proper error code." -msgstr "" - -msgid "" -"Fixed a bug that there is only one section for multi-column index for :ref:" -"`select-match-columns`, it doesn't return correct search results. For " -"example, consider the case that there is multi-column index which is named " -"as ``memo_index`` for ``title`` column and ``content`` column. Thus, this " -"bug occurs when ``memo_index[0]`` which means index for ``title`` column is " -"specified for :ref:`select-match-columns`." -msgstr "" - -msgid "" -"mecab: Added workaround for ``mecab_strerror(NULL)`` on MeCab 0.993. Without " -"this workaround, Groonga aborts if there is no MeCab dictionary. [Reported " -"by Shuhei Tanuma]" -msgstr "" - -msgid "groonga-httpd: Fixed a bug that custom log file is ignored." -msgstr "" - -msgid "groonga-httpd: Fixed a bug that empty dump doesn't return." -msgstr "" - -msgid "Shuhei Tanuma" -msgstr "" - -msgid "Release 4.1.0 - 2015-01-09" -msgstr "" - -# c34a00700c694595aea05a4b44d109f1 -msgid "It's a bug fix release of 4.0.9." -msgstr "" - -# 7633824e61f9476f8a3bf306f805624e -msgid "" -"If you have already upgraded to 4.0.9, please upgrade to 4.1.0. And re-" -"create your all indexes. You can re-create your indexes by removing and re-" -"creating your indexes such as::" -msgstr "" - -msgid ":doc:`/reference/commands/column_remove`" -msgstr "" - -msgid ":doc:`/reference/commands/column_create`" -msgstr "" - -# cd8a50e5b79c40caa20c8531a0e53f31 -msgid "" -"If you didn't change your indexes by Groonga 4.0.9, you don't need to re-" -"create your indexes. \"change\" means \"add\", \"remove\" and \"update\". If " -"you use your indexes only for \"search\" by Groonga 4.0.9, you don't need to " -"re-create your indexes." -msgstr "" - -# eec36f7644d24a0e8bae40f427308c29 -msgid "" -"Fixed a bug that index may be broken. But the following bug fixed in Groonga " -"4.0.9 is re-appeared." -msgstr "" - -msgid "" -"Fixed a crash bug that may be occurred by deleting or updating many indexed " -"values at once. [groonga-dev,02942] [Reported by kashihara]" -msgstr "" - -msgid "Release 4.0.9 - 2014-12-29" -msgstr "" - -msgid "" -"Use 4.1.0 instead of 4.0.9. 4.0.9 has a serious bug that may break index." -msgstr "" - -# 1a9a4ae1ae5847a8be98c96d9b7df541 -msgid "[:doc:`/reference/executables/groonga-httpd`] Marked as stable." -msgstr "" - -msgid "" -"[doc] Described about ``groonga-token-filter-stem`` package. [GitHub#259] " -"[Patch by Masafumi Yokoyama]" -msgstr "" - -# 4ad510500ece4416907978ad3ba0520b -msgid "" -"[build] Supported ``make install`` without ``make``. [Reported by akira " -"yamada]" -msgstr "" - -msgid "" -"[experimental] Added :doc:`/reference/commands/request_cancel` command that " -"cancels running request." -msgstr "" - -msgid "[experimental] Added :c:func:`grn_db_recover()`." -msgstr "" - -# 5301cf5d3ccc432c87011a9d6d1763fc -msgid "" -"Supported indexing vector of fixed size data such as vector of ``UInt64``. " -"[groonga-dev,03014] [Reported by funa 1g]" -msgstr "" - -msgid "[experimental] Added :doc:`/reference/executables/grndb`." -msgstr "" - -msgid "[deb] Supported armhf architecture." -msgstr "" - -msgid "[:doc:`/reference/executables/groonga-server-http`] Supported HEAD." -msgstr "" - -msgid "" -"[doc] Updated :doc:`/contribution/documentation/introduction`. [GitHub#270] " -"[Patch by Yuya TAMANO]" -msgstr "" - -# e9fdb289010b407f9c6338e279d390c4 -msgid "" -"[doc] Updated :doc:`/install/others`. [GitHub#271] [Patch by Hiroshi Hatake]" -msgstr "" - -# a41aa3b6de59458aa8974ae82babd023 -msgid "" -"[:ref:`token-filter-stem`] Supported token that consists with only upper-" -"case alphabets, digits, ``-`` and ``'``. It means that :ref:`token-filter-" -"stem` can work with MySQL compatible normalizers." -msgstr "" - -msgid "[:doc:`/reference/commands/truncate`] Supported column." -msgstr "" - -# 4cb60cf9178c465189d0a0b237173e50 -msgid "" -"[:doc:`/reference/commands/truncate`] Changed parameter name to " -"``target_name`` from ``table``. ``table`` parameter can be used for backward " -"compatibility but it shouldn't used for newly written code." -msgstr "" - -# c66ca536d95842309c95107739e79420 -msgid "Exported :c:func:`grn_column_truncate()`." -msgstr "" - -msgid "Added :doc:`/reference/commands/lock_clear`." -msgstr "" - -msgid "Marked :doc:`/reference/commands/clearlock` deprecated." -msgstr "" - -# 34cb9e0d20d9463ebc3abdf6b1ef6f90 -msgid "" -"[backward incompatible] Stopped to set world writable permission for newly " -"created files on ``umask(0)`` environment such as daemoned :doc:`/reference/" -"executables/groonga-httpd`. It's a backward incompatible change but done " -"because the previous behavior has a security risk." -msgstr "" - -# 3749e6a86673495e82a646688b7e80cf -msgid "" -"Fixed build error on BSD based system. [GitHub#253] [Reported by Hiroshi " -"Hatake]" -msgstr "" - -# 3fdc7c8d2b214cf49607d1c163009f61 -msgid "Fixed build error on OS X. [GitHub#253] [Reported by Hiroshi Hatake]" -msgstr "" - -# 51a695ee23bd4ba8af73d1a3a353a894 -msgid "" -"Fixed a regression bug that equal operation against nonexistent reference " -"always matches." -msgstr "" - -# a737c0e78e154876a716a1d45e6a6bae -msgid "" -"Fixed a regression bug that static index construction doesn't work on BSD " -"based system. [GitHub#264] [Reported by Ayumu Osanai]" -msgstr "" - -# 7b3548207df54c5e89af223262870959 -msgid "Fixed a bug that ``--with-libstemmer`` configure option is ignored." -msgstr "" - -msgid "[deb] Fixed a bug that logrotate script has a syntax error." -msgstr "" - -# 28af245ee15a497a91b7803665b30191 -msgid "" -"Fixed a bug that grouped result can't be got when :doc:`/reference/command/" -"command_version` is ``2``. [GitHub ranguba/rroonga#38] [Reported by YUKI " -"\"Piro\" Hiroshi]" -msgstr "" - -msgid "Hiroshi Hatake" -msgstr "" - -# c72a2e1d12c544f28225b3ba1f12228d -msgid "akira yamada" -msgstr "" - -# 711adc2b885041b08d3b8c44060221f7 -msgid "kashihara" -msgstr "" - -# 2f2197a1749a475e9329f4e63a655572 -msgid "Ayumu Osanai" -msgstr "" - -# 35e9dc2cce9f4b019eff75a6e4d7e071 -msgid "funa 1g" -msgstr "" - -# eb68b4d05d1d4f448e6a4d8b9fd8bf07 -msgid "YUKI \"Piro\" Hiroshi" -msgstr "" - -# e520bdf5563a4a8b9c80022fe921da74 -msgid "Yuya TAMANO" -msgstr "" - -msgid "Release 4.0.8 - 2014/11/29" -msgstr "" - -msgid "[deb] Supported Ubuntu 12.04 again because Travis-CI runs on it." -msgstr "" - -msgid "" -"[mruby] Supported pretty print - ``\"pp\"`` for debugging. And supported to " -"show internal objects more descriptive format when inspecting it." -msgstr "" - -msgid "" -"Supported full text search query without index if one column is specified " -"for ``--match_columns`` even though sequential search is executed by ``--" -"query`` and ``--match_columns`` combination. [groonga-dev,02902] [Reported " -"by Atsushi Shinoda]" -msgstr "" - -msgid "" -"[experimental] :doc:`/reference/functions/in_values` supports auto " -"sequential search mode. There is a case that sequential search is faster " -"than index search when the number of narrowed down records is small enough " -"in contrast to the number of expected records to narrow down by " -"``in_values`` with ``AND`` operation which use indexes. The value of " -"``GRN_IN_VALUES_TOO_MANY_INDEX_MATCH_RATIO`` is used as threshold whether " -"Groonga execute sequential search or search with indexes in such a case." -msgstr "" - -msgid "[mruby] Supported to load relative path of script." -msgstr "" - -msgid "" -"Supported test suite to write query optimizer test more easily with mruby " -"enabled build." -msgstr "" - -msgid "" -"Supported offline index construction for token filters. [GitHub#239] [Patch " -"by Naoya Murakami]" -msgstr "" - -msgid "" -"[experimental] :doc:`/reference/functions/between` supports auto sequential " -"search mode. Use the value of ``GRN_BETWEEN_TOO_MANY_INDEX_MATCH_RATIO`` as " -"threshold. Basic concept is similar to " -"``GRN_IN_VALUES_TOO_MANY_INDEX_MATCH_RATIO``." -msgstr "" - -msgid "" -"[experimental] Supported multiple drilldowns for :doc:`/reference/commands/" -"select` command. The syntax is extended to support this feature. The new one " -"is ``--drilldown[LABEL1].keys COLUMN1,COLUMN2`` for keys, ``--" -"drilldown[LABEL1].output_columns _value.COLUMN1,_value.COLUMN2,_nsubrecs`` " -"for output columns. In the previous versions, a client application must " -"implement by oneself for drilldown by multiple keys. Use ``_key[N]`` for ``--" -"drilldown[LABEL1].output_columns`` to show original value of key in records." -msgstr "" - -msgid "Supported to search ``'reference_column @ \"query\"'`` without index." -msgstr "" - -msgid "" -"[experimental] Added :doc:`/reference/commands/range_filter` command. It is " -"faster than :doc:`/reference/commands/select` command to fetch specific " -"range of records in most cases, because it doesn't returns the number of " -"matched records. There are limitations which doesn't support drilldown and " -"so on. Thus, ``range_filter`` is suitable for extracting first ``N`` " -"records in specific range for ranking or something else." -msgstr "" - -msgid "[httpd] Supported ``groonga-httpd`` on windows." -msgstr "" - -msgid "Supported vector column for drilldown." -msgstr "" - -msgid "" -"[deb] Changed ``groonga-httpd`` as default HTTP server package. ``groonga-" -"server-http`` is deprecated. Note that :doc:`/reference/executables/groonga-" -"server-http` functionality itself is still exists in Groonga. If you just " -"want to use simple HTTP server in traditional way, specify proper arguments " -"by command line for :doc:`/reference/executables/groonga`." -msgstr "" - -msgid "" -"Added configuration file for Windows CI on AppVeyor. [groonga-" -"dev,02970,02981] [Patch by Hiroshi Hatake]" -msgstr "" - -msgid "" -"[doc] Fixed duplicated execution example path about :doc:`/reference/" -"commands/table_create`. [GitHub groonga.org#14] [Reported by Masafumi " -"Yokoyama]" -msgstr "" - -msgid "" -"Fixed a bug that nested indexed full text search against ``X._key`` returns " -"empty results." -msgstr "" - -msgid "" -"Fixed flags parameter which is strict in BSD ``mkostemp(3)``. [GitHub#240] " -"[Patch by Jun Kuriyama]" -msgstr "" - -msgid "" -"Fixed a bug that :doc:`/reference/commands/select` command reports invalid " -"value type (table) as index column value type. It was fixed to ``UInt32``. " -"Note that it affects only the value of response header. The search results " -"is not changed at all." -msgstr "" - -msgid "" -"Fixed a bug that compare operations such as ``<``, ``<=``, ``>``, ``>=``, ``!" -"=`` with Time and String type returns invalid results." -msgstr "" - -msgid "" -"Fixed a bug that prefix search can't be executed against single character " -"such as ``\"x*\"``. [GitHub#242] [Patch by Naoya Murakami]" -msgstr "" - -msgid "Fixed a memory leak on drilldown ``ShortText`` value with ``--filter``." -msgstr "" - -msgid "" -"Fixed missing ``\",\"`` for ``\"DDL:set_token_filters\"`` log. [Reported by " -"Naoya Murakami]" -msgstr "" - -msgid "Atsushi Shinoda" -msgstr "" - -msgid "Jun Kuriyama" -msgstr "" - -msgid "Release 4.0.7 - 2014/10/29" -msgstr "" - -msgid "[windows] Supported Groonga with mruby on Windows." -msgstr "" - -msgid "Added token filter plugin API." -msgstr "" - -msgid "" -"Added :ref:`token-filter-stop-word` token filter plugin. It treats records " -"of ``is_stop_word`` column as actual stop words." -msgstr "" - -msgid "" -"[doc] Added :doc:`/client` section which introduces link to client " -"libraries. [GitHub#210] [Patch by Naoya Murakami]" -msgstr "" - -msgid "" -"[doc] Reconstructed documentation. :doc:`/reference/suggest` and :doc:`/" -"reference/operations/geolocation_search` are grouped under :doc:`/" -"reference`. [GitHub#206] [Patch by Naoya Murakami]" -msgstr "" - -msgid "" -"[deb] Added stop word token filter plugin. [GitHub#216] [Patch by Hiroshi " -"Hatake]" -msgstr "" - -msgid "[deb] Clarified licenses about used/bundled files in debian/copyright." -msgstr "" - -msgid "Dropped LZO compression support." -msgstr "" - -msgid "Added LZ4 compression support. [GitHub#223] [Patch by Naoya Murakami]" -msgstr "" - -msgid "" -"Added :doc:`/reference/functions/in_values`. We recommends to use it instead " -"of ``==`` and ``OR`` combinations ( ``((COLUMN == \"a\") OR (COLUMN == \"b" -"\") OR (COLUMN == \"c\"))`` ) because of better performance." -msgstr "" - -msgid "" -"[load] Supported to update existing record in ``TABLE_NO_KEY`` by specifying " -"a record by ``_id``." -msgstr "" - -msgid "" -"Added :ref:`token-filter-stem` token filter plugin. It provides stemming " -"feature. To use this token filter, you need to install `libstemmer <http://" -"http://snowball.tartarus.org/>`_ library." -msgstr "" - -msgid "" -"[doc] Added :doc:`/reference/token_filters` documentation. [GitHub#227] " -"[Patch by Naoya Murakami]" -msgstr "" - -msgid "" -"[doc] Fixed link of the Ranguba project. [GitHub#212] [Patch by Naoya " -"Murakami]" -msgstr "" - -msgid "" -"[httpd] Updated bundled nginx version to 1.7.6. [GitHub#208] [Patch by " -"Hiroshi Hatake]" -msgstr "" - -msgid "" -"[power8] Fixed build failure. See http://lists.askmonty.org/pipermail/" -"commits/2014-October/006752.html [Patch by Sergey Vojtovich]" -msgstr "" - -msgid "" -"Fixed a bug that URL encoding fails if ``char`` type is build as ``unsigned " -"char`` type. [GitHub#217]" -msgstr "" - -msgid "" -"Fixed a bug that a ``TABLE_DAT_KEY`` table returns empty results for :doc:`/" -"reference/commands/select`. [GitHub#220]" -msgstr "" - -msgid "" -"Fixed a memory leak about inspecting vector column. It occurs when something " -"error reports about vector column." -msgstr "" - -msgid "" -"Fixed memory leaks in zlib/LZO compressed column [GitHub#221] [Patch by " -"Naoya Murakami]" -msgstr "" - -msgid "" -"Fixed a bug that the value of ``Int8`` column which is less than 100 may " -"return true in ``--filter``. By this issue, not intended records may be " -"included as search results." -msgstr "" - -msgid "Fixed to handle binary operation for vector column as an error." -msgstr "" - -msgid "" -"Fixed a bug that ``!XXX`` may return inverted result on big endian " -"environment." -msgstr "" - -msgid "Fixed a memory leak on converting weight vector to text." -msgstr "" - -msgid "" -"[dump] Fixed token filters and ``TABLE_NO_KEY`` related error in :doc:`/" -"reference/commands/dump`. [GitHub#215] [Patch by Naoya Murakami]" -msgstr "" - -msgid "Sergey Vojtovich" -msgstr "" - -msgid "Release 4.0.6 - 2014/09/29" -msgstr "Release 4.0.6 - 2014/09/29" - -msgid "" -"[deb] Updated to follow the rule about machine-readable debian/copyright " -"file. [Reported by Hideki Yamane]" -msgstr "" - -msgid "" -"[deb][rpm] Changed to use signal instead of HTTP to control nginx. This way " -"meets nginx style init script." -msgstr "" - -msgid "" -"[doc] Updated English documentation about [ :doc:`/reference/executables` ]. " -"[GitHub#196] [Patch by Masafumi Yokoyama]" -msgstr "" - -msgid "" -"[OS X] Added missing sphinx error message for Homebrew users. [GitHub#198] " -"[Patch by cosmo0920]" -msgstr "" - -msgid "" -"[mruby] Query optimizer by mruby became a practical for some range select " -"query. For example, mruby optimizer overhead is negligible enough for query " -"such as \"between(X, 0, 'exclude', 100, 'include')\" - \"X > 0 && X <= 100\"." -msgstr "" - -msgid "" -"[doc] Changed to recommend GitHub for reporting issues. Until now, Redmine " -"account must be approved by administrator, so you can not report at feel " -"free. [GitHub#202] [Patch by cosmo0920]" -msgstr "" - -msgid "" -"[doc] Translated C API document. [GitHub#203] [Patch by NOKUBI Takatsugu]" -msgstr "" - -msgid "" -"Supported to customize similarity threshold by ``'*S10\"...\"'`` syntax." -msgstr "" - -msgid "" -"Added source column validation to :doc:`/reference/commands/column_create`. " -"If source column doesn't exist, :doc:`/reference/commands/column_create` " -"returns ``false`` and column isn't created." -msgstr "" - -msgid "[debian] Dropped Debian jessie and sid support." -msgstr "" - -msgid "" -"Fixed a bug that similar search doesn't use IDF (Inverse Document Frequency) " -"for choosing target tokens. In the previous versions, it used token ID " -"instead of IDF. [groonga-dev,02731] [groonga-dev,02754] [Reported by Satoshi " -"Mitani, warp kawada]" -msgstr "" - -msgid "" -"Fixed a crash bug when deleting a record. If the table of the record has " -"``_key`` and ``_key`` is indexed from two or more index columns, deleting " -"causes a crash." -msgstr "" - -msgid "" -"Fixed compiler warning about unused variable 'e'. [GitHub#197] [Patch by " -"cosmo0920]" -msgstr "" - -msgid "[fedora][httpd] Fixed service start failure without log directory." -msgstr "" - -msgid "" -"[mruby] Fixed build error with ``--disable-mruby``. [GitHub#200] [Patch by " -"cosmo0920]" -msgstr "" - -msgid "" -"Fixed build warning about CMP0014 for MariaDB bundled Mroonga package. " -"[GitHub#201] [Patch by cosmo0920]" -msgstr "" - -msgid "" -"Fixed a bug that \"*\" is parsed as prefix search with empty string. " -"[groonga-dev,02796] [Reported by Kazuhiko]" -msgstr "" - -msgid "" -"[httpd] Updated bundled nginx version to the latest mainline (1.7.5). This " -"update contains vulnerability fix (CVE-2014-3616)." -msgstr "" - -msgid "NOKUBI Takatsugu" -msgstr "" - -msgid "Satoshi Mitani" -msgstr "" - -msgid "warp kawada" -msgstr "" - -msgid "Release 4.0.5 - 2014/08/29" -msgstr "" - -msgid "Dropped Ubuntu 13.10 (Saucy Salamander)." -msgstr "" - -msgid "Supported to show weight vector element as XML." -msgstr "" - -msgid "" -"[ :doc:`/reference/functions/between` ] Supported outside of key range. " -"[GitHub#183] [Patch by Naoya Murakami]" -msgstr "" - -msgid "[mruby] Changed to use Onigmo as regexp implementation." -msgstr "" - -msgid "" -"Added :doc:`/reference/functions/highlight_full` and :doc:`/reference/" -"functions/highlight_html` which tags output text. [GitHub#185] [Patch by " -"Naoya Murakami]" -msgstr "" - -msgid "" -"[doc] Updated outdated functions/commands reference [GitHub#188] " -"[GitHub#189] [Patch by Naoya Murakami]" -msgstr "" - -msgid "[benchmark] Added average and median in benchmark result." -msgstr "" - -msgid "" -"Exported :c:func:`grn_selector_func` and :c:func:`grn_proc_set_selector` for " -"plugin developer. [GitHub#190] [Patch by Naoya Murakami]" -msgstr "" - -msgid "" -"[ :doc:`/reference/commands/tokenize` ] Added \"mode\" option to control " -"behavior. You can use ``GET`` or ``ADD`` as a mode. [GitHub#191] " -"[GitHub#192] [Patch by Naoya Murakami]" -msgstr "" - -msgid "Supported near search by '\\*N\"A Z\"' syntax." -msgstr "" - -msgid "" -"Supported to customize behavior of tokenizer whether it skips token or skips " -"token with position. This feature is useful for developing tokenizer plugin. " -"[GitHub#193] [Patch by Naoya Murakami]" -msgstr "" - -msgid "" -"[doc] Updated description that a bug report is accepted in Japanese on " -"GitHub issue tracker. [Reported by 6elz] [groonga-dev,02651]" -msgstr "" - -msgid "[doc] Updated tutorial in English. [GitHub#194] [Patch by cosmo0920]" -msgstr "" - -msgid "" -"[php] Fixed memory leak when :c:func:`grn_ctx_recv()` is used. [GitHub#184] " -"[Patch by @do-aki]" -msgstr "" - -msgid "" -"[php] Fixed to avoid double free when :c:func:`grn_ctx_close()` is called. " -"[GitHub#184] [Patch by @do-aki]" -msgstr "" - -msgid "Fixed to support out-of-tree build again." -msgstr "" - -msgid "" -"[httpd] Updated bundled nginx version to the latest mainline (1.7.4). This " -"update contains vulnerability fix." -msgstr "" - -msgid "" -"Fixed a bug that infinite loop occurs sometimes when updating indexes. " -"[groonga-dev,02673] [Reported by MINAGAWA Sho]" -msgstr "" - -msgid "" -"Fixed a bug that document frequency is invalid when :ref:`offline-index-" -"construction` is used. [groonga-dev,02691] [Reported by Naoya Murakami]" -msgstr "" - -msgid "@do-aki" -msgstr "" - -msgid "6elz" -msgstr "" - -msgid "MINAGAWA Sho" -msgstr "" - -msgid "Release 4.0.4 - 2014/07/29" -msgstr "" - -msgid "[httpd] Updated bundled nginx version to the latest mainline (1.7.3)." -msgstr "" - -msgid "Supported weight in vector column." -msgstr "" - -msgid "" -"[ :doc:`/reference/executables/groonga-benchmark` ] Added missing " -"description about HTTP." -msgstr "" - -msgid "[ :doc:`/tutorial` ] Updated English tutorial documentation." -msgstr "" - -msgid "[example] Supported Ruby 1.9 or later for edict2grn.rb." -msgstr "" - -msgid "[http][admin] Updated to use English as default language. [GitHub#182]" -msgstr "" - -msgid "Fixed to show right syntax error location in response." -msgstr "" - -msgid "" -"[httpd] Fixed build error on Clang. [GitHub clear-code/rurema-search#11] " -"[Reported by niku]" -msgstr "" - -msgid "niku" -msgstr "" - -msgid "Release 4.0.3 - 2014/06/29" -msgstr "" - -msgid "" -"[experimental][ :doc:`/reference/executables/groonga-server-http` ] " -"Supported POST." -msgstr "" - -msgid "" -"[windows] Bundled libwinpthread-1.dll. Because newer libgcc_s_sjlj-1.dll " -"depends on libwinpthread-1.dll. [groonga-dev,02398] [Reported by Masafumi " -"Yokoyama]" -msgstr "" - -msgid "" -"[ :doc:`/reference/executables/groonga` ] Changed the default port number of " -"GQTP to 10043. Because server packages use 10043 by default. [GitHub#172] " -"[Patch by Naoya Murakami]" -msgstr "" - -msgid "" -"[ :doc:`/reference/commands/normalize` ] Added more validations for invalid " -"argument. [groonga-dev,02409][GitHub:#174] [Reported by GMO Media, Inc.]" -"[Patch by Naoya Murakami]" -msgstr "" - -msgid "" -"[ :doc:`/reference/commands/tokenize` ] Added more validations for invalid " -"argument." -msgstr "" - -msgid "" -"[ :doc:`/reference/executables/groonga-server-http` ] Supported ``Expect: " -"100-Continue`` request." -msgstr "" - -msgid "Exported ``grn_proc_get_type()``." -msgstr "" - -msgid "" -"[ :doc:`/reference/executables/groonga-suggest-learner` ] Added ``--log-" -"path`` and ``--log-level`` options." -msgstr "" - -msgid "Deprecated ``GRN_CTX_USE_QL``." -msgstr "" - -msgid "Deprecated ``GRN_CTX_BATCH_MODE``." -msgstr "" - -msgid "Added ``grn_text_printf()``." -msgstr "" - -msgid "Added ``grn_text_vprintf()``." -msgstr "" - -msgid "Removed limitation of one query log size." -msgstr "" - -msgid "" -"Added :c:func:`grn_plugin_expr_var_init()`. [GitHub#175][Patch by Naoya " -"Murakami]" -msgstr "" - -msgid "" -"Added :c:func:`grn_plugin_command_create()`. [GitHub#175][Patch by Naoya " -"Murakami]" -msgstr "" - -msgid "[GitHub#176] Supported reference vector column with weight." -msgstr "" - -msgid "" -"[plugin] Used public API instead of internal API. [GitHub#177][GitHub#178] " -"[Patch by Naoya Murakami]" -msgstr "" - -msgid "[doc][plugin] Added plugin APIs. [GitHub#179] [Patch by Naoya Murakami]" -msgstr "" - -msgid "" -"[windows] Re-supported Visual C++ 2010. [groonga-dev,02454] [Reported by " -"cosmo0920]." -msgstr "" - -msgid "" -"[rpm][groonga-server-gqtp] Fixed a bug that HTTP protocol is used not GQTP. " -"[GitHub#173] [Patch by Naoya Murakami]" -msgstr "" - -msgid "" -"[ :doc:`/reference/commands/select` ] Fixed a crash bug when :ref:`select-" -"adjuster` has a syntax error." -msgstr "" - -msgid "GMO Media, Inc." -msgstr "" - -msgid "Release 4.0.2 - 2014/05/29" -msgstr "" - -msgid "" -"[doc] Updated documentation about :doc:`/reference/executables/groonga-" -"suggest-leaner`." -msgstr "" - -msgid "" -"[doc] Added documentation about how to update files. [GitHub#160] [Patch by " -"cosmo0920]" -msgstr "" - -msgid "" -"[doc] Updated to caplitalized \"Groonga\" terms in documentation. " -"[GitHub#162][GitHub#163][GitHub#164] [Patch by cosmo0920]" -msgstr "" - -msgid "Supported Ubuntu 14.04 (Trusty Tahr)." -msgstr "" - -msgid "Dropped Ubuntu 12.10." -msgstr "" - -msgid "" -"Migrated Ubuntu package distribution site to PPA on Launchpad. See :doc:`/" -"install/ubuntu` for details." -msgstr "" - -msgid "" -"Handled all requests that start with ``/d/`` as API requests. You need to " -"put files to directories that don't start with ``/d/`` to serve by Groonga " -"HTTP service." -msgstr "" - -msgid "" -"[munin] Supported :doc:`/reference/executables/groonga-httpd`. [Reported by " -"Naoya Murakami]" -msgstr "" - -msgid "Supported daylight saving time. [#2546]" -msgstr "" - -msgid "" -"[doc] Added a description about ``--with-mecab`` in :doc:`/install/mac_os_x`." -msgstr "" - -msgid "" -"[http] Changed HTTP return code to ``400 Bad Request`` from ``500 Internal " -"Server Error`` for syntax error case." -msgstr "" - -msgid "" -"[http][admin] Removed jQuery JSON plugin. [GitHub#168] [Patch by Tetsuharu " -"OHZEKI]" -msgstr "" - -msgid "" -"[http][admin] Enabled strict mode. [GitHub#169] [Patch by Tetsuharu OHZEKI]" -msgstr "" - -msgid "" -"Exported getting variable APIs to :doc:`/reference/api/plugin`. [GitHub#170] " -"[Patch by Naoya Murakami]" -msgstr "" - -msgid "Added ``grn_plugin_proc_get_var()``." -msgstr "" - -msgid "Added ``grn_plugin_proc_get_var_by_offset()``." -msgstr "" - -msgid "" -"[experimental] Added :doc:`/reference/commands/tokenizer_list`. [GitHub#171] " -"[Patch by Naoya Murakami]" -msgstr "" - -msgid "" -"[experimental] Added :doc:`/reference/commands/normalizer_list`. " -"[GitHub#171] [Patch by Naoya Murakami]" -msgstr "" - -msgid "" -"[index] Fixed a bug that wrong max segment. It causes a crash when you use " -"all allocated resource for an index column. [#2438] [Reported by GMO Media, " -"Inc.]" -msgstr "" - -msgid "" -"[doc] Fixed a typo in :doc:`/install/centos`. [GitHub#166] [Patch by Naoya " -"Murakami]" -msgstr "" - -msgid "" -"[doc] Fixed the wrong default value of ``drilldown_output_columns`` in :doc:" -"`/reference/commands/select`. [GitHub#167] [Patch by Naoya Murakami]" -msgstr "" - -msgid "" -"[doc] Added a missing ``\\`` escape exception in :doc:`/reference/grn_expr/" -"query_syntax`. [Reported by @Yappo]" -msgstr "" - -msgid "Tetsuharu OHZEKI" -msgstr "" - -msgid "Release 4.0.1 - 2014/03/29" -msgstr "Release 4.0.1 - 2014/03/29" - -msgid "" -"[doc] Added a link in return value to detailed header description (:doc:`/" -"reference/command/output_format`)." -msgstr "" -"[doc] Added a link in return value to detailed header description (:doc:`/" -"reference/command/output_format`)." - -msgid "" -"Supported to inspect vector and object value in JSON load. It shows more " -"details about data which is failed to load." -msgstr "" -"Supported to inspect vector and object value in JSON load. It shows more " -"details about data which is failed to load." - -msgid "" -"Added ``adjuster`` option to select command. adjuster options accepts " -"following syntax: INDEX_COLUMN @ STRING_LITERAL (* FACTOR)." -msgstr "" -"Added ``adjuster`` option to select command. adjuster options accepts " -"following syntax: INDEX_COLUMN @ STRING_LITERAL (* FACTOR)." - -msgid "" -"Supported :ref:`weight-vector-column`. You need to specify 'COLUMN_VECTOR|" -"WITH_WEIGHT' flags to create weight vector column." -msgstr "" -"Supported :ref:`weight-vector-column`. You need to specify 'COLUMN_VECTOR|" -"WITH_WEIGHT' flags to create weight vector column." - -msgid "" -"Added missing MIN/MAX macros on SunOS. [GitHub#154] [Patch by Sebastian " -"Wiedenroth]" -msgstr "" -"Added missing MIN/MAX macros on SunOS. [GitHub#154] [Patch by Sebastian " -"Wiedenroth]" - -msgid "Improved recycling garbage data. It suppress to increse database size." -msgstr "Improved recycling garbage data. It suppress to increse database size." - -msgid "" -"[doc] Added documentation about GET parameters for :doc:`/reference/" -"executables/groonga-suggest-httpd`." -msgstr "" -"[doc] Added documentation about GET parameters for :doc:`/reference/" -"executables/groonga-suggest-httpd`." - -msgid "[doc] Added documentation about :doc:`/reference/column`." -msgstr "[doc] Added documentation about :doc:`/reference/column`." - -msgid "[doc] Added documentation about :doc:`/reference/columns/vector`." -msgstr "[doc] Added documentation about :doc:`/reference/columns/vector`." - -msgid "[column_list] Supported to show weight vector column." -msgstr "[column_list] Supported to show weight vector column." - -msgid "" -"[column_create] Added error check for creating multi column index without " -"WITH_SECTION." -msgstr "" -"[column_create] Added error check for creating multi column index without " -"WITH_SECTION." - -msgid "" -"[httpd] Enabled stub status module (NginxHttpStubStatusModule) for groonga-" -"httpd. [Suggested by Masahiro Nagano]" -msgstr "" -"[httpd] Enabled stub status module (NginxHttpStubStatusModule) for groonga-" -"httpd. [Suggested by Masahiro Nagano]" - -msgid "" -"Fixed a bug that a division overflow caused a fatal error. For example, it " -"occurs when you execute 'COLUMN / -1' operation to Int32 or Int64 column. " -"[#2307]" -msgstr "" -"Fixed a bug that a division overflow caused a fatal error. For example, it " -"occurs when you execute 'COLUMN / -1' operation to Int32 or Int64 column. " -"[#2307]" - -msgid "Fixed a bug that '%' operations performs '/' operations. [#2307]" -msgstr "Fixed a bug that '%' operations performs '/' operations. [#2307]" - -msgid "" -"[doc] Fixed a wrong documentation about :doc:`reference/commands/" -"column_rename`. [Reported by nise_nabe]" -msgstr "" -"[doc] Fixed a wrong documentation about :doc:`reference/commands/" -"column_rename`. [Reported by nise_nabe]" - -msgid "" -"Fixed the issue that out of bound array element access may occurs. " -"[GitHub#158] [Reported by dcb314]" -msgstr "" -"Fixed the issue that out of bound array element access may occurs. " -"[GitHub#158] [Reported by dcb314]" - -msgid "Sebastian Wiedenroth" -msgstr "Sebastian Wiedenroth" - -msgid "Masahiro Nagano" -msgstr "Masahiro Nagano" - -msgid "nise_nabe" -msgstr "nise_nabe" - -msgid "dcb314" -msgstr "dcb314" - -msgid "Release 4.0.0 - 2014/02/09" -msgstr "Release 4.0.0 - 2014/02/09" - -msgid "Bump version to 4.0.0!" -msgstr "Bump version to 4.0.0!" - -msgid "" -"[normalizer] Supported to show \"checks\" which is used for calculating next " -"character position. Use WITH_CHECKS flag to enable this feature." -msgstr "" -"[normalizer] Supported to show \"checks\" which is used for calculating next " -"character position. Use WITH_CHECKS flag to enable this feature." - -msgid "[deb] Dropped Ubuntu 13.04 support." -msgstr "[deb] Dropped Ubuntu 13.04 support." - -msgid "" -"Fixed a crash bug that an object in grn_expr is used after it is freed. " -"Normally Groonga server users aren't affected this bug. This bug mainly " -"affects Rroonga users. Because this bug is occured by specifying column name " -"including pseudo column name - such as '_key' - Rroonga users may use the " -"usage." -msgstr "" -"Fixed a crash bug that an object in grn_expr is used after it is freed. " -"Normally Groonga server users aren't affected this bug. This bug mainly " -"affects Rroonga users. Because this bug is occured by specifying column name " -"including pseudo column name - such as '_key' - Rroonga users may use the " -"usage." - -msgid "" -"Fixed not to execute unexpected cascade delete which is introduced Groonga " -"3.0.8 release. If source's range and index's domain are different, Groonga " -"doesn't execute cascade delete. [groonga-dev,02073] [Reported by yoku]" -msgstr "" -"Fixed not to execute unexpected cascade delete which is introduced Groonga " -"3.0.8 release. If source's range and index's domain are different, Groonga " -"doesn't execute cascade delete. [groonga-dev,02073] [Reported by yoku]" - -msgid "" -"Fixed not to publish grn_snip structure. Use grn_obj instead of grn_snip. If " -"you use grn_snip_close, please replace grn_snip_close to grn_obj_close." -msgstr "" -"Fixed not to publish grn_snip structure. Use grn_obj instead of grn_snip. If " -"you use grn_snip_close, please replace grn_snip_close to grn_obj_close." - -msgid "" -"[snippet_html] Fixed a crash bug when --query is empty. [groonga-dev,02097] " -"[Reported by Naoya Murakami]" -msgstr "" -"[snippet_html] Fixed a crash bug when --query is empty. [groonga-dev,02097] " -"[Reported by Naoya Murakami]" - -msgid "" -"[snippet_html] Fixed to suppress ALERT level message when contents of column " -"is empty text. [groonga-dev,02097] [Reported by Naoya Murakami]" -msgstr "" -"[snippet_html] Fixed to suppress ALERT level message when contents of column " -"is empty text. [groonga-dev,02097] [Reported by Naoya Murakami]" - -msgid "" -"[groonga-httpd] Fixed a bug \"off\" is used as path name in " -"groonga_query_log_path. [groonga-dev,02113] [Reported by Ryoji Yamamoto]" -msgstr "" -"[groonga-httpd] Fixed a bug \"off\" is used as path name in " -"groonga_query_log_path. [groonga-dev,02113] [Reported by Ryoji Yamamoto]" - -msgid "Ryoji Yamamoto" -msgstr "Ryoji Yamamoto" - -msgid "News in Senna period" -msgstr "News in Senna period" - -msgid "Senna -> groonga - 2009/01/14" -msgstr "Senna -> groonga - 2009/01/14" - -msgid "2006/04/05" -msgstr "2006/04/05" - -msgid "SEN_INDEX_DELIMITED added" -msgstr "SEN_INDEX_DELIMITED added" - -msgid "sen_sel_term_extract added" -msgstr "sen_sel_term_extract added" - -msgid "2006/03/03" -msgstr "2006/03/03" - -msgid "snippet function added" -msgstr "snippet function added" - -msgid "2006/01/16" -msgstr "2006/01/16" - -msgid "io.c bug fix. index format changed" -msgstr "io.c bug fix. index format changed" - -msgid "2006/01/12" -msgstr "2006/01/12" - -msgid "windows porting released" -msgstr "windows porting released" - -msgid "2005/12/22" -msgstr "2005/12/22" - -msgid "" -"support unpatched version of mecab (0.81, 0.82pre, 0.90) no longer depends " -"on mecab mte patch." -msgstr "" -"support unpatched version of mecab (0.81, 0.82pre, 0.90) no longer depends " -"on mecab mte patch." - -msgid "2005/10/27" -msgstr "2005/10/27" - -msgid "mysql binding updated" -msgstr "mysql binding updated" - -msgid "2005/09/17" -msgstr "2005/09/17" - -msgid "mysql-5.0.12-beta binding from <tasuk****@hotto*****>" -msgstr "mysql-5.0.12-beta binding from <tasuk****@hotto*****>" - -msgid "2005/09/08" -msgstr "2005/09/08" - -msgid "utf-8 support enhanced. (SEN_INDEX_NORMALIZE become available)" -msgstr "utf-8 support enhanced. (SEN_INDEX_NORMALIZE become available)" - -msgid "2005/08/16" -msgstr "2005/08/16" - -msgid "Ruby binding has rewrited using SWIG and supports advanced API." -msgstr "Ruby binding has rewrited using SWIG and supports advanced API." - -msgid "SJIS support enhanced." -msgstr "SJIS support enhanced." - -msgid "2005/07/05" -msgstr "2005/07/05" - -msgid "Changes" -msgstr "Changes" - -msgid "the license has changed to LGPL from GPL." -msgstr "the license has changed to LGPL from GPL." - -msgid "2005/06/23" -msgstr "2005/06/23" - -msgid "advanced API functions implemented" -msgstr "advanced API functions implemented" - -msgid "2005/04/12" -msgstr "2005/04/12" - -msgid "" -"applied ftb patch for mysql binding from <ko****@yappo*****> 'IN BOOLEAN " -"MODE' supported" -msgstr "" -"applied ftb patch for mysql binding from <ko****@yappo*****> 'IN BOOLEAN " -"MODE' supported" - -#~ msgid "Added english documentation for ``load`` command." -#~ msgstr "Added english documentation for ``load`` command." Deleted: doc/locale/en/LC_MESSAGES/reference.po (+0 -16532) 100644 =================================================================== --- doc/locale/en/LC_MESSAGES/reference.po 2015-03-25 14:48:34 +0900 (d2f7ab5) +++ /dev/null @@ -1,16532 +0,0 @@ -# -*- po -*- -# English translations for Groonga package. -# Copyright (C) 2009-2014, Brazil, Inc -# This file is distributed under the same license as the Groonga package. -# Kouhei Sutou <kou �� clear-code.com>, 2014. -# -msgid "" -msgstr "" -"Project-Id-Version: Groonga 4.0.1\n" -"Report-Msgid-Bugs-To: \n" -"PO-Revision-Date: 2015-02-18 10:35+0900\n" -"Last-Translator: Kouhei Sutou <kou �� clear-code.com>\n" -"Language-Team: English\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" - -msgid "Execution example::" -msgstr "Execution example::" - -msgid "Reference manual" -msgstr "Reference manual" - -msgid "API" -msgstr "API" - -msgid "" -"Groonga can be used as a fulltext search library. This section describes " -"APIs that are provided by groonga." -msgstr "" -"Groonga can be used as a fulltext search library. This section describes " -"APIs that are provided by groonga." - -msgid "Global configurations" -msgstr "Global configurations" - -msgid "Summary" -msgstr "Summary" - -msgid "Groonga has the global configurations. You can access them by API." -msgstr "Groonga has the global configurations. You can access them by API." - -msgid "Reference" -msgstr "Reference" - -msgid "Returns the lock timeout." -msgstr "Returns the lock timeout." - -msgid "" -":c:type:`grn_ctx` acquires a lock for updating a shared value. If other :c:" -"type:`grn_ctx` is already updating the same value, :c:type:`grn_ctx` that " -"try to acquire a lock can't acquires a lock. The :c:type:`grn_ctx` that " -"can't acquires a lock waits 1 millisecond and try to acquire a lock again. " -"The try is done ``timeout`` times. If the :c:type:`grn_ctx` that can't " -"acquires a lock until ``timeout`` times, the tries are failed." -msgstr "" -":c:type:`grn_ctx` acquires a lock for updating a shared value. If other :c:" -"type:`grn_ctx` is already updating the same value, :c:type:`grn_ctx` that " -"try to acquire a lock can't acquires a lock. The :c:type:`grn_ctx` that " -"can't acquires a lock waits 1 millisecond and try to acquire a lock again. " -"The try is done ``timeout`` times. If the :c:type:`grn_ctx` that can't " -"acquires a lock until ``timeout`` times, the tries are failed." - -msgid "" -"The default lock timeout is ``10000000``. It means that Groonga doesn't " -"report a lock failure until about 3 hours. (1 * 10000000 [msec] = 10000 " -"[sec] = 166.666... [min] = 2.777... [hour])" -msgstr "" -"The default lock timeout is ``10000000``. It means that Groonga doesn't " -"report a lock failure until about 3 hours. (1 * 10000000 [msec] = 10000 " -"[sec] = 166.666... [min] = 2.777... [hour])" - -msgid "The lock timeout." -msgstr "The lock timeout." - -msgid "Sets the lock timeout." -msgstr "Sets the lock timeout." - -msgid "See :c:func:`grn_get_lock_timeout` about lock timeout." -msgstr "See :c:func:`grn_get_lock_timeout` about lock timeout." - -msgid "There are some special values for ``timeout``." -msgstr "There are some special values for ``timeout``." - -msgid "" -"``0``: It means that Groonga doesn't retry acquiring a lock. Groonga reports " -"a failure after one lock acquirement failure." -msgstr "" -"``0``: It means that Groonga doesn't retry acquiring a lock. Groonga reports " -"a failure after one lock acquirement failure." - -msgid "" -"negative value: It means that Groonga retries acquiring a lock until Groonga " -"can acquire a lock." -msgstr "" -"negative value: It means that Groonga retries acquiring a lock until Groonga " -"can acquire a lock." - -msgid "The new lock timeout." -msgstr "The new lock timeout." - -msgid "``GRN_SUCCESS``. It doesn't fail." -msgstr "``GRN_SUCCESS``. It doesn't fail." - -msgid "``grn_cache``" -msgstr "``grn_cache``" - -msgid "This API is experimental." -msgstr "This API is experimental." - -msgid "" -"``grn_cache`` is a data store that keeps responses of :doc:`/reference/" -"commands/select` command. It is not general use cache object. It is only " -"for :doc:`/reference/commands/select` command." -msgstr "" -"``grn_cache`` is a data store that keeps responses of :doc:`/reference/" -"commands/select` command. It is not general use cache object. It is only " -"for :doc:`/reference/commands/select` command." - -msgid "" -"You can just change the current cache object by :c:func:" -"`grn_cache_current_set()`. :doc:`/reference/commands/select` command " -"response cache is done internally." -msgstr "" -"You can just change the current cache object by :c:func:" -"`grn_cache_current_set()`. :doc:`/reference/commands/select` command " -"response cache is done internally." - -msgid "" -":doc:`/reference/commands/select` command uses one global cache object. If " -"you open multiple databases, the one cache is shared. It is an important " -"problem." -msgstr "" -":doc:`/reference/commands/select` command uses one global cache object. If " -"you open multiple databases, the one cache is shared. It is an important " -"problem." - -msgid "" -"If you open multiple databases and use :doc:`/reference/commands/select` " -"command, you need to use ``grn_cache`` object. It is :doc:`/reference/" -"executables/groonga-httpd` case. If you open only one database or don't use :" -"doc:`/reference/commands/select` command, you don't need to use " -"``grn_cache`` object. It is `rroonga <http://ranguba.org/#about-rroonga>`_ " -"case." -msgstr "" -"If you open multiple databases and use :doc:`/reference/commands/select` " -"command, you need to use ``grn_cache`` object. It is :doc:`/reference/" -"executables/groonga-httpd` case. If you open only one database or don't use :" -"doc:`/reference/commands/select` command, you don't need to use " -"``grn_cache`` object. It is `rroonga <http://ranguba.org/#about-rroonga>`_ " -"case." - -msgid "Example" -msgstr "Example" - -msgid "Here is an example that change the current cache object." -msgstr "Here is an example that change the current cache object." - -msgid "" -"It is an opaque cache object. You can create a ``grn_cache`` by :c:func:" -"`grn_cache_open()` and free the created object by :c:func:" -"`grn_cache_close()`." -msgstr "" -"It is an opaque cache object. You can create a ``grn_cache`` by :c:func:" -"`grn_cache_open()` and free the created object by :c:func:" -"`grn_cache_close()`." - -msgid "Creates a new cache object." -msgstr "Creates a new cache object." - -msgid "" -"If memory allocation for the new cache object is failed, ``NULL`` is " -"returned. Error information is stored into the ``ctx``." -msgstr "" -"If memory allocation for the new cache object is failed, ``NULL`` is " -"returned. Error information is stored into the ``ctx``." - -msgid "The context." -msgstr "The context." - -msgid "" -"A newly allocated cache object on success, ``NULL`` otherwise. The returned " -"cache object must be freed by :c:func:`grn_cache_close()`." -msgstr "" -"A newly allocated cache object on success, ``NULL`` otherwise. The returned " -"cache object must be freed by :c:func:`grn_cache_close()`." - -msgid "Frees resourses of the ``cache``." -msgstr "Frees resourses of the ``cache``." - -msgid "The cache object to be freed." -msgstr "The cache object to be freed." - -msgid "``GRN_SUCCESS`` on success, not ``GRN_SUCCESS`` otherwise." -msgstr "``GRN_SUCCESS`` on success, not ``GRN_SUCCESS`` otherwise." - -msgid "" -"Sets the cache object that is used in :doc:`/reference/commands/select` " -"command." -msgstr "" -"Sets the cache object that is used in :doc:`/reference/commands/select` " -"command." - -msgid "" -"The cache object that is used in :doc:`/reference/commands/select` command." -msgstr "" -"The cache object that is used in :doc:`/reference/commands/select` command." - -msgid "" -"Gets the cache object that is used in :doc:`/reference/commands/select` " -"command." -msgstr "" -"Gets the cache object that is used in :doc:`/reference/commands/select` " -"command." - -msgid "" -"The cache object that is used in :doc:`/reference/commands/select` command. " -"It may be ``NULL``." -msgstr "" -"The cache object that is used in :doc:`/reference/commands/select` command. " -"It may be ``NULL``." - -msgid "Sets the max number of entries of the cache object." -msgstr "Sets the max number of entries of the cache object." - -msgid "The cache object to be changed." -msgstr "The cache object to be changed." - -msgid "The new max number of entries of the cache object." -msgstr "The new max number of entries of the cache object." - -msgid "Gets the max number of entries of the cache object." -msgstr "Gets the max number of entries of the cache object." - -msgid "The target cache object." -msgstr "The target cache object." - -msgid "The max number of entries of the cache object." -msgstr "The max number of entries of the cache object." - -msgid "``grn_column``" -msgstr "``grn_column``" - -msgid "TODO..." -msgstr "TODO..." - -msgid "It returns the name of :doc:`/reference/columns/pseudo` ``_id``." -msgstr "It returns the name of :doc:`/reference/columns/pseudo` ``_id``." - -msgid "" -"It is useful to use with :c:macro:`GRN_COLUMN_NAME_ID_LEN` like the " -"following::" -msgstr "" -"It is useful to use with :c:macro:`GRN_COLUMN_NAME_ID_LEN` like the " -"following::" - -msgid "Since 3.1.1." -msgstr "Since 3.1.1." - -msgid "It returns the byte size of :c:macro:`GRN_COLUMN_NAME_ID`." -msgstr "It returns the byte size of :c:macro:`GRN_COLUMN_NAME_ID`." - -msgid "It returns the name of :doc:`/reference/columns/pseudo` ``_key``." -msgstr "It returns the name of :doc:`/reference/columns/pseudo` ``_key``." - -msgid "" -"It is useful to use with :c:macro:`GRN_COLUMN_NAME_KEY_LEN` like the " -"following::" -msgstr "" -"It is useful to use with :c:macro:`GRN_COLUMN_NAME_KEY_LEN` like the " -"following::" - -msgid "It returns the byte size of :c:macro:`GRN_COLUMN_NAME_KEY`." -msgstr "It returns the byte size of :c:macro:`GRN_COLUMN_NAME_KEY`." - -msgid "It returns the name of :doc:`/reference/columns/pseudo` ``_value``." -msgstr "It returns the name of :doc:`/reference/columns/pseudo` ``_value``." - -msgid "" -"It is useful to use with :c:macro:`GRN_COLUMN_NAME_VALUE_LEN` like the " -"following::" -msgstr "" -"It is useful to use with :c:macro:`GRN_COLUMN_NAME_VALUE_LEN` like the " -"following::" - -msgid "It returns the byte size of :c:macro:`GRN_COLUMN_NAME_VALUE`." -msgstr "It returns the byte size of :c:macro:`GRN_COLUMN_NAME_VALUE`." - -msgid "It returns the name of :doc:`/reference/columns/pseudo` ``_score``." -msgstr "It returns the name of :doc:`/reference/columns/pseudo` ``_score``." - -msgid "" -"It is useful to use with :c:macro:`GRN_COLUMN_NAME_SCORE_LEN` like the " -"following::" -msgstr "" -"It is useful to use with :c:macro:`GRN_COLUMN_NAME_SCORE_LEN` like the " -"following::" - -msgid "It returns the byte size of :c:macro:`GRN_COLUMN_NAME_SCORE`." -msgstr "It returns the byte size of :c:macro:`GRN_COLUMN_NAME_SCORE`." - -msgid "It returns the name of :doc:`/reference/columns/pseudo` ``_nsubrecs``." -msgstr "It returns the name of :doc:`/reference/columns/pseudo` ``_nsubrecs``." - -msgid "" -"It is useful to use with :c:macro:`GRN_COLUMN_NAME_NSUBRECS_LEN` like the " -"following::" -msgstr "" -"It is useful to use with :c:macro:`GRN_COLUMN_NAME_NSUBRECS_LEN` like the " -"following::" - -msgid "It returns the byte size of :c:macro:`GRN_COLUMN_NAME_NSUBRECS`." -msgstr "It returns the byte size of :c:macro:`GRN_COLUMN_NAME_NSUBRECS`." - -msgid "" -"tableに新たなカラムを定義します。nameは省略できません。一つのtableに同一の" -"nameのcolumnを複数定義することはできません。" -msgstr "" -"tableに新たなカラムを定義します。nameは省略できません。一つのtableに同一の" -"nameのcolumnを複数定義することはできません。" - -msgid "対象tableを指定します。" -msgstr "対象tableを指定します。" - -msgid "カラム名を指定します。" -msgstr "カラム名を指定します。" - -msgid "nameパラメータのsize(byte)を指定します。" -msgstr "nameパラメータのsize(byte)を指定します。" - -msgid "" -"カラムを格納するファイルパスを指定します。 flagsに ``GRN_OBJ_PERSISTENT`` が" -"指定されている場合のみ有効です。 NULLなら自動的にファイルパスが付与されます。" -msgstr "" -"カラムを格納するファイルパスを指定します。 flagsに ``GRN_OBJ_PERSISTENT`` が" -"指定されている場合のみ有効です。 NULLなら自動的にファイルパスが付与されます。" - -msgid "" -"``GRN_OBJ_PERSISTENT`` を指定すると永続columnとなります。 " -"``GRN_OBJ_COLUMN_INDEX`` を指定すると転置インデックスとなります。 " -"``GRN_OBJ_COLUMN_SCALAR`` を指定するとスカラ値(単独の値)を格納します。 " -"``GRN_OBJ_COLUMN_VECTOR`` を指定すると値の配列を格納します。 " -"``GRN_OBJ_COMPRESS_ZLIB`` を指定すると値をzlib圧縮して格納します。 " -"``GRN_OBJ_COMPRESS_LZO`` を指定すると値をlzo圧縮して格納します。 " -"``GRN_OBJ_COLUMN_INDEX`` と共に ``GRN_OBJ_WITH_SECTION`` を指定すると、転置索" -"引にsection(段落情報)を合わせて格納します。 ``GRN_OBJ_COLUMN_INDEX`` と共に " -"``GRN_OBJ_WITH_WEIGHT`` を指定すると、転置索引にweight情報を合わせて格納しま" -"す。 ``GRN_OBJ_COLUMN_INDEX`` と共に ``GRN_OBJ_WITH_POSITION`` を指定する" -"と、転置索引に出現位置情報を合わせて格納します。" -msgstr "" -"``GRN_OBJ_PERSISTENT`` を指定すると永続columnとなります。 " -"``GRN_OBJ_COLUMN_INDEX`` を指定すると転置インデックスとなります。 " -"``GRN_OBJ_COLUMN_SCALAR`` を指定するとスカラ値(単独の値)を格納します。 " -"``GRN_OBJ_COLUMN_VECTOR`` を指定すると値の配列を格納します。 " -"``GRN_OBJ_COMPRESS_ZLIB`` を指定すると値をzlib圧縮して格納します。 " -"``GRN_OBJ_COMPRESS_LZO`` を指定すると値をlzo圧縮して格納します。 " -"``GRN_OBJ_COLUMN_INDEX`` と共に ``GRN_OBJ_WITH_SECTION`` を指定すると、転置索" -"引にsection(段落情報)を合わせて格納します。 ``GRN_OBJ_COLUMN_INDEX`` と共に " -"``GRN_OBJ_WITH_WEIGHT`` を指定すると、転置索引にweight情報を合わせて格納しま" -"す。 ``GRN_OBJ_COLUMN_INDEX`` と共に ``GRN_OBJ_WITH_POSITION`` を指定する" -"と、転置索引に出現位置情報を合わせて格納します。" - -msgid "``GRN_OBJ_PERSISTENT`` を指定すると永続columnとなります。" -msgstr "``GRN_OBJ_PERSISTENT`` を指定すると永続columnとなります。" - -msgid "``GRN_OBJ_COLUMN_INDEX`` を指定すると転置インデックスとなります。" -msgstr "``GRN_OBJ_COLUMN_INDEX`` を指定すると転置インデックスとなります。" - -msgid "``GRN_OBJ_COLUMN_SCALAR`` を指定するとスカラ値(単独の値)を格納します。" -msgstr "``GRN_OBJ_COLUMN_SCALAR`` を指定するとスカラ値(単独の値)を格納します。" - -msgid "``GRN_OBJ_COLUMN_VECTOR`` を指定すると値の配列を格納します。" -msgstr "``GRN_OBJ_COLUMN_VECTOR`` を指定すると値の配列を格納します。" - -msgid "``GRN_OBJ_COMPRESS_ZLIB`` を指定すると値をzlib圧縮して格納します。" -msgstr "``GRN_OBJ_COMPRESS_ZLIB`` を指定すると値をzlib圧縮して格納します。" - -msgid "``GRN_OBJ_COMPRESS_LZO`` を指定すると値をlzo圧縮して格納します。" -msgstr "``GRN_OBJ_COMPRESS_LZO`` を指定すると値をlzo圧縮して格納します。" - -msgid "" -"``GRN_OBJ_COLUMN_INDEX`` と共に ``GRN_OBJ_WITH_SECTION`` を指定すると、転置索" -"引にsection(段落情報)を合わせて格納します。" -msgstr "" -"``GRN_OBJ_COLUMN_INDEX`` と共に ``GRN_OBJ_WITH_SECTION`` を指定すると、転置索" -"引にsection(段落情報)を合わせて格納します。" - -msgid "" -"``GRN_OBJ_COLUMN_INDEX`` と共に ``GRN_OBJ_WITH_WEIGHT`` を指定すると、転置索" -"引にweight情報を合わせて格納します。" -msgstr "" -"``GRN_OBJ_COLUMN_INDEX`` と共に ``GRN_OBJ_WITH_WEIGHT`` を指定すると、転置索" -"引にweight情報を合わせて格納します。" - -msgid "" -"``GRN_OBJ_COLUMN_INDEX`` と共に ``GRN_OBJ_WITH_POSITION`` を指定すると、転置" -"索引に出現位置情報を合わせて格納します。" -msgstr "" -"``GRN_OBJ_COLUMN_INDEX`` と共に ``GRN_OBJ_WITH_POSITION`` を指定すると、転置" -"索引に出現位置情報を合わせて格納します。" - -msgid "カラム値の型を指定します。定義済みのtypeあるいはtableを指定できます。" -msgstr "カラム値の型を指定します。定義済みのtypeあるいはtableを指定できます。" - -msgid "" -"oldvalue, newvalueの値から得られるキーに対応するcolumnの値の中の、id, section" -"に対応するエントリを更新します。columnは ``GRN_OBJ_COLUMN_INDEX`` 型のカラム" -"でなければなりません。" -msgstr "" -"oldvalue, newvalueの値から得られるキーに対応するcolumnの値の中の、id, section" -"に対応するエントリを更新します。columnは ``GRN_OBJ_COLUMN_INDEX`` 型のカラム" -"でなければなりません。" - -msgid "対象columnを指定します。" -msgstr "対象columnを指定します。" - -msgid "対象レコードのIDを指定します。" -msgstr "対象レコードのIDを指定します。" - -msgid "対象レコードのセクション番号を指定します。" -msgstr "対象レコードのセクション番号を指定します。" - -msgid "更新前の値を指定します。" -msgstr "更新前の値を指定します。" - -msgid "更新後の値を指定します。" -msgstr "更新後の値を指定します。" - -msgid "columnが属するtableを返します。" -msgstr "columnが属するtableを返します。" - -msgid "" -"ctxが使用するdbにおいてcolumnに対応する名前をnameに更新します。columnは永続オ" -"ブジェクトでなければいけません。" -msgstr "" -"ctxが使用するdbにおいてcolumnに対応する名前をnameに更新します。columnは永続オ" -"ブジェクトでなければいけません。" - -msgid "新しい名前を指定します。" -msgstr "新しい名前を指定します。" - -msgid "nameパラメータのsize（byte）を指定します。" -msgstr "nameパラメータのsize（byte）を指定します。" - -msgid "" -"カラムobjの名前の長さを返します。buf_sizeの長さが名前の長さ以上であった場合" -"は、namebufに該当する名前をコピーします。" -msgstr "" -"カラムobjの名前の長さを返します。buf_sizeの長さが名前の長さ以上であった場合" -"は、namebufに該当する名前をコピーします。" - -msgid "対象objectを指定します。" -msgstr "対象objectを指定します。" - -msgid "名前を格納するバッファ（呼出側で準備する）を指定します。" -msgstr "名前を格納するバッファ（呼出側で準備する）を指定します。" - -msgid "namebufのサイズ（byte長）を指定します。" -msgstr "namebufのサイズ（byte長）を指定します。" - -msgid "" -"columnに張られているindexのうち、opの操作を実行可能なものの数を返します。また" -"それらのidを、buf_sizeに指定された個数を上限としてindexbufに返します。" -msgstr "" -"columnに張られているindexのうち、opの操作を実行可能なものの数を返します。また" -"それらのidを、buf_sizeに指定された個数を上限としてindexbufに返します。" - -msgid "対象のcolumnを指定します。" -msgstr "対象のcolumnを指定します。" - -msgid "indexで実行したい操作を指定します。" -msgstr "indexで実行したい操作を指定します。" - -msgid "indexを格納するバッファ（呼出側で準備する）を指定します。" -msgstr "indexを格納するバッファ（呼出側で準備する）を指定します。" - -msgid "indexbufのサイズ（byte長）を指定します。" -msgstr "indexbufのサイズ（byte長）を指定します。" - -msgid "section番号を格納するint長バッファ（呼出側で準備する）を指定します。" -msgstr "section番号を格納するint長バッファ（呼出側で準備する）を指定します。" - -# 5028ca08c9934f03a4e524786dad5c78 -msgid "" -"This is a dangerous API. You must not use this API when other thread or " -"process accesses the target column. If you use this API against shared " -"column, the process that accesses the column may be broken and the column " -"may be broken." -msgstr "" - -# 6ad8cd3fce074509b2e47fff14ee58da -msgid "Clears all values in the column." -msgstr "" - -msgid "The column to be truncated." -msgstr "" - -msgid "``GRN_SUCCESS`` on success, not ``GRN_SUCCESS`` on error." -msgstr "``GRN_SUCCESS`` on success, not ``GRN_SUCCESS`` on error." - -msgid "``grn_command_version``" -msgstr "``grn_command_version``" - -msgid "デフォルトのcommand_versionを返します。" -msgstr "デフォルトのcommand_versionを返します。" - -msgid "デフォルトのcommand_versionを変更します。" -msgstr "デフォルトのcommand_versionを変更します。" - -msgid "変更後のデフォルトのcommand_versionを指定します。" -msgstr "変更後のデフォルトのcommand_versionを指定します。" - -msgid "``grn_content_type``" -msgstr "" - -msgid "" -":c:type:`grn_content_type` shows input type and output type. Currently, it " -"is used only for output type." -msgstr "" - -msgid "" -"Normally, you don't need to use this type. It is used internally in :c:func:" -"`grn_ctx_send()`." -msgstr "" - -msgid "Here are available values:" -msgstr "Here are available values:" - -msgid "" -"It means that outputting nothing or using the original format. :doc:`/" -"reference/commands/dump` uses the type." -msgstr "" - -msgid "`GRN_CONTENT_NONE`" -msgstr "" - -msgid "It means tab separated values format." -msgstr "" - -msgid "`GRN_CONTENT_TSV`" -msgstr "" - -msgid "It means JSON format." -msgstr "" - -msgid "`GRN_CONTENT_JSON`" -msgstr "" - -msgid "It means XML format." -msgstr "" - -msgid "`GRN_CONTENT_XML`" -msgstr "" - -msgid "" -"It means MessagePack format. You need MessagePack library on building " -"Groonga. If you don't have MessagePack library, you can't use this type." -msgstr "" - -msgid "`GRN_CONTENT_MSGPACK`" -msgstr "" - -msgid "``grn_ctx``" -msgstr "``grn_ctx``" - -msgid "" -":c:type:`grn_ctx` is the most important object. :c:type:`grn_ctx` keeps the " -"current infomation such as:" -msgstr "" -":c:type:`grn_ctx` is the most important object. :c:type:`grn_ctx` keeps the " -"current infomation such as:" - -msgid "The last occurred error." -msgstr "The last occurred error." - -msgid "The current encoding." -msgstr "The current encoding." - -msgid "The default thresholds. (e.g. :ref:`match-escalation-threshold`)" -msgstr "The default thresholds. (e.g. :ref:`match-escalation-threshold`)" - -msgid "" -"The default command version. (See :doc:`/reference/command/command_version`)" -msgstr "" -"The default command version. (See :doc:`/reference/command/command_version`)" - -msgid ":c:type:`grn_ctx` provides platform features such as:" -msgstr ":c:type:`grn_ctx` provides platform features such as:" - -msgid "Memory management." -msgstr "Memory management." - -msgid "Logging." -msgstr "Logging." - -msgid "Most APIs receive :c:type:`grn_ctx` as the first argument." -msgstr "Most APIs receive :c:type:`grn_ctx` as the first argument." - -msgid "" -"You can't use the same :c:type:`grn_ctx` from two or more threads. You need " -"to create a :c:type:`grn_ctx` for a thread. You can use two or more :c:type:" -"`grn_ctx` in a thread but it is not needed for usual use-case." -msgstr "" -"You can't use the same :c:type:`grn_ctx` from two or more threads. You need " -"to create a :c:type:`grn_ctx` for a thread. You can use two or more :c:type:" -"`grn_ctx` in a thread but it is not needed for usual use-case." - -msgid "ctxを初期化します。" -msgstr "ctxを初期化します。" - -msgid "初期化するctx構造体へのポインタを指定します。" -msgstr "初期化するctx構造体へのポインタを指定します。" - -msgid "初期化する ``ctx`` のオプションを指定します。" -msgstr "初期化する ``ctx`` のオプションを指定します。" - -msgid "ctxの管理するメモリを解放し、使用を終了します。" -msgstr "ctxの管理するメモリを解放し、使用を終了します。" - -msgid "" -"If ``ctx`` is initialized by :c:func:`grn_ctx_open()` not :c:func:" -"`grn_ctx_init()`, you need to use :c:func:`grn_ctx_close()` instead of :c:" -"func:`grn_ctx_fin()`." -msgstr "" - -msgid "解放するctx構造体へのポインタを指定します。" -msgstr "解放するctx構造体へのポインタを指定します。" - -msgid "初期化された :c:type:`grn_ctx` オブジェクトを返します。" -msgstr "初期化された :c:type:`grn_ctx` オブジェクトを返します。" - -msgid "" -":c:func:`grn_ctx_init()` で初期化された :c:type:`grn_ctx` オブジェクトは構造" -"体の実体をAPIの呼び元で確保するのに対して、 :c:func:`grn_ctx_open()` では" -"Groongaライブラリの内部で、実体を確保します。 どちらで初期化された :c:type:" -"`grn_ctx` も、 :c:func:`grn_ctx_fin()` で解放できます。 :c:func:" -"`grn_ctx_open()` で確保した :c:type:`grn_ctx` 構造体に関しては、:c:func:" -"`grn_ctx_fin()` で解放した後に、その :c:type:`grn_ctx` で作成した :c:type:" -"`grn_obj` を :c:func:`grn_obj_close()` によって解放しても問題ありません。" -msgstr "" -":c:func:`grn_ctx_init()` で初期化された :c:type:`grn_ctx` オブジェクトは構造" -"体の実体をAPIの呼び元で確保するのに対して、 :c:func:`grn_ctx_open()` では" -"Groongaライブラリの内部で、実体を確保します。 どちらで初期化された :c:type:" -"`grn_ctx` も、 :c:func:`grn_ctx_fin()` で解放できます。 :c:func:" -"`grn_ctx_open()` で確保した :c:type:`grn_ctx` 構造体に関しては、:c:func:" -"`grn_ctx_fin()` で解放した後に、その :c:type:`grn_ctx` で作成した :c:type:" -"`grn_obj` を :c:func:`grn_obj_close()` によって解放しても問題ありません。" - -msgid "" -"It calls :c:func:`grn_ctx_fin()` and frees allocated memory for ``ctx`` by :" -"c:func:`grn_ctx_open()`." -msgstr "" -"It calls :c:func:`grn_ctx_fin()` and frees allocated memory for ``ctx`` by :" -"c:func:`grn_ctx_open()`." - -msgid "no longer needed :c:type:`grn_ctx`." -msgstr "no longer needed :c:type:`grn_ctx`." - -msgid "ctxを破棄するときに呼ばれる関数を設定します。" -msgstr "ctxを破棄するときに呼ばれる関数を設定します。" - -msgid "対象ctxを指定します。" -msgstr "対象ctxを指定します。" - -msgid "``ctx`` を破棄するときに呼ばれる関数を指定します。" -msgstr "``ctx`` を破棄するときに呼ばれる関数を指定します。" - -msgid "command_versionを返します。" -msgstr "command_versionを返します。" - -msgid "command_versionを変更します。" -msgstr "command_versionを変更します。" - -msgid "変更後のcommand_versionを指定します。" -msgstr "変更後のcommand_versionを指定します。" - -msgid "" -"ctxが操作対象とするdbを指定します。NULLを指定した場合は、dbを操作しない状態" -"(init直後の状態)になります。" -msgstr "" -"ctxが操作対象とするdbを指定します。NULLを指定した場合は、dbを操作しない状態" -"(init直後の状態)になります。" - -msgid "Don't use it with :c:type:`grn_ctx` that has ``GRN_CTX_PER_DB`` flag." -msgstr "Don't use it with :c:type:`grn_ctx` that has ``GRN_CTX_PER_DB`` flag." - -msgid "ctxが使用するdbを指定します。" -msgstr "ctxが使用するdbを指定します。" - -msgid "" -"ctxが現在操作対象としているdbを返します。dbを使用していない場合はNULLを返しま" -"す。" -msgstr "" -"ctxが現在操作対象としているdbを返します。dbを使用していない場合はNULLを返しま" -"す。" - -msgid "" -"ctxが使用するdbからnameに対応するオブジェクトを検索して返す。nameに一致するオ" -"ブジェクトが存在しなければNULLを返す。" -msgstr "" -"ctxが使用するdbからnameに対応するオブジェクトを検索して返す。nameに一致するオ" -"ブジェクトが存在しなければNULLを返す。" - -msgid "検索しようとするオブジェクトの名前。" -msgstr "検索しようとするオブジェクトの名前。" - -msgid "" -"The number of bytes of name. If negative value is specified, name is assumed " -"that NULL-terminated string." -msgstr "" -"The number of bytes of name. If negative value is specified, name is assumed " -"that NULL-terminated string." - -msgid "" -"ctx、またはctxが使用するdbからidに対応するオブジェクトを検索して返す。idに一" -"致するオブジェクトが存在しなければNULLを返す。" -msgstr "" -"ctx、またはctxが使用するdbからidに対応するオブジェクトを検索して返す。idに一" -"致するオブジェクトが存在しなければNULLを返す。" - -msgid "検索しようとするオブジェクトのidを指定します。" -msgstr "検索しようとするオブジェクトのidを指定します。" - -# 227ef8afa1fc40b1a61bf3946b2fc63d -msgid "" -"It pushes all tables in the database of ``ctx`` into ``tables_buffer``. " -"``tables_buffer`` should be initialized as ``GRN_PVECTOR``. You can use " -"``GRN_PTR_INIT()`` with ``GRN_OBJ_VECTOR`` flags to initialize " -"``tables_buffer``." -msgstr "" - -msgid "Here is an example:" -msgstr "" - -msgid "The context object." -msgstr "" - -# c3046c21fa354c2dbcfd886e3ed2b46a -msgid "The output buffer to store tables." -msgstr "" - -msgid "Gets the current output type of the context." -msgstr "" - -msgid "Normally, this function isn't needed." -msgstr "" - -msgid "The output type of the context." -msgstr "" - -msgid "" -"Sets the new output type to the context. It is used by executing a command " -"by :c:func:`grn_expr_exec()`. If you use :c:func:`grn_ctx_send()`, the new " -"output type isn't used. :c:func:`grn_ctx_send()` sets output type from " -"command line internally." -msgstr "" - -msgid "The new output type." -msgstr "" - -msgid "``grn_db``" -msgstr "``grn_db``" - -msgid "It is used for specifying options for :c:func:`grn_db_create`." -msgstr "It is used for specifying options for :c:func:`grn_db_create`." - -msgid "組み込み型の名前となるnul終端文字列の配列を指定する。" -msgstr "組み込み型の名前となるnul終端文字列の配列を指定する。" - -msgid "" -"n_builtin_type_namesには、optarg.builtin_type_namesで指定する文字列の数を 指" -"定する。配列のoffsetはenum型grn_builtin_typeの値に対応する。" -msgstr "" -"n_builtin_type_namesには、optarg.builtin_type_namesで指定する文字列の数を 指" -"定する。配列のoffsetはenum型grn_builtin_typeの値に対応する。" - -msgid "新たなdbを作成します。" -msgstr "新たなdbを作成します。" - -msgid "初期化済みの :c:type:`grn_ctx` を指定します。" -msgstr "初期化済みの :c:type:`grn_ctx` を指定します。" - -msgid "" -"作成するdbを格納するファイルパスを指定します。NULLならtemporary dbとなりま" -"す。NULL以外のパスを指定した場合はpersistent dbとなります。" -msgstr "" -"作成するdbを格納するファイルパスを指定します。NULLならtemporary dbとなりま" -"す。NULL以外のパスを指定した場合はpersistent dbとなります。" - -msgid "" -"Currently, it is not used. It is just ignored. 作成するdbの組み込み型の名前" -"を変更する時に指定します。 optarg.builtin_type_namesには、組み込み型の名前と" -"なるnull終端文字列の配列を指定します。optarg.n_builtin_type_namesには、" -"optarg.builtin_type_namesで指定する文字列の数を指定します。配列のoffsetはenum" -"型grn_builtin_typeの値に対応します。" -msgstr "" -"Currently, it is not used. It is just ignored. 作成するdbの組み込み型の名前" -"を変更する時に指定します。 optarg.builtin_type_namesには、組み込み型の名前と" -"なるnull終端文字列の配列を指定します。optarg.n_builtin_type_namesには、" -"optarg.builtin_type_namesで指定する文字列の数を指定します。配列のoffsetはenum" -"型grn_builtin_typeの値に対応します。" - -msgid "Currently, it is not used. It is just ignored." -msgstr "Currently, it is not used. It is just ignored." - -msgid "作成するdbの組み込み型の名前を変更する時に指定します。" -msgstr "作成するdbの組み込み型の名前を変更する時に指定します。" - -msgid "" -"optarg.builtin_type_namesには、組み込み型の名前となるnull終端文字列の配列を指" -"定します。optarg.n_builtin_type_namesには、optarg.builtin_type_namesで指定す" -"る文字列の数を指定します。配列のoffsetはenum型grn_builtin_typeの値に対応しま" -"す。" -msgstr "" -"optarg.builtin_type_namesには、組み込み型の名前となるnull終端文字列の配列を指" -"定します。optarg.n_builtin_type_namesには、optarg.builtin_type_namesで指定す" -"る文字列の数を指定します。配列のoffsetはenum型grn_builtin_typeの値に対応しま" -"す。" - -msgid "既存のdbを開きます。" -msgstr "既存のdbを開きます。" - -msgid "開こうとするdbを格納するファイルパスを指定します。" -msgstr "開こうとするdbを格納するファイルパスを指定します。" - -msgid "dbの内容の最終更新時刻を現在時刻にします。" -msgstr "dbの内容の最終更新時刻を現在時刻にします。" - -msgid "最終更新時刻はキャッシュが有効かどうかの判断などに利用されます。" -msgstr "最終更新時刻はキャッシュが有効かどうかの判断などに利用されます。" - -msgid "内容が変更されたdbを指定します。" -msgstr "内容が変更されたdbを指定します。" - -msgid "objの属するdbを返します。" -msgstr "objの属するdbを返します。" - -msgid "This is an experimental API." -msgstr "" - -# 4631f4433f434d019da39a89596ce36f -msgid "" -"This is a dangerous API. You must not use this API when other thread or " -"process opens the target database. If you use this API against shared " -"database, the database may be broken." -msgstr "" - -# 9eec77d0e91148598f919310d74e80ff -msgid "" -"Checks the passed database and recovers it if it is broken and it can be " -"recovered." -msgstr "" - -# 270b866fb2dc478c8bcbfcb4541f7347 -msgid "" -"This API uses lock existence for checking whether the database is broken or " -"not." -msgstr "" - -msgid "Here are recoverable cases:" -msgstr "" - -# b193ebcacfe84eb39b682fce5cd87dea -msgid "Index column is broken. The index column must have source column." -msgstr "" - -msgid "Here are unrecoverable cases:" -msgstr "" - -# 15ad5f7022254e83a3ffb265b05f20c5 -msgid "Object name management feature is broken." -msgstr "" - -# 8846369aa8944f7f83b4cb952a0d3407 -msgid "Table is broken." -msgstr "" - -# 3cdd9995b63649369d5cc1fc886240d5 -msgid "Data column is broken." -msgstr "" - -# d46326cd16964bd68ff0f43eda983ede -msgid "" -"Object name management feature is used for managing table name, column name " -"and so on. If the feature is broken, the database can't be recovered. Please " -"re-create the database from backup." -msgstr "" - -# 31bb862557da4766b329f6af0eb3dbe9 -msgid "" -"Table and data column can be recovered by removing an existence lock and re-" -"add data." -msgstr "" - -msgid "The database to be recovered." -msgstr "" - -msgid "``grn_encoding``" -msgstr "``grn_encoding``" - -msgid "デフォルトのencodingを返します。" -msgstr "デフォルトのencodingを返します。" - -msgid "デフォルトのencodingを変更します。" -msgstr "デフォルトのencodingを変更します。" - -msgid "変更後のデフォルトのencodingを指定します。" -msgstr "変更後のデフォルトのencodingを指定します。" - -msgid "" -"Returns string representation for the encoding. For example, " -"'grn_encoding_to_string(``GRN_ENC_UTF8``)' returns '\"utf8\"'." -msgstr "" -"Returns string representation for the encoding. For example, " -"'grn_encoding_to_string(``GRN_ENC_UTF8``)' returns '\"utf8\"'." - -msgid "\"unknown\" is returned for invalid encoding." -msgstr "\"unknown\" is returned for invalid encoding." - -msgid "The encoding." -msgstr "The encoding." - -msgid "" -"Parses encoding name and returns grn_encoding. For example, " -"'grn_encoding_parse(\"UTF8\")' returns '``GRN_ENC_UTF8``'." -msgstr "" -"Parses encoding name and returns grn_encoding. For example, " -"'grn_encoding_parse(\"UTF8\")' returns '``GRN_ENC_UTF8``'." - -msgid "``GRN_ENC_UTF8`` is returned for invalid encoding name." -msgstr "``GRN_ENC_UTF8`` is returned for invalid encoding name." - -msgid "The encoding name." -msgstr "The encoding name." - -msgid "grn_expr" -msgstr "grn_expr" - -msgid "" -"`grn_expr` is an :c:type:`grn_obj` that represents an expression. Here is a " -"list of what expression can do:" -msgstr "" -"`grn_expr` is an :c:type:`grn_obj` that represents an expression. Here is a " -"list of what expression can do:" - -msgid "" -"Expression can apply some operations to a record by :c:func:`grn_expr_exec`." -msgstr "" -"Expression can apply some operations to a record by :c:func:`grn_expr_exec`." - -msgid "" -"Expression can represents search condition. :c:func:`grn_table_select` can " -"select records that match against the search condition represented by " -"expression." -msgstr "" -"Expression can represents search condition. :c:func:`grn_table_select` can " -"select records that match against the search condition represented by " -"expression." - -msgid "There are two string representations of expression:" -msgstr "There are two string representations of expression:" - -msgid ":doc:`/reference/grn_expr/query_syntax`" -msgstr ":doc:`/reference/grn_expr/query_syntax`" - -msgid ":doc:`/reference/grn_expr/script_syntax`" -msgstr ":doc:`/reference/grn_expr/script_syntax`" - -msgid "" -":c:func:`grn_expr_parse` parses string represented expression and appends " -"the parsed expression to another expression." -msgstr "" -":c:func:`grn_expr_parse` parses string represented expression and appends " -"the parsed expression to another expression." - -msgid "" -"Extracts keywords from ``expr`` and stores to ``keywords``. Keywords in " -"``keywords`` are owned by ``expr``. Don't unlink them. Each keyword is " -"``GRN_BULK`` and its domain is ``GRN_DB_TEXT``." -msgstr "" - -msgid "``keywords`` must be ``GRN_PVECTOR``." -msgstr "" - -msgid "Here is an example code::" -msgstr "" - -msgid "The context that creates the ``expr``." -msgstr "" - -msgid "The expression to be extracted." -msgstr "" - -msgid "The container to store extracted keywords. It must be ``GRN_PVECTOR``." -msgstr "" - -msgid "" -"The container to store extracted keywords. It must be ``GRN_PVECTOR``. Each " -"extracted keyword is ``GRN_BULK`` and its domain is ``GRN_DB_TEXT``. " -"Extracted keywords are owned by ``expr``. Don't unlink them." -msgstr "" - -msgid "" -"Each extracted keyword is ``GRN_BULK`` and its domain is ``GRN_DB_TEXT``." -msgstr "" - -msgid "Extracted keywords are owned by ``expr``. Don't unlink them." -msgstr "" - -msgid "Escapes ``target_characters`` in ``string`` by ``escape_character``." -msgstr "Escapes ``target_characters`` in ``string`` by ``escape_character``." - -msgid "" -"Its encoding must be the same encoding of ``string``. It is used for " -"allocating buffer for ``escaped_string``." -msgstr "" -"Its encoding must be the same encoding of ``string``. It is used for " -"allocating buffer for ``escaped_string``." - -msgid "String expression representation." -msgstr "String expression representation." - -msgid "" -"The byte size of ``string``. ``-1`` means ``string`` is NULL terminated " -"string." -msgstr "" -"The byte size of ``string``. ``-1`` means ``string`` is NULL terminated " -"string." - -msgid "" -"NULL terminated escape target characters. For example, ``\"+-><~*()\\\"\\\\:" -"\"`` is ``target_characters`` for :doc:`/reference/grn_expr/query_syntax`." -msgstr "" -"NULL terminated escape target characters. For example, ``\"+-><~*()\\\"\\\\:" -"\"`` is ``target_characters`` for :doc:`/reference/grn_expr/query_syntax`." - -msgid "" -"The character to use escape a character in ``target_characters``. For " -"example, ``\\\\`` (backslash) is ``escaped_character`` for :doc:`/reference/" -"grn_expr/query_syntax`." -msgstr "" -"The character to use escape a character in ``target_characters``. For " -"example, ``\\\\`` (backslash) is ``escaped_character`` for :doc:`/reference/" -"grn_expr/query_syntax`." - -msgid "The output of escaped ``string``. It should be text typed bulk." -msgstr "The output of escaped ``string``. It should be text typed bulk." - -msgid "Escapes special characters in :doc:`/reference/grn_expr/query_syntax`." -msgstr "Escapes special characters in :doc:`/reference/grn_expr/query_syntax`." - -msgid "" -"Its encoding must be the same encoding of ``query``. It is used for " -"allocating buffer for ``escaped_query``." -msgstr "" -"Its encoding must be the same encoding of ``query``. It is used for " -"allocating buffer for ``escaped_query``." - -msgid "" -"String expression representation in :doc:`/reference/grn_expr/query_syntax`." -msgstr "" -"String expression representation in :doc:`/reference/grn_expr/query_syntax`." - -msgid "" -"The byte size of ``query``. ``-1`` means ``query`` is NULL terminated string." -msgstr "" -"The byte size of ``query``. ``-1`` means ``query`` is NULL terminated string." - -msgid "The output of escaped ``query``. It should be text typed bulk." -msgstr "The output of escaped ``query``. It should be text typed bulk." - -msgid "``grn_geo``" -msgstr "``grn_geo``" - -msgid "" -"It selects records that are in the rectangle specified by top_left_point " -"parameter and bottom_right_point parameter. Records are searched by index " -"parameter. Found records are added to res parameter table with op parameter " -"operation." -msgstr "" -"It selects records that are in the rectangle specified by top_left_point " -"parameter and bottom_right_point parameter. Records are searched by index " -"parameter. Found records are added to res parameter table with op parameter " -"operation." - -msgid "the index column for TokyoGeoPoint or WGS84GeoPpoint type." -msgstr "the index column for TokyoGeoPoint or WGS84GeoPpoint type." - -msgid "" -"the top left point of the target rectangle. (ShortText, Text, LongText, " -"TokyoGeoPoint or WGS84GeoPoint)" -msgstr "" -"the top left point of the target rectangle. (ShortText, Text, LongText, " -"TokyoGeoPoint or WGS84GeoPoint)" - -msgid "" -"the bottom right point of the target rectangle. (ShortText, Text, LongText, " -"TokyoGeoPoint or WGS84GeoPoint)" -msgstr "" -"the bottom right point of the target rectangle. (ShortText, Text, LongText, " -"TokyoGeoPoint or WGS84GeoPoint)" - -msgid "" -"the table to store found record IDs. It must be ``GRN_TABLE_HASH_KEY`` type " -"table." -msgstr "" -"the table to store found record IDs. It must be ``GRN_TABLE_HASH_KEY`` type " -"table." - -msgid "the operator for matched records." -msgstr "the operator for matched records." - -msgid "" -"It estimates number of records in the rectangle specified by top_left_point " -"parameter and bottom_right_point parameter. Number of records is estimated " -"by index parameter. If an error is occurred, -1 is returned." -msgstr "" -"It estimates number of records in the rectangle specified by top_left_point " -"parameter and bottom_right_point parameter. Number of records is estimated " -"by index parameter. If an error is occurred, -1 is returned." - -msgid "" -"the top left point of the target rectangle. (ShortText, Text, LongText, " -"TokyoGeoPoint or WGS84GeoPoint)" -msgstr "" -"the top left point of the target rectangle. (ShortText, Text, LongText, " -"TokyoGeoPoint or WGS84GeoPoint)" - -msgid "" -"It opens a cursor to get records in the rectangle specfied by top_left_point " -"parameter and bottom_right_point parameter." -msgstr "" -"It opens a cursor to get records in the rectangle specfied by top_left_point " -"parameter and bottom_right_point parameter." - -msgid "" -"the cursor returns records from offset parameter position. offset parameter " -"is based on 0." -msgstr "" -"the cursor returns records from offset parameter position. offset parameter " -"is based on 0." - -msgid "the cursor returns at most limit parameter records. -1 means no limit." -msgstr "the cursor returns at most limit parameter records. -1 means no limit." - -msgid "" -"It returns the next posting that has record ID. It returns NULL after all " -"records are returned." -msgstr "" -"It returns the next posting that has record ID. It returns NULL after all " -"records are returned." - -msgid "the geo cursor." -msgstr "the geo cursor." - -msgid "``grn_hook``" -msgstr "``grn_hook``" - -msgid "objに対してhookを追加します。" -msgstr "objに対してhookを追加します。" - -msgid "" -"``GRN_HOOK_GET`` は、objectの参照時に呼び出されるhookを定義します。 " -"``GRN_HOOK_SET`` は、objectの更新時に呼び出されるhookを定義します。 " -"``GRN_HOOK_SELECT`` は、検索処理の実行中に適時呼び出され、処理の実行状況を調" -"べたり、実行の中断を指示することができます。" -msgstr "" -"``GRN_HOOK_GET`` は、objectの参照時に呼び出されるhookを定義します。 " -"``GRN_HOOK_SET`` は、objectの更新時に呼び出されるhookを定義します。 " -"``GRN_HOOK_SELECT`` は、検索処理の実行中に適時呼び出され、処理の実行状況を調" -"べたり、実行の中断を指示することができます。" - -msgid "``GRN_HOOK_GET`` は、objectの参照時に呼び出されるhookを定義します。" -msgstr "``GRN_HOOK_GET`` は、objectの参照時に呼び出されるhookを定義します。" - -msgid "``GRN_HOOK_SET`` は、objectの更新時に呼び出されるhookを定義します。" -msgstr "``GRN_HOOK_SET`` は、objectの更新時に呼び出されるhookを定義します。" - -msgid "" -"``GRN_HOOK_SELECT`` は、検索処理の実行中に適時呼び出され、処理の実行状況を調" -"べたり、実行の中断を指示することができます。" -msgstr "" -"``GRN_HOOK_SELECT`` は、検索処理の実行中に適時呼び出され、処理の実行状況を調" -"べたり、実行の中断を指示することができます。" - -msgid "" -"hookの実行順位。offsetに対応するhookの直前に新たなhookを挿入します。 0を指定" -"した場合は先頭に挿入されます。-1を指定した場合は末尾に挿入されます。 object" -"に複数のhookが定義されている場合は順位の順に呼び出されます。" -msgstr "" -"hookの実行順位。offsetに対応するhookの直前に新たなhookを挿入します。 0を指定" -"した場合は先頭に挿入されます。-1を指定した場合は末尾に挿入されます。 object" -"に複数のhookが定義されている場合は順位の順に呼び出されます。" - -msgid "hookの実行順位。offsetに対応するhookの直前に新たなhookを挿入します。" -msgstr "hookの実行順位。offsetに対応するhookの直前に新たなhookを挿入します。" - -msgid "" -"0を指定した場合は先頭に挿入されます。-1を指定した場合は末尾に挿入されます。" -msgstr "" -"0を指定した場合は先頭に挿入されます。-1を指定した場合は末尾に挿入されます。" - -msgid "objectに複数のhookが定義されている場合は順位の順に呼び出されます。" -msgstr "objectに複数のhookが定義されている場合は順位の順に呼び出されます。" - -msgid "手続きを指定します。" -msgstr "手続きを指定します。" - -msgid "hook固有情報を指定します。" -msgstr "hook固有情報を指定します。" - -msgid "objに定義されているhookの数を返します。" -msgstr "objに定義されているhookの数を返します。" - -msgid "hookタイプを指定します。" -msgstr "hookタイプを指定します。" - -msgid "" -"objに定義されているhookの手続き（proc）を返します。hook固有情報が定義されてい" -"る場合は、その内容をdataにコピーして返します。" -msgstr "" -"objに定義されているhookの手続き（proc）を返します。hook固有情報が定義されてい" -"る場合は、その内容をdataにコピーして返します。" - -msgid "実行順位を指定します。" -msgstr "実行順位を指定します。" - -msgid "hook固有情報格納バッファを指定します。" -msgstr "hook固有情報格納バッファを指定します。" - -msgid "objに定義されているhookを削除します。" -msgstr "objに定義されているhookを削除します。" - -msgid "``grn_ii``" -msgstr "``grn_ii``" - -msgid "buffered index builder" -msgstr "buffered index builder" - -msgid "特定のアプリケーション用に準備した内部APIです。" -msgstr "特定のアプリケーション用に準備した内部APIです。" - -msgid "``grn_index_cursor``" -msgstr "``grn_index_cursor``" - -msgid "" -":c:type:`grn_table_cursor` から取得できるそれぞれのレコードについて、 " -"``GRN_OBJ_COLUMN_INDEX`` 型のカラムの値を順番に取り出すためのカーソルを生成し" -"て返します。" -msgstr "" -":c:type:`grn_table_cursor` から取得できるそれぞれのレコードについて、 " -"``GRN_OBJ_COLUMN_INDEX`` 型のカラムの値を順番に取り出すためのカーソルを生成し" -"て返します。" - -msgid "" -"rid_min, rid_maxを指定して取得するレコードidの値を制限することができます。" -msgstr "" -"rid_min, rid_maxを指定して取得するレコードidの値を制限することができます。" - -msgid "" -"戻り値であるgrn_index_cursorは :c:func:`grn_obj_close()` を使って解放します。" -msgstr "" -"戻り値であるgrn_index_cursorは :c:func:`grn_obj_close()` を使って解放します。" - -msgid "対象cursorを指定します。" -msgstr "対象cursorを指定します。" - -msgid "対象インデックスカラムを指定します。" -msgstr "対象インデックスカラムを指定します。" - -msgid "出力するレコードidの下限を指定します。" -msgstr "出力するレコードidの下限を指定します。" - -msgid "出力するレコードidの上限を指定します。" -msgstr "出力するレコードidの上限を指定します。" - -msgid "cursorの範囲内のインデックスの値を順番に取り出します。" -msgstr "cursorの範囲内のインデックスの値を順番に取り出します。" - -msgid "" -"tidにNULL以外を指定した場合は、index_cursorを作成するときに指定した" -"table_cursorの現在の対象レコードのidを返します。" -msgstr "" -"tidにNULL以外を指定した場合は、index_cursorを作成するときに指定した" -"table_cursorの現在の対象レコードのidを返します。" - -msgid "戻り値である :c:type:`grn_posting` 構造体は解放する必要はありません。" -msgstr "戻り値である :c:type:`grn_posting` 構造体は解放する必要はありません。" - -msgid "テーブルレコードIDを指定します。" -msgstr "テーブルレコードIDを指定します。" - -msgid "``grn_info``" -msgstr "``grn_info``" - -msgid "objのtypeに対応する情報をvaluebufに格納します。" -msgstr "objのtypeに対応する情報をvaluebufに格納します。" - -msgid "対象objを指定します。" -msgstr "対象objを指定します。" - -msgid "取得する情報の種類を指定します。" -msgstr "取得する情報の種類を指定します。" - -msgid "値を格納するバッファ（呼出側で準備）を指定します。" -msgstr "値を格納するバッファ（呼出側で準備）を指定します。" - -msgid "objのtypeに対応する情報をvalueの内容に更新します。" -msgstr "objのtypeに対応する情報をvalueの内容に更新します。" - -msgid "設定する情報の種類を指定します。" -msgstr "設定する情報の種類を指定します。" - -msgid "" -"objのidに対応するレコードの、typeに対応する情報をvaluebufに格納します。呼出側" -"ではtypeに応じて十分なサイズのバッファを確保しなければいけません。" -msgstr "" -"objのidに対応するレコードの、typeに対応する情報をvaluebufに格納します。呼出側" -"ではtypeに応じて十分なサイズのバッファを確保しなければいけません。" - -msgid "対象IDを指定します。" -msgstr "対象IDを指定します。" - -msgid "" -"objのidに対応するレコードのtypeに対応する情報をvalueの内容に更新します。" -msgstr "" -"objのidに対応するレコードのtypeに対応する情報をvalueの内容に更新します。" - -msgid "設定しようとする値を指定します。" -msgstr "設定しようとする値を指定します。" - -msgid "``grn_match_escalation``" -msgstr "``grn_match_escalation``" - -msgid "" -"検索の挙動をエスカレーションする閾値を返します。エスカレーションの詳細は検索" -"の仕様に関するドキュメントを参照してください。" -msgstr "" -"検索の挙動をエスカレーションする閾値を返します。エスカレーションの詳細は検索" -"の仕様に関するドキュメントを参照してください。" - -msgid "" -"検索の挙動をエスカレーションする閾値を変更します。エスカレーションの詳細は検" -"索の仕様に関するドキュメントを参照してください。" -msgstr "" -"検索の挙動をエスカレーションする閾値を変更します。エスカレーションの詳細は検" -"索の仕様に関するドキュメントを参照してください。" - -msgid "変更後の検索の挙動をエスカレーションする閾値を指定します。" -msgstr "変更後の検索の挙動をエスカレーションする閾値を指定します。" - -msgid "" -"デフォルトの検索の挙動をエスカレーションする閾値を返します。エスカレーション" -"の詳細は検索の仕様に関するドキュメントを参照してください。" -msgstr "" -"デフォルトの検索の挙動をエスカレーションする閾値を返します。エスカレーション" -"の詳細は検索の仕様に関するドキュメントを参照してください。" - -msgid "" -"デフォルトの検索の挙動をエスカレーションする閾値を変更します。エスカレーショ" -"ンの詳細は詳細は検索の仕様に関するドキュメントを参照してください。" -msgstr "" -"デフォルトの検索の挙動をエスカレーションする閾値を変更します。エスカレーショ" -"ンの詳細は詳細は検索の仕様に関するドキュメントを参照してください。" - -msgid "変更後のデフォルトの検索の挙動をエスカレーションする閾値を指定します。" -msgstr "変更後のデフォルトの検索の挙動をエスカレーションする閾値を指定します。" - -msgid "``grn_obj``" -msgstr "``grn_obj``" - -msgid "" -"nameがカラム名の場合、それに対応するtableのカラムを返します。対応するカラムが" -"存在しなければNULLを返します。" -msgstr "" -"nameがカラム名の場合、それに対応するtableのカラムを返します。対応するカラムが" -"存在しなければNULLを返します。" - -msgid "" -"nameはアクセサ文字列の場合、それに対応するaccessorを返します。アクセサ文字列" -"とは、カラム名等を'.'で連結した文字列です。'_id', '_key'は特殊なアクセサで、" -"それぞれレコードID/keyを返します。例) 'col1' / 'col2.col3' / 'col2._id'" -msgstr "" -"nameはアクセサ文字列の場合、それに対応するaccessorを返します。アクセサ文字列" -"とは、カラム名等を'.'で連結した文字列です。'_id', '_key'は特殊なアクセサで、" -"それぞれレコードID/keyを返します。例) 'col1' / 'col2.col3' / 'col2._id'" - -msgid "Check whether Groonga built-in object." -msgstr "Check whether Groonga built-in object." - -msgid "context" -msgstr "context" - -msgid "target object" -msgstr "target object" - -msgid "``GRN_TRUE`` for built-in groonga object, ``GRN_FALSE`` otherwise." -msgstr "``GRN_TRUE`` for built-in groonga object, ``GRN_FALSE`` otherwise." - -msgid "" -"objのIDに対応するレコードのvalueを取得します。valueを戻り値として返します。" -msgstr "" -"objのIDに対応するレコードのvalueを取得します。valueを戻り値として返します。" - -msgid "値を格納するバッファ（呼出側で準備する）を指定します。" -msgstr "値を格納するバッファ（呼出側で準備する）を指定します。" - -msgid "" -"objに指定されたカラムについて、offsetに指定されたレコードIDを開始位置として、" -"IDが連続するレコードに対応するカラム値が昇順に格納された配列へのポインタを" -"valuesにセットします。" -msgstr "" -"objに指定されたカラムについて、offsetに指定されたレコードIDを開始位置として、" -"IDが連続するレコードに対応するカラム値が昇順に格納された配列へのポインタを" -"valuesにセットします。" - -msgid "" -"取得できた件数が戻り値として返されます。エラーが発生した場合は -1 が返されま" -"す。" -msgstr "" -"取得できた件数が戻り値として返されます。エラーが発生した場合は -1 が返されま" -"す。" - -msgid "" -"値が固定長であるカラムのみがobjに指定できます。範囲内のIDに対応するレコードが" -"有効であるとは限りません。delete操作を実行したことのあるテーブルに対しては、:" -"c:func:`grn_table_at()` などによって各レコードの存否を別途確認しなければなり" -"ません。" -msgstr "" -"値が固定長であるカラムのみがobjに指定できます。範囲内のIDに対応するレコードが" -"有効であるとは限りません。delete操作を実行したことのあるテーブルに対しては、:" -"c:func:`grn_table_at()` などによって各レコードの存否を別途確認しなければなり" -"ません。" - -msgid "値を取得する範囲の開始位置となるレコードIDを指定します。" -msgstr "値を取得する範囲の開始位置となるレコードIDを指定します。" - -msgid "値の配列がセットされます。" -msgstr "値の配列がセットされます。" - -msgid "" -"objのIDに対応するレコードの値を更新します。対応するレコードが存在しない場合" -"は ``GRN_INVALID_ARGUMENT`` を返します。" -msgstr "" -"objのIDに対応するレコードの値を更新します。対応するレコードが存在しない場合" -"は ``GRN_INVALID_ARGUMENT`` を返します。" - -msgid "格納する値を指定します。" -msgstr "格納する値を指定します。" - -msgid "" -"以下の値を指定できます。 .. hlist:: :columns: 3 * :c:macro:" -"`GRN_OBJ_SET` * :c:macro:`GRN_OBJ_INCR` * :c:macro:`GRN_OBJ_DECR` " -"* :c:macro:`GRN_OBJ_APPEND` * :c:macro:`GRN_OBJ_PREPEND` * :c:macro:" -"`GRN_OBJ_GET` * :c:macro:`GRN_OBJ_COMPARE` * :c:macro:" -"`GRN_OBJ_LOCK` * :c:macro:`GRN_OBJ_UNLOCK`" -msgstr "" -"以下の値を指定できます。 .. hlist:: :columns: 3 * :c:macro:" -"`GRN_OBJ_SET` * :c:macro:`GRN_OBJ_INCR` * :c:macro:`GRN_OBJ_DECR` " -"* :c:macro:`GRN_OBJ_APPEND` * :c:macro:`GRN_OBJ_PREPEND` * :c:macro:" -"`GRN_OBJ_GET` * :c:macro:`GRN_OBJ_COMPARE` * :c:macro:" -"`GRN_OBJ_LOCK` * :c:macro:`GRN_OBJ_UNLOCK`" - -msgid "以下の値を指定できます。" -msgstr "以下の値を指定できます。" - -msgid ":c:macro:`GRN_OBJ_SET`" -msgstr ":c:macro:`GRN_OBJ_SET`" - -msgid ":c:macro:`GRN_OBJ_INCR`" -msgstr ":c:macro:`GRN_OBJ_INCR`" - -msgid ":c:macro:`GRN_OBJ_DECR`" -msgstr ":c:macro:`GRN_OBJ_DECR`" - -msgid ":c:macro:`GRN_OBJ_APPEND`" -msgstr ":c:macro:`GRN_OBJ_APPEND`" - -msgid ":c:macro:`GRN_OBJ_PREPEND`" -msgstr ":c:macro:`GRN_OBJ_PREPEND`" - -msgid ":c:macro:`GRN_OBJ_GET`" -msgstr ":c:macro:`GRN_OBJ_GET`" - -msgid ":c:macro:`GRN_OBJ_COMPARE`" -msgstr ":c:macro:`GRN_OBJ_COMPARE`" - -msgid ":c:macro:`GRN_OBJ_LOCK`" -msgstr ":c:macro:`GRN_OBJ_LOCK`" - -msgid ":c:macro:`GRN_OBJ_UNLOCK`" -msgstr ":c:macro:`GRN_OBJ_UNLOCK`" - -msgid "レコードの値をvalueと置き換えます。" -msgstr "レコードの値をvalueと置き換えます。" - -msgid "レコードの値にvalueを加算します。" -msgstr "レコードの値にvalueを加算します。" - -msgid "レコードの値にvalueを減算します。" -msgstr "レコードの値にvalueを減算します。" - -msgid "レコードの値の末尾にvalueを追加します。" -msgstr "レコードの値の末尾にvalueを追加します。" - -msgid "レコードの値の先頭にvalueを追加します。" -msgstr "レコードの値の先頭にvalueを追加します。" - -msgid "新しいレコードの値をvalueにセットします。" -msgstr "新しいレコードの値をvalueにセットします。" - -msgid "レコードの値とvalueが等しいか調べます。" -msgstr "レコードの値とvalueが等しいか調べます。" - -msgid "" -"当該レコードをロックします。:c:macro:`GRN_OBJ_COMPARE` と共に指定された場合" -"は、レコードの値とvalueが等しい場合に限ってロックします。" -msgstr "" -"当該レコードをロックします。:c:macro:`GRN_OBJ_COMPARE` と共に指定された場合" -"は、レコードの値とvalueが等しい場合に限ってロックします。" - -msgid "当該レコードのロックを解除します。" -msgstr "当該レコードのロックを解除します。" - -msgid "" -"objをメモリから解放し、それが永続オブジェクトであった場合は、該当するファイル" -"一式を削除します。" -msgstr "" -"objをメモリから解放し、それが永続オブジェクトであった場合は、該当するファイル" -"一式を削除します。" - -msgid "" -"ctxが使用するdbにおいてobjに対応する名前をnameに更新します。objは永続オブジェ" -"クトでなければいけません。" -msgstr "" -"ctxが使用するdbにおいてobjに対応する名前をnameに更新します。objは永続オブジェ" -"クトでなければいけません。" - -msgid "" -"一時的なobjectであるobjをメモリから解放します。objに属するobjectも再帰的にメ" -"モリから解放されます。" -msgstr "" -"一時的なobjectであるobjをメモリから解放します。objに属するobjectも再帰的にメ" -"モリから解放されます。" - -msgid "" -"永続的な、table, column, exprなどは解放してはいけません。一般的には、一時的か" -"永続的かを気にしなくてよい :c:func:`grn_obj_unlink()` を用いるべきです。" -msgstr "" -"永続的な、table, column, exprなどは解放してはいけません。一般的には、一時的か" -"永続的かを気にしなくてよい :c:func:`grn_obj_unlink()` を用いるべきです。" - -msgid "objの型を変更します。" -msgstr "objの型を変更します。" - -msgid "" -"objは :c:func:`GRN_OBJ_INIT()` マクロなどで初期化済みでなければいけません。" -msgstr "" -"objは :c:func:`GRN_OBJ_INIT()` マクロなどで初期化済みでなければいけません。" - -msgid "変更後のobjの型を指定します。" -msgstr "変更後のobjの型を指定します。" - -msgid "" -"``GRN_OBJ_VECTOR`` を指定するとdomain型の値のベクタを格納するオブジェクトにな" -"ります。" -msgstr "" -"``GRN_OBJ_VECTOR`` を指定するとdomain型の値のベクタを格納するオブジェクトにな" -"ります。" - -msgid "" -"objをメモリから解放します。objに属するobjectも再帰的にメモリから解放されま" -"す。" -msgstr "" -"objをメモリから解放します。objに属するobjectも再帰的にメモリから解放されま" -"す。" - -msgid "objに対応するファイルパスを返します。一時objectならNULLを返します。" -msgstr "objに対応するファイルパスを返します。一時objectならNULLを返します。" - -msgid "objの名前の長さを返します。無名objectなら0を返します。" -msgstr "objの名前の長さを返します。無名objectなら0を返します。" - -msgid "" -"名前付きのobjectであり、buf_sizeの長さが名前の長以上であった場合は、namebufに" -"該当する名前をコピーします。" -msgstr "" -"名前付きのobjectであり、buf_sizeの長さが名前の長以上であった場合は、namebufに" -"該当する名前をコピーします。" - -msgid "" -"objパラメータのとる値の範囲を表わしているオブジェクトのIDを返します。例え" -"ば、:c:type:`grn_builtin_type` にある ``GRN_DB_INT`` などを返します。" -msgstr "" -"objパラメータのとる値の範囲を表わしているオブジェクトのIDを返します。例え" -"ば、:c:type:`grn_builtin_type` にある ``GRN_DB_INT`` などを返します。" - -msgid "" -"objの占有するメモリのうち、可能な領域をthresholdを指標として解放します。" -msgstr "" -"objの占有するメモリのうち、可能な領域をthresholdを指標として解放します。" - -msgid "objに対応するファイルの整合性を検査します。" -msgstr "objに対応するファイルの整合性を検査します。" - -msgid "" -"objをlockします。timeout（秒）経過してもlockを取得できない場合は " -"``GRN_RESOURCE_DEADLOCK_AVOIDED`` を返します。" -msgstr "" -"objをlockします。timeout（秒）経過してもlockを取得できない場合は " -"``GRN_RESOURCE_DEADLOCK_AVOIDED`` を返します。" - -msgid "objをunlockします。" -msgstr "objをunlockします。" - -msgid "強制的にロックをクリアします。" -msgstr "強制的にロックをクリアします。" - -msgid "objが現在lockされていれば0以外の値を返します。" -msgstr "objが現在lockされていれば0以外の値を返します。" - -msgid "" -"objの占有するDBファイル領域のうち、可能な領域をthresholdを指標としてフラグメ" -"ントの解消を行います。" -msgstr "" -"objの占有するDBファイル領域のうち、可能な領域をthresholdを指標としてフラグメ" -"ントの解消を行います。" - -msgid "フラグメント解消が実行されたセグメントの数を返します。" -msgstr "フラグメント解消が実行されたセグメントの数を返します。" - -msgid "objのidを返します。" -msgstr "objのidを返します。" - -msgid "" -"dbからidに対応するテーブルやカラムなどを削除します。mroonga向けに用意した内部" -"APIです。" -msgstr "" -"dbからidに対応するテーブルやカラムなどを削除します。mroonga向けに用意した内部" -"APIです。" - -msgid "The target database." -msgstr "The target database." - -msgid "The object (table, column and so on) ID to be deleted." -msgstr "The object (table, column and so on) ID to be deleted." - -msgid "" -"If ``GRN_TRUE``, clear object cache and remove relation between ID and key " -"in database. Otherwise, just clear object cache." -msgstr "" -"If ``GRN_TRUE``, clear object cache and remove relation between ID and key " -"in database. Otherwise, just clear object cache." - -msgid "dbのidに対応するpathを返します。mroonga向けに用意した内部APIです。" -msgstr "dbのidに対応するpathを返します。mroonga向けに用意した内部APIです。" - -msgid "path string corresponding to the id will be set in this buffer." -msgstr "path string corresponding to the id will be set in this buffer." - -msgid "``grn_proc``" -msgstr "``grn_proc``" - -msgid "nameに対応する新たなproc(手続き)をctxが使用するdbに定義します。" -msgstr "nameに対応する新たなproc(手続き)をctxが使用するdbに定義します。" - -msgid "作成するprocの名前を指定します。" -msgstr "作成するprocの名前を指定します。" - -msgid "" -"The number of bytes of name parameter. If negative value is specified, name " -"parameter is assumed that NULL-terminated string." -msgstr "" -"The number of bytes of name parameter. If negative value is specified, name " -"parameter is assumed that NULL-terminated string." - -msgid "procの種類を指定します。" -msgstr "procの種類を指定します。" - -msgid "初期化関数のポインタを指定します。" -msgstr "初期化関数のポインタを指定します。" - -msgid "実処理関数のポインタを指定します。" -msgstr "実処理関数のポインタを指定します。" - -msgid "終了関数のポインタを指定します。" -msgstr "終了関数のポインタを指定します。" - -msgid "procで使用する変数の数を指定します。" -msgstr "procで使用する変数の数を指定します。" - -msgid "" -"procで使用する変数の定義を指定します。( :c:type:`grn_expr_var` 構造体の配列)" -msgstr "" -"procで使用する変数の定義を指定します。( :c:type:`grn_expr_var` 構造体の配列)" - -msgid "" -"user_dataをキーとして、現在実行中の :c:type:`grn_proc_func` 関数および定義さ" -"れている変数( :c:type:`grn_expr_var` )の配列とその数を取得します。" -msgstr "" -"user_dataをキーとして、現在実行中の :c:type:`grn_proc_func` 関数および定義さ" -"れている変数( :c:type:`grn_expr_var` )の配列とその数を取得します。" - -msgid ":c:type:`grn_proc_func` に渡されたuser_dataを指定します。" -msgstr ":c:type:`grn_proc_func` に渡されたuser_dataを指定します。" - -msgid "変数の数を取得します。" -msgstr "変数の数を取得します。" - -msgid "objectを破棄するときに呼ばれる関数を設定します。" -msgstr "objectを破棄するときに呼ばれる関数を設定します。" - -msgid "table, column, proc, exprのみ設定可能です。" -msgstr "table, column, proc, exprのみ設定可能です。" - -msgid "objectを破棄するときに呼ばれる関数を指定します。" -msgstr "objectを破棄するときに呼ばれる関数を指定します。" - -msgid "``grn_search``" -msgstr "``grn_search``" - -msgid "" -"objを対象としてqueryにマッチするレコードを検索し、opの指定に従ってresにレコー" -"ドを追加あるいは削除します。" -msgstr "" -"objを対象としてqueryにマッチするレコードを検索し、opの指定に従ってresにレコー" -"ドを追加あるいは削除します。" - -msgid "検索対象のobjectを指定します。" -msgstr "検索対象のobjectを指定します。" - -msgid "検索クエリを指定します。" -msgstr "検索クエリを指定します。" - -msgid "検索結果を格納するテーブルを指定します。" -msgstr "検索結果を格納するテーブルを指定します。" - -msgid "" -"``GRN_OP_OR``, ``GRN_OP_AND``, ``GRN_OP_AND_NOT``, ``GRN_OP_ADJUST`` のいずれ" -"かを指定します。" -msgstr "" -"``GRN_OP_OR``, ``GRN_OP_AND``, ``GRN_OP_AND_NOT``, ``GRN_OP_ADJUST`` のいずれ" -"かを指定します。" - -msgid "詳細検索条件を指定します。" -msgstr "詳細検索条件を指定します。" - -msgid "``grn_table``" -msgstr "``grn_table``" - -msgid "nameパラメータに対応する新たなtableをctxが使用するdbに定義します。" -msgstr "nameパラメータに対応する新たなtableをctxが使用するdbに定義します。" - -msgid "" -"作成するtableの名前を指定します。NULLなら無名tableとなります。 persistent db" -"に対して名前をありのtableを作成するときには、flagsに ``GRN_OBJ_PERSISTENT`` " -"が指定されていなけれなりません。" -msgstr "" -"作成するtableの名前を指定します。NULLなら無名tableとなります。 persistent db" -"に対して名前をありのtableを作成するときには、flagsに ``GRN_OBJ_PERSISTENT`` " -"が指定されていなけれなりません。" - -msgid "作成するtableの名前を指定します。NULLなら無名tableとなります。" -msgstr "作成するtableの名前を指定します。NULLなら無名tableとなります。" - -msgid "" -"persistent dbに対して名前をありのtableを作成するときには、flagsに " -"``GRN_OBJ_PERSISTENT`` が指定されていなけれなりません。" -msgstr "" -"persistent dbに対して名前をありのtableを作成するときには、flagsに " -"``GRN_OBJ_PERSISTENT`` が指定されていなけれなりません。" - -msgid "" -"作成するtableのファイルパスを指定します。 flagsに ``GRN_OBJ_PERSISTENT`` が指" -"定されている場合のみ有効です。 NULLなら自動的にファイルパスが付与されます。" -msgstr "" -"作成するtableのファイルパスを指定します。 flagsに ``GRN_OBJ_PERSISTENT`` が指" -"定されている場合のみ有効です。 NULLなら自動的にファイルパスが付与されます。" - -msgid "" -"``GRN_OBJ_PERSISTENT`` を指定すると永続tableとなります。 " -"``GRN_OBJ_TABLE_PAT_KEY``, ``GRN_OBJ_TABLE_HASH_KEY``, " -"``GRN_OBJ_TABLE_NO_KEY`` のいずれかを指定します。 ``GRN_OBJ_KEY_NORMALIZE`` " -"を指定すると正規化された文字列がkeyとなります。 ``GRN_OBJ_KEY_WITH_SIS`` を" -"指定するとkey文字列の全suffixが自動的に登録されます。" -msgstr "" -"``GRN_OBJ_PERSISTENT`` を指定すると永続tableとなります。 " -"``GRN_OBJ_TABLE_PAT_KEY``, ``GRN_OBJ_TABLE_HASH_KEY``, " -"``GRN_OBJ_TABLE_NO_KEY`` のいずれかを指定します。 ``GRN_OBJ_KEY_NORMALIZE`` " -"を指定すると正規化された文字列がkeyとなります。 ``GRN_OBJ_KEY_WITH_SIS`` を" -"指定するとkey文字列の全suffixが自動的に登録されます。" - -msgid "``GRN_OBJ_PERSISTENT`` を指定すると永続tableとなります。" -msgstr "``GRN_OBJ_PERSISTENT`` を指定すると永続tableとなります。" - -msgid "" -"``GRN_OBJ_TABLE_PAT_KEY``, ``GRN_OBJ_TABLE_HASH_KEY``, " -"``GRN_OBJ_TABLE_NO_KEY`` のいずれかを指定します。" -msgstr "" -"``GRN_OBJ_TABLE_PAT_KEY``, ``GRN_OBJ_TABLE_HASH_KEY``, " -"``GRN_OBJ_TABLE_NO_KEY`` のいずれかを指定します。" - -msgid "" -"``GRN_OBJ_KEY_NORMALIZE`` を指定すると正規化された文字列がkeyとなります。" -msgstr "" -"``GRN_OBJ_KEY_NORMALIZE`` を指定すると正規化された文字列がkeyとなります。" - -msgid "" -"``GRN_OBJ_KEY_WITH_SIS`` を指定するとkey文字列の全suffixが自動的に登録されま" -"す。" -msgstr "" -"``GRN_OBJ_KEY_WITH_SIS`` を指定するとkey文字列の全suffixが自動的に登録されま" -"す。" - -msgid "" -"keyの型を指定します。``GRN_OBJ_TABLE_NO_KEY`` が指定された場合は無効です。 既" -"存のtypeあるいはtableを指定できます。 key_typeにtable Aを指定してtable Bを作" -"成した場合、Bは必ずAのサブセットとなります。" -msgstr "" -"keyの型を指定します。``GRN_OBJ_TABLE_NO_KEY`` が指定された場合は無効です。 既" -"存のtypeあるいはtableを指定できます。 key_typeにtable Aを指定してtable Bを作" -"成した場合、Bは必ずAのサブセットとなります。" - -msgid "" -"keyの型を指定します。``GRN_OBJ_TABLE_NO_KEY`` が指定された場合は無効です。 既" -"存のtypeあるいはtableを指定できます。" -msgstr "" -"keyの型を指定します。``GRN_OBJ_TABLE_NO_KEY`` が指定された場合は無効です。 既" -"存のtypeあるいはtableを指定できます。" - -msgid "" -"key_typeにtable Aを指定してtable Bを作成した場合、Bは必ずAのサブセットとなり" -"ます。" -msgstr "" -"key_typeにtable Aを指定してtable Bを作成した場合、Bは必ずAのサブセットとなり" -"ます。" - -msgid "" -"keyに対応する値を格納する領域の型を指定します。 tableはcolumnとは別に、keyに" -"対応する値を格納する領域を一つだけ持つことができます。" -msgstr "" -"keyに対応する値を格納する領域の型を指定します。 tableはcolumnとは別に、keyに" -"対応する値を格納する領域を一つだけ持つことができます。" - -msgid "" -"keyに対応する新しいrecordをtableに追加し、そのIDを返します。keyに対応する" -"recordがすでにtableに存在するならば、そのrecordのIDを返します。" -msgstr "" -"keyに対応する新しいrecordをtableに追加し、そのIDを返します。keyに対応する" -"recordがすでにtableに存在するならば、そのrecordのIDを返します。" - -msgid "" -"``GRN_OBJ_TABLE_NO_KEY`` が指定されたtableでは、key, key_size は無視されま" -"す。" -msgstr "" -"``GRN_OBJ_TABLE_NO_KEY`` が指定されたtableでは、key, key_size は無視されま" -"す。" - -msgid "検索keyを指定します。" -msgstr "検索keyを指定します。" - -msgid "" -"NULL以外の値が指定された場合、新たにrecordが追加された時には1が、既存record" -"だった時には0がセットされます。" -msgstr "" -"NULL以外の値が指定された場合、新たにrecordが追加された時には1が、既存record" -"だった時には0がセットされます。" - -msgid "" -"It finds a record that has key parameter and returns ID of the found record. " -"If table parameter is a database, it finds an object (table, column and so " -"on) that has key parameter and returns ID of the found object." -msgstr "" -"It finds a record that has key parameter and returns ID of the found record. " -"If table parameter is a database, it finds an object (table, column and so " -"on) that has key parameter and returns ID of the found object." - -msgid "The table or database." -msgstr "The table or database." - -msgid "The record or object key to be found." -msgstr "The record or object key to be found." - -msgid "" -"tableにidに対応するrecordが存在するか確認し、存在すれば指定されたIDを、存在し" -"なければ ``GRN_ID_NIL`` を返します。" -msgstr "" -"tableにidに対応するrecordが存在するか確認し、存在すれば指定されたIDを、存在し" -"なければ ``GRN_ID_NIL`` を返します。" - -msgid "" -"注意: 実行には相応のコストがかかるのであまり頻繁に呼ばないようにして下さい。" -msgstr "" -"注意: 実行には相応のコストがかかるのであまり頻繁に呼ばないようにして下さい。" - -msgid "検索idを指定します。" -msgstr "検索idを指定します。" - -msgid "" -"tableが ``GRN_TABLE_PAT_KEY`` もしくは ``GRN_TABLE_DAT_KEY`` を指定して作った" -"tableなら、longest common prefix searchを行い、対応するIDを返します。" -msgstr "" -"tableが ``GRN_TABLE_PAT_KEY`` もしくは ``GRN_TABLE_DAT_KEY`` を指定して作った" -"tableなら、longest common prefix searchを行い、対応するIDを返します。" - -msgid "" -"tableが ``GRN_TABLE_HASH_KEY`` を指定して作ったtableなら、完全に一致するキー" -"を検索し、対応するIDを返します。" -msgstr "" -"tableが ``GRN_TABLE_HASH_KEY`` を指定して作ったtableなら、完全に一致するキー" -"を検索し、対応するIDを返します。" - -msgid "tableのIDに対応するレコードのkeyを取得します。" -msgstr "tableのIDに対応するレコードのkeyを取得します。" - -msgid "" -"対応するレコードが存在する場合はkey長を返します。見つからない場合は0を返しま" -"す。対応するキーの検索に成功し、またbuf_sizeの長さがkey長以上であった場合は、" -"keybufに該当するkeyをコピーします。" -msgstr "" -"対応するレコードが存在する場合はkey長を返します。見つからない場合は0を返しま" -"す。対応するキーの検索に成功し、またbuf_sizeの長さがkey長以上であった場合は、" -"keybufに該当するkeyをコピーします。" - -msgid "keyを格納するバッファ(呼出側で準備する)を指定します。" -msgstr "keyを格納するバッファ(呼出側で準備する)を指定します。" - -msgid "keybufのサイズ(byte長)を指定します。" -msgstr "keybufのサイズ(byte長)を指定します。" - -msgid "" -"tableのkeyに対応するレコードを削除します。対応するレコードが存在しない場合は " -"``GRN_INVALID_ARGUMENT`` を返します。" -msgstr "" -"tableのkeyに対応するレコードを削除します。対応するレコードが存在しない場合は " -"``GRN_INVALID_ARGUMENT`` を返します。" - -msgid "検索keyのサイズを指定します。" -msgstr "検索keyのサイズを指定します。" - -msgid "" -"tableのidに対応するレコードを削除します。対応するレコードが存在しない場合は " -"``GRN_INVALID_ARGUMENT`` を返します。" -msgstr "" -"tableのidに対応するレコードを削除します。対応するレコードが存在しない場合は " -"``GRN_INVALID_ARGUMENT`` を返します。" - -msgid "レコードIDを指定します。" -msgstr "レコードIDを指定します。" - -msgid "" -"tableのidに対応するレコードのkeyを変更します。新しいkeyとそのbyte長をdest_key" -"とdest_key_sizeに指定します。" -msgstr "" -"tableのidに対応するレコードのkeyを変更します。新しいkeyとそのbyte長をdest_key" -"とdest_key_sizeに指定します。" - -msgid "この操作は、``GRN_TABLE_DAT_KEY`` 型のテーブルのみ使用できます。" -msgstr "この操作は、``GRN_TABLE_DAT_KEY`` 型のテーブルのみ使用できます。" - -msgid "" -"tableのsrc_keyに対応するレコードのkeyを変更します。新しいkeyとそのbyte長を" -"dest_keyとdest_key_sizeに指定します。" -msgstr "" -"tableのsrc_keyに対応するレコードのkeyを変更します。新しいkeyとそのbyte長を" -"dest_keyとdest_key_sizeに指定します。" - -msgid "対象レコードのkeyを指定します。" -msgstr "対象レコードのkeyを指定します。" - -msgid "対象レコードのkeyの長さ(byte)を指定します。" -msgstr "対象レコードのkeyの長さ(byte)を指定します。" - -msgid "変更後のkeyを指定します。" -msgstr "変更後のkeyを指定します。" - -msgid "変更後のkeyの長さ(byte)を指定します。" -msgstr "変更後のkeyの長さ(byte)を指定します。" - -msgid "tableの全レコードを一括して削除します。" -msgstr "tableの全レコードを一括して削除します。" - -msgid "" -"注意: multithread環境では他のthreadのアクセスによって、存在しないアドレスへア" -"クセスし、SIGSEGVが発生する可能性があります。" -msgstr "" -"注意: multithread環境では他のthreadのアクセスによって、存在しないアドレスへア" -"クセスし、SIGSEGVが発生する可能性があります。" - -msgid "table内のレコードをソートし、上位limit個の要素をresultに格納します。" -msgstr "table内のレコードをソートし、上位limit個の要素をresultに格納します。" - -msgid "" -"keys.keyには、tableのcolumn,accessor,procのいずれかが指定できます。keys.flags" -"には、``GRN_TABLE_SORT_ASC`` / ``GRN_TABLE_SORT_DESC`` のいずれかを指定できま" -"す。``GRN_TABLE_SORT_ASC`` では昇順、``GRN_TABLE_SORT_DESC`` では降順でソート" -"されます。keys.offsetは、内部利用のためのメンバです。" -msgstr "" -"keys.keyには、tableのcolumn,accessor,procのいずれかが指定できます。keys.flags" -"には、``GRN_TABLE_SORT_ASC`` / ``GRN_TABLE_SORT_DESC`` のいずれかを指定できま" -"す。``GRN_TABLE_SORT_ASC`` では昇順、``GRN_TABLE_SORT_DESC`` では降順でソート" -"されます。keys.offsetは、内部利用のためのメンバです。" - -msgid "" -"sortされたレコードのうち、(0ベースで)offset番目から順にresにレコードを格納し" -"ます。" -msgstr "" -"sortされたレコードのうち、(0ベースで)offset番目から順にresにレコードを格納し" -"ます。" - -msgid "resに格納するレコードの上限を指定します。" -msgstr "resに格納するレコードの上限を指定します。" - -msgid "結果を格納するtableを指定します。" -msgstr "結果を格納するtableを指定します。" - -msgid "ソートキー配列へのポインタを指定します。" -msgstr "ソートキー配列へのポインタを指定します。" - -msgid "ソートキー配列のサイズを指定します。" -msgstr "ソートキー配列のサイズを指定します。" - -msgid "tableのレコードを特定の条件でグループ化します。" -msgstr "tableのレコードを特定の条件でグループ化します。" - -msgid "group化キー構造体の配列へのポインタを指定します。" -msgstr "group化キー構造体の配列へのポインタを指定します。" - -msgid "group化キー構造体の配列のサイズを指定します。" -msgstr "group化キー構造体の配列のサイズを指定します。" - -msgid "group化の結果を格納する構造体の配列へのポインタを指定します。" -msgstr "group化の結果を格納する構造体の配列へのポインタを指定します。" - -msgid "group化の結果を格納する構造体の配列のサイズを指定します。" -msgstr "group化の結果を格納する構造体の配列のサイズを指定します。" - -msgid "table1とtable2をopの指定に従って集合演算した結果をresに格納します。" -msgstr "table1とtable2をopの指定に従って集合演算した結果をresに格納します。" - -msgid "" -"resにtable1あるいはtable2そのものを指定した場合を除けば、table1, table2は破壊" -"されません。" -msgstr "" -"resにtable1あるいはtable2そのものを指定した場合を除けば、table1, table2は破壊" -"されません。" - -msgid "対象table1を指定します。" -msgstr "対象table1を指定します。" - -msgid "対象table2を指定します。" -msgstr "対象table2を指定します。" - -msgid "実行する演算の種類を指定します。" -msgstr "実行する演算の種類を指定します。" - -msgid "" -"table1とtable2から重複するレコードを取り除いた結果をそれぞれres1, res2に格納" -"します。" -msgstr "" -"table1とtable2から重複するレコードを取り除いた結果をそれぞれres1, res2に格納" -"します。" - -msgid "" -"nameパラメータから始まるtableのカラムIDをresパラメータに格納します。name_size" -"パラメータが0の場合はすべてのカラムIDを格納します。" -msgstr "" -"nameパラメータから始まるtableのカラムIDをresパラメータに格納します。name_size" -"パラメータが0の場合はすべてのカラムIDを格納します。" - -msgid "取得したいカラム名のprefixを指定します。" -msgstr "取得したいカラム名のprefixを指定します。" - -msgid "nameパラメータの長さを指定します。" -msgstr "nameパラメータの長さを指定します。" - -msgid "結果を格納する ``GRN_TABLE_HASH_KEY`` のtableを指定します。" -msgstr "結果を格納する ``GRN_TABLE_HASH_KEY`` のtableを指定します。" - -msgid "格納したカラムIDの数を返します。" -msgstr "格納したカラムIDの数を返します。" - -msgid "tableに登録されているレコードの件数を返します。" -msgstr "tableに登録されているレコードの件数を返します。" - -msgid "" -"ctxが使用するdbにおいてtableに対応する名前をnameに更新します。tableの全ての" -"columnも同時に名前が変更されます。tableは永続オブジェクトでなければいけませ" -"ん。" -msgstr "" -"ctxが使用するdbにおいてtableに対応する名前をnameに更新します。tableの全ての" -"columnも同時に名前が変更されます。tableは永続オブジェクトでなければいけませ" -"ん。" - -msgid "``grn_table_cursor``" -msgstr "``grn_table_cursor``" - -msgid "" -"tableに登録されているレコードを順番に取り出すためのカーソルを生成して返しま" -"す。" -msgstr "" -"tableに登録されているレコードを順番に取り出すためのカーソルを生成して返しま" -"す。" - -msgid "" -"keyの下限を指定します。（NULLは下限なしと見なします。） " -"``GRN_CURSOR_PREFIX`` については後述。" -msgstr "" -"keyの下限を指定します。（NULLは下限なしと見なします。） " -"``GRN_CURSOR_PREFIX`` については後述。" - -msgid "minのsizeを指定します。``GRN_CURSOR_PREFIX`` については後述。" -msgstr "minのsizeを指定します。``GRN_CURSOR_PREFIX`` については後述。" - -msgid "" -"keyの上限を指定します。（NULLは上限なしと見なします。） " -"``GRN_CURSOR_PREFIX`` については後述。" -msgstr "" -"keyの上限を指定します。（NULLは上限なしと見なします。） " -"``GRN_CURSOR_PREFIX`` については後述。" - -msgid "" -"maxのsizeを指定します。``GRN_CURSOR_PREFIX`` については無視される場合がありま" -"す。" -msgstr "" -"maxのsizeを指定します。``GRN_CURSOR_PREFIX`` については無視される場合がありま" -"す。" - -msgid "" -"``GRN_CURSOR_ASCENDING`` を指定すると昇順にレコードを取り出します。 " -"``GRN_CURSOR_DESCENDING`` を指定すると降順にレコードを取り出します。(下記 " -"``GRN_CURSOR_PREFIX`` を指定し、keyが近いレコードを取得する場合、もしくは、" -"common prefix searchを行う場合には、``GRN_CURSOR_ASCENDING`` / " -"``GRN_CURSOR_DESCENDING`` は無視されます。) ``GRN_CURSOR_GT`` を指定すると" -"minに一致したkeyをcursorの範囲に含みません。(minがNULLの場合もしくは、下記 " -"``GRN_CURSOR_PREFIX`` を指定し、keyが近いレコードを取得する場合、もしくは、" -"common prefix searchを行う場合には、``GRN_CURSOR_GT`` は無視されます。) " -"``GRN_CURSOR_LT`` を指定するとmaxに一致したkeyをcursorの範囲に含みません。" -"(maxがNULLの場合もしくは、下記 ``GRN_CURSOR_PREFIX`` を指定した場合には、" -"``GRN_CURSOR_LT`` は無視されます。) ``GRN_CURSOR_BY_ID`` を指定するとID順に" -"レコードを取り出します。(下記 ``GRN_CURSOR_PREFIX`` を指定した場合には、" -"``GRN_CURSOR_BY_ID`` は無視されます。) ``GRN_OBJ_TABLE_PAT_KEY`` を指定した" -"tableについては、``GRN_CURSOR_BY_KEY`` を指定するとkey順にレコードを取り出し" -"ます。( ``GRN_OBJ_TABLE_HASH_KEY`` , ``GRN_OBJ_TABLE_NO_KEY`` を指定したテー" -"ブルでは ``GRN_CURSOR_BY_KEY`` は無視されます。) ``GRN_CURSOR_PREFIX`` を指" -"定すると、 ``GRN_OBJ_TABLE_PAT_KEY`` を指定したテーブルに関する下記のレコード" -"を取り出すカーソルが作成されます。maxがNULLの場合には、keyがminと前方一致する" -"レコードを取り出します。max_sizeパラメータは無視されます。 maxとmax_sizeが指" -"定され、かつ、テーブルのkeyがShortText型である場合、maxとcommon prefix search" -"を行い、common prefixがmin_sizeバイト以上のレコードを取り出します。minは無視" -"されます。 maxとmax_sizeが指定され、かつ、テーブルのkeyが固定長型の場合、max" -"とPAT木上で近い位置にあるノードから順番にレコードを取り出します。ただし、key" -"のパトリシア木で、min_sizeバイト未満のビットに対するノードで、maxと異なった方" -"向にあるノードに対応するレコードについては取り出しません。PAT木上で位置が近い" -"こととkeyの値が近いことは同一ではありません。この場合、maxで与えられるポイン" -"タが指す値は、対象テーブルのkeyサイズと同じか超える幅である必要があります。" -"minは無視されます。 ``GRN_CURSOR_BY_ID`` / ``GRN_CURSOR_BY_KEY`` / " -"``GRN_CURSOR_PREFIX`` の3フラグは、同時に指定することができません。 " -"``GRN_OBJ_TABLE_PAT_KEY`` を指定して作ったテーブルで、``GRN_CURSOR_PREFIX`` " -"と ``GRN_CURSOR_RK`` を指定すると、半角小文字のアルファベット文字列から、それ" -"を旧JIS X 4063:2000規格に従って全角カタカナに変換した文字列に前方一致する値を" -"keyとするレコードを取り出します。``GRN_ENC_UTF8`` のみをサポートしています。" -"``GRN_CURSOR_ASCENDING`` / ``GRN_CURSOR_DESCENDING`` は無効であり、レコードを" -"key値の昇降順で取り出すことはできません。" -msgstr "" -"``GRN_CURSOR_ASCENDING`` を指定すると昇順にレコードを取り出します。 " -"``GRN_CURSOR_DESCENDING`` を指定すると降順にレコードを取り出します。(下記 " -"``GRN_CURSOR_PREFIX`` を指定し、keyが近いレコードを取得する場合、もしくは、" -"common prefix searchを行う場合には、``GRN_CURSOR_ASCENDING`` / " -"``GRN_CURSOR_DESCENDING`` は無視されます。) ``GRN_CURSOR_GT`` を指定すると" -"minに一致したkeyをcursorの範囲に含みません。(minがNULLの場合もしくは、下記 " -"``GRN_CURSOR_PREFIX`` を指定し、keyが近いレコードを取得する場合、もしくは、" -"common prefix searchを行う場合には、``GRN_CURSOR_GT`` は無視されます。) " -"``GRN_CURSOR_LT`` を指定するとmaxに一致したkeyをcursorの範囲に含みません。" -"(maxがNULLの場合もしくは、下記 ``GRN_CURSOR_PREFIX`` を指定した場合には、" -"``GRN_CURSOR_LT`` は無視されます。) ``GRN_CURSOR_BY_ID`` を指定するとID順に" -"レコードを取り出します。(下記 ``GRN_CURSOR_PREFIX`` を指定した場合には、" -"``GRN_CURSOR_BY_ID`` は無視されます。) ``GRN_OBJ_TABLE_PAT_KEY`` を指定した" -"tableについては、``GRN_CURSOR_BY_KEY`` を指定するとkey順にレコードを取り出し" -"ます。( ``GRN_OBJ_TABLE_HASH_KEY`` , ``GRN_OBJ_TABLE_NO_KEY`` を指定したテー" -"ブルでは ``GRN_CURSOR_BY_KEY`` は無視されます。) ``GRN_CURSOR_PREFIX`` を指" -"定すると、 ``GRN_OBJ_TABLE_PAT_KEY`` を指定したテーブルに関する下記のレコード" -"を取り出すカーソルが作成されます。maxがNULLの場合には、keyがminと前方一致する" -"レコードを取り出します。max_sizeパラメータは無視されます。 maxとmax_sizeが指" -"定され、かつ、テーブルのkeyがShortText型である場合、maxとcommon prefix search" -"を行い、common prefixがmin_sizeバイト以上のレコードを取り出します。minは無視" -"されます。 maxとmax_sizeが指定され、かつ、テーブルのkeyが固定長型の場合、max" -"とPAT木上で近い位置にあるノードから順番にレコードを取り出します。ただし、key" -"のパトリシア木で、min_sizeバイト未満のビットに対するノードで、maxと異なった方" -"向にあるノードに対応するレコードについては取り出しません。PAT木上で位置が近い" -"こととkeyの値が近いことは同一ではありません。この場合、maxで与えられるポイン" -"タが指す値は、対象テーブルのkeyサイズと同じか超える幅である必要があります。" -"minは無視されます。 ``GRN_CURSOR_BY_ID`` / ``GRN_CURSOR_BY_KEY`` / " -"``GRN_CURSOR_PREFIX`` の3フラグは、同時に指定することができません。 " -"``GRN_OBJ_TABLE_PAT_KEY`` を指定して作ったテーブルで、``GRN_CURSOR_PREFIX`` " -"と ``GRN_CURSOR_RK`` を指定すると、半角小文字のアルファベット文字列から、それ" -"を旧JIS X 4063:2000規格に従って全角カタカナに変換した文字列に前方一致する値を" -"keyとするレコードを取り出します。``GRN_ENC_UTF8`` のみをサポートしています。" -"``GRN_CURSOR_ASCENDING`` / ``GRN_CURSOR_DESCENDING`` は無効であり、レコードを" -"key値の昇降順で取り出すことはできません。" - -msgid "``GRN_CURSOR_ASCENDING`` を指定すると昇順にレコードを取り出します。" -msgstr "``GRN_CURSOR_ASCENDING`` を指定すると昇順にレコードを取り出します。" - -msgid "" -"``GRN_CURSOR_DESCENDING`` を指定すると降順にレコードを取り出します。(下記 " -"``GRN_CURSOR_PREFIX`` を指定し、keyが近いレコードを取得する場合、もしくは、" -"common prefix searchを行う場合には、``GRN_CURSOR_ASCENDING`` / " -"``GRN_CURSOR_DESCENDING`` は無視されます。)" -msgstr "" -"``GRN_CURSOR_DESCENDING`` を指定すると降順にレコードを取り出します。(下記 " -"``GRN_CURSOR_PREFIX`` を指定し、keyが近いレコードを取得する場合、もしくは、" -"common prefix searchを行う場合には、``GRN_CURSOR_ASCENDING`` / " -"``GRN_CURSOR_DESCENDING`` は無視されます。)" - -msgid "" -"``GRN_CURSOR_GT`` を指定するとminに一致したkeyをcursorの範囲に含みません。" -"(minがNULLの場合もしくは、下記 ``GRN_CURSOR_PREFIX`` を指定し、keyが近いレ" -"コードを取得する場合、もしくは、common prefix searchを行う場合には、" -"``GRN_CURSOR_GT`` は無視されます。)" -msgstr "" -"``GRN_CURSOR_GT`` を指定するとminに一致したkeyをcursorの範囲に含みません。" -"(minがNULLの場合もしくは、下記 ``GRN_CURSOR_PREFIX`` を指定し、keyが近いレ" -"コードを取得する場合、もしくは、common prefix searchを行う場合には、" -"``GRN_CURSOR_GT`` は無視されます。)" - -msgid "" -"``GRN_CURSOR_LT`` を指定するとmaxに一致したkeyをcursorの範囲に含みません。" -"(maxがNULLの場合もしくは、下記 ``GRN_CURSOR_PREFIX`` を指定した場合には、" -"``GRN_CURSOR_LT`` は無視されます。)" -msgstr "" -"``GRN_CURSOR_LT`` を指定するとmaxに一致したkeyをcursorの範囲に含みません。" -"(maxがNULLの場合もしくは、下記 ``GRN_CURSOR_PREFIX`` を指定した場合には、" -"``GRN_CURSOR_LT`` は無視されます。)" - -msgid "" -"``GRN_CURSOR_BY_ID`` を指定するとID順にレコードを取り出します。(下記 " -"``GRN_CURSOR_PREFIX`` を指定した場合には、``GRN_CURSOR_BY_ID`` は無視されま" -"す。) ``GRN_OBJ_TABLE_PAT_KEY`` を指定したtableについては、" -"``GRN_CURSOR_BY_KEY`` を指定するとkey順にレコードを取り出します。" -"( ``GRN_OBJ_TABLE_HASH_KEY`` , ``GRN_OBJ_TABLE_NO_KEY`` を指定したテーブルで" -"は ``GRN_CURSOR_BY_KEY`` は無視されます。)" -msgstr "" -"``GRN_CURSOR_BY_ID`` を指定するとID順にレコードを取り出します。(下記 " -"``GRN_CURSOR_PREFIX`` を指定した場合には、``GRN_CURSOR_BY_ID`` は無視されま" -"す。) ``GRN_OBJ_TABLE_PAT_KEY`` を指定したtableについては、" -"``GRN_CURSOR_BY_KEY`` を指定するとkey順にレコードを取り出します。" -"( ``GRN_OBJ_TABLE_HASH_KEY`` , ``GRN_OBJ_TABLE_NO_KEY`` を指定したテーブルで" -"は ``GRN_CURSOR_BY_KEY`` は無視されます。)" - -msgid "" -"``GRN_CURSOR_PREFIX`` を指定すると、 ``GRN_OBJ_TABLE_PAT_KEY`` を指定したテー" -"ブルに関する下記のレコードを取り出すカーソルが作成されます。maxがNULLの場合に" -"は、keyがminと前方一致するレコードを取り出します。max_sizeパラメータは無視さ" -"れます。" -msgstr "" -"``GRN_CURSOR_PREFIX`` を指定すると、 ``GRN_OBJ_TABLE_PAT_KEY`` を指定したテー" -"ブルに関する下記のレコードを取り出すカーソルが作成されます。maxがNULLの場合に" -"は、keyがminと前方一致するレコードを取り出します。max_sizeパラメータは無視さ" -"れます。" - -msgid "" -"maxとmax_sizeが指定され、かつ、テーブルのkeyがShortText型である場合、maxと" -"common prefix searchを行い、common prefixがmin_sizeバイト以上のレコードを取り" -"出します。minは無視されます。" -msgstr "" -"maxとmax_sizeが指定され、かつ、テーブルのkeyがShortText型である場合、maxと" -"common prefix searchを行い、common prefixがmin_sizeバイト以上のレコードを取り" -"出します。minは無視されます。" - -msgid "" -"maxとmax_sizeが指定され、かつ、テーブルのkeyが固定長型の場合、maxとPAT木上で" -"近い位置にあるノードから順番にレコードを取り出します。ただし、keyのパトリシア" -"木で、min_sizeバイト未満のビットに対するノードで、maxと異なった方向にあるノー" -"ドに対応するレコードについては取り出しません。PAT木上で位置が近いこととkeyの" -"値が近いことは同一ではありません。この場合、maxで与えられるポインタが指す値" -"は、対象テーブルのkeyサイズと同じか超える幅である必要があります。minは無視さ" -"れます。" -msgstr "" -"maxとmax_sizeが指定され、かつ、テーブルのkeyが固定長型の場合、maxとPAT木上で" -"近い位置にあるノードから順番にレコードを取り出します。ただし、keyのパトリシア" -"木で、min_sizeバイト未満のビットに対するノードで、maxと異なった方向にあるノー" -"ドに対応するレコードについては取り出しません。PAT木上で位置が近いこととkeyの" -"値が近いことは同一ではありません。この場合、maxで与えられるポインタが指す値" -"は、対象テーブルのkeyサイズと同じか超える幅である必要があります。minは無視さ" -"れます。" - -msgid "" -"``GRN_CURSOR_BY_ID`` / ``GRN_CURSOR_BY_KEY`` / ``GRN_CURSOR_PREFIX`` の3フラ" -"グは、同時に指定することができません。" -msgstr "" -"``GRN_CURSOR_BY_ID`` / ``GRN_CURSOR_BY_KEY`` / ``GRN_CURSOR_PREFIX`` の3フラ" -"グは、同時に指定することができません。" - -msgid "" -"``GRN_OBJ_TABLE_PAT_KEY`` を指定して作ったテーブルで、``GRN_CURSOR_PREFIX`` " -"と ``GRN_CURSOR_RK`` を指定すると、半角小文字のアルファベット文字列から、それ" -"を旧JIS X 4063:2000規格に従って全角カタカナに変換した文字列に前方一致する値を" -"keyとするレコードを取り出します。``GRN_ENC_UTF8`` のみをサポートしています。" -"``GRN_CURSOR_ASCENDING`` / ``GRN_CURSOR_DESCENDING`` は無効であり、レコードを" -"key値の昇降順で取り出すことはできません。" -msgstr "" -"``GRN_OBJ_TABLE_PAT_KEY`` を指定して作ったテーブルで、``GRN_CURSOR_PREFIX`` " -"と ``GRN_CURSOR_RK`` を指定すると、半角小文字のアルファベット文字列から、それ" -"を旧JIS X 4063:2000規格に従って全角カタカナに変換した文字列に前方一致する値を" -"keyとするレコードを取り出します。``GRN_ENC_UTF8`` のみをサポートしています。" -"``GRN_CURSOR_ASCENDING`` / ``GRN_CURSOR_DESCENDING`` は無効であり、レコードを" -"key値の昇降順で取り出すことはできません。" - -msgid "" -"該当する範囲のレコードのうち、(0ベースで)offset番目からレコードを取り出しま" -"す。 ``GRN_CURSOR_PREFIX`` を指定したときは負の数を指定することはできませ" -"ん。" -msgstr "" -"該当する範囲のレコードのうち、(0ベースで)offset番目からレコードを取り出しま" -"す。 ``GRN_CURSOR_PREFIX`` を指定したときは負の数を指定することはできませ" -"ん。" - -msgid "" -"該当する範囲のレコードのうち、(0ベースで)offset番目からレコードを取り出しま" -"す。" -msgstr "" -"該当する範囲のレコードのうち、(0ベースで)offset番目からレコードを取り出しま" -"す。" - -msgid "" -"``GRN_CURSOR_PREFIX`` を指定したときは負の数を指定することはできません。" -msgstr "" -"``GRN_CURSOR_PREFIX`` を指定したときは負の数を指定することはできません。" - -msgid "" -"該当する範囲のレコードのうち、limit件のみを取り出します。-1が指定された場合" -"は、全件が指定されたものとみなします。 ``GRN_CURSOR_PREFIX`` を指定したとき" -"は-1より小さい負の数を指定することはできません。" -msgstr "" -"該当する範囲のレコードのうち、limit件のみを取り出します。-1が指定された場合" -"は、全件が指定されたものとみなします。 ``GRN_CURSOR_PREFIX`` を指定したとき" -"は-1より小さい負の数を指定することはできません。" - -msgid "" -"該当する範囲のレコードのうち、limit件のみを取り出します。-1が指定された場合" -"は、全件が指定されたものとみなします。" -msgstr "" -"該当する範囲のレコードのうち、limit件のみを取り出します。-1が指定された場合" -"は、全件が指定されたものとみなします。" - -msgid "" -"``GRN_CURSOR_PREFIX`` を指定したときは-1より小さい負の数を指定することはでき" -"ません。" -msgstr "" -"``GRN_CURSOR_PREFIX`` を指定したときは-1より小さい負の数を指定することはでき" -"ません。" - -msgid ":c:func:`grn_table_cursor_open` で生成したcursorを解放します。" -msgstr ":c:func:`grn_table_cursor_open` で生成したcursorを解放します。" - -msgid "" -"cursorのカレントレコードを一件進めてそのIDを返します。cursorの対象範囲の末尾" -"に達すると ``GRN_ID_NIL`` を返します。" -msgstr "" -"cursorのカレントレコードを一件進めてそのIDを返します。cursorの対象範囲の末尾" -"に達すると ``GRN_ID_NIL`` を返します。" - -msgid "" -"cursorのカレントレコードのkeyをkeyパラメータにセットし、その長さを返します。" -msgstr "" -"cursorのカレントレコードのkeyをkeyパラメータにセットし、その長さを返します。" - -msgid "カレントレコードのkeyへのポインタがセットされます。" -msgstr "カレントレコードのkeyへのポインタがセットされます。" - -msgid "" -"cursorパラメータのカレントレコードのvalueをvalueパラメータにセットし、その長" -"さを返します。" -msgstr "" -"cursorパラメータのカレントレコードのvalueをvalueパラメータにセットし、その長" -"さを返します。" - -msgid "カレントレコードのvalueへのポインタがセットされます。" -msgstr "カレントレコードのvalueへのポインタがセットされます。" - -msgid "" -"cursorのカレントレコードのvalueを引数の内容に置き換えます。cursorのカレントレ" -"コードが存在しない場合は ``GRN_INVALID_ARGUMENT`` を返します。" -msgstr "" -"cursorのカレントレコードのvalueを引数の内容に置き換えます。cursorのカレントレ" -"コードが存在しない場合は ``GRN_INVALID_ARGUMENT`` を返します。" - -msgid "新しいvalueの値を指定します。" -msgstr "新しいvalueの値を指定します。" - -msgid ":c:func:`grn_obj_set_value()` のflagsと同様の値を指定できます。" -msgstr ":c:func:`grn_obj_set_value()` のflagsと同様の値を指定できます。" - -msgid "" -"cursorのカレントレコードを削除します。cursorのカレントレコードが存在しない場" -"合は ``GRN_INVALID_ARGUMENT`` を返します。" -msgstr "" -"cursorのカレントレコードを削除します。cursorのカレントレコードが存在しない場" -"合は ``GRN_INVALID_ARGUMENT`` を返します。" - -msgid "cursorが属するtableを返します。" -msgstr "cursorが属するtableを返します。" - -msgid "``grn_type``" -msgstr "``grn_type``" - -msgid "nameに対応する新たなtype（型）をdbに定義します。" -msgstr "nameに対応する新たなtype（型）をdbに定義します。" - -msgid "作成するtypeの名前を指定します。" -msgstr "作成するtypeの名前を指定します。" - -msgid "" -"``GRN_OBJ_KEY_VAR_SIZE``, ``GRN_OBJ_KEY_FLOAT``, ``GRN_OBJ_KEY_INT``, " -"``GRN_OBJ_KEY_UINT`` のいずれかを指定します。" -msgstr "" -"``GRN_OBJ_KEY_VAR_SIZE``, ``GRN_OBJ_KEY_FLOAT``, ``GRN_OBJ_KEY_INT``, " -"``GRN_OBJ_KEY_UINT`` のいずれかを指定します。" - -msgid "" -"``GRN_OBJ_KEY_VAR_SIZE`` の場合は最大長、それ以外の場合は長さ（単位:byte）を" -"指定します。" -msgstr "" -"``GRN_OBJ_KEY_VAR_SIZE`` の場合は最大長、それ以外の場合は長さ（単位:byte）を" -"指定します。" - -msgid "``grn_user_data``" -msgstr "``grn_user_data``" - -msgid "" -"objectに登録できるユーザデータへのポインタを返します。table, column, proc, " -"exprのみ使用可能です。" -msgstr "" -"objectに登録できるユーザデータへのポインタを返します。table, column, proc, " -"exprのみ使用可能です。" - -# ff055c16fb884cb1a3988e064875e005 -msgid "Overview" -msgstr "" - -# 4155eeddd9594eadaa514fb172542b79 -msgid "" -"You can use Groonga as a library. You need to use the following APIs to " -"initialize and finalize Groonga." -msgstr "" - -# 84769298f391417391b74ad3f4a2dbec -msgid "" -":c:func:`grn_init()` initializes Groonga. In contrast, :c:func:`grn_fin()` " -"finalizes Groonga." -msgstr "" - -# 5cd46a4cf8014615982fef78d2e820b3 -msgid "" -"You must call :c:func:`grn_init()` only once before you use APIs which are " -"provided by Groonga. You must call :c:func:`grn_fin()` only once after you " -"finish to use APIs which are provided by Groonga." -msgstr "" - -msgid "Here is an example that uses Groonga as a full-text search library." -msgstr "" - -# 4bcc12e9ef4f433299af2176771166ba -msgid "" -"``grn_init()`` initializes resources that are used by Groonga. You must call " -"it just once before you call other Groonga APIs." -msgstr "" - -# 92760cf9b36f41a2bb8b3a3b7efefef2 -msgid "" -"``grn_fin()`` releases resources that are used by Groonga. You can't call " -"other Groonga APIs after you call ``grn_fin()``." -msgstr "" - -msgid "Plugin" -msgstr "Plugin" - -msgid "" -"Groonga supports plugin. You can create a new plugin with the following API." -msgstr "" -"Groonga supports plugin. You can create a new plugin with the following API." - -msgid "" -"TOOD: Describe about how to create the minimum plugin here or create a " -"tutorial about it." -msgstr "" -"TOOD: Describe about how to create the minimum plugin here or create a " -"tutorial about it." - -msgid "" -"GRN_PLUGIN_MALLOC() allocates `size` bytes and returns a pointer to the " -"allocated memory space. Note that the memory space is associated with `ctx`." -msgstr "" - -msgid "" -"GRN_PLUGIN_REALLOC() resizes the memory space pointed to by `ptr` or " -"allocates a new memory space of `size` bytes. GRN_PLUGIN_REALLOC() returns a " -"pointer to the memory space. The contents is unchanged or copied from the " -"old memory space to the new memory space." -msgstr "" - -msgid "" -"GRN_PLUGIN_FREE() frees a memory space allocated by GRN_PLUGIN_MALLOC() or " -"GRN_PLUGIN_REALLOC(). This means that `ptr` must be a pointer returned by " -"GRN_PLUGIN_MALLOC() or GRN_PLUGIN_REALLOC()." -msgstr "" - -msgid "" -"GRN_PLUGIN_LOG() reports a log of `level`. Its error message is generated " -"from the varying number of arguments, in which the first one is the format " -"string and the rest are its arguments. See grn_log_level in \"groonga.h\" " -"for more details of `level`." -msgstr "" - -msgid "" -"GRN_PLUGIN_ERROR() reports an error of `error_code`. Its error message is " -"generated from the varying number of arguments, in which the first one is " -"the format string and the rest are its arguments. See grn_rc in \"groonga.h" -"\" for more details of `error_code`." -msgstr "" - -msgid "" -"grn_plugin_mutex is available to make a critical section. See the following " -"functions." -msgstr "" - -msgid "" -"grn_plugin_mutex_open() returns a pointer to a new object of " -"grn_plugin_mutex. Memory for the new object is obtained with " -"GRN_PLUGIN_MALLOC(). grn_plugin_mutex_open() returns NULL if sufficient " -"memory is not available." -msgstr "" - -msgid "" -"grn_plugin_mutex_close() finalizes an object of grn_plugin_mutex and then " -"frees memory allocated for that object." -msgstr "" - -msgid "" -"grn_plugin_mutex_lock() locks a mutex object. If the object is already " -"locked, the calling thread waits until the object will be unlocked." -msgstr "" - -msgid "" -"grn_plugin_mutex_unlock() unlocks a mutex object. grn_plugin_mutex_unlock() " -"should not be called for an unlocked object." -msgstr "" - -msgid "" -"grn_plugin_proc_alloc() allocates a `grn_obj` object. You can use it in " -"function that is registered as GRN_PROC_FUNCTION." -msgstr "" - -msgid "" -"It gets a variable value from `grn_user_data` by specifying the variable " -"name." -msgstr "" - -msgid "The variable name." -msgstr "" - -msgid "" -"The number of bytes of name. If `name_size` is negative, `name` must be NUL-" -"terminated. `name_size` is computed by `strlen(name)` for the case." -msgstr "" - -msgid "A variable value on success, NULL otherwise." -msgstr "" - -msgid "" -"It gets a variable value from `grn_user_data` by specifying the offset " -"position of the variable." -msgstr "" - -msgid "The offset position of the variable." -msgstr "" - -msgid "" -"grn_plugin_win32_base_dir() returns the groonga install directory. The " -"install directory is computed from the directory that has `groonga.dll`. You " -"can use the directory to generate install directory aware path. It only " -"works on Windows. It returns `NULL` on other platforms." -msgstr "" - -msgid "" -"grn_plugin_charlen() returns the length (#bytes) of the first character in " -"the string specified by `str_ptr` and `str_length`. If the starting bytes " -"are invalid as a character, grn_plugin_charlen() returns 0. See grn_encoding " -"in \"groonga.h\" for more details of `encoding`." -msgstr "" - -msgid "" -"grn_plugin_isspace() returns the length (#bytes) of the first character in " -"the string specified by `str_ptr` and `str_length` if it is a space " -"character. Otherwise, grn_plugin_isspace() returns 0." -msgstr "" - -msgid "It initializes a `grn_expr_var`." -msgstr "" - -msgid "The pointer of `grn_expr_var` object to be initialized." -msgstr "" - -msgid "The name of `grn_expr_var` object to be initialized." -msgstr "" - -msgid "It creates a command." -msgstr "" - -msgid "The `proc` name of the command to be created." -msgstr "" - -msgid "The function name to be called by the created command." -msgstr "" - -msgid "The number of the variables of the command to create." -msgstr "" - -msgid "The pointer of initialized `grn_expr_var` object." -msgstr "" - -msgid "" -"The created command object if it creates a command successfully, `NULL` " -"otherwise. See `ctx` for error details." -msgstr "" - -msgid "Cast" -msgstr "Cast" - -msgid "Column" -msgstr "Column" - -msgid "Column is a data store object or an index object for fast search." -msgstr "Column is a data store object or an index object for fast search." - -msgid "A column belongs to a table. Table has zero or more columns." -msgstr "A column belongs to a table. Table has zero or more columns." - -msgid "" -"Both data store column and index column have type. Type of data store column " -"specifies data range. In other words, it is \"value type\". Type of index " -"column specifies set of documents to be indexed. A set of documents is a " -"table in Groonga. In other words, type of index column must be a table." -msgstr "" -"Both data store column and index column have type. Type of data store column " -"specifies data range. In other words, it is \"value type\". Type of index " -"column specifies set of documents to be indexed. A set of documents is a " -"table in Groonga. In other words, type of index column must be a table." - -msgid "Here are data store columns:" -msgstr "Here are data store columns:" - -msgid "Here is an index column:" -msgstr "Here is an index column:" - -msgid "Index column" -msgstr "" - -msgid "TODO" -msgstr "TODO" - -msgid "Usage" -msgstr "Usage" - -msgid "Pseudo column" -msgstr "" - -msgid "名前" -msgstr "名前" - -msgid "疑似カラム" -msgstr "疑似カラム" - -msgid "説明" -msgstr "説明" - -msgid "" -"Groongaのデータベースで作成したテーブルには、いくつかのカラムが自動的に定義さ" -"れます。" -msgstr "" -"Groongaのデータベースで作成したテーブルには、いくつかのカラムが自動的に定義さ" -"れます。" - -msgid "" -"これらのカラムはいずれもアンダースコア('_')で始まる名前が付与されます。定義さ" -"れる疑似カラムは、テーブルの種類によって異なります。" -msgstr "" -"これらのカラムはいずれもアンダースコア('_')で始まる名前が付与されます。定義さ" -"れる疑似カラムは、テーブルの種類によって異なります。" - -msgid "``_id``" -msgstr "``_id``" - -msgid "" -"レコードに付与される一意な番号です。全てのテーブルに定義されます。値の範囲は" -"1〜1073741824の整数で、通常はレコードを追加した順に1ずつ加算されます。_idの値" -"は不変で、レコードが存在する限り変更することはできません。ただし、削除された" -"レコードの_idの値は再利用されます。" -msgstr "" -"レコードに付与される一意な番号です。全てのテーブルに定義されます。値の範囲は" -"1〜1073741824の整数で、通常はレコードを追加した順に1ずつ加算されます。_idの値" -"は不変で、レコードが存在する限り変更することはできません。ただし、削除された" -"レコードの_idの値は再利用されます。" - -msgid "``_key``" -msgstr "``_key``" - -msgid "" -"レコードの主キー値を表します。主キーを持つテーブルのみに定義されます。主キー" -"値はテーブルの中で一意であり、変更することはできません。" -msgstr "" -"レコードの主キー値を表します。主キーを持つテーブルのみに定義されます。主キー" -"値はテーブルの中で一意であり、変更することはできません。" - -msgid "``_value``" -msgstr "``_value``" - -msgid "" -"レコードの値を表します。value_typeを指定したテーブルのみに定義されます。自由" -"に変更可能です。" -msgstr "" -"レコードの値を表します。value_typeを指定したテーブルのみに定義されます。自由" -"に変更可能です。" - -msgid "``_score``" -msgstr "``_score``" - -msgid "" -"各レコードのスコア値を表します。検索結果として生成されたテーブルのみに定義さ" -"れます。" -msgstr "" -"各レコードのスコア値を表します。検索結果として生成されたテーブルのみに定義さ" -"れます。" - -msgid "検索処理を実行する過程で値が設定されますが、自由に変更可能です。" -msgstr "検索処理を実行する過程で値が設定されますが、自由に変更可能です。" - -msgid "``_nsubrecs``" -msgstr "``_nsubrecs``" - -msgid "" -"主キーの値が同一であったレコードの件数を表します。検索結果として生成された" -"テーブルのみに定義されます。グループ化(drilldown)処理を実行すると、グループ化" -"前のテーブルにおいて、グループ化キーの値が同一であったレコードの件数が、グ" -"ループ化処理の結果を格納するテーブルの_nsubrecsに記録されます。" -msgstr "" -"主キーの値が同一であったレコードの件数を表します。検索結果として生成された" -"テーブルのみに定義されます。グループ化(drilldown)処理を実行すると、グループ化" -"前のテーブルにおいて、グループ化キーの値が同一であったレコードの件数が、グ" -"ループ化処理の結果を格納するテーブルの_nsubrecsに記録されます。" - -msgid "Scalar column" -msgstr "" - -msgid "Vector column" -msgstr "Vector column" - -msgid "" -"Vector column is a data store object. It can stores zero or more scalar " -"values. In short, scalar value is a single value such as number and string. " -"See :doc:`scalar` about scalar value details." -msgstr "" -"Vector column is a data store object. It can stores zero or more scalar " -"values. In short, scalar value is a single value such as number and string. " -"See :doc:`scalar` about scalar value details." - -msgid "" -"One of vector column use cases is tags store. You can use a vector column to " -"store tag values." -msgstr "" -"One of vector column use cases is tags store. You can use a vector column to " -"store tag values." - -msgid "" -"You can use vector column as index search target in the same way as scalar " -"column. You can set weight for each element. The element that has one or " -"more weight is matched, the record has more score rather than no weight " -"case. It is a vector column specific feature. Vector column that can store " -"weight is called weight vector column." -msgstr "" -"You can use vector column as index search target in the same way as scalar " -"column. You can set weight for each element. The element that has one or " -"more weight is matched, the record has more score rather than no weight " -"case. It is a vector column specific feature. Vector column that can store " -"weight is called weight vector column." - -msgid "" -"You can also do full text search against each text element. But search score " -"is too high when weight is used. You should use full text search with weight " -"carefully." -msgstr "" -"You can also do full text search against each text element. But search score " -"is too high when weight is used. You should use full text search with weight " -"carefully." - -msgid "There are three vector column types:" -msgstr "There are three vector column types:" - -msgid "Normal vector column" -msgstr "Normal vector column" - -msgid "Reference vector column" -msgstr "Reference vector column" - -msgid "Weight vector column" -msgstr "Weight vector column" - -msgid "This section describes how to use these types." -msgstr "This section describes how to use these types." - -msgid "" -"Normal vector column stores zero or more scalar data. For example, scalar " -"data are number, string and so on." -msgstr "" -"Normal vector column stores zero or more scalar data. For example, scalar " -"data are number, string and so on." - -msgid "" -"A normal vector column can store the same type elements. You can't mix " -"types. For example, you can't store a number and a string in the same normal " -"vector column." -msgstr "" -"A normal vector column can store the same type elements. You can't mix " -"types. For example, you can't store a number and a string in the same normal " -"vector column." - -msgid "" -"Normal vector column is useful when a record has multiple values with a key. " -"Tags are the most popular use case." -msgstr "" -"Normal vector column is useful when a record has multiple values with a key. " -"Tags are the most popular use case." - -msgid "How to create" -msgstr "How to create" - -msgid "" -"Use :doc:`/reference/commands/column_create` command to create a normal " -"vector column. The point is ``COLUMN_VECTOR`` flag:" -msgstr "" -"Use :doc:`/reference/commands/column_create` command to create a normal " -"vector column. The point is ``COLUMN_VECTOR`` flag:" - -msgid "You can set zero or more tags to a bookmark." -msgstr "You can set zero or more tags to a bookmark." - -msgid "How to load" -msgstr "How to load" - -msgid "You can load vector data by JSON array syntax::" -msgstr "You can load vector data by JSON array syntax::" - -msgid "Let's load the following data:" -msgstr "Let's load the following data:" - -msgid "``tags``" -msgstr "``tags``" - -msgid "``http://groonga.org/``" -msgstr "``http://groonga.org/``" - -msgid "``[\"groonga\"]``" -msgstr "``[\"groonga\"]``" - -msgid "``http://mroonga.org/``" -msgstr "``http://mroonga.org/``" - -msgid "``[\"mroonga\", \"mysql\", \"groonga\"]``" -msgstr "``[\"mroonga\", \"mysql\", \"groonga\"]``" - -msgid "``http://ranguba.org/``" -msgstr "``http://ranguba.org/``" - -msgid "``[\"ruby\", \"groonga\"]``" -msgstr "``[\"ruby\", \"groonga\"]``" - -msgid "Here is a command that loads the data:" -msgstr "Here is a command that loads the data:" - -msgid "The loaded data can be outputted as JSON array syntax:" -msgstr "The loaded data can be outputted as JSON array syntax:" - -msgid "How to search" -msgstr "How to search" - -msgid "You need to create an index to search normal vector column:" -msgstr "You need to create an index to search normal vector column:" - -msgid "" -"There are no vector column specific way. You can create an index like a " -"scalar column." -msgstr "" -"There are no vector column specific way. You can create an index like a " -"scalar column." - -msgid "You can search an element in ``tags`` like full text search syntax." -msgstr "You can search an element in ``tags`` like full text search syntax." - -msgid "With :ref:`select-match-columns` and :ref:`select-query`:" -msgstr "With :ref:`select-match-columns` and :ref:`select-query`:" - -msgid "You can also use weight in :ref:`select-match-columns`:" -msgstr "You can also use weight in :ref:`select-match-columns`:" - -msgid "With :ref:`select-filter`:" -msgstr "With :ref:`select-filter`:" - -msgid "" -"Reference vector column is space-efficient if there are many same value " -"elements. Reference vector column keeps reference record IDs not value " -"itself. Record ID is smaller than value itself." -msgstr "" -"Reference vector column is space-efficient if there are many same value " -"elements. Reference vector column keeps reference record IDs not value " -"itself. Record ID is smaller than value itself." - -msgid "" -"Weight vector column is similar to normal vector column. It can store " -"elements. It can also stores weights for them. Weight is degree of " -"importance of the element." -msgstr "" -"Weight vector column is similar to normal vector column. It can store " -"elements. It can also stores weights for them. Weight is degree of " -"importance of the element." - -msgid "" -"Weight is positive integer. ``0`` is the default weight. It means that no " -"weight." -msgstr "" -"Weight is positive integer. ``0`` is the default weight. It means that no " -"weight." - -msgid "" -"If weight is one or larger, search score is increased by the weight. If the " -"weight is ``0``, score is ``1``. If the weight is ``10``, score is ``11`` " -"(``= 1 + 10``)." -msgstr "" -"If weight is one or larger, search score is increased by the weight. If the " -"weight is ``0``, score is ``1``. If the weight is ``10``, score is ``11`` " -"(``= 1 + 10``)." - -msgid "" -"Weight vector column is useful for tuning search score. See also :ref:" -"`select-adjuster`. You can increase search score of specific records." -msgstr "" -"Weight vector column is useful for tuning search score. See also :ref:" -"`select-adjuster`. You can increase search score of specific records." - -msgid "Limitations" -msgstr "Limitations" - -msgid "" -"There are some limitations for now. They will be resolved in the future." -msgstr "" -"There are some limitations for now. They will be resolved in the future." - -msgid "Here are limitations:" -msgstr "Here are limitations:" - -msgid "" -"You need to use string representation for element value on load. For " -"example, you can't use ``29`` for number 29. You need to use ``\"29\"`` for " -"number 29." -msgstr "" -"You need to use string representation for element value on load. For " -"example, you can't use ``29`` for number 29. You need to use ``\"29\"`` for " -"number 29." - -msgid "" -"Use :doc:`/reference/commands/column_create` command to create a weight " -"vector column. The point is ``COLUMN_VECTOR|WITH_WEIGHT`` flags:" -msgstr "" -"Use :doc:`/reference/commands/column_create` command to create a weight " -"vector column. The point is ``COLUMN_VECTOR|WITH_WEIGHT`` flags:" - -msgid "" -"If you don't specify ``WITH_WEIGHT`` flag, it is just a normal vector column." -msgstr "" -"If you don't specify ``WITH_WEIGHT`` flag, it is just a normal vector column." - -msgid "You can set zero or more tags with weight to a bookmark." -msgstr "You can set zero or more tags with weight to a bookmark." - -msgid "You can load vector data by JSON object syntax::" -msgstr "You can load vector data by JSON object syntax::" - -msgid "``{\"groonga\": 100}``" -msgstr "``{\"groonga\": 100}``" - -msgid "``{\"mroonga\": 100, \"mysql\": 50, \"groonga\": 10}``" -msgstr "``{\"mroonga\": 100, \"mysql\": 50, \"groonga\": 10}``" - -msgid "``{\"ruby\": 100, \"groonga\": 50}``" -msgstr "``{\"ruby\": 100, \"groonga\": 50}``" - -msgid "The loaded data can be outputted as JSON object syntax:" -msgstr "The loaded data can be outputted as JSON object syntax:" - -msgid "" -"You need to create an index to search weight vector column. You don't forget " -"to specify ``WITH_WEIGHT`` flag to ``column_create``:" -msgstr "" -"You need to create an index to search weight vector column. You don't forget " -"to specify ``WITH_WEIGHT`` flag to ``column_create``:" - -msgid "" -"There are no weight vector column specific way except ``WITH_WEIGHT`` flag. " -"You can create an index like a scalar column." -msgstr "" -"There are no weight vector column specific way except ``WITH_WEIGHT`` flag. " -"You can create an index like a scalar column." - -msgid "" -"You can also use weight in :ref:`select-match-columns`. The score is ``(1 + " -"weight_in_weight_vector) * weight_in_match_columns``:" -msgstr "" -"You can also use weight in :ref:`select-match-columns`. The score is ``(1 + " -"weight_in_weight_vector) * weight_in_match_columns``:" - -msgid "How to apply just weight" -msgstr "How to apply just weight" - -msgid "" -"You can use weight in weight vector column to just increase search score " -"without changing a set of matched records." -msgstr "" -"You can use weight in weight vector column to just increase search score " -"without changing a set of matched records." - -msgid "Use :ref:`select-adjuster` for the purpose:" -msgstr "Use :ref:`select-adjuster` for the purpose:" - -msgid "" -"The ``select`` command uses ``--filter true``. So all records are matched " -"with score 1. Then it applies ``--adjuster``. The adjuster does the " -"following:" -msgstr "" -"The ``select`` command uses ``--filter true``. So all records are matched " -"with score 1. Then it applies ``--adjuster``. The adjuster does the " -"following:" - -msgid "" -"``tags @ \"mysql\" * 10`` increases score by ``(1 + weight) * 10`` of " -"records that has ``\"mysql\"`` tag." -msgstr "" -"``tags @ \"mysql\" * 10`` increases score by ``(1 + weight) * 10`` of " -"records that has ``\"mysql\"`` tag." - -msgid "" -"``tags @ \"groonga\" * 5`` increases score by ``(1 + weight) * 5`` of " -"records that has ``\"groonga\"`` tag." -msgstr "" -"``tags @ \"groonga\" * 5`` increases score by ``(1 + weight) * 5`` of " -"records that has ``\"groonga\"`` tag." - -msgid "" -"For example, record ``\"http://mroonga.org/\"`` has both ``\"mysql\"`` tag " -"and ``\"groonga\"`` tag. So its score is increased by ``565`` (``= ((1 + 50) " -"* 10) + ((1 + 10) * 5) = (51 * 10) + (11 * 5) = 510 + 55``). The search " -"score is 1 by ``--filter true`` before applying ``--adjuster``. So the final " -"search score is ``566`` (``= 1 + 565``) of record ``\"http://mroonga.org/" -"\"``." -msgstr "" -"For example, record ``\"http://mroonga.org/\"`` has both ``\"mysql\"`` tag " -"and ``\"groonga\"`` tag. So its score is increased by ``565`` (``= ((1 + 50) " -"* 10) + ((1 + 10) * 5) = (51 * 10) + (11 * 5) = 510 + 55``). The search " -"score is 1 by ``--filter true`` before applying ``--adjuster``. So the final " -"search score is ``566`` (``= 1 + 565``) of record ``\"http://mroonga.org/" -"\"``." - -msgid "Command" -msgstr "Command" - -msgid "" -"Command is the most important processing unit in query API. You request a " -"processing to groonga by a command." -msgstr "" -"Command is the most important processing unit in query API. You request a " -"processing to groonga by a command." - -msgid "This section describes about command and built-in commands." -msgstr "This section describes about command and built-in commands." - -msgid "コマンドバージョン" -msgstr "コマンドバージョン" - -msgid "概要" -msgstr "概要" - -msgid "" -"Groonga1.1からコマンドバージョンという概念が導入されます。コマンドバージョン" -"は、selectやloadなどのGroongaのコマンドの仕様の互換性を表します。Groongaパッ" -"ケージのバージョンが新しくなったとしても、同一のコマンドバージョンが使用可能" -"であるなら、すべてのコマンドについて互換性が保証されます。コマンドバージョン" -"が異なれば、同じ名前のコマンドであっても、動作に互換性がない可能性がありま" -"す。" -msgstr "" -"Groonga1.1からコマンドバージョンという概念が導入されます。コマンドバージョン" -"は、selectやloadなどのGroongaのコマンドの仕様の互換性を表します。Groongaパッ" -"ケージのバージョンが新しくなったとしても、同一のコマンドバージョンが使用可能" -"であるなら、すべてのコマンドについて互換性が保証されます。コマンドバージョン" -"が異なれば、同じ名前のコマンドであっても、動作に互換性がない可能性がありま" -"す。" - -msgid "" -"あるバージョンのGroongaは、二つのコマンドバージョンを同時にサポートするように" -"なります。 使用するコマンドバージョンは、groongaを起動する際のコマンドライン" -"オプションないしコンフィグファイルにdefault-commnad-versionパラメータを与える" -"ことによって指定できます。また、個々のコマンドを実行する際に、command_version" -"パラメータを与えることによっても指定することができます。" -msgstr "" -"あるバージョンのGroongaは、二つのコマンドバージョンを同時にサポートするように" -"なります。 使用するコマンドバージョンは、groongaを起動する際のコマンドライン" -"オプションないしコンフィグファイルにdefault-commnad-versionパラメータを与える" -"ことによって指定できます。また、個々のコマンドを実行する際に、command_version" -"パラメータを与えることによっても指定することができます。" - -msgid "" -"コマンドバージョンは1からはじまり、更新されるたびに1ずつ大きくなります。現状" -"のGroongaのコマンドの仕様はcommand-version 1という扱いになります。次回提供す" -"るGroongaは、command-version 1とcommand-version 2の二つをサポートすることにな" -"ります。" -msgstr "" -"コマンドバージョンは1からはじまり、更新されるたびに1ずつ大きくなります。現状" -"のGroongaのコマンドの仕様はcommand-version 1という扱いになります。次回提供す" -"るGroongaは、command-version 1とcommand-version 2の二つをサポートすることにな" -"ります。" - -msgid "バージョンの位置づけ" -msgstr "バージョンの位置づけ" - -msgid "" -"あるバージョンのGroongaにおいてサポートされるコマンドバージョンは、develop, " -"stable,deprecatedのいずれかの位置づけとなります。" -msgstr "" -"あるバージョンのGroongaにおいてサポートされるコマンドバージョンは、develop, " -"stable,deprecatedのいずれかの位置づけとなります。" - -msgid "develop" -msgstr "develop" - -msgid "まだ開発中であり、仕様が変更される可能性があります。" -msgstr "まだ開発中であり、仕様が変更される可能性があります。" - -msgid "stable" -msgstr "stable" - -msgid "" -"使用可能であり仕様も安定しています。その時点で使用することが推奨されます。" -msgstr "" -"使用可能であり仕様も安定しています。その時点で使用することが推奨されます。" - -msgid "deprecated" -msgstr "deprecated" - -msgid "" -"使用可能であり仕様も安定していますが、廃止予定であり使用が推奨されません。" -msgstr "" -"使用可能であり仕様も安定していますが、廃止予定であり使用が推奨されません。" - -msgid "" -"あるバージョンのGroongaがサポートする二つのコマンドバージョンのうち、いずれか" -"一つが必ずstableの位置づけとなります。残りの一つは、developないしdeprecatedと" -"なります。" -msgstr "" -"あるバージョンのGroongaがサポートする二つのコマンドバージョンのうち、いずれか" -"一つが必ずstableの位置づけとなります。残りの一つは、developないしdeprecatedと" -"なります。" - -msgid "" -"たとえば下記のようにGroongaのサポートするコマンドバージョンは推移します。::" -msgstr "" -"たとえば下記のようにGroongaのサポートするコマンドバージョンは推移します。::" - -msgid "" -"あるコマンドバージョンははじめにdevelop扱いとしてリリースされ、やがてstableに" -"移行します。 その後二世代経過するとそのコマンドバージョンはdeprecated扱いとな" -"ります。さらに次のコマンドバージョンがリリースされると、deprecatedだったコマ" -"ンドバージョンはサポート対象外となります。" -msgstr "" -"あるコマンドバージョンははじめにdevelop扱いとしてリリースされ、やがてstableに" -"移行します。 その後二世代経過するとそのコマンドバージョンはdeprecated扱いとな" -"ります。さらに次のコマンドバージョンがリリースされると、deprecatedだったコマ" -"ンドバージョンはサポート対象外となります。" - -msgid "" -"default-commnad-versionパラメータやcommand_versionパラメータを指定せずに" -"groongaコマンドを実行した際には、その時点でstableであるコマンドバージョンが指" -"定されたものとみなします。" -msgstr "" -"default-commnad-versionパラメータやcommand_versionパラメータを指定せずに" -"groongaコマンドを実行した際には、その時点でstableであるコマンドバージョンが指" -"定されたものとみなします。" - -msgid "" -"groongaプロセス起動時に、default-command-versionパラメータにstable扱いでない" -"コマンドバージョンを指定した場合には、警告メッセージがログファイルに出力され" -"ます。また、サポート範囲外のコマンドバージョンを指定した場合にはエラーとな" -"り、プロセスは速やかに停止します。" -msgstr "" -"groongaプロセス起動時に、default-command-versionパラメータにstable扱いでない" -"コマンドバージョンを指定した場合には、警告メッセージがログファイルに出力され" -"ます。また、サポート範囲外のコマンドバージョンを指定した場合にはエラーとな" -"り、プロセスは速やかに停止します。" - -msgid "コマンドバージョンの指定方法" -msgstr "コマンドバージョンの指定方法" - -msgid "" -"コマンドバージョンの指定方法はgroonga実行モジュールの引数として指定する方法と" -"各コマンドの引数として指定する方法があります。" -msgstr "" -"コマンドバージョンの指定方法はgroonga実行モジュールの引数として指定する方法と" -"各コマンドの引数として指定する方法があります。" - -msgid "default-command-versionパラメータ" -msgstr "default-command-versionパラメータ" - -msgid "" -"groonga実行モジュールの引数としてdefault-command-versionパラメータを指定でき" -"ます。 (configファイルの中に指定することも可能です)" -msgstr "" -"groonga実行モジュールの引数としてdefault-command-versionパラメータを指定でき" -"ます。 (configファイルの中に指定することも可能です)" - -msgid "実行例::" -msgstr "実行例::" - -msgid "" -"そのプロセスで実行するすべてのコマンドについて、デフォルトのコマンドバージョ" -"ンとして指定されたバージョンを使用します。指定されたコマンドバージョンが" -"stableであった場合にはなんのメッセージも表示されずそのまま起動します。指定さ" -"れたコマンドバージョンがdevelopあるいはdeprecatedであった場合には、groonga." -"logファイルに警告メッセージを出力します。指定されたコマンドバージョンがサポー" -"ト対象外であった場合には標準エラー出力にエラーメッセージを出力し、プロセスは" -"速やかに終了します。" -msgstr "" -"そのプロセスで実行するすべてのコマンドについて、デフォルトのコマンドバージョ" -"ンとして指定されたバージョンを使用します。指定されたコマンドバージョンが" -"stableであった場合にはなんのメッセージも表示されずそのまま起動します。指定さ" -"れたコマンドバージョンがdevelopあるいはdeprecatedであった場合には、groonga." -"logファイルに警告メッセージを出力します。指定されたコマンドバージョンがサポー" -"ト対象外であった場合には標準エラー出力にエラーメッセージを出力し、プロセスは" -"速やかに終了します。" - -msgid "command_versionパラメータ" -msgstr "command_versionパラメータ" - -msgid "" -"select,loadなどのすべてのgroongaコマンドにcommand_versionが指定できます。" -msgstr "" -"select,loadなどのすべてのgroongaコマンドにcommand_versionが指定できます。" - -msgid "" -"指定されたコマンドバージョンでコマンドを実行します。指定されたコマンドバー" -"ジョンがサポート対象外であった場合にはエラーが返されます。command-versionが指" -"定されなかった場合は、当該プロセス起動時にdefault-command-versionに指定した値" -"が指定されたものとみなします。" -msgstr "" -"指定されたコマンドバージョンでコマンドを実行します。指定されたコマンドバー" -"ジョンがサポート対象外であった場合にはエラーが返されます。command-versionが指" -"定されなかった場合は、当該プロセス起動時にdefault-command-versionに指定した値" -"が指定されたものとみなします。" - -msgid "Output format" -msgstr "Output format" - -msgid "Commands output their result as JSON, MessagePack, XML or TSV format." -msgstr "Commands output their result as JSON, MessagePack, XML or TSV format." - -msgid "" -"JSON and MessagePack output have the same structure. XML and TSV are their " -"original structure." -msgstr "" -"JSON and MessagePack output have the same structure. XML and TSV are their " -"original structure." - -msgid "" -"JSON or MessagePack is recommend format. XML is useful for visual result " -"check. TSV is just for special use. Normally you doesn't need to use TSV." -msgstr "" -"JSON or MessagePack is recommend format. XML is useful for visual result " -"check. TSV is just for special use. Normally you doesn't need to use TSV." - -msgid "JSON and MessagePack" -msgstr "JSON and MessagePack" - -msgid "" -"This secsion describes the structure of command result on JSON and " -"MessagePack format. JSON is used to show structure because MessagePack is " -"binary format. Binary format isn't proper for documenataion." -msgstr "" -"This secsion describes the structure of command result on JSON and " -"MessagePack format. JSON is used to show structure because MessagePack is " -"binary format. Binary format isn't proper for documenataion." - -msgid "JSON and MessagePack uses the following structure::" -msgstr "JSON and MessagePack uses the following structure::" - -msgid "For example::" -msgstr "For example::" - -msgid "In the example, the following part is ``HEADER``::" -msgstr "In the example, the following part is ``HEADER``::" - -msgid "The following part is ``BODY``::" -msgstr "The following part is ``BODY``::" - -msgid "``HEADER``" -msgstr "``HEADER``" - -msgid "``HEADER`` is an array. The content of ``HEADER`` has some patterns." -msgstr "``HEADER`` is an array. The content of ``HEADER`` has some patterns." - -msgid "Success case" -msgstr "Success case" - -msgid "``HEADER`` has three elements on success::" -msgstr "``HEADER`` has three elements on success::" - -msgid "The first element is always ``0``." -msgstr "The first element is always ``0``." - -msgid "" -"``UNIX_TIME_WHEN_COMMAND_IS_STARTED`` is the number of seconds since " -"1970-01-01 00:00:00 UTC when the command is started processing. " -"``ELAPSED_TIME`` is the elapsed time for processing the command in seconds. " -"Both ``UNIX_TIME_WHEN_COMMAND_IS_STARTED`` and ``ELAPSED_TIME`` are float " -"value. The precision of them are nanosecond." -msgstr "" -"``UNIX_TIME_WHEN_COMMAND_IS_STARTED`` is the number of seconds since " -"1970-01-01 00:00:00 UTC when the command is started processing. " -"``ELAPSED_TIME`` is the elapsed time for processing the command in seconds. " -"Both ``UNIX_TIME_WHEN_COMMAND_IS_STARTED`` and ``ELAPSED_TIME`` are float " -"value. The precision of them are nanosecond." - -msgid "Error case" -msgstr "Error case" - -msgid "``HEADER`` has four or five elements on error::" -msgstr "``HEADER`` has four or five elements on error::" - -msgid "" -"``ERROR_LOCATION`` may not be included in ``HEADER`` but other four elements " -"are always included." -msgstr "" -"``ERROR_LOCATION`` may not be included in ``HEADER`` but other four elements " -"are always included." - -msgid "" -"``RETURN_CODE`` is non 0 value. See :doc:`return_code` about available " -"return codes." -msgstr "" -"``RETURN_CODE`` is non 0 value. See :doc:`return_code` about available " -"return codes." - -msgid "" -"``UNIX_TIME_WHEN_COMMAND_IS_STARTED`` and ``ELAPSED_TIME`` are the same as " -"success case." -msgstr "" -"``UNIX_TIME_WHEN_COMMAND_IS_STARTED`` and ``ELAPSED_TIME`` are the same as " -"success case." - -msgid "``ERROR_MESSAGE`` is an error message in string." -msgstr "``ERROR_MESSAGE`` is an error message in string." - -msgid "" -"``ERROR_LOCATION`` is optional. If error location is collected, " -"``ERROR_LOCATION`` is included. ``ERROR_LOCATION`` is an array. " -"``ERROR_LOCATION`` has one ore two elements::" -msgstr "" -"``ERROR_LOCATION`` is optional. If error location is collected, " -"``ERROR_LOCATION`` is included. ``ERROR_LOCATION`` is an array. " -"``ERROR_LOCATION`` has one ore two elements::" - -msgid "" -"``LOCATION_IN_GROONGA`` is the source location that error is occurred in " -"groonga. It is useful for groonga developers but not useful for users. " -"``LOCATION_IN_GROONGA`` is an array. ``LOCATION_IN_GROONGA`` has three " -"elements::" -msgstr "" -"``LOCATION_IN_GROONGA`` is the source location that error is occurred in " -"groonga. It is useful for groonga developers but not useful for users. " -"``LOCATION_IN_GROONGA`` is an array. ``LOCATION_IN_GROONGA`` has three " -"elements::" - -msgid "``FUNCTION_NAME`` is the name of function that error is occurred." -msgstr "``FUNCTION_NAME`` is the name of function that error is occurred." - -msgid "" -"``SOURCE_FILE_NAME`` is the name of groonga's source file that error is " -"occurred." -msgstr "" -"``SOURCE_FILE_NAME`` is the name of groonga's source file that error is " -"occurred." - -msgid "" -"``LINE_NUMBER`` is the line number of ``SOURCE_FILE_NAME`` that error is " -"occurred." -msgstr "" -"``LINE_NUMBER`` is the line number of ``SOURCE_FILE_NAME`` that error is " -"occurred." - -msgid "" -"``LOCATION_IN_INPUT`` is optional. ``LOCATION_IN_INPUT`` is included when " -"the location that error is occurred in input file is collected. Input file " -"can be specified by ``--file`` command line option for ``groonga`` command. " -"``LOCATION_IN_GROONGA`` is an array. ``LOCATION_IN_GROONGA`` has three " -"elements::" -msgstr "" -"``LOCATION_IN_INPUT`` is optional. ``LOCATION_IN_INPUT`` is included when " -"the location that error is occurred in input file is collected. Input file " -"can be specified by ``--file`` command line option for ``groonga`` command. " -"``LOCATION_IN_GROONGA`` is an array. ``LOCATION_IN_GROONGA`` has three " -"elements::" - -msgid "``INPUT_FILE_NAME`` is the input file name that error is occurred." -msgstr "``INPUT_FILE_NAME`` is the input file name that error is occurred." - -msgid "" -"``LINE_NUMBER`` is the line number of ``INPUT_FILE_NAME`` that error is " -"occurred." -msgstr "" -"``LINE_NUMBER`` is the line number of ``INPUT_FILE_NAME`` that error is " -"occurred." - -msgid "" -"``LINE_CONTENT`` is the content at ``LINE_NUMBER`` in ``INPUT_FILE_NAME``." -msgstr "" -"``LINE_CONTENT`` is the content at ``LINE_NUMBER`` in ``INPUT_FILE_NAME``." - -msgid "``BODY``" -msgstr "``BODY``" - -msgid "``BODY`` content depends on the executed command. It may be omitted." -msgstr "``BODY`` content depends on the executed command. It may be omitted." - -msgid "``BODY`` may be an error message on error case." -msgstr "``BODY`` may be an error message on error case." - -msgid "XML" -msgstr "XML" - -msgid "TSV" -msgstr "TSV" - -msgid "See also" -msgstr "See also" - -msgid ":doc:`return_code` describes about return code." -msgstr ":doc:`return_code` describes about return code." - -msgid "Request ID" -msgstr "" - -# 59b175046aad404ea18bedf1729331eb -msgid "You can assign ID to each request." -msgstr "" - -# 536d3a9d246b4a95b822a7acd2fdb69b -msgid "" -"The ID can be used by canceling the request. See also :doc:`/reference/" -"commands/request_cancel` for details about canceling a request." -msgstr "" - -# 82c00caf9c0348a9be89cbddabf2f5ec -msgid "" -"Request ID should be managed by user. If you assign the same ID for some " -"running requests, you can't cancel the request." -msgstr "" - -# f4e4ad1af9714d5ab7b7da06ff3fcb22 -msgid "" -"The simplest ID sequence is incremented numbers such as ``1``, ``2`` , ``..." -"``." -msgstr "" - -# 9aaa4b35213c4144965de9d59a0a9bf6 -msgid "A request ID is a string. The maximum request ID size is 4096 byte." -msgstr "" - -# b0e0322c97084478914f521b313fcc6a -msgid "How to assign ID to request" -msgstr "" - -# 02654e49ebcd4dbe82903044a7ccae9a -msgid "" -"All commands accept ``request_id`` parameter. You can assign ID to request " -"by adding ``request_id`` parameter." -msgstr "" - -msgid "Here is an example to assign ``id-1`` ID to a request::" -msgstr "" - -msgid ":doc:`/reference/commands/request_cancel`" -msgstr "" - -msgid "Return code" -msgstr "Return code" - -msgid "" -"Return code is used to show whether a processing is succeeded or not. If the " -"processing is not succeeded, return code shows error type." -msgstr "" -"Return code is used to show whether a processing is succeeded or not. If the " -"processing is not succeeded, return code shows error type." - -msgid "" -"Return code is used in C API and query API. You can check return code via " -"``grn_ctx_t::rc`` in C API. You can check return code by looking the header " -"element in query API. See :doc:`output_format` about the header element in " -"query API." -msgstr "" -"Return code is used in C API and query API. You can check return code via " -"``grn_ctx_t::rc`` in C API. You can check return code by looking the header " -"element in query API. See :doc:`output_format` about the header element in " -"query API." - -msgid "List" -msgstr "List" - -msgid "" -"Here is a list of return codes. ``GRN_SUCCESS`` (= 0) means that the " -"processing is succeeded. Return codes that have negative value show error " -"type. ``GRN_END_OF_DATA`` is a special return code. It is used only C API. " -"It is not showen in query API." -msgstr "" -"Here is a list of return codes. ``GRN_SUCCESS`` (= 0) means that the " -"processing is succeeded. Return codes that have negative value show error " -"type. ``GRN_END_OF_DATA`` is a special return code. It is used only C API. " -"It is not showen in query API." - -msgid "0: ``GRN_SUCCESS``" -msgstr "0: ``GRN_SUCCESS``" - -msgid "1: ``GRN_END_OF_DATA``" -msgstr "1: ``GRN_END_OF_DATA``" - -msgid "-1: ``GRN_UNKNOWN_ERROR``" -msgstr "-1: ``GRN_UNKNOWN_ERROR``" - -msgid "-2: ``GRN_OPERATION_NOT_PERMITTED``" -msgstr "-2: ``GRN_OPERATION_NOT_PERMITTED``" - -msgid "-3: ``GRN_NO_SUCH_FILE_OR_DIRECTORY``" -msgstr "-3: ``GRN_NO_SUCH_FILE_OR_DIRECTORY``" - -msgid "-4: ``GRN_NO_SUCH_PROCESS``" -msgstr "-4: ``GRN_NO_SUCH_PROCESS``" - -msgid "-5: ``GRN_INTERRUPTED_FUNCTION_CALL``" -msgstr "-5: ``GRN_INTERRUPTED_FUNCTION_CALL``" - -msgid "-6: ``GRN_INPUT_OUTPUT_ERROR``" -msgstr "-6: ``GRN_INPUT_OUTPUT_ERROR``" - -msgid "-7: ``GRN_NO_SUCH_DEVICE_OR_ADDRESS``" -msgstr "-7: ``GRN_NO_SUCH_DEVICE_OR_ADDRESS``" - -msgid "-8: ``GRN_ARG_LIST_TOO_LONG``" -msgstr "-8: ``GRN_ARG_LIST_TOO_LONG``" - -msgid "-9: ``GRN_EXEC_FORMAT_ERROR``" -msgstr "-9: ``GRN_EXEC_FORMAT_ERROR``" - -msgid "-10: ``GRN_BAD_FILE_DESCRIPTOR``" -msgstr "-10: ``GRN_BAD_FILE_DESCRIPTOR``" - -msgid "-11: ``GRN_NO_CHILD_PROCESSES``" -msgstr "-11: ``GRN_NO_CHILD_PROCESSES``" - -msgid "-12: ``GRN_RESOURCE_TEMPORARILY_UNAVAILABLE``" -msgstr "-12: ``GRN_RESOURCE_TEMPORARILY_UNAVAILABLE``" - -msgid "-13: ``GRN_NOT_ENOUGH_SPACE``" -msgstr "-13: ``GRN_NOT_ENOUGH_SPACE``" - -msgid "-14: ``GRN_PERMISSION_DENIED``" -msgstr "-14: ``GRN_PERMISSION_DENIED``" - -msgid "-15: ``GRN_BAD_ADDRESS``" -msgstr "-15: ``GRN_BAD_ADDRESS``" - -msgid "-16: ``GRN_RESOURCE_BUSY``" -msgstr "-16: ``GRN_RESOURCE_BUSY``" - -msgid "-17: ``GRN_FILE_EXISTS``" -msgstr "-17: ``GRN_FILE_EXISTS``" - -msgid "-18: ``GRN_IMPROPER_LINK``" -msgstr "-18: ``GRN_IMPROPER_LINK``" - -msgid "-19: ``GRN_NO_SUCH_DEVICE``" -msgstr "-19: ``GRN_NO_SUCH_DEVICE``" - -msgid "-20: ``GRN_NOT_A_DIRECTORY``" -msgstr "-20: ``GRN_NOT_A_DIRECTORY``" - -msgid "-21: ``GRN_IS_A_DIRECTORY``" -msgstr "-21: ``GRN_IS_A_DIRECTORY``" - -msgid "-22: ``GRN_INVALID_ARGUMENT``" -msgstr "-22: ``GRN_INVALID_ARGUMENT``" - -msgid "-23: ``GRN_TOO_MANY_OPEN_FILES_IN_SYSTEM``" -msgstr "-23: ``GRN_TOO_MANY_OPEN_FILES_IN_SYSTEM``" - -msgid "-24: ``GRN_TOO_MANY_OPEN_FILES``" -msgstr "-24: ``GRN_TOO_MANY_OPEN_FILES``" - -msgid "-25: ``GRN_INAPPROPRIATE_I_O_CONTROL_OPERATION``" -msgstr "-25: ``GRN_INAPPROPRIATE_I_O_CONTROL_OPERATION``" - -msgid "-26: ``GRN_FILE_TOO_LARGE``" -msgstr "-26: ``GRN_FILE_TOO_LARGE``" - -msgid "-27: ``GRN_NO_SPACE_LEFT_ON_DEVICE``" -msgstr "-27: ``GRN_NO_SPACE_LEFT_ON_DEVICE``" - -msgid "-28: ``GRN_INVALID_SEEK``" -msgstr "-28: ``GRN_INVALID_SEEK``" - -msgid "-29: ``GRN_READ_ONLY_FILE_SYSTEM``" -msgstr "-29: ``GRN_READ_ONLY_FILE_SYSTEM``" - -msgid "-30: ``GRN_TOO_MANY_LINKS``" -msgstr "-30: ``GRN_TOO_MANY_LINKS``" - -msgid "-31: ``GRN_BROKEN_PIPE``" -msgstr "-31: ``GRN_BROKEN_PIPE``" - -msgid "-32: ``GRN_DOMAIN_ERROR``" -msgstr "-32: ``GRN_DOMAIN_ERROR``" - -msgid "-33: ``GRN_RESULT_TOO_LARGE``" -msgstr "-33: ``GRN_RESULT_TOO_LARGE``" - -msgid "-34: ``GRN_RESOURCE_DEADLOCK_AVOIDED``" -msgstr "-34: ``GRN_RESOURCE_DEADLOCK_AVOIDED``" - -msgid "-35: ``GRN_NO_MEMORY_AVAILABLE``" -msgstr "-35: ``GRN_NO_MEMORY_AVAILABLE``" - -msgid "-36: ``GRN_FILENAME_TOO_LONG``" -msgstr "-36: ``GRN_FILENAME_TOO_LONG``" - -msgid "-37: ``GRN_NO_LOCKS_AVAILABLE``" -msgstr "-37: ``GRN_NO_LOCKS_AVAILABLE``" - -msgid "-38: ``GRN_FUNCTION_NOT_IMPLEMENTED``" -msgstr "-38: ``GRN_FUNCTION_NOT_IMPLEMENTED``" - -msgid "-39: ``GRN_DIRECTORY_NOT_EMPTY``" -msgstr "-39: ``GRN_DIRECTORY_NOT_EMPTY``" - -msgid "-40: ``GRN_ILLEGAL_BYTE_SEQUENCE``" -msgstr "-40: ``GRN_ILLEGAL_BYTE_SEQUENCE``" - -msgid "-41: ``GRN_SOCKET_NOT_INITIALIZED``" -msgstr "-41: ``GRN_SOCKET_NOT_INITIALIZED``" - -msgid "-42: ``GRN_OPERATION_WOULD_BLOCK``" -msgstr "-42: ``GRN_OPERATION_WOULD_BLOCK``" - -msgid "-43: ``GRN_ADDRESS_IS_NOT_AVAILABLE``" -msgstr "-43: ``GRN_ADDRESS_IS_NOT_AVAILABLE``" - -msgid "-44: ``GRN_NETWORK_IS_DOWN``" -msgstr "-44: ``GRN_NETWORK_IS_DOWN``" - -msgid "-45: ``GRN_NO_BUFFER``" -msgstr "-45: ``GRN_NO_BUFFER``" - -msgid "-46: ``GRN_SOCKET_IS_ALREADY_CONNECTED``" -msgstr "-46: ``GRN_SOCKET_IS_ALREADY_CONNECTED``" - -msgid "-47: ``GRN_SOCKET_IS_NOT_CONNECTED``" -msgstr "-47: ``GRN_SOCKET_IS_NOT_CONNECTED``" - -msgid "-48: ``GRN_SOCKET_IS_ALREADY_SHUTDOWNED``" -msgstr "-48: ``GRN_SOCKET_IS_ALREADY_SHUTDOWNED``" - -msgid "-49: ``GRN_OPERATION_TIMEOUT``" -msgstr "-49: ``GRN_OPERATION_TIMEOUT``" - -msgid "-50: ``GRN_CONNECTION_REFUSED``" -msgstr "-50: ``GRN_CONNECTION_REFUSED``" - -msgid "-51: ``GRN_RANGE_ERROR``" -msgstr "-51: ``GRN_RANGE_ERROR``" - -msgid "-52: ``GRN_TOKENIZER_ERROR``" -msgstr "-52: ``GRN_TOKENIZER_ERROR``" - -msgid "-53: ``GRN_FILE_CORRUPT``" -msgstr "-53: ``GRN_FILE_CORRUPT``" - -msgid "-54: ``GRN_INVALID_FORMAT``" -msgstr "-54: ``GRN_INVALID_FORMAT``" - -msgid "-55: ``GRN_OBJECT_CORRUPT``" -msgstr "-55: ``GRN_OBJECT_CORRUPT``" - -msgid "-56: ``GRN_TOO_MANY_SYMBOLIC_LINKS``" -msgstr "-56: ``GRN_TOO_MANY_SYMBOLIC_LINKS``" - -msgid "-57: ``GRN_NOT_SOCKET``" -msgstr "-57: ``GRN_NOT_SOCKET``" - -msgid "-58: ``GRN_OPERATION_NOT_SUPPORTED``" -msgstr "-58: ``GRN_OPERATION_NOT_SUPPORTED``" - -msgid "-59: ``GRN_ADDRESS_IS_IN_USE``" -msgstr "-59: ``GRN_ADDRESS_IS_IN_USE``" - -msgid "-60: ``GRN_ZLIB_ERROR``" -msgstr "-60: ``GRN_ZLIB_ERROR``" - -msgid "-61: ``GRN_LZO_ERROR``" -msgstr "-61: ``GRN_LZO_ERROR``" - -msgid "-62: ``GRN_STACK_OVER_FLOW``" -msgstr "-62: ``GRN_STACK_OVER_FLOW``" - -msgid "-63: ``GRN_SYNTAX_ERROR``" -msgstr "-63: ``GRN_SYNTAX_ERROR``" - -msgid "-64: ``GRN_RETRY_MAX``" -msgstr "-64: ``GRN_RETRY_MAX``" - -msgid "-65: ``GRN_INCOMPATIBLE_FILE_FORMAT``" -msgstr "-65: ``GRN_INCOMPATIBLE_FILE_FORMAT``" - -msgid "-66: ``GRN_UPDATE_NOT_ALLOWED``" -msgstr "-66: ``GRN_UPDATE_NOT_ALLOWED``" - -msgid "-67: ``GRN_TOO_SMALL_OFFSET``" -msgstr "-67: ``GRN_TOO_SMALL_OFFSET``" - -msgid "-68: ``GRN_TOO_LARGE_OFFSET``" -msgstr "-68: ``GRN_TOO_LARGE_OFFSET``" - -msgid "-69: ``GRN_TOO_SMALL_LIMIT``" -msgstr "-69: ``GRN_TOO_SMALL_LIMIT``" - -msgid "-70: ``GRN_CAS_ERROR``" -msgstr "-70: ``GRN_CAS_ERROR``" - -msgid "-71: ``GRN_UNSUPPORTED_COMMAND_VERSION``" -msgstr "-71: ``GRN_UNSUPPORTED_COMMAND_VERSION``" - -msgid "" -":doc:`output_format` shows where return code is appeared in query API " -"response." -msgstr "" -":doc:`output_format` shows where return code is appeared in query API " -"response." - -msgid "" -":doc:`/spec/gqtp`: GQTP protocol also uses return code as status but it uses " -"2byte unsigned integer. So return codes that have negative value are " -"statuses that have positive value in GQTP protocol. You can convert status " -"value in GQTP protocol to return code by handling it as 2byte signed integer." -msgstr "" -":doc:`/spec/gqtp`: GQTP protocol also uses return code as status but it uses " -"2byte unsigned integer. So return codes that have negative value are " -"statuses that have positive value in GQTP protocol. You can convert status " -"value in GQTP protocol to return code by handling it as 2byte signed integer." - -msgid "``cache_limit``" -msgstr "``cache_limit``" - -msgid "" -"``cache_limit`` gets or sets the max number of query cache entries. Query " -"cache is used only by :doc:`select` command." -msgstr "" -"``cache_limit`` gets or sets the max number of query cache entries. Query " -"cache is used only by :doc:`select` command." - -msgid "" -"If the max number of query cache entries is 100, the recent 100 ``select`` " -"commands are only cached. The cache expire algorithm is LRU (least recently " -"used)." -msgstr "" -"If the max number of query cache entries is 100, the recent 100 ``select`` " -"commands are only cached. The cache expire algorithm is LRU (least recently " -"used)." - -msgid "Syntax" -msgstr "Syntax" - -msgid "``cache_limit`` has one optional parameter::" -msgstr "``cache_limit`` has one optional parameter::" - -msgid "" -"You can get the current max number of cache entries by executing " -"``cache_limit`` without parameter." -msgstr "" -"You can get the current max number of cache entries by executing " -"``cache_limit`` without parameter." - -msgid "" -"You can set the max number of cache entries by executing ``cache_limit`` " -"with ``max`` parameter." -msgstr "" -"You can set the max number of cache entries by executing ``cache_limit`` " -"with ``max`` parameter." - -msgid "Here is an example that sets ``10`` as the max number of cache entries." -msgstr "" -"Here is an example that sets ``10`` as the max number of cache entries." - -msgid "" -"If ``max`` parameter is used, the return value is the max number of cache " -"entries before ``max`` parameter is set." -msgstr "" -"If ``max`` parameter is used, the return value is the max number of cache " -"entries before ``max`` parameter is set." - -msgid "Parameters" -msgstr "Parameters" - -msgid "This section describes all parameters." -msgstr "This section describes all parameters." - -msgid "``max``" -msgstr "``max``" - -msgid "It specifies the max number of query cache entries as a number." -msgstr "It specifies the max number of query cache entries as a number." - -msgid "" -"If ``max`` parameter isn't specified, the current max number of query cache " -"entries isn't changed. ``cache_limit`` just returns the current max number " -"of query cache entries." -msgstr "" -"If ``max`` parameter isn't specified, the current max number of query cache " -"entries isn't changed. ``cache_limit`` just returns the current max number " -"of query cache entries." - -msgid "Return value" -msgstr "Return value" - -msgid "``cache_limit`` returns the current max number of query cache entries::" -msgstr "" -"``cache_limit`` returns the current max number of query cache entries::" - -msgid "See :doc:`/reference/command/output_format` about ``HEADER``." -msgstr "See :doc:`/reference/command/output_format` about ``HEADER``." - -msgid "``N_ENTRIES``" -msgstr "``N_ENTRIES``" - -msgid "" -"``N_ENTRIES`` is the current max number of query cache entries. It is a " -"number." -msgstr "" -"``N_ENTRIES`` is the current max number of query cache entries. It is a " -"number." - -msgid ":doc:`select`" -msgstr ":doc:`select`" - -msgid "``check``" -msgstr "" - -msgid "check - オブジェクトの状態表示" -msgstr "check - オブジェクトの状態表示" - -msgid "" -"Groonga組込コマンドの一つであるcheckについて説明します。組込コマンドは、" -"groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリク" -"エストを送信することによって実行します。" -msgstr "" -"Groonga組込コマンドの一つであるcheckについて説明します。組込コマンドは、" -"groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリク" -"エストを送信することによって実行します。" - -msgid "" -"checkコマンドは、groongaプロセス内の指定したオブジェクトの状態を表示します。" -"主にデータベースが壊れた場合など異常時の問題解決のために使用することを想定し" -"ています。デバッグ用のため、返値のフォーマットが安定しているということは保証" -"されません。（フォーマットが変更される可能性が高い）" -msgstr "" -"checkコマンドは、groongaプロセス内の指定したオブジェクトの状態を表示します。" -"主にデータベースが壊れた場合など異常時の問題解決のために使用することを想定し" -"ています。デバッグ用のため、返値のフォーマットが安定しているということは保証" -"されません。（フォーマットが変更される可能性が高い）" - -msgid "テーブルTermsのインデックスカラムnameの状態を表示します。::" -msgstr "テーブルTermsのインデックスカラムnameの状態を表示します。::" - -msgid "``obj``" -msgstr "``obj``" - -msgid "状態を表示するオブジェクトの名前を指定します。" -msgstr "状態を表示するオブジェクトの名前を指定します。" - -msgid "チェックするオブジェクトにより返される値が変わります。" -msgstr "チェックするオブジェクトにより返される値が変わります。" - -msgid "インデックスカラムの場合::" -msgstr "インデックスカラムの場合::" - -msgid "``インデックスの状態`` には下記の項目がハッシュ形式で出力されます。" -msgstr "``インデックスの状態`` には下記の項目がハッシュ形式で出力されます。" - -msgid "``flags``" -msgstr "``flags``" - -msgid "指定されているフラグ値です。16進数で表現されています。" -msgstr "指定されているフラグ値です。16進数で表現されています。" - -msgid "``max sid``" -msgstr "``max sid``" - -msgid "セグメントのうち最も大きなIDです。" -msgstr "セグメントのうち最も大きなIDです。" - -msgid "``number of garbage segments``" -msgstr "``number of garbage segments``" - -msgid "ゴミセグメントの数です。" -msgstr "ゴミセグメントの数です。" - -msgid "``number of array segments``" -msgstr "``number of array segments``" - -msgid "配列セグメントの数です。" -msgstr "配列セグメントの数です。" - -msgid "``max id of array segment``" -msgstr "``max id of array segment``" - -msgid "配列セグメントのうち最も大きなIDです。" -msgstr "配列セグメントのうち最も大きなIDです。" - -msgid "``number of buffer segments``" -msgstr "``number of buffer segments``" - -msgid "バッファセグメントの数です。" -msgstr "バッファセグメントの数です。" - -msgid "``max id of buffer segment``" -msgstr "``max id of buffer segment``" - -msgid "バッファセグメントのうち最も大きなIDです。" -msgstr "バッファセグメントのうち最も大きなIDです。" - -msgid "``max id of physical segment in use``" -msgstr "``max id of physical segment in use``" - -msgid "使用中の論理セグメントのうち最も大きなIDです。" -msgstr "使用中の論理セグメントのうち最も大きなIDです。" - -msgid "``number of unmanaged segments``" -msgstr "``number of unmanaged segments``" - -msgid "管理されていないセグメントの数です。" -msgstr "管理されていないセグメントの数です。" - -msgid "``total chunk size``" -msgstr "``total chunk size``" - -msgid "チャンクサイズの合計です。" -msgstr "チャンクサイズの合計です。" - -msgid "``max id of chunk segments in use``" -msgstr "``max id of chunk segments in use``" - -msgid "使用中のチャンクセグメントのうち最も大きなIDです。" -msgstr "使用中のチャンクセグメントのうち最も大きなIDです。" - -msgid "``number of garbage chunk``" -msgstr "``number of garbage chunk``" - -msgid "各チャンク毎のゴミの数です。" -msgstr "各チャンク毎のゴミの数です。" - -msgid "``バッファの状態`` には下記の項目がハッシュ形式で出力されます。" -msgstr "``バッファの状態`` には下記の項目がハッシュ形式で出力されます。" - -msgid "``buffer id``" -msgstr "``buffer id``" - -msgid "バッファIDです。" -msgstr "バッファIDです。" - -msgid "``chunk size``" -msgstr "``chunk size``" - -msgid "チャンクのサイズです。" -msgstr "チャンクのサイズです。" - -msgid "``buffer term``" -msgstr "``buffer term``" - -msgid "" -"バッファ内にある語の一覧です。各語の状態は以下のような配列となっています。" -msgstr "" -"バッファ内にある語の一覧です。各語の状態は以下のような配列となっています。" - -msgid "" -"[語, バッファに登録されている語のID, 用語集に登録されている語のID, バッファ内" -"でのサイズ, チャンク内でのサイズ]" -msgstr "" -"[語, バッファに登録されている語のID, 用語集に登録されている語のID, バッファ内" -"でのサイズ, チャンク内でのサイズ]" - -msgid "``buffer free``" -msgstr "``buffer free``" - -msgid "バッファの空き容量です。" -msgstr "バッファの空き容量です。" - -msgid "``size in buffer``" -msgstr "``size in buffer``" - -msgid "バッファの使用量です。" -msgstr "バッファの使用量です。" - -msgid "``nterms``" -msgstr "``nterms``" - -msgid "バッファ内にある語の数です。" -msgstr "バッファ内にある語の数です。" - -msgid "``nterms with chunk``" -msgstr "``nterms with chunk``" - -msgid "バッファ内にある語のうち、チャンクを使っている語の数です。" -msgstr "バッファ内にある語のうち、チャンクを使っている語の数です。" - -msgid "``clearlock``" -msgstr "``clearlock``" - -# e00d19a13acf4e8588248661c00cacde -msgid "Use :doc:`lock_clear` instead." -msgstr "" - -msgid "clearlock - オブジェクトにセットされたロックを解除する" -msgstr "clearlock - オブジェクトにセットされたロックを解除する" - -msgid "" -"Groonga組込コマンドの一つであるclearlockについて説明します。組込コマンドは、" -"groonga実行ファイルの引数、標準>入力、またはソケット経由でgroongaサーバにリク" -"エストを送信することによって実行します。" -msgstr "" - -msgid "" -"clearlockは、対象となるオブジェクト(データベース,テーブル,インデックス等)を指" -"定し、オブジェクトにかけられた>ロックを再帰的に解除します。" -msgstr "" - -msgid "開いているデータベースのロックをすべて解除する::" -msgstr "開いているデータベースのロックをすべて解除する::" - -msgid "テーブル名 Entry のカラム body のロックを解除する::" -msgstr "テーブル名 Entry のカラム body のロックを解除する::" - -msgid "``objname``" -msgstr "``objname``" - -msgid "" -"対象となるオブジェクト名を指定します。空の場合、開いているdbオブジェクトが対" -"象となります。" -msgstr "" -"対象となるオブジェクト名を指定します。空の場合、開いているdbオブジェクトが対" -"象となります。" - -msgid "``成功かどうかのフラグ``" -msgstr "``成功かどうかのフラグ``" - -msgid "エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。" -msgstr "エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。" - -msgid ":doc:`load`" -msgstr ":doc:`load`" - -msgid "``column_create``" -msgstr "``column_create``" - -msgid "column_create - カラムの追加" -msgstr "column_create - カラムの追加" - -msgid "" -"Groonga組込コマンドの一つであるcolumn_createについて説明します。組込コマンド" -"は、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバに" -"リクエストを送信することによって実行します。" -msgstr "" -"Groonga組込コマンドの一つであるcolumn_createについて説明します。組込コマンド" -"は、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバに" -"リクエストを送信することによって実行します。" - -msgid "" -"column_createは、使用しているデータベースのテーブルに対してカラムを追加しま" -"す。" -msgstr "" -"column_createは、使用しているデータベースのテーブルに対してカラムを追加しま" -"す。" - -msgid "テーブルEntryに、ShortText型の値を格納するカラム、bodyを作成します。::" -msgstr "テーブルEntryに、ShortText型の値を格納するカラム、bodyを作成します。::" - -msgid "" -"テーブルTermに、Entryテーブルのbodyカラムの値を対象とする完全転置インデックス" -"型カラム、entry_bodyを作成します。::" -msgstr "" -"テーブルTermに、Entryテーブルのbodyカラムの値を対象とする完全転置インデックス" -"型カラム、entry_bodyを作成します。::" - -msgid "``table``" -msgstr "``table``" - -msgid "カラムを追加するテーブルの名前を指定します。" -msgstr "カラムを追加するテーブルの名前を指定します。" - -msgid "``name``" -msgstr "``name``" - -msgid "" -"作成するカラムの名前を指定します。カラム名は、テーブルの中で一意でなければな" -"りません。" -msgstr "" -"作成するカラムの名前を指定します。カラム名は、テーブルの中で一意でなければな" -"りません。" - -msgid "" -"ピリオド('.'), コロン(':')を含む名前のカラムは作成できません。また、アンダー" -"スコア('_')で始まる名前は予約済みであり、使用できません。" -msgstr "" -"ピリオド('.'), コロン(':')を含む名前のカラムは作成できません。また、アンダー" -"スコア('_')で始まる名前は予約済みであり、使用できません。" - -msgid "" -"カラムの属性を表す以下の数値か、パイプ('|')で組み合わせたシンボル名を指定しま" -"す。" -msgstr "" -"カラムの属性を表す以下の数値か、パイプ('|')で組み合わせたシンボル名を指定しま" -"す。" - -msgid "0, ``COLUMN_SCALAR``" -msgstr "0, ``COLUMN_SCALAR``" - -msgid "単一の値が格納できるカラムを作成します。" -msgstr "単一の値が格納できるカラムを作成します。" - -msgid "1, ``COLUMN_VECTOR``" -msgstr "1, ``COLUMN_VECTOR``" - -msgid "複数の値の配列を格納できるカラムを作成します。" -msgstr "複数の値の配列を格納できるカラムを作成します。" - -msgid "2, ``COLUMN_INDEX``" -msgstr "2, ``COLUMN_INDEX``" - -msgid "インデックス型のカラムを作成します。" -msgstr "インデックス型のカラムを作成します。" - -msgid "" -"There are two flags to compress the value of column, but you can't specify " -"these flags for now because there are memory leaks issue `GitHub#6 <https://" -"github.com/groonga/groonga/issues/6>`_ when refers the value of column. This " -"issue occurs both of them (zlib and lzo)." -msgstr "" -"There are two flags to compress the value of column, but you can't specify " -"these flags for now because there are memory leaks issue `GitHub#6 <https://" -"github.com/groonga/groonga/issues/6>`_ when refers the value of column. This " -"issue occurs both of them (zlib and lzo)." - -msgid "16, ``COMPRESS_ZLIB``" -msgstr "16, ``COMPRESS_ZLIB``" - -msgid "" -"Reserved. Compress the value of column by using zlib. This flag is disabled " -"feature even if you build groonga with ``--with-zlib``." -msgstr "" -"Reserved. Compress the value of column by using zlib. This flag is disabled " -"feature even if you build groonga with ``--with-zlib``." - -msgid "32, ``COMPRESS_LZO``" -msgstr "32, ``COMPRESS_LZO``" - -msgid "" -"Reserved. Compress the value of column by using lzo. This flag is disabled " -"feature even if you build groonga with ``--with-lzo``." -msgstr "" -"Reserved. Compress the value of column by using lzo. This flag is disabled " -"feature even if you build groonga with ``--with-lzo``." - -msgid "" -"インデックス型のカラムについては、flagsの値に以下の値を加えることによって、追" -"加の属 性を指定することができます。" -msgstr "" -"インデックス型のカラムについては、flagsの値に以下の値を加えることによって、追" -"加の属 性を指定することができます。" - -msgid "128, ``WITH_SECTION``" -msgstr "128, ``WITH_SECTION``" - -msgid "段落情報を格納するインデックスを作成します。" -msgstr "段落情報を格納するインデックスを作成します。" - -msgid "256, ``WITH_WEIGHT``" -msgstr "256, ``WITH_WEIGHT``" - -msgid "ウェイト情報を格納するインデックスを作成します。" -msgstr "ウェイト情報を格納するインデックスを作成します。" - -msgid "512, ``WITH_POSITION``" -msgstr "512, ``WITH_POSITION``" - -msgid "位置情報を格納するインデックス(完全転置インデックス)を作成します。" -msgstr "位置情報を格納するインデックス(完全転置インデックス)を作成します。" - -msgid "``type``" -msgstr "``type``" - -msgid "" -"値の型を指定します。Groongaの組込型か、同一データベースに定義済みのユーザ定義" -"型、定義済みのテーブルを指定することができます。" -msgstr "" -"値の型を指定します。Groongaの組込型か、同一データベースに定義済みのユーザ定義" -"型、定義済みのテーブルを指定することができます。" - -msgid "``source``" -msgstr "``source``" - -msgid "" -"インデックス型のカラムを作成した場合は、インデックス対象となるカラムをsource" -"引数に指定します。" -msgstr "" -"インデックス型のカラムを作成した場合は、インデックス対象となるカラムをsource" -"引数に指定します。" - -msgid "``SUCCEEDED``" -msgstr "``SUCCEEDED``" - -msgid "If command is succeeded, it returns true on success, false otherwise." -msgstr "If command is succeeded, it returns true on success, false otherwise." - -msgid "``column_list``" -msgstr "``column_list``" - -msgid "``column_list`` command lists columns in a table." -msgstr "``column_list`` command lists columns in a table." - -msgid "``column_list`` command takes one required parameter::" -msgstr "``column_list`` command takes one required parameter::" - -msgid "Here is a simple example of ``column_list`` command." -msgstr "Here is a simple example of ``column_list`` command." - -msgid "This section describes parameters of ``column_list``." -msgstr "This section describes parameters of ``column_list``." - -msgid "Required parameters" -msgstr "Required parameters" - -msgid "All parameters are required." -msgstr "All parameters are required." - -msgid "It specifies the name of table to be listed columns." -msgstr "It specifies the name of table to be listed columns." - -msgid "``column_list`` returns the list of column information in the table::" -msgstr "``column_list`` returns the list of column information in the table::" - -msgid "``COLUMN_LIST_HEADER``" -msgstr "``COLUMN_LIST_HEADER``" - -msgid "" -"``COLUMN_LIST_HEADER`` describes about content of each " -"``COLUMN_INFORMATION``." -msgstr "" -"``COLUMN_LIST_HEADER`` describes about content of each " -"``COLUMN_INFORMATION``." - -msgid "``COLUMN_LIST_HEADER`` is the following format::" -msgstr "``COLUMN_LIST_HEADER`` is the following format::" - -msgid "It means the following:" -msgstr "It means the following:" - -msgid "" -"The first content in ``COLUMN_INFORMATION`` is ``id`` value and the value " -"type is ``UInt32``." -msgstr "" -"The first content in ``COLUMN_INFORMATION`` is ``id`` value and the value " -"type is ``UInt32``." - -msgid "" -"The second content in ``COLUMN_INFORMATION`` is ``name`` value and the value " -"type is ``ShortText``." -msgstr "" -"The second content in ``COLUMN_INFORMATION`` is ``name`` value and the value " -"type is ``ShortText``." - -msgid "The third content ...." -msgstr "The third content ...." - -msgid "See the following ``COLUMN_INFORMATION`` description for details." -msgstr "See the following ``COLUMN_INFORMATION`` description for details." - -msgid "" -"This field provides meta-data of column information. So this field will be " -"useful for programs rather than humans." -msgstr "" -"This field provides meta-data of column information. So this field will be " -"useful for programs rather than humans." - -msgid "``COLUMN_INFORMATION``" -msgstr "``COLUMN_INFORMATION``" - -msgid "Each ``COLUMN_INFORMATION`` is the following format::" -msgstr "Each ``COLUMN_INFORMATION`` is the following format::" - -msgid "``ID``" -msgstr "``ID``" - -msgid "" -"The column ID in the Groonga database. Normally, you don't care about it." -msgstr "" -"The column ID in the Groonga database. Normally, you don't care about it." - -msgid "``NAME``" -msgstr "``NAME``" - -msgid "The column name." -msgstr "The column name." - -msgid "``PATH``" -msgstr "``PATH``" - -msgid "The path for storing column data." -msgstr "The path for storing column data." - -msgid "``TYPE``" -msgstr "``TYPE``" - -msgid "The type of the column. It is one of the followings:" -msgstr "The type of the column. It is one of the followings:" - -msgid "Value" -msgstr "Value" - -msgid "Description" -msgstr "Description" - -msgid "``fix``" -msgstr "``fix``" - -msgid "" -"The column is a fixed size column. Scalar column that its type is fixed size " -"type is fixed size column." -msgstr "" -"The column is a fixed size column. Scalar column that its type is fixed size " -"type is fixed size column." - -msgid "``var``" -msgstr "``var``" - -msgid "" -"The column is a variable size column. Vector column or scalar column that " -"its type is variable size type are variable size column." -msgstr "" -"The column is a variable size column. Vector column or scalar column that " -"its type is variable size type are variable size column." - -msgid "``index``" -msgstr "``index``" - -msgid "The column is an index column." -msgstr "The column is an index column." - -msgid "``FLAGS``" -msgstr "``FLAGS``" - -msgid "" -"The flags of the column. Each flag is separated by ``|`` like " -"``COLUMN_VECTOR|WITH_WEIGHT``. ``FLAGS`` must include one of " -"``COLUMN_SCALAR``, ``COLUMN_VECTOR`` or ``COLUMN_INDEX``. Other flags are " -"optional." -msgstr "" -"The flags of the column. Each flag is separated by ``|`` like " -"``COLUMN_VECTOR|WITH_WEIGHT``. ``FLAGS`` must include one of " -"``COLUMN_SCALAR``, ``COLUMN_VECTOR`` or ``COLUMN_INDEX``. Other flags are " -"optional." - -msgid "Here is the available flags:" -msgstr "Here is the available flags:" - -msgid "Flag" -msgstr "Flag" - -msgid "``COLUMN_SCALAR``" -msgstr "``COLUMN_SCALAR``" - -msgid "The column is a scalar column." -msgstr "The column is a scalar column." - -msgid "``COLUMN_VECTOR``" -msgstr "``COLUMN_VECTOR``" - -msgid "The column is a vector column." -msgstr "The column is a vector column." - -msgid "``COLUMN_INDEX``" -msgstr "``COLUMN_INDEX``" - -msgid "``WITH_WEIGHT``" -msgstr "``WITH_WEIGHT``" - -msgid "" -"The column can have weight. ``COLUMN_VECTOR`` and ``COLUMN_INDEX`` may have " -"it. ``COLUMN_SCALAR`` doesn't have it." -msgstr "" -"The column can have weight. ``COLUMN_VECTOR`` and ``COLUMN_INDEX`` may have " -"it. ``COLUMN_SCALAR`` doesn't have it." - -msgid "``WITH_SECTION``" -msgstr "``WITH_SECTION``" - -msgid "" -"The column can have section information. ``COLUMN_INDEX`` may have it. " -"``COLUMN_SCALAR`` and ``COLUMN_VECTOR`` don't have it." -msgstr "" -"The column can have section information. ``COLUMN_INDEX`` may have it. " -"``COLUMN_SCALAR`` and ``COLUMN_VECTOR`` don't have it." - -msgid "Multiple column index has it." -msgstr "Multiple column index has it." - -msgid "``WITH_POSITION``" -msgstr "``WITH_POSITION``" - -msgid "" -"The column can have position information. ``COLUMN_INDEX`` may have it. " -"``COLUMN_SCALAR`` and ``COLUMN_VECTOR`` don't have it." -msgstr "" -"The column can have position information. ``COLUMN_INDEX`` may have it. " -"``COLUMN_SCALAR`` and ``COLUMN_VECTOR`` don't have it." - -msgid "Full text search index must has it." -msgstr "Full text search index must has it." - -msgid "``PERSISTENT``" -msgstr "``PERSISTENT``" - -msgid "" -"The column is a persistent column. It means that the column isn't a :doc:`/" -"reference/columns/pseudo`." -msgstr "" -"The column is a persistent column. It means that the column isn't a :doc:`/" -"reference/columns/pseudo`." - -msgid "``DOMAIN``" -msgstr "``DOMAIN``" - -msgid "The name of table that has the column." -msgstr "The name of table that has the column." - -msgid "``RANGE``" -msgstr "``RANGE``" - -msgid "The value type name of the column. It is a type name or a table name." -msgstr "The value type name of the column. It is a type name or a table name." - -msgid "``SOURCES``" -msgstr "``SOURCES``" - -msgid "" -"An array of the source column names of the index. If the index column is " -"multiple column index, the array has two or more source column names." -msgstr "" -"An array of the source column names of the index. If the index column is " -"multiple column index, the array has two or more source column names." - -msgid "" -"It is always an empty array for ``COLUMN_SCALAR`` and ``COLUMN_VECTOR``." -msgstr "" -"It is always an empty array for ``COLUMN_SCALAR`` and ``COLUMN_VECTOR``." - -msgid ":doc:`/reference/commands/column_create`" -msgstr ":doc:`/reference/commands/column_create`" - -msgid ":doc:`/reference/column`" -msgstr ":doc:`/reference/column`" - -msgid "``column_remove``" -msgstr "``column_remove``" - -msgid "column_remove - テーブルに定義されているカラムの削除" -msgstr "column_remove - テーブルに定義されているカラムの削除" - -msgid "" -"Groonga組込コマンドの一つであるcolumn_removeについて説明します。組込コマンド" -"は、groonga実行ファイルの引数、>標準入力、またはソケット経由でgroongaサーバに" -"リクエストを送信することによって実行します。" -msgstr "" - -msgid "" -"column_removeはテーブルに定義されているカラムを削除します。 また、付随するイ" -"ンデックスも削除されます。[#]_" -msgstr "" -"column_removeはテーブルに定義されているカラムを削除します。 また、付随するイ" -"ンデックスも削除されます。[#]_" - -msgid "脚注" -msgstr "脚注" - -msgid "" -"マルチセクションインデックスの一部である場合も、インデックスが削除されます。" -msgstr "" -"マルチセクションインデックスの一部である場合も、インデックスが削除されます。" - -msgid "削除対象のカラムが定義されているテーブルの名前を指定します。" -msgstr "削除対象のカラムが定義されているテーブルの名前を指定します。" - -msgid "削除対象のカラム名を指定します。" -msgstr "削除対象のカラム名を指定します。" - -msgid "``column_rename``" -msgstr "``column_rename``" - -msgid "``column_rename`` command renames a column." -msgstr "``column_rename`` command renames a column." - -msgid "" -"It is a light operation. It just changes a relationship between name and the " -"column object. It doesn't copy column values." -msgstr "" -"It is a light operation. It just changes a relationship between name and the " -"column object. It doesn't copy column values." - -msgid "" -"It is a dangerous operation. You must stop all operations including read " -"operations while you run ``column_rename``. If the following case is " -"occurred, Groonga process may be crashed:" -msgstr "" -"It is a dangerous operation. You must stop all operations including read " -"operations while you run ``column_rename``. If the following case is " -"occurred, Groonga process may be crashed:" - -msgid "" -"Starts an operation (like ``select``) that accesses the column to be renamed " -"by the current column name. The current column name is called as ``the old " -"column name`` in the below because the column name is renamed." -msgstr "" -"Starts an operation (like ``select``) that accesses the column to be renamed " -"by the current column name. The current column name is called as ``the old " -"column name`` in the below because the column name is renamed." - -msgid "Runs ``column_rename``. The ``select`` is still running." -msgstr "Runs ``column_rename``. The ``select`` is still running." - -msgid "" -"The ``select`` accesses the column to be renamed by the old column name. But " -"the ``select`` can't find the column by the old name because the column has " -"been renamed to the new column name. It may crash the Groonga process." -msgstr "" -"The ``select`` accesses the column to be renamed by the old column name. But " -"the ``select`` can't find the column by the old name because the column has " -"been renamed to the new column name. It may crash the Groonga process." - -msgid "" -"``column_rename`` command takes three parameters. All parameters are " -"required::" -msgstr "" -"``column_rename`` command takes three parameters. All parameters are " -"required::" - -msgid "Here is a simple example of ``column_rename`` command." -msgstr "Here is a simple example of ``column_rename`` command." - -msgid "This section describes parameters of ``column_rename``." -msgstr "This section describes parameters of ``column_rename``." - -msgid "It specifies the name of table that has the column to be renamed." -msgstr "It specifies the name of table that has the column to be renamed." - -msgid "It specifies the column name to be renamed." -msgstr "It specifies the column name to be renamed." - -msgid "``new_name``" -msgstr "``new_name``" - -msgid "It specifies the new column name." -msgstr "It specifies the new column name." - -msgid "``SUCCEEDED_OR_NOT``" -msgstr "``SUCCEEDED_OR_NOT``" - -msgid "It is ``true`` on success, ``false`` otherwise." -msgstr "It is ``true`` on success, ``false`` otherwise." - -msgid "``define_selector``" -msgstr "``define_selector``" - -msgid "define_selector - 検索コマンドを定義" -msgstr "define_selector - 検索コマンドを定義" - -msgid "" -"Groonga組込コマンドの一つであるdefine_selectorについて説明します。組込コマン" -"ドは、groonga実行ファイルの引数>、標準入力、またはソケット経由でgroongaサーバ" -"にリクエストを送信することによって実行します。" -msgstr "" - -msgid "" -"define_selectorは、検索条件をカスタマイズした新たな検索コマンドを定義します。" -msgstr "" -"define_selectorは、検索条件をカスタマイズした新たな検索コマンドを定義します。" - -msgid "" -"テーブルEntryの全レコード・全カラムの値を出力するselectorコマンドを定義しま" -"す。::" -msgstr "" -"テーブルEntryの全レコード・全カラムの値を出力するselectorコマンドを定義しま" -"す。::" - -msgid "定義するselectorコマンドの名前を指定します。" -msgstr "定義するselectorコマンドの名前を指定します。" - -msgid "検索対象のテーブルを指定します。" -msgstr "検索対象のテーブルを指定します。" - -msgid "``match_columns``" -msgstr "``match_columns``" - -msgid "追加するselectorコマンドのmatch_columns引数のデフォルト値を指定します。" -msgstr "" -"追加するselectorコマンドのmatch_columns引数のデフォルト値を指定します。" - -msgid "``query``" -msgstr "``query``" - -msgid "追加するselectorコマンドのquery引数のデフォルト値を指定します。" -msgstr "追加するselectorコマンドのquery引数のデフォルト値を指定します。" - -msgid "``filter``" -msgstr "``filter``" - -msgid "追加するselectorコマンドのfilter引数のデフォルト値を指定します。" -msgstr "追加するselectorコマンドのfilter引数のデフォルト値を指定します。" - -msgid "``scorer``" -msgstr "``scorer``" - -msgid "追加するselectorコマンドのscorer引数のデフォルト値を指定します。" -msgstr "追加するselectorコマンドのscorer引数のデフォルト値を指定します。" - -msgid "``sortby``" -msgstr "``sortby``" - -msgid "追加するselectorコマンドのsortby引数のデフォルト値を指定します。" -msgstr "追加するselectorコマンドのsortby引数のデフォルト値を指定します。" - -msgid "``output_columns``" -msgstr "``output_columns``" - -msgid "" -"追加するselectorコマンドのoutput_columns引数のデフォルト値を指定します。" -msgstr "" -"追加するselectorコマンドのoutput_columns引数のデフォルト値を指定します。" - -msgid "``offset``" -msgstr "``offset``" - -msgid "追加するselectorコマンドのoffset引数のデフォルト値を指定します。" -msgstr "追加するselectorコマンドのoffset引数のデフォルト値を指定します。" - -msgid "``limit``" -msgstr "``limit``" - -msgid "追加するselectorコマンドのlimit引数のデフォルト値を指定します。" -msgstr "追加するselectorコマンドのlimit引数のデフォルト値を指定します。" - -msgid "``drilldown``" -msgstr "``drilldown``" - -msgid "追加するselectorコマンドのdrilldown引数のデフォルト値を指定します。" -msgstr "追加するselectorコマンドのdrilldown引数のデフォルト値を指定します。" - -msgid "``drilldown_sortby``" -msgstr "``drilldown_sortby``" - -msgid "" -"追加するselectorコマンドのdrilldown_sortby引数のデフォルト値を指定します。" -msgstr "" -"追加するselectorコマンドのdrilldown_sortby引数のデフォルト値を指定します。" - -msgid "``drilldown_output_columns``" -msgstr "``drilldown_output_columns``" - -msgid "" -"追加するselectorコマンドのdrilldown_output_columns引数のデフォルト値を指定し" -"ます。" -msgstr "" -"追加するselectorコマンドのdrilldown_output_columns引数のデフォルト値を指定し" -"ます。" - -msgid "``drilldown_offset``" -msgstr "``drilldown_offset``" - -msgid "" -"追加するselectorコマンドのdrilldown_offset引数のデフォルト値を指定します。" -msgstr "" -"追加するselectorコマンドのdrilldown_offset引数のデフォルト値を指定します。" - -msgid "``drilldown_limit``" -msgstr "``drilldown_limit``" - -msgid "" -"追加するselectorコマンドのdrilldown_limit引数のデフォルト値を指定します。" -msgstr "" -"追加するselectorコマンドのdrilldown_limit引数のデフォルト値を指定します。" - -msgid ":doc:`/reference/grn_expr`" -msgstr ":doc:`/reference/grn_expr`" - -msgid "``defrag``" -msgstr "" - -msgid "``defrag`` command resolves fragmentation of specified objects." -msgstr "``defrag`` command resolves fragmentation of specified objects." - -msgid "" -"Groonga組込コマンドの一つであるdefragについて説明します。組込コマンドは、" -"groonga実行ファイルの引数、標準入力 、またはソケット経由でgroongaサーバにリク" -"エストを送信することによって実行します。" -msgstr "" - -msgid "" -"defragは、対象となるオブジェクト(データベースか可変長サイズカラム)を指定し、" -"オブジェクトのフラグメンテーショ ンを解消します。" -msgstr "" - -msgid "開いているデータベースのフラグメンテーションを解消する::" -msgstr "開いているデータベースのフラグメンテーションを解消する::" - -msgid "テーブル名 Entry のカラム body のフラグメンテーションを解消する::" -msgstr "テーブル名 Entry のカラム body のフラグメンテーションを解消する::" - -msgid "``フラグメンテーション解消を実行したセグメントの数``" -msgstr "``フラグメンテーション解消を実行したセグメントの数``" - -msgid "フラグメンテーション解消を実行したセグメントの数を返す。" -msgstr "フラグメンテーション解消を実行したセグメントの数を返す。" - -msgid "``delete``" -msgstr "``delete``" - -msgid "``delete`` command deletes specified record of table." -msgstr "``delete`` command deletes specified record of table." - -msgid "Cascade delete" -msgstr "Cascade delete" - -msgid "" -"There is a case that multiple table is associated. For example, the key of " -"one table are referenced by other table's records. In such a case, if you " -"delete the key of one table, other table's records are also removed." -msgstr "" -"There is a case that multiple table is associated. For example, the key of " -"one table are referenced by other table's records. In such a case, if you " -"delete the key of one table, other table's records are also removed." - -msgid "" -"Note that the type of other table's column is COLUMN_VECTOR, only the value " -"of referencing key is removed from the vector value." -msgstr "" -"Note that the type of other table's column is COLUMN_VECTOR, only the value " -"of referencing key is removed from the vector value." - -msgid "Here are a schema definition and sample data to show usage." -msgstr "Here are a schema definition and sample data to show usage." - -msgid "Delete the record from Entry table which has \"2\" as the key." -msgstr "Delete the record from Entry table which has \"2\" as the key." - -msgid "Here is the example about cascaded delete." -msgstr "Here is the example about cascaded delete." - -msgid "The country column of Users table associates with Country table." -msgstr "The country column of Users table associates with Country table." - -msgid "" -"\"Cascaded delete\" removes the records which matches specified key and " -"refers that key." -msgstr "" -"\"Cascaded delete\" removes the records which matches specified key and " -"refers that key." - -msgid "It specifies the name of table to delete the records." -msgstr "It specifies the name of table to delete the records." - -msgid "``key``" -msgstr "``key``" - -msgid "" -"It specifies the key of record to delete. If you use the table with " -"TABLE_NO_KEY, the key is just ignored. (Use ``id`` parameter in such a case)" -msgstr "" -"It specifies the key of record to delete. If you use the table with " -"TABLE_NO_KEY, the key is just ignored. (Use ``id`` parameter in such a case)" - -msgid "``id``" -msgstr "``id``" - -msgid "" -"It specifies the id of record to delete. If you specify ``id`` parameter, " -"you must not specify ``key`` parameter." -msgstr "" -"It specifies the id of record to delete. If you specify ``id`` parameter, " -"you must not specify ``key`` parameter." - -msgid "" -"It specifies the expression of grn_expr to identify the record. If you " -"specify ``filter`` parameter, you must not specify ``key`` and ``id`` " -"parameter." -msgstr "" -"It specifies the expression of grn_expr to identify the record. If you " -"specify ``filter`` parameter, you must not specify ``key`` and ``id`` " -"parameter." - -msgid "" -"If command succeeded, it returns true, otherwise it returns false on error." -msgstr "" -"If command succeeded, it returns true, otherwise it returns false on error." - -msgid "``dump``" -msgstr "" - -msgid "dump - データベースのスキーマとデータを出力する" -msgstr "dump - データベースのスキーマとデータを出力する" - -msgid "" -"Groonga組込コマンドの一つであるdumpについて説明します。組込コマンドは、" -"groonga実行ファイルの引数、標準入力、 またはソケット経由でgroongaサーバにリク" -"エストを送信することによって実行します。" -msgstr "" - -msgid "" -"dumpはデータベースのスキーマとデータを後から読み込めるフォーマットで出力しま" -"す。dumpの結果は大きくなるため、 主にコマンドラインから使うことを想定していま" -"す。データベースのバックアップが主な利用方法です。" -msgstr "" - -msgid "" -"dumpが出力するフォーマットは直接Groongaが解釈できるフォーマットです。そのた" -"め、以下のようにしてデータベース>をコピーすることができます。::" -msgstr "" - -msgid "データベース内のすべてのデータを出力::" -msgstr "データベース内のすべてのデータを出力::" - -msgid "データベース内のスキーマと特定のテーブルのデータのみ出力::" -msgstr "データベース内のスキーマと特定のテーブルのデータのみ出力::" - -msgid "``tables``" -msgstr "``tables``" - -msgid "" -"出力対象のテーブルを「,」（カンマ）区切りで指定します。存在しないテーブルを指" -"定した場合は無視されます。" -msgstr "" -"出力対象のテーブルを「,」（カンマ）区切りで指定します。存在しないテーブルを指" -"定した場合は無視されます。" - -msgid "" -"データベースのスキーマとデータをGroongaの組み込みコマンド呼び出し形式で出力し" -"ます。output_type指定は無視されます。" -msgstr "" -"データベースのスキーマとデータをGroongaの組み込みコマンド呼び出し形式で出力し" -"ます。output_type指定は無視されます。" - -msgid "``load``" -msgstr "``load``" - -msgid "" -"``load`` loads data as records in the current database and updates values of " -"each columns." -msgstr "" -"``load`` loads data as records in the current database and updates values of " -"each columns." - -msgid "``values``" -msgstr "``values``" - -msgid "" -"It specifies values loaded to records. Values should satisfy ``input_type`` " -"format. If you specify \"json\" as ``input_type``, you can choose a format " -"from below:" -msgstr "" -"It specifies values loaded to records. Values should satisfy ``input_type`` " -"format. If you specify \"json\" as ``input_type``, you can choose a format " -"from below:" - -msgid "" -"[[COLUMN_NAME1, COLUMN_NAME2,..], [VALUE1, VALUE2,..], [VALUE1, " -"VALUE2,..],..]" -msgstr "" -"[[COLUMN_NAME1, COLUMN_NAME2,..], [VALUE1, VALUE2,..], [VALUE1, " -"VALUE2,..],..]" - -msgid "``Format 1:``" -msgstr "``Format 1:``" - -msgid "" -"[{COLUMN_NAME1: VALUE1, COLUMN_NAME2: VALUE2}, {COLUMN_NAME1: VALUE1, " -"COLUMN_NAME2: VALUE2},..]" -msgstr "" -"[{COLUMN_NAME1: VALUE1, COLUMN_NAME2: VALUE2}, {COLUMN_NAME1: VALUE1, " -"COLUMN_NAME2: VALUE2},..]" - -msgid "``Format 2:``" -msgstr "``Format 2:``" - -msgid "" -"``[COLUMN_NAME1, COLUMN_NAME2,..]`` format in ``Format 1`` is effective only " -"when ``column`` parameter isn't specified." -msgstr "" -"``[COLUMN_NAME1, COLUMN_NAME2,..]`` format in ``Format 1`` is effective only " -"when ``column`` parameter isn't specified." - -msgid "" -"When a target table contains primary key, you must specify ``_key`` column " -"(pseudo column associated primary key) as the one of ``COLUMN_NAME``." -msgstr "" -"When a target table contains primary key, you must specify ``_key`` column " -"(pseudo column associated primary key) as the one of ``COLUMN_NAME``." - -msgid "" -"If ``values`` isn't specified any values, they are read from the standard " -"input until all opened parenthes match their closed ones. You don't have to " -"enclose them with single-quotes or double-quotes, but if you specified " -"values with ``values`` parameter, you should do." -msgstr "" -"If ``values`` isn't specified any values, they are read from the standard " -"input until all opened parenthes match their closed ones. You don't have to " -"enclose them with single-quotes or double-quotes, but if you specified " -"values with ``values`` parameter, you should do." - -msgid "" -"In following values, you also don't have to enclose any spaces (' ') with " -"single-quotes or double-quotes." -msgstr "" -"In following values, you also don't have to enclose any spaces (' ') with " -"single-quotes or double-quotes." - -msgid "It specifies a table name you want to add records." -msgstr "It specifies a table name you want to add records." - -msgid "``columns``" -msgstr "``columns``" - -msgid "It specifies column names in added records with comma separations." -msgstr "It specifies column names in added records with comma separations." - -msgid "``ifexists``" -msgstr "``ifexists``" - -msgid "" -"It specifies executed ``grn_expr`` string when the same primary key as added " -"records already exists in your table. If ``ifexists`` specifies ``grn_expr`` " -"string (default: true) and its value is true, values in other (all columns " -"excluding ``_key`` column) columns is updated." -msgstr "" -"It specifies executed ``grn_expr`` string when the same primary key as added " -"records already exists in your table. If ``ifexists`` specifies ``grn_expr`` " -"string (default: true) and its value is true, values in other (all columns " -"excluding ``_key`` column) columns is updated." - -msgid "``input_type``" -msgstr "``input_type``" - -msgid "It specifies an input format for ``values``. It supports JSON only." -msgstr "It specifies an input format for ``values``. It supports JSON only." - -msgid "Here is an example to add records to \"Entry\" table. ::" -msgstr "Here is an example to add records to \"Entry\" table. ::" - -msgid "This example shows how to add values from standard input. ::" -msgstr "This example shows how to add values from standard input. ::" - -msgid "JSON format" -msgstr "JSON format" - -msgid "``load`` returns the number of added records such as ::" -msgstr "``load`` returns the number of added records such as ::" - -msgid "``lock_clear``" -msgstr "" - -# 5f540a5f2ca54b17967367fbaedac173 -msgid "" -"``lock_clear`` command clear the lock of the target object recursively. The " -"target object is one of database, table and column." -msgstr "" - -# b84e0f92ad904b7da4680d8dd52c56b5 -msgid "" -"This is a dangerous command. You must not use this command while other " -"process or thread is doing a write operation to the target object. If you do " -"it, your database may be broken and/or your process may be crashed." -msgstr "" - -msgid "``truncate`` command takes only one parameter." -msgstr "``truncate`` command takes only one parameter." - -msgid "There is no required parameter::" -msgstr "" - -# f6d3c67dcb734afb8331db59c2238be8 -msgid "" -"If ``target_name`` parameters is omitted, database is used for the target " -"object. It means that all locks in the database are cleared." -msgstr "" - -msgid "Here is an example to clear all locks in the database::" -msgstr "" - -msgid "" -"Here is an example to clear locks of ``Entry`` table and ``Entry`` table " -"columns::" -msgstr "" - -msgid "Here is an example to clear the lock of ``Site.title`` column::" -msgstr "" - -msgid "``target_name``" -msgstr "" - -msgid "It specifies the name of table or column." -msgstr "" - -# 212aa475a95a41af82bbd4c742923d23 -msgid "If you don't specify it, database is used for the target object." -msgstr "" - -# 347992f875914a41bb2003924323f072 -msgid "The default is none. It means that the target object is database." -msgstr "" - -msgid "``log_level``" -msgstr "``log_level``" - -msgid "log_level - ログ出力レベルの設定" -msgstr "log_level - ログ出力レベルの設定" - -msgid "" -"Groonga組込コマンドの一つであるlog_levelについて説明します。組込コマンドは、" -"groonga実行ファイルの引数、標準>入力、またはソケット経由でgroongaサーバにリク" -"エストを送信することによって実行します。" -msgstr "" - -msgid "log_levelは、ログ出力レベルを設定します。" -msgstr "log_levelは、ログ出力レベルを設定します。" - -msgid "``level``" -msgstr "``level``" - -msgid "設定するログ出力レベルの値を以下のいずれかで指定します。" -msgstr "設定するログ出力レベルの値を以下のいずれかで指定します。" - -msgid "EMERG ALERT CRIT error warning notice info debug" -msgstr "EMERG ALERT CRIT error warning notice info debug" - -msgid ":doc:`log_put` :doc:`log_reopen`" -msgstr ":doc:`log_put` :doc:`log_reopen`" - -msgid "``log_put``" -msgstr "``log_put``" - -msgid "log_put - ログ出力" -msgstr "log_put - ログ出力" - -msgid "" -"groonga組込コマンドの一つであるlog_putについて説明します。組込コマンドは、" -"groonga実行ファイルの引数、標準入>力、またはソケット経由でgroongaサーバにリク" -"エストを送信することによって実行します。" -msgstr "" - -msgid "log_putは、ログにmessageを出力します。" -msgstr "log_putは、ログにmessageを出力します。" - -msgid "``message``" -msgstr "``message``" - -msgid "出力する文字列を指定します。" -msgstr "出力する文字列を指定します。" - -msgid ":doc:`log_level` :doc:`log_reopen`" -msgstr ":doc:`log_level` :doc:`log_reopen`" - -msgid "``log_reopen``" -msgstr "" - -msgid "log_reopen - ログファイルの再読み込み" -msgstr "log_reopen - ログファイルの再読み込み" - -msgid "" -"Groonga組込コマンドの一つであるlog_reopenについて説明します。組込コマンドは、" -"groonga実行ファイルの引数、標準 入力、またはソケット経由でgroongaサーバにリク" -"エストを送信することによって実行します。" -msgstr "" - -msgid "log_reopenは、ログファイルを再読み込みします。" -msgstr "log_reopenは、ログファイルを再読み込みします。" - -msgid "現在、デフォルトのログ関数を用いている場合のみに対応しています。" -msgstr "現在、デフォルトのログ関数を用いている場合のみに対応しています。" - -msgid "log_reopenを用いたログのローテーション" -msgstr "log_reopenを用いたログのローテーション" - -msgid "" -"ログファイルをmvなどで移動する。 ログはmvで移動された先のファイルに書き込まれ" -"る。" -msgstr "" -"ログファイルをmvなどで移動する。 ログはmvで移動された先のファイルに書き込まれ" -"る。" - -msgid "log_reopenコマンドを実行する。" -msgstr "log_reopenコマンドを実行する。" - -msgid "" -"既存のログファイル名と同じファイル名で、新たなログファイルが作成される。 今後" -"のログは新たなログファイルに書き込まれる。" -msgstr "" -"既存のログファイル名と同じファイル名で、新たなログファイルが作成される。 今後" -"のログは新たなログファイルに書き込まれる。" - -msgid "ありません。" -msgstr "ありません。" - -msgid ":doc:`log_level` :doc:`log_put`" -msgstr ":doc:`log_level` :doc:`log_put`" - -msgid "``normalize``" -msgstr "``normalize``" - -msgid "" -"``normalize`` command is the experimental feature. This command may be " -"changed in the future." -msgstr "" -"``normalize`` command is the experimental feature. This command may be " -"changed in the future." - -msgid "``normalize`` command normalizes text by the specified normalizer." -msgstr "``normalize`` command normalizes text by the specified normalizer." - -msgid "" -"There is no need to create table to use ``normalize`` command. It is useful " -"for you to check the results of normalizer." -msgstr "" -"There is no need to create table to use ``normalize`` command. It is useful " -"for you to check the results of normalizer." - -msgid "" -"``normalize`` commands has two required parameters. They are ``normalizer`` " -"and ``string``." -msgstr "" -"``normalize`` commands has two required parameters. They are ``normalizer`` " -"and ``string``." - -msgid "Here is a simple example of ``normalize`` command." -msgstr "Here is a simple example of ``normalize`` command." - -msgid "This section describes parameters of ``normalizer``." -msgstr "This section describes parameters of ``normalizer``." - -msgid "Required parameter" -msgstr "Required parameter" - -msgid "There are required parameters, ``normalizer`` and ``string``." -msgstr "There are required parameters, ``normalizer`` and ``string``." - -msgid "``normalizer``" -msgstr "``normalizer``" - -msgid "" -"It specifies the normalizer name. ``normalize`` command uses the normalizer " -"that is named ``normalizer``." -msgstr "" -"It specifies the normalizer name. ``normalize`` command uses the normalizer " -"that is named ``normalizer``." - -msgid "See :doc:`/reference/normalizers` about built-in normalizers." -msgstr "See :doc:`/reference/normalizers` about built-in normalizers." - -msgid "Here is an example to use built-in ``NormalizerAuto`` normalizer." -msgstr "Here is an example to use built-in ``NormalizerAuto`` normalizer." - -msgid "" -"If you want to use other normalizers, you need to register additional " -"normalizer plugin by :doc:`register` command. For example, you can use MySQL " -"compatible normalizer by registering `groonga-normalizer-mysql <https://" -"github.com/groonga/groonga-normalizer-mysql>`_." -msgstr "" -"If you want to use other normalizers, you need to register additional " -"normalizer plugin by :doc:`register` command. For example, you can use MySQL " -"compatible normalizer by registering `groonga-normalizer-mysql <https://" -"github.com/groonga/groonga-normalizer-mysql>`_." - -msgid "``string``" -msgstr "``string``" - -msgid "It specifies any string which you want to normalize." -msgstr "It specifies any string which you want to normalize." - -msgid "" -"If you want to include spaces in ``string``, you need to quote ``string`` by " -"single quotation (``'``) or double quotation (``\"``)." -msgstr "" -"If you want to include spaces in ``string``, you need to quote ``string`` by " -"single quotation (``'``) or double quotation (``\"``)." - -msgid "Here is an example to use spaces in ``string``." -msgstr "Here is an example to use spaces in ``string``." - -msgid "Optional parameters" -msgstr "Optional parameters" - -msgid "There are optional parameters." -msgstr "There are optional parameters." - -msgid "" -"It specifies a normalization customize options. You can specify multiple " -"options separated by \"``|``\". For example, ``REMOVE_BLANK|WITH_TYPES``." -msgstr "" -"It specifies a normalization customize options. You can specify multiple " -"options separated by \"``|``\". For example, ``REMOVE_BLANK|WITH_TYPES``." - -msgid "Here are available flags." -msgstr "Here are available flags." - -msgid "``NONE``" -msgstr "``NONE``" - -msgid "Just ignored." -msgstr "Just ignored." - -msgid "``REMOVE_BLANK``" -msgstr "``REMOVE_BLANK``" - -msgid "``WITH_TYPES``" -msgstr "``WITH_TYPES``" - -msgid "``WITH_CHECKS``" -msgstr "``WITH_CHECKS``" - -msgid "``REMOVE_TOKENIZED_DELIMITER``" -msgstr "``REMOVE_TOKENIZED_DELIMITER``" - -msgid "Here is an example that uses ``REMOVE_BLANK``." -msgstr "Here is an example that uses ``REMOVE_BLANK``." - -msgid "Here is an example that uses ``WITH_TYPES``." -msgstr "Here is an example that uses ``WITH_TYPES``." - -msgid "Here is an example that uses ``REMOVE_TOKENIZED_DELIMITER``." -msgstr "Here is an example that uses ``REMOVE_TOKENIZED_DELIMITER``." - -msgid "``normalized_text``" -msgstr "``normalized_text``" - -msgid "``normalized_text`` is an object that has the following attributes." -msgstr "``normalized_text`` is an object that has the following attributes." - -msgid "Name" -msgstr "Name" - -msgid "``normalized``" -msgstr "``normalized``" - -msgid "The normalized text." -msgstr "The normalized text." - -msgid "``types``" -msgstr "``types``" - -msgid "" -"An array of types of the normalized text. The N-th ``types`` shows the type " -"of the N-th character in ``normalized``." -msgstr "" -"An array of types of the normalized text. The N-th ``types`` shows the type " -"of the N-th character in ``normalized``." - -msgid ":doc:`/reference/normalizers`" -msgstr ":doc:`/reference/normalizers`" - -msgid "``normalizer_list``" -msgstr "" - -msgid "``normalizer_list`` command lists normalizers in a database." -msgstr "" - -msgid "``normalizer_list`` command takes no parameter. ::" -msgstr "" - -msgid "Here is a simple example." -msgstr "Here is a simple example." - -msgid "It returns normalizers in a database." -msgstr "" - -msgid "" -"``normalizer_list`` command returns normalizers. Each normalizers has an " -"attribute that contains the name. The attribute will be increased in the " -"feature::" -msgstr "" - -msgid "``normalizers``" -msgstr "" - -msgid "" -"``normalizers`` is an array of normalizer. Normalizer is an object that has " -"the following attributes." -msgstr "" - -msgid "Normalizer name." -msgstr "" - -msgid ":doc:`/reference/commands/normalize`" -msgstr "" - -msgid "``quit``" -msgstr "``quit``" - -msgid "quit - セッション終了" -msgstr "quit - セッション終了" - -msgid "" -"Groonga組込コマンドの一つであるquitについて説明します。組込コマンドは、" -"groonga実行ファイルの引数、標準入力、 またはソケット経由でgroongaサーバにリク" -"エストを送信することによって実行します。" -msgstr "" - -msgid "" -"quitは、groongaプロセスとのセッションを終了します。クライアントプロセスならば" -"groongaプロセスとの接続を切りま す。" -msgstr "" - -msgid "``range_filter``" -msgstr "" - -msgid "TODO: write me" -msgstr "" - -msgid ":doc:`/reference/commands/select`" -msgstr ":doc:`/reference/commands/select`" - -msgid "``register``" -msgstr "" - -msgid "" -"``register`` command registers a plugin. You need to register a plugin " -"before you use a plugin." -msgstr "" -"``register`` command registers a plugin. You need to register a plugin " -"before you use a plugin." - -msgid "" -"You need just one ``register`` command for a plugin in the same database " -"because registered plugin information is written into the database. When " -"you restart your ``groonga`` process, ``groonga`` process loads all " -"registered plugins without ``register`` command." -msgstr "" -"You need just one ``register`` command for a plugin in the same database " -"because registered plugin information is written into the database. When " -"you restart your ``groonga`` process, ``groonga`` process loads all " -"registered plugins without ``register`` command." - -msgid "Registered plugins can't be removed for now." -msgstr "Registered plugins can't be removed for now." - -msgid "``register`` has a parameter ``path``. It is required parameter::" -msgstr "``register`` has a parameter ``path``. It is required parameter::" - -msgid "" -"Here is a sample that registers ``QueryExpanderTSV`` query expander that is " -"included in ``${PREFIX}/lib/groonga/plugins/query_expanders/tsv.so``." -msgstr "" -"Here is a sample that registers ``QueryExpanderTSV`` query expander that is " -"included in ``${PREFIX}/lib/groonga/plugins/query_expanders/tsv.so``." - -msgid "" -"You can omit ``${PREFIX}/lib/groonga/plugins/`` and suffix (``.so``). They " -"are completed automatically." -msgstr "" -"You can omit ``${PREFIX}/lib/groonga/plugins/`` and suffix (``.so``). They " -"are completed automatically." - -msgid "" -"You can specify absolute path such as ``register /usr/lib/groonga/plugins/" -"query_expanders/tsv.so``." -msgstr "" -"You can specify absolute path such as ``register /usr/lib/groonga/plugins/" -"query_expanders/tsv.so``." - -msgid "``register`` returns ``true`` as body on success such as::" -msgstr "``register`` returns ``true`` as body on success such as::" - -msgid "If ``register`` fails, error details are in ``HEADER``." -msgstr "If ``register`` fails, error details are in ``HEADER``." - -msgid "See :doc:`/reference/command/output_format` for ``HEADER``." -msgstr "See :doc:`/reference/command/output_format` for ``HEADER``." - -msgid "``request_cancel``" -msgstr "" - -msgid "``request_cancel`` command is an experimental feature." -msgstr "" - -# cfec1fe5c74d4ee0a9eda2335e43c562 -msgid "``request_cancel`` command cancels a running request." -msgstr "" - -msgid "There are some limitations:" -msgstr "" - -# d702ca1e9c4d40088b66e285770e2d28 -msgid "" -"Request ID must be managed by user. (You need to assign unique key for each " -"request.)" -msgstr "" - -# 30ea816b2a5a4b9eb582be3f4e4de7ca -msgid "" -"Cancel request may be ignored. (You can send ``request_cancel`` command " -"multiple times for the same request ID.)" -msgstr "" - -# a1ec5a736a214ad08a04f219b81cafe6 -msgid "" -"Only multithreading type Groonga server is supported. (You can use with :doc:" -"`/reference/executables/groonga` based server but can't use with :doc:`/" -"reference/executables/groonga-httpd`.)" -msgstr "" - -msgid "See :doc:`/reference/command/request_id` about request ID." -msgstr "" - -# 0da91ba692b24b8f831442eab7d223cd -msgid "" -"If request is canceled, the canceled request has ``-5`` " -"(``GRN_INTERRUPTED_FUNCTION_CALL``) as :doc:`/reference/command/return_code`." -msgstr "" - -msgid "``request_cancel`` command takes only one parameter." -msgstr "" - -msgid "The required parameter is only ``id``::" -msgstr "" - -msgid "Here is an example of ``request_cancel`` command::" -msgstr "" - -# dba222ab0deb473abc00f0e59fc768b1 -msgid "" -"Assume that the first ``select`` command takes a long time. ``unique-id-1`` " -"request ID is assigned to the ``select`` command by ``request_id=unique-" -"id-1`` parameter." -msgstr "" - -# 7a7bca8c029b4e679567b1c69c015a0d -msgid "" -"The second ``request_cancel`` command passes ``id=unique-id-1`` parameter. " -"``unique-id-1`` is the same request ID passed in ``select`` command." -msgstr "" - -# b978256ad5624f2aae83d4a5586c1370 -msgid "" -"The ``select`` command may not be canceled immediately. And the cancel " -"request may be ignored." -msgstr "" - -# a62832d3c63344ad906168d148e02f67 -msgid "" -"You can send cancel request for the same request ID multiple times. If the " -"target request is canceled or finished, ``\"canceled\"`` value is changed to " -"``false`` from ``true``::" -msgstr "" - -# a6a03a484d984e9bb52f4e0d30d213d3 -msgid "" -"If the ``select`` command is canceled, response of the ``select`` command " -"has ``-5`` (``GRN_INTERRUPTED_FUNCTION_CALL``) as :doc:`/reference/command/" -"return_code`::" -msgstr "" - -msgid "This section describes parameters of ``request_cancel``." -msgstr "" - -msgid "There is required parameter, ``id``." -msgstr "" - -msgid "It specifies the ID for the target request." -msgstr "" - -# 778460b3299a42a6a7c83c8252287105 -msgid "``request_cancel`` command returns the result of the cancel request::" -msgstr "" - -# dc61e4c01c314a3388905976cfd78c8d -msgid "The ID of the target request." -msgstr "" - -# f2ce2ecb9db945f698f70303b71c85fb -msgid "``CANCEL_REQUEST_IS_ACCEPTED_OR_NOT``" -msgstr "" - -# 4ddc8d24dd054e0b936611fb2a7f0808 -msgid "" -"If the cancel request is accepted, this is ``true``, otherwise this is " -"``false``." -msgstr "" - -# 7b2a86467ead413d8ec0337f6f3188ab -msgid "" -"Note that \"cancel request is accepted\" doesn't means that \"the target " -"request is canceled\". It just means \"cancel request is notified to the " -"target request but the cancel request may be ignored by the target request\"." -msgstr "" - -# b81cee5eafa94fcbbfa6f3da88dd32de -msgid "" -"If request assigned with the request ID doesn't exist, this is ``false``." -msgstr "" - -msgid ":doc:`/reference/command/request_id`" -msgstr "" - -msgid "``ruby_eval``" -msgstr "``ruby_eval``" - -msgid "``ruby_eval`` command evaluates Ruby script and returns the result." -msgstr "``ruby_eval`` command evaluates Ruby script and returns the result." - -msgid "``ruby_eval`` has one required parameter::" -msgstr "``ruby_eval`` has one required parameter::" - -msgid "" -"You can execute any scripts which mruby supports by calling ``ruby_eval``." -msgstr "" -"You can execute any scripts which mruby supports by calling ``ruby_eval``." - -msgid "Here is an example that just calculate ``1 + 2`` as Ruby script." -msgstr "Here is an example that just calculate ``1 + 2`` as Ruby script." - -msgid "Register ``ruby/eval`` plugin to use ``ruby_eval`` command in advance." -msgstr "Register ``ruby/eval`` plugin to use ``ruby_eval`` command in advance." - -msgid "" -"Note that ``ruby_eval`` is implemented as an experimental plugin, and the " -"specification may be changed in the future." -msgstr "" -"Note that ``ruby_eval`` is implemented as an experimental plugin, and the " -"specification may be changed in the future." - -msgid "``script``" -msgstr "``script``" - -msgid "It specifies the Ruby script which you want to evaluate." -msgstr "It specifies the Ruby script which you want to evaluate." - -msgid "" -"``ruby_eval`` returns the evaluated result with metadata such as exception " -"information (Including metadata isn't implemented yet)::" -msgstr "" -"``ruby_eval`` returns the evaluated result with metadata such as exception " -"information (Including metadata isn't implemented yet)::" - -msgid "``EVALUATED_VALUE``" -msgstr "``EVALUATED_VALUE``" - -msgid "``EVALUATED_VALUE`` is the evaludated value of ``ruby_script``." -msgstr "``EVALUATED_VALUE`` is the evaludated value of ``ruby_script``." - -msgid "" -"``ruby_eval`` supports only a number for evaluated value for now. Supported " -"types will be increased in the future." -msgstr "" -"``ruby_eval`` supports only a number for evaluated value for now. Supported " -"types will be increased in the future." - -msgid "``ruby_load``" -msgstr "``ruby_load``" - -msgid "``ruby_load`` command loads specified Ruby script." -msgstr "``ruby_load`` command loads specified Ruby script." - -msgid "``ruby_load`` has one required parameter::" -msgstr "``ruby_load`` has one required parameter::" - -msgid "" -"You can load any script file which mruby supports by calling ``ruby_load``." -msgstr "" -"You can load any script file which mruby supports by calling ``ruby_load``." - -msgid "Here is an example that just load ``expression.rb`` as Ruby script." -msgstr "Here is an example that just load ``expression.rb`` as Ruby script." - -msgid "Register ``ruby/load`` plugin to use ``ruby_load`` command in advance." -msgstr "Register ``ruby/load`` plugin to use ``ruby_load`` command in advance." - -msgid "" -"Note that ``ruby_load`` is implemented as an experimental plugin, and the " -"specification may be changed in the future." -msgstr "" -"Note that ``ruby_load`` is implemented as an experimental plugin, and the " -"specification may be changed in the future." - -msgid "``path``" -msgstr "``path``" - -msgid "It specifies the Ruby script path which you want to load." -msgstr "It specifies the Ruby script path which you want to load." - -msgid "" -"``ruby_load`` returns the loaded result with metadata such as exception " -"information (Including metadata isn't implemented yet)::" -msgstr "" -"``ruby_load`` returns the loaded result with metadata such as exception " -"information (Including metadata isn't implemented yet)::" - -msgid "``LOADED_VALUE``" -msgstr "``LOADED_VALUE``" - -msgid "``LOADED_VALUE`` is the loaded value of ruby script." -msgstr "``LOADED_VALUE`` is the loaded value of ruby script." - -msgid "" -"``ruby_load`` just return ``null`` as ``LOADED_VALUE`` for now, it will be " -"supported in the future." -msgstr "" -"``ruby_load`` just return ``null`` as ``LOADED_VALUE`` for now, it will be " -"supported in the future." - -msgid ":doc:`/reference/commands/ruby_eval`" -msgstr ":doc:`/reference/commands/ruby_eval`" - -msgid "``select``" -msgstr "``select``" - -msgid "" -"``select`` searches records that are matched to specified conditions from a " -"table and then outputs them." -msgstr "" -"``select`` searches records that are matched to specified conditions from a " -"table and then outputs them." - -msgid "" -"``select`` is the most important command in groonga. You need to understand " -"``select`` to use the full power of groonga." -msgstr "" -"``select`` is the most important command in groonga. You need to understand " -"``select`` to use the full power of groonga." - -msgid "" -"``select`` has many parameters. The required parameter is only ``table`` and " -"others are optional::" -msgstr "" -"``select`` has many parameters. The required parameter is only ``table`` and " -"others are optional::" - -msgid "``select`` has the following named parameters for advanced drilldown:" -msgstr "" - -msgid "``drilldown[${LABEL}].keys=null``" -msgstr "" - -msgid "``drilldown[${LABEL}].sortby=null``" -msgstr "" - -msgid "``drilldown[${LABEL}].output_columns=\"_key, _nsubrecs\"``" -msgstr "" - -msgid "``drilldown[${LABEL}].offset=0``" -msgstr "" - -msgid "``drilldown[${LABEL}].limit=10``" -msgstr "" - -msgid "``drilldown[${LABEL}].calc_types=NONE``" -msgstr "" - -msgid "``drilldown[${LABEL}].calc_target=null``" -msgstr "" - -msgid "" -"You can use one or more alphabets, digits, ``_`` and ``.`` for ``${LABEL}``. " -"For example, ``parent.sub1`` is a valid ``${LABEL}``." -msgstr "" - -msgid "Parameters that have the same ``${LABEL}`` are grouped." -msgstr "" - -msgid "For example, the following parameters specify one drilldown:" -msgstr "" - -msgid "``--drilldown[label].keys column``" -msgstr "" - -msgid "``--drilldown[label].sortby -_nsubrecs``" -msgstr "" - -msgid "The following parameters specify two drilldowns:" -msgstr "" - -msgid "``--drilldown[label1].keys column1``" -msgstr "" - -msgid "``--drilldown[label1].sortby -_nsubrecs``" -msgstr "" - -msgid "``--drilldown[label2].keys column2``" -msgstr "" - -msgid "``--drilldown[label2].sortby _key``" -msgstr "" - -msgid "" -"Let's learn about ``select`` usage with examples. This section shows many " -"popular usages." -msgstr "" -"Let's learn about ``select`` usage with examples. This section shows many " -"popular usages." - -msgid "" -"There is a table, ``Entries``, for blog entries. An entry has title, " -"content, the number of likes for the entry and tag. Title is key of " -"``Entries``. Content is value of ``Entries.content`` column. The number of " -"likes is value of ``Entries.n_likes`` column. Tag is value of ``Entries." -"tag`` column." -msgstr "" - -msgid "" -"``Entries._key`` column and ``Entries.content`` column are indexed using " -"``TokenBigram`` tokenizer. So both ``Entries._key`` and ``Entries.content`` " -"are fulltext search ready." -msgstr "" -"``Entries._key`` column and ``Entries.content`` column are indexed using " -"``TokenBigram`` tokenizer. So both ``Entries._key`` and ``Entries.content`` " -"are fulltext search ready." - -msgid "OK. The schema and data for examples are ready." -msgstr "OK. The schema and data for examples are ready." - -msgid "Simple usage" -msgstr "Simple usage" - -msgid "" -"Here is the most simple usage with the above schema and data. It outputs all " -"records in ``Entries`` table." -msgstr "" -"Here is the most simple usage with the above schema and data. It outputs all " -"records in ``Entries`` table." - -msgid "" -"Why does the command output all records? There are two reasons. The first " -"reason is that the command doesn't specify any search conditions. No search " -"condition means all records are matched. The second reason is that the " -"number of all records is 5. ``select`` command outputs 10 records at a " -"maximum by default. There are only 5 records. It is less than 10. So the " -"command outputs all records." -msgstr "" -"Why does the command output all records? There are two reasons. The first " -"reason is that the command doesn't specify any search conditions. No search " -"condition means all records are matched. The second reason is that the " -"number of all records is 5. ``select`` command outputs 10 records at a " -"maximum by default. There are only 5 records. It is less than 10. So the " -"command outputs all records." - -msgid "Search conditions" -msgstr "Search conditions" - -msgid "" -"Search conditions are specified by ``query`` or ``filter``. You can also " -"specify both ``query`` and ``filter``. It means that selected records must " -"be matched against both ``query`` and ``filter``." -msgstr "" -"Search conditions are specified by ``query`` or ``filter``. You can also " -"specify both ``query`` and ``filter``. It means that selected records must " -"be matched against both ``query`` and ``filter``." - -msgid "Search condition: ``query``" -msgstr "Search condition: ``query``" - -msgid "" -"``query`` is designed for search box in Web page. Imagine a search box in " -"google.com. You specify search conditions for ``query`` as space separated " -"keywords. For example, ``search engine`` means a matched record should " -"contain two words, ``search`` and ``engine``." -msgstr "" -"``query`` is designed for search box in Web page. Imagine a search box in " -"google.com. You specify search conditions for ``query`` as space separated " -"keywords. For example, ``search engine`` means a matched record should " -"contain two words, ``search`` and ``engine``." - -msgid "" -"Normally, ``query`` parameter is used for specifying fulltext search " -"conditions. It can be used for non fulltext search conditions but ``filter`` " -"is used for the propose." -msgstr "" -"Normally, ``query`` parameter is used for specifying fulltext search " -"conditions. It can be used for non fulltext search conditions but ``filter`` " -"is used for the propose." - -msgid "" -"``query`` parameter is used with ``match_columns`` parameter when ``query`` " -"parameter is used for specifying fulltext search conditions. " -"``match_columns`` specifies which columnes and indexes are matched against " -"``query``." -msgstr "" -"``query`` parameter is used with ``match_columns`` parameter when ``query`` " -"parameter is used for specifying fulltext search conditions. " -"``match_columns`` specifies which columnes and indexes are matched against " -"``query``." - -msgid "Here is a simple ``query`` usage example." -msgstr "Here is a simple ``query`` usage example." - -msgid "" -"The ``select`` command searches records that contain a word ``fast`` in " -"``content`` column value from ``Entries`` table." -msgstr "" -"The ``select`` command searches records that contain a word ``fast`` in " -"``content`` column value from ``Entries`` table." - -msgid "" -"``query`` has query syntax but its deatils aren't described here. See :doc:`/" -"reference/grn_expr/query_syntax` for datails." -msgstr "" -"``query`` has query syntax but its deatils aren't described here. See :doc:`/" -"reference/grn_expr/query_syntax` for datails." - -msgid "Search condition: ``filter``" -msgstr "Search condition: ``filter``" - -msgid "" -"``filter`` is designed for complex search conditions. You specify search " -"conditions for ``filter`` as ECMAScript like syntax." -msgstr "" -"``filter`` is designed for complex search conditions. You specify search " -"conditions for ``filter`` as ECMAScript like syntax." - -msgid "Here is a simple ``filter`` usage example." -msgstr "Here is a simple ``filter`` usage example." - -msgid "" -"The ``select`` command searches records that contain a word ``fast`` in " -"``content`` column value and has ``Groonga`` as ``_key`` from ``Entries`` " -"table. There are three operators in the command, ``@``, ``&&`` and ``==``. " -"``@`` is fulltext search operator. ``&&`` and ``==`` are the same as " -"ECMAScript. ``&&`` is logical AND operator and ``==`` is equality operator." -msgstr "" -"The ``select`` command searches records that contain a word ``fast`` in " -"``content`` column value and has ``Groonga`` as ``_key`` from ``Entries`` " -"table. There are three operators in the command, ``@``, ``&&`` and ``==``. " -"``@`` is fulltext search operator. ``&&`` and ``==`` are the same as " -"ECMAScript. ``&&`` is logical AND operator and ``==`` is equality operator." - -msgid "" -"``filter`` has more operators and syntax like grouping by ``(...)`` its " -"details aren't described here. See :doc:`/reference/grn_expr/script_syntax` " -"for datails." -msgstr "" - -msgid "Paging" -msgstr "Paging" - -msgid "" -"You can specify range of outputted records by ``offset`` and ``limit``. Here " -"is an example to output only the 2nd record." -msgstr "" -"You can specify range of outputted records by ``offset`` and ``limit``. Here " -"is an example to output only the 2nd record." - -msgid "" -"``offset`` is zero-based. ``--offset 1`` means output range is started from " -"the 2nd record." -msgstr "" - -msgid "" -"``limit`` specifies the max number of output records. ``--limit 1`` means " -"the number of output records is 1 at a maximium. If no records are matched, " -"``select`` command outputs no records." -msgstr "" -"``limit`` specifies the max number of output records. ``--limit 1`` means " -"the number of output records is 1 at a maximium. If no records are matched, " -"``select`` command outputs no records." - -msgid "The total number of records" -msgstr "The total number of records" - -msgid "" -"You can use ``--limit 0`` to retrieve the total number of recrods without " -"any contents of records." -msgstr "" -"You can use ``--limit 0`` to retrieve the total number of recrods without " -"any contents of records." - -msgid "" -"``--limit 0`` is also useful for retrieving only the number of matched " -"records." -msgstr "" -"``--limit 0`` is also useful for retrieving only the number of matched " -"records." - -msgid "Drilldown" -msgstr "" - -msgid "" -"You can get additional grouped results against the search result in one " -"``select``. You need to use two or more ``SELECT``s in SQL but ``select`` in " -"Groonga can do it in one ``select``." -msgstr "" - -msgid "" -"This feature is called as `drilldown <http://en.wikipedia.org/wiki/" -"Drill_down>`_ in Groonga. It's also called as `faceted search <http://en." -"wikipedia.org/wiki/Faceted_search>`_ in other search engine." -msgstr "" - -msgid "For example, think about the following situation." -msgstr "" - -msgid "You search entries that has ``fast`` word:" -msgstr "" - -msgid "" -"You want to use ``tag`` for additional search condition like ``--filter " -"'content @ \"fast\" && tag == \"???\"``. But you don't know suitable tag " -"until you see the result of ``content @ \"fast\"``." -msgstr "" - -msgid "" -"If you know the number of matched records of each available tag, you can " -"choose suitable tag. You can use drilldown for the case:" -msgstr "" - -msgid "" -"``--drilldown tag`` returns a list of pair of available tag and the number " -"of matched records. You can avoid \"no hit search\" case by choosing a tag " -"from the list. You can also avoid \"too many search results\" case by " -"choosing a tag that the number of matched records is few from the list." -msgstr "" - -msgid "You can create the following UI with the drilldown results:" -msgstr "" - -msgid "" -"Links to narrow search results. (Users don't need to input a search query by " -"their keyboard. They just click a link.)" -msgstr "" - -msgid "Most EC sites use the UI. See side menu at Amazon." -msgstr "" - -msgid "" -"Groonga supports not only counting grouped records but also finding the " -"maximum and/or minimum value from grouped records, summing values in grouped " -"records and so on. See :ref:`select-drilldown-related-parameters` for " -"details." -msgstr "" - -msgid "This section describes all parameters. Parameters are categorized." -msgstr "This section describes all parameters. Parameters are categorized." - -msgid "There is a required parameter, ``table``." -msgstr "There is a required parameter, ``table``." - -msgid "It specifies a table to be searched. ``table`` must be specified." -msgstr "It specifies a table to be searched. ``table`` must be specified." - -msgid "If nonexistent table is specified, an error is returned." -msgstr "If nonexistent table is specified, an error is returned." - -msgid "Search related parameters" -msgstr "Search related parameters" - -msgid "" -"There are search related parameters. Typically, ``match_columns`` and " -"``query`` parameters are used for implementing a search box. ``filter`` " -"parameters is used for implementing complex search feature." -msgstr "" -"There are search related parameters. Typically, ``match_columns`` and " -"``query`` parameters are used for implementing a search box. ``filter`` " -"parameters is used for implementing complex search feature." - -msgid "" -"If both ``query`` and ``filter`` are specified, selected records must be " -"matched against both ``query`` and ``filter``. If both ``query`` and " -"``filter`` aren't specified, all records are selected." -msgstr "" -"If both ``query`` and ``filter`` are specified, selected records must be " -"matched against both ``query`` and ``filter``. If both ``query`` and " -"``filter`` aren't specified, all records are selected." - -msgid "" -"It specifies the default target column for fulltext search by ``query`` " -"parameter value. A target column for fulltext search can be specified in " -"``query`` parameter. The difference between ``match_columns`` and ``query`` " -"is whether weight is supported or not. ``match_columns`` supports weight but " -"``query`` doesn't." -msgstr "" -"It specifies the default target column for fulltext search by ``query`` " -"parameter value. A target column for fulltext search can be specified in " -"``query`` parameter. The difference between ``match_columns`` and ``query`` " -"is whether weight is supported or not. ``match_columns`` supports weight but " -"``query`` doesn't." - -msgid "" -"Weight is relative importance of target column. A higher weight target " -"column gets more hit score rather than a lower weight target column when a " -"record is matched by fulltext search. The default weight is 1." -msgstr "" -"Weight is relative importance of target column. A higher weight target " -"column gets more hit score rather than a lower weight target column when a " -"record is matched by fulltext search. The default weight is 1." - -msgid "Here is a simple ``match_columns`` usage example." -msgstr "Here is a simple ``match_columns`` usage example." - -msgid "" -"``--match_columns content`` means the default target column for fulltext " -"search is ``content`` column and its weight is 1. ``--output_columns '_key, " -"_score'`` means that the ``select`` command outputs ``_key`` value and " -"``_score`` value for matched records." -msgstr "" -"``--match_columns content`` means the default target column for fulltext " -"search is ``content`` column and its weight is 1. ``--output_columns '_key, " -"_score'`` means that the ``select`` command outputs ``_key`` value and " -"``_score`` value for matched records." - -msgid "" -"Pay attention to ``_score`` value. ``_score`` value is the number of matched " -"counts against ``query`` parameter value. In the example, ``query`` " -"parameter value is ``fast``. The fact that ``_score`` value is 1 means that " -"``fast`` appers in ``content`` column only once. The fact that ``_score`` " -"value is 2 means that ``fast`` appears in ``content`` column twice." -msgstr "" -"Pay attention to ``_score`` value. ``_score`` value is the number of matched " -"counts against ``query`` parameter value. In the example, ``query`` " -"parameter value is ``fast``. The fact that ``_score`` value is 1 means that " -"``fast`` appers in ``content`` column only once. The fact that ``_score`` " -"value is 2 means that ``fast`` appears in ``content`` column twice." - -msgid "" -"To specify weight, ``column * weight`` syntax is used. Here is a weight " -"usage example." -msgstr "" -"To specify weight, ``column * weight`` syntax is used. Here is a weight " -"usage example." - -msgid "" -"``--match_columns 'content * 2'`` means the default target column for " -"fulltext search is ``content`` column and its weight is 2." -msgstr "" -"``--match_columns 'content * 2'`` means the default target column for " -"fulltext search is ``content`` column and its weight is 2." - -msgid "" -"Pay attention to ``_score`` value. ``_score`` value is doubled because " -"weight is 2." -msgstr "" -"Pay attention to ``_score`` value. ``_score`` value is doubled because " -"weight is 2." - -msgid "" -"You can specify one or more columns as the default target columns for " -"fulltext search. If one or more columns are specified, fulltext search is " -"done for all columns and scores are accumulated. If one of the columns is " -"matched against ``query`` parameter value, the record is treated as matched." -msgstr "" -"You can specify one or more columns as the default target columns for " -"fulltext search. If one or more columns are specified, fulltext search is " -"done for all columns and scores are accumulated. If one of the columns is " -"matched against ``query`` parameter value, the record is treated as matched." - -msgid "" -"To specify one or more columns, ``column1 * weight1 || column2 * weight2 " -"|| ...`` syntax is used. ``* weight`` can be omitted. If it is omitted, 1 is " -"used for weight. Here is a one or more columns usage example." -msgstr "" -"To specify one or more columns, ``column1 * weight1 || column2 * weight2 " -"|| ...`` syntax is used. ``* weight`` can be omitted. If it is omitted, 1 is " -"used for weight. Here is a one or more columns usage example." - -msgid "" -"``--match_columns '_key * 10 || content'`` means the default target columns " -"for fulltext search are ``_key`` and ``content`` columns and ``_key`` " -"column's weight is 10 and ``content`` column's weight is 1. This weight " -"allocation means ``_key`` column value is more important rather than " -"``content`` column value. In this example, title of blog entry is more " -"important rather thatn content of blog entry." -msgstr "" -"``--match_columns '_key * 10 || content'`` means the default target columns " -"for fulltext search are ``_key`` and ``content`` columns and ``_key`` " -"column's weight is 10 and ``content`` column's weight is 1. This weight " -"allocation means ``_key`` column value is more important rather than " -"``content`` column value. In this example, title of blog entry is more " -"important rather thatn content of blog entry." - -msgid "" -"It specifies the query text. Normally, it is used for fulltext search with " -"``match_columns`` parameter. ``query`` parameter is designed for a fulltext " -"search form in a Web page. A query text should be formatted in :doc:`/" -"reference/grn_expr/query_syntax`. The syntax is similar to common search " -"form like Google's search form. For example, ``word1 word2`` means that " -"groonga searches records that contain both ``word1`` and ``word2``. ``word1 " -"OR word2`` means that groogna searches records that contain either ``word1`` " -"or ``word2``." -msgstr "" -"It specifies the query text. Normally, it is used for fulltext search with " -"``match_columns`` parameter. ``query`` parameter is designed for a fulltext " -"search form in a Web page. A query text should be formatted in :doc:`/" -"reference/grn_expr/query_syntax`. The syntax is similar to common search " -"form like Google's search form. For example, ``word1 word2`` means that " -"groonga searches records that contain both ``word1`` and ``word2``. ``word1 " -"OR word2`` means that groogna searches records that contain either ``word1`` " -"or ``word2``." - -msgid "Here is a simple logical and search example." -msgstr "Here is a simple logical and search example." - -msgid "" -"The ``select`` command searches records that contain two words ``fast`` and " -"``groonga`` in ``content`` column value from ``Entries`` table." -msgstr "" -"The ``select`` command searches records that contain two words ``fast`` and " -"``groonga`` in ``content`` column value from ``Entries`` table." - -msgid "Here is a simple logical or search example." -msgstr "Here is a simple logical or search example." - -msgid "" -"The ``select`` command searches records that contain one of two words " -"``groonga`` or ``mroonga`` in ``content`` column value from ``Entries`` " -"table." -msgstr "" -"The ``select`` command searches records that contain one of two words " -"``groonga`` or ``mroonga`` in ``content`` column value from ``Entries`` " -"table." - -msgid "See :doc:`/reference/grn_expr/query_syntax` for other syntax." -msgstr "See :doc:`/reference/grn_expr/query_syntax` for other syntax." - -msgid "" -"It can be used for not only fulltext search but also other conditions. For " -"example, ``column:value`` means the value of ``column`` column is equal to " -"``value``. ``column:<value`` means the value of ``column`` column is less " -"than ``value``." -msgstr "" -"It can be used for not only fulltext search but also other conditions. For " -"example, ``column:value`` means the value of ``column`` column is equal to " -"``value``. ``column:<value`` means the value of ``column`` column is less " -"than ``value``." - -msgid "Here is a simple equality operator search example." -msgstr "Here is a simple equality operator search example." - -msgid "" -"The ``select`` command searches records that ``_key`` column value is " -"``Groonga`` from ``Entries`` table." -msgstr "" -"The ``select`` command searches records that ``_key`` column value is " -"``Groonga`` from ``Entries`` table." - -msgid "Here is a simple less than operator search example." -msgstr "Here is a simple less than operator search example." - -msgid "" -"The ``select`` command searches records that ``n_likes`` column value is " -"less than ``11`` from ``Entries`` table." -msgstr "" -"The ``select`` command searches records that ``n_likes`` column value is " -"less than ``11`` from ``Entries`` table." - -msgid "See :doc:`/reference/grn_expr/query_syntax` for other operations." -msgstr "See :doc:`/reference/grn_expr/query_syntax` for other operations." - -msgid "" -"It specifies the filter text. Normally, it is used for complex search " -"conditions. ``filter`` can be used with ``query`` parameter. If both " -"``filter`` and ``query`` are specified, there are conbined with logical and. " -"It means that matched records should be matched against both ``filter`` and " -"``query``." -msgstr "" -"It specifies the filter text. Normally, it is used for complex search " -"conditions. ``filter`` can be used with ``query`` parameter. If both " -"``filter`` and ``query`` are specified, there are conbined with logical and. " -"It means that matched records should be matched against both ``filter`` and " -"``query``." - -msgid "" -"``filter`` parameter is designed for complex conditions. A filter text " -"should be formated in :doc:`/reference/grn_expr/script_syntax`. The syntax " -"is similar to ECMAScript. For example, ``column == \"value\"`` means that " -"the value of ``column`` column is equal to ``\"value\"``. ``column < value`` " -"means that the value of ``column`` column is less than ``value``." -msgstr "" -"``filter`` parameter is designed for complex conditions. A filter text " -"should be formated in :doc:`/reference/grn_expr/script_syntax`. The syntax " -"is similar to ECMAScript. For example, ``column == \"value\"`` means that " -"the value of ``column`` column is equal to ``\"value\"``. ``column < value`` " -"means that the value of ``column`` column is less than ``value``." - -msgid "See :doc:`/reference/grn_expr/script_syntax` for other operators." -msgstr "See :doc:`/reference/grn_expr/script_syntax` for other operators." - -msgid "Advanced search parameters" -msgstr "Advanced search parameters" - -msgid "``match_escalation_threshold``" -msgstr "``match_escalation_threshold``" - -msgid "" -"It specifies threshold to determine whether search storategy escalation is " -"used or not. The threshold is compared against the number of matched " -"records. If the number of matched records is equal to or less than the " -"threshold, the search storategy escalation is used. See :doc:`/spec/search` " -"about the search storategy escalation." -msgstr "" -"It specifies threshold to determine whether search storategy escalation is " -"used or not. The threshold is compared against the number of matched " -"records. If the number of matched records is equal to or less than the " -"threshold, the search storategy escalation is used. See :doc:`/spec/search` " -"about the search storategy escalation." - -msgid "" -"The default threshold is 0. It means that search storategy escalation is " -"used only when no records are matched." -msgstr "" -"The default threshold is 0. It means that search storategy escalation is " -"used only when no records are matched." - -msgid "The default threshold can be customized by one of the followings." -msgstr "The default threshold can be customized by one of the followings." - -msgid "``--with-match-escalation-threshold`` option of configure" -msgstr "``--with-match-escalation-threshold`` option of configure" - -msgid "``--match-escalation-threshold`` option of groogna command" -msgstr "``--match-escalation-threshold`` option of groogna command" - -msgid "``match-escalation-threshold`` configuration item in configuration file" -msgstr "" -"``match-escalation-threshold`` configuration item in configuration file" - -msgid "" -"Here is a simple ``match_escalation_threshold`` usage example. The first " -"``select`` doesn't have ``match_escalation_threshold`` parameter. The second " -"``select`` has ``match_escalation_threshold`` parameter." -msgstr "" -"Here is a simple ``match_escalation_threshold`` usage example. The first " -"``select`` doesn't have ``match_escalation_threshold`` parameter. The second " -"``select`` has ``match_escalation_threshold`` parameter." - -msgid "" -"The first ``select`` command searches records that contain a word ``groo`` " -"in ``content`` column value from ``Entries`` table. But no records are " -"matched because the ``TokenBigram`` tokenizer tokenizes ``groonga`` to " -"``groonga`` not ``gr|ro|oo|on|ng|ga``. (The ``TokenBigramSplitSymbolAlpha`` " -"tokenizer tokenizes ``groonga`` to ``gr|ro|oo|on|ng|ga``. See :doc:`/" -"reference/tokenizers` for details.) It means that ``groonga`` is indexed but " -"``groo`` isn't indexed. So no records are matched against ``groo`` by exact " -"match. In the case, the search storategy escalation is used because the " -"number of matched records (0) is equal to ``match_escalation_threshold`` " -"(0). One record is matched against ``groo`` by unsplit search." -msgstr "" -"The first ``select`` command searches records that contain a word ``groo`` " -"in ``content`` column value from ``Entries`` table. But no records are " -"matched because the ``TokenBigram`` tokenizer tokenizes ``groonga`` to " -"``groonga`` not ``gr|ro|oo|on|ng|ga``. (The ``TokenBigramSplitSymbolAlpha`` " -"tokenizer tokenizes ``groonga`` to ``gr|ro|oo|on|ng|ga``. See :doc:`/" -"reference/tokenizers` for details.) It means that ``groonga`` is indexed but " -"``groo`` isn't indexed. So no records are matched against ``groo`` by exact " -"match. In the case, the search storategy escalation is used because the " -"number of matched records (0) is equal to ``match_escalation_threshold`` " -"(0). One record is matched against ``groo`` by unsplit search." - -msgid "" -"The second ``select`` command also searches records that contain a word " -"``groo`` in ``content`` column value from ``Entries`` table. And it also " -"doesn't found matched records. In this case, the search storategy escalation " -"is not used because the number of matched records (0) is larger than " -"``match_escalation_threshold`` (-1). So no more searches aren't executed. " -"And no records are matched." -msgstr "" -"The second ``select`` command also searches records that contain a word " -"``groo`` in ``content`` column value from ``Entries`` table. And it also " -"doesn't found matched records. In this case, the search storategy escalation " -"is not used because the number of matched records (0) is larger than " -"``match_escalation_threshold`` (-1). So no more searches aren't executed. " -"And no records are matched." - -msgid "``query_expansion``" -msgstr "``query_expansion``" - -msgid "Deprecated. Use :ref:`query-expander` instead." -msgstr "Deprecated. Use :ref:`query-expander` instead." - -msgid "``query_flags``" -msgstr "``query_flags``" - -msgid "" -"It customs ``query`` parameter syntax. You cannot update column value by " -"``query`` parameter by default. But if you specify ``ALLOW_COLUMN|" -"ALLOW_UPDATE`` as ``query_flags``, you can update column value by ``query``." -msgstr "" -"It customs ``query`` parameter syntax. You cannot update column value by " -"``query`` parameter by default. But if you specify ``ALLOW_COLUMN|" -"ALLOW_UPDATE`` as ``query_flags``, you can update column value by ``query``." - -msgid "``ALLOW_PRAGMA``" -msgstr "``ALLOW_PRAGMA``" - -msgid "``ALLOW_COLUMN``" -msgstr "``ALLOW_COLUMN``" - -msgid "``ALLOW_UPDATE``" -msgstr "``ALLOW_UPDATE``" - -msgid "``ALLOW_LEADING_NOT``" -msgstr "``ALLOW_LEADING_NOT``" - -msgid "" -"``ALLOW_PRAGMA`` enables pragma at the head of ``query``. This is not " -"implemented yet." -msgstr "" -"``ALLOW_PRAGMA`` enables pragma at the head of ``query``. This is not " -"implemented yet." - -msgid "" -"``ALLOW_COLUMN`` enables search againt columns that are not included in " -"``match_columns``. To specify column, there are ``COLUMN:...`` syntaxes." -msgstr "" -"``ALLOW_COLUMN`` enables search againt columns that are not included in " -"``match_columns``. To specify column, there are ``COLUMN:...`` syntaxes." - -msgid "" -"``ALLOW_UPDATE`` enables column update by ``query`` with ``COLUMN:" -"=NEW_VALUE`` syntax. ``ALLOW_COLUMN`` is also required to update column " -"because the column update syntax specifies column." -msgstr "" -"``ALLOW_UPDATE`` enables column update by ``query`` with ``COLUMN:" -"=NEW_VALUE`` syntax. ``ALLOW_COLUMN`` is also required to update column " -"because the column update syntax specifies column." - -msgid "" -"``ALLOW_LEADING_NOT`` enables leading NOT condition with ``-WORD`` syntax. " -"The query searches records that doesn't match ``WORD``. Leading NOT " -"condition query is heavy query in many cases because it matches many " -"records. So this flag is disabled by default. Be careful about it when you " -"use the flag." -msgstr "" -"``ALLOW_LEADING_NOT`` enables leading NOT condition with ``-WORD`` syntax. " -"The query searches records that doesn't match ``WORD``. Leading NOT " -"condition query is heavy query in many cases because it matches many " -"records. So this flag is disabled by default. Be careful about it when you " -"use the flag." - -msgid "``NONE`` is just ignores. You can use ``NONE`` for specifying no flags." -msgstr "" -"``NONE`` is just ignores. You can use ``NONE`` for specifying no flags." - -msgid "" -"They can be combined by separated ``|`` such as ``ALLOW_COLUMN|" -"ALLOW_UPDATE``." -msgstr "" -"They can be combined by separated ``|`` such as ``ALLOW_COLUMN|" -"ALLOW_UPDATE``." - -msgid "The default value is ``ALLOW_PRAGMA|ALLOW_COLUMN``." -msgstr "The default value is ``ALLOW_PRAGMA|ALLOW_COLUMN``." - -msgid "Here is a usage example of ``ALLOW_COLUMN``." -msgstr "Here is a usage example of ``ALLOW_COLUMN``." - -msgid "" -"The ``select`` command searches records that contain ``mroonga`` in " -"``content`` column value from ``Entries`` table." -msgstr "" -"The ``select`` command searches records that contain ``mroonga`` in " -"``content`` column value from ``Entries`` table." - -msgid "Here is a usage example of ``ALLOW_UPDATE``." -msgstr "Here is a usage example of ``ALLOW_UPDATE``." - -msgid "" -"The first ``select`` command sets ``age`` column value of all records to " -"``19``. The second ``select`` command outputs updated ``age`` column values." -msgstr "" -"The first ``select`` command sets ``age`` column value of all records to " -"``19``. The second ``select`` command outputs updated ``age`` column values." - -msgid "Here is a usage example of ``ALLOW_LEADING_NOT``." -msgstr "Here is a usage example of ``ALLOW_LEADING_NOT``." - -msgid "" -"The ``select`` command searches records that don't contain ``mroonga`` in " -"``content`` column value from ``Entries`` table." -msgstr "" -"The ``select`` command searches records that don't contain ``mroonga`` in " -"``content`` column value from ``Entries`` table." - -msgid "Here is a usage example of ``NONE``." -msgstr "Here is a usage example of ``NONE``." - -msgid "" -"The ``select`` command searches records that contain one of two words " -"``mroonga`` or ``_key:Groonga`` in ``content`` from ``Entries`` table. Note " -"that ``_key:Groonga`` doesn't mean that the value of ``_key`` column is " -"equal to ``Groonga``. Because ``ALLOW_COLUMN`` flag is not specified." -msgstr "" -"The ``select`` command searches records that contain one of two words " -"``mroonga`` or ``_key:Groonga`` in ``content`` from ``Entries`` table. Note " -"that ``_key:Groonga`` doesn't mean that the value of ``_key`` column is " -"equal to ``Groonga``. Because ``ALLOW_COLUMN`` flag is not specified." - -msgid "See also :doc:`/reference/grn_expr/query_syntax`." -msgstr "See also :doc:`/reference/grn_expr/query_syntax`." - -msgid "``query_expander``" -msgstr "``query_expander``" - -msgid "" -"It's for query expansion. Query expansion substitutes specific words to " -"another words in query. Nomally, it's used for synonym search." -msgstr "" -"It's for query expansion. Query expansion substitutes specific words to " -"another words in query. Nomally, it's used for synonym search." - -msgid "" -"It specifies a column that is used to substitute ``query`` parameter value. " -"The format of this parameter value is \"``${TABLE}.${COLUMN}``\". For " -"example, \"``Terms.synonym``\" specifies ``synonym`` column in ``Terms`` " -"table." -msgstr "" -"It specifies a column that is used to substitute ``query`` parameter value. " -"The format of this parameter value is \"``${TABLE}.${COLUMN}``\". For " -"example, \"``Terms.synonym``\" specifies ``synonym`` column in ``Terms`` " -"table." - -msgid "" -"Table for query expansion is called \"substitution table\". Substitution " -"table's key must be ``ShortText``. So array table (``TABLE_NO_KEY``) can't " -"be used for query expansion. Because array table doesn't have key." -msgstr "" -"Table for query expansion is called \"substitution table\". Substitution " -"table's key must be ``ShortText``. So array table (``TABLE_NO_KEY``) can't " -"be used for query expansion. Because array table doesn't have key." - -msgid "" -"Column for query expansion is called \"substitution column\". Substitution " -"column's value type must be ``ShortText``. Column type must be vector " -"(``COLUMN_VECTOR``)." -msgstr "" -"Column for query expansion is called \"substitution column\". Substitution " -"column's value type must be ``ShortText``. Column type must be vector " -"(``COLUMN_VECTOR``)." - -msgid "" -"Query expansion substitutes key of substitution table in query with values " -"in substitution column. If a word in ``query`` is a key of substitution " -"table, the word is substituted with substitution column value that is " -"associated with the key. Substition isn't performed recursively. It means " -"that substitution target words in substituted query aren't substituted." -msgstr "" -"Query expansion substitutes key of substitution table in query with values " -"in substitution column. If a word in ``query`` is a key of substitution " -"table, the word is substituted with substitution column value that is " -"associated with the key. Substition isn't performed recursively. It means " -"that substitution target words in substituted query aren't substituted." - -msgid "" -"Here is a sample substitution table to show a simple ``query_expander`` " -"usage example." -msgstr "" -"Here is a sample substitution table to show a simple ``query_expander`` " -"usage example." - -msgid "" -"``Thesaurus`` substitution table has two synonyms, ``\"mroonga\"`` and ``" -"\"groonga\"``. If an user searches with ``\"mroonga\"``, groonga searches " -"with ``\"((mroonga) OR (tritonn) OR (groonga mysql))\"``. If an user " -"searches with ``\"groonga\"``, groonga searches with ``\"((groonga) OR " -"(senna))\"``. Nomrally, it's good idea that substitution table has " -"``KEY_NORMALIZE`` flag. If the flag is used, substitute target word is " -"matched in case insensitive manner." -msgstr "" -"``Thesaurus`` substitution table has two synonyms, ``\"mroonga\"`` and ``" -"\"groonga\"``. If an user searches with ``\"mroonga\"``, groonga searches " -"with ``\"((mroonga) OR (tritonn) OR (groonga mysql))\"``. If an user " -"searches with ``\"groonga\"``, groonga searches with ``\"((groonga) OR " -"(senna))\"``. Nomrally, it's good idea that substitution table has " -"``KEY_NORMALIZE`` flag. If the flag is used, substitute target word is " -"matched in case insensitive manner." - -msgid "" -"Note that those synonym values include the key value such as ``\"mroonga\"`` " -"and ``\"groonga\"``. It's recommended that you include the key value. If you " -"don't include key value, substituted value doesn't include the original " -"substitute target value. Normally, including the original value is better " -"search result. If you have a word that you don't want to be searched, you " -"should not include the original word. For example, you can implement \"stop " -"words\" by an empty vector value." -msgstr "" -"Note that those synonym values include the key value such as ``\"mroonga\"`` " -"and ``\"groonga\"``. It's recommended that you include the key value. If you " -"don't include key value, substituted value doesn't include the original " -"substitute target value. Normally, including the original value is better " -"search result. If you have a word that you don't want to be searched, you " -"should not include the original word. For example, you can implement \"stop " -"words\" by an empty vector value." - -msgid "Here is a simple ``query_expander`` usage example." -msgstr "Here is a simple ``query_expander`` usage example." - -msgid "" -"The first ``select`` command doesn't use query expansion. So a record that " -"has ``\"tritonn\"`` isn't found. The second ``select`` command uses query " -"expansion. So a record that has ``\"tritonn\"`` is found. The third " -"``select`` command doesn't use query expansion but it is same as the second " -"``select`` command. The third one uses expanded query." -msgstr "" -"The first ``select`` command doesn't use query expansion. So a record that " -"has ``\"tritonn\"`` isn't found. The second ``select`` command uses query " -"expansion. So a record that has ``\"tritonn\"`` is found. The third " -"``select`` command doesn't use query expansion but it is same as the second " -"``select`` command. The third one uses expanded query." - -msgid "" -"Each substitute value can contain any :doc:`/reference/grn_expr/" -"query_syntax` syntax such as ``(...)`` and ``OR``. You can use complex " -"substitution by using those syntax." -msgstr "" -"Each substitute value can contain any :doc:`/reference/grn_expr/" -"query_syntax` syntax such as ``(...)`` and ``OR``. You can use complex " -"substitution by using those syntax." - -msgid "Here is a complex substitution usage example that uses query syntax." -msgstr "Here is a complex substitution usage example that uses query syntax." - -msgid "" -"The ``load`` command registers a new synonym ``\"popular\"``. It is " -"substituted with ``((popular) OR (n_likes:>=10))``. The substituted query " -"means that \"popular\" is containing the word \"popular\" or 10 or more " -"liked entries." -msgstr "" -"The ``load`` command registers a new synonym ``\"popular\"``. It is " -"substituted with ``((popular) OR (n_likes:>=10))``. The substituted query " -"means that \"popular\" is containing the word \"popular\" or 10 or more " -"liked entries." - -msgid "" -"The ``select`` command outputs records that ``n_likes`` column value is " -"equal to or more than ``10`` from ``Entries`` table." -msgstr "" -"The ``select`` command outputs records that ``n_likes`` column value is " -"equal to or more than ``10`` from ``Entries`` table." - -msgid "Output related parameters" -msgstr "Output related parameters" - -msgid "It specifies output columns separated by ``,``." -msgstr "It specifies output columns separated by ``,``." - -msgid "Here is a simple ``output_columns`` usage example." -msgstr "Here is a simple ``output_columns`` usage example." - -msgid "The ``select`` command just outputs ``_id`` and ``_key`` column values." -msgstr "" -"The ``select`` command just outputs ``_id`` and ``_key`` column values." - -msgid "" -"``*`` is a special value. It means that all columns that are not :doc:`/" -"reference/columns/pseudo`." -msgstr "" -"``*`` is a special value. It means that all columns that are not :doc:`/" -"reference/columns/pseudo`." - -msgid "Here is a ``*`` usage example." -msgstr "Here is a ``*`` usage example." - -msgid "" -"The ``select`` command outputs ``_key`` pseudo column, ``content`` column " -"and ``n_likes`` column values but doesn't output ``_id`` pseudo column value." -msgstr "" -"The ``select`` command outputs ``_key`` pseudo column, ``content`` column " -"and ``n_likes`` column values but doesn't output ``_id`` pseudo column value." - -msgid "" -"The default value is ``_id, _key, *``. It means that all column values " -"except ``_score`` are outputted." -msgstr "" -"The default value is ``_id, _key, *``. It means that all column values " -"except ``_score`` are outputted." - -msgid "" -"It specifies sort keys separated by ``,``. Each sort key is column name." -msgstr "" -"It specifies sort keys separated by ``,``. Each sort key is column name." - -msgid "Here is a simple ``sortby`` usage example." -msgstr "Here is a simple ``sortby`` usage example." - -msgid "" -"The ``select`` command sorts by ``n_likes`` column value in ascending order. " -"For records that has the same ``n_likes`` are sorted by ``_id`` in ascending " -"order. ``\"Good-bye Senna\"`` and ``\"Good-bye Tritonn\"`` are the case." -msgstr "" -"The ``select`` command sorts by ``n_likes`` column value in ascending order. " -"For records that has the same ``n_likes`` are sorted by ``_id`` in ascending " -"order. ``\"Good-bye Senna\"`` and ``\"Good-bye Tritonn\"`` are the case." - -msgid "If you want to sort in descending order, add ``-`` before column name." -msgstr "If you want to sort in descending order, add ``-`` before column name." - -msgid "Here is a descending order ``sortby`` usage example." -msgstr "Here is a descending order ``sortby`` usage example." - -msgid "" -"The ``select`` command sorts by ``n_likes`` column value in descending " -"order. But ascending order is used for sorting by ``_id``." -msgstr "" -"The ``select`` command sorts by ``n_likes`` column value in descending " -"order. But ascending order is used for sorting by ``_id``." - -msgid "" -"You can use ``_score`` pseudo column in ``sortby`` if you use ``query`` or " -"``filter`` parameter." -msgstr "" -"You can use ``_score`` pseudo column in ``sortby`` if you use ``query`` or " -"``filter`` parameter." - -msgid "" -"The ``select`` command sorts matched records by hit score in descending " -"order and outputs record key and hit score." -msgstr "" -"The ``select`` command sorts matched records by hit score in descending " -"order and outputs record key and hit score." - -msgid "" -"If you use ``_score`` without ``query`` nor ``filter`` parameters, it's just " -"ignored but get a warning in log file." -msgstr "" -"If you use ``_score`` without ``query`` nor ``filter`` parameters, it's just " -"ignored but get a warning in log file." - -msgid "" -"It specifies offset to determine output records range. Offset is zero-based. " -"``--offset 1`` means output range is started from the 2nd record." -msgstr "" - -msgid "The ``select`` command outputs from the 4th record." -msgstr "The ``select`` command outputs from the 4th record." - -msgid "" -"You can specify negative value. It means that ``the number of matched " -"records + offset``. If you have 3 matched records and specify ``--offset " -"-2``, you get records from the 2nd (``3 + -2 = 1``. ``1`` means 2nd. " -"Remember that offset is zero-based.) record to the 3rd record." -msgstr "" - -msgid "" -"The ``select`` command outputs from the 4th record because the total number " -"of records is ``5``." -msgstr "" -"The ``select`` command outputs from the 4th record because the total number " -"of records is ``5``." - -msgid "The default value is ``0``." -msgstr "The default value is ``0``." - -msgid "" -"It specifies the max number of output records. If the number of matched " -"records is less than ``limit``, all records are outputted." -msgstr "" -"It specifies the max number of output records. If the number of matched " -"records is less than ``limit``, all records are outputted." - -msgid "Here is a simple ``limit`` usage example." -msgstr "Here is a simple ``limit`` usage example." - -msgid "The ``select`` command outputs the 3rd, the 4th and the 5th records." -msgstr "The ``select`` command outputs the 3rd, the 4th and the 5th records." - -msgid "" -"You can specify negative value. It means that ``the number of matched " -"records + limit + 1``. For example, ``--limit -1`` outputs all records. It's " -"very useful value to show all records." -msgstr "" -"You can specify negative value. It means that ``the number of matched " -"records + limit + 1``. For example, ``--limit -1`` outputs all records. It's " -"very useful value to show all records." - -msgid "Here is a simple negative ``limit`` value usage example." -msgstr "Here is a simple negative ``limit`` value usage example." - -msgid "The ``select`` command outputs all records." -msgstr "The ``select`` command outputs all records." - -msgid "The default value is ``10``." -msgstr "The default value is ``10``." - -msgid "TODO: write in English and add example." -msgstr "TODO: write in English and add example." - -msgid "" -"検索条件にマッチする全てのレコードに対して適用するgrn_exprをscript形式で指定" -"します。" -msgstr "" -"検索条件にマッチする全てのレコードに対して適用するgrn_exprをscript形式で指定" -"します。" - -msgid "" -"scorerは、検索処理が完了し、ソート処理が実行される前に呼び出されます。従っ" -"て、各レコードのスコアを操作する式を指定しておけば、検索結果のソート順序をカ" -"スタマイズできるようになります。" -msgstr "" -"scorerは、検索処理が完了し、ソート処理が実行される前に呼び出されます。従っ" -"て、各レコードのスコアを操作する式を指定しておけば、検索結果のソート順序をカ" -"スタマイズできるようになります。" - -msgid "Drilldown related parameters" -msgstr "" - -msgid "" -"This section describes basic drilldown related parameters. Advanced " -"drilldown related parameters are described in another section." -msgstr "" - -msgid "It specifies keys for grouping separated by ``,``." -msgstr "" - -msgid "" -"Matched records by specified search conditions are grouped by each key. If " -"you specify no search condition, all records are grouped by each key." -msgstr "" - -msgid "Here is a simple ``drilldown`` example:" -msgstr "" - -msgid "The ``select`` command outputs the following information:" -msgstr "" - -msgid "There is one record that has \"Hello\" tag." -msgstr "" - -msgid "There is two records that has \"Groonga\" tag." -msgstr "" - -msgid "There is two records that has \"Senna\" tag." -msgstr "" - -msgid "Here is a ``drilldown`` with search condition example:" -msgstr "" - -msgid "In records that have 5 or larger as ``n_likes`` value:" -msgstr "" - -msgid "Here is a ``drilldown`` with multiple group keys example:" -msgstr "" - -msgid "About ``tag``:" -msgstr "" - -msgid "About ``n_likes``:" -msgstr "" - -msgid "" -"It specifies sort keys for drilldown outputs separated by ``,``. Each sort " -"key is column name." -msgstr "" - -msgid "" -"You can refer the number of grouped records by ``_nsubrecs`` :doc:`/" -"reference/columns/pseudo`." -msgstr "" - -msgid "Here is a simple ``drilldown_sortby`` example:" -msgstr "" - -msgid "" -"Drilldown result is sorted by the number of grouped records (= " -"``_nsubrecs`` ) in descending order. If there are grouped results that the " -"number of records in the group are the same, these grouped results are " -"sorted by grouped key (= ``_key`` ) in ascending order." -msgstr "" - -msgid "The sort keys are used in all group keys specified in ``drilldown``:" -msgstr "" - -msgid "" -"The same sort keys are used in ``tag`` drilldown and ``n_likes`` drilldown." -msgstr "" - -msgid "" -"If you want to use different sort keys for each drilldown, use :ref:`select-" -"advanced-drilldown-related-parameters`." -msgstr "" - -msgid "It specifies output columns for drilldown separated by ``,``." -msgstr "" - -msgid "Here is a ``drilldown_output_columns`` example:" -msgstr "" - -msgid "The ``select`` command just outputs grouped key." -msgstr "" - -msgid "" -"If grouped key is a referenced type column (= column that its type is a " -"table), you can access column of the table referenced by the referenced type " -"column." -msgstr "" - -msgid "" -"Here are a schema definition and sample data to show drilldown against " -"referenced type column:" -msgstr "" - -msgid "" -"``Tags`` table is a referenced table. ``Items.tag`` is a referenced type " -"column." -msgstr "" - -msgid "" -"You can refer ``Tags.label`` by ``label`` in ``drilldown_output_columns``:" -msgstr "" - -msgid "" -"You can use ``*`` to refer all columns in referenced table (= ``Tags``):" -msgstr "" - -msgid "``*`` is expanded to ``label, priority``." -msgstr "" - -msgid "" -"The default value of ``drilldown_output_columns`` is ``_key, _nsubrecs``. It " -"means that grouped key and the number of records in the group are output." -msgstr "" - -msgid "" -"You can use more :doc:`/reference/columns/pseudo` in " -"``drilldown_output_columns`` such as ``_max``, ``_min``, ``_sum`` and " -"``_avg`` when you use :ref:`select-drilldown-calc-types`. See " -"``drilldown_calc_types`` document for details." -msgstr "" - -msgid "" -"It specifies offset to determine range of drilldown output records. Offset " -"is zero-based. ``--drilldown_offset 1`` means output range is started from " -"the 2nd record." -msgstr "" - -msgid "Here is a ``drilldown_offset`` example:" -msgstr "" - -msgid "The ``select`` command outputs from the 2nd record." -msgstr "" - -msgid "" -"You can specify negative value. It means that ``the number of grouped " -"results + offset``. If you have 3 grouped results and specify ``--" -"drilldown_offset -2``, you get grouped results from the 2st (``3 + -2 = 1``. " -"``1`` means 2nd. Remember that offset is zero-based.) grouped result to the " -"3rd grouped result." -msgstr "" - -msgid "" -"The ``select`` command outputs from the 2nd grouped result because the total " -"number of grouped results is ``3``." -msgstr "" - -msgid "The default value of ``drilldown_offset`` is ``0``." -msgstr "" - -msgid "" -"It specifies the max number of groups in a drilldown. If the number of " -"groups is less than ``drilldown_limit``, all groups are outputted." -msgstr "" - -msgid "Here is a ``drilldown_limit`` example:" -msgstr "" - -msgid "The ``select`` command outputs the 2rd and the 3rd groups." -msgstr "" - -msgid "" -"You can specify negative value. It means that ``the number of groups + " -"drilldown_limit + 1``. For example, ``--drilldown_limit -1`` outputs all " -"groups. It's very useful value to show all groups." -msgstr "" - -msgid "Here is a negative ``drilldown_limit`` value example." -msgstr "" - -msgid "The ``select`` command outputs all groups." -msgstr "" - -msgid "The default value of ``drilldown_limit`` is ``10``." -msgstr "" - -msgid "``drilldown_calc_types``" -msgstr "" - -msgid "" -"It specifies how to calculate (aggregate) values in grouped records by a " -"drilldown. You can specify multiple calculation types separated by \"``,``" -"\". For example, ``MAX,MIN``." -msgstr "" - -msgid "" -"Calculation target values are read from a column of grouped records. The " -"column is specified by :ref:`select-drilldown-calc-target`." -msgstr "" - -msgid "" -"You can read calculated value by :doc:`/reference/columns/pseudo` such as " -"``_max`` and ``_min`` in :ref:`select-drilldown-output-columns`." -msgstr "" - -msgid "You can use the following calculation types:" -msgstr "" - -msgid "Type name" -msgstr "" - -msgid ":doc:`/reference/columns/pseudo` name" -msgstr "" - -msgid "Need :ref:`select-drilldown-calc-target`" -msgstr "" - -msgid "Nothing." -msgstr "" - -msgid "Not needs." -msgstr "" - -msgid "``COUNT``" -msgstr "" - -msgid "Counting grouped records. It's always enabled. So you don't specify it." -msgstr "" - -msgid "``MAX``" -msgstr "" - -msgid "``_max``" -msgstr "" - -msgid "Needs." -msgstr "" - -msgid "" -"Finding the maximum integer value from integer values in grouped records." -msgstr "" - -msgid "``MIN``" -msgstr "" - -msgid "``_min``" -msgstr "" - -msgid "" -"Finding the minimum integer value from integer values in grouped records." -msgstr "" - -msgid "``SUM``" -msgstr "" - -msgid "``_sum``" -msgstr "" - -msgid "Summing integer values in grouped records." -msgstr "" - -msgid "``AVG``" -msgstr "" - -msgid "``_avg``" -msgstr "" - -msgid "Averaging integer/float values in grouped records." -msgstr "" - -msgid "Here is a ``MAX`` example:" -msgstr "" - -msgid "" -"The ``select`` command groups all records by ``tag`` column value, finding " -"the maximum ``n_likes`` column value for each group and outputs pairs of " -"grouped key and the maximum ``n_likes`` column value for the group. It uses " -"``_max`` :doc:`/reference/columns/pseudo` to read the maximum ``n_likes`` " -"column value." -msgstr "" - -msgid "Here is a ``MIN`` example:" -msgstr "" - -msgid "" -"The ``select`` command groups all records by ``tag`` column value, finding " -"the minimum ``n_likes`` column value for each group and outputs pairs of " -"grouped key and the minimum ``n_likes`` column value for the group. It uses " -"``_min`` :doc:`/reference/columns/pseudo` to read the minimum ``n_likes`` " -"column value." -msgstr "" - -msgid "Here is a ``SUM`` example:" -msgstr "" - -msgid "" -"The ``select`` command groups all records by ``tag`` column value, sums all " -"``n_likes`` column values for each group and outputs pairs of grouped key " -"and the summed ``n_likes`` column values for the group. It uses ``_sum`` :" -"doc:`/reference/columns/pseudo` to read the summed ``n_likes`` column values." -msgstr "" - -msgid "Here is a ``AVG`` example:" -msgstr "" - -msgid "" -"The ``select`` command groups all records by ``tag`` column value, averages " -"all ``n_likes`` column values for each group and outputs pairs of grouped " -"key and the averaged ``n_likes`` column values for the group. It uses " -"``_avg`` :doc:`/reference/columns/pseudo` to read the averaged ``n_likes`` " -"column values." -msgstr "" - -msgid "Here is an example that uses all calculation types:" -msgstr "" - -msgid "" -"The ``select`` command specifies multiple calculation types separated by " -"\"``,``\" like ``MAX,MIN,SUM,AVG``. You can use ``_nsubrecs`` :doc:`/" -"reference/columns/pseudo` in :ref:`select-drilldown-output-columns` without " -"specifying ``COUNT`` in ``drilldown_calc_types``. Because ``COUNT`` is " -"always enabled." -msgstr "" - -msgid "" -"The default value of ``drilldown_calc_types`` is ``NONE``. It means that " -"only ``COUNT`` is enabled. Because ``NONE`` is just ignored and ``COUNT`` is " -"always enabled." -msgstr "" - -msgid "``drilldown_calc_target``" -msgstr "" - -msgid "It specifies the target column for :ref:`select-drilldown-calc-types`." -msgstr "" - -msgid "" -"If you specify a calculation type that needs a target column such as ``MAX`` " -"in :ref:`select-drilldown-calc-types` but you omit " -"``drilldown_calc_target``, the calculation result is always ``0``." -msgstr "" - -msgid "" -"You can specify only one column name like ``--drilldown_calc_target " -"n_likes``. You can't specify multiple column name like ``--" -"drilldown_calc_target _key,n_likes``." -msgstr "" - -msgid "" -"You can use referenced value from the target record by combining \"``.``\" " -"like ``--drilldown_calc_target reference_column.nested_reference_column." -"value``." -msgstr "" - -msgid "" -"See :ref:`select-drilldown-calc-types` to know how to use " -"``drilldown_calc_target``." -msgstr "" - -msgid "" -"The default value of ``drilldown_calc_target`` is ``null``. It means that no " -"calculation target column is specified." -msgstr "" - -msgid "Advanced drilldown related parameters" -msgstr "" - -msgid "" -"You can get multiple drilldown results by specifying multiple group keys by :" -"ref:`select-drilldown`. But you need to use the same configuration for all " -"drilldowns. For example, :ref:`select-drilldown-output-columns` is used by " -"all drilldowns." -msgstr "" - -msgid "" -"You can use a configuration for each drilldown by the following parameters:" -msgstr "" - -msgid "``drilldown[${LABEL}].keys``" -msgstr "" - -msgid "``drilldown[${LABEL}].sortby``" -msgstr "" - -msgid "``drilldown[${LABEL}].output_columns``" -msgstr "" - -msgid "``drilldown[${LABEL}].offset``" -msgstr "" - -msgid "``drilldown[${LABEL}].limit``" -msgstr "" - -msgid "``drilldown[${LABEL}].calc_types``" -msgstr "" - -msgid "``drilldown[${LABEL}].calc_target``" -msgstr "" - -msgid "" -"``${LABEL}`` is a variable. You can use the following characters for ``" -"${LABEL}``:" -msgstr "" - -msgid "Alphabets" -msgstr "" - -msgid "Digits" -msgstr "" - -msgid "``.``" -msgstr "" - -msgid "``_``" -msgstr "" - -msgid "" -"Parameters that has the same ``${LABEL}`` value are grouped. Grouped " -"parameters are used for one drilldown." -msgstr "" - -msgid "For example, there are 2 groups for the following parameters:" -msgstr "" - -msgid "``--drilldown[label1].keys _key``" -msgstr "" - -msgid "``--drilldown[label1].output_columns _nsubrecs``" -msgstr "" - -msgid "``--drilldown[label2].keys tag``" -msgstr "" - -msgid "``--drilldown[label2].output_columns _key,_nsubrecs``" -msgstr "" - -msgid "" -"``drilldown[label1].keys`` and ``drilldown[label1].output_columns`` are " -"grouped. ``drilldown[label2].keys`` and ``drilldown[label2].output_columns`` " -"are also grouped." -msgstr "" - -msgid "" -"In ``label1`` group, ``_key`` is used for group key and ``_nsubrecs`` is " -"used for output columns." -msgstr "" - -msgid "" -"In ``label2`` group, ``tag`` is used for group key and ``_key,_nsubrecs`` is " -"used for output columns." -msgstr "" - -msgid "" -"See document for corresponding ``drilldown_XXX`` parameter to know how to " -"use it for the following parameters:" -msgstr "" - -msgid "``drilldown[${LABEL}].sortby``: :ref:`select-drilldown-sortby`" -msgstr "" - -msgid "``drilldown[${LABEL}].offset``: :ref:`select-drilldown-offset`" -msgstr "" - -msgid "``drilldown[${LABEL}].limit``: :ref:`select-drilldown-limit`" -msgstr "" - -msgid "``drilldown[${LABEL}].calc_types``: :ref:`select-drilldown-calc-types`" -msgstr "" - -msgid "" -"``drilldown[${LABEL}].calc_target``: :ref:`select-drilldown-calc-target`" -msgstr "" - -msgid "The following parameters are needed more description:" -msgstr "" - -msgid "Output format is different a bit. It's also needed more description." -msgstr "" - -msgid "" -":ref:`select-drilldown` can specify multiple keys for multiple drilldowns. " -"But it can't specify multiple keys for one drilldown." -msgstr "" - -msgid "" -"``drilldown[${LABEL}].keys`` can't specify multiple keys for multiple " -"drilldowns. But it can specify multiple keys for one drilldown." -msgstr "" - -msgid "You can specify multiple keys separated by \"``,``\"." -msgstr "" - -msgid "" -"Here is an example to group by multiple keys, ``tag`` and ``n_likes`` column " -"values:" -msgstr "" - -msgid "" -"``tag.n_likes`` is used as the label for the drilldown parameters group. You " -"can refer grouped keys by ``_value.${KEY_NAME}`` syntax in :ref:`select-" -"drilldown-label-output-columns`. ``${KEY_NAME}`` is a column name to be used " -"by group key. ``tag`` and ``n_likes`` are ``${KEY_NAME}`` in this case." -msgstr "" - -msgid "" -"Note that you can't use ``_value.${KEY_NAME}`` syntax when you just specify " -"one key as ``drilldown[${LABEL}].keys`` like ``--drilldown[tag].keys tag``. " -"You should use ``_key`` for the case. It's the same rule in :ref:`select-" -"drilldown-output-columns`." -msgstr "" - -msgid "" -"It's almost same as :ref:`select-drilldown-output-columns`. The difference " -"between :ref:`select-drilldown-output-columns` and ``drilldown[${LABEL}]." -"output_columns`` is how to refer group keys." -msgstr "" - -msgid "" -":ref:`select-drilldown-output-columns` uses ``_key`` :doc:`/reference/" -"columns/pseudo` to refer group key. ``drilldown[${LABEL}].output_columns`` " -"also uses ``_key`` :doc:`/reference/columns/pseudo` to refer group key when " -"you specify only one group key by :ref:`select-drilldown-label-keys`." -msgstr "" - -msgid "" -"Here is an example to refer single group key by ``_key`` :doc:`/reference/" -"columns/pseudo`:" -msgstr "" - -msgid "" -"But you can't refer each group key by ``_key`` :doc:`/reference/columns/" -"pseudo` in ``drilldown[${LABEL}].output_columns``. You need to use ``_value." -"${KEY_NAME}`` syntax. ``${KEY_NAME}`` is a column name that is used for " -"group key in :ref:`select-drilldown-label-keys`." -msgstr "" - -msgid "" -"Here is an example to refer each group key in multiple group keys by " -"``_value.${KEY_NAME}`` syntax:" -msgstr "" - -msgid "Why ``_value.${KEY_NAME}`` syntax?" -msgstr "" - -msgid "It's implementation specific information." -msgstr "" - -msgid "" -"``_key`` is a vector value. The vector value is consists of all group keys. " -"You can see byte sequence of the vector value by referring ``_key`` in " -"``drilldown[${LABEL}].output_columns``." -msgstr "" - -msgid "" -"There is one grouped record in ``_value`` to refer each grouped values when " -"you specify multiple group keys to :ref:`select-drilldown-label-keys`. So " -"you can refer each group key by ``_value.${KEY_NAME}`` syntax." -msgstr "" - -msgid "" -"On the other hand, there is no grouped record in ``_value`` when you specify " -"only one group key to :ref:`select-drilldown-label-keys`. So you can't refer " -"group key by ``_value.${KEY_NAME}`` syntax." -msgstr "" - -msgid "Output format for ``drilldown[${LABEL}]`` style" -msgstr "" - -msgid "" -"There is a difference in output format between :ref:`select-drilldown` and :" -"ref:`select-drilldown-label-keys`. :ref:`select-drilldown` uses array to " -"output multiple drilldown results. :ref:`select-drilldown-label-keys` uses " -"pairs of label and drilldown result." -msgstr "" - -msgid ":ref:`select-drilldown` uses the following output format::" -msgstr "" - -msgid ":ref:`select-drilldown-label-keys` uses the following output format::" -msgstr "" - -msgid "Cache related parameter" -msgstr "Cache related parameter" - -msgid "``cache``" -msgstr "``cache``" - -msgid "クエリキャッシュに関する動作を設定します。" -msgstr "クエリキャッシュに関する動作を設定します。" - -msgid "``no``" -msgstr "``no``" - -msgid "" -"検索結果をクエリキャッシュに残しません。キャッシュして再利用される可能性が低" -"いクエリに対して用います。キャッシュ容量は有限です。有効なキャッシュが多く" -"ヒットするために、このパラメータは有効です。" -msgstr "" -"検索結果をクエリキャッシュに残しません。キャッシュして再利用される可能性が低" -"いクエリに対して用います。キャッシュ容量は有限です。有効なキャッシュが多く" -"ヒットするために、このパラメータは有効です。" - -msgid "Score related parameters" -msgstr "Score related parameters" - -msgid "There is a score related parameter, ``adjuster``." -msgstr "There is a score related parameter, ``adjuster``." - -msgid "``adjuster``" -msgstr "``adjuster``" - -msgid "" -"It specifies one or more score adjust expressions. You need to use " -"``adjuster`` with ``query`` or ``filter``. ``adjuster`` doesn't work with " -"not searched request." -msgstr "" -"It specifies one or more score adjust expressions. You need to use " -"``adjuster`` with ``query`` or ``filter``. ``adjuster`` doesn't work with " -"not searched request." - -msgid "" -"You can increase score of specific records by ``adjuster``. You can use " -"``adjuster`` to set high score for important records." -msgstr "" -"You can increase score of specific records by ``adjuster``. You can use " -"``adjuster`` to set high score for important records." - -msgid "" -"For example, you can use ``adjuster`` to increase score of records that have " -"``groonga`` tag." -msgstr "" -"For example, you can use ``adjuster`` to increase score of records that have " -"``groonga`` tag." - -msgid "Here is the syntax::" -msgstr "Here is the syntax::" - -msgid "Here is the ``SCORE_ADJUST_EXPRESSION`` syntax::" -msgstr "Here is the ``SCORE_ADJUST_EXPRESSION`` syntax::" - -msgid "Note the following:" -msgstr "Note the following:" - -msgid "``COLUMN`` must be indexed." -msgstr "``COLUMN`` must be indexed." - -msgid "``\"KEYWORD\"`` must be a string." -msgstr "``\"KEYWORD\"`` must be a string." - -msgid "``FACTOR`` must be a positive integer." -msgstr "``FACTOR`` must be a positive integer." - -msgid "" -"Here is a sample ``adjuster`` usage example that uses just one " -"``SCORE_ADJUST_EXPRESSION``:" -msgstr "" -"Here is a sample ``adjuster`` usage example that uses just one " -"``SCORE_ADJUST_EXPRESSION``:" - -msgid "" -"The ``select`` command matches all records. Then it applies ``adjuster``. " -"The adjuster increases score of records that have ``\"groonga\"`` in " -"``Entries.content`` column by 5. There is only one record that has ``" -"\"groonga\"`` in ``Entries.content`` column. So the record that its key is " -"``\"Groonga\"`` has score 6 (``= 1 + 5``)." -msgstr "" -"The ``select`` command matches all records. Then it applies ``adjuster``. " -"The adjuster increases score of records that have ``\"groonga\"`` in " -"``Entries.content`` column by 5. There is only one record that has ``" -"\"groonga\"`` in ``Entries.content`` column. So the record that its key is " -"``\"Groonga\"`` has score 6 (``= 1 + 5``)." - -msgid "You can omit ``FACTOR``. If you omit ``FACTOR``, it is treated as 1." -msgstr "You can omit ``FACTOR``. If you omit ``FACTOR``, it is treated as 1." - -msgid "Here is a sample ``adjuster`` usage example that omits ``FACTOR``:" -msgstr "Here is a sample ``adjuster`` usage example that omits ``FACTOR``:" - -msgid "" -"The ``adjuster`` in the ``select`` command doesn't have ``FACTOR``. So the " -"factor is treated as 1. There is only one record that has ``\"groonga\"`` in " -"``Entries.content`` column. So the record that its key is ``\"Groonga\"`` " -"has score 2 (``= 1 + 1``)." -msgstr "" -"The ``adjuster`` in the ``select`` command doesn't have ``FACTOR``. So the " -"factor is treated as 1. There is only one record that has ``\"groonga\"`` in " -"``Entries.content`` column. So the record that its key is ``\"Groonga\"`` " -"has score 2 (``= 1 + 1``)." - -msgid "" -"Here is a sample ``adjuster`` usage example that uses multiple " -"``SCORE_ADJUST_EXPRESSION``:" -msgstr "" -"Here is a sample ``adjuster`` usage example that uses multiple " -"``SCORE_ADJUST_EXPRESSION``:" - -msgid "" -"The ``adjuster`` in the ``select`` command has two " -"``SCORE_ADJUST_EXPRESSION`` s. The final increased score is sum of scores of " -"these ``SCORE_ADJUST_EXPRESSION`` s. All ``SCORE_ADJUST_EXPRESSION`` s in " -"the ``select`` command are applied to a record that its key is ``\"Groonga" -"\"``. So the final increased score of the record is sum of scores of all " -"``SCORE_ADJUST_EXPRESSION`` s." -msgstr "" -"The ``adjuster`` in the ``select`` command has two " -"``SCORE_ADJUST_EXPRESSION`` s. The final increased score is sum of scores of " -"these ``SCORE_ADJUST_EXPRESSION`` s. All ``SCORE_ADJUST_EXPRESSION`` s in " -"the ``select`` command are applied to a record that its key is ``\"Groonga" -"\"``. So the final increased score of the record is sum of scores of all " -"``SCORE_ADJUST_EXPRESSION`` s." - -msgid "" -"The first ``SCORE_ADJUST_EXPRESSION`` is ``content @ \"groonga\" * 5``. It " -"increases score by 5." -msgstr "" -"The first ``SCORE_ADJUST_EXPRESSION`` is ``content @ \"groonga\" * 5``. It " -"increases score by 5." - -msgid "" -"The second ``SCORE_ADJUST_EXPRESSION`` is ``content @ \"started\" * 3``. It " -"increases score by 3." -msgstr "" -"The second ``SCORE_ADJUST_EXPRESSION`` is ``content @ \"started\" * 3``. It " -"increases score by 3." - -msgid "The final increased score is 9 (``= 1 + 5 + 3``)." -msgstr "The final increased score is 9 (``= 1 + 5 + 3``)." - -msgid "" -"A ``SCORE_ADJUST_EXPRESSION`` has a factor for ``\"KEYWORD\"``. This means " -"that increased scores of all records that has ``\"KEYWORD\"`` are the same " -"value. You can change increase score for each record that has the same ``" -"\"KEYWORD\"``. It is useful to tune search score. See :ref:`weight-vector-" -"column` for details." -msgstr "" -"A ``SCORE_ADJUST_EXPRESSION`` has a factor for ``\"KEYWORD\"``. This means " -"that increased scores of all records that has ``\"KEYWORD\"`` are the same " -"value. You can change increase score for each record that has the same ``" -"\"KEYWORD\"``. It is useful to tune search score. See :ref:`weight-vector-" -"column` for details." - -msgid "返値" -msgstr "返値" - -msgid "以下のようなjson形式で値が返却されます。" -msgstr "以下のようなjson形式で値が返却されます。" - -msgid "``リターンコード``" -msgstr "``リターンコード``" - -msgid "" -"grn_rcに対応する数値が返されます。0(GRN_SUCCESS)以外の場合は、続いてエラー内" -"容を示す 文字列が返されます。" -msgstr "" -"grn_rcに対応する数値が返されます。0(GRN_SUCCESS)以外の場合は、続いてエラー内" -"容を示す 文字列が返されます。" - -msgid "``処理開始時間``" -msgstr "``処理開始時間``" - -msgid "" -"処理を開始した時間について、1970年1月1日0時0分0秒を起点とした秒数を小数で返し" -"ます。" -msgstr "" -"処理を開始した時間について、1970年1月1日0時0分0秒を起点とした秒数を小数で返し" -"ます。" - -msgid "``処理時間``" -msgstr "``処理時間``" - -msgid "処理にかかった秒数を返します。" -msgstr "処理にかかった秒数を返します。" - -msgid "``検索結果``" -msgstr "``検索結果``" - -msgid "drilldown条件が実行される前の検索結果が以下のように出力されます。::" -msgstr "drilldown条件が実行される前の検索結果が以下のように出力されます。::" - -msgid "``ヒット数``" -msgstr "``ヒット数``" - -msgid "" -"検索条件にヒットしたレコードの数が出力されます。 ``--limit`` オプションで出力" -"件数を制限した場合は出力するレコード数と一致しません。 ``ヒット数`` は ``--" -"limit`` オプションに関係なく常にヒットしたレコードの数になります。" -msgstr "" -"検索条件にヒットしたレコードの数が出力されます。 ``--limit`` オプションで出力" -"件数を制限した場合は出力するレコード数と一致しません。 ``ヒット数`` は ``--" -"limit`` オプションに関係なく常にヒットしたレコードの数になります。" - -msgid "``カラム名n``" -msgstr "``カラム名n``" - -msgid "" -"output_columnsに指定された条件に従って、対象となるカラム名が出力されます。" -msgstr "" -"output_columnsに指定された条件に従って、対象となるカラム名が出力されます。" - -msgid "``カラム型n``" -msgstr "``カラム型n``" - -msgid "" -"output_columnsに指定された条件に従って、対象となるカラム型が出力されます。" -msgstr "" -"output_columnsに指定された条件に従って、対象となるカラム型が出力されます。" - -msgid "``検索結果n``" -msgstr "``検索結果n``" - -msgid "" -"output_columns, offset, limitによって指定された条件に従って各レコードの値が出" -"力されます。" -msgstr "" -"output_columns, offset, limitによって指定された条件に従って各レコードの値が出" -"力されます。" - -msgid "``drilldown結果``" -msgstr "``drilldown結果``" - -msgid "drilldown処理の結果が以下のように出力されます。::" -msgstr "drilldown処理の結果が以下のように出力されます。::" - -msgid "``件数``" -msgstr "``件数``" - -msgid "drilldownに指定されたカラムの値の異なり数が出力されます。" -msgstr "drilldownに指定されたカラムの値の異なり数が出力されます。" - -msgid "" -"drilldown_output_columnsに指定された条件に従って、対象となるカラム名が出力さ" -"れます。" -msgstr "" -"drilldown_output_columnsに指定された条件に従って、対象となるカラム名が出力さ" -"れます。" - -msgid "" -"drilldown_output_columnsに指定された条件に従って、対象となるカラム型が出力さ" -"れます。" -msgstr "" -"drilldown_output_columnsに指定された条件に従って、対象となるカラム型が出力さ" -"れます。" - -msgid "``ドリルダウン結果n``" -msgstr "``ドリルダウン結果n``" - -msgid "" -"drilldown_output_columns, drilldown_offset, drilldown_limitによって指定された" -"条件に従って各レコードの値が出力されます。" -msgstr "" -"drilldown_output_columns, drilldown_offset, drilldown_limitによって指定された" -"条件に従って各レコードの値が出力されます。" - -msgid "``shutdown``" -msgstr "``shutdown``" - -msgid "shutdown - サーバプロセスの停止" -msgstr "shutdown - サーバプロセスの停止" - -msgid "" -"Groonga組込コマンドの一つであるshutdownについて説明します。組込コマンドは、" -"groonga実行ファイルの引数、標準入 力、またはソケット経由でgroongaサーバにリク" -"エストを送信することによって実行します。" -msgstr "" - -msgid "shutdownは、接続しているgroongaサーバプロセスを停止します。" -msgstr "shutdownは、接続しているgroongaサーバプロセスを停止します。" - -msgid "``status``" -msgstr "``status``" - -msgid "status - groongaプロセスの状態表示" -msgstr "status - groongaプロセスの状態表示" - -msgid "" -"Groonga組込コマンドの一つであるstatusについて説明します。組込コマンドは、" -"groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリク" -"エストを送信することによって実行します。" -msgstr "" -"Groonga組込コマンドの一つであるstatusについて説明します。組込コマンドは、" -"groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリク" -"エストを送信することによって実行します。" - -msgid "" -"statusコマンドは、groongaプロセスの状態を表示します。主にgroongaサーバプロセ" -"スに対して使用することを想定しています。" -msgstr "" -"statusコマンドは、groongaプロセスの状態を表示します。主にgroongaサーバプロセ" -"スに対して使用することを想定しています。" - -msgid "``alloc_count``" -msgstr "``alloc_count``" - -msgid "" -"groongaプロセスの内部でアロケートされ、まだ解放されてないメモリブロックの数を" -"示します。Groongaをbuildする際に、configureオプションで --enable-exact-alloc-" -"countが指定されていたならば、正確な値を返します。それ以外の場合は不正確な値を" -"返す場合があります。" -msgstr "" -"groongaプロセスの内部でアロケートされ、まだ解放されてないメモリブロックの数を" -"示します。Groongaをbuildする際に、configureオプションで --enable-exact-alloc-" -"countが指定されていたならば、正確な値を返します。それ以外の場合は不正確な値を" -"返す場合があります。" - -msgid "``starttime``" -msgstr "``starttime``" - -msgid "groongaプロセスが起動した時刻のtvsec値を返します。" -msgstr "groongaプロセスが起動した時刻のtvsec値を返します。" - -msgid "``uptime``" -msgstr "``uptime``" - -msgid "groongaプロセスが起動してから経過した秒数を返します。" -msgstr "groongaプロセスが起動してから経過した秒数を返します。" - -msgid "``suggest``" -msgstr "``suggest``" - -msgid "" -"The suggest feature specification isn't stable. The specification may be " -"changed." -msgstr "" -"The suggest feature specification isn't stable. The specification may be " -"changed." - -msgid "suggest - returns completion, correction and/or suggestion for a query." -msgstr "" -"suggest - returns completion, correction and/or suggestion for a query." - -msgid "" -"The suggest command returns completion, correction and/or suggestion for a " -"specified query." -msgstr "" -"The suggest command returns completion, correction and/or suggestion for a " -"specified query." - -msgid "" -"See :doc:`/reference/suggest/introduction` about completion, correction and " -"suggestion." -msgstr "" -"See :doc:`/reference/suggest/introduction` about completion, correction and " -"suggestion." - -msgid "Here are learned data for completion." -msgstr "Here are learned data for completion." - -msgid "Here are learned data for correction." -msgstr "Here are learned data for correction." - -msgid "Here are learned data for suggestion." -msgstr "Here are learned data for suggestion." - -msgid "Here is a completion example." -msgstr "Here is a completion example." - -msgid "Here is a correction example." -msgstr "Here is a correction example." - -msgid "Here is a suggestion example." -msgstr "Here is a suggestion example." - -msgid "Here is a mixed example." -msgstr "Here is a mixed example." - -msgid "It specifies what types are returned by the suggest command." -msgstr "It specifies what types are returned by the suggest command." - -msgid "Here are available types:" -msgstr "Here are available types:" - -msgid "The suggest command does completion." -msgstr "The suggest command does completion." - -msgid "``complete``" -msgstr "``complete``" - -msgid "The suggest command does correction." -msgstr "The suggest command does correction." - -msgid "``correct``" -msgstr "``correct``" - -msgid "The suggest command does suggestion." -msgstr "The suggest command does suggestion." - -msgid "" -"You can specify one or more types separated by ``|``. Here are examples:" -msgstr "" -"You can specify one or more types separated by ``|``. Here are examples:" - -msgid "It returns correction::" -msgstr "It returns correction::" - -msgid "It returns correction and suggestion::" -msgstr "It returns correction and suggestion::" - -msgid "It returns complete, correction and suggestion::" -msgstr "It returns complete, correction and suggestion::" - -msgid "" -"It specifies table name that has ``item_${DATA_SET_NAME}`` format. For " -"example, ``item_query`` is a table name if you created dataset by the " -"following command::" -msgstr "" -"It specifies table name that has ``item_${DATA_SET_NAME}`` format. For " -"example, ``item_query`` is a table name if you created dataset by the " -"following command::" - -msgid "" -"It specifies a column name that has furigana in Katakana in ``table`` table." -msgstr "" -"It specifies a column name that has furigana in Katakana in ``table`` table." - -msgid "``column``" -msgstr "``column``" - -msgid "It specifies query for completion, correction and/or suggestion." -msgstr "It specifies query for completion, correction and/or suggestion." - -msgid "It specifies sort key." -msgstr "It specifies sort key." - -msgid "Default:" -msgstr "Default:" - -msgid "``-_score``" -msgstr "``-_score``" - -msgid "It specifies output columns." -msgstr "It specifies output columns." - -msgid "``_key,_score``" -msgstr "``_key,_score``" - -msgid "It specifies returned records offset." -msgstr "It specifies returned records offset." - -msgid "``0``" -msgstr "``0``" - -msgid "It specifies number of returned records." -msgstr "It specifies number of returned records." - -msgid "``10``" -msgstr "``10``" - -msgid "" -"It specifies threshold for item frequency. Returned records must have " -"``_score`` that is greater than or equal to ``frequency_threshold``." -msgstr "" -"It specifies threshold for item frequency. Returned records must have " -"``_score`` that is greater than or equal to ``frequency_threshold``." - -msgid "``100``" -msgstr "``100``" - -msgid "``frequency_threshold``" -msgstr "``frequency_threshold``" - -msgid "``conditional_probability_threshold``" -msgstr "``conditional_probability_threshold``" - -msgid "" -"It specifies threshold for conditional probability. Conditional probability " -"is used for learned data. It is probability of query submission when " -"``query`` is occurred. Returned records must have conditional probability " -"that is greater than or equal to ``conditional_probability_threshold``." -msgstr "" -"It specifies threshold for conditional probability. Conditional probability " -"is used for learned data. It is probability of query submission when " -"``query`` is occurred. Returned records must have conditional probability " -"that is greater than or equal to ``conditional_probability_threshold``." - -msgid "``0.2``" -msgstr "``0.2``" - -msgid "" -"It specifies whether optional prefix search is used or not in completion." -msgstr "" -"It specifies whether optional prefix search is used or not in completion." - -msgid "Prefix search is always used." -msgstr "Prefix search is always used." - -msgid "``yes``" -msgstr "``yes``" - -msgid "Prefix search is never used." -msgstr "Prefix search is never used." - -msgid "Prefix search is used only when other search can't find any records." -msgstr "Prefix search is used only when other search can't find any records." - -msgid "``auto``" -msgstr "``auto``" - -msgid "``prefix_search``" -msgstr "``prefix_search``" - -msgid "" -"It specifies whether optional similar search is used or not in correction." -msgstr "" -"It specifies whether optional similar search is used or not in correction." - -msgid "Similar search is always used." -msgstr "Similar search is always used." - -msgid "Similar search is never used." -msgstr "Similar search is never used." - -msgid "Similar search is used only when other search can't find any records." -msgstr "Similar search is used only when other search can't find any records." - -msgid "``similar_search``" -msgstr "``similar_search``" - -msgid "Here is a returned JSON format::" -msgstr "Here is a returned JSON format::" - -msgid "A type specified by ``types``." -msgstr "A type specified by ``types``." - -msgid "``candidate``" -msgstr "``candidate``" - -msgid "A candidate for completion, correction or suggestion." -msgstr "A candidate for completion, correction or suggestion." - -msgid "``score of candidate``" -msgstr "``score of candidate``" - -msgid "" -"A score of corresponding ``candidate``. It means that higher score candidate " -"is more likely candidate for completion, correction or suggestion. Returned " -"candidates are sorted by ``score of candidate`` descending by default." -msgstr "" -"A score of corresponding ``candidate``. It means that higher score candidate " -"is more likely candidate for completion, correction or suggestion. Returned " -"candidates are sorted by ``score of candidate`` descending by default." - -msgid ":doc:`/reference/suggest`" -msgstr ":doc:`/reference/suggest`" - -msgid ":doc:`/reference/executables/groonga-suggest-create-dataset`" -msgstr ":doc:`/reference/executables/groonga-suggest-create-dataset`" - -msgid "``table_create``" -msgstr "``table_create``" - -msgid "" -"``table_create`` creates a new table in the current database. You need to " -"create one or more tables to store and search data." -msgstr "" -"``table_create`` creates a new table in the current database. You need to " -"create one or more tables to store and search data." - -msgid "" -"``table_create`` has many parameters. The required parameter is only " -"``name`` and otehrs are optional::" -msgstr "" -"``table_create`` has many parameters. The required parameter is only " -"``name`` and otehrs are optional::" - -msgid "" -"``table_create`` command creates a new persistent table. See :doc:`/" -"reference/tables` for table details." -msgstr "" -"``table_create`` command creates a new persistent table. See :doc:`/" -"reference/tables` for table details." - -msgid "Create data store table" -msgstr "Create data store table" - -msgid "" -"You can use all table types for data store table. See :doc:`/reference/" -"tables` for all table types." -msgstr "" -"You can use all table types for data store table. See :doc:`/reference/" -"tables` for all table types." - -msgid "Table type is specified as ``TABLE_${TYPE}`` to ``flags`` parameter." -msgstr "Table type is specified as ``TABLE_${TYPE}`` to ``flags`` parameter." - -msgid "Here is an example to create ``TABLE_NO_KEY`` table:" -msgstr "Here is an example to create ``TABLE_NO_KEY`` table:" - -msgid "" -"The ``table_create`` command creates a table that is named ``Logs`` and is " -"``TABLE_NO_KEY`` type." -msgstr "" -"The ``table_create`` command creates a table that is named ``Logs`` and is " -"``TABLE_NO_KEY`` type." - -msgid "" -"If your records aren't searched by key, ``TABLE_NO_KEY`` type table is " -"suitable. Because ``TABLE_NO_KEY`` doesn't support key but it is fast and " -"small table. Storing logs into Groonga database is the case." -msgstr "" -"If your records aren't searched by key, ``TABLE_NO_KEY`` type table is " -"suitable. Because ``TABLE_NO_KEY`` doesn't support key but it is fast and " -"small table. Storing logs into Groonga database is the case." - -msgid "" -"If your records are searched by key or referenced by one or more columns, " -"``TABLE_NO_KEY`` type isn't suitable. Lexicon for fulltext search is the " -"case." -msgstr "" -"If your records are searched by key or referenced by one or more columns, " -"``TABLE_NO_KEY`` type isn't suitable. Lexicon for fulltext search is the " -"case." - -msgid "Create lexicon table" -msgstr "Create lexicon table" - -msgid "" -"You can use all table types except ``TABLE_NO_KEY`` for lexicon table. " -"Lexicon table needs key support but ``TABLE_NO_KEY`` doesn't support key." -msgstr "" -"You can use all table types except ``TABLE_NO_KEY`` for lexicon table. " -"Lexicon table needs key support but ``TABLE_NO_KEY`` doesn't support key." - -msgid "Here is an example to create ``TABLE_PAT_KEY`` table:" -msgstr "Here is an example to create ``TABLE_PAT_KEY`` table:" - -msgid "The ``table_create`` command creates the following table:" -msgstr "The ``table_create`` command creates the following table:" - -msgid "The table is named ``Lexicon``." -msgstr "The table is named ``Lexicon``." - -msgid "The table is ``TABLE_PAT_KEY`` type table." -msgstr "The table is ``TABLE_PAT_KEY`` type table." - -msgid "The table's key is ``ShortText`` type." -msgstr "The table's key is ``ShortText`` type." - -msgid "" -"The table uses ``TokenBigram`` tokenizer to extract tokens from a normalized " -"text." -msgstr "" -"The table uses ``TokenBigram`` tokenizer to extract tokens from a normalized " -"text." - -msgid "The table uses ``NormalizerAuto`` normalizer to normalize a text." -msgstr "The table uses ``NormalizerAuto`` normalizer to normalize a text." - -msgid "" -"``TABLE_PAT_KEY`` is suitable table type for lexicon table. Lexicon table is " -"used for fulltext search." -msgstr "" -"``TABLE_PAT_KEY`` is suitable table type for lexicon table. Lexicon table is " -"used for fulltext search." - -msgid "" -"In fulltext search, predictive search may be used for fuzzy search. " -"Predictive search is supported by ``TABLE_PAT_KEY`` and ``TABLE_DAT_KEY``." -msgstr "" -"In fulltext search, predictive search may be used for fuzzy search. " -"Predictive search is supported by ``TABLE_PAT_KEY`` and ``TABLE_DAT_KEY``." - -msgid "" -"Lexicon table has many keys because a fulltext target text has many tokens. " -"Table that has many keys should consider table size because large table " -"requires large memory. Requiring large memory causes disk I/O. It blocks " -"fast search. So table size is important for a table that has many keys. " -"``TABLE_PAT_KEY`` is less table size than ``TABLE_DAT_KEY``." -msgstr "" -"Lexicon table has many keys because a fulltext target text has many tokens. " -"Table that has many keys should consider table size because large table " -"requires large memory. Requiring large memory causes disk I/O. It blocks " -"fast search. So table size is important for a table that has many keys. " -"``TABLE_PAT_KEY`` is less table size than ``TABLE_DAT_KEY``." - -msgid "" -"Because of the above reasons, ``TABLE_PAT_KEY`` is suitable table type for " -"lexicon table." -msgstr "" -"Because of the above reasons, ``TABLE_PAT_KEY`` is suitable table type for " -"lexicon table." - -msgid "Create tag index table" -msgstr "Create tag index table" - -msgid "" -"You can use all table types except ``TABLE_NO_KEY`` for tag index table. Tag " -"index table needs key support but ``TABLE_NO_KEY`` doesn't support key." -msgstr "" -"You can use all table types except ``TABLE_NO_KEY`` for tag index table. Tag " -"index table needs key support but ``TABLE_NO_KEY`` doesn't support key." - -msgid "Here is an example to create ``TABLE_HASH_KEY`` table:" -msgstr "Here is an example to create ``TABLE_HASH_KEY`` table:" - -msgid "" -"The ``table_create`` command creates a table that is named ``Tags``, is " -"``TABLE_HASH_KEY`` type and has ``ShortText`` type key." -msgstr "" -"The ``table_create`` command creates a table that is named ``Tags``, is " -"``TABLE_HASH_KEY`` type and has ``ShortText`` type key." - -msgid "" -"``TABLE_HASH_KEY`` or ``TABLE_DAT_KEY`` are suitable table types for tag " -"index table." -msgstr "" -"``TABLE_HASH_KEY`` or ``TABLE_DAT_KEY`` are suitable table types for tag " -"index table." - -msgid "" -"If you need only exact match tag search feature, ``TABLE_HASH_KEY`` is " -"suitable. It is the common case." -msgstr "" -"If you need only exact match tag search feature, ``TABLE_HASH_KEY`` is " -"suitable. It is the common case." - -msgid "" -"If you also need predictive tag search feature (for example, searching ``" -"\"groonga\"`` by ``\"gr\"`` keyword.), ``TABLE_DAT_KEY`` is suitable. " -"``TABLE_DAT_KEY`` is large table size but it is not important because the " -"number of tags will not be large." -msgstr "" -"If you also need predictive tag search feature (for example, searching ``" -"\"groonga\"`` by ``\"gr\"`` keyword.), ``TABLE_DAT_KEY`` is suitable. " -"``TABLE_DAT_KEY`` is large table size but it is not important because the " -"number of tags will not be large." - -msgid "Create range index table" -msgstr "Create range index table" - -msgid "" -"You can use ``TABLE_PAT_KEY`` and ``TABLE_DAT_KEY`` table types for range " -"index table. Range index table needs range search support but " -"``TABLE_NO_KEY`` and ``TABLE_HASH_KEY`` don't support it." -msgstr "" -"You can use ``TABLE_PAT_KEY`` and ``TABLE_DAT_KEY`` table types for range " -"index table. Range index table needs range search support but " -"``TABLE_NO_KEY`` and ``TABLE_HASH_KEY`` don't support it." - -msgid "Here is an example to create ``TABLE_DAT_KEY`` table:" -msgstr "Here is an example to create ``TABLE_DAT_KEY`` table:" - -msgid "" -"The ``table_create`` command creates a table that is named ``Ages``, is " -"``TABLE_DAT_KEY`` type and has ``UInt32`` type key." -msgstr "" -"The ``table_create`` command creates a table that is named ``Ages``, is " -"``TABLE_DAT_KEY`` type and has ``UInt32`` type key." - -msgid "" -"``TABLE_PAT_KEY`` and ``TABLE_DAT_KEY`` are suitable table types for range " -"index table." -msgstr "" -"``TABLE_PAT_KEY`` and ``TABLE_DAT_KEY`` are suitable table types for range " -"index table." - -msgid "" -"If you don't have many indexed items, ``TABLE_DAT_KEY`` is suitable. Index " -"for age is the case in the above example. Index for age will have only 0-100 " -"items because human doesn't live so long." -msgstr "" -"If you don't have many indexed items, ``TABLE_DAT_KEY`` is suitable. Index " -"for age is the case in the above example. Index for age will have only 0-100 " -"items because human doesn't live so long." - -msgid "" -"If you have many indexed items, ``TABLE_PAT_KEY`` is suitable. Because " -"``TABLE_PAT_KEY`` is smaller than ``TABLE_DAT_KEY``." -msgstr "" -"If you have many indexed items, ``TABLE_PAT_KEY`` is suitable. Because " -"``TABLE_PAT_KEY`` is smaller than ``TABLE_DAT_KEY``." - -msgid "It specifies a table name to be created. ``name`` must be specified." -msgstr "It specifies a table name to be created. ``name`` must be specified." - -msgid "Here are available characters:" -msgstr "Here are available characters:" - -msgid "``0`` .. ``9`` (digit)" -msgstr "``0`` .. ``9`` (digit)" - -msgid "``a`` .. ``z`` (alphabet, lower case)" -msgstr "``a`` .. ``z`` (alphabet, lower case)" - -msgid "``A`` .. ``Z`` (alphabet, upper case)" -msgstr "``A`` .. ``Z`` (alphabet, upper case)" - -msgid "``#`` (hash)" -msgstr "``#`` (hash)" - -msgid "``@`` (at mark)" -msgstr "``@`` (at mark)" - -msgid "``-`` (hyphen)" -msgstr "``-`` (hyphen)" - -msgid "" -"``_`` (underscore) (NOTE: Underscore can't be used as the first character.)" -msgstr "" -"``_`` (underscore) (NOTE: Underscore can't be used as the first character.)" - -msgid "" -"You need to create a name with one or more the above chracters. Note that " -"you cannot use ``_`` as the first character such as ``_name``." -msgstr "" -"You need to create a name with one or more the above chracters. Note that " -"you cannot use ``_`` as the first character such as ``_name``." - -msgid "It specifies a table type and table customize options." -msgstr "It specifies a table type and table customize options." - -msgid "Here are available flags:" -msgstr "Here are available flags:" - -msgid "description" -msgstr "description" - -msgid "flags" -msgstr "flags" - -msgid "Array table." -msgstr "Array table." - -msgid "``TABLE_NO_KEY``" -msgstr "``TABLE_NO_KEY``" - -msgid "Hash table." -msgstr "Hash table." - -msgid "``TABLE_HASH_KEY``" -msgstr "``TABLE_HASH_KEY``" - -msgid "Patricia trie." -msgstr "Patricia trie." - -msgid "``TABLE_PAT_KEY``" -msgstr "``TABLE_PAT_KEY``" - -msgid "Double Array trie." -msgstr "Double Array trie." - -msgid "``TABLE_DAT_KEY``" -msgstr "``TABLE_DAT_KEY``" - -msgid "Enable Semi Infinite String. Require ``TABLE_PAT_KEY``." -msgstr "Enable Semi Infinite String. Require ``TABLE_PAT_KEY``." - -msgid "``KEY_WITH_SIS``" -msgstr "``KEY_WITH_SIS``" - -msgid "" -"Since Groonga 2.1.0 ``KEY_NORMALIZE`` flag is deprecated. Use ``normalizer`` " -"option with ``NormalizerAuto`` instead." -msgstr "" -"Since Groonga 2.1.0 ``KEY_NORMALIZE`` flag is deprecated. Use ``normalizer`` " -"option with ``NormalizerAuto`` instead." - -msgid "" -"You must specify one of ``TABLE_${TYPE}`` flags. You cannot specify two or " -"more ``TABLE_${TYPE}`` flags. For example, ``TABLE_NO_KEY|TABLE_HASH_KEY`` " -"is invalid." -msgstr "" -"You must specify one of ``TABLE_${TYPE}`` flags. You cannot specify two or " -"more ``TABLE_${TYPE}`` flags. For example, ``TABLE_NO_KEY|TABLE_HASH_KEY`` " -"is invalid." - -msgid "" -"You can combine flags with ``|`` (vertical bar) such as ``TABLE_PAT_KEY|" -"KEY_WITH_SIS``." -msgstr "" -"You can combine flags with ``|`` (vertical bar) such as ``TABLE_PAT_KEY|" -"KEY_WITH_SIS``." - -msgid "See :doc:`/reference/tables` for difference between table types." -msgstr "See :doc:`/reference/tables` for difference between table types." - -msgid "The default flags are ``TABLE_HASH_KEY``." -msgstr "The default flags are ``TABLE_HASH_KEY``." - -msgid "``key_type``" -msgstr "``key_type``" - -msgid "It specifies key type." -msgstr "It specifies key type." - -msgid "" -"If you specify ``TABLE_HASH_KEY``, ``TABLE_PAT_KEY`` or ``TABLE_DAT_KEY`` as " -"``flags`` parameter, you need to specify ``key_type`` option." -msgstr "" -"If you specify ``TABLE_HASH_KEY``, ``TABLE_PAT_KEY`` or ``TABLE_DAT_KEY`` as " -"``flags`` parameter, you need to specify ``key_type`` option." - -msgid "See :doc:`/reference/types` for all types." -msgstr "See :doc:`/reference/types` for all types." - -msgid "The default value is none." -msgstr "The default value is none." - -msgid "``value_type``" -msgstr "``value_type``" - -msgid "It specifies value type." -msgstr "It specifies value type." - -msgid "" -"You can use value when you specify ``TABLE_NO_KEY``, ``TABLE_HASH_KEY`` or " -"``TABLE_PAT_KEY`` as ``flags`` parameter. Value type must be a fixed size " -"type. For example, ``UInt32`` can be used but ``ShortText`` cannot be used. " -"Use columns instead of value." -msgstr "" -"You can use value when you specify ``TABLE_NO_KEY``, ``TABLE_HASH_KEY`` or " -"``TABLE_PAT_KEY`` as ``flags`` parameter. Value type must be a fixed size " -"type. For example, ``UInt32`` can be used but ``ShortText`` cannot be used. " -"Use columns instead of value." - -msgid "``default_tokenizer``" -msgstr "``default_tokenizer``" - -msgid "" -"It specifies the default tokenizer that is used on searching and data " -"loading." -msgstr "" -"It specifies the default tokenizer that is used on searching and data " -"loading." - -msgid "" -"You cannot use ``default_tokenizer`` with ``TABLE_NO_KEY`` because " -"``TABLE_NO_KEY`` cannot be used for index." -msgstr "" -"You cannot use ``default_tokenizer`` with ``TABLE_NO_KEY`` because " -"``TABLE_NO_KEY`` cannot be used for index." - -msgid "" -"You must specify ``default_tokenizer`` for a table that is used for fulltext " -"search index." -msgstr "" -"You must specify ``default_tokenizer`` for a table that is used for fulltext " -"search index." - -msgid "See :doc:`/reference/tokenizers` for all tokenizers" -msgstr "See :doc:`/reference/tokenizers` for all tokenizers" - -msgid "It specifies a normalizer that is used to normalize key." -msgstr "It specifies a normalizer that is used to normalize key." - -msgid "" -"You cannot use ``normalizer`` with ``TABLE_NO_KEY`` because ``TABLE_NO_KEY`` " -"doesn't support key." -msgstr "" -"You cannot use ``normalizer`` with ``TABLE_NO_KEY`` because ``TABLE_NO_KEY`` " -"doesn't support key." - -msgid "See :doc:`/reference/normalizers` for all normalizsers." -msgstr "See :doc:`/reference/normalizers` for all normalizsers." - -msgid "``token_filters``" -msgstr "" - -msgid "" -"It specifies token filters that is used to some processes tokenized token." -msgstr "" -"It specifies token filters that is used to some processes tokenized token." - -msgid "" -"You cannot use ``token_filters`` with ``TABLE_NO_KEY`` because " -"``TABLE_NO_KEY`` doesn't support key." -msgstr "" -"You cannot use ``token_filters`` with ``TABLE_NO_KEY`` because " -"``TABLE_NO_KEY`` doesn't support key." - -msgid "See :doc:`/reference/token_filters` for all token filters." -msgstr "See :doc:`/reference/token_filters` for all token filters." - -msgid "``table_create`` returns ``true`` as body on success such as::" -msgstr "``table_create`` returns ``true`` as body on success such as::" - -msgid "If ``table_create`` fails, error details are in ``HEADER``." -msgstr "If ``table_create`` fails, error details are in ``HEADER``." - -msgid ":doc:`/reference/tables`" -msgstr ":doc:`/reference/tables`" - -msgid ":doc:`/reference/tokenizers`" -msgstr ":doc:`/reference/tokenizers`" - -msgid ":doc:`/reference/command/output_format`" -msgstr ":doc:`/reference/command/output_format`" - -msgid "``table_list``" -msgstr "``table_list``" - -msgid "table_list - DBに定義されているテーブルをリスト表示" -msgstr "table_list - DBに定義されているテーブルをリスト表示" - -msgid "" -"Groonga組込コマンドの一つであるtable_listについて説明します。組込コマンドは、" -"groonga実行ファイルの引数、標準 入力、またはソケット経由でgroongaサーバにリク" -"エストを送信することによって実行します。" -msgstr "" - -msgid "table_listは、DBに定義されているテーブルのリストを表示します。" -msgstr "table_listは、DBに定義されているテーブルのリストを表示します。" - -msgid "テーブル名一覧が以下の形式で返却されます。::" -msgstr "テーブル名一覧が以下の形式で返却されます。::" - -msgid "``テーブル情報名n``" -msgstr "``テーブル情報名n``" - -msgid "" -"``テーブル情報n`` には複数の情報が含まれますが、そこに入る情報がどんな内容か" -"を示す名前を出力します。 情報名は以下の通りです。" -msgstr "" -"``テーブル情報n`` には複数の情報が含まれますが、そこに入る情報がどんな内容か" -"を示す名前を出力します。 情報名は以下の通りです。" - -msgid "テーブルオブジェクトに割り当てられたID" -msgstr "テーブルオブジェクトに割り当てられたID" - -msgid "テーブル名" -msgstr "テーブル名" - -msgid "テーブルのレコードを格納するファイル名" -msgstr "テーブルのレコードを格納するファイル名" - -msgid "テーブルのflags属性" -msgstr "テーブルのflags属性" - -msgid "``domain``" -msgstr "``domain``" - -msgid "主キー値の属する型" -msgstr "主キー値の属する型" - -msgid "``range``" -msgstr "``range``" - -msgid "valueが属する型" -msgstr "valueが属する型" - -msgid "``テーブル情報型n``" -msgstr "``テーブル情報型n``" - -msgid "テーブル情報の型を出力します。" -msgstr "テーブル情報の型を出力します。" - -msgid "``テーブル情報n``" -msgstr "``テーブル情報n``" - -msgid "" -"``テーブル情報名n`` で示された情報の配列を出力します。 情報の順序は ``テーブ" -"ル情報名n`` の順序と同じです。" -msgstr "" -"``テーブル情報名n`` で示された情報の配列を出力します。 情報の順序は ``テーブ" -"ル情報名n`` の順序と同じです。" - -msgid "``table_remove``" -msgstr "``table_remove``" - -msgid "table_remove - テーブルの削除" -msgstr "table_remove - テーブルの削除" - -msgid "" -"groonga組込コマンドの一つであるtable_removeについて説明します。組込コマンド" -"は、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバに" -"リクエストを送信することによって実行します。" -msgstr "" -"groonga組込コマンドの一つであるtable_removeについて説明します。組込コマンド" -"は、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバに" -"リクエストを送信することによって実行します。" - -msgid "" -"table_removeはテーブルと定義されているカラムを削除します。カラムに付随するイ" -"ンデックスも再帰的に削除されます。" -msgstr "" -"table_removeはテーブルと定義されているカラムを削除します。カラムに付随するイ" -"ンデックスも再帰的に削除されます。" - -msgid "``table_tokenize``" -msgstr "" - -msgid "" -"``table_tokenize`` command tokenizes text by the specified table's tokenizer." -msgstr "" -"``table_tokenize`` command tokenizes text by the specified table's tokenizer." - -msgid "" -"``table_tokenize`` command has required parameters and optional parameters. " -"``table`` and ``string`` are required parameters. Others are optional::" -msgstr "" -"``table_tokenize`` command has required parameters and optional parameters. " -"``table`` and ``string`` are required parameters. Others are optional::" - -msgid "" -"``Terms`` table is set ``TokenBigram`` tokenizer, ``NormalizerAuto`` " -"normalizer, ``TokenFilterStopWord`` token filter. It returns tokens that is " -"generated by tokenizeing ``\"Hello and Good-bye\"`` with ``TokenBigram`` " -"tokenizer. It is normalized by ``NormalizerAuto`` normalizer. ``and`` token " -"is removed with ``TokenFilterStopWord`` token filter." -msgstr "" -"``Terms`` table is set ``TokenBigram`` tokenizer, ``NormalizerAuto`` " -"normalizer, ``TokenFilterStopWord`` token filter. It returns tokens that is " -"generated by tokenizeing ``\"Hello and Good-bye\"`` with ``TokenBigram`` " -"tokenizer. It is normalized by ``NormalizerAuto`` normalizer. ``and`` token " -"is removed with ``TokenFilterStopWord`` token filter." - -msgid "There are required parameters, ``table`` and ``string``." -msgstr "There are required parameters, ``table`` and ``string``." - -msgid "" -"It specifies the lexicon table. ``table_tokenize`` command uses the " -"tokenizer, the normalizer, the token filters that is set the lexicon table." -msgstr "" -"It specifies the lexicon table. ``table_tokenize`` command uses the " -"tokenizer, the normalizer, the token filters that is set the lexicon table." - -msgid "It specifies any string which you want to tokenize." -msgstr "It specifies any string which you want to tokenize." - -msgid "" -"See :ref:`tokenize-string` option in :doc:`/reference/commands/tokenize` " -"about details." -msgstr "" -"See :ref:`tokenize-string` option in :doc:`/reference/commands/tokenize` " -"about details." - -msgid "" -"It specifies a tokenization customize options. You can specify multiple " -"options separated by \"``|``\"." -msgstr "" -"It specifies a tokenization customize options. You can specify multiple " -"options separated by \"``|``\"." - -msgid "The default value is ``NONE``." -msgstr "" - -msgid "" -"See :ref:`tokenize-flags` option in :doc:`/reference/commands/tokenize` " -"about details." -msgstr "" -"See :ref:`tokenize-flags` option in :doc:`/reference/commands/tokenize` " -"about details." - -msgid "``mode``" -msgstr "" - -msgid "It specifies a tokenize mode." -msgstr "It specifies a tokenize mode." - -msgid "The default value is ``GET``." -msgstr "" - -msgid "" -"See :ref:`tokenize-mode` option in :doc:`/reference/commands/tokenize` about " -"details." -msgstr "" -"See :ref:`tokenize-mode` option in :doc:`/reference/commands/tokenize` about " -"details." - -msgid "``table_tokenize`` command returns tokenized tokens." -msgstr "``table_tokenize`` command returns tokenized tokens." - -msgid "" -"See :ref:`tokenize-return-value` option in :doc:`/reference/commands/" -"tokenize` about details." -msgstr "" -"See :ref:`tokenize-return-value` option in :doc:`/reference/commands/" -"tokenize` about details." - -msgid ":doc:`/reference/commands/tokenize`" -msgstr "" - -msgid "``tokenize``" -msgstr "``tokenize``" - -msgid "" -"``tokenize`` command tokenizes text by the specified tokenizer. It is useful " -"to debug tokenization." -msgstr "" -"``tokenize`` command tokenizes text by the specified tokenizer. It is useful " -"to debug tokenization." - -msgid "" -"``tokenize`` command has required parameters and optional parameters. " -"``tokenizer`` and ``string`` are required parameters. Others are optional::" -msgstr "" -"``tokenize`` command has required parameters and optional parameters. " -"``tokenizer`` and ``string`` are required parameters. Others are optional::" - -msgid "" -"It has only required parameters. ``tokenizer`` is ``TokenBigram`` and " -"``string`` is ``\"Fulltext Search\"``. It returns tokens that is generated " -"by tokenizing ``\"Fulltext Search\"`` with ``TokenBigram`` tokenizer. It " -"doesn't normalize ``\"Fulltext Search\"``." -msgstr "" -"It has only required parameters. ``tokenizer`` is ``TokenBigram`` and " -"``string`` is ``\"Fulltext Search\"``. It returns tokens that is generated " -"by tokenizing ``\"Fulltext Search\"`` with ``TokenBigram`` tokenizer. It " -"doesn't normalize ``\"Fulltext Search\"``." - -msgid "There are required parameters, ``tokenizer`` and ``string``." -msgstr "There are required parameters, ``tokenizer`` and ``string``." - -msgid "``tokenizer``" -msgstr "``tokenizer``" - -msgid "" -"It specifies the tokenizer name. ``tokenize`` command uses the tokenizer " -"that is named ``tokenizer``." -msgstr "" -"It specifies the tokenizer name. ``tokenize`` command uses the tokenizer " -"that is named ``tokenizer``." - -msgid "See :doc:`/reference/tokenizers` about built-in tokenizers." -msgstr "See :doc:`/reference/tokenizers` about built-in tokenizers." - -msgid "Here is an example to use built-in ``TokenTrigram`` tokenizer." -msgstr "Here is an example to use built-in ``TokenTrigram`` tokenizer." - -msgid "" -"If you want to use other tokenizers, you need to register additional " -"tokenizer plugin by :doc:`register` command. For example, you can use `KyTea " -"<http://www.phontron.com/kytea/>`_ based tokenizer by registering " -"``tokenizers/kytea``." -msgstr "" -"If you want to use other tokenizers, you need to register additional " -"tokenizer plugin by :doc:`register` command. For example, you can use `KyTea " -"<http://www.phontron.com/kytea/>`_ based tokenizer by registering " -"``tokenizers/kytea``." - -msgid "" -"It specifies the normalizer name. ``tokenize`` command uses the normalizer " -"that is named ``normalizer``. Normalizer is important for N-gram family " -"tokenizers such as ``TokenBigram``." -msgstr "" -"It specifies the normalizer name. ``tokenize`` command uses the normalizer " -"that is named ``normalizer``. Normalizer is important for N-gram family " -"tokenizers such as ``TokenBigram``." - -msgid "" -"Normalizer detects character type for each character while normalizing. N-" -"gram family tokenizers use character types while tokenizing." -msgstr "" -"Normalizer detects character type for each character while normalizing. N-" -"gram family tokenizers use character types while tokenizing." - -msgid "Here is an example that doesn't use normalizer." -msgstr "Here is an example that doesn't use normalizer." - -msgid "" -"All alphabets are tokenized by two characters. For example, ``Fu`` is a " -"token." -msgstr "" -"All alphabets are tokenized by two characters. For example, ``Fu`` is a " -"token." - -msgid "Here is an example that uses normalizer." -msgstr "Here is an example that uses normalizer." - -msgid "" -"Continuous alphabets are tokenized as one token. For example, ``fulltext`` " -"is a token." -msgstr "" -"Continuous alphabets are tokenized as one token. For example, ``fulltext`` " -"is a token." - -msgid "" -"If you want to tokenize by two characters with noramlizer, use " -"``TokenBigramSplitSymbolAlpha``." -msgstr "" -"If you want to tokenize by two characters with noramlizer, use " -"``TokenBigramSplitSymbolAlpha``." - -msgid "" -"All alphabets are tokenized by two characters. And they are normalized to " -"lower case characters. For example, ``fu`` is a token." -msgstr "" -"All alphabets are tokenized by two characters. And they are normalized to " -"lower case characters. For example, ``fu`` is a token." - -msgid "" -"It specifies a tokenization customize options. You can specify multiple " -"options separated by \"``|``\". For example, ``NONE|" -"ENABLE_TOKENIZED_DELIMITER``." -msgstr "" -"It specifies a tokenization customize options. You can specify multiple " -"options separated by \"``|``\". For example, ``NONE|" -"ENABLE_TOKENIZED_DELIMITER``." - -msgid "``ENABLE_TOKENIZED_DELIMITER``" -msgstr "``ENABLE_TOKENIZED_DELIMITER``" - -msgid "" -"Enables tokenized delimiter. See :doc:`/reference/tokenizers` about " -"tokenized delimiter details." -msgstr "" -"Enables tokenized delimiter. See :doc:`/reference/tokenizers` about " -"tokenized delimiter details." - -msgid "Here is an example that uses ``ENABLE_TOKENIZED_DELIMITER``." -msgstr "Here is an example that uses ``ENABLE_TOKENIZED_DELIMITER``." - -msgid "" -"``TokenDelimit`` tokenizer is one of tokenized delimiter supported " -"tokenizer. ``ENABLE_TOKENIZED_DELIMITER`` enables tokenized delimiter. " -"Tokenized delimiter is special character that indicates token border. It is " -"``U+FFFE``. The character is not assigned any character. It means that the " -"character is not appeared in normal string. So the character is good " -"character for this puropose. If ``ENABLE_TOKENIZED_DELIMITER`` is enabled, " -"the target string is treated as already tokenized string. Tokenizer just " -"tokenizes by tokenized delimiter." -msgstr "" -"``TokenDelimit`` tokenizer is one of tokenized delimiter supported " -"tokenizer. ``ENABLE_TOKENIZED_DELIMITER`` enables tokenized delimiter. " -"Tokenized delimiter is special character that indicates token border. It is " -"``U+FFFE``. The character is not assigned any character. It means that the " -"character is not appeared in normal string. So the character is good " -"character for this puropose. If ``ENABLE_TOKENIZED_DELIMITER`` is enabled, " -"the target string is treated as already tokenized string. Tokenizer just " -"tokenizes by tokenized delimiter." - -msgid "" -"It specifies a tokenize mode. If the mode is specified ``ADD``, the text is " -"tokenized by the rule that adding a document. If the mode is specified " -"``GET``, the text is tokenized by the rule that searching a document. If the " -"mode is omitted, the text is tokenized by the ``ADD`` mode." -msgstr "" -"It specifies a tokenize mode. If the mode is specified ``ADD``, the text is " -"tokenized by the rule that adding a document. If the mode is specified " -"``GET``, the text is tokenized by the rule that searching a document. If the " -"mode is omitted, the text is tokenized by the ``ADD`` mode." - -msgid "The default mode is ``ADD``." -msgstr "" - -msgid "Here is an example to the ``ADD`` mode." -msgstr "Here is an example to the ``ADD`` mode." - -msgid "The last alphabet is tokenized by one character." -msgstr "The last alphabet is tokenized by one character." - -msgid "Here is an example to the ``GET`` mode." -msgstr "Here is an example to the ``GET`` mode." - -msgid "The last alphabet is tokenized by two characters." -msgstr "The last alphabet is tokenized by two characters." - -msgid "" -"It specifies the token filter names. ``tokenize`` command uses the tokenizer " -"that is named ``token_filters``." -msgstr "" -"It specifies the token filter names. ``tokenize`` command uses the tokenizer " -"that is named ``token_filters``." - -msgid "See :doc:`/reference/token_filters` about token filters." -msgstr "See :doc:`/reference/token_filters` about token filters." - -msgid "" -"``tokenize`` command returns tokenized tokens. Each token has some " -"attributes except token itself. The attributes will be increased in the " -"feature::" -msgstr "" -"``tokenize`` command returns tokenized tokens. Each token has some " -"attributes except token itself. The attributes will be increased in the " -"feature::" - -msgid "``tokens``" -msgstr "``tokens``" - -msgid "" -"``tokens`` is an array of token. Token is an object that has the following " -"attributes." -msgstr "" -"``tokens`` is an array of token. Token is an object that has the following " -"attributes." - -msgid "``value``" -msgstr "``value``" - -msgid "Token itself." -msgstr "Token itself." - -msgid "``position``" -msgstr "``position``" - -msgid "The N-th token." -msgstr "The N-th token." - -msgid "``tokenizer_list``" -msgstr "" - -msgid "``tokenizer_list`` command lists tokenizers in a database." -msgstr "" - -msgid "``tokenizer_list`` command takes no parameter. ::" -msgstr "" - -msgid "It returns tokenizers in a database." -msgstr "" - -msgid "" -"``tokenizer_list`` command returns tokenizers. Each tokenizers has an " -"attribute that contains the name. The attribute will be increased in the " -"feature::" -msgstr "" - -msgid "``tokenizers``" -msgstr "" - -msgid "" -"``tokenizers`` is an array of tokenizer. Tokenizer is an object that has the " -"following attributes." -msgstr "" - -msgid "Tokenizer name." -msgstr "" - -msgid "``truncate``" -msgstr "``truncate``" - -msgid "" -"``truncate`` command deletes all records from specified table or all values " -"from specified column." -msgstr "" - -msgid "The required parameter is only ``target_name``::" -msgstr "" - -# eacfe2fd99ff4d288665e8b7e3b318bc -msgid "" -"``target_name`` parameter can be used since 4.0.9. You need to use ``table`` " -"parameter for 4.0.8 or earlier." -msgstr "" - -# 618d2efd4f70422eb408ab2ce093228f -msgid "" -"For backward compatibility, ``truncate`` command accepts ``table`` " -"parameter. But it should not be used for newly written code." -msgstr "" - -msgid "Here is a simple example of ``truncate`` command against a table." -msgstr "" - -msgid "Here is a simple example of ``truncate`` command against a column." -msgstr "" - -msgid "This section describes parameters of ``truncate``." -msgstr "This section describes parameters of ``truncate``." - -msgid "There is required parameter, ``target_name``." -msgstr "" - -# 86370f5f205f4ff682ec896a81ec8856 -msgid "``truncate`` command returns whether truncation is succeeded or not::" -msgstr "" - -msgid "Executables" -msgstr "Executables" - -msgid "This section describes executable files provided by groonga package." -msgstr "This section describes executable files provided by groonga package." - -msgid "``grndb``" -msgstr "" - -# dc50df85d7844d28bc610836aff86c6b -msgid "This executable command is an experimental feature." -msgstr "" - -# c94eb5ab6c4f432ba5b96bb865554620 -msgid "``grndb`` manages a Groonga database." -msgstr "" - -msgid "Here are features:" -msgstr "" - -# 4914fb8cf17246cf87289d3c5c848d01 -msgid "Checks whether database is broken or not." -msgstr "" - -# bdf35dd95ce54a92a8bfbf3b23330694 -msgid "Recovers broken database automatically if the database is recoverable." -msgstr "" - -# c5623b075c524076a5f1567f18da2197 -msgid "``grndb`` requires command and database path::" -msgstr "" - -msgid "Here are available commands:" -msgstr "" - -# cc3e5070687446678fb14ccdbf9bcd53 -msgid "``check`` - Checks whether database is broken or not." -msgstr "" - -# bba8325a9e3b486ea04cb1cbd606485a -msgid "``recover`` - Recovers database." -msgstr "" - -msgid "" -"Here is an example to check the database at ``/var/lib/groonga/db/db``::" -msgstr "" - -msgid "" -"Here is an example to recover the database at ``/var/lib/groonga/db/db``::" -msgstr "" - -msgid "Commands" -msgstr "" - -msgid "This section describes available commands." -msgstr "" - -# e23b3bdf6f6542afb826b543476e16a8 -msgid "" -"It checks an existing Groonga database. If the database is broken, ``grndb`` " -"reports reasons and exits with non-``0`` exit status." -msgstr "" - -# f8cc59eca6ad4707928c66c7c6893175 -msgid "" -"You must not use this command for opened database. If the database is " -"opened, this command may report wrong result." -msgstr "" - -msgid "``recover``" -msgstr "" - -# 3dcf9077fb354d05ad39007cf5a1f58e -msgid "It recovers an existing broken Groonga database." -msgstr "" - -# 31e20f6c01ce411a938b3ba78c28cebe -msgid "" -"If the database is not broken, ``grndb`` does nothing and exits with ``0`` " -"exit status." -msgstr "" - -# 83971e14a44c4c43a45653fce788fd3a -msgid "" -"If the database is broken and one or more index columns are only broken, " -"``grndb`` recovers these index columns and exists with ``0`` exit status. It " -"may take a long time for large indexed data." -msgstr "" - -# 07b128f6bf54418abde9b9ed52fa57e1 -msgid "" -"If the database is broken and tables or data columns are broken, ``grndb`` " -"reports broken reasons and exits with non-``0`` exit status. You can know " -"whether the database is recoverable or not by ``check`` command." -msgstr "" - -# c5f81ca168dd41a7aa6592f27eeacdfa -msgid "" -"You must not use this command for opened database. If the database is " -"opened, this command may break the database." -msgstr "" - -msgid "grnslap" -msgstr "grnslap" - -msgid "grnslap - groongaプロセスの通信層のパフォーマンスをチェックするツール" -msgstr "grnslap - groongaプロセスの通信層のパフォーマンスをチェックするツール" - -msgid "書式" -msgstr "書式" - -msgid "" -"grnslapは、groongaプロセスに対してリクエストを多重に行い、パフォーマンスを" -"チェックするためのツールです。" -msgstr "" -"grnslapは、groongaプロセスに対してリクエストを多重に行い、パフォーマンスを" -"チェックするためのツールです。" - -msgid "" -"Groonga独自プロトコルであるGQTPと、httpの両プロトコルでリクエストを行うことが" -"できます。また、リクエストの多重度を指定することができます。" -msgstr "" -"Groonga独自プロトコルであるGQTPと、httpの両プロトコルでリクエストを行うことが" -"できます。また、リクエストの多重度を指定することができます。" - -msgid "" -"クエリの内容を標準入力から与えることができます。実稼動環境でのクエリパタンに" -"近いクエリを標準入力に与えることによって、実稼動環境に近い状態での検証を行う" -"ことができます。" -msgstr "" -"クエリの内容を標準入力から与えることができます。実稼動環境でのクエリパタンに" -"近いクエリを標準入力に与えることによって、実稼動環境に近い状態での検証を行う" -"ことができます。" - -msgid "現在は、make installしてもインストールは行われない。" -msgstr "現在は、make installしてもインストールは行われない。" - -msgid "オプション" -msgstr "オプション" - -msgid "リクエストのプロトコルを指定します。" -msgstr "リクエストのプロトコルを指定します。" - -msgid "`http`" -msgstr "`http`" - -msgid "" -"httpでリクエストします。対象のhttpのパス群(GETパラメータを含む)をLF区切り形式" -"で標準入力に与えると、それらのパスに順次アクセスします。" -msgstr "" -"httpでリクエストします。対象のhttpのパス群(GETパラメータを含む)をLF区切り形式" -"で標準入力に与えると、それらのパスに順次アクセスします。" - -msgid "`gqtp`" -msgstr "`gqtp`" - -msgid "" -"gqtpでリクエストします。gqtpのリクエストをLF区切り形式で標準入力に与えると、" -"それらのリクエストを順次行います。" -msgstr "" -"gqtpでリクエストします。gqtpのリクエストをLF区切り形式で標準入力に与えると、" -"それらのリクエストを順次行います。" - -msgid "リクエストの多重度を指定します。初期値は10です。" -msgstr "リクエストの多重度を指定します。初期値は10です。" - -msgid "引数" -msgstr "引数" - -msgid "" -"接続先のホスト名とポート番号をを指定します(デフォルト値は'localhost:10041')。" -"ポート番号を指定しない場合には、10041が指定されたものとします。" -msgstr "" -"接続先のホスト名とポート番号をを指定します(デフォルト値は'localhost:10041')。" -"ポート番号を指定しない場合には、10041が指定されたものとします。" - -msgid "サンプル" -msgstr "サンプル" - -msgid "http://localhost:10041/d/status に、多重度100でリクエストを行う。" -msgstr "http://localhost:10041/d/status に、多重度100でリクエストを行う。" - -msgid "groonga-benchmark" -msgstr "groonga-benchmark" - -msgid "groonga-benchmark - groongaテストプログラム" -msgstr "groonga-benchmark - groongaテストプログラム" - -msgid "groonga-benchmarkは、groonga汎用ベンチマークツールです。" -msgstr "groonga-benchmarkは、groonga汎用ベンチマークツールです。" - -msgid "" -"groongaを単独のプロセスとして利用する場合はもちろん、サーバプログラムとして利" -"用する場合の動作確認や実行速度測定が可能です。" -msgstr "" -"groongaを単独のプロセスとして利用する場合はもちろん、サーバプログラムとして利" -"用する場合の動作確認や実行速度測定が可能です。" - -msgid "" -"groonga-benchmark用のデータファイルは自分で作成することも既存のものを利用する" -"こともできます。既存のデータファイルは、ftp.groonga.orgから必要に応じダウン" -"ロードします。そのため、groonga及びgroonga-benchmarkが動作し、インターネット" -"に接続できる環境であればgroongaコマンドの知識がなくてもgroongaの動作を確認で" -"きます。" -msgstr "" -"groonga-benchmark用のデータファイルは自分で作成することも既存のものを利用する" -"こともできます。既存のデータファイルは、ftp.groonga.orgから必要に応じダウン" -"ロードします。そのため、groonga及びgroonga-benchmarkが動作し、インターネット" -"に接続できる環境であればgroongaコマンドの知識がなくてもgroongaの動作を確認で" -"きます。" - -msgid "" -"現在は、Linux 及びWindows上で動作します。make installしてもインストールは行わ" -"れません。" -msgstr "" -"現在は、Linux 及びWindows上で動作します。make installしてもインストールは行わ" -"れません。" - -msgid "" -"接続するgroongaサーバを、ipアドレスまたはホスト名で指定します。指定先に" -"groongaサーバが立ち上がっていない場合、接続不能となることに注意してください。" -"このオプションを指定しない場合、groonga-benchmarkは自動的にlocalhostのgroonga" -"サーバを起動して接続します。" -msgstr "" -"接続するgroongaサーバを、ipアドレスまたはホスト名で指定します。指定先に" -"groongaサーバが立ち上がっていない場合、接続不能となることに注意してください。" -"このオプションを指定しない場合、groonga-benchmarkは自動的にlocalhostのgroonga" -"サーバを起動して接続します。" - -msgid "" -"自動的に起動するgroongaサーバ、または明示的に指定した接続先のgroonga サーバが" -"利用するポート番号を指定します。接続先のgroongaサーバが利用しているポートと、" -"このオプションで指定したポート番号が異なる場合、接続不能となることに注意して" -"ください。" -msgstr "" -"自動的に起動するgroongaサーバ、または明示的に指定した接続先のgroonga サーバが" -"利用するポート番号を指定します。接続先のgroongaサーバが利用しているポートと、" -"このオプションで指定したポート番号が異なる場合、接続不能となることに注意して" -"ください。" - -msgid "ftp.groonga.org に用意されているスクリプトファイルを表示します。" -msgstr "ftp.groonga.org に用意されているスクリプトファイルを表示します。" - -msgid "" -"ftp.groonga.orgとFTP通信を行い、scriptファイルの同期やログファイルの送信を行" -"います。" -msgstr "" -"ftp.groonga.orgとFTP通信を行い、scriptファイルの同期やログファイルの送信を行" -"います。" - -msgid "" -"デフォルトでは、groonga-benchmark終了後のログファイルの出力先ははカレントディ" -"レクトリです。このオプションを利用すると、任意のディレクトリに出力先を変更す" -"ることができます。" -msgstr "" -"デフォルトでは、groonga-benchmark終了後のログファイルの出力先ははカレントディ" -"レクトリです。このオプションを利用すると、任意のディレクトリに出力先を変更す" -"ることができます。" - -msgid "" -"groongaコマンドのパスを指定します。デフォルトでは、PATHの中からgroongaコマン" -"ドを探します。" -msgstr "" -"groongaコマンドのパスを指定します。デフォルトでは、PATHの中からgroongaコマン" -"ドを探します。" - -msgid "" -"groongaコマンドが使うプロトコルとして `gqtp` または `http` を指定します。" -msgstr "" -"groongaコマンドが使うプロトコルとして `gqtp` または `http` を指定します。" - -msgid "" -"groonga-benchmarkの動作方法(以下、groonga-benchmark命令と呼びます)を記述した" -"テキストファイルです。拡張子は.scrです。" -msgstr "" -"groonga-benchmarkの動作方法(以下、groonga-benchmark命令と呼びます)を記述した" -"テキストファイルです。拡張子は.scrです。" - -msgid "" -"groonga-benchmarkが利用するgroonga データベースです。指定されたデータベースが" -"存在しない場合、groonga-benchmarkが新規に作成します。またgroonga サーバを自動" -"的に起動する場合もこの引数で指定したデータベースが利用されます。接続する" -"groonga サーバを明示的に指定した場合に利用するデータベースは、接続先サーバが" -"使用中のデータベースになることに注意してください。" -msgstr "" -"groonga-benchmarkが利用するgroonga データベースです。指定されたデータベースが" -"存在しない場合、groonga-benchmarkが新規に作成します。またgroonga サーバを自動" -"的に起動する場合もこの引数で指定したデータベースが利用されます。接続する" -"groonga サーバを明示的に指定した場合に利用するデータベースは、接続先サーバが" -"使用中のデータベースになることに注意してください。" - -msgid "使い方" -msgstr "使い方" - -msgid "まず、シェル上(Windowsならコマンドプロンプト上)で::" -msgstr "まず、シェル上(Windowsならコマンドプロンプト上)で::" - -msgid "とタイプしてください。もしgroonga-benchmarkが正常に動作すれば、::" -msgstr "とタイプしてください。もしgroonga-benchmarkが正常に動作すれば、::" - -msgid "" -"というファイルが作成されるはずです。作成されない場合、このドキュメントの「ト" -"ラブルシューティング」の章を参照してください。" -msgstr "" -"というファイルが作成されるはずです。作成されない場合、このドキュメントの「ト" -"ラブルシューティング」の章を参照してください。" - -msgid "スクリプトファイル" -msgstr "スクリプトファイル" - -msgid "" -"スクリプトファイルは、groonga-benchmark命令を記述したテキストファイルです。 " -"\";\"セミコロンを利用して、一行に複数のgroonga-benchmark命令を記述することが" -"できます。一行に複数のgroonga-benchmark命令がある場合、各命令は並列に実行され" -"ます。 \"#\"で始まる行はコメントとして扱われます。" -msgstr "" -"スクリプトファイルは、groonga-benchmark命令を記述したテキストファイルです。 " -"\";\"セミコロンを利用して、一行に複数のgroonga-benchmark命令を記述することが" -"できます。一行に複数のgroonga-benchmark命令がある場合、各命令は並列に実行され" -"ます。 \"#\"で始まる行はコメントとして扱われます。" - -msgid "groonga-benchmark命令" -msgstr "groonga-benchmark命令" - -msgid "現在サポートされているgroonga-benchmark命令は以下の11種類です。" -msgstr "" - -msgid "do_local コマンドファイル [スレッド数] [繰り返し数]" -msgstr "do_local コマンドファイル [スレッド数] [繰り返し数]" - -msgid "" -"コマンドファイルをgroonga-benchmark単体で実行します。スレッド数が指定されてい" -"る場合、複数のスレッドで同じコマンドファイルを同時に実行します。繰り返し数が" -"指定されてい場合、コマンドファイルの内容を繰り返し実行します。スレッド数、繰" -"り返し数とも省略時は1です。1スレッドで複数回動作させたい場合は、do_local コマ" -"ンドファイル 1 [繰り返し数]と明示的に指定してください。" -msgstr "" -"コマンドファイルをgroonga-benchmark単体で実行します。スレッド数が指定されてい" -"る場合、複数のスレッドで同じコマンドファイルを同時に実行します。繰り返し数が" -"指定されてい場合、コマンドファイルの内容を繰り返し実行します。スレッド数、繰" -"り返し数とも省略時は1です。1スレッドで複数回動作させたい場合は、do_local コマ" -"ンドファイル 1 [繰り返し数]と明示的に指定してください。" - -msgid "do_gqpt コマンドファイル [スレッド数] [繰り返し数]" -msgstr "do_gqpt コマンドファイル [スレッド数] [繰り返し数]" - -msgid "" -"コマンドファイルをgroongaサーバでGQTP経由で実行します。スレッド数や繰り返し数" -"の意味はdo_localの場合と同じです。" -msgstr "" - -msgid "do_http コマンドファイル [スレッド数] [繰り返し数]" -msgstr "" - -msgid "" -"コマンドファイルをgroongaサーバでHTTP経由で実行します。スレッド数や繰り返し数" -"の意味はdo_localの場合と同じです。" -msgstr "" - -msgid "rep_local コマンドファイル [スレッド数] [繰り返し数]" -msgstr "rep_local コマンドファイル [スレッド数] [繰り返し数]" - -msgid "" -"コマンドファイルをgroonga-benchmark単体で実行し、より詳細な報告を行います。" -msgstr "" -"コマンドファイルをgroonga-benchmark単体で実行し、より詳細な報告を行います。" - -msgid "rep_gqpt コマンドファイル [スレッド数] [繰り返し数]" -msgstr "rep_gqpt コマンドファイル [スレッド数] [繰り返し数]" - -msgid "" -"コマンドファイルをgroongaサーバでGQTP経由で実行し、より詳細な報告を行いま" -"す。 スレッド数や繰り返し数の意味はdo_localと 同じです。" -msgstr "" - -msgid "rep_http コマンドファイル [スレッド数] [繰り返し数]" -msgstr "" - -msgid "" -"コマンドファイルをgroongaサーバでHTTP経由で実行し、より詳細な報告を行いま" -"す。 スレッド数や繰り返し数の意味はdo_localと 同じです。" -msgstr "" - -msgid "out_local コマンドファイル 入力ファイル名" -msgstr "out_local コマンドファイル 入力ファイル名" - -msgid "" -"コマンドファイルをgroonga-benchmark単体で実行し、各コマンドの実行結果をすべ" -"て”出力ファイル\"に書きだします。この結果は、test_local, test_gqtp命令で利用" -"します。なおこの命令の「出力ファイル」とは、groonga-benchmark実行時に自動的に" -"作成されるログとは別のものです。groonga-benchmarkではコメントが利用できる以" -"外、::" -msgstr "" -"コマンドファイルをgroonga-benchmark単体で実行し、各コマンドの実行結果をすべ" -"て”出力ファイル\"に書きだします。この結果は、test_local, test_gqtp命令で利用" -"します。なおこの命令の「出力ファイル」とは、groonga-benchmark実行時に自動的に" -"作成されるログとは別のものです。groonga-benchmarkではコメントが利用できる以" -"外、::" - -msgid "とした場合と同じです。" -msgstr "とした場合と同じです。" - -msgid "out_gqtp コマンドファイル 出力ファイル名" -msgstr "out_gqtp コマンドファイル 出力ファイル名" - -msgid "" -"コマンドファイルをgroongaサーバでGQTP経由で実行します。その他はout_local命令" -"と同等です。" -msgstr "" - -msgid "out_http コマンドファイル 出力ファイル名" -msgstr "" - -msgid "" -"コマンドファイルをgroongaサーバでHTTP経由で実行します。その他はout_local命令" -"と同等です。" -msgstr "" - -msgid "" -"コマンドファイルをgroonga-benchmark単体で実行し、各コマンドの実行結果を入力" -"ファイルと比較します。処理時間など本質的要素以外に差分があった場合、差分を、" -"入力ファイル.diffというファイルに書きだします。" -msgstr "" -"コマンドファイルをgroonga-benchmark単体で実行し、各コマンドの実行結果を入力" -"ファイルと比較します。処理時間など本質的要素以外に差分があった場合、差分を、" -"入力ファイル.diffというファイルに書きだします。" - -msgid "test_local コマンドファイル 入力ファイル名" -msgstr "test_local コマンドファイル 入力ファイル名" - -msgid "コマンドファイル" -msgstr "コマンドファイル" - -msgid "" -"コマンドファイルは、groonga組み込みコマンドを1行に1つずつ記述したテキストファ" -"イルです。拡張子に制限はありません。groonga組み込みコマンドに関しては :doc:`/" -"reference/command` を参照してください。" -msgstr "" -"コマンドファイルは、groonga組み込みコマンドを1行に1つずつ記述したテキストファ" -"イルです。拡張子に制限はありません。groonga組み込みコマンドに関しては :doc:`/" -"reference/command` を参照してください。" - -msgid "スクリプトファイルのサンプルです。::" -msgstr "スクリプトファイルのサンプルです。::" - -msgid "上記の意味は以下のとおりです。" -msgstr "上記の意味は以下のとおりです。" - -msgid "1行目" -msgstr "1行目" - -msgid "コメント行。" -msgstr "コメント行。" - -msgid "2行目" -msgstr "2行目" - -msgid "test.ddl というコマンドファイルをgroonga単体で実行し、詳細に報告する。" -msgstr "" - -msgid "3行目" -msgstr "3行目" - -msgid "" -"test.load というコマンドファイルをgroonga単体で実行する。(最後の\";\"セミコロ" -"ンは複数のgroonga-benchmark命令を記述する場合に必要ですが、この例のように1つ" -"のgroonga-benchmark命令を実行する場合に付与しても問題ありません。)" -msgstr "" -"test.load というコマンドファイルをgroonga単体で実行する。(最後の\";\"セミコロ" -"ンは複数のgroonga-benchmark命令を記述する場合に必要ですが、この例のように1つ" -"のgroonga-benchmark命令を実行する場合に付与しても問題ありません。)" - -msgid "4行目" -msgstr "4行目" - -msgid "" -"test.select というコマンドファイルをgroongaサーバで10個のスレッドで同時に実行" -"する。各スレッドはtest.selectの中身を10回繰り返す。また同時に、groonga単体で" -"test.statusというコマンドファイルを10個のスレッドで実行する。" -msgstr "" -"test.select というコマンドファイルをgroongaサーバで10個のスレッドで同時に実行" -"する。各スレッドはtest.selectの中身を10回繰り返す。また同時に、groonga単体で" -"test.statusというコマンドファイルを10個のスレッドで実行する。" - -msgid "特殊命令" -msgstr "特殊命令" - -msgid "" -"スクリプトファイルのコメント行には特殊コマンドを埋め込むことが可能です。現在" -"サポートされている特殊命令は以下の二つです。" -msgstr "" -"スクリプトファイルのコメント行には特殊コマンドを埋め込むことが可能です。現在" -"サポートされている特殊命令は以下の二つです。" - -msgid "#SET_HOST <ip/hostname>" -msgstr "#SET_HOST <ip/hostname>" - -msgid "" -"-i, --hostオプションと同等の機能です。コマンドラインオプションに指定したIPア" -"ドレス/ホスト名と、SET_HOSTで指定したIPアドレス/ホスト名が異なる場合、またコ" -"マンドラインオプションを指定しなかった場合にもSET_HOSTが優先されます。" -"SET_HOSTを利用した場合、サーバが自動的には起動されないのもコマンドラインオプ" -"ションで指定した場合と同様です。" -msgstr "" -"-i, --hostオプションと同等の機能です。コマンドラインオプションに指定したIPア" -"ドレス/ホスト名と、SET_HOSTで指定したIPアドレス/ホスト名が異なる場合、またコ" -"マンドラインオプションを指定しなかった場合にもSET_HOSTが優先されます。" -"SET_HOSTを利用した場合、サーバが自動的には起動されないのもコマンドラインオプ" -"ションで指定した場合と同様です。" - -msgid "" -"-p, --port オプションと同等の機能です。コマンドラインオプションに指定したポー" -"ト番号とSET_PORTで指定したポート番号が異なる場合、またコマンドラインオプショ" -"ンを指定しなかった場合にもSET_PORTが優先されます。" -msgstr "" -"-p, --port オプションと同等の機能です。コマンドラインオプションに指定したポー" -"ト番号とSET_PORTで指定したポート番号が異なる場合、またコマンドラインオプショ" -"ンを指定しなかった場合にもSET_PORTが優先されます。" - -msgid "#SET_PORT <port number>" -msgstr "#SET_PORT <port number>" - -msgid "" -"特殊命令はスクリプトファイルの任意の場所に書き込むことができます。同一ファイ" -"ル内に複数回特殊命令を記述した場合、「最後の」特殊命令が有効となります。" -msgstr "" -"特殊命令はスクリプトファイルの任意の場所に書き込むことができます。同一ファイ" -"ル内に複数回特殊命令を記述した場合、「最後の」特殊命令が有効となります。" - -msgid "例えば、" -msgstr "例えば、" - -msgid "とコマンド上でポートを指定した場合でも、もしtest.scrの中身が" -msgstr "とコマンド上でポートを指定した場合でも、もしtest.scrの中身が" - -msgid "" -"であれば、自動的に起動されるgroongaサーバはポート番号10400を利用します。" -msgstr "" -"であれば、自動的に起動されるgroongaサーバはポート番号10400を利用します。" - -msgid "groonga-benchmark実行結果" -msgstr "groonga-benchmark実行結果" - -msgid "" -"groonga-benchmarkが正常に終了すると、(拡張子を除いた)スクリプト名-ユーザ名-実" -"行開始時刻.logという形式のログファイルがカレントディレクトリに作られます。ロ" -"グファイルは自動的にftp.groonga.org に送信されます。ログファイルは以下のよう" -"なjson形式のテキストです。" -msgstr "" -"groonga-benchmarkが正常に終了すると、(拡張子を除いた)スクリプト名-ユーザ名-実" -"行開始時刻.logという形式のログファイルがカレントディレクトリに作られます。ロ" -"グファイルは自動的にftp.groonga.org に送信されます。ログファイルは以下のよう" -"なjson形式のテキストです。" - -msgid "制限事項" -msgstr "制限事項" - -msgid "" -"スクリプトファイルの一行には複数のgroonga-benchmark命令を記述できますが、すべ" -"てのスレッド数の合計は最大64までに制限されます。" -msgstr "" -"スクリプトファイルの一行には複数のgroonga-benchmark命令を記述できますが、すべ" -"てのスレッド数の合計は最大64までに制限されます。" - -msgid "コマンドファイル中のgroongaコマンドの長さは最長5000000byteです。" -msgstr "コマンドファイル中のgroongaコマンドの長さは最長5000000byteです。" - -msgid "トラブルシューティング" -msgstr "トラブルシューティング" - -msgid "" -"もし、groonga-benchmarkが正常に動作しない場合、まず以下を確認してください。" -msgstr "" -"もし、groonga-benchmarkが正常に動作しない場合、まず以下を確認してください。" - -msgid "" -"インターネットに接続しているか？ `--ftp` オプションを指定すると、groonga-" -"benchmarkは動作のたびにftp.groonga.orgと通信します。ftp.groonga.orgと通信可能" -"でない場合、groonga-benchmarkは正常に動作しません。" -msgstr "" -"インターネットに接続しているか？ `--ftp` オプションを指定すると、groonga-" -"benchmarkは動作のたびにftp.groonga.orgと通信します。ftp.groonga.orgと通信可能" -"でない場合、groonga-benchmarkは正常に動作しません。" - -msgid "" -"groonga サーバが動作していないか？ groonga-benchmarkは、-i, --host オプショ" -"ンで明示的にサーバを指定しないかぎり、自動的にlocalhostのgroongaサーバを立ち" -"上げます。すでにgroongaサーバが動作している場合、groonga-benchmarkは正常に動" -"作しない可能性があります。" -msgstr "" -"groonga サーバが動作していないか？ groonga-benchmarkは、-i, --host オプショ" -"ンで明示的にサーバを指定しないかぎり、自動的にlocalhostのgroongaサーバを立ち" -"上げます。すでにgroongaサーバが動作している場合、groonga-benchmarkは正常に動" -"作しない可能性があります。" - -msgid "" -"指定したDBが適切か？ groonga-benchmarkは、引数で指定したDBの中身はチェックし" -"ません。もし指定されたDBが存在しなければ自動的にDBを作成しますが、もしファイ" -"ルとして存在する場合は中身に関わらず動作を続けてしまい、結果が異常になる可能" -"性があります。" -msgstr "" -"指定したDBが適切か？ groonga-benchmarkは、引数で指定したDBの中身はチェックし" -"ません。もし指定されたDBが存在しなければ自動的にDBを作成しますが、もしファイ" -"ルとして存在する場合は中身に関わらず動作を続けてしまい、結果が異常になる可能" -"性があります。" - -msgid "" -"以上の原因でなければ、問題はgroonga-benchmarkかgroongaにあります。ご報告をお" -"願いします。" -msgstr "" -"以上の原因でなければ、問題はgroonga-benchmarkかgroongaにあります。ご報告をお" -"願いします。" - -msgid "groonga-httpd" -msgstr "groonga-httpd" - -msgid "" -"groonga-httpd is a program to communicate with a Groonga server using the " -"HTTP protocol. It functions as same as :doc:`groonga-server-http`. Although :" -"doc:`groonga-server-http` has limited support for HTTP with a minimal built-" -"in HTTP server, groonga-httpd has full support for HTTP with an embedded " -"`nginx <http://nginx.org/>`_. All standards-compliance and features provided " -"by nginx is also available in groonga-httpd." -msgstr "" -"groonga-httpd is a program to communicate with a Groonga server using the " -"HTTP protocol. It functions as same as :doc:`groonga-server-http`. Although :" -"doc:`groonga-server-http` has limited support for HTTP with a minimal built-" -"in HTTP server, groonga-httpd has full support for HTTP with an embedded " -"`nginx <http://nginx.org/>`_. All standards-compliance and features provided " -"by nginx is also available in groonga-httpd." - -msgid "" -"groonga-httpd has an Web-based administration tool implemented with HTML and " -"JavaScript. You can access to it from http://hostname:port/." -msgstr "" -"groonga-httpd has an Web-based administration tool implemented with HTML and " -"JavaScript. You can access to it from http://hostname:port/." - -msgid "Synopsis" -msgstr "Synopsis" - -msgid "Set up" -msgstr "Set up" - -msgid "" -"First, you'll need to edit the groonga-httpd configuration file to specify a " -"database. Edit /etc/groonga/httpd/groonga-httpd.conf to enable the " -"``groonga_database`` directive like this::" -msgstr "" -"First, you'll need to edit the groonga-httpd configuration file to specify a " -"database. Edit /etc/groonga/httpd/groonga-httpd.conf to enable the " -"``groonga_database`` directive like this::" - -msgid "" -"Then, run groonga-httpd. Note that the control immediately returns back to " -"the console because groonga-httpd runs as a daemon process by default.::" -msgstr "" -"Then, run groonga-httpd. Note that the control immediately returns back to " -"the console because groonga-httpd runs as a daemon process by default.::" - -msgid "Request queries" -msgstr "Request queries" - -msgid "To check, request a simple query (:doc:`/reference/commands/status`)." -msgstr "To check, request a simple query (:doc:`/reference/commands/status`)." - -msgid "Loading data by POST" -msgstr "Loading data by POST" - -msgid "" -"The feature of groonga-httpd in contrast to groonga is supporting POST " -"method." -msgstr "" -"The feature of groonga-httpd in contrast to groonga is supporting POST " -"method." - -msgid "You can load data by POST JSON data." -msgstr "You can load data by POST JSON data." - -msgid "" -"Here is an example curl command line that loads two users alice and bob to " -"Users table::" -msgstr "" -"Here is an example curl command line that loads two users alice and bob to " -"Users table::" - -msgid "If you loads users from JSON file, prepare JSON file like this::" -msgstr "If you loads users from JSON file, prepare JSON file like this::" - -msgid "Then specify JSON file in curl command line::" -msgstr "Then specify JSON file in curl command line::" - -msgid "Browse the administration tool" -msgstr "Browse the administration tool" - -msgid "" -"Also, you can browse Web-based administration tool at http://" -"localhost:10041/." -msgstr "" -"Also, you can browse Web-based administration tool at http://" -"localhost:10041/." - -msgid "Shut down" -msgstr "Shut down" - -msgid "Finally, to terminate the running groonga-httpd daemon, run this::" -msgstr "Finally, to terminate the running groonga-httpd daemon, run this::" - -msgid "Configuration directives" -msgstr "Configuration directives" - -msgid "" -"This section decribes only important directives. They are groonga-httpd " -"specific directives and performance related directives." -msgstr "" -"This section decribes only important directives. They are groonga-httpd " -"specific directives and performance related directives." - -msgid "" -"The following directives can be used in the groonga-httpd configuration " -"file. By default, it's located at /etc/groonga/httpd/groonga-httpd.conf." -msgstr "" -"The following directives can be used in the groonga-httpd configuration " -"file. By default, it's located at /etc/groonga/httpd/groonga-httpd.conf." - -msgid "Groonga-httpd specific directives" -msgstr "Groonga-httpd specific directives" - -msgid "" -"The following directives aren't provided by nginx. They are provided by " -"groonga-httpd to configure groonga-httpd specific configurations." -msgstr "" -"The following directives aren't provided by nginx. They are provided by " -"groonga-httpd to configure groonga-httpd specific configurations." - -msgid "``groonga``" -msgstr "``groonga``" - -msgid "Synopsis::" -msgstr "Synopsis::" - -msgid "Default" -msgstr "Default" - -msgid "``groonga off;``" -msgstr "``groonga off;``" - -msgid "Context" -msgstr "Context" - -msgid "``location``" -msgstr "``location``" - -msgid "" -"Specifies whether Groonga is enabled in the ``location`` block. The default " -"is ``off``. You need to specify ``on`` to enable groonga." -msgstr "" -"Specifies whether Groonga is enabled in the ``location`` block. The default " -"is ``off``. You need to specify ``on`` to enable groonga." - -msgid "Examples::" -msgstr "Examples::" - -msgid "``groonga_database``" -msgstr "``groonga_database``" - -msgid "``groonga_database /usr/local/var/lib/groonga/db/db;``" -msgstr "``groonga_database /usr/local/var/lib/groonga/db/db;``" - -msgid "``http``, ``server``, ``location``" -msgstr "``http``, ``server``, ``location``" - -msgid "" -"Specifies the path to a Groonga database. This is the required directive." -msgstr "" -"Specifies the path to a Groonga database. This is the required directive." - -msgid "``groonga_database_auto_create``" -msgstr "``groonga_database_auto_create``" - -msgid "``groonga_database_auto_create on;``" -msgstr "``groonga_database_auto_create on;``" - -msgid "" -"Specifies whether Groonga database is created automatically or not. If the " -"value is ``on`` and the Groonga database specified by :ref:`groonga-" -"database` doesn't exist, the Groonga database is created automatically. If " -"the Groonga database exists, groonga-httpd does nothing." -msgstr "" -"Specifies whether Groonga database is created automatically or not. If the " -"value is ``on`` and the Groonga database specified by :ref:`groonga-" -"database` doesn't exist, the Groonga database is created automatically. If " -"the Groonga database exists, groonga-httpd does nothing." - -msgid "" -"If parent directory doesn't exist, parent directory is also created " -"recursively." -msgstr "" -"If parent directory doesn't exist, parent directory is also created " -"recursively." - -msgid "" -"The default value is ``on``. Normally, the value doesn't need to be changed." -msgstr "" -"The default value is ``on``. Normally, the value doesn't need to be changed." - -msgid "``groonga_base_path``" -msgstr "``groonga_base_path``" - -msgid "The same value as ``location`` name." -msgstr "The same value as ``location`` name." - -msgid "" -"Specifies the base path in URI. Groonga uses ``/d/command?" -"parameter1=value1&...`` path to run ``command``. The form of path in used in " -"groonga-httpd but groonga-httpd also supports ``/other-prefix/command?" -"parameter1=value1&...`` form. To support the form, groonga-httpd removes the " -"base path from the head of request URI and prepend ``/d/`` to the processed " -"request URI. By the path conversion, users can use custom path prefix and " -"Groonga can always uses ``/d/command?parameter1=value1&...`` form." -msgstr "" -"Specifies the base path in URI. Groonga uses ``/d/command?" -"parameter1=value1&...`` path to run ``command``. The form of path in used in " -"groonga-httpd but groonga-httpd also supports ``/other-prefix/command?" -"parameter1=value1&...`` form. To support the form, groonga-httpd removes the " -"base path from the head of request URI and prepend ``/d/`` to the processed " -"request URI. By the path conversion, users can use custom path prefix and " -"Groonga can always uses ``/d/command?parameter1=value1&...`` form." - -msgid "" -"Nomally, this directive isn't needed. It is needed for per command " -"configuration." -msgstr "" -"Nomally, this directive isn't needed. It is needed for per command " -"configuration." - -msgid "" -"Here is an example configuration to add authorization to :doc:`/reference/" -"commands/shutdown` command::" -msgstr "" -"Here is an example configuration to add authorization to :doc:`/reference/" -"commands/shutdown` command::" - -msgid "``groonga_log_path``" -msgstr "``groonga_log_path``" - -msgid "``/var/log/groonga/httpd/groonga.log``" -msgstr "``/var/log/groonga/httpd/groonga.log``" - -msgid "" -"Specifies Groonga log path in the ``http``, ``server`` or ``location`` " -"block. The default is ``/var/log/groonga/httpd/groonga.log``. You can " -"disable logging to specify ``off``." -msgstr "" -"Specifies Groonga log path in the ``http``, ``server`` or ``location`` " -"block. The default is ``/var/log/groonga/httpd/groonga.log``. You can " -"disable logging to specify ``off``." - -msgid "``groonga_log_level``" -msgstr "``groonga_log_level``" - -msgid "``notice``" -msgstr "``notice``" - -msgid "" -"Specifies Groonga log level in the ``http``, ``server`` or ``location`` " -"block. The default is ``notice``. You can disable logging by specifying " -"``none`` as log level." -msgstr "" -"Specifies Groonga log level in the ``http``, ``server`` or ``location`` " -"block. The default is ``notice``. You can disable logging by specifying " -"``none`` as log level." - -msgid "``groonga_query_log_path``" -msgstr "``groonga_query_log_path``" - -msgid "``/var/log/groonga/httpd/groonga-query.log``" -msgstr "``/var/log/groonga/httpd/groonga-query.log``" - -msgid "" -"Specifies Groonga's query log path in the ``http``, ``server`` or " -"``location`` block. The default is ``/var/log/groonga/httpd/groonga-query." -"log``. You can disable logging to specify ``off``." -msgstr "" -"Specifies Groonga's query log path in the ``http``, ``server`` or " -"``location`` block. The default is ``/var/log/groonga/httpd/groonga-query." -"log``. You can disable logging to specify ``off``." - -msgid "Query log is useful for the following cases:" -msgstr "Query log is useful for the following cases:" - -msgid "Detecting slow query." -msgstr "Detecting slow query." - -msgid "Debugging." -msgstr "Debugging." - -msgid "" -"You can analyze your query log by `groonga-query-log package <https://github." -"com/groonga/groonga-query-log>`_. The package provides useful tools." -msgstr "" -"You can analyze your query log by `groonga-query-log package <https://github." -"com/groonga/groonga-query-log>`_. The package provides useful tools." - -msgid "" -"For example, there is a tool that analyzing your query log. It can detect " -"slow queries from your query log. There is a tool that replaying same " -"queries in your query log. It can test the new Groonga before updating " -"production environment." -msgstr "" -"For example, there is a tool that analyzing your query log. It can detect " -"slow queries from your query log. There is a tool that replaying same " -"queries in your query log. It can test the new Groonga before updating " -"production environment." - -msgid "Performance related directives" -msgstr "Performance related directives" - -msgid "" -"The following directives are related to the performance of groonga-httpd." -msgstr "" -"The following directives are related to the performance of groonga-httpd." - -msgid "``worker_processes``" -msgstr "``worker_processes``" - -msgid "" -"For optimum performance, set this to be equal to the number of CPUs or " -"cores. In many cases, Groonga queries may be CPU-intensive work, so to fully " -"utilize multi-CPU/core systems, it's essential to set this accordingly." -msgstr "" -"For optimum performance, set this to be equal to the number of CPUs or " -"cores. In many cases, Groonga queries may be CPU-intensive work, so to fully " -"utilize multi-CPU/core systems, it's essential to set this accordingly." - -msgid "" -"This isn't a groonga-httpd specific directive, but an nginx's one. For " -"details, see http://wiki.nginx.org/CoreModule#worker_processes." -msgstr "" -"This isn't a groonga-httpd specific directive, but an nginx's one. For " -"details, see http://wiki.nginx.org/CoreModule#worker_processes." - -msgid "By default, this is set to 1. It is nginx's default." -msgstr "By default, this is set to 1. It is nginx's default." - -msgid "``groonga_cache_limit``" -msgstr "``groonga_cache_limit``" - -msgid "" -"This directive is introduced to customize cache limit for each worker " -"process." -msgstr "" -"This directive is introduced to customize cache limit for each worker " -"process." - -msgid "100" -msgstr "100" - -msgid "" -"Specifies Groonga's limit of query cache in the ``http``, ``server`` or " -"``location`` block. The default value is 100. You can disable query cache to " -"specify 0 to ``groonga_cache_limit`` explicitly." -msgstr "" -"Specifies Groonga's limit of query cache in the ``http``, ``server`` or " -"``location`` block. The default value is 100. You can disable query cache to " -"specify 0 to ``groonga_cache_limit`` explicitly." - -msgid "``proxy_cache``" -msgstr "``proxy_cache``" - -msgid "" -"In short, you can use nginx's reverse proxy and cache mechanism instead of " -"Groonga's built-in query cache feature." -msgstr "" -"In short, you can use nginx's reverse proxy and cache mechanism instead of " -"Groonga's built-in query cache feature." - -msgid "Query cache" -msgstr "Query cache" - -msgid "" -"Groonga has query cache feature for :doc:`/reference/commands/select` " -"command. The feature improves performance in many cases." -msgstr "" -"Groonga has query cache feature for :doc:`/reference/commands/select` " -"command. The feature improves performance in many cases." - -msgid "" -"Query cache feature works well on groonga-httpd except you use :doc:`/" -"reference/commands/cache_limit` command on 2 or more workers. Normally, :doc:" -"`/reference/commands/cache_limit` command isn't used. So there is no problem " -"on many cases." -msgstr "" -"Query cache feature works well on groonga-httpd except you use :doc:`/" -"reference/commands/cache_limit` command on 2 or more workers. Normally, :doc:" -"`/reference/commands/cache_limit` command isn't used. So there is no problem " -"on many cases." - -msgid "" -"Here is a description about a problem of using :doc:`/reference/commands/" -"cache_limit` command on 2 or more workers." -msgstr "" -"Here is a description about a problem of using :doc:`/reference/commands/" -"cache_limit` command on 2 or more workers." - -msgid "" -"Groonga's query cache is available in the same process. It means that " -"workers can't share the cache. If you don't change cache size, it isn't a " -"big problem. If you want to change cache size by :doc:`/reference/commands/" -"cache_limit` command, there is a problem." -msgstr "" -"Groonga's query cache is available in the same process. It means that " -"workers can't share the cache. If you don't change cache size, it isn't a " -"big problem. If you want to change cache size by :doc:`/reference/commands/" -"cache_limit` command, there is a problem." - -msgid "There is no portable ways to change cache size for all workers." -msgstr "There is no portable ways to change cache size for all workers." - -msgid "For example, there are 3 workers::" -msgstr "For example, there are 3 workers::" - -msgid "" -"The client requests :doc:`/reference/commands/cache_limit` command and the " -"worker 1 receives it::" -msgstr "" -"The client requests :doc:`/reference/commands/cache_limit` command and the " -"worker 1 receives it::" - -msgid "" -"The client requests :doc:`/reference/commands/cache_limit` command again and " -"the worker 1 receives it again::" -msgstr "" -"The client requests :doc:`/reference/commands/cache_limit` command again and " -"the worker 1 receives it again::" - -msgid "" -"In this case, the worker 2 and the worker 3 aren't received any requests. So " -"they don't change cache size." -msgstr "" -"In this case, the worker 2 and the worker 3 aren't received any requests. So " -"they don't change cache size." - -msgid "" -"You can't choose a worker. So you can't change cache sizes of all workers " -"by :doc:`/reference/commands/cache_limit` command." -msgstr "" -"You can't choose a worker. So you can't change cache sizes of all workers " -"by :doc:`/reference/commands/cache_limit` command." - -msgid "Reverse proxy and cache" -msgstr "Reverse proxy and cache" - -msgid "You can use nginx's reverse proxy and cache feature for query cache::" -msgstr "You can use nginx's reverse proxy and cache feature for query cache::" - -msgid "" -"You can use the same cache configuration for all workers but you can't " -"change cache configuration dynamically by HTTP." -msgstr "" -"You can use the same cache configuration for all workers but you can't " -"change cache configuration dynamically by HTTP." - -msgid "Here is a sample configuration::" -msgstr "Here is a sample configuration::" - -msgid "See the following nginx documentations for parameter details:" -msgstr "See the following nginx documentations for parameter details:" - -msgid "" -"http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache_path" -msgstr "" -"http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache_path" - -msgid "" -"http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache_valid" -msgstr "" -"http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache_valid" - -msgid "http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache" -msgstr "http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache" - -msgid "http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_pass" -msgstr "http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_pass" - -msgid "" -"Note that you need to remove cache files created by nginx by hand after you " -"load new data to Groonga. For the above sample configuration, run the " -"following command to remove cache files::" -msgstr "" -"Note that you need to remove cache files created by nginx by hand after you " -"load new data to Groonga. For the above sample configuration, run the " -"following command to remove cache files::" - -msgid "" -"If you use Groonga's query cache feature, you don't need to expire cache by " -"hand. It is done automatically." -msgstr "" -"If you use Groonga's query cache feature, you don't need to expire cache by " -"hand. It is done automatically." - -msgid "Available nginx modules" -msgstr "Available nginx modules" - -msgid "" -"All standard HTTP modules are available. HttpRewriteModule is disabled when " -"you don't have PCRE (Perl Compatible Regular Expressions). For the list of " -"standard HTTP modules, see http://wiki.nginx.org/Modules." -msgstr "" -"All standard HTTP modules are available. HttpRewriteModule is disabled when " -"you don't have PCRE (Perl Compatible Regular Expressions). For the list of " -"standard HTTP modules, see http://wiki.nginx.org/Modules." - -msgid "groonga HTTPサーバー" -msgstr "groonga HTTPサーバー" - -msgid "" -"groongaサーバを起動する時に--protocolオプションにhttpを指定すると、httpで通信" -"可能になります。また、--document-root によって静的ページのパスを指定すると、" -"httpリクエストに指定されたURIに対応する、パス配下に置かれたファイルを出力しま" -"す。" -msgstr "" -"groongaサーバを起動する時に--protocolオプションにhttpを指定すると、httpで通信" -"可能になります。また、--document-root によって静的ページのパスを指定すると、" -"httpリクエストに指定されたURIに対応する、パス配下に置かれたファイルを出力しま" -"す。" - -msgid "" -"groongaにはHTML + JavaScriptで実装された管理ツールが標準で付属しています。--" -"document-rootを指定しない場合は管理ツールがインストールされているパスが指定さ" -"れたとみなされますので、ウェブブラウザでhttp://hostname:port/にアクセスする" -"と、管理ツールを利用できます。" -msgstr "" -"groongaにはHTML + JavaScriptで実装された管理ツールが標準で付属しています。--" -"document-rootを指定しない場合は管理ツールがインストールされているパスが指定さ" -"れたとみなされますので、ウェブブラウザでhttp://hostname:port/にアクセスする" -"と、管理ツールを利用できます。" - -msgid "コマンド" -msgstr "コマンド" - -msgid "" -"httpを指定して起動したgroongaサーバに対しても、他のモードで起動したgroongaと" -"同じコマンドが使用できます。" -msgstr "" -"httpを指定して起動したgroongaサーバに対しても、他のモードで起動したgroongaと" -"同じコマンドが使用できます。" - -msgid "" -"コマンドは、複数の引数をとります。引数にはそれぞれ名前があります。また、特殊" -"な引数である「output_type」と「command_version」があります。" -msgstr "" -"コマンドは、複数の引数をとります。引数にはそれぞれ名前があります。また、特殊" -"な引数である「output_type」と「command_version」があります。" - -msgid "" -"スタンドアロンやクライアントモードでは、コマンドは以下のような形式で指定しま" -"す。" -msgstr "" -"スタンドアロンやクライアントモードでは、コマンドは以下のような形式で指定しま" -"す。" - -msgid "形式1: コマンド名 値1 値2,.." -msgstr "形式1: コマンド名 値1 値2,.." - -msgid "形式2: コマンド名 --引数名1 値1 --引数名2 値2,.." -msgstr "形式2: コマンド名 --引数名1 値1 --引数名2 値2,.." - -msgid "" -"形式1と形式2は混在させることができます。これらの形式では、output_typeという引" -"数名を用いてoutput_typeを指定します。" -msgstr "" -"形式1と形式2は混在させることができます。これらの形式では、output_typeという引" -"数名を用いてoutput_typeを指定します。" - -msgid "" -"httpでgroongaサーバと通信する際には、以下のような形式でコマンドを指定しま" -"す。::" -msgstr "" -"httpでgroongaサーバと通信する際には、以下のような形式でコマンドを指定しま" -"す。::" - -msgid "ただし、コマンド名、引数名、値はURLエンコードが必要です。" -msgstr "ただし、コマンド名、引数名、値はURLエンコードが必要です。" - -msgid "GETメソッドのみが使用可能です。" -msgstr "GETメソッドのみが使用可能です。" - -msgid "output_typeにはjson, tsv, xmlが指定可能です。" -msgstr "output_typeにはjson, tsv, xmlが指定可能です。" - -msgid "" -"command_versionはコマンドの仕様の互換性を指定します。詳細は :doc:`/reference/" -"command/command_version` を参照してください。" -msgstr "" -"command_versionはコマンドの仕様の互換性を指定します。詳細は :doc:`/reference/" -"command/command_version` を参照してください。" - -msgid "output_typeの指定に従って、コマンドの実行結果を出力します。" -msgstr "output_typeの指定に従って、コマンドの実行結果を出力します。" - -msgid "groonga-suggest-create-dataset" -msgstr "groonga-suggest-create-dataset" - -msgid "NAME" -msgstr "NAME" - -msgid "" -"groonga-suggest-create-dataset - Defines schema for a suggestion dataset" -msgstr "" -"groonga-suggest-create-dataset - Defines schema for a suggestion dataset" - -msgid "SYNOPSTIS" -msgstr "SYNOPSTIS" - -msgid "DESCTIPION" -msgstr "DESCTIPION" - -msgid "" -"groonga-suggest-create-dataset creates a dataset for :doc:`/reference/" -"suggest`. A database has many datasets. This command just defines schema for " -"a suggestion dataset." -msgstr "" -"groonga-suggest-create-dataset creates a dataset for :doc:`/reference/" -"suggest`. A database has many datasets. This command just defines schema for " -"a suggestion dataset." - -msgid "" -"This command generates some tables and columns for :doc:`/reference/suggest`." -msgstr "" -"This command generates some tables and columns for :doc:`/reference/suggest`." - -msgid "" -"Here is the list of such tables. If you specify 'query' as dataset name, " -"following '_DATASET' suffix are replaced. Thus, 'item_query', 'pair_query', " -"'sequence_query', 'event_query' tables are generated." -msgstr "" -"Here is the list of such tables. If you specify 'query' as dataset name, " -"following '_DATASET' suffix are replaced. Thus, 'item_query', 'pair_query', " -"'sequence_query', 'event_query' tables are generated." - -msgid "event_type" -msgstr "event_type" - -msgid "bigram" -msgstr "bigram" - -msgid "kana" -msgstr "kana" - -msgid "item_DATASET" -msgstr "item_DATASET" - -msgid "pair_DATASET" -msgstr "pair_DATASET" - -msgid "sequence_DATASET" -msgstr "sequence_DATASET" - -msgid "event_DATASET" -msgstr "event_DATASET" - -msgid "configuration" -msgstr "configuration" - -msgid "OPTIONS" -msgstr "OPTIONS" - -msgid "None." -msgstr "None." - -msgid "EXIT STATUS" -msgstr "EXIT STATUS" - -msgid "FILES" -msgstr "FILES" - -msgid "EXAMPLE" -msgstr "EXAMPLE" - -msgid "SEE ALSO" -msgstr "SEE ALSO" - -msgid "" -":doc:`/reference/suggest` :doc:`groonga-suggest-httpd` :doc:`groonga-suggest-" -"learner`" -msgstr "" -":doc:`/reference/suggest` :doc:`groonga-suggest-httpd` :doc:`groonga-suggest-" -"learner`" - -msgid "groonga-suggest-httpd" -msgstr "groonga-suggest-httpd" - -msgid "" -"groonga-suggest-httpd is a program to provide interface which accepts HTTP " -"request and returns suggestion dataset, then saves logs for learning. " -"groonga-suggest-httpd behaves similar in point of view of suggestion " -"functionality, but the name of parameter is different." -msgstr "" -"groonga-suggest-httpd is a program to provide interface which accepts HTTP " -"request and returns suggestion dataset, then saves logs for learning. " -"groonga-suggest-httpd behaves similar in point of view of suggestion " -"functionality, but the name of parameter is different." - -msgid "First you need to set up database for suggestion." -msgstr "First you need to set up database for suggestion." - -msgid "Launch groonga-suggest-httpd" -msgstr "Launch groonga-suggest-httpd" - -msgid "Execute groonga-suggest-httpd command:" -msgstr "Execute groonga-suggest-httpd command:" - -msgid "" -"After executing above command, groonga-suggest-httpd accepts HTTP request on " -"8080 port." -msgstr "" -"After executing above command, groonga-suggest-httpd accepts HTTP request on " -"8080 port." - -msgid "If you just want to save requests into log file, use ``-l`` option." -msgstr "If you just want to save requests into log file, use ``-l`` option." - -msgid "" -"Here is the example to save log files under ``logs`` directory with ``log`` " -"prefix for each file.::" -msgstr "" -"Here is the example to save log files under ``logs`` directory with ``log`` " -"prefix for each file.::" - -msgid "" -"Under ``logs`` directory, log files such as ``logYYYYmmddHHMMSS-00`` are " -"created." -msgstr "" -"Under ``logs`` directory, log files such as ``logYYYYmmddHHMMSS-00`` are " -"created." - -msgid "Request to groonga-suggest-httpd" -msgstr "Request to groonga-suggest-httpd" - -msgid "" -"Here is the sample requests to learn ``groonga`` for ``query`` dataset::" -msgstr "" -"Here is the sample requests to learn ``groonga`` for ``query`` dataset::" - -msgid "Options" -msgstr "Options" - -msgid "Specify http server port number. The default value is 8080." -msgstr "Specify http server port number. The default value is 8080." - -msgid "" -"Specify number of threads. The default value is 8. This option accepts 128 " -"as the max value, but use the number of CPU cores for performance." -msgstr "" -"Specify number of threads. The default value is 8. This option accepts 128 " -"as the max value, but use the number of CPU cores for performance." - -msgid "Specify endpoint for sender." -msgstr "Specify endpoint for sender." - -msgid "Specify endpoint for receiver." -msgstr "Specify endpoint for receiver." - -msgid "Specify path prefix of log." -msgstr "Specify path prefix of log." - -msgid "" -"Specify the number of lines in a log file. The default value is 1,000,000." -msgstr "" -"Specify the number of lines in a log file. The default value is 1,000,000." - -msgid "Specify this option to daemonize." -msgstr "Specify this option to daemonize." - -msgid "Specify this option to disable checking max fd on start." -msgstr "Specify this option to disable checking max fd on start." - -msgid "Command line parameters" -msgstr "Command line parameters" - -msgid "There is one required parameter - ``database_path``." -msgstr "There is one required parameter - ``database_path``." - -msgid "``database_path``" -msgstr "``database_path``" - -msgid "" -"Specifies the path to a Groonga database. This database must be created by :" -"doc:`groonga-suggest-create-dataset` command because it executes required " -"initialization for suggestion." -msgstr "" -"Specifies the path to a Groonga database. This database must be created by :" -"doc:`groonga-suggest-create-dataset` command because it executes required " -"initialization for suggestion." - -msgid "GET parameters" -msgstr "GET parameters" - -msgid "groonga-suggest-httpd accepts following GET parameters." -msgstr "groonga-suggest-httpd accepts following GET parameters." - -msgid "There are required parameters which depends on type of query." -msgstr "There are required parameters which depends on type of query." - -msgid "Key" -msgstr "Key" - -msgid "Note" -msgstr "Note" - -msgid "q" -msgstr "q" - -msgid "UTF-8 encoded string which user fills in form" -msgstr "UTF-8 encoded string which user fills in form" - -msgid "t" -msgstr "t" - -msgid "" -"The type of query. The value of type must be complete, correct, suggest or " -"submit. It also accepts multiple type of query which is concatinated by ``|" -"``. Note that ``submit`` is invalid value when you specify multiple type of " -"query." -msgstr "" -"The type of query. The value of type must be complete, correct, suggest or " -"submit. It also accepts multiple type of query which is concatinated by ``|" -"``. Note that ``submit`` is invalid value when you specify multiple type of " -"query." - -msgid "Required parameters for learning" -msgstr "Required parameters for learning" - -msgid "s" -msgstr "s" - -msgid "Elapsed time from 0:00 January 1, 1970" -msgstr "Elapsed time from 0:00 January 1, 1970" - -msgid "Note that you need specify the value of ``s`` in milliseconds" -msgstr "Note that you need specify the value of ``s`` in milliseconds" - -msgid "i" -msgstr "i" - -msgid "Unique ID to distinct user" -msgstr "Unique ID to distinct user" - -msgid "Use session ID or IP address for example" -msgstr "Use session ID or IP address for example" - -msgid "l" -msgstr "l" - -msgid "" -"Specify the name of dataset for learning. It also accepts multiple dataset " -"name which is concatinated by ``|``" -msgstr "" -"Specify the name of dataset for learning. It also accepts multiple dataset " -"name which is concatinated by ``|``" - -msgid "" -"Note that dataset name must be matched to following regular expression ``[A-" -"Za-z ][A-Za-z0-9 ]{0,15}``" -msgstr "" -"Note that dataset name must be matched to following regular expression ``[A-" -"Za-z ][A-Za-z0-9 ]{0,15}``" - -msgid "Required parameters for suggestion" -msgstr "Required parameters for suggestion" - -msgid "n" -msgstr "n" - -msgid "Specify the name of dataset for suggestion" -msgstr "Specify the name of dataset for suggestion" - -msgid "This dataset name is used to calculate suggestion results" -msgstr "This dataset name is used to calculate suggestion results" - -msgid "Optional parameter" -msgstr "Optional parameter" - -msgid "callback" -msgstr "callback" - -msgid "Specify the name of function if you prefer JSONP as response format" -msgstr "Specify the name of function if you prefer JSONP as response format" - -msgid "" -"The name of function must be matched to reqular expression ``[A-Za-z ][A-Za-" -"z0-9 ]{0,15}``" -msgstr "" -"The name of function must be matched to reqular expression ``[A-Za-z ][A-Za-" -"z0-9 ]{0,15}``" - -msgid "" -"``groonga-suggest-httpd`` command returns following response in JSON or " -"JSONP format." -msgstr "" -"``groonga-suggest-httpd`` command returns following response in JSON or " -"JSONP format." - -msgid "In JSON format::" -msgstr "In JSON format::" - -msgid "In JSONP format::" -msgstr "In JSONP format::" - -msgid "One of ``complete``, ``correct`` and ``suggest``." -msgstr "One of ``complete``, ``correct`` and ``suggest``." - -msgid "``CANDIDATE_N``" -msgstr "``CANDIDATE_N``" - -msgid "The string of candidate (UTF-8)." -msgstr "The string of candidate (UTF-8)." - -msgid "``SCORE_N``" -msgstr "``SCORE_N``" - -msgid "The score." -msgstr "The score." - -msgid "groonga-suggest-learner" -msgstr "groonga-suggest-learner" - -msgid "" -"groonga-suggest-learner is a program to learn suggest result from data which " -"derived from groonga-suggest-httpd. Usually, it is used with groonga-suggest-" -"httpd, but It is allowed to launch standalone. In such a case, groonga-" -"suggest-learner loads data from log directory." -msgstr "" -"groonga-suggest-learner is a program to learn suggest result from data which " -"derived from groonga-suggest-httpd. Usually, it is used with groonga-suggest-" -"httpd, but It is allowed to launch standalone. In such a case, groonga-" -"suggest-learner loads data from log directory." - -msgid "" -"groonga-suggest-leaner supports the two way of learning data. One is " -"learning data from groonga-suggest-httpd, the other is learning data from " -"already existing log files." -msgstr "" -"groonga-suggest-leaner supports the two way of learning data. One is " -"learning data from groonga-suggest-httpd, the other is learning data from " -"already existing log files." - -msgid "Learning data from groonga-suggest-httpd" -msgstr "Learning data from groonga-suggest-httpd" - -msgid "Execute groonga-suggest-learner.::" -msgstr "Execute groonga-suggest-learner.::" - -msgid "Learning data from log files" -msgstr "Learning data from log files" - -msgid "Execute groonga-suggest-learner with ``-l`` option." -msgstr "Execute groonga-suggest-learner with ``-l`` option." - -msgid "Here is the sample to load log data under ``logs`` directory::" -msgstr "Here is the sample to load log data under ``logs`` directory::" - -msgid "Uses ``<endpoint>`` as the receiver endpoint." -msgstr "" - -msgid "Uses ``<endpoint>`` as the sender endpoint." -msgstr "" - -msgid "Runs as a daemon." -msgstr "" - -msgid "Reads logs from ``<directory>``." -msgstr "" - -msgid "Outputs log to ``<path>``." -msgstr "" - -msgid "" -"Uses ``<level>`` for log level. ``<level>`` must be between 1 and 9. Larger " -"level outputs more logs." -msgstr "" - -msgid "Specifies the path to a groonga database." -msgstr "Specifies the path to a groonga database." - -msgid "Related tables" -msgstr "Related tables" - -msgid "" -"Here is the list of table which learned data is stored. If you specify " -"``query`` as dataset name, following ``_DATASET`` suffix are replaced. Thus, " -"``event_query`` table is used." -msgstr "" -"Here is the list of table which learned data is stored. If you specify " -"``query`` as dataset name, following ``_DATASET`` suffix are replaced. Thus, " -"``event_query`` table is used." - -msgid "groonga command" -msgstr "groonga command" - -msgid "groonga - 列指向データベース機能を持つ全文検索エンジンソフトウェア" -msgstr "groonga - 列指向データベース機能を持つ全文検索エンジンソフトウェア" - -msgid "" -"Groongaは列指向のデータベース機能を持つ高速でスケーラブルな全文検索エンジンで" -"す。 Groongaのデータベースは、groongaコマンドかCライブラリインタフェースを通" -"して操作することができます。このマニュアルページでは、groongaコマンドの使い方" -"について説明します。" -msgstr "" -"Groongaは列指向のデータベース機能を持つ高速でスケーラブルな全文検索エンジンで" -"す。 Groongaのデータベースは、groongaコマンドかCライブラリインタフェースを通" -"して操作することができます。このマニュアルページでは、groongaコマンドの使い方" -"について説明します。" - -msgid "新たなデータベースを作成します。" -msgstr "新たなデータベースを作成します。" - -msgid "クライアントモードで実行します。" -msgstr "クライアントモードで実行します。" - -msgid "サーバモードで実行します。" -msgstr "サーバモードで実行します。" - -msgid "デーモンモードで実行します。(forkする点がサーバモードと異なる)" -msgstr "デーモンモードで実行します。(forkする点がサーバモードと異なる)" - -msgid "" -"データベースで使用する文字エンコーディング方式を指定します。新たなデータベー" -"スを作成する時のみ有効です。none, euc, utf8, sjis, latin, koi8rのいずれかが指" -"定できます。" -msgstr "" -"データベースで使用する文字エンコーディング方式を指定します。新たなデータベー" -"スを作成する時のみ有効です。none, euc, utf8, sjis, latin, koi8rのいずれかが指" -"定できます。" - -msgid "" -"ログレベルを指定します。0〜8までの数値が指定可能で、数が大きいほど多くのログ" -"が出力されます。" -msgstr "" -"ログレベルを指定します。0〜8までの数値が指定可能で、数が大きいほど多くのログ" -"が出力されます。" - -msgid "Use :option:`--bind-address` instead." -msgstr "Use :option:`--bind-address` instead." - -msgid "" -"サーバモードかデーモンモードで実行するとき、listenするアドレスを指定します。" -"(デフォルトは `hostname` の返すホスト名)" -msgstr "" -"サーバモードかデーモンモードで実行するとき、listenするアドレスを指定します。" -"(デフォルトは `hostname` の返すホスト名)" - -msgid "" -"クライアント、サーバ、またはデーモンモードで使用するTCPポート番号。 (クライア" -"ントモードのデフォルトは10043番、サーバ、またはデーモンモードのデフォルトは、" -"HTTPの場合、10041番、GQTPの場合、10043番)" -msgstr "" - -msgid "" -"サーバモードかデーモンモードで実行するとき、サーバのIDとなるアドレスを指定し" -"ます。(デフォルトは`hostname`の返すホスト名)" -msgstr "" -"サーバモードかデーモンモードで実行するとき、サーバのIDとなるアドレスを指定し" -"ます。(デフォルトは`hostname`の返すホスト名)" - -msgid "ヘルプメッセージを出力します。" -msgstr "ヘルプメッセージを出力します。" - -msgid "" -"httpサーバとしてgroongaを使用する場合に静的ページを格納するディレクトリを指定" -"します。" -msgstr "" -"httpサーバとしてgroongaを使用する場合に静的ページを格納するディレクトリを指定" -"します。" - -msgid "" -"デフォルトでは、データベースを管理するための汎用的なページに対応するファイル" -"が/usr/share/groonga/admin_html以下にインストールされます。このディレクトリを" -"document-rootオプションの値に指定して起動した場合、ウェブブラウザでhttp://" -"hostname:port/index.htmlにアクセスすると、ウェブベースのデータベース管理ツー" -"ルを使用できます。" -msgstr "" -"デフォルトでは、データベースを管理するための汎用的なページに対応するファイル" -"が/usr/share/groonga/admin_html以下にインストールされます。このディレクトリを" -"document-rootオプションの値に指定して起動した場合、ウェブブラウザでhttp://" -"hostname:port/index.htmlにアクセスすると、ウェブベースのデータベース管理ツー" -"ルを使用できます。" - -msgid "http,gqtpのいずれかを指定します。(デフォルトはgqtp)" -msgstr "http,gqtpのいずれかを指定します。(デフォルトはgqtp)" - -msgid "" -"ログを出力するファイルのパスを指定します。(デフォルトは/var/log/groonga/" -"groonga.logです)" -msgstr "" -"ログを出力するファイルのパスを指定します。(デフォルトは/var/log/groonga/" -"groonga.logです)" - -msgid "" -"クエリーログを出力するファイルのパスを指定します。(デフォルトでは出力されませ" -"ん)" -msgstr "" -"クエリーログを出力するファイルのパスを指定します。(デフォルトでは出力されませ" -"ん)" - -msgid "" -"最大で利用するスレッド数を指定します。(デフォルトはマシンのCPUコア数と同じ数" -"です)" -msgstr "" -"最大で利用するスレッド数を指定します。(デフォルトはマシンのCPUコア数と同じ数" -"です)" - -msgid "PIDを保存するパスを指定します。(デフォルトでは保存しません)" -msgstr "PIDを保存するパスを指定します。(デフォルトでは保存しません)" - -msgid "" -"設定ファイルのパスを指定します。設定ファイルは以下のようなフォーマットになり" -"ます。::" -msgstr "" -"設定ファイルのパスを指定します。設定ファイルは以下のようなフォーマットになり" -"ます。::" - -msgid "キャッシュ数の最大値を指定します。(デフォルトは100です)" -msgstr "キャッシュ数の最大値を指定します。(デフォルトは100です)" - -msgid "検索の挙動をエスカレーションする閾値を指定します。(デフォルトは0です)" -msgstr "検索の挙動をエスカレーションする閾値を指定します。(デフォルトは0です)" - -msgid "使用するデータベースのパス名を指定します。" -msgstr "使用するデータベースのパス名を指定します。" - -msgid "" -"クライアントモードの場合は接続先のホスト名とポート番号を指定します(デフォルト" -"値は'localhost:10043')。ポート番号を指定しない場合には、10043が指定されたもの" -"とします。" -msgstr "" - -msgid "" -"スタンドアロンおよびクライアントモードの場合は、実行するコマンドとその引数を" -"コマンドライン引数に指定できます。コマンドライン引数にcommandを与えなかった場" -"合は、標準入力から一行ずつEOFに達するまでコマンド文字列を読み取り、順次実行し" -"ます。" -msgstr "" -"スタンドアロンおよびクライアントモードの場合は、実行するコマンドとその引数を" -"コマンドライン引数に指定できます。コマンドライン引数にcommandを与えなかった場" -"合は、標準入力から一行ずつEOFに達するまでコマンド文字列を読み取り、順次実行し" -"ます。" - -msgid "" -"groongaコマンドを通してデータベースを操作する命令をコマンドと呼びます。コマン" -"ドは主にC言語で記述され、groongaプロセスにロードすることによって使用できるよ" -"うになります。 それぞれのコマンドは一意な名前と、0個以上の引数を持ちます。" -msgstr "" -"groongaコマンドを通してデータベースを操作する命令をコマンドと呼びます。コマン" -"ドは主にC言語で記述され、groongaプロセスにロードすることによって使用できるよ" -"うになります。 それぞれのコマンドは一意な名前と、0個以上の引数を持ちます。" - -msgid "引数は以下の2種類の方法のいずれかで指定することができます。::" -msgstr "引数は以下の2種類の方法のいずれかで指定することができます。::" - -msgid "" -"形式1でコマンドを実行する場合は、定義された順番で値を指定しなければならず、途" -"中の引数の値を省略することはできません。形式2でコマンドを実行する場合は、「--" -"引数名」のように引数の名前を明示しなければならない代わりに、任意の順番で引数" -"を指定することが可能で、途中の引数の指定を省略することもできます。" -msgstr "" -"形式1でコマンドを実行する場合は、定義された順番で値を指定しなければならず、途" -"中の引数の値を省略することはできません。形式2でコマンドを実行する場合は、「--" -"引数名」のように引数の名前を明示しなければならない代わりに、任意の順番で引数" -"を指定することが可能で、途中の引数の指定を省略することもできます。" - -msgid "" -"標準入力からコマンド文字列を与える場合は、コマンド名と引数名と値は、空白( )で" -"区切ります。空白や、記号「\"'()\\」のうちいずれかを含む値を指定したい場合は、" -"シングルクォート(')かダブルクォート(\")で値を囲みます。値として指定する文字列" -"の中では、改行文字は'\\n'に置き換えて指定します。また、引用符に使用した文字を" -"値の中で指定する場合には、その文字の前にバックスラッシュ('\\') を指定します。" -"バックスラッシュ文字自身を値として指定する場合には、その前にバックスラッシュ" -"を指定します。" -msgstr "" -"標準入力からコマンド文字列を与える場合は、コマンド名と引数名と値は、空白( )で" -"区切ります。空白や、記号「\"'()\\」のうちいずれかを含む値を指定したい場合は、" -"シングルクォート(')かダブルクォート(\")で値を囲みます。値として指定する文字列" -"の中では、改行文字は'\\n'に置き換えて指定します。また、引用符に使用した文字を" -"値の中で指定する場合には、その文字の前にバックスラッシュ('\\') を指定します。" -"バックスラッシュ文字自身を値として指定する場合には、その前にバックスラッシュ" -"を指定します。" - -msgid "" -"You can write command list with continuous line which is represented by '\\" -"\\' character.::" -msgstr "" -"You can write command list with continuous line which is represented by '\\" -"\\' character.::" - -msgid "組み込みコマンド" -msgstr "組み込みコマンド" - -msgid "以下のコマンドは組み込みコマンドとして予め定義されています。" -msgstr "以下のコマンドは組み込みコマンドとして予め定義されています。" - -msgid "groongaプロセスの状態を表示します。" -msgstr "groongaプロセスの状態を表示します。" - -msgid "DBに定義されているテーブルのリストを表示します。" -msgstr "DBに定義されているテーブルのリストを表示します。" - -msgid "テーブルに定義されているカラムのリストを表示します。" -msgstr "テーブルに定義されているカラムのリストを表示します。" - -msgid "DBにテーブルを追加します。" -msgstr "DBにテーブルを追加します。" - -msgid "テーブルにカラムを追加します。" -msgstr "テーブルにカラムを追加します。" - -msgid "DBに定義されているテーブルを削除します。" -msgstr "DBに定義されているテーブルを削除します。" - -msgid "テーブルに定義されているカラムを削除します。" -msgstr "テーブルに定義されているカラムを削除します。" - -msgid "テーブルにレコードを挿入します。" -msgstr "テーブルにレコードを挿入します。" - -msgid "テーブルに含まれるレコードを検索して表示します。" -msgstr "テーブルに含まれるレコードを検索して表示します。" - -msgid "検索条件をカスタマイズした新たな検索コマンドを定義します。" -msgstr "検索条件をカスタマイズした新たな検索コマンドを定義します。" - -msgid "データベースとのセッションを終了します。" -msgstr "データベースとのセッションを終了します。" - -msgid "サーバ(デーモン)プロセスを停止します。" -msgstr "サーバ(デーモン)プロセスを停止します。" - -msgid "ログ出力レベルを設定します。" -msgstr "ログ出力レベルを設定します。" - -msgid "ログ出力を行います。" -msgstr "ログ出力を行います。" - -msgid "ロックを解除します。" -msgstr "ロックを解除します。" - -msgid "例" -msgstr "例" - -msgid "新しいデータベースを作成します。::" -msgstr "新しいデータベースを作成します。::" - -msgid "作成済みのデータベースにテーブルを定義します。::" -msgstr "作成済みのデータベースにテーブルを定義します。::" - -msgid "サーバを起動します。::" -msgstr "サーバを起動します。::" - -msgid "httpサーバとして起動します。::" -msgstr "httpサーバとして起動します。::" - -msgid "サーバに接続し、テーブル一覧を表示します。::" -msgstr "サーバに接続し、テーブル一覧を表示します。::" - -msgid "Function" -msgstr "Function" - -msgid "" -"Function can be used in some commands. For example, you can use function in " -"``--filter``, ``--scorer`` and ``output_columns`` options of :doc:`commands/" -"select`." -msgstr "" -"Function can be used in some commands. For example, you can use function in " -"``--filter``, ``--scorer`` and ``output_columns`` options of :doc:`commands/" -"select`." - -msgid "This section describes about function and built-in functions." -msgstr "This section describes about function and built-in functions." - -msgid "TODO: Add documentations about function." -msgstr "TODO: Add documentations about function." - -msgid "between" -msgstr "between" - -msgid "" -"``between`` is used for checking the specified value exists in the specific " -"range. It is often used for combination with :ref:`select-filter` option in :" -"doc:`/reference/commands/select`." -msgstr "" -"``between`` is used for checking the specified value exists in the specific " -"range. It is often used for combination with :ref:`select-filter` option in :" -"doc:`/reference/commands/select`." - -msgid "``between`` has five parameters::" -msgstr "``between`` has five parameters::" - -msgid "Here are a schema definition and sample data to show usage.::" -msgstr "Here are a schema definition and sample data to show usage.::" - -msgid "Here is the query to show the persons to match PG-13 rating (MPAA)." -msgstr "Here is the query to show the persons to match PG-13 rating (MPAA)." - -msgid "It returns 13, 14, 15 and 16 years old users." -msgstr "It returns 13, 14, 15 and 16 years old users." - -msgid "" -"``between`` function accepts not only a column of table, but also the value." -msgstr "" -"``between`` function accepts not only a column of table, but also the value." - -msgid "" -"If you specify the value as 1st parameter, it is checked whether the value " -"is included or not. if it matches to the specified range, it returns the all " -"records because ``between`` function returns true." -msgstr "" -"If you specify the value as 1st parameter, it is checked whether the value " -"is included or not. if it matches to the specified range, it returns the all " -"records because ``between`` function returns true." - -msgid "" -"If it doesn't match to the specified range, it returns no records because " -"``between`` function returns false." -msgstr "" -"If it doesn't match to the specified range, it returns no records because " -"``between`` function returns false." - -msgid "" -"In the above case, it returns all the records, because 14 exists in between " -"13 and 16. This behavior is used for checking the specified value exists or " -"not in the table." -msgstr "" -"In the above case, it returns all the records, because 14 exists in between " -"13 and 16. This behavior is used for checking the specified value exists or " -"not in the table." - -msgid "" -"There are five required parameters, ``column_or_value``, and ``min``, " -"``min_border``, ``max`` and ``max_border``." -msgstr "" -"There are five required parameters, ``column_or_value``, and ``min``, " -"``min_border``, ``max`` and ``max_border``." - -msgid "``column_or_value``" -msgstr "``column_or_value``" - -msgid "It specifies a column of the table or the value." -msgstr "It specifies a column of the table or the value." - -msgid "``min``" -msgstr "``min``" - -msgid "" -"It specifies the minimal border value of the range. You can control the " -"behavior that the value of ``max`` is included or excluded by ``max_border`` " -"parameter." -msgstr "" -"It specifies the minimal border value of the range. You can control the " -"behavior that the value of ``max`` is included or excluded by ``max_border`` " -"parameter." - -msgid "``min_border``" -msgstr "``min_border``" - -msgid "" -"It specifies whether the specified range contains the value of ``min`` or " -"not. The value of ``min_border`` are either \"include\" or \"exclude\". If " -"it is \"include\", ``min`` value is included. If it is \"exclude\", ``min`` " -"value is not included." -msgstr "" -"It specifies whether the specified range contains the value of ``min`` or " -"not. The value of ``min_border`` are either \"include\" or \"exclude\". If " -"it is \"include\", ``min`` value is included. If it is \"exclude\", ``min`` " -"value is not included." - -msgid "" -"It specifies the maximum border value of the range. You can control the " -"behavior that the value of ``max`` is included or excluded by ``max_border`` " -"parameter." -msgstr "" -"It specifies the maximum border value of the range. You can control the " -"behavior that the value of ``max`` is included or excluded by ``max_border`` " -"parameter." - -msgid "``max_border``" -msgstr "``max_border``" - -msgid "" -"It specifies whether the specified range contains the value of ``max`` or " -"not. The value of ``max_border`` are either \"include\" or \"exclude\". If " -"it is \"include\", ``max`` value is included. If it is \"exclude\", ``max`` " -"value is not included." -msgstr "" -"It specifies whether the specified range contains the value of ``max`` or " -"not. The value of ``max_border`` are either \"include\" or \"exclude\". If " -"it is \"include\", ``max`` value is included. If it is \"exclude\", ``max`` " -"value is not included." - -msgid "" -"``between`` returns whether the value of column exists in specified the " -"value of range or not. If record is matched to specified the value of range, " -"it returns true. Otherwise, it returns false." -msgstr "" -"``between`` returns whether the value of column exists in specified the " -"value of range or not. If record is matched to specified the value of range, " -"it returns true. Otherwise, it returns false." - -msgid "edit_distance" -msgstr "edit_distance" - -msgid "edit_distance - 指定した2つの文字列の編集距離を計算する" -msgstr "edit_distance - 指定した2つの文字列の編集距離を計算する" - -msgid "" -"Groonga組込関数の一つであるedit_distanceについて説明します。組込関数は、" -"script形式のgrn_expr中で呼び出すことができます。" -msgstr "" -"Groonga組込関数の一つであるedit_distanceについて説明します。組込関数は、" -"script形式のgrn_expr中で呼び出すことができます。" - -msgid "" -"edit_distance() 関数は、string1に指定した文字列とstring2に指定した文字列の間" -"の編集距離を求めます。" -msgstr "" -"edit_distance() 関数は、string1に指定した文字列とstring2に指定した文字列の間" -"の編集距離を求めます。" - -msgid "``string1``" -msgstr "``string1``" - -msgid "文字列を指定します" -msgstr "文字列を指定します" - -msgid "``string2``" -msgstr "``string2``" - -msgid "もうひとつの文字列を指定します" -msgstr "もうひとつの文字列を指定します" - -msgid "指定した2つ文字列の編集距離をUint32型の値として返します。" -msgstr "指定した2つ文字列の編集距離をUint32型の値として返します。" - -msgid "geo_distance" -msgstr "geo_distance" - -msgid "" -"``geo_distance`` calculates the value of distance between specified two " -"points." -msgstr "" -"``geo_distance`` calculates the value of distance between specified two " -"points." - -msgid "" -"``geo_distance`` requires two point. The parameter ``approximate_type`` is " -"optional::" -msgstr "" -"``geo_distance`` requires two point. The parameter ``approximate_type`` is " -"optional::" - -msgid "" -"The default value of ``approximate_type`` is ``\"rectangle\"``. If you omit " -"``approximate_type``, ``geo_distance`` calculates the value of distance as " -"if ``\"rectangle\"`` was specified." -msgstr "" -"The default value of ``approximate_type`` is ``\"rectangle\"``. If you omit " -"``approximate_type``, ``geo_distance`` calculates the value of distance as " -"if ``\"rectangle\"`` was specified." - -msgid "``geo_distance`` is one of the Groonga builtin functions." -msgstr "``geo_distance`` is one of the Groonga builtin functions." - -msgid "You can call a builtin function in :doc:`/reference/grn_expr`" -msgstr "You can call a builtin function in :doc:`/reference/grn_expr`" - -msgid "" -"``geo_distance`` function calculates the value of distance (approximate " -"value) between the coordinate of ``point1`` and the coordinate of ``point2``." -msgstr "" -"``geo_distance`` function calculates the value of distance (approximate " -"value) between the coordinate of ``point1`` and the coordinate of ``point2``." - -msgid "" -"Groonga provides three built in functions for calculating the value of " -"distance. There are ``geo_distance()``, ``geo_distance2()`` and " -"``geo_distance3()``. The difference of them is the algorithm of calculating " -"distance. ``geo_distance2()`` and ``geo_distance3()`` were deprecated since " -"version 1.2.9. Use ``geo_distance(point1, point2, \"sphere\")`` instead of " -"``geo_distance2(point1, point2)``. Use ``geo_distance(point1, point2, " -"\"ellipsoid\")`` instead of ``geo_distance3(point1, point2)``." -msgstr "" -"Groonga provides three built in functions for calculating the value of " -"distance. There are ``geo_distance()``, ``geo_distance2()`` and " -"``geo_distance3()``. The difference of them is the algorithm of calculating " -"distance. ``geo_distance2()`` and ``geo_distance3()`` were deprecated since " -"version 1.2.9. Use ``geo_distance(point1, point2, \"sphere\")`` instead of " -"``geo_distance2(point1, point2)``. Use ``geo_distance(point1, point2, " -"\"ellipsoid\")`` instead of ``geo_distance3(point1, point2)``." - -msgid "" -"Lets's learn about ``geo_distance`` usage with examples. This section shows " -"simple usages." -msgstr "" -"Lets's learn about ``geo_distance`` usage with examples. This section shows " -"simple usages." - -msgid "" -"Here are two schema definition and sample data to show the difference " -"according to the usage. Those samples show how to calculate the value of " -"distance between New York City and London." -msgstr "" -"Here are two schema definition and sample data to show the difference " -"according to the usage. Those samples show how to calculate the value of " -"distance between New York City and London." - -msgid "" -"Using the column value of location for calculating the distance (``Cities`` " -"table)" -msgstr "" -"Using the column value of location for calculating the distance (``Cities`` " -"table)" - -msgid "" -"Using the explicitly specified coordinates for calculating the distance " -"(``Geo`` table)" -msgstr "" -"Using the explicitly specified coordinates for calculating the distance " -"(``Geo`` table)" - -msgid "Using the column value of location" -msgstr "Using the column value of location" - -msgid "" -"Here are a schema definition of ``Cities`` table and sample data to show " -"usage." -msgstr "" -"Here are a schema definition of ``Cities`` table and sample data to show " -"usage." - -msgid "" -"This execution example creates a table named ``Cities`` which has one column " -"named ``location``. ``location`` column stores the value of coordinate. The " -"coordinate of Tokyo is stored as sample data." -msgstr "" -"This execution example creates a table named ``Cities`` which has one column " -"named ``location``. ``location`` column stores the value of coordinate. The " -"coordinate of Tokyo is stored as sample data." - -msgid "" -"This sample shows that ``geo_distance`` use the value of ``location`` column " -"and the value of coordinate to calculate distance." -msgstr "" -"This sample shows that ``geo_distance`` use the value of ``location`` column " -"and the value of coordinate to calculate distance." - -msgid "" -"The value (\"185428000x-461000\") passed to ``geo_distance`` as the second " -"argument is the coordinate of London." -msgstr "" -"The value (\"185428000x-461000\") passed to ``geo_distance`` as the second " -"argument is the coordinate of London." - -msgid "Using the explicitly specified value of location" -msgstr "Using the explicitly specified value of location" - -msgid "" -"Here are a schema definition of ``Geo`` table and sample data to show usage." -msgstr "" -"Here are a schema definition of ``Geo`` table and sample data to show usage." - -msgid "" -"This execution example creates a table named ``Geo`` which has one column " -"named ``distance``. ``distance`` column stores the value of distance." -msgstr "" -"This execution example creates a table named ``Geo`` which has one column " -"named ``distance``. ``distance`` column stores the value of distance." - -msgid "" -"This sample shows that ``geo_distance`` use the coordinate of London and the " -"coordinate of New York to calculate distance." -msgstr "" -"This sample shows that ``geo_distance`` use the coordinate of London and the " -"coordinate of New York to calculate distance." - -msgid "There are two required parameter, ``point1`` and ``point2``." -msgstr "There are two required parameter, ``point1`` and ``point2``." - -msgid "``point1``" -msgstr "``point1``" - -msgid "" -"It specifies the start point that you want to calculate the value of " -"distance between two points." -msgstr "" -"It specifies the start point that you want to calculate the value of " -"distance between two points." - -msgid "You can specify the value of GeoPoint type. [#]_" -msgstr "You can specify the value of GeoPoint type. [#]_" - -msgid "See :doc:`/reference/types` about GeoPoint." -msgstr "See :doc:`/reference/types` about GeoPoint." - -msgid "``point2``" -msgstr "``point2``" - -msgid "" -"It specifies the end point that you want to calculate the value of distance " -"between two points." -msgstr "" -"It specifies the end point that you want to calculate the value of distance " -"between two points." - -msgid "" -"You can specify the value of GeoPoint type or the string indicating the " -"coordinate." -msgstr "" -"You can specify the value of GeoPoint type or the string indicating the " -"coordinate." - -msgid "See :doc:`/reference/types` about GeoPoint and the coordinate." -msgstr "See :doc:`/reference/types` about GeoPoint and the coordinate." - -msgid "There is a optional parameter, ``approximate_type``." -msgstr "There is a optional parameter, ``approximate_type``." - -msgid "``approximate_type``" -msgstr "``approximate_type``" - -msgid "" -"It specifies how to approximate the geographical features for calculating " -"the value of distance." -msgstr "" -"It specifies how to approximate the geographical features for calculating " -"the value of distance." - -msgid "" -"You can specify the value of ``approximate_type`` by one of the followings." -msgstr "" -"You can specify the value of ``approximate_type`` by one of the followings." - -msgid "``rectangle``" -msgstr "``rectangle``" - -msgid "``sphere``" -msgstr "``sphere``" - -msgid "``ellipsoid``" -msgstr "``ellipsoid``" - -msgid "" -"There is a limitation about ``geo_distance``. ``geo_distance`` can not " -"calculate the value of distance between two points across meridian, equator " -"or the date line if you use ``sphere`` or ``ellipsoid`` as approximate type. " -"There is not such a limitation for ``rectangle``. This is temporary " -"limitation according to the implementation of Groonga, but it will be fixed " -"in the future release." -msgstr "" -"There is a limitation about ``geo_distance``. ``geo_distance`` can not " -"calculate the value of distance between two points across meridian, equator " -"or the date line if you use ``sphere`` or ``ellipsoid`` as approximate type. " -"There is not such a limitation for ``rectangle``. This is temporary " -"limitation according to the implementation of Groonga, but it will be fixed " -"in the future release." - -msgid "" -"This parameter require to approximate the geographical features by square " -"approximation for calculating the distance." -msgstr "" -"This parameter require to approximate the geographical features by square " -"approximation for calculating the distance." - -msgid "" -"Since the value of distance is calculated by simple formula, you can " -"calculate the value of distance fast. But, the error of distance increases " -"as it approaches the pole." -msgstr "" -"Since the value of distance is calculated by simple formula, you can " -"calculate the value of distance fast. But, the error of distance increases " -"as it approaches the pole." - -msgid "You can also specify ``rect`` as abbrev expression." -msgstr "You can also specify ``rect`` as abbrev expression." - -msgid "" -"Here is a sample about calculating the value of distance with column value." -msgstr "" -"Here is a sample about calculating the value of distance with column value." - -msgid "" -"Here is a sample about calculating the value of distance with explicitly " -"specified point." -msgstr "" -"Here is a sample about calculating the value of distance with explicitly " -"specified point." - -msgid "" -"Here are samples about calculating the value of distance with explicitly " -"specified point across meridian, equator, the date line." -msgstr "" -"Here are samples about calculating the value of distance with explicitly " -"specified point across meridian, equator, the date line." - -msgid "" -"This sample shows the value of distance across meridian. The return value of " -"``geo_distance(\"175904000x8464000\", \"145508000x-13291000\", \"rectangle" -"\")`` is the value of distance from Paris, Flance to Madrid, Spain." -msgstr "" -"This sample shows the value of distance across meridian. The return value of " -"``geo_distance(\"175904000x8464000\", \"145508000x-13291000\", \"rectangle" -"\")`` is the value of distance from Paris, Flance to Madrid, Spain." - -msgid "" -"This sample shows the value of distance across equator. The return value of " -"``geo_distance(\"146566000x-266422000\", \"-56880000x-172310000\", " -"\"rectangle\")`` is the value of distance from New York, The United Status " -"to Brasillia, Brasil." -msgstr "" -"This sample shows the value of distance across equator. The return value of " -"``geo_distance(\"146566000x-266422000\", \"-56880000x-172310000\", " -"\"rectangle\")`` is the value of distance from New York, The United Status " -"to Brasillia, Brasil." - -msgid "" -"This sample shows the value of distance across the date line. The return " -"value of ``geo_distance(\"143660000x419009000\", \"135960000x-440760000\", " -"\"rectangle\")`` is the value of distance from Beijin, China to San " -"Francisco, The United States." -msgstr "" -"This sample shows the value of distance across the date line. The return " -"value of ``geo_distance(\"143660000x419009000\", \"135960000x-440760000\", " -"\"rectangle\")`` is the value of distance from Beijin, China to San " -"Francisco, The United States." - -msgid "" -"``geo_distance`` uses square approximation as default. If you omit " -"``approximate_type``, ``geo_distance`` behaves like ``rectangle`` was " -"specified." -msgstr "" -"``geo_distance`` uses square approximation as default. If you omit " -"``approximate_type``, ``geo_distance`` behaves like ``rectangle`` was " -"specified." - -msgid "" -"``geo_distance`` accepts the string indicating the coordinate as the value " -"of ``point1`` when the value of ``approximate_type`` is ``\"rectangle\"``. " -"If you specified the string indicating the coordinate as the value of " -"``point1`` with ``sphere`` or ``ellipsoid``, ``geo_distance`` returns 0 as " -"the value of distance." -msgstr "" -"``geo_distance`` accepts the string indicating the coordinate as the value " -"of ``point1`` when the value of ``approximate_type`` is ``\"rectangle\"``. " -"If you specified the string indicating the coordinate as the value of " -"``point1`` with ``sphere`` or ``ellipsoid``, ``geo_distance`` returns 0 as " -"the value of distance." - -msgid "" -"This parameter require to approximate the geographical features by spherical " -"approximation for calculating the distance." -msgstr "" -"This parameter require to approximate the geographical features by spherical " -"approximation for calculating the distance." - -msgid "" -"It is slower than ``rectangle``, but the error of distance becomes smaller " -"than ``rectangle``." -msgstr "" -"It is slower than ``rectangle``, but the error of distance becomes smaller " -"than ``rectangle``." - -msgid "You can also specify ``sphr`` as abbrev expression." -msgstr "You can also specify ``sphr`` as abbrev expression." - -msgid "" -"This parameter require to approximate the geographical features by ellipsoid " -"approximation for calculating the distance." -msgstr "" -"This parameter require to approximate the geographical features by ellipsoid " -"approximation for calculating the distance." - -msgid "" -"It uses the calculation of distance by the formula of Hubeny. It is slower " -"than ``sphere``, but the error of distance becomes smaller than ``sphere``." -msgstr "" -"It uses the calculation of distance by the formula of Hubeny. It is slower " -"than ``sphere``, but the error of distance becomes smaller than ``sphere``." - -msgid "You can also specify ``ellip`` as abbrev expression." -msgstr "You can also specify ``ellip`` as abbrev expression." - -msgid "" -"``geo_distance`` returns the value of distance in float type. The unit of " -"return value is meter." -msgstr "" -"``geo_distance`` returns the value of distance in float type. The unit of " -"return value is meter." - -msgid "Footnote" -msgstr "Footnote" - -msgid "You can specify whether TokyoGeoPoint or WGS84GeoPoint." -msgstr "You can specify whether TokyoGeoPoint or WGS84GeoPoint." - -msgid "geo_in_circle" -msgstr "geo_in_circle" - -msgid "geo_in_circle - 座標が円の範囲内に存在するかどうかを調べます。" -msgstr "geo_in_circle - 座標が円の範囲内に存在するかどうかを調べます。" - -msgid "" -"Groonga組込関数の一つであるgeo_in_circleについて説明します。組込関数は、" -"script形式のgrn_expr中で呼び出すことができます。" -msgstr "" -"Groonga組込関数の一つであるgeo_in_circleについて説明します。組込関数は、" -"script形式のgrn_expr中で呼び出すことができます。" - -msgid "" -"geo_in_circle() 関数は、pointに指定した座標が、centerに指定した座標を中心とす" -"る円の範囲内にあるかどうかを調べます。" -msgstr "" -"geo_in_circle() 関数は、pointに指定した座標が、centerに指定した座標を中心とす" -"る円の範囲内にあるかどうかを調べます。" - -msgid "``point``" -msgstr "``point``" - -msgid "" -"円の範囲内に存在するかどうかを調べる座標を指定します。Point型の値を指定できま" -"す。 [#]_" -msgstr "" -"円の範囲内に存在するかどうかを調べる座標を指定します。Point型の値を指定できま" -"す。 [#]_" - -msgid "``center``" -msgstr "``center``" - -msgid "" -"円の中心となる座標を指定します。Point型の値、あるいは座標を示す文字列を指定で" -"きます。" -msgstr "" -"円の中心となる座標を指定します。Point型の値、あるいは座標を示す文字列を指定で" -"きます。" - -msgid "``radious_or_point``" -msgstr "``radious_or_point``" - -msgid "" -"円の半径を指定します。数値を指定した場合には、半径(単位:メートル)が指定された" -"ものとみなします。 Point型の値、あるいは座標を示す文字列を指定した場合は、円" -"周上の点の一つの座標が指定されたものとみなします。" -msgstr "" -"円の半径を指定します。数値を指定した場合には、半径(単位:メートル)が指定された" -"ものとみなします。 Point型の値、あるいは座標を示す文字列を指定した場合は、円" -"周上の点の一つの座標が指定されたものとみなします。" - -msgid "" -"半径からの距離を求めるために地形をどのように近似するかを指定します。指定でき" -"る値は以下の通りです。" -msgstr "" -"半径からの距離を求めるために地形をどのように近似するかを指定します。指定でき" -"る値は以下の通りです。" - -msgid "``\"rectangle\"``" -msgstr "``\"rectangle\"``" - -msgid "" -"方形近似で近似します。単純な計算式で距離を求めることができるため高速ですが、" -"極付近では誤差が大きくなります。" -msgstr "" -"方形近似で近似します。単純な計算式で距離を求めることができるため高速ですが、" -"極付近では誤差が大きくなります。" - -msgid "``\"rect\"`` と省略して指定することもできます。" -msgstr "``\"rect\"`` と省略して指定することもできます。" - -msgid "" -"この近似方法がデフォルト値です。 ``approximate_type`` を省略した場合は方形近" -"似になります。" -msgstr "" -"この近似方法がデフォルト値です。 ``approximate_type`` を省略した場合は方形近" -"似になります。" - -msgid "``\"sphere\"``" -msgstr "``\"sphere\"``" - -msgid "" -"球面近似で近似します。 ``\"rectangle\"`` よりも遅くなりますが、誤差は小さいで" -"す。" -msgstr "" -"球面近似で近似します。 ``\"rectangle\"`` よりも遅くなりますが、誤差は小さいで" -"す。" - -msgid "``\"sphr\"`` と省略して指定することもできます。" -msgstr "``\"sphr\"`` と省略して指定することもできます。" - -msgid "``\"ellipsoid\"``" -msgstr "``\"ellipsoid\"``" - -msgid "" -"楕円体近似で近似します。距離の計算にはヒュベニの距離計算式を用います。 ``" -"\"sphere\"`` よりも遅くなりますが、誤差は小さくなります。" -msgstr "" -"楕円体近似で近似します。距離の計算にはヒュベニの距離計算式を用います。 ``" -"\"sphere\"`` よりも遅くなりますが、誤差は小さくなります。" - -msgid "``\"ellip\"`` と省略して指定することもできます。" -msgstr "``\"ellip\"`` と省略して指定することもできます。" - -msgid "pointに指定した座標が円の範囲内にあるかどうかをBool型の値で返します。" -msgstr "pointに指定した座標が円の範囲内にあるかどうかをBool型の値で返します。" - -msgid "" -"TokyoGeoPoint(日本測地系座標)かWGS84GeoPoint(世界測地系座標)のいずれかを指定" -"できます。" -msgstr "" -"TokyoGeoPoint(日本測地系座標)かWGS84GeoPoint(世界測地系座標)のいずれかを指定" -"できます。" - -msgid "geo_in_rectangle" -msgstr "geo_in_rectangle" - -msgid "geo_in_rectangle - 座標が矩形の範囲内に存在するかどうかを調べます。" -msgstr "geo_in_rectangle - 座標が矩形の範囲内に存在するかどうかを調べます。" - -msgid "" -"Groonga組込関数の一つであるgeo_in_rectangleについて説明します。組込関数は、" -"script形式のgrn_expr中で呼び出すことができます。" -msgstr "" -"Groonga組込関数の一つであるgeo_in_rectangleについて説明します。組込関数は、" -"script形式のgrn_expr中で呼び出すことができます。" - -msgid "" -"geo_in_rectangle() 関数は、pointに指定した座標が、top_leftとbottom_rightがな" -"す矩形の範囲内にあるかどうかを調べます。" -msgstr "" -"geo_in_rectangle() 関数は、pointに指定した座標が、top_leftとbottom_rightがな" -"す矩形の範囲内にあるかどうかを調べます。" - -msgid "" -"矩形の範囲内に存在するかどうかを調べる座標を指定します。Point型の値を指定でき" -"ます。 [#]_" -msgstr "" -"矩形の範囲内に存在するかどうかを調べる座標を指定します。Point型の値を指定でき" -"ます。 [#]_" - -msgid "``top_left``" -msgstr "``top_left``" - -msgid "" -"矩形の左上隅となる座標を指定します。Point型の値、あるいは座標を示す文字列を指" -"定できます。" -msgstr "" -"矩形の左上隅となる座標を指定します。Point型の値、あるいは座標を示す文字列を指" -"定できます。" - -msgid "``bottom_right``" -msgstr "``bottom_right``" - -msgid "" -"矩形の右下隅となる座標を指定します。Point型の値、あるいは座標を示す文字列を指" -"定できます。" -msgstr "" -"矩形の右下隅となる座標を指定します。Point型の値、あるいは座標を示す文字列を指" -"定できます。" - -msgid "pointに指定した座標が矩形の範囲内にあるかどうかをBool型の値で返します。" -msgstr "" -"pointに指定した座標が矩形の範囲内にあるかどうかをBool型の値で返します。" - -msgid "highlight_full" -msgstr "" - -msgid "This feature is experimental. API will be changed." -msgstr "This feature is experimental. API will be changed." - -msgid "" -"``highlight_full`` tags target text. It can use to highlight the search " -"keyword. It can specify use/not use HTML escape, the normalizer name and " -"change the tag for each keyword." -msgstr "" -"``highlight_full`` tags target text. It can use to highlight the search " -"keyword. It can specify use/not use HTML escape, the normalizer name and " -"change the tag for each keyword." - -msgid "``highlight_full`` has required parameter and optional parameter::" -msgstr "``highlight_full`` has required parameter and optional parameter::" - -msgid "" -"``highlight_full`` can be used in only ``--output_columns`` in :doc:`/" -"reference/commands/select`." -msgstr "" -"``highlight_full`` can be used in only ``--output_columns`` in :doc:`/" -"reference/commands/select`." - -msgid "``highlight_full`` requires Groonga 4.0.5 or later." -msgstr "``highlight_full`` requires Groonga 4.0.5 or later." - -msgid "" -"``highlight_full`` requires :doc:`/reference/command/command_version` 2 or " -"later." -msgstr "" -"``highlight_full`` requires :doc:`/reference/command/command_version` 2 or " -"later." - -msgid "" -"The following example uses HTML escape and normalzier is ``NormalizeAuto``. " -"It specifies the tags ``<span class=\"keyword1\">`` and ``</span>`` of the " -"keyword ``groonga``, and the tags ``<span class=\"keyword2\">`` and ``</" -"span>`` of the keyword ``mysql``." -msgstr "" -"The following example uses HTML escape and normalzier is ``NormalizeAuto``. " -"It specifies the tags ``<span class=\"keyword1\">`` and ``</span>`` of the " -"keyword ``groonga``, and the tags ``<span class=\"keyword2\">`` and ``</" -"span>`` of the keyword ``mysql``." - -msgid "" -"The text are scanned by the keywords for tagging after they are normalized " -"by ``NormalizerAuto`` normalizer." -msgstr "" -"The text are scanned by the keywords for tagging after they are normalized " -"by ``NormalizerAuto`` normalizer." - -msgid "" -"``--query \"groonga mysql\"`` matches to the first record's body. " -"``highight_full`` surrounds the keywords ``groonga`` contained in the text " -"with ``<span class=\"keyword1\">`` and ``</span>``, and the keywords " -"``mysql`` contained in the text with with ``<span class=\"keyword2\">`` and " -"``</span>``." -msgstr "" -"``--query \"groonga mysql\"`` matches to the first record's body. " -"``highight_full`` surrounds the keywords ``groonga`` contained in the text " -"with ``<span class=\"keyword1\">`` and ``</span>``, and the keywords " -"``mysql`` contained in the text with with ``<span class=\"keyword2\">`` and " -"``</span>``." - -msgid "" -"Special characters such as ``<`` and ``>`` are escapsed as ``<`` and " -"``>``." -msgstr "" -"Special characters such as ``<`` and ``>`` are escapsed as ``<`` and " -"``>``." - -msgid "You can specify string literal instead of column." -msgstr "You can specify string literal instead of column." - -msgid "" -"There are three required parameters, ``column``, ``normalizer_name`` and " -"``use_html_escape``. There are three or over optional parameters, " -"``keywordN``, ``open_tagN`` and ``end_tagN``." -msgstr "" -"There are three required parameters, ``column``, ``normalizer_name`` and " -"``use_html_escape``. There are three or over optional parameters, " -"``keywordN``, ``open_tagN`` and ``end_tagN``." - -msgid "It specifies a column of the table." -msgstr "It specifies a column of the table." - -msgid "``normalizer_name``" -msgstr "" - -msgid "It specifies a normalizer name." -msgstr "It specifies a normalizer name." - -msgid "``use_html_escape``" -msgstr "" - -msgid "" -"It specifies use or not use HTML escape. If it is ``true`` , use HTML " -"escape. If it is ``false`` , not use HTML escape." -msgstr "" -"It specifies use or not use HTML escape. If it is ``true`` , use HTML " -"escape. If it is ``false`` , not use HTML escape." - -msgid "``keywordN``" -msgstr "" - -msgid "" -"It specifies a keyword for tagging. You can specify multiple keywords for " -"each three arguments." -msgstr "" -"It specifies a keyword for tagging. You can specify multiple keywords for " -"each three arguments." - -msgid "``open_tagN``" -msgstr "" - -msgid "" -"It specifies a open tag. You can specify multiple open tags for each three " -"arguments." -msgstr "" -"It specifies a open tag. You can specify multiple open tags for each three " -"arguments." - -msgid "``close_tagN``" -msgstr "" - -msgid "" -"It specifies a close tag. You can specify multiple close tags for each three " -"arguments." -msgstr "" -"It specifies a close tag. You can specify multiple close tags for each three " -"arguments." - -msgid "" -"``highlight_full`` returns a tagged string or ``null``. If " -"``highlight_full`` can't find any keywords, it returns ``null``." -msgstr "" -"``highlight_full`` returns a tagged string or ``null``. If " -"``highlight_full`` can't find any keywords, it returns ``null``." - -msgid ":doc:`/reference/functions/highlight_html`" -msgstr "" - -msgid "highlight_html" -msgstr "" - -msgid "" -"``highlight_html`` tags target text. It can use to highlight the search " -"keywords. The tagged text are prepared for embedding HTML. Special " -"characters such as ``<`` and ``>`` are escapsed as ``<`` and ``>``. " -"Keyword is surrounded with ``<span class=\"keyword\">`` and ``</span>``. For " -"example, a tagged text of ``I am a groonga user. <3`` for keyword " -"``groonga`` is ``I am a <span class=\"keyword\">groonga</span> user. <3``." -msgstr "" -"``highlight_html`` tags target text. It can use to highlight the search " -"keywords. The tagged text are prepared for embedding HTML. Special " -"characters such as ``<`` and ``>`` are escapsed as ``<`` and ``>``. " -"Keyword is surrounded with ``<span class=\"keyword\">`` and ``</span>``. For " -"example, a tagged text of ``I am a groonga user. <3`` for keyword " -"``groonga`` is ``I am a <span class=\"keyword\">groonga</span> user. <3``." - -msgid "``highlight_html`` has only one parameter::" -msgstr "``highlight_html`` has only one parameter::" - -msgid "" -"``highlight_html`` can be used in only ``--output_columns`` in :doc:`/" -"reference/commands/select`." -msgstr "" -"``highlight_html`` can be used in only ``--output_columns`` in :doc:`/" -"reference/commands/select`." - -msgid "``highlight_html`` requires Groonga 4.0.5 or later." -msgstr "``highlight_html`` requires Groonga 4.0.5 or later." - -msgid "" -"``highlight_html`` requires :doc:`/reference/command/command_version` 2 or " -"later." -msgstr "" -"``highlight_html`` requires :doc:`/reference/command/command_version` 2 or " -"later." - -msgid "" -"You also need to specify ``--query`` and/or ``--filter``. Keywords are " -"extracted from ``--query`` and ``--filter`` arguments." -msgstr "" -"You also need to specify ``--query`` and/or ``--filter``. Keywords are " -"extracted from ``--query`` and ``--filter`` arguments." - -msgid "" -"The following example uses ``--query \"groonga mysql\"``. In this case, " -"``groonga`` and ``mysql`` are used as keywords." -msgstr "" -"The following example uses ``--query \"groonga mysql\"``. In this case, " -"``groonga`` and ``mysql`` are used as keywords." - -msgid "" -"``--query \"groonga mysql\"`` matches to only the first record's body. " -"``highlight_html(body)`` surrounds the keywords ``groonga`` or ``mysql`` " -"contained in the text with ``<span class=\"keyword\">`` and ``</span>``." -msgstr "" -"``--query \"groonga mysql\"`` matches to only the first record's body. " -"``highlight_html(body)`` surrounds the keywords ``groonga`` or ``mysql`` " -"contained in the text with ``<span class=\"keyword\">`` and ``</span>``." - -msgid "There is only one parameter ``column`` ." -msgstr "" - -msgid "" -"``highlight_html`` returns a tagged string or ``null``. If " -"``highlight_html`` can't find any keywords, it returns ``null``." -msgstr "" -"``highlight_html`` returns a tagged string or ``null``. If " -"``highlight_html`` can't find any keywords, it returns ``null``." - -msgid ":doc:`/reference/functions/highlight_full`" -msgstr "" - -msgid "html_untag" -msgstr "html_untag" - -msgid "``html_untag`` strips HTML tags from HTML and outputs plain text." -msgstr "``html_untag`` strips HTML tags from HTML and outputs plain text." - -msgid "" -"``html_untag`` is used in ``--output_columns`` described at :ref:`select-" -"output-columns`." -msgstr "" - -msgid "``html_untag`` requires only one argument. It is ``html``." -msgstr "``html_untag`` requires only one argument. It is ``html``." - -msgid "Requirements" -msgstr "Requirements" - -msgid "``html_untag`` requires Groonga 3.0.5 or later." -msgstr "``html_untag`` requires Groonga 3.0.5 or later." - -msgid "" -"``html_untag`` requires :doc:`/reference/command/command_version` 2 or later." -msgstr "" -"``html_untag`` requires :doc:`/reference/command/command_version` 2 or later." - -msgid "Sample schema:" -msgstr "Sample schema:" - -msgid "Sample data:" -msgstr "Sample data:" - -msgid "" -"Here is the simple usage of ``html_untag`` function which strips HTML tags " -"from content of column." -msgstr "" -"Here is the simple usage of ``html_untag`` function which strips HTML tags " -"from content of column." - -msgid "" -"When executing the above query, you can see \"span\" tag with \"class\" " -"attribute is stripped. Note that you must specify ``--command_version 2`` to " -"use ``html_untag`` function." -msgstr "" -"When executing the above query, you can see \"span\" tag with \"class\" " -"attribute is stripped. Note that you must specify ``--command_version 2`` to " -"use ``html_untag`` function." - -msgid "There is one required parameter, ``html``." -msgstr "There is one required parameter, ``html``." - -msgid "``html``" -msgstr "``html``" - -msgid "It specifies HTML text to be untagged." -msgstr "It specifies HTML text to be untagged." - -msgid "" -"``html_untag`` returns plain text which is stripped HTML tags from HTML text." -msgstr "" -"``html_untag`` returns plain text which is stripped HTML tags from HTML text." - -msgid "in_values" -msgstr "" - -# febf9cd9a0e1442996c96e55b1b01bec -msgid "``in_values`` function is added since Groonga 4.0.7." -msgstr "" - -# 96c88bb561244790bab603a67b330349 -msgid "" -"``in_values`` enables you to simplify the query which uses multiple ``OR`` " -"or ``==``. It is recommended to use this function in point of view about " -"performance improvements in such a case." -msgstr "" - -msgid "" -"``query`` requires two or more arguments - ``target_value`` and multiple " -"``value``." -msgstr "" - -msgid "Here is a schema definition and sample data." -msgstr "" - -# 2e685560f66a4b10b5d739dadfce351d -msgid "" -"Here is the simple usage of ``in_values`` function which selects the records " -"- the value of ``tag`` column is \"groonga\" or \"mroonga\" or \"droonga\"." -msgstr "" - -# 597d231d2fba4609b07f04681a9b259e -msgid "" -"When executing the above query, you can get the records except \"rroonga\" " -"because \"rroonga\" is not specified as value in ``in_values``." -msgstr "" - -msgid "" -"There are two or more required parameter, ``target_value`` and multiple " -"``value``." -msgstr "" - -msgid "``target_value``" -msgstr "" - -msgid "" -"It specifies a column of the table that is specified by ``table`` parameter " -"in ``select``." -msgstr "" - -msgid "It specifies a value of the column which you want to select." -msgstr "" - -msgid "" -"``in_values`` returns whether the value of column exists in specified the " -"value of parameters or not." -msgstr "" - -msgid "" -"If record is matched to specified the value of parameters, it returns true. " -"Otherwise, it returns false." -msgstr "" - -msgid "now" -msgstr "now" - -msgid "now - 現在時刻を返す" -msgstr "now - 現在時刻を返す" - -msgid "" -"Groonga組込関数の一つであるnowについて説明します。組込関数は、script形式の" -"grn_expr中で呼び出すことができます。" -msgstr "" -"Groonga組込関数の一つであるnowについて説明します。組込関数は、script形式の" -"grn_expr中で呼び出すことができます。" - -msgid "now() 関数は現在時刻に対応するTime型の値を返します。" -msgstr "now() 関数は現在時刻に対応するTime型の値を返します。" - -msgid "現在時刻に対応するTime型のオブジェクトを返します。" -msgstr "現在時刻に対応するTime型のオブジェクトを返します。" - -msgid "query" -msgstr "query" - -msgid "" -"``query`` provides ``--match_columns`` and ``--query`` parameters of :doc:`/" -"reference/commands/select` feature as function. You can specify multiple " -"``query`` functions in ``--filter`` parameter in :doc:`/reference/commands/" -"select`." -msgstr "" -"``query`` provides ``--match_columns`` and ``--query`` parameters of :doc:`/" -"reference/commands/select` feature as function. You can specify multiple " -"``query`` functions in ``--filter`` parameter in :doc:`/reference/commands/" -"select`." - -msgid "" -"Because of such flexibility, you can control full text search behavior by " -"combination of multiple ``query`` functions." -msgstr "" -"Because of such flexibility, you can control full text search behavior by " -"combination of multiple ``query`` functions." - -msgid "" -"``query`` can be used in only ``--filter`` in :doc:`/reference/commands/" -"select`." -msgstr "" -"``query`` can be used in only ``--filter`` in :doc:`/reference/commands/" -"select`." - -msgid "" -"``query`` requires two arguments - ``match_columns`` and ``query_string``." -msgstr "" -"``query`` requires two arguments - ``match_columns`` and ``query_string``." - -msgid "The parameter ``query_expander`` or ``substitution_table`` is optional." -msgstr "" -"The parameter ``query_expander`` or ``substitution_table`` is optional." - -msgid "" -"Here is the simple usage of ``query`` function which execute full text " -"search by keyword 'alice' without using ``--match_columns`` and ``--query`` " -"arguments in ``--filter``." -msgstr "" -"Here is the simple usage of ``query`` function which execute full text " -"search by keyword 'alice' without using ``--match_columns`` and ``--query`` " -"arguments in ``--filter``." - -msgid "" -"When executing above query, the keyword 'alice' is weighted to the value - " -"'10'." -msgstr "" -"When executing above query, the keyword 'alice' is weighted to the value - " -"'10'." - -msgid "Here are the contrasting examples with/without ``query``." -msgstr "Here are the contrasting examples with/without ``query``." - -msgid "" -"In this case, the keywords 'groonga' and 'mroonga' and 'user' are given same " -"weight value. You can't pass different weight value to each keyword in this " -"way." -msgstr "" -"In this case, the keywords 'groonga' and 'mroonga' and 'user' are given same " -"weight value. You can't pass different weight value to each keyword in this " -"way." - -msgid "" -"On the other hand, by specifying multiple ``query``, the keywords 'groonga' " -"and 'mroonga' and 'user' are given different value of weight." -msgstr "" -"On the other hand, by specifying multiple ``query``, the keywords 'groonga' " -"and 'mroonga' and 'user' are given different value of weight." - -msgid "" -"As a result, you can control full text search result by giving different " -"weight to the keywords on your purpose." -msgstr "" -"As a result, you can control full text search result by giving different " -"weight to the keywords on your purpose." - -msgid "" -"There are two required parameter, ``match_columns`` and ``query_string``." -msgstr "" -"There are two required parameter, ``match_columns`` and ``query_string``." - -msgid "" -"It specifies the default target column for fulltext search by " -"``query_string`` parameter value. It is the same role as :ref:`select-match-" -"columns` parameter in ``select``." -msgstr "" -"It specifies the default target column for fulltext search by " -"``query_string`` parameter value. It is the same role as :ref:`select-match-" -"columns` parameter in ``select``." - -msgid "``query_string``" -msgstr "``query_string``" - -msgid "" -"It specifies the search condition in :doc:`/reference/grn_expr/" -"query_syntax`. It is the same role as ``query`` parameter in ``select``." -msgstr "" -"It specifies the search condition in :doc:`/reference/grn_expr/" -"query_syntax`. It is the same role as ``query`` parameter in ``select``." - -msgid "" -"See :ref:`select-match-columns` about ``query`` parameter in ``select``." -msgstr "" -"See :ref:`select-match-columns` about ``query`` parameter in ``select``." - -msgid "There are some optional parameters." -msgstr "There are some optional parameters." - -msgid "It specifies the plugin name for query expansion." -msgstr "It specifies the plugin name for query expansion." - -msgid "" -"There is one plugin bundled in official release - :doc:`/reference/" -"query_expanders/tsv`." -msgstr "" -"There is one plugin bundled in official release - :doc:`/reference/" -"query_expanders/tsv`." - -msgid "See :doc:`/reference/query_expanders/tsv` about details." -msgstr "See :doc:`/reference/query_expanders/tsv` about details." - -msgid "``substitution_table``" -msgstr "``substitution_table``" - -msgid "" -"It specifies the substitution table and substitution column name by " -"following format such as ``${TABLE}.${COLUMN}`` for query expansion." -msgstr "" -"It specifies the substitution table and substitution column name by " -"following format such as ``${TABLE}.${COLUMN}`` for query expansion." - -msgid "See :ref:`query-expander` about details." -msgstr "See :ref:`query-expander` about details." - -msgid "" -"``query`` returns whether any record is matched or not. If one or more " -"records are matched, it returns ``true``. Otherwise, it returns ``false``." -msgstr "" -"``query`` returns whether any record is matched or not. If one or more " -"records are matched, it returns ``true``. Otherwise, it returns ``false``." - -msgid "Support query_flags" -msgstr "Support query_flags" - -msgid "rand" -msgstr "rand" - -msgid "rand - 乱数を生成する" -msgstr "rand - 乱数を生成する" - -msgid "" -"Groonga組込関数の一つであるrandについて説明します。組込関数は、script形式の" -"grn_expr中で呼び出すことができます。" -msgstr "" -"Groonga組込関数の一つであるrandについて説明します。組込関数は、script形式の" -"grn_expr中で呼び出すことができます。" - -msgid "rand() 関数は 0 から max の間の疑似乱数整数を返します。" -msgstr "rand() 関数は 0 から max の間の疑似乱数整数を返します。" - -msgid "" -"返値の最大値を指定します。省略した場合は RAND_MAX が指定されたものとみなされ" -"ます。" -msgstr "" -"返値の最大値を指定します。省略した場合は RAND_MAX が指定されたものとみなされ" -"ます。" - -msgid "0 と max の間の数を表すInt32型の値を返します。" -msgstr "0 と max の間の数を表すInt32型の値を返します。" - -msgid "snippet_html" -msgstr "snippet_html" - -msgid "" -"``snippet_html`` extracts snippets of target text around search keywords " -"(``KWIC``. ``KeyWord In Context``). The snippets are prepared for embedding " -"HTML. Special characters such as ``<`` and ``>`` are escapsed as ``<`` " -"and ``>``. Keyword is surrounded with ``<span class=\"keyword\">`` and " -"``</span>``. For example, a snippet of ``I am a groonga user. <3`` for " -"keyword ``groonga`` is ``I am a <span class=\"keyword\">groonga</span> user. " -"<3``." -msgstr "" -"``snippet_html`` extracts snippets of target text around search keywords " -"(``KWIC``. ``KeyWord In Context``). The snippets are prepared for embedding " -"HTML. Special characters such as ``<`` and ``>`` are escapsed as ``<`` " -"and ``>``. Keyword is surrounded with ``<span class=\"keyword\">`` and " -"``</span>``. For example, a snippet of ``I am a groonga user. <3`` for " -"keyword ``groonga`` is ``I am a <span class=\"keyword\">groonga</span> user. " -"<3``." - -msgid "``snippet_html`` has only one parameter::" -msgstr "``snippet_html`` has only one parameter::" - -msgid "" -"``snippet_html`` has many parameters internally but they can't be specified " -"for now. You will be able to custom those parameters soon." -msgstr "" -"``snippet_html`` has many parameters internally but they can't be specified " -"for now. You will be able to custom those parameters soon." - -msgid "" -"``snippet_html`` can be used in only ``--output_columns`` in :doc:`/" -"reference/commands/select`." -msgstr "" -"``snippet_html`` can be used in only ``--output_columns`` in :doc:`/" -"reference/commands/select`." - -msgid "" -"You need to specify ``--command_version 2`` argument explicitly because " -"function call in ``--output_columns`` is experimental feature in Groonga " -"2.0.9. It will be enabled by default soon." -msgstr "" -"You need to specify ``--command_version 2`` argument explicitly because " -"function call in ``--output_columns`` is experimental feature in Groonga " -"2.0.9. It will be enabled by default soon." - -msgid "" -"The following example uses ``--query \"fast performance\"``. In this case, " -"``fast`` and ``performance`` are used as keywords." -msgstr "" -"The following example uses ``--query \"fast performance\"``. In this case, " -"``fast`` and ``performance`` are used as keywords." - -msgid "" -"``--query \"fast performance\"`` matches to only the first record's content. " -"``snippet_html(content)`` extracts two text parts that include the keywords " -"``fast`` or ``performance`` and surrounds the keywords with ``<span class=" -"\"keyword\">`` and ``</span>``." -msgstr "" -"``--query \"fast performance\"`` matches to only the first record's content. " -"``snippet_html(content)`` extracts two text parts that include the keywords " -"``fast`` or ``performance`` and surrounds the keywords with ``<span class=" -"\"keyword\">`` and ``</span>``." - -msgid "" -"The max number of text parts is 3. If there are 4 or more text parts that " -"include the keywords, only the leading 3 parts are only used." -msgstr "" -"The max number of text parts is 3. If there are 4 or more text parts that " -"include the keywords, only the leading 3 parts are only used." - -msgid "" -"The max size of a text part is 200byte. The unit is bytes not chracters. The " -"size doesn't include inserted ``<span keyword=\"keyword\">`` and ``</span>``." -msgstr "" -"The max size of a text part is 200byte. The unit is bytes not chracters. The " -"size doesn't include inserted ``<span keyword=\"keyword\">`` and ``</span>``." - -msgid "" -"Both the max number of text parts and the max size of a text part aren't " -"customizable." -msgstr "" -"Both the max number of text parts and the max size of a text part aren't " -"customizable." - -msgid "" -"``snippet_html`` returns an array of string or ``null``. If ``snippet_html`` " -"can't find any snippets, it returns ``null``." -msgstr "" -"``snippet_html`` returns an array of string or ``null``. If ``snippet_html`` " -"can't find any snippets, it returns ``null``." - -msgid "An element of array is a snippet::" -msgstr "An element of array is a snippet::" - -msgid "" -"A snippet includes one or more keywords. The max byte size of a snippet " -"except ``<span keyword=\"keyword\">`` and ``</span>`` is 200byte. The unit " -"isn't the number of chracters." -msgstr "" -"A snippet includes one or more keywords. The max byte size of a snippet " -"except ``<span keyword=\"keyword\">`` and ``</span>`` is 200byte. The unit " -"isn't the number of chracters." - -msgid "" -"The array size is larger than or equal to 0 and less than or equal to 3. The " -"max size 3 will be customizable soon." -msgstr "" -"The array size is larger than or equal to 0 and less than or equal to 3. The " -"max size 3 will be customizable soon." - -msgid "Make the max number of text parts customizable." -msgstr "Make the max number of text parts customizable." - -msgid "Make the max size of a text part customizable." -msgstr "Make the max size of a text part customizable." - -msgid "Make keywords customizable." -msgstr "Make keywords customizable." - -msgid "Make tag that surrounds a keyword customizable." -msgstr "Make tag that surrounds a keyword customizable." - -msgid "Make normalization customizable." -msgstr "Make normalization customizable." - -msgid "Support options by object literal." -msgstr "Support options by object literal." - -msgid "sub_filter" -msgstr "sub_filter" - -msgid "``sub_filter`` evaluates ``filter_string`` in ``scope`` context." -msgstr "``sub_filter`` evaluates ``filter_string`` in ``scope`` context." - -msgid "" -"``sub_filter`` can be used in only ``--filter`` in :doc:`/reference/commands/" -"select`." -msgstr "" -"``sub_filter`` can be used in only ``--filter`` in :doc:`/reference/commands/" -"select`." - -msgid "" -"``sub_filter`` requires two arguments. They are ``scope`` and " -"``filter_string``." -msgstr "" -"``sub_filter`` requires two arguments. They are ``scope`` and " -"``filter_string``." - -msgid "" -"Here is the simple usage of ``sub_filter`` function which extracts the blog " -"entry" -msgstr "" -"Here is the simple usage of ``sub_filter`` function which extracts the blog " -"entry" - -msgid "user 'A' commented out." -msgstr "user 'A' commented out." - -msgid "" -"When executing the above query, not only \"groonga's blog\", but also " -"\"mroonga's blog\". This is not what you want because user \"A\" does not " -"mention \"groonga\" to \"mroonga's blog\"." -msgstr "" -"When executing the above query, not only \"groonga's blog\", but also " -"\"mroonga's blog\". This is not what you want because user \"A\" does not " -"mention \"groonga\" to \"mroonga's blog\"." - -msgid "Without sub_filter, it means that following conditions are met." -msgstr "Without sub_filter, it means that following conditions are met." - -msgid "There is at least one record that user \"A\" commented out." -msgstr "There is at least one record that user \"A\" commented out." - -msgid "There is at least one record that mentioned about \"groonga\"." -msgstr "There is at least one record that mentioned about \"groonga\"." - -msgid "" -"On the other hand, executing the above query returns the intended result. " -"Because the arguments of sub_filter is evaluated in comments column's " -"context." -msgstr "" -"On the other hand, executing the above query returns the intended result. " -"Because the arguments of sub_filter is evaluated in comments column's " -"context." - -msgid "It means that sub_filter requires the following condition is met." -msgstr "It means that sub_filter requires the following condition is met." - -msgid "There are the records that user \"A\" mentions about \"groonga\"." -msgstr "There are the records that user \"A\" mentions about \"groonga\"." - -msgid "There are two required parameter, ``scope`` and ``filter_string``." -msgstr "There are two required parameter, ``scope`` and ``filter_string``." - -msgid "``scope``" -msgstr "``scope``" - -msgid "" -"It specifies a column of the table that is specified by ``table`` parameter " -"in ``select``. The column has a limitation. The limitation is described " -"later. ``filter_string`` is evaluated in the column context. It means that " -"``filter_string`` is evaluated like ``select --table TYPE_OF_THE_COLUMN --" -"filter FILTER_STRING``." -msgstr "" -"It specifies a column of the table that is specified by ``table`` parameter " -"in ``select``. The column has a limitation. The limitation is described " -"later. ``filter_string`` is evaluated in the column context. It means that " -"``filter_string`` is evaluated like ``select --table TYPE_OF_THE_COLUMN --" -"filter FILTER_STRING``." - -msgid "" -"The specified column type must be a table. In other words, the column type " -"must be reference type." -msgstr "" -"The specified column type must be a table. In other words, the column type " -"must be reference type." - -msgid "" -"You can chain columns by ``COLUMN_1.COLUMN_2.COLUMN_3...COLUMN_N`` syntax. " -"For example, ``user.group.name``." -msgstr "" -"You can chain columns by ``COLUMN_1.COLUMN_2.COLUMN_3...COLUMN_N`` syntax. " -"For example, ``user.group.name``." - -msgid "See :ref:`select-table` about ``table`` parameter in ``select``." -msgstr "See :ref:`select-table` about ``table`` parameter in ``select``." - -msgid "``filter_string``" -msgstr "``filter_string``" - -msgid "" -"It specifies a search condition in :doc:`/reference/grn_expr/script_syntax`. " -"It is evaluated in ``scope`` context." -msgstr "" -"It specifies a search condition in :doc:`/reference/grn_expr/script_syntax`. " -"It is evaluated in ``scope`` context." - -msgid "" -"``sub_filter`` returns whether any record is matched or not. If one or more " -"records are matched, it returns ``true``. Otherwise, it returns ``false``." -msgstr "" -"``sub_filter`` returns whether any record is matched or not. If one or more " -"records are matched, it returns ``true``. Otherwise, it returns ``false``." - -msgid "" -"Grn_expr is an object that searches records with specified conditions and " -"manipulates a database. It's pronounced as ``gurun expression``." -msgstr "" -"Grn_expr is an object that searches records with specified conditions and " -"manipulates a database. It's pronounced as ``gurun expression``." - -msgid "" -"Conditions for searching records from a database can be represented by " -"conbining condition expressions such as ``equal condition expression`` and " -"``less than condition expression`` with set operations such as ``AND``, " -"``OR`` and ``NOT``. Grn_expr executes those conditions to search records. " -"You can also use advanced searches such as similar search and near search by " -"grn_expr. You can also use flexible full text search. For example, you can " -"control hit scores for specified words and improve recall by re-searching " -"with high-recall algolithm dinamically. To determine whether re-searching or " -"not, the number of matched rescords is used." -msgstr "" -"Conditions for searching records from a database can be represented by " -"conbining condition expressions such as ``equal condition expression`` and " -"``less than condition expression`` with set operations such as ``AND``, " -"``OR`` and ``NOT``. Grn_expr executes those conditions to search records. " -"You can also use advanced searches such as similar search and near search by " -"grn_expr. You can also use flexible full text search. For example, you can " -"control hit scores for specified words and improve recall by re-searching " -"with high-recall algolithm dinamically. To determine whether re-searching or " -"not, the number of matched rescords is used." - -msgid "There are three ways to create grn_expr:" -msgstr "There are three ways to create grn_expr:" - -msgid "Parsing :doc:`/reference/grn_expr/query_syntax` string." -msgstr "Parsing :doc:`/reference/grn_expr/query_syntax` string." - -msgid "Parsing :doc:`/reference/grn_expr/script_syntax` string." -msgstr "Parsing :doc:`/reference/grn_expr/script_syntax` string." - -msgid "Calling grn_expr related APIs." -msgstr "Calling grn_expr related APIs." - -msgid "" -":doc:`/reference/grn_expr/query_syntax` is for common search form in " -"Internet search site. It's simple and easy to use but it has a limitation. " -"You can not use all condition expressions and set operations in :doc:`/" -"reference/grn_expr/query_syntax`. You can use :doc:`/reference/grn_expr/" -"query_syntax` with ``query`` option in :doc:`/reference/commands/select`." -msgstr "" -":doc:`/reference/grn_expr/query_syntax` is for common search form in " -"Internet search site. It's simple and easy to use but it has a limitation. " -"You can not use all condition expressions and set operations in :doc:`/" -"reference/grn_expr/query_syntax`. You can use :doc:`/reference/grn_expr/" -"query_syntax` with ``query`` option in :doc:`/reference/commands/select`." - -msgid "" -":doc:`/reference/grn_expr/script_syntax` is ECMAScript like syntax. You can " -"use all condition expresssions and set operations in :doc:`/reference/" -"grn_expr/script_syntax`. You can use :doc:`/reference/grn_expr/" -"script_syntax` with ``filter`` option and ``scorer`` option in :doc:`/" -"reference/commands/select`." -msgstr "" -":doc:`/reference/grn_expr/script_syntax` is ECMAScript like syntax. You can " -"use all condition expresssions and set operations in :doc:`/reference/" -"grn_expr/script_syntax`. You can use :doc:`/reference/grn_expr/" -"script_syntax` with ``filter`` option and ``scorer`` option in :doc:`/" -"reference/commands/select`." - -msgid "" -"You can use groonga as a library and create a grn_expr by calling grn_expr " -"related APIs. You can use full features with calling APIs like :doc:`/" -"reference/grn_expr/script_syntax`. Calling APIs is useful creating a custom " -"syntax to create grn_expr. They are used in `rroonga <http://ranguba.org/" -"#about-rroonga>`_ that is Ruby bindings of Groonga. Rroonga can create a " -"grn_expr by Ruby's syntax instead of parsing string." -msgstr "" -"You can use groonga as a library and create a grn_expr by calling grn_expr " -"related APIs. You can use full features with calling APIs like :doc:`/" -"reference/grn_expr/script_syntax`. Calling APIs is useful creating a custom " -"syntax to create grn_expr. They are used in `rroonga <http://ranguba.org/" -"#about-rroonga>`_ that is Ruby bindings of Groonga. Rroonga can create a " -"grn_expr by Ruby's syntax instead of parsing string." - -msgid ":doc:`/reference/api/grn_expr`: grn_expr related APIs" -msgstr ":doc:`/reference/api/grn_expr`: grn_expr related APIs" - -msgid "Query syntax" -msgstr "Query syntax" - -msgid "" -"Query syntax is a syntax to specify search condition for common Web search " -"form. It is similar to the syntax of Google's search form. For example, " -"``word1 word2`` means that groonga searches records that contain both " -"``word1`` and ``word2``. ``word1 OR word2`` means that groogna searches " -"records that contain either ``word1`` or ``word2``." -msgstr "" -"Query syntax is a syntax to specify search condition for common Web search " -"form. It is similar to the syntax of Google's search form. For example, " -"``word1 word2`` means that groonga searches records that contain both " -"``word1`` and ``word2``. ``word1 OR word2`` means that groogna searches " -"records that contain either ``word1`` or ``word2``." - -msgid "" -"Query syntax consists of ``conditional expression``, ``combind expression`` " -"and ``assignment expression``. Nomrally ``assignment expression`` can be " -"ignored. Because ``assignment expression`` is disabled in ``--query`` option " -"of :doc:`/reference/commands/select`. You can use it if you use groonga as " -"library and customize query syntax parser options." -msgstr "" -"Query syntax consists of ``conditional expression``, ``combind expression`` " -"and ``assignment expression``. Nomrally ``assignment expression`` can be " -"ignored. Because ``assignment expression`` is disabled in ``--query`` option " -"of :doc:`/reference/commands/select`. You can use it if you use groonga as " -"library and customize query syntax parser options." - -msgid "" -"``Conditinal expression`` specifies an condition. ``Combinded expression`` " -"consists of one or more ``conditional expression``, ``combined expression`` " -"or ``assignment expression``. ``Assignment expression`` can assigns a column " -"to a value." -msgstr "" -"``Conditinal expression`` specifies an condition. ``Combinded expression`` " -"consists of one or more ``conditional expression``, ``combined expression`` " -"or ``assignment expression``. ``Assignment expression`` can assigns a column " -"to a value." - -msgid "Sample data" -msgstr "Sample data" - -msgid "" -"There is a table, ``Entries``, for blog entries. An entry has title, content " -"and the number of likes for the entry. Title is key of ``Entries``. Content " -"is value of ``Entries.content`` column. The number of likes is value of " -"``Entries.n_likes`` column." -msgstr "" -"There is a table, ``Entries``, for blog entries. An entry has title, content " -"and the number of likes for the entry. Title is key of ``Entries``. Content " -"is value of ``Entries.content`` column. The number of likes is value of " -"``Entries.n_likes`` column." - -msgid "Escape" -msgstr "Escape" - -msgid "" -"There are special characters in query syntax. To use a special character as " -"itself, it should be escaped by prepending ``\\``. For example, ``\"`` is a " -"special character. It is escaped as ``\\\"``." -msgstr "" -"There are special characters in query syntax. To use a special character as " -"itself, it should be escaped by prepending ``\\``. For example, ``\"`` is a " -"special character. It is escaped as ``\\\"``." - -msgid "Here is a special character list:" -msgstr "Here is a special character list:" - -msgid "" -"``[space]`` (escaped as ``[backslash][space]``) (You should substitute " -"``[space]`` with a white space character that is 0x20 in ASCII and " -"``[backslash]`` with ``\\\\``.)" -msgstr "" -"``[space]`` (escaped as ``[backslash][space]``) (You should substitute " -"``[space]`` with a white space character that is 0x20 in ASCII and " -"``[backslash]`` with ``\\\\``.)" - -msgid "``\"`` (escaped as ``\\\"``)" -msgstr "``\"`` (escaped as ``\\\"``)" - -msgid "``'`` (escaped as ``\\'``)" -msgstr "``'`` (escaped as ``\\'``)" - -msgid "``(`` (escaped as ``\\(``)" -msgstr "``(`` (escaped as ``\\(``)" - -msgid "``)`` (escaped as ``\\)``)" -msgstr "``)`` (escaped as ``\\)``)" - -msgid "``\\`` (escaped as ``\\\\``)" -msgstr "``\\`` (escaped as ``\\\\``)" - -msgid "" -"You can use quote instead of escape special characters except ``\\`` " -"(backslash). You need to use backslash for escaping backslash like ``\\\\`` " -"in quote." -msgstr "" -"You can use quote instead of escape special characters except ``\\`` " -"(backslash). You need to use backslash for escaping backslash like ``\\\\`` " -"in quote." - -msgid "" -"Quote syntax is ``\"...\"`` or ``'...'``. You need escape ``\"`` as ``\\\"`` " -"in ``\"...\"`` quote syntax. You need escape ``'`` as ``\\'`` in ``'...'`` " -"quote syntax. For example, ``Alice's brother (Bob)`` can be quoted ``" -"\"Alice's brother (Bob)\"`` or ``'Alice\\'s brother (Bob)'``." -msgstr "" -"Quote syntax is ``\"...\"`` or ``'...'``. You need escape ``\"`` as ``\\\"`` " -"in ``\"...\"`` quote syntax. You need escape ``'`` as ``\\'`` in ``'...'`` " -"quote syntax. For example, ``Alice's brother (Bob)`` can be quoted ``" -"\"Alice's brother (Bob)\"`` or ``'Alice\\'s brother (Bob)'``." - -msgid "" -"There is an important point which you have to care. The ``\\`` (backslash) " -"character is interpreted by command line shell. So if you want to search " -"``(`` itself for example, you need to escape twice (``\\\\(``) in command " -"line shell. The command line shell interprets ``\\\\(`` as ``\\(``, then " -"pass such a literal to Groonga. Groonga regards ``\\(`` as ``(``, then " -"search ``(`` itself from database. If you can't do intended search by " -"Groonga, confirm whether special character is escaped properly." -msgstr "" - -msgid "Conditional expression" -msgstr "Conditional expression" - -msgid "Here is available conditional expression list." -msgstr "Here is available conditional expression list." - -msgid "Full text search condition" -msgstr "Full text search condition" - -msgid "Its syntax is ``keyword``." -msgstr "Its syntax is ``keyword``." - -msgid "" -"``Full text search condition`` specifies a full text search condition " -"against the default match columns. Match columns are full text search target " -"columns." -msgstr "" -"``Full text search condition`` specifies a full text search condition " -"against the default match columns. Match columns are full text search target " -"columns." - -msgid "" -"You should specify the default match columns for full text search. They can " -"be specified by ``--match_columns`` option of :doc:`/reference/commands/" -"select`. If you don't specify the default match columns, this conditional " -"expression fails." -msgstr "" -"You should specify the default match columns for full text search. They can " -"be specified by ``--match_columns`` option of :doc:`/reference/commands/" -"select`. If you don't specify the default match columns, this conditional " -"expression fails." - -msgid "" -"This conditional expression does full text search with ``keyword``. " -"``keyword`` should not contain any spaces. If ``keyword`` contains a space " -"such as ``search keyword``, it means two full text search conditions; " -"``search`` and ``keyword``. If you want to specifies a keyword that contains " -"one or more spaces, you can use ``phrase search condition`` that is " -"described below." -msgstr "" -"This conditional expression does full text search with ``keyword``. " -"``keyword`` should not contain any spaces. If ``keyword`` contains a space " -"such as ``search keyword``, it means two full text search conditions; " -"``search`` and ``keyword``. If you want to specifies a keyword that contains " -"one or more spaces, you can use ``phrase search condition`` that is " -"described below." - -msgid "Here is a simple exmaple." -msgstr "Here is a simple exmaple." - -msgid "" -"The expression matches records that contain a word ``fast`` in ``content`` " -"column value." -msgstr "" -"The expression matches records that contain a word ``fast`` in ``content`` " -"column value." - -msgid "``content`` column is the default match column." -msgstr "``content`` column is the default match column." - -msgid "Phrase search condition" -msgstr "Phrase search condition" - -msgid "Its syntax is ``\"search keyword\"``." -msgstr "Its syntax is ``\"search keyword\"``." - -msgid "" -"``Phrase search condition`` specifies a phrase search condition against the " -"default match columns." -msgstr "" -"``Phrase search condition`` specifies a phrase search condition against the " -"default match columns." - -msgid "" -"This conditional expression does phrase search with ``search keyword``. " -"Phrase search searches records that contain ``search`` and ``keyword`` and " -"those terms are appeared in the same order and adjacent. Thus, ``Put a " -"search keyword in the form`` is matched but ``Search by the keyword`` and " -"``There is a keyword. Search by it!`` aren't matched." -msgstr "" -"This conditional expression does phrase search with ``search keyword``. " -"Phrase search searches records that contain ``search`` and ``keyword`` and " -"those terms are appeared in the same order and adjacent. Thus, ``Put a " -"search keyword in the form`` is matched but ``Search by the keyword`` and " -"``There is a keyword. Search by it!`` aren't matched." - -msgid "" -"The expression matches records that contain a phrase ``I started`` in " -"``content`` column value. ``I also started`` isn't matched because ``I`` and " -"``started`` aren't adjacent." -msgstr "" -"The expression matches records that contain a phrase ``I started`` in " -"``content`` column value. ``I also started`` isn't matched because ``I`` and " -"``started`` aren't adjacent." - -msgid "Full text search condition (with explicit match column)" -msgstr "Full text search condition (with explicit match column)" - -msgid "Its syntax is ``column:@keyword``." -msgstr "Its syntax is ``column:@keyword``." - -msgid "" -"It's similar to ``full text search condition`` but it doesn't require the " -"default match columns. You need to specify match column for the full text " -"search condition by ``column:`` instead of ``--match_columns`` option of :" -"doc:`/reference/commands/select`." -msgstr "" -"It's similar to ``full text search condition`` but it doesn't require the " -"default match columns. You need to specify match column for the full text " -"search condition by ``column:`` instead of ``--match_columns`` option of :" -"doc:`/reference/commands/select`." - -msgid "" -"This condtional expression is useful when you want to use two or more full " -"text search against different columns. The default match columns specified " -"by ``--match_columns`` option can't be specified multiple times. You need to " -"specify the second match column by this conditional expression." -msgstr "" -"This condtional expression is useful when you want to use two or more full " -"text search against different columns. The default match columns specified " -"by ``--match_columns`` option can't be specified multiple times. You need to " -"specify the second match column by this conditional expression." - -msgid "" -"The different between ``full text search condition`` and ``full text search " -"condition (with explicit match column)`` is whether advanced match columns " -"are supported or not. ``Full text search condition`` supports advanced match " -"columns but ``full text search condition (with explicit match column)`` " -"isn't supported. Advanced match columns has the following features:" -msgstr "" -"The different between ``full text search condition`` and ``full text search " -"condition (with explicit match column)`` is whether advanced match columns " -"are supported or not. ``Full text search condition`` supports advanced match " -"columns but ``full text search condition (with explicit match column)`` " -"isn't supported. Advanced match columns has the following features:" - -msgid "Weight is supported." -msgstr "Weight is supported." - -msgid "Using multiple columns are supported." -msgstr "Using multiple columns are supported." - -msgid "Using index column as a match column is supported." -msgstr "Using index column as a match column is supported." - -msgid "" -"See description of ``--match_columns`` option of :doc:`/reference/commands/" -"select` about them." -msgstr "" -"See description of ``--match_columns`` option of :doc:`/reference/commands/" -"select` about them." - -msgid "Phrase search condition (with explicit match column)" -msgstr "Phrase search condition (with explicit match column)" - -msgid "Its syntax is ``column:@\"search keyword\"``." -msgstr "Its syntax is ``column:@\"search keyword\"``." - -msgid "" -"It's similar to ``phrase search condition`` but it doesn't require the " -"default match columns. You need to specify match column for the phrase " -"search condition by ``column:`` instead of ``--match_columns`` option of :" -"doc:`/reference/commands/select`." -msgstr "" -"It's similar to ``phrase search condition`` but it doesn't require the " -"default match columns. You need to specify match column for the phrase " -"search condition by ``column:`` instead of ``--match_columns`` option of :" -"doc:`/reference/commands/select`." - -msgid "" -"The different between ``phrase search condition`` and ``phrase search " -"condition (with explicit match column)`` is similar to between ``full text " -"search condition`` and ``full text search condition (with explicit match " -"column)``. ``Phrase search condition`` supports advanced match columns but " -"``phrase search condition (with explicit match column)`` isn't supported. " -"See description of ``full text search condition (with explicit match " -"column)`` about advanced match columns." -msgstr "" -"The different between ``phrase search condition`` and ``phrase search " -"condition (with explicit match column)`` is similar to between ``full text " -"search condition`` and ``full text search condition (with explicit match " -"column)``. ``Phrase search condition`` supports advanced match columns but " -"``phrase search condition (with explicit match column)`` isn't supported. " -"See description of ``full text search condition (with explicit match " -"column)`` about advanced match columns." - -msgid "Prefix search condition" -msgstr "Prefix search condition" - -msgid "Its syntax is ``column:^value`` or ``value*``." -msgstr "Its syntax is ``column:^value`` or ``value*``." - -msgid "" -"This conditional expression does prefix search with ``value``. Prefix search " -"searches records that contain a word that starts with ``value``." -msgstr "" -"This conditional expression does prefix search with ``value``. Prefix search " -"searches records that contain a word that starts with ``value``." - -msgid "" -"You can use fast prefix search against a column. The column must be indexed " -"and index table must be patricia trie table (``TABLE_PAT_KEY``) or double " -"array trie table (``TABLE_DAT_KEY``). You can also use fast prefix search " -"against ``_key`` pseudo column of patricia trie table or double array trie " -"table. You don't need to index ``_key``." -msgstr "" -"You can use fast prefix search against a column. The column must be indexed " -"and index table must be patricia trie table (``TABLE_PAT_KEY``) or double " -"array trie table (``TABLE_DAT_KEY``). You can also use fast prefix search " -"against ``_key`` pseudo column of patricia trie table or double array trie " -"table. You don't need to index ``_key``." - -msgid "" -"Prefix search can be used with other table types but it causes all records " -"scan. It's not problem for small records but it spends more time for large " -"records." -msgstr "" -"Prefix search can be used with other table types but it causes all records " -"scan. It's not problem for small records but it spends more time for large " -"records." - -msgid "" -"It doesn't require the default match columns such as ``full text search " -"condition`` and ``phrase search condition``." -msgstr "" -"It doesn't require the default match columns such as ``full text search " -"condition`` and ``phrase search condition``." - -msgid "" -"The expression matches records that contain a word that starts with ``Goo`` " -"in ``_key`` pseudo column value. ``Good-bye Senna`` and ``Good-bye Tritonn`` " -"are matched with the expression." -msgstr "" -"The expression matches records that contain a word that starts with ``Goo`` " -"in ``_key`` pseudo column value. ``Good-bye Senna`` and ``Good-bye Tritonn`` " -"are matched with the expression." - -msgid "Suffix search condition" -msgstr "Suffix search condition" - -msgid "Its syntax is ``column:$value``." -msgstr "Its syntax is ``column:$value``." - -msgid "" -"This conditional expression does suffix search with ``value``. Suffix search " -"searches records that contain a word that ends with ``value``." -msgstr "" -"This conditional expression does suffix search with ``value``. Suffix search " -"searches records that contain a word that ends with ``value``." - -msgid "" -"You can use fast suffix search against a column. The column must be indexed " -"and index table must be patricia trie table (``TABLE_PAT_KEY``) with " -"``KEY_WITH_SIS`` flag. You can also use fast suffix search against ``_key`` " -"pseudo column of patricia trie table (``TABLE_PAT_KEY``) with " -"``KEY_WITH_SIS`` flag. You don't need to index ``_key``. We recommended that " -"you use index column based fast suffix search instead of ``_key`` based fast " -"suffix search. ``_key`` based fast suffix search returns automatically " -"registered substrings. (TODO: write document about suffix search and link to " -"it from here.)" -msgstr "" -"You can use fast suffix search against a column. The column must be indexed " -"and index table must be patricia trie table (``TABLE_PAT_KEY``) with " -"``KEY_WITH_SIS`` flag. You can also use fast suffix search against ``_key`` " -"pseudo column of patricia trie table (``TABLE_PAT_KEY``) with " -"``KEY_WITH_SIS`` flag. You don't need to index ``_key``. We recommended that " -"you use index column based fast suffix search instead of ``_key`` based fast " -"suffix search. ``_key`` based fast suffix search returns automatically " -"registered substrings. (TODO: write document about suffix search and link to " -"it from here.)" - -msgid "" -"Fast suffix search can be used only for non-ASCII characters such as " -"hiragana in Japanese. You cannot use fast suffix search for ASCII character." -msgstr "" -"Fast suffix search can be used only for non-ASCII characters such as " -"hiragana in Japanese. You cannot use fast suffix search for ASCII character." - -msgid "" -"Suffix search can be used with other table types or patricia trie table " -"without ``KEY_WITH_SIS`` flag but it causes all records scan. It's not " -"problem for small records but it spends more time for large records." -msgstr "" -"Suffix search can be used with other table types or patricia trie table " -"without ``KEY_WITH_SIS`` flag but it causes all records scan. It's not " -"problem for small records but it spends more time for large records." - -msgid "" -"Here is a simple exmaple. It uses fast suffix search for hiragana in " -"Japanese that is one of non-ASCII characters." -msgstr "" -"Here is a simple exmaple. It uses fast suffix search for hiragana in " -"Japanese that is one of non-ASCII characters." - -msgid "" -"The expression matches records that have value that ends with ``んが`` in " -"``content`` column value. ``ぐるんが`` and ``むるんが`` are matched with the " -"expression." -msgstr "" -"The expression matches records that have value that ends with ``んが`` in " -"``content`` column value. ``ぐるんが`` and ``むるんが`` are matched with the " -"expression." - -msgid "Equal condition" -msgstr "Equal condition" - -msgid "Its syntax is ``column:value``." -msgstr "Its syntax is ``column:value``." - -msgid "It matches records that ``column`` value is equal to ``value``." -msgstr "It matches records that ``column`` value is equal to ``value``." - -msgid "" -"The expression matches records that ``_key`` column value is equal to " -"``Groonga``." -msgstr "" -"The expression matches records that ``_key`` column value is equal to " -"``Groonga``." - -msgid "Not equal condition" -msgstr "Not equal condition" - -msgid "Its syntax is ``column:!value``." -msgstr "Its syntax is ``column:!value``." - -msgid "It matches records that ``column`` value isn't equal to ``value``." -msgstr "It matches records that ``column`` value isn't equal to ``value``." - -msgid "" -"The expression matches records that ``_key`` column value is not equal to " -"``Groonga``." -msgstr "" -"The expression matches records that ``_key`` column value is not equal to " -"``Groonga``." - -msgid "Less than condition" -msgstr "Less than condition" - -msgid "Its syntax is ``column:<value``." -msgstr "Its syntax is ``column:<value``." - -msgid "It matches records that ``column`` value is less than ``value``." -msgstr "It matches records that ``column`` value is less than ``value``." - -msgid "" -"If ``column`` type is numerical type such as ``Int32``, ``column`` value and " -"``value`` are compared as number. If ``column`` type is text type such as " -"``ShortText``, ``column`` value and ``value`` are compared as bit sequence." -msgstr "" -"If ``column`` type is numerical type such as ``Int32``, ``column`` value and " -"``value`` are compared as number. If ``column`` type is text type such as " -"``ShortText``, ``column`` value and ``value`` are compared as bit sequence." - -msgid "" -"The expression matches records that ``n_likes`` column value is less than " -"``10``." -msgstr "" -"The expression matches records that ``n_likes`` column value is less than " -"``10``." - -msgid "Greater than condition" -msgstr "Greater than condition" - -msgid "Its syntax is ``column:>value``." -msgstr "Its syntax is ``column:>value``." - -msgid "It matches records that ``column`` value is greater than ``value``." -msgstr "It matches records that ``column`` value is greater than ``value``." - -msgid "" -"The expression matches records that ``n_likes`` column value is greater than " -"``10``." -msgstr "" -"The expression matches records that ``n_likes`` column value is greater than " -"``10``." - -msgid "Less than or equal to condition" -msgstr "Less than or equal to condition" - -msgid "Its syntax is ``column:<=value``." -msgstr "Its syntax is ``column:<=value``." - -msgid "" -"It matches records that ``column`` value is less than or equal to ``value``." -msgstr "" -"It matches records that ``column`` value is less than or equal to ``value``." - -msgid "" -"The expression matches records that ``n_likes`` column value is less than or " -"equal to ``10``." -msgstr "" -"The expression matches records that ``n_likes`` column value is less than or " -"equal to ``10``." - -msgid "Greater than or equal to condition" -msgstr "Greater than or equal to condition" - -msgid "Its syntax is ``column:>=value``." -msgstr "Its syntax is ``column:>=value``." - -msgid "" -"It matches records that ``column`` value is greater than or equal to " -"``value``." -msgstr "" -"It matches records that ``column`` value is greater than or equal to " -"``value``." - -msgid "" -"The expression matches records that ``n_likes`` column value is greater than " -"or equal to ``10``." -msgstr "" -"The expression matches records that ``n_likes`` column value is greater than " -"or equal to ``10``." - -msgid "Combined expression" -msgstr "Combined expression" - -msgid "Here is available combined expression list." -msgstr "Here is available combined expression list." - -msgid "Logical OR" -msgstr "Logical OR" - -msgid "Its syntax is ``a OR b``." -msgstr "Its syntax is ``a OR b``." - -msgid "" -"``a`` and ``b`` are conditional expressions, conbinded expressions or " -"assignment expressions." -msgstr "" -"``a`` and ``b`` are conditional expressions, conbinded expressions or " -"assignment expressions." - -msgid "If at least one of ``a`` and ``b`` are matched, ``a OR b`` is matched." -msgstr "If at least one of ``a`` and ``b`` are matched, ``a OR b`` is matched." - -msgid "" -"The expression matches records that ``n_likes`` column value is greater than " -"``10`` or contain a word ``senna`` in ``content`` column value." -msgstr "" -"The expression matches records that ``n_likes`` column value is greater than " -"``10`` or contain a word ``senna`` in ``content`` column value." - -msgid "Logical AND" -msgstr "Logical AND" - -msgid "Its syntax is ``a + b`` or just ``a b``." -msgstr "Its syntax is ``a + b`` or just ``a b``." - -msgid "If both ``a`` and ``b`` are matched, ``a + b`` is matched." -msgstr "If both ``a`` and ``b`` are matched, ``a + b`` is matched." - -msgid "" -"You can specify ``+`` the first expression such as ``+a``. The ``+`` is just " -"ignored." -msgstr "" -"You can specify ``+`` the first expression such as ``+a``. The ``+`` is just " -"ignored." - -msgid "" -"The expression matches records that ``n_likes`` column value is greater than " -"or equal to ``10`` and contain a word ``groonga`` in ``content`` column " -"value." -msgstr "" -"The expression matches records that ``n_likes`` column value is greater than " -"or equal to ``10`` and contain a word ``groonga`` in ``content`` column " -"value." - -msgid "Logical NOT" -msgstr "Logical NOT" - -msgid "Its syntax is ``a - b``." -msgstr "Its syntax is ``a - b``." - -msgid "If ``a`` is matched and ``b`` is not matched, ``a - b`` is matched." -msgstr "If ``a`` is matched and ``b`` is not matched, ``a - b`` is matched." - -msgid "" -"You can not specify ``-`` the first expression such as ``-a``. It's syntax " -"error." -msgstr "" -"You can not specify ``-`` the first expression such as ``-a``. It's syntax " -"error." - -msgid "" -"The expression matches records that ``n_likes`` column value is greater than " -"or equal to ``10`` and don't contain a word ``groonga`` in ``content`` " -"column value." -msgstr "" -"The expression matches records that ``n_likes`` column value is greater than " -"or equal to ``10`` and don't contain a word ``groonga`` in ``content`` " -"column value." - -msgid "Grouping" -msgstr "Grouping" - -msgid "Its syntax is ``(...)``. ``...`` is space separated expression list." -msgstr "Its syntax is ``(...)``. ``...`` is space separated expression list." - -msgid "" -"``(...)`` groups one ore more expressions and they can be processed as an " -"expression. ``a b OR c`` means that ``a`` and ``b`` are matched or ``c`` is " -"matched. ``a (b OR c)`` means that ``a`` and one of ``b`` and ``c`` are " -"matched." -msgstr "" -"``(...)`` groups one ore more expressions and they can be processed as an " -"expression. ``a b OR c`` means that ``a`` and ``b`` are matched or ``c`` is " -"matched. ``a (b OR c)`` means that ``a`` and one of ``b`` and ``c`` are " -"matched." - -msgid "" -"The first expression doesn't use grouping. It matches records that ``n_likes:" -"<5`` and ``content:@senna`` are matched or ``content:@fast`` is matched." -msgstr "" -"The first expression doesn't use grouping. It matches records that ``n_likes:" -"<5`` and ``content:@senna`` are matched or ``content:@fast`` is matched." - -msgid "" -"The second expression uses grouping. It matches records that ``n_likes:<5`` " -"and one of ``content:@senna`` or ``content:@fast`` are matched." -msgstr "" -"The second expression uses grouping. It matches records that ``n_likes:<5`` " -"and one of ``content:@senna`` or ``content:@fast`` are matched." - -msgid "Assignment expression" -msgstr "Assignment expression" - -msgid "" -"This section is for advanced users. Because assignment expression is " -"disabled in ``--query`` option of :doc:`/reference/commands/select` by " -"default. You need to specify ``ALLOW_COLUMN|ALLOW_UPDATE`` as ``--" -"query_flags`` option value to enable assignment expression." -msgstr "" -"This section is for advanced users. Because assignment expression is " -"disabled in ``--query`` option of :doc:`/reference/commands/select` by " -"default. You need to specify ``ALLOW_COLUMN|ALLOW_UPDATE`` as ``--" -"query_flags`` option value to enable assignment expression." - -msgid "" -"Assignment expression in query syntax has some limitations. So you should " -"use :doc:`/reference/grn_expr/script_syntax` instead of query syntax for " -"assignment." -msgstr "" -"Assignment expression in query syntax has some limitations. So you should " -"use :doc:`/reference/grn_expr/script_syntax` instead of query syntax for " -"assignment." - -msgid "" -"There is only one syntax for assignment expression. It's ``column:=value``." -msgstr "" -"There is only one syntax for assignment expression. It's ``column:=value``." - -msgid "" -"``value`` is assigend to ``column``. ``value`` is always processed as string " -"in query syntax. ``value`` is casted to the type of ``column`` " -"automatically. It causes some limitations. For example, you cannot use " -"boolean literal such as ``true`` and ``false`` for ``Bool`` type column. You " -"need to use empty string for ``false`` but query syntax doesn't support " -"``column:=`` syntax." -msgstr "" -"``value`` is assigend to ``column``. ``value`` is always processed as string " -"in query syntax. ``value`` is casted to the type of ``column`` " -"automatically. It causes some limitations. For example, you cannot use " -"boolean literal such as ``true`` and ``false`` for ``Bool`` type column. You " -"need to use empty string for ``false`` but query syntax doesn't support " -"``column:=`` syntax." - -msgid "See :doc:`/reference/cast` about cast." -msgstr "See :doc:`/reference/cast` about cast." - -msgid "Script syntax" -msgstr "Script syntax" - -msgid "" -"Script syntax is a syntax to specify complex search condition. It is similar " -"to ECMAScript. For example, ``_key == \"book\"`` means that groonga searches " -"records that ``_key`` value is ``\"book\"``. All values are string in :doc:" -"`query_syntax` but its own type in script syntax. For example, ``\"book\"`` " -"is string, ``1`` is integer, ``TokenBigram`` is the object whose name is " -"``TokenBigram`` and so on." -msgstr "" -"Script syntax is a syntax to specify complex search condition. It is similar " -"to ECMAScript. For example, ``_key == \"book\"`` means that groonga searches " -"records that ``_key`` value is ``\"book\"``. All values are string in :doc:" -"`query_syntax` but its own type in script syntax. For example, ``\"book\"`` " -"is string, ``1`` is integer, ``TokenBigram`` is the object whose name is " -"``TokenBigram`` and so on." - -msgid "" -"Script syntax doesn't support full ECMAScript syntax. For example, script " -"syntax doesn't support statement such as ``if`` control statement, ``for`` " -"iteration statement and variable definition statement. Function definion is " -"not supported too. But script syntax addes the original additional " -"operators. They are described after ECMAScript syntax is described." -msgstr "" -"Script syntax doesn't support full ECMAScript syntax. For example, script " -"syntax doesn't support statement such as ``if`` control statement, ``for`` " -"iteration statement and variable definition statement. Function definion is " -"not supported too. But script syntax addes the original additional " -"operators. They are described after ECMAScript syntax is described." - -msgid "Security" -msgstr "" - -msgid "" -"For security reason, you should not pass an input from users to Groonga " -"directly. If there is an evil user, the user may input a query that " -"retrieves records that should not be shown to the user." -msgstr "" - -msgid "Think about the following case." -msgstr "" - -msgid "" -"A Groonga application constructs a Groonga request by the following program::" -msgstr "" - -msgid "" -"``user_input`` is an input from user. If the input is ``query``, here is the " -"constructed :ref:`select-filter` parameter::" -msgstr "" - -msgid "" -"If the input is ``x\" || true || \"``, here is the constructed ref:`select-" -"filter` parameter::" -msgstr "" - -msgid "" -"This query matches to all records. The user will get all records from your " -"database. The user may be evil." -msgstr "" - -msgid "" -"It's better that you just receive an user input as a value. It means that " -"you don't accept that user input can contain operator such as ``@`` and " -"``&&``. If you accept operator, user can create evil query." -msgstr "" - -msgid "" -"If user input has only value, you blocks evil query by escaping user input " -"value. Here is a list how to escape user input value:" -msgstr "" - -msgid "True value: Convert it to ``true``." -msgstr "" - -msgid "False value: Convert it to ``false``." -msgstr "" - -msgid "" -"Numerical value: Convert it to number. For example, ``1.2`` should be " -"converted to ``1.2``." -msgstr "" - -msgid "" -"String value: Replace ``\"`` with ``\\\"`` and ``\\`` with ``\\\\`` in the " -"string value and surround substituted string value by ``\"``. For example, " -"``double \" quote and back \\ slash`` should be converted to ``\"double \\\" " -"quote and back \\\\ slash\"``." -msgstr "" - -msgid "Literals" -msgstr "Literals" - -msgid "Integer" -msgstr "Integer" - -msgid "" -"Integer literal is sequence of ``0`` to ``9`` such as ``1234567890``. ``+`` " -"or ``-`` can be prepended as sign such as ``+29`` and ``-29``. Integer " -"literal must be decimal. Octal notation, hex and so on can't be used." -msgstr "" -"Integer literal is sequence of ``0`` to ``9`` such as ``1234567890``. ``+`` " -"or ``-`` can be prepended as sign such as ``+29`` and ``-29``. Integer " -"literal must be decimal. Octal notation, hex and so on can't be used." - -msgid "" -"The maximum value of integer literal is ``9223372036854775807`` (``= 2 ** 63 " -"- 1``). The minimum value of integer literal is ``-9223372036854775808`` " -"(``= -(2 ** 63)``)." -msgstr "" -"The maximum value of integer literal is ``9223372036854775807`` (``= 2 ** 63 " -"- 1``). The minimum value of integer literal is ``-9223372036854775808`` " -"(``= -(2 ** 63)``)." - -msgid "Float" -msgstr "Float" - -msgid "" -"Float literal is sequence of ``0`` to ``9``, ``.`` and ``0`` to ``9`` such " -"as ``3.14``. ``+`` or ``-`` can be prepended as sign such as ``+3.14`` and " -"``-3.14``. ``${RADIX}e${EXPORNENTIAL}`` and ``${RADIX}E${EXPORNENTIAL}`` " -"formats are also supported. For example, ``314e-2`` is the same as ``3.14``." -msgstr "" -"Float literal is sequence of ``0`` to ``9``, ``.`` and ``0`` to ``9`` such " -"as ``3.14``. ``+`` or ``-`` can be prepended as sign such as ``+3.14`` and " -"``-3.14``. ``${RADIX}e${EXPORNENTIAL}`` and ``${RADIX}E${EXPORNENTIAL}`` " -"formats are also supported. For example, ``314e-2`` is the same as ``3.14``." - -msgid "String" -msgstr "String" - -msgid "" -"String literal is ``\"...\"``. You need to escape ``\"`` in literal by " -"prepending ``\\\\'' such as ``\\\"``. For example, ``\"Say \\\"Hello!\\\"." -"\"`` is a literal for ``Say \"Hello!\".`` string." -msgstr "" -"String literal is ``\"...\"``. You need to escape ``\"`` in literal by " -"prepending ``\\\\'' such as ``\\\"``. For example, ``\"Say \\\"Hello!\\\"." -"\"`` is a literal for ``Say \"Hello!\".`` string." - -msgid "" -"String encoding must be the same as encoding of database. The default " -"encoding is UTF-8. It can be changed by ``--with-default-encoding`` " -"configure option, ``--encodiong`` :doc:`/reference/executables/groonga` " -"option and so on." -msgstr "" -"String encoding must be the same as encoding of database. The default " -"encoding is UTF-8. It can be changed by ``--with-default-encoding`` " -"configure option, ``--encodiong`` :doc:`/reference/executables/groonga` " -"option and so on." - -msgid "Boolean" -msgstr "Boolean" - -msgid "" -"Boolean literal is ``true`` and ``false``. ``true`` means true and ``false`` " -"means false." -msgstr "" -"Boolean literal is ``true`` and ``false``. ``true`` means true and ``false`` " -"means false." - -msgid "Null" -msgstr "Null" - -msgid "" -"Null literal is ``null``. Groonga doesn't support null value but null " -"literal is supported." -msgstr "" -"Null literal is ``null``. Groonga doesn't support null value but null " -"literal is supported." - -msgid "Time" -msgstr "Time" - -msgid "This is the groonga original notation." -msgstr "This is the groonga original notation." - -msgid "" -"Time literal doesn't exit. There are string time notation, integer time " -"notation and float time notation." -msgstr "" -"Time literal doesn't exit. There are string time notation, integer time " -"notation and float time notation." - -msgid "" -"String time notation is ``\"YYYY/MM/DD hh:mm:ss.uuuuuu\"`` or ``\"YYYY-MM-DD " -"hh:mm:ss.uuuuuu\"``. ``YYYY`` is year, ``MM`` is month, ``DD`` is day, " -"``hh`` is hour, ``mm`` is minute, ``ss`` is second and ``uuuuuu`` is micro " -"second. It is local time. For example, ``\"2012/07/23 02:41:10.436218\"`` is " -"``2012-07-23T02:41:10.436218`` in ISO 8601 format." -msgstr "" -"String time notation is ``\"YYYY/MM/DD hh:mm:ss.uuuuuu\"`` or ``\"YYYY-MM-DD " -"hh:mm:ss.uuuuuu\"``. ``YYYY`` is year, ``MM`` is month, ``DD`` is day, " -"``hh`` is hour, ``mm`` is minute, ``ss`` is second and ``uuuuuu`` is micro " -"second. It is local time. For example, ``\"2012/07/23 02:41:10.436218\"`` is " -"``2012-07-23T02:41:10.436218`` in ISO 8601 format." - -msgid "" -"Integer time notation is the number of seconds that have elapsed since " -"midnight UTC, January 1, 1970. It is also known as POSIX time. For example, " -"``1343011270`` is ``2012-07-23T02:41:10Z`` in ISO 8601 format." -msgstr "" -"Integer time notation is the number of seconds that have elapsed since " -"midnight UTC, January 1, 1970. It is also known as POSIX time. For example, " -"``1343011270`` is ``2012-07-23T02:41:10Z`` in ISO 8601 format." - -msgid "" -"Float time notation is the number of seconds and micro seconds that have " -"elapsed since midnight UTC, January 1, 1970. For example, " -"``1343011270.436218`` is ``2012-07-23T02:41:10.436218Z`` in ISO 8601 format." -msgstr "" -"Float time notation is the number of seconds and micro seconds that have " -"elapsed since midnight UTC, January 1, 1970. For example, " -"``1343011270.436218`` is ``2012-07-23T02:41:10.436218Z`` in ISO 8601 format." - -msgid "Geo point" -msgstr "Geo point" - -msgid "Geo point literal doesn't exist. There is string geo point notation." -msgstr "Geo point literal doesn't exist. There is string geo point notation." - -msgid "String geo point notation has the following patterns:" -msgstr "String geo point notation has the following patterns:" - -msgid "``\"LATITUDE_IN_MSECxLONGITUDE_IN_MSEC\"``" -msgstr "``\"LATITUDE_IN_MSECxLONGITUDE_IN_MSEC\"``" - -msgid "``\"LATITUDE_IN_MSEC,LONGITUDE_IN_MSEC\"``" -msgstr "``\"LATITUDE_IN_MSEC,LONGITUDE_IN_MSEC\"``" - -msgid "``\"LATITUDE_IN_DEGREExLONGITUDE_IN_DEGREE\"``" -msgstr "``\"LATITUDE_IN_DEGREExLONGITUDE_IN_DEGREE\"``" - -msgid "``\"LATITUDE_IN_DEGREE,LONGITUDE_IN_DEGREE\"``" -msgstr "``\"LATITUDE_IN_DEGREE,LONGITUDE_IN_DEGREE\"``" - -msgid "" -"``x`` and ``,`` can be used for separator. Latitude and longitude can be " -"represented in milliseconds or degree." -msgstr "" -"``x`` and ``,`` can be used for separator. Latitude and longitude can be " -"represented in milliseconds or degree." - -msgid "Array" -msgstr "Array" - -msgid "Array literal is ``[element1, element2, ...]``." -msgstr "Array literal is ``[element1, element2, ...]``." - -msgid "Object literal" -msgstr "Object literal" - -msgid "" -"Object literal is ``{name1: value1, name2: value2, ...}``. Groonga doesn't " -"support object literal yet." -msgstr "" -"Object literal is ``{name1: value1, name2: value2, ...}``. Groonga doesn't " -"support object literal yet." - -msgid "Control syntaxes" -msgstr "Control syntaxes" - -msgid "" -"Script syntax doesn't support statement. So you cannot use control statement " -"such as ``if``. You can only use ``A ? B : C`` expression as control syntax." -msgstr "" -"Script syntax doesn't support statement. So you cannot use control statement " -"such as ``if``. You can only use ``A ? B : C`` expression as control syntax." - -msgid "``A ? B : C`` returns ``B`` if ``A`` is true, ``C`` otherwise." -msgstr "``A ? B : C`` returns ``B`` if ``A`` is true, ``C`` otherwise." - -msgid "" -"The expression matches records that ``_id`` column value is equal to ``1`` " -"and ``n_likes`` column value is equal to ``5`` or ``_id`` column value is " -"not equal to 1 and ``n_likes`` column value is equal to ``3``." -msgstr "" -"The expression matches records that ``_id`` column value is equal to ``1`` " -"and ``n_likes`` column value is equal to ``5`` or ``_id`` column value is " -"not equal to 1 and ``n_likes`` column value is equal to ``3``." - -msgid "Its syntax is ``(...)``. ``...`` is comma separated expression list." -msgstr "Its syntax is ``(...)``. ``...`` is comma separated expression list." - -msgid "" -"``(...)`` groups one ore more expressions and they can be processed as an " -"expression. ``a && b || c`` means that ``a`` and ``b`` are matched or ``c`` " -"is matched. ``a && (b || c)`` means that ``a`` and one of ``b`` and ``c`` " -"are matched." -msgstr "" -"``(...)`` groups one ore more expressions and they can be processed as an " -"expression. ``a && b || c`` means that ``a`` and ``b`` are matched or ``c`` " -"is matched. ``a && (b || c)`` means that ``a`` and one of ``b`` and ``c`` " -"are matched." - -msgid "" -"The first expression doesn't use grouping. It matches records that ``n_likes " -"< 5`` and ``content @ \"senna\"`` are matched or ``content @ \"fast\"`` is " -"matched." -msgstr "" -"The first expression doesn't use grouping. It matches records that ``n_likes " -"< 5`` and ``content @ \"senna\"`` are matched or ``content @ \"fast\"`` is " -"matched." - -msgid "" -"The second expression uses grouping. It matches records that ``n_likes < 5`` " -"and one of ``content @ \"senna\"`` or ``content @ \"fast\"`` are matched." -msgstr "" -"The second expression uses grouping. It matches records that ``n_likes < 5`` " -"and one of ``content @ \"senna\"`` or ``content @ \"fast\"`` are matched." - -msgid "Function call" -msgstr "Function call" - -msgid "Its syntax is ``name(arugment1, argument2, ...)``." -msgstr "Its syntax is ``name(arugment1, argument2, ...)``." - -msgid "" -"``name(argument1, argument2, ...)`` calls a function that is named ``name`` " -"with arguments ``argument1``, ``argument2`` and ``...``." -msgstr "" -"``name(argument1, argument2, ...)`` calls a function that is named ``name`` " -"with arguments ``argument1``, ``argument2`` and ``...``." - -msgid "See :doc:`/reference/function` for available functin list." -msgstr "See :doc:`/reference/function` for available functin list." - -msgid "" -"The expression uses :doc:`/reference/functions/edit_distance`. It matches " -"records that ``_key`` column value is similar to ``\"Groonga\"``. Similality " -"of ``\"Groonga\"`` is computed as edit distance. If edit distance is less " -"than or equal to 1, the value is treated as similar. In this case, ``" -"\"Groonga\"`` and ``\"Mroonga\"`` are treated as similar." -msgstr "" -"The expression uses :doc:`/reference/functions/edit_distance`. It matches " -"records that ``_key`` column value is similar to ``\"Groonga\"``. Similality " -"of ``\"Groonga\"`` is computed as edit distance. If edit distance is less " -"than or equal to 1, the value is treated as similar. In this case, ``" -"\"Groonga\"`` and ``\"Mroonga\"`` are treated as similar." - -msgid "Basic operators" -msgstr "Basic operators" - -msgid "Groonga supports operators defined in ECMAScript." -msgstr "Groonga supports operators defined in ECMAScript." - -msgid "Arithmetic operators" -msgstr "Arithmetic operators" - -msgid "Here are arithmetic operators." -msgstr "Here are arithmetic operators." - -msgid "Addition operator" -msgstr "Addition operator" - -msgid "Its syntax is ``number1 + number2``." -msgstr "Its syntax is ``number1 + number2``." - -msgid "The operator adds ``number1`` and ``number2`` and returns the result." -msgstr "The operator adds ``number1`` and ``number2`` and returns the result." - -msgid "" -"The expression matches records that ``n_likes`` column value is equal to " -"``15`` (= ``10 + 5``)." -msgstr "" -"The expression matches records that ``n_likes`` column value is equal to " -"``15`` (= ``10 + 5``)." - -msgid "Subtraction operator" -msgstr "Subtraction operator" - -msgid "Its syntax is ``number1 - number2``." -msgstr "Its syntax is ``number1 - number2``." - -msgid "" -"The operator subtracts ``number2`` from ``number1`` and returns the result." -msgstr "" -"The operator subtracts ``number2`` from ``number1`` and returns the result." - -msgid "" -"The expression matches records that ``n_likes`` column value is equal to " -"``15`` (= ``20 - 5``)." -msgstr "" -"The expression matches records that ``n_likes`` column value is equal to " -"``15`` (= ``20 - 5``)." - -msgid "Multiplication operator" -msgstr "Multiplication operator" - -msgid "Its syntax is ``number1 * number2``." -msgstr "Its syntax is ``number1 * number2``." - -msgid "" -"The operator multiplies ``number1`` and ``number2`` and returns the result." -msgstr "" -"The operator multiplies ``number1`` and ``number2`` and returns the result." - -msgid "" -"The expression matches records that ``n_likes`` column value is equal to " -"``15`` (= ``3 * 5``)." -msgstr "" -"The expression matches records that ``n_likes`` column value is equal to " -"``15`` (= ``3 * 5``)." - -msgid "Division operator" -msgstr "Division operator" - -msgid "Its syntax is ``number1 / number2`` and ``number1 % number2``." -msgstr "Its syntax is ``number1 / number2`` and ``number1 % number2``." - -msgid "" -"The operator divides ``number2`` by ``number1``. ``/`` returns the quotient " -"of result. ``%`` returns the remainder of result." -msgstr "" -"The operator divides ``number2`` by ``number1``. ``/`` returns the quotient " -"of result. ``%`` returns the remainder of result." - -msgid "Here is simple examples." -msgstr "Here is simple examples." - -msgid "" -"The expression matches records that ``n_likes`` column value is equal to " -"``3`` (= ``26 / 7``)." -msgstr "" -"The expression matches records that ``n_likes`` column value is equal to " -"``3`` (= ``26 / 7``)." - -msgid "" -"The expression matches records that ``n_likes`` column value is equal to " -"``5`` (= ``26 % 7``)." -msgstr "" -"The expression matches records that ``n_likes`` column value is equal to " -"``5`` (= ``26 % 7``)." - -msgid "Logical operators" -msgstr "Logical operators" - -msgid "Here are logical operators." -msgstr "Here are logical operators." - -msgid "Logical NOT operator" -msgstr "Logical NOT operator" - -msgid "Its syntax is ``!condition``." -msgstr "Its syntax is ``!condition``." - -msgid "The operator inverts boolean value of ``condition``." -msgstr "The operator inverts boolean value of ``condition``." - -msgid "" -"The expression matches records that ``n_likes`` column value is not equal to " -"``5``." -msgstr "" -"The expression matches records that ``n_likes`` column value is not equal to " -"``5``." - -msgid "Logical AND operator" -msgstr "Logical AND operator" - -msgid "Its syntax is ``condition1 && condition2``." -msgstr "Its syntax is ``condition1 && condition2``." - -msgid "" -"The operator returns true if both of ``condition1`` and ``condition2`` are " -"true, false otherwise." -msgstr "" -"The operator returns true if both of ``condition1`` and ``condition2`` are " -"true, false otherwise." - -msgid "" -"The expression matches records that ``content`` column value has the word " -"``fast`` and ``n_likes`` column value is greater or equal to ``10``." -msgstr "" -"The expression matches records that ``content`` column value has the word " -"``fast`` and ``n_likes`` column value is greater or equal to ``10``." - -msgid "Logical OR operator" -msgstr "Logical OR operator" - -msgid "Its syntax is ``condition1 || condition2``." -msgstr "Its syntax is ``condition1 || condition2``." - -msgid "" -"The operator returns true if either ``condition1`` or ``condition2`` is " -"true, false otherwise." -msgstr "" -"The operator returns true if either ``condition1`` or ``condition2`` is " -"true, false otherwise." - -msgid "" -"The expression matches records that ``n_likes`` column value is equal to " -"``5`` or ``10``." -msgstr "" -"The expression matches records that ``n_likes`` column value is equal to " -"``5`` or ``10``." - -msgid "Logical AND NOT operator" -msgstr "Logical AND NOT operator" - -msgid "Its syntax is ``condition1 &! condition2``." -msgstr "Its syntax is ``condition1 &! condition2``." - -msgid "" -"The operator returns true if ``condition1`` is true but ``condition2`` is " -"false, false otherwise. It returns difference set." -msgstr "" -"The operator returns true if ``condition1`` is true but ``condition2`` is " -"false, false otherwise. It returns difference set." - -msgid "" -"The expression matches records that ``content`` column value has the word " -"``fast`` but doesn't have the word ``mroonga``." -msgstr "" -"The expression matches records that ``content`` column value has the word " -"``fast`` but doesn't have the word ``mroonga``." - -msgid "Bitwise operators" -msgstr "Bitwise operators" - -msgid "Here are bitwise operators." -msgstr "Here are bitwise operators." - -msgid "Bitwise NOT operator" -msgstr "Bitwise NOT operator" - -msgid "Its syntax is ``~number``." -msgstr "Its syntax is ``~number``." - -msgid "The operator returns bitwise NOT of ``number``." -msgstr "The operator returns bitwise NOT of ``number``." - -msgid "" -"The expression matches records that ``n_likes`` column value is equal to " -"``5`` because bitwise NOT of ``5`` is equal to ``-6``." -msgstr "" -"The expression matches records that ``n_likes`` column value is equal to " -"``5`` because bitwise NOT of ``5`` is equal to ``-6``." - -msgid "Bitwise AND operator" -msgstr "Bitwise AND operator" - -msgid "Its syntax is ``number1 & number2``." -msgstr "Its syntax is ``number1 & number2``." - -msgid "The operator returns bitwise AND between ``number1`` and ``number2``." -msgstr "The operator returns bitwise AND between ``number1`` and ``number2``." - -msgid "" -"The expression matches records that ``n_likes`` column value is even number " -"because bitwise AND between an even number and ``1`` is equal to ``1`` and " -"bitwise AND between an odd number and ``1`` is equal to ``0``." -msgstr "" -"The expression matches records that ``n_likes`` column value is even number " -"because bitwise AND between an even number and ``1`` is equal to ``1`` and " -"bitwise AND between an odd number and ``1`` is equal to ``0``." - -msgid "Bitwise OR operator" -msgstr "Bitwise OR operator" - -msgid "Its syntax is ``number1 | number2``." -msgstr "Its syntax is ``number1 | number2``." - -msgid "The operator returns bitwise OR between ``number1`` and ``number2``." -msgstr "The operator returns bitwise OR between ``number1`` and ``number2``." - -msgid "" -"The expression matches records that ``n_likes`` column value is equal to " -"``5`` (= ``1 | 4``)." -msgstr "" -"The expression matches records that ``n_likes`` column value is equal to " -"``5`` (= ``1 | 4``)." - -msgid "Bitwise XOR operator" -msgstr "Bitwise XOR operator" - -msgid "Its syntax is ``number1 ^ number2``." -msgstr "Its syntax is ``number1 ^ number2``." - -msgid "The operator returns bitwise XOR between ``number1`` and ``number2``." -msgstr "The operator returns bitwise XOR between ``number1`` and ``number2``." - -msgid "" -"The expression matches records that ``n_likes`` column value is equal to " -"``5`` (= ``10 ^ 15``)." -msgstr "" -"The expression matches records that ``n_likes`` column value is equal to " -"``5`` (= ``10 ^ 15``)." - -msgid "Shift operators" -msgstr "Shift operators" - -msgid "Here are shift operators." -msgstr "Here are shift operators." - -msgid "Left shift operator" -msgstr "Left shift operator" - -msgid "Its syntax is ``number1 << number2``." -msgstr "Its syntax is ``number1 << number2``." - -msgid "" -"The operator performs a bitwise left shift operation on ``number1`` by " -"``number2``." -msgstr "" -"The operator performs a bitwise left shift operation on ``number1`` by " -"``number2``." - -msgid "" -"The expression matches records that ``n_likes`` column value is equal to " -"``10`` (= ``5 << 1``)." -msgstr "" -"The expression matches records that ``n_likes`` column value is equal to " -"``10`` (= ``5 << 1``)." - -msgid "Signed right shift operator" -msgstr "Signed right shift operator" - -msgid "Its syntax is ``number1 >> number2``." -msgstr "Its syntax is ``number1 >> number2``." - -msgid "" -"The operator shifts bits of ``number1`` to right by ``number2``. The sign of " -"the result is the same as ``number1``." -msgstr "" -"The operator shifts bits of ``number1`` to right by ``number2``. The sign of " -"the result is the same as ``number1``." - -msgid "" -"The expression matches records that ``n_likes`` column value is equal to " -"``5`` (= ``-(-10 >> 1)`` = ``-(-5)``)." -msgstr "" -"The expression matches records that ``n_likes`` column value is equal to " -"``5`` (= ``-(-10 >> 1)`` = ``-(-5)``)." - -msgid "Unsigned right shift operator" -msgstr "Unsigned right shift operator" - -msgid "Its syntax is ``number1 >>> number2``." -msgstr "Its syntax is ``number1 >>> number2``." - -msgid "" -"The operator shifts bits of ``number1`` to right by ``number2``. The " -"leftmost ``number2`` bits are filled by ``0``." -msgstr "" -"The operator shifts bits of ``number1`` to right by ``number2``. The " -"leftmost ``number2`` bits are filled by ``0``." - -msgid "" -"The expression matches records that ``n_likes`` column value is equal to " -"``5`` (= ``2147483648 - (-10 >>> 1)`` = ``2147483648 - 2147483643``)." -msgstr "" -"The expression matches records that ``n_likes`` column value is equal to " -"``5`` (= ``2147483648 - (-10 >>> 1)`` = ``2147483648 - 2147483643``)." - -msgid "Comparison operators" -msgstr "Comparison operators" - -msgid "Here are comparison operators." -msgstr "Here are comparison operators." - -msgid "Equal operator" -msgstr "Equal operator" - -msgid "Its syntax is ``object1 == object2``." -msgstr "Its syntax is ``object1 == object2``." - -msgid "" -"The operator returns true if ``object1`` equals to ``object2``, false " -"otherwise." -msgstr "" -"The operator returns true if ``object1`` equals to ``object2``, false " -"otherwise." - -msgid "" -"The expression matches records that ``n_likes`` column value is equal to " -"``5``." -msgstr "" -"The expression matches records that ``n_likes`` column value is equal to " -"``5``." - -msgid "Not equal operator" -msgstr "Not equal operator" - -msgid "Its syntax is ``object1 != object2``." -msgstr "Its syntax is ``object1 != object2``." - -msgid "" -"The operator returns true if ``object1`` does not equal to ``object2``, " -"false otherwise." -msgstr "" -"The operator returns true if ``object1`` does not equal to ``object2``, " -"false otherwise." - -msgid "Less than operator" -msgstr "Less than operator" - -msgid "TODO: ..." -msgstr "TODO: ..." - -msgid "Less than or equal to operator" -msgstr "Less than or equal to operator" - -msgid "Greater than operator" -msgstr "Greater than operator" - -msgid "Greater than or equal to operator" -msgstr "Greater than or equal to operator" - -msgid "Assignment operators" -msgstr "Assignment operators" - -msgid "Addition assignment operator" -msgstr "Addition assignment operator" - -msgid "Its syntax is ``column1 += column2``." -msgstr "Its syntax is ``column1 += column2``." - -msgid "" -"The operator performs addition assginment operation on column1 by column2." -msgstr "" -"The operator performs addition assginment operation on column1 by column2." - -msgid "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs addition assignment operation such as '_score = _score + n_likes' " -"for each records." -msgstr "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs addition assignment operation such as '_score = _score + n_likes' " -"for each records." - -msgid "" -"For example, the value of ``_score`` about the record which stores \"Good-" -"bye Senna\" as the ``_key`` is 3." -msgstr "" -"For example, the value of ``_score`` about the record which stores \"Good-" -"bye Senna\" as the ``_key`` is 3." - -msgid "" -"So the expression ``1 + 3`` is evaluated and stored to ``_score`` column as " -"the execution result." -msgstr "" -"So the expression ``1 + 3`` is evaluated and stored to ``_score`` column as " -"the execution result." - -msgid "Subtraction assignment operator" -msgstr "Subtraction assignment operator" - -msgid "Its syntax is ``column1 -= column2``." -msgstr "Its syntax is ``column1 -= column2``." - -msgid "" -"The operator performs subtraction assginment operation on column1 by column2." -msgstr "" -"The operator performs subtraction assginment operation on column1 by column2." - -msgid "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs subtraction assignment operation such as '_score = _score - " -"n_likes' for each records." -msgstr "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs subtraction assignment operation such as '_score = _score - " -"n_likes' for each records." - -msgid "" -"So the expression ``1 - 3`` is evaluated and stored to ``_score`` column as " -"the execution result." -msgstr "" -"So the expression ``1 - 3`` is evaluated and stored to ``_score`` column as " -"the execution result." - -msgid "Multiplication assignment operator" -msgstr "Multiplication assignment operator" - -msgid "Its syntax is ``column1 *= column2``." -msgstr "Its syntax is ``column1 *= column2``." - -msgid "" -"The operator performs multiplication assginment operation on column1 by " -"column2." -msgstr "" -"The operator performs multiplication assginment operation on column1 by " -"column2." - -msgid "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs subtraction assignment operation such as '_score = _score * " -"n_likes' for each records." -msgstr "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs subtraction assignment operation such as '_score = _score * " -"n_likes' for each records." - -msgid "" -"So the expression ``1 * 3`` is evaluated and stored to ``_score`` column as " -"the execution result." -msgstr "" -"So the expression ``1 * 3`` is evaluated and stored to ``_score`` column as " -"the execution result." - -msgid "Division assignment operator" -msgstr "Division assignment operator" - -msgid "Its syntax is ``column1 /= column2``." -msgstr "Its syntax is ``column1 /= column2``." - -msgid "" -"The operator performs division assginment operation on column1 by column2." -msgstr "" -"The operator performs division assginment operation on column1 by column2." - -msgid "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs subtraction assignment operation such as '_score = _score / " -"n_likes' for each records." -msgstr "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs subtraction assignment operation such as '_score = _score / " -"n_likes' for each records." - -msgid "" -"So the expression ``1 / 3`` is evaluated and stored to ``_score`` column as " -"the execution result." -msgstr "" -"So the expression ``1 / 3`` is evaluated and stored to ``_score`` column as " -"the execution result." - -msgid "Modulo assignment operator" -msgstr "Modulo assignment operator" - -msgid "Its syntax is ``column1 %= column2``." -msgstr "Its syntax is ``column1 %= column2``." - -msgid "" -"The operator performs modulo assginment operation on column1 by column2." -msgstr "" -"The operator performs modulo assginment operation on column1 by column2." - -msgid "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs subtraction assignment operation such as '_score = _score % " -"n_likes' for each records." -msgstr "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs subtraction assignment operation such as '_score = _score % " -"n_likes' for each records." - -msgid "" -"So the expression ``1 % 3`` is evaluated and stored to ``_score`` column as " -"the execution result." -msgstr "" -"So the expression ``1 % 3`` is evaluated and stored to ``_score`` column as " -"the execution result." - -msgid "Bitwise left shift assignment operator" -msgstr "Bitwise left shift assignment operator" - -msgid "Its syntax is ``column1 <<= column2``." -msgstr "Its syntax is ``column1 <<= column2``." - -msgid "" -"The operator performs left shift assginment operation on column1 by column2." -msgstr "" -"The operator performs left shift assginment operation on column1 by column2." - -msgid "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs subtraction assignment operation such as '_score = _score << " -"n_likes' for each records." -msgstr "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs subtraction assignment operation such as '_score = _score << " -"n_likes' for each records." - -msgid "" -"So the expression ``1 << 3`` is evaluated and stored to ``_score`` column as " -"the execution result." -msgstr "" -"So the expression ``1 << 3`` is evaluated and stored to ``_score`` column as " -"the execution result." - -msgid "Bitwise signed right shift assignment operator" -msgstr "Bitwise signed right shift assignment operator" - -msgid "Its syntax is ``column2 >>= column2``." -msgstr "Its syntax is ``column2 >>= column2``." - -msgid "" -"The operator performs signed right shift assginment operation on column1 by " -"column2." -msgstr "" -"The operator performs signed right shift assginment operation on column1 by " -"column2." - -msgid "Bitwise unsigned right shift assignment operator" -msgstr "Bitwise unsigned right shift assignment operator" - -msgid "Its syntax is ``column1 >>>= column2``." -msgstr "Its syntax is ``column1 >>>= column2``." - -msgid "" -"The operator performs unsigned right shift assginment operation on column1 " -"by column2." -msgstr "" -"The operator performs unsigned right shift assginment operation on column1 " -"by column2." - -msgid "Bitwise AND assignment operator" -msgstr "Bitwise AND assignment operator" - -msgid "Its syntax is ``column1 &= column2``." -msgstr "Its syntax is ``column1 &= column2``." - -msgid "" -"The operator performs bitwise AND assignment operation on column1 by column2." -msgstr "" -"The operator performs bitwise AND assignment operation on column1 by column2." - -msgid "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs subtraction assignment operation such as '_score = _score & " -"n_likes' for each records." -msgstr "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs subtraction assignment operation such as '_score = _score & " -"n_likes' for each records." - -msgid "" -"For example, the value of ``_score`` about the record which stores \"Groonga" -"\" as the ``_key`` is 10." -msgstr "" -"For example, the value of ``_score`` about the record which stores \"Groonga" -"\" as the ``_key`` is 10." - -msgid "" -"So the expression ``1 & 10`` is evaluated and stored to ``_score`` column as " -"the execution result." -msgstr "" -"So the expression ``1 & 10`` is evaluated and stored to ``_score`` column as " -"the execution result." - -msgid "Bitwise OR assignment operator" -msgstr "Bitwise OR assignment operator" - -msgid "Its syntax is ``column1 |= column2``." -msgstr "Its syntax is ``column1 |= column2``." - -msgid "" -"The operator performs bitwise OR assignment operation on column1 by column2." -msgstr "" -"The operator performs bitwise OR assignment operation on column1 by column2." - -msgid "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs subtraction assignment operation such as '_score = _score | " -"n_likes' for each records." -msgstr "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs subtraction assignment operation such as '_score = _score | " -"n_likes' for each records." - -msgid "" -"So the expression ``1 | 10`` is evaluated and stored to ``_score`` column as " -"the execution result." -msgstr "" -"So the expression ``1 | 10`` is evaluated and stored to ``_score`` column as " -"the execution result." - -msgid "Bitwise XOR assignment operator" -msgstr "Bitwise XOR assignment operator" - -msgid "Its syntax is ``column1 ^= column2``." -msgstr "Its syntax is ``column1 ^= column2``." - -msgid "" -"The operator performs bitwise XOR assginment operation on column1 by column2." -msgstr "" -"The operator performs bitwise XOR assginment operation on column1 by column2." - -msgid "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs subtraction assignment operation such as '_score = _score ^ " -"n_likes' for each records." -msgstr "" -"The value of ``_score`` by ``--filter`` is always 1 in this case, then " -"performs subtraction assignment operation such as '_score = _score ^ " -"n_likes' for each records." - -msgid "" -"So the expression ``1 ^ 3`` is evaluated and stored to ``_score`` column as " -"the execution result." -msgstr "" -"So the expression ``1 ^ 3`` is evaluated and stored to ``_score`` column as " -"the execution result." - -msgid "Original operators" -msgstr "Original operators" - -msgid "" -"Script syntax adds the original binary opearators to ECMAScript syntax. They " -"operate search specific operations. They are starts with ``@`` or ``*``." -msgstr "" -"Script syntax adds the original binary opearators to ECMAScript syntax. They " -"operate search specific operations. They are starts with ``@`` or ``*``." - -msgid "Match operator" -msgstr "Match operator" - -msgid "Its syntax is ``column @ value``." -msgstr "Its syntax is ``column @ value``." - -msgid "" -"The operator searches ``value`` by inverted index of ``column``. Normally, " -"full text search is operated but tag search can be operated. Because tag " -"search is also implemented by inverted index." -msgstr "" -"The operator searches ``value`` by inverted index of ``column``. Normally, " -"full text search is operated but tag search can be operated. Because tag " -"search is also implemented by inverted index." - -msgid ":doc:`query_syntax` uses this operator by default." -msgstr ":doc:`query_syntax` uses this operator by default." - -msgid "Prefix search operator" -msgstr "Prefix search operator" - -msgid "Its syntax is ``column @^ value``." -msgstr "Its syntax is ``column @^ value``." - -msgid "" -"The operator does prefix search with ``value``. Prefix search searches " -"records that contain a word that starts with ``value``." -msgstr "" -"The operator does prefix search with ``value``. Prefix search searches " -"records that contain a word that starts with ``value``." - -msgid "Suffix search operator" -msgstr "Suffix search operator" - -msgid "Its syntax is ``column @$ value``." -msgstr "Its syntax is ``column @$ value``." - -msgid "" -"This operator does suffix search with ``value``. Suffix search searches " -"records that contain a word that ends with ``value``." -msgstr "" -"This operator does suffix search with ``value``. Suffix search searches " -"records that contain a word that ends with ``value``." - -msgid "Near search operator" -msgstr "Near search operator" - -msgid "Its syntax is ``column *N \"word1 word2 ...\"``." -msgstr "Its syntax is ``column *N \"word1 word2 ...\"``." - -msgid "" -"The operator does near search with words ``word1 word2 ...``. Near search " -"searches records that contain the words and the words are appeared in the " -"near distance. Near distance is always ``10`` for now. The unit of near " -"distance is the number of characters in N-gram family tokenizers and the " -"number of words in morphological analysis family tokenizers." -msgstr "" -"The operator does near search with words ``word1 word2 ...``. Near search " -"searches records that contain the words and the words are appeared in the " -"near distance. Near distance is always ``10`` for now. The unit of near " -"distance is the number of characters in N-gram family tokenizers and the " -"number of words in morphological analysis family tokenizers." - -msgid "" -"(TODO: Add a description about ``TokenBigram`` doesn't split ASCII only word " -"into tokens. So the unit for ASCII words with ``TokenBigram`` is the number " -"of words even if ``TokenBigram`` is a N-gram family tokenizer.)" -msgstr "" -"(TODO: Add a description about ``TokenBigram`` doesn't split ASCII only word " -"into tokens. So the unit for ASCII words with ``TokenBigram`` is the number " -"of words even if ``TokenBigram`` is a N-gram family tokenizer.)" - -msgid "" -"Note that an index column for full text search must be defined for " -"``column``." -msgstr "" -"Note that an index column for full text search must be defined for " -"``column``." - -msgid "" -"The first expression matches records that contain ``I`` and ``fast`` and the " -"near distance of those words are in 10 words. So the record that its content " -"is ``I also started to use mroonga. It's also very fast! ...`` is matched. " -"The number of words between ``I`` and ``fast`` is just 10." -msgstr "" -"The first expression matches records that contain ``I`` and ``fast`` and the " -"near distance of those words are in 10 words. So the record that its content " -"is ``I also started to use mroonga. It's also very fast! ...`` is matched. " -"The number of words between ``I`` and ``fast`` is just 10." - -msgid "" -"The second expression matches records that contain ``I`` and ``Really`` and " -"the near distance of those words are in 10 words. So the record that its " -"content is ``I also started to use mroonga. It's also very fast! Really fast!" -"`` is not matched. The number of words between ``I`` and ``Really`` is 11." -msgstr "" -"The second expression matches records that contain ``I`` and ``Really`` and " -"the near distance of those words are in 10 words. So the record that its " -"content is ``I also started to use mroonga. It's also very fast! Really fast!" -"`` is not matched. The number of words between ``I`` and ``Really`` is 11." - -msgid "" -"The third expression matches records that contain ``also`` and ``Really`` " -"and the near distance of those words are in 10 words. So the record that its " -"content is ``I also st arted to use mroonga. It's also very fast! Really " -"fast!`` is matched. The number of words between ``also`` and ``Really`` is " -"10." -msgstr "" -"The third expression matches records that contain ``also`` and ``Really`` " -"and the near distance of those words are in 10 words. So the record that its " -"content is ``I also st arted to use mroonga. It's also very fast! Really " -"fast!`` is matched. The number of words between ``also`` and ``Really`` is " -"10." - -msgid "Similar search" -msgstr "Similar search" - -msgid "Its syntax is ``column *S \"document\"``." -msgstr "Its syntax is ``column *S \"document\"``." - -msgid "" -"The operator does similar search with document ``document``. Similar search " -"searches records that have similar content to ``document``." -msgstr "" -"The operator does similar search with document ``document``. Similar search " -"searches records that have similar content to ``document``." - -msgid "" -"The expression matches records that have similar content to ``I migrated all " -"Solr system!``. In this case, records that have ``I migrated all XXX system!" -"`` content are matched." -msgstr "" -"The expression matches records that have similar content to ``I migrated all " -"Solr system!``. In this case, records that have ``I migrated all XXX system!" -"`` content are matched." - -msgid "Term extract operator" -msgstr "Term extract operator" - -msgid "Its syntax is ``_key *T \"document\"``." -msgstr "Its syntax is ``_key *T \"document\"``." - -msgid "" -"The operator extracts terms from ``document``. Terms must be registered as " -"keys of the table of ``_key``." -msgstr "" -"The operator extracts terms from ``document``. Terms must be registered as " -"keys of the table of ``_key``." - -msgid "" -"Note that the table must be patricia trie (``TABLE_PAT_KEY``) or double " -"array trie (``TABLE_DAT_KEY``). You can't use hash table " -"(``TABLE_HASH_KEY``) and array (``TABLE_NO_KEY``) because they don't support " -"longest common prefix search. Longest common prefix search is used to " -"implement the operator." -msgstr "" -"Note that the table must be patricia trie (``TABLE_PAT_KEY``) or double " -"array trie (``TABLE_DAT_KEY``). You can't use hash table " -"(``TABLE_HASH_KEY``) and array (``TABLE_NO_KEY``) because they don't support " -"longest common prefix search. Longest common prefix search is used to " -"implement the operator." - -msgid "" -"The expression extrcts terms that included in document ``Groonga is the " -"successor project to Senna.``. In this case, ``KEY_NORMALIZE`` flag is " -"specified to ``Words``. So ``Groonga`` can be extracted even if it is loaded " -"as ``groonga`` into ``Words``. All of extracted terms are also normalized." -msgstr "" -"The expression extrcts terms that included in document ``Groonga is the " -"successor project to Senna.``. In this case, ``KEY_NORMALIZE`` flag is " -"specified to ``Words``. So ``Groonga`` can be extracted even if it is loaded " -"as ``groonga`` into ``Words``. All of extracted terms are also normalized." - -msgid "Indexing" -msgstr "Indexing" - -msgid "" -"Groonga supports both online index construction and offline index " -"construction since 2.0.0." -msgstr "" -"Groonga supports both online index construction and offline index " -"construction since 2.0.0." - -msgid "Online index construction" -msgstr "Online index construction" - -msgid "" -"In online index construction, registered documents can be searchable quickly " -"while indexing. But indexing requires more cost rather than indexing by " -"offline index construction." -msgstr "" -"In online index construction, registered documents can be searchable quickly " -"while indexing. But indexing requires more cost rather than indexing by " -"offline index construction." - -msgid "" -"Online index construction is suitable for a search system that values " -"freshness. For example, a search system for tweets, news, blog posts and so " -"on will value freshness. Online index construction can make fresh documents " -"searchable and keep searchable while indexing." -msgstr "" -"Online index construction is suitable for a search system that values " -"freshness. For example, a search system for tweets, news, blog posts and so " -"on will value freshness. Online index construction can make fresh documents " -"searchable and keep searchable while indexing." - -msgid "Offline index construction" -msgstr "Offline index construction" - -msgid "" -"In offline index construction, indexing cost is less than indexing cost by " -"online index construction. Indexing time will be shorter. Index will be " -"smaller. Resources required for indexing will be smaller. But a registering " -"document cannot be searchable until all registered documents are indexed." -msgstr "" -"In offline index construction, indexing cost is less than indexing cost by " -"online index construction. Indexing time will be shorter. Index will be " -"smaller. Resources required for indexing will be smaller. But a registering " -"document cannot be searchable until all registered documents are indexed." - -msgid "" -"Offline index construction is suitable for a search system that values less " -"required resources. If a search system doesn't value freshness, offline " -"index construction will be suitable. For example, a reference manual search " -"system doesn't value freshness because a reference manual will be updated " -"only at a release." -msgstr "" -"Offline index construction is suitable for a search system that values less " -"required resources. If a search system doesn't value freshness, offline " -"index construction will be suitable. For example, a reference manual search " -"system doesn't value freshness because a reference manual will be updated " -"only at a release." - -msgid "How to use" -msgstr "How to use" - -msgid "" -"Groonga uses online index construction by default. We register a document, " -"we can search it quickly." -msgstr "" -"Groonga uses online index construction by default. We register a document, " -"we can search it quickly." - -msgid "" -"Groonga uses offline index construction by adding an index to a column that " -"already has data." -msgstr "" -"Groonga uses offline index construction by adding an index to a column that " -"already has data." - -msgid "We define a schema:" -msgstr "We define a schema:" - -msgid "We register data:" -msgstr "We register data:" - -msgid "We search without index. We get no result:" -msgstr "We search without index. We get no result:" - -msgid "" -"We create index for ``Tweets.content``. Already registered data in ``Tweets." -"content`` are indexed by offline index construction:" -msgstr "" -"We create index for ``Tweets.content``. Already registered data in ``Tweets." -"content`` are indexed by offline index construction:" - -msgid "We search with index. We get a matched record:" -msgstr "We search with index. We get a matched record:" - -msgid "We register data again. They are indexed by online index construction:" -msgstr "We register data again. They are indexed by online index construction:" - -msgid "We can also get newly registered records by searching:" -msgstr "We can also get newly registered records by searching:" - -msgid "Log" -msgstr "Log" - -msgid "" -"Groonga has two log files. They are process log and query log. Process log " -"is for all of :doc:`executables/groonga` works. Query log is just for query " -"processing." -msgstr "" -"Groonga has two log files. They are process log and query log. Process log " -"is for all of :doc:`executables/groonga` works. Query log is just for query " -"processing." - -msgid "Process log" -msgstr "Process log" - -msgid "" -"Process log is enabled by default. Log path can be customized by :option:`--" -"log-path` option. Each log has its log level. If a log is smaller than " -"groonga process' log level, it's not logged. Log level can be customized by :" -"option:`-l` or :doc:`commands/log_level`." -msgstr "" -"Process log is enabled by default. Log path can be customized by :option:`--" -"log-path` option. Each log has its log level. If a log is smaller than " -"groonga process' log level, it's not logged. Log level can be customized by :" -"option:`-l` or :doc:`commands/log_level`." - -msgid "Format" -msgstr "Format" - -msgid "Process log uses the following format::" -msgstr "Process log uses the following format::" - -msgid "It's time stamp uses the following format::" -msgstr "It's time stamp uses the following format::" - -msgid "YYYY" -msgstr "YYYY" - -msgid "Year with four digits." -msgstr "Year with four digits." - -msgid "MM" -msgstr "MM" - -msgid "Month with two digits." -msgstr "Month with two digits." - -msgid "DD" -msgstr "DD" - -msgid "Day with two digits." -msgstr "Day with two digits." - -msgid "Hour with two digits." -msgstr "Hour with two digits." - -msgid "hh" -msgstr "hh" - -msgid "Minute with two digits." -msgstr "Minute with two digits." - -msgid "mm" -msgstr "mm" - -msgid "Second with two digits." -msgstr "Second with two digits." - -msgid "ss" -msgstr "ss" - -msgid "Microsecond with six digits." -msgstr "Microsecond with six digits." - -msgid "SSSSSS" -msgstr "SSSSSS" - -msgid "Example::" -msgstr "Example::" - -msgid "TIME_STAMP" -msgstr "TIME_STAMP" - -msgid "Log level with a character. Here is a character and log level map." -msgstr "Log level with a character. Here is a character and log level map." - -msgid "E" -msgstr "E" - -msgid "Emergency" -msgstr "Emergency" - -msgid "A" -msgstr "A" - -msgid "Alert" -msgstr "Alert" - -msgid "C" -msgstr "C" - -msgid "Critical" -msgstr "Critical" - -msgid "Error" -msgstr "Error" - -msgid "e" -msgstr "e" - -msgid "Warning" -msgstr "Warning" - -msgid "w" -msgstr "w" - -msgid "Notification" -msgstr "Notification" - -msgid "Information" -msgstr "Information" - -msgid "Debug" -msgstr "Debug" - -msgid "d" -msgstr "d" - -msgid "Dump" -msgstr "Dump" - -msgid "\\-" -msgstr "\\-" - -msgid "L" -msgstr "L" - -msgid "Details about the log with free format." -msgstr "Details about the log with free format." - -msgid "MESSAGE" -msgstr "MESSAGE" - -msgid "Query log" -msgstr "Query log" - -msgid "" -"Query log is disabled by default. It can be enabled by :option:`--query-log-" -"path` option." -msgstr "" -"Query log is disabled by default. It can be enabled by :option:`--query-log-" -"path` option." - -msgid "Query log uses the following formats::" -msgstr "Query log uses the following formats::" - -msgid "" -"ID of a thread. Groonga process creates threads to process requests " -"concurrently. Each thread outputs some logs for a request. This ID can be " -"used to extract a log sequence by a thread." -msgstr "" -"ID of a thread. Groonga process creates threads to process requests " -"concurrently. Each thread outputs some logs for a request. This ID can be " -"used to extract a log sequence by a thread." - -msgid "ID" -msgstr "ID" - -msgid ">" -msgstr ">" - -msgid "A character that indicates query is started." -msgstr "A character that indicates query is started." - -msgid ":" -msgstr ":" - -msgid "A character that indicates query is processing." -msgstr "A character that indicates query is processing." - -msgid "<" -msgstr "<" - -msgid "A character that indicates query is finished." -msgstr "A character that indicates query is finished." - -msgid "A query to be processed." -msgstr "A query to be processed." - -msgid "QUERY" -msgstr "QUERY" - -msgid "Elapsed time in nanoseconds since query is started." -msgstr "Elapsed time in nanoseconds since query is started." - -msgid "ELAPSED_TIME" -msgstr "ELAPSED_TIME" - -msgid "A processed work at the time." -msgstr "A processed work at the time." - -msgid "PROGRESS" -msgstr "PROGRESS" - -msgid "A return code for the query." -msgstr "A return code for the query." - -msgid "RETURN_CODE" -msgstr "RETURN_CODE" - -msgid "Normalizers" -msgstr "Normalizers" - -msgid "" -"Groonga has normalizer module that normalizes text. It is used when " -"tokenizing text and storing table key. For example, ``A`` and ``a`` are " -"processed as the same character after normalization." -msgstr "" -"Groonga has normalizer module that normalizes text. It is used when " -"tokenizing text and storing table key. For example, ``A`` and ``a`` are " -"processed as the same character after normalization." - -msgid "" -"Normalizer module can be added as a plugin. You can customize text " -"normalization by registering your normalizer plugins to Groonga." -msgstr "" -"Normalizer module can be added as a plugin. You can customize text " -"normalization by registering your normalizer plugins to Groonga." - -msgid "" -"A normalizer module is attached to a table. A table can have zero or one " -"normalizer module. You can attach a normalizer module to a table by :ref:" -"`table-create-normalizer` option in :doc:`/reference/commands/table_create`." -msgstr "" -"A normalizer module is attached to a table. A table can have zero or one " -"normalizer module. You can attach a normalizer module to a table by :ref:" -"`table-create-normalizer` option in :doc:`/reference/commands/table_create`." - -msgid "" -"Here is an example ``table_create`` that uses ``NormalizerAuto`` normalizer " -"module:" -msgstr "" -"Here is an example ``table_create`` that uses ``NormalizerAuto`` normalizer " -"module:" - -msgid "" -"Groonga 2.0.9 or earlier doesn't have ``--normalizer`` option in " -"``table_create``. ``KEY_NORMALIZE`` flag was used instead." -msgstr "" -"Groonga 2.0.9 or earlier doesn't have ``--normalizer`` option in " -"``table_create``. ``KEY_NORMALIZE`` flag was used instead." - -msgid "" -"You can open an old database by Groonga 2.1.0 or later. An old database " -"means that the database is created by Groonga 2.0.9 or earlier. But you " -"cannot open the opened old database by Groonga 2.0.9 or earlier. Once you " -"open the old database by Groonga 2.1.0 or later, ``KEY_NORMALIZE`` flag " -"information in the old database is converted to normalizer information. So " -"Groonga 2.0.9 or earlier cannot find ``KEY_NORMALIZE`` flag information in " -"the opened old database." -msgstr "" -"You can open an old database by Groonga 2.1.0 or later. An old database " -"means that the database is created by Groonga 2.0.9 or earlier. But you " -"cannot open the opened old database by Groonga 2.0.9 or earlier. Once you " -"open the old database by Groonga 2.1.0 or later, ``KEY_NORMALIZE`` flag " -"information in the old database is converted to normalizer information. So " -"Groonga 2.0.9 or earlier cannot find ``KEY_NORMALIZE`` flag information in " -"the opened old database." - -msgid "Keys of a table that has a normalizer module are normalized:" -msgstr "Keys of a table that has a normalizer module are normalized:" - -msgid "" -"``NormalizerAuto`` normalizer normalizes a text as a downcased text. For " -"example, ``\"Apple\"`` is normalized to ``\"apple\"``, ``\"black\"`` is " -"normalized to ``\"blank\"`` and ``\"COLOR\"`` is normalized to ``\"color\"``." -msgstr "" -"``NormalizerAuto`` normalizer normalizes a text as a downcased text. For " -"example, ``\"Apple\"`` is normalized to ``\"apple\"``, ``\"black\"`` is " -"normalized to ``\"blank\"`` and ``\"COLOR\"`` is normalized to ``\"color\"``." - -msgid "" -"If a table is a lexicon for fulltext search, tokenized tokens are " -"normalized. Because tokens are stored as table keys. Table keys are " -"normalized as described above." -msgstr "" -"If a table is a lexicon for fulltext search, tokenized tokens are " -"normalized. Because tokens are stored as table keys. Table keys are " -"normalized as described above." - -msgid "Built-in normalizers" -msgstr "Built-in normalizers" - -msgid "Here is a list of built-in normalizers:" -msgstr "Here is a list of built-in normalizers:" - -msgid "``NormalizerAuto``" -msgstr "``NormalizerAuto``" - -msgid "``NormalizerNFKC51``" -msgstr "``NormalizerNFKC51``" - -msgid "" -"Normally you should use ``NormalizerAuto`` normalizer. ``NormalizerAuto`` " -"was the normalizer for Groonga 2.0.9 or earlier. ``KEY_NORMALIZE`` flag in " -"``table_create`` on Groonga 2.0.9 or earlier equals to ``--normalizer " -"NormalizerAuto`` option in ``table_create`` on Groonga 2.1.0 or later." -msgstr "" -"Normally you should use ``NormalizerAuto`` normalizer. ``NormalizerAuto`` " -"was the normalizer for Groonga 2.0.9 or earlier. ``KEY_NORMALIZE`` flag in " -"``table_create`` on Groonga 2.0.9 or earlier equals to ``--normalizer " -"NormalizerAuto`` option in ``table_create`` on Groonga 2.1.0 or later." - -msgid "" -"``NormalizerAuto`` supports all encoding. It uses Unicode NFKC " -"(Normalization Form Compatibility Composition) for UTF-8 encoding text. It " -"uses encoding specific original normalization for other encodings. The " -"results of those original normalization are similar to NFKC." -msgstr "" -"``NormalizerAuto`` supports all encoding. It uses Unicode NFKC " -"(Normalization Form Compatibility Composition) for UTF-8 encoding text. It " -"uses encoding specific original normalization for other encodings. The " -"results of those original normalization are similar to NFKC." - -msgid "" -"For example, half-width katakana (such as U+FF76 HALFWIDTH KATAKANA LETTER " -"KA) + half-width katakana voiced sound mark (U+FF9E HALFWIDTH KATAKANA " -"VOICED SOUND MARK) is normalized to full-width katakana with voiced sound " -"mark (U+30AC KATAKANA LETTER GA). The former is two chracters but the latter " -"is one character." -msgstr "" -"For example, half-width katakana (such as U+FF76 HALFWIDTH KATAKANA LETTER " -"KA) + half-width katakana voiced sound mark (U+FF9E HALFWIDTH KATAKANA " -"VOICED SOUND MARK) is normalized to full-width katakana with voiced sound " -"mark (U+30AC KATAKANA LETTER GA). The former is two chracters but the latter " -"is one character." - -msgid "Here is an example that uses ``NormalizerAuto`` normalizer:" -msgstr "Here is an example that uses ``NormalizerAuto`` normalizer:" - -msgid "" -"``NormalizerNFKC51`` normalizes texts by Unicode NFKC (Normalization Form " -"Compatibility Composition) for Unicode version 5.1. It supports only UTF-8 " -"encoding." -msgstr "" -"``NormalizerNFKC51`` normalizes texts by Unicode NFKC (Normalization Form " -"Compatibility Composition) for Unicode version 5.1. It supports only UTF-8 " -"encoding." - -msgid "" -"Normally you don't need to use ``NormalizerNFKC51`` explicitly. You can use " -"``NormalizerAuto`` instead." -msgstr "" -"Normally you don't need to use ``NormalizerNFKC51`` explicitly. You can use " -"``NormalizerAuto`` instead." - -msgid "Here is an example that uses ``NormalizerNFKC51`` normalizer:" -msgstr "Here is an example that uses ``NormalizerNFKC51`` normalizer:" - -msgid "Additional normalizers" -msgstr "Additional normalizers" - -msgid "There are additional normalizers:" -msgstr "" - -# f953b55db14f42ea92bf856e22248435 -msgid "" -"`groonga-normalizer-mysql <https://github.com/groonga/groonga-normalizer-" -"mysql>_`" -msgstr "" - -msgid ":doc:`/reference/commands/table_create`" -msgstr ":doc:`/reference/commands/table_create`" - -msgid "Operations" -msgstr "Operations" - -msgid "" -"Groonga has the search feature of multiple. This section describes how to " -"search operations." -msgstr "" -"Groonga has the search feature of multiple. This section describes how to " -"search operations." - -msgid "Geolocation Search" -msgstr "Geolocation Search" - -msgid "" -"Groonga supports geolocation search. It uses index for search. It means that " -"you can search by geolocation fast like fulltext search." -msgstr "" -"Groonga supports geolocation search. It uses index for search. It means that " -"you can search by geolocation fast like fulltext search." - -msgid "Supported features" -msgstr "Supported features" - -msgid "" -"Groonga supports only point as data type. Line, surface and so on aren't " -"supported yet. Here is a feature list:" -msgstr "" -"Groonga supports only point as data type. Line, surface and so on aren't " -"supported yet. Here is a feature list:" - -msgid "Groonga can store a point to a column." -msgstr "Groonga can store a point to a column." - -msgid "" -"Groonga can search records that have a point in the specified rectangle." -msgstr "" -"Groonga can search records that have a point in the specified rectangle." - -msgid "Groonga can search records that have a point in the specified circle." -msgstr "Groonga can search records that have a point in the specified circle." - -msgid "Groonga can calculate distance between two points." -msgstr "Groonga can calculate distance between two points." - -msgid "" -"Groonga can sort records by distance from the specified point in ascending " -"order." -msgstr "" -"Groonga can sort records by distance from the specified point in ascending " -"order." - -msgid "Here are use cases for Groonga's geolocation search:" -msgstr "Here are use cases for Groonga's geolocation search:" - -msgid "You list McDonald's around a station." -msgstr "You list McDonald's around a station." - -msgid "" -"You list KFS around the current location sort by distance from the current " -"location in ascending order with distance." -msgstr "" -"You list KFS around the current location sort by distance from the current " -"location in ascending order with distance." - -msgid "Here are not use cases:" -msgstr "Here are not use cases:" - -msgid "" -"You search McDonald's in a city. (Groonga doesn't support geolocation search " -"by a shape except a rectangle and a circle.)" -msgstr "" -"You search McDonald's in a city. (Groonga doesn't support geolocation search " -"by a shape except a rectangle and a circle.)" - -msgid "" -"You store a region instead of a point as a lake record. (A column can't has " -"geolocation data except a point.)" -msgstr "" -"You store a region instead of a point as a lake record. (A column can't has " -"geolocation data except a point.)" - -msgid "The following figures show about Groonga's geolocation search features." -msgstr "" -"The following figures show about Groonga's geolocation search features." - -msgid "" -"Here is a figure that only has records. A black point describes a record. " -"The following figures shows how records are treated." -msgstr "" -"Here is a figure that only has records. A black point describes a record. " -"The following figures shows how records are treated." - -msgid "Coming soon..." -msgstr "Coming soon..." - -msgid "Output" -msgstr "Output" - -msgid "Groonga supports the following output format types:" -msgstr "Groonga supports the following output format types:" - -msgid "`JSON <http://www.json.org/>`_" -msgstr "`JSON <http://www.json.org/>`_" - -msgid "`XML <http://www.w3.org/XML/>`_" -msgstr "`XML <http://www.w3.org/XML/>`_" - -msgid "TSV (Tab Separated Values)" -msgstr "TSV (Tab Separated Values)" - -msgid "`MessagePack <http://msgpack.org/>`_" -msgstr "`MessagePack <http://msgpack.org/>`_" - -msgid "JSON is the default output format." -msgstr "JSON is the default output format." - -msgid "Groonga has the following query interfaces:" -msgstr "Groonga has the following query interfaces:" - -msgid "command line" -msgstr "command line" - -msgid "HTTP" -msgstr "HTTP" - -msgid "They provides different ways to change output format type." -msgstr "They provides different ways to change output format type." - -msgid "Command line" -msgstr "Command line" - -msgid "" -"You can use command line query interface by ``groonga DB_PATH`` or ``groonga " -"-c``. Those groonga commands shows ``> `` prompt. In this query interface, " -"you can specify output format type by ``output_type`` option." -msgstr "" -"You can use command line query interface by ``groonga DB_PATH`` or ``groonga " -"-c``. Those groonga commands shows ``> `` prompt. In this query interface, " -"you can specify output format type by ``output_type`` option." - -msgid "" -"If you don't specify ``output_type`` option, you will get a result in JSON " -"format::" -msgstr "" -"If you don't specify ``output_type`` option, you will get a result in JSON " -"format::" - -msgid "" -"You can specify ``json`` as ``output_type`` value to get a result in JSON " -"format explicitly::" -msgstr "" -"You can specify ``json`` as ``output_type`` value to get a result in JSON " -"format explicitly::" - -msgid "" -"You need to specify ``xml`` as ``output_type`` value to get a result in XML " -"format::" -msgstr "" -"You need to specify ``xml`` as ``output_type`` value to get a result in XML " -"format::" - -msgid "" -"You need to specify ``tsv`` as ``output_type`` value to get a result in TSV " -"format::" -msgstr "" -"You need to specify ``tsv`` as ``output_type`` value to get a result in TSV " -"format::" - -msgid "" -"You need to specify ``msgpack`` as ``output_type`` value to get a result in " -"MessagePack format::" -msgstr "" -"You need to specify ``msgpack`` as ``output_type`` value to get a result in " -"MessagePack format::" - -msgid "" -"You can use HTTP query interface by ``groonga --protocol http -s DB_PATH``. " -"Groonga HTTP server starts on port 10041 by default. In this query " -"interface, you can specify output format type by extension." -msgstr "" -"You can use HTTP query interface by ``groonga --protocol http -s DB_PATH``. " -"Groonga HTTP server starts on port 10041 by default. In this query " -"interface, you can specify output format type by extension." - -msgid "If you don't specify extension, you will get a result in JSON format::" -msgstr "If you don't specify extension, you will get a result in JSON format::" - -msgid "" -"You can specify ``json`` as extension to get a result in JSON format " -"explicitly::" -msgstr "" -"You can specify ``json`` as extension to get a result in JSON format " -"explicitly::" - -msgid "" -"You need to specify ``xml`` as extension to get a result in XML format::" -msgstr "" -"You need to specify ``xml`` as extension to get a result in XML format::" - -msgid "" -"You need to specify ``tsv`` as extension to get a result in TSV format::" -msgstr "" -"You need to specify ``tsv`` as extension to get a result in TSV format::" - -msgid "" -"You need to specify ``msgpack`` as extension to get a result in MessagePack " -"format::" -msgstr "" -"You need to specify ``msgpack`` as extension to get a result in MessagePack " -"format::" - -msgid "Query expanders" -msgstr "Query expanders" - -msgid "QueryExpanderTSV" -msgstr "QueryExpanderTSV" - -msgid "" -"``QueryExpanderTSV`` is a query expander plugin that reads synonyms from TSV " -"(Tab Separated Values) file. This plugin provides poor feature than the " -"embedded query expansion feature. For example, it doesn't support word " -"normalization. But it may be easy to use because you can manage your " -"synonyms by TSV file. You can edit your synonyms by spreadsheet application " -"such as Excel. With the embedded query expansion feature, you manage your " -"synonyms by Groonga's table." -msgstr "" -"``QueryExpanderTSV`` is a query expander plugin that reads synonyms from TSV " -"(Tab Separated Values) file. This plugin provides poor feature than the " -"embedded query expansion feature. For example, it doesn't support word " -"normalization. But it may be easy to use because you can manage your " -"synonyms by TSV file. You can edit your synonyms by spreadsheet application " -"such as Excel. With the embedded query expansion feature, you manage your " -"synonyms by Groonga's table." - -msgid "Install" -msgstr "Install" - -msgid "" -"You need to register ``query_expanders/tsv`` as a plugin before you use " -"``QueryExpanderTSV``::" -msgstr "" -"You need to register ``query_expanders/tsv`` as a plugin before you use " -"``QueryExpanderTSV``::" - -msgid "" -"You just add ``--query_expansion QueryExpanderTSV`` parameter to ``select`` " -"command::" -msgstr "" -"You just add ``--query_expansion QueryExpanderTSV`` parameter to ``select`` " -"command::" - -msgid "" -"If ``QUERY`` has registered synonyms, they are expanded. For example, there " -"are the following synonyms." -msgstr "" -"If ``QUERY`` has registered synonyms, they are expanded. For example, there " -"are the following synonyms." - -msgid "synonym 1" -msgstr "synonym 1" - -msgid "synonym 2" -msgstr "synonym 2" - -msgid "word" -msgstr "word" - -msgid "Senna" -msgstr "Senna" - -msgid "groonga" -msgstr "groonga" - -msgid "groonga MySQL" -msgstr "groonga MySQL" - -msgid "mroonga" -msgstr "mroonga" - -msgid "" -"The table means that ``synonym 1`` and ``synonym 2`` are synonyms of " -"``word``. For example, ``groonga`` and ``Senna`` are synonyms of " -"``groonga``. And ``mroonga`` and ``groonga MySQL`` are synonyms of " -"``mroonga``." -msgstr "" -"The table means that ``synonym 1`` and ``synonym 2`` are synonyms of " -"``word``. For example, ``groonga`` and ``Senna`` are synonyms of " -"``groonga``. And ``mroonga`` and ``groonga MySQL`` are synonyms of " -"``mroonga``." - -msgid "Here is an example of query expnasion that uses ``groonga`` as query::" -msgstr "Here is an example of query expnasion that uses ``groonga`` as query::" - -msgid "The above command equals to the following command::" -msgstr "The above command equals to the following command::" - -msgid "" -"Here is another example of query expnasion that uses ``mroonga search`` as " -"query::" -msgstr "" -"Here is another example of query expnasion that uses ``mroonga search`` as " -"query::" - -msgid "" -"It is important that registered words (``groonga`` and ``mroonga``) are only " -"expanded to synonyms and not registered words (``search``) are not expanded. " -"Query expansion isn't occurred recursively. ``groonga`` is appeared in " -"``(mroonga OR (groonga MySQL))`` as query expansion result but it isn't " -"expanded." -msgstr "" -"It is important that registered words (``groonga`` and ``mroonga``) are only " -"expanded to synonyms and not registered words (``search``) are not expanded. " -"Query expansion isn't occurred recursively. ``groonga`` is appeared in " -"``(mroonga OR (groonga MySQL))`` as query expansion result but it isn't " -"expanded." - -msgid "" -"Normally, you need to include ``word`` itself into synonyms. For example, " -"``groonga`` and ``mroonga`` are included in synonyms of themselves. If you " -"want to ignore ``word`` itself, you don't include ``word`` itself into " -"synonyms. For example, if you want to use query expansion as spelling " -"correction, you should use the following synonyms." -msgstr "" -"Normally, you need to include ``word`` itself into synonyms. For example, " -"``groonga`` and ``mroonga`` are included in synonyms of themselves. If you " -"want to ignore ``word`` itself, you don't include ``word`` itself into " -"synonyms. For example, if you want to use query expansion as spelling " -"correction, you should use the following synonyms." - -msgid "synonym" -msgstr "synonym" - -msgid "gronga" -msgstr "gronga" - -msgid "" -"``gronga`` in ``word`` has a typo. A ``o`` is missing. ``groonga`` in " -"``synonym`` is the correct word." -msgstr "" -"``gronga`` in ``word`` has a typo. A ``o`` is missing. ``groonga`` in " -"``synonym`` is the correct word." - -msgid "Here is an example of using query expnasion as spelling correction::" -msgstr "Here is an example of using query expnasion as spelling correction::" - -msgid "" -"The former command has a typo in ``--query`` value but the latter command " -"doesn't have any typos." -msgstr "" -"The former command has a typo in ``--query`` value but the latter command " -"doesn't have any typos." - -msgid "TSV File" -msgstr "TSV File" - -msgid "" -"Synonyms are defined in TSV format file. This section describes about it." -msgstr "" -"Synonyms are defined in TSV format file. This section describes about it." - -msgid "Location" -msgstr "Location" - -msgid "" -"The file name should be ``synonyms.tsv`` and it is located at configuration " -"directory. For example, ``/etc/groonga/synonyms.tsv`` is a TSV file " -"location. The location is decided at build time." -msgstr "" -"The file name should be ``synonyms.tsv`` and it is located at configuration " -"directory. For example, ``/etc/groonga/synonyms.tsv`` is a TSV file " -"location. The location is decided at build time." - -msgid "" -"You can change the location by environment variable " -"``GRN_QUERY_EXPANDER_TSV_SYNONYMS_FILE`` at run time::" -msgstr "" -"You can change the location by environment variable " -"``GRN_QUERY_EXPANDER_TSV_SYNONYMS_FILE`` at run time::" - -msgid "With the above command, ``/tmp/synonyms.tsv`` file is used." -msgstr "With the above command, ``/tmp/synonyms.tsv`` file is used." - -msgid "" -"You can define zero or more synonyms in a TSV file. You define a ``word`` " -"and ``synonyms`` pair by a line. ``word`` is expanded to ``synonyms`` in ``--" -"query`` value. ``Synonyms`` are combined by ``OR``. For example, ``groonga`` " -"and ``Senna`` synonyms are expanded as ``groonga OR Senna``." -msgstr "" -"You can define zero or more synonyms in a TSV file. You define a ``word`` " -"and ``synonyms`` pair by a line. ``word`` is expanded to ``synonyms`` in ``--" -"query`` value. ``Synonyms`` are combined by ``OR``. For example, ``groonga`` " -"and ``Senna`` synonyms are expanded as ``groonga OR Senna``." - -msgid "" -"The first column is ``word`` and the rest columns are ``synonyms`` of the " -"``word``. Here is a sample line for ``word`` is ``groonga`` and ``synonyms`` " -"are ``groonga`` and ``Senna``. ``(TAB)`` means a tab character (``U+0009``)::" -msgstr "" -"The first column is ``word`` and the rest columns are ``synonyms`` of the " -"``word``. Here is a sample line for ``word`` is ``groonga`` and ``synonyms`` " -"are ``groonga`` and ``Senna``. ``(TAB)`` means a tab character (``U+0009``)::" - -msgid "" -"Comment line is supported. Lines that start with ``#`` are ignored. Here is " -"an example for comment line. ``groonga`` line is ignored as comment line::" -msgstr "" -"Comment line is supported. Lines that start with ``#`` are ignored. Here is " -"an example for comment line. ``groonga`` line is ignored as comment line::" - -msgid "Limitation" -msgstr "Limitation" - -msgid "" -"You need to restart groonga to reload your synonyms. TSV file is loaded only " -"at the plugin load time." -msgstr "" -"You need to restart groonga to reload your synonyms. TSV file is loaded only " -"at the plugin load time." - -msgid ":ref:`query-expansion`" -msgstr ":ref:`query-expansion`" - -msgid "Suggest" -msgstr "Suggest" - -msgid "" -"Groonga has the suggest feature. This section describes how to use it and " -"how it works." -msgstr "" -"Groonga has the suggest feature. This section describes how to use it and " -"how it works." - -msgid "Completion" -msgstr "Completion" - -msgid "This section describes about the following completion features:" -msgstr "This section describes about the following completion features:" - -msgid "How it works" -msgstr "How it works" - -msgid "How to learn" -msgstr "How to learn" - -msgid "The completion feature uses three searches to compute completed words:" -msgstr "The completion feature uses three searches to compute completed words:" - -msgid "Prefix RK search against registered words." -msgstr "Prefix RK search against registered words." - -msgid "Cooccurrence search against learned data." -msgstr "Cooccurrence search against learned data." - -msgid "Prefix search against registered words. (optional)" -msgstr "Prefix search against registered words. (optional)" - -msgid "Prefix RK search" -msgstr "Prefix RK search" - -msgid "" -"RK means Romaji and Katakana. Prefix RK search can find registered words " -"that start with user's input by romaji, katakana or hiragana. It's useful " -"for searching in Japanese." -msgstr "" -"RK means Romaji and Katakana. Prefix RK search can find registered words " -"that start with user's input by romaji, katakana or hiragana. It's useful " -"for searching in Japanese." - -msgid "" -"For example, there is a registered word \"日本\". And \"ニホン\" (it must be " -"katakana) is registered as its reading. An user can find \"日本\" by \"ni\", " -"\"二\" or \"に\"." -msgstr "" -"For example, there is a registered word \"日本\". And \"ニホン\" (it must be " -"katakana) is registered as its reading. An user can find \"日本\" by \"ni\", " -"\"二\" or \"に\"." - -msgid "" -"If you create dataset which is named as ``example`` by :doc:`/reference/" -"executables/groonga-suggest-create-dataset` executable file, you can update " -"pairs of registered word and its reading by loading data to ``_key`` and " -"``kana`` column of ``item_example`` table explicitly for prefix RK search." -msgstr "" - -msgid "Cooccurrence search" -msgstr "Cooccurrence search" - -msgid "" -"Cooccurrence search can find registered words from user's partial input. It " -"uses user input sequences that will be learned from query logs, access logs " -"and so on." -msgstr "" -"Cooccurrence search can find registered words from user's partial input. It " -"uses user input sequences that will be learned from query logs, access logs " -"and so on." - -msgid "For example, there is the following user input sequence:" -msgstr "For example, there is the following user input sequence:" - -msgid "input" -msgstr "input" - -msgid "submit" -msgstr "submit" - -msgid "no" -msgstr "no" - -msgid "se" -msgstr "se" - -msgid "sea" -msgstr "sea" - -msgid "sear" -msgstr "sear" - -msgid "searc" -msgstr "searc" - -msgid "search" -msgstr "search" - -msgid "yes" -msgstr "yes" - -msgid "en" -msgstr "en" - -msgid "eng" -msgstr "eng" - -msgid "engi" -msgstr "engi" - -msgid "engin" -msgstr "engin" - -msgid "engine" -msgstr "engine" - -msgid "enginen" -msgstr "enginen" - -msgid "no (typo!)" -msgstr "no (typo!)" - -msgid "Groonga creates the following completion pairs:" -msgstr "Groonga creates the following completion pairs:" - -msgid "completed word" -msgstr "completed word" - -msgid "" -"All user not-submitted inputs (e.g. \"s\", \"se\" and so on) before each an " -"user submission maps to the submitted input (e.g. \"search\")." -msgstr "" -"All user not-submitted inputs (e.g. \"s\", \"se\" and so on) before each an " -"user submission maps to the submitted input (e.g. \"search\")." - -msgid "" -"To be precise, this description isn't correct because it omits about time " -"stamp. Groonga doesn't case about \"all user not-submitted inputs before " -"each an user submission\". Groonga just case about \"all user not-submitted " -"inputs within a minute from an user submission before each an user submission" -"\". Groonga doesn't treat user inputs before a minute ago." -msgstr "" -"To be precise, this description isn't correct because it omits about time " -"stamp. Groonga doesn't case about \"all user not-submitted inputs before " -"each an user submission\". Groonga just case about \"all user not-submitted " -"inputs within a minute from an user submission before each an user submission" -"\". Groonga doesn't treat user inputs before a minute ago." - -msgid "" -"If an user inputs \"sea\" and cooccurrence search returns \"search\" because " -"\"sea\" is in input column and corresponding completed word column value is " -"\"search\"." -msgstr "" -"If an user inputs \"sea\" and cooccurrence search returns \"search\" because " -"\"sea\" is in input column and corresponding completed word column value is " -"\"search\"." - -msgid "Prefix search" -msgstr "Prefix search" - -msgid "" -"Prefix search can find registered word that start with user's input. This " -"search doesn't care about romaji, katakana and hiragana not like prefix RK " -"search." -msgstr "" - -msgid "" -"This search isn't always ran. It's just ran when it's requested explicitly " -"or both prefix RK search and cooccurrence search return nothing." -msgstr "" -"This search isn't always ran. It's just ran when it's requested explicitly " -"or both prefix RK search and cooccurrence search return nothing." - -msgid "" -"For example, there is a registered word \"search\". An user can find \"search" -"\" by \"s\", \"se\", \"sea\", \"sear\", \"searc\" and \"search\"." -msgstr "" -"For example, there is a registered word \"search\". An user can find \"search" -"\" by \"s\", \"se\", \"sea\", \"sear\", \"searc\" and \"search\"." - -msgid "" -"Groonga provides :doc:`/reference/commands/suggest` command to use " -"completion. ``--type complete`` option requests completion." -msgstr "" - -msgid "For example, here is an command to get completion results by \"en\":" -msgstr "For example, here is an command to get completion results by \"en\":" - -msgid "How it learns" -msgstr "How it learns" - -msgid "" -"Cooccurrence search uses learned data. They are based on query logs, access " -"logs and so on. To create learned data, Groonga needs user input sequence " -"with time stamp and user submit input with time stamp." -msgstr "" - -msgid "" -"For example, an user wants to search by \"engine\". The user inputs the " -"query with the following sequence:" -msgstr "" -"For example, an user wants to search by \"engine\". The user inputs the " -"query with the following sequence:" - -msgid "2011-08-10T13:33:23+09:00: e" -msgstr "2011-08-10T13:33:23+09:00: e" - -msgid "2011-08-10T13:33:23+09:00: en" -msgstr "2011-08-10T13:33:23+09:00: en" - -msgid "2011-08-10T13:33:24+09:00: eng" -msgstr "2011-08-10T13:33:24+09:00: eng" - -msgid "2011-08-10T13:33:24+09:00: engi" -msgstr "2011-08-10T13:33:24+09:00: engi" - -msgid "2011-08-10T13:33:24+09:00: engin" -msgstr "2011-08-10T13:33:24+09:00: engin" - -msgid "2011-08-10T13:33:25+09:00: engine (submit!)" -msgstr "2011-08-10T13:33:25+09:00: engine (submit!)" - -msgid "" -"Groonga can be learned from the input sequence by the following command::" -msgstr "" -"Groonga can be learned from the input sequence by the following command::" - -msgid "How to update reading data" -msgstr "" - -msgid "" -"Groonga requires registered word and its reading for prefix RK search. This " -"section describes how to register a word and its reading." -msgstr "" - -msgid "Here is an example to register \"日本\" which means Japan in English:" -msgstr "" - -msgid "Here is an example to update reading data to complete \"日本\":" -msgstr "" - -msgid "" -"Then you can complete registered word \"日本\" by Romaji input - \"nihon\"." -msgstr "" - -msgid "" -"Without loading above reading data, you can't complete registered word \"日本" -"\" by query - \"nihon\"." -msgstr "" - -# 7b9c3e64f6624637802f8aba5a79b13b -msgid "" -"You can register multiple readings for a registered word because ``kana`` " -"column in ``item_query`` table is defined as a :doc:`/reference/columns/" -"vector`." -msgstr "" - -msgid "" -"This is the reason that you can also complete the registered word \"日本\" " -"by query - \"nippon\"." -msgstr "" -"This is the reason that you can also complete the registered word \"日本\" " -"by query - \"nippon\"." - -msgid "" -"This feature is very convenient because you can search registered word even " -"though Japanese input method is disabled." -msgstr "" - -msgid "" -"If there are multiple candidates as completed result, you can customize " -"priority to set the value of ``boost`` column in ``item_query`` table." -msgstr "" - -msgid "Here is an example to customize priority for prefix RK search:" -msgstr "" - -msgid "Correction" -msgstr "Correction" - -msgid "This section describes about the following correction features:" -msgstr "This section describes about the following correction features:" - -msgid "The correction feature uses three searches to compute corrected words:" -msgstr "The correction feature uses three searches to compute corrected words:" - -msgid "Similar search against registered words. (optional)" -msgstr "Similar search against registered words. (optional)" - -msgid "" -"Cooccurrence search can find registered words from user's wrong input. It " -"uses user submit sequences that will be learned from query logs, access logs " -"and so on." -msgstr "" -"Cooccurrence search can find registered words from user's wrong input. It " -"uses user submit sequences that will be learned from query logs, access logs " -"and so on." - -msgid "For example, there are the following user submissions:" -msgstr "For example, there are the following user submissions:" - -msgid "time" -msgstr "time" - -msgid "2011-08-10T22:20:50+09:00" -msgstr "2011-08-10T22:20:50+09:00" - -msgid "serach (typo!)" -msgstr "serach (typo!)" - -msgid "2011-08-10T22:20:52+09:00" -msgstr "2011-08-10T22:20:52+09:00" - -msgid "search (fixed!)" -msgstr "search (fixed!)" - -msgid "" -"Groonga creates the following correction pair from the above submissions:" -msgstr "" -"Groonga creates the following correction pair from the above submissions:" - -msgid "corrected word" -msgstr "corrected word" - -msgid "serach" -msgstr "serach" - -msgid "" -"Groonga treats continuous submissions within a minute as input correction by " -"user. Not submitted user input sequence between two submissions isn't used " -"as learned data for correction." -msgstr "" -"Groonga treats continuous submissions within a minute as input correction by " -"user. Not submitted user input sequence between two submissions isn't used " -"as learned data for correction." - -msgid "" -"If an user inputs \"serach\" and cooccurrence search returns \"search\" " -"because \"serach\" is in input column and corresponding corrected word " -"column value is \"search\"." -msgstr "" -"If an user inputs \"serach\" and cooccurrence search returns \"search\" " -"because \"serach\" is in input column and corresponding corrected word " -"column value is \"search\"." - -msgid "" -"Similar search can find registered words that has one or more the same " -"tokens as user input. TokenBigram tokenizer is used for tokenization because " -"suggest dataset schema created by :doc:`/reference/executables/groonga-" -"suggest-create-dataset` uses TokenBigram tokenizer as the default tokenizer." -msgstr "" -"Similar search can find registered words that has one or more the same " -"tokens as user input. TokenBigram tokenizer is used for tokenization because " -"suggest dataset schema created by :doc:`/reference/executables/groonga-" -"suggest-create-dataset` uses TokenBigram tokenizer as the default tokenizer." - -msgid "" -"For example, there is a registered query \"search engine\". An user can find " -"\"search engine\" by \"web search service\", \"sound engine\" and so on. " -"Because \"search engine\" and \"web search engine\" have the same token " -"\"search\" and \"search engine\" and \"sound engine\" have the same token " -"\"engine\"." -msgstr "" -"For example, there is a registered query \"search engine\". An user can find " -"\"search engine\" by \"web search service\", \"sound engine\" and so on. " -"Because \"search engine\" and \"web search engine\" have the same token " -"\"search\" and \"search engine\" and \"sound engine\" have the same token " -"\"engine\"." - -msgid "" -"\"search engine\" is tokenized to \"search\" and \"engine\" tokens. " -"(Groonga's TokenBigram tokenizer doesn't tokenize two characters for " -"continuous alphabets and continuous digits for reducing search noise. " -"TokenBigramSplitSymbolAlphaDigit tokenizer should be used to ensure " -"tokenizing to two characters.) \"web search service\" is tokenized to \"web" -"\", \"search\" and \"service\". \"sound engine\" is tokenized to \"sound\" " -"and \"engine\"." -msgstr "" -"\"search engine\" is tokenized to \"search\" and \"engine\" tokens. " -"(Groonga's TokenBigram tokenizer doesn't tokenize two characters for " -"continuous alphabets and continuous digits for reducing search noise. " -"TokenBigramSplitSymbolAlphaDigit tokenizer should be used to ensure " -"tokenizing to two characters.) \"web search service\" is tokenized to \"web" -"\", \"search\" and \"service\". \"sound engine\" is tokenized to \"sound\" " -"and \"engine\"." - -msgid "" -"Groonga provides :doc:`/reference/commands/suggest` command to use " -"correction. `--type correct` option requests corrections." -msgstr "" -"Groonga provides :doc:`/reference/commands/suggest` command to use " -"correction. `--type correct` option requests corrections." - -msgid "" -"For example, here is an command to get correction results by \"saerch\":" -msgstr "" -"For example, here is an command to get correction results by \"saerch\":" - -msgid "" -"Cooccurrence search uses learned data. They are based on query logs, access " -"logs and so on. To create learned data, groonga needs user submit inputs " -"with time stamp." -msgstr "" -"Cooccurrence search uses learned data. They are based on query logs, access " -"logs and so on. To create learned data, groonga needs user submit inputs " -"with time stamp." - -msgid "" -"For example, an user wants to search by \"search\" but the user has typo " -"\"saerch\" before inputs the correct query. The user inputs the query with " -"the following sequence:" -msgstr "" -"For example, an user wants to search by \"search\" but the user has typo " -"\"saerch\" before inputs the correct query. The user inputs the query with " -"the following sequence:" - -msgid "2011-08-10T13:33:23+09:00: s" -msgstr "2011-08-10T13:33:23+09:00: s" - -msgid "2011-08-10T13:33:23+09:00: sa" -msgstr "2011-08-10T13:33:23+09:00: sa" - -msgid "2011-08-10T13:33:24+09:00: sae" -msgstr "2011-08-10T13:33:24+09:00: sae" - -msgid "2011-08-10T13:33:24+09:00: saer" -msgstr "2011-08-10T13:33:24+09:00: saer" - -msgid "2011-08-10T13:33:24+09:00: saerc" -msgstr "2011-08-10T13:33:24+09:00: saerc" - -msgid "2011-08-10T13:33:25+09:00: saerch (submit!)" -msgstr "2011-08-10T13:33:25+09:00: saerch (submit!)" - -msgid "2011-08-10T13:33:29+09:00: serch (correcting...)" -msgstr "2011-08-10T13:33:29+09:00: serch (correcting...)" - -msgid "2011-08-10T13:33:30+09:00: search (submit!)" -msgstr "2011-08-10T13:33:30+09:00: search (submit!)" - -msgid "Introduction" -msgstr "Introduction" - -msgid "The suggest feature in Groonga provides the following features:" -msgstr "The suggest feature in Groonga provides the following features:" - -msgid "Suggestion" -msgstr "Suggestion" - -msgid "" -"Completion helps user input. If user inputs a partial word, Groonga can " -"return complete words from registered words." -msgstr "" -"Completion helps user input. If user inputs a partial word, Groonga can " -"return complete words from registered words." - -msgid "For example, there are registered words:" -msgstr "For example, there are registered words:" - -msgid "\"groonga\"" -msgstr "\"groonga\"" - -msgid "\"complete\"" -msgstr "\"complete\"" - -msgid "\"correction\"" -msgstr "\"correction\"" - -msgid "\"suggest\"" -msgstr "\"suggest\"" - -msgid "" -"An user inputs \"co\" and groonga returns \"complete\" and \"correction\" " -"because they starts with \"co\"." -msgstr "" -"An user inputs \"co\" and groonga returns \"complete\" and \"correction\" " -"because they starts with \"co\"." - -msgid "" -"An user inputs \"sug\" and groonga returns \"suggest\" because \"suggest\" " -"starts with \"sug\"." -msgstr "" -"An user inputs \"sug\" and groonga returns \"suggest\" because \"suggest\" " -"starts with \"sug\"." - -msgid "" -"An user inputs \"ab\" and groonga returns nothing because no word starts " -"with \"ab\"." -msgstr "" -"An user inputs \"ab\" and groonga returns nothing because no word starts " -"with \"ab\"." - -msgid "" -"Correction also helps user input. If user inputs a wrong word, groonga can " -"return correct words from registered correction pairs." -msgstr "" -"Correction also helps user input. If user inputs a wrong word, groonga can " -"return correct words from registered correction pairs." - -msgid "For example, there are registered correction pairs:" -msgstr "For example, there are registered correction pairs:" - -msgid "correct word" -msgstr "correct word" - -msgid "wrong word" -msgstr "wrong word" - -msgid "grroonga" -msgstr "grroonga" - -msgid "gronnga" -msgstr "gronnga" - -msgid "" -"An user inputs \"gronga\" and groonga returns \"groonga\" because \"gronga\" " -"is in wrong word and corresponding correct word is \"groonga\"." -msgstr "" -"An user inputs \"gronga\" and groonga returns \"groonga\" because \"gronga\" " -"is in wrong word and corresponding correct word is \"groonga\"." - -msgid "" -"An user inputs \"roonga\" and groonga returns nothing because \"roonga\" " -"isn't in wrong word." -msgstr "" -"An user inputs \"roonga\" and groonga returns nothing because \"roonga\" " -"isn't in wrong word." - -msgid "" -"Suggestion helps that user filters many found documents. If user inputs a " -"query, groonga can return new queries that has more additional keywords from " -"registered related query pairs." -msgstr "" -"Suggestion helps that user filters many found documents. If user inputs a " -"query, groonga can return new queries that has more additional keywords from " -"registered related query pairs." - -msgid "For example, there are registered related query pairs:" -msgstr "For example, there are registered related query pairs:" - -msgid "keyword" -msgstr "keyword" - -msgid "related query" -msgstr "related query" - -msgid "groonga search engine" -msgstr "groonga search engine" - -msgid "Google search" -msgstr "Google search" - -msgid "groonga speed" -msgstr "groonga speed" - -msgid "speed" -msgstr "speed" - -msgid "" -"An user inputs \"groonga\" and groonga returns \"groonga search engine\" " -"because \"groonga\" is in keyword column and related query column is " -"\"groonga search engine\"." -msgstr "" -"An user inputs \"groonga\" and groonga returns \"groonga search engine\" " -"because \"groonga\" is in keyword column and related query column is " -"\"groonga search engine\"." - -msgid "" -"An user inputs \"MySQL\" and groonga returns nothing because \"MySQL\" isn't " -"in keyword column values." -msgstr "" -"An user inputs \"MySQL\" and groonga returns nothing because \"MySQL\" isn't " -"in keyword column values." - -msgid "Learning" -msgstr "Learning" - -msgid "" -"The suggest feature requires registered data before using the feature. Those " -"data can be registered from user inputs. Gronnga-suggest-httpd and groonga-" -"suggest-learner commands are provided for the propose." -msgstr "" -"The suggest feature requires registered data before using the feature. Those " -"data can be registered from user inputs. Gronnga-suggest-httpd and groonga-" -"suggest-learner commands are provided for the propose." - -msgid "The suggestion feature uses a search to compute suggested words:" -msgstr "The suggestion feature uses a search to compute suggested words:" - -msgid "" -"Cooccurrence search can find related words from user's input. It uses user " -"submissions that will be learned from query logs, access logs and so on." -msgstr "" -"Cooccurrence search can find related words from user's input. It uses user " -"submissions that will be learned from query logs, access logs and so on." - -msgid "search engine" -msgstr "search engine" - -msgid "web search realtime" -msgstr "web search realtime" - -msgid "Groonga creates the following suggestion pairs:" -msgstr "Groonga creates the following suggestion pairs:" - -msgid "suggested words" -msgstr "suggested words" - -msgid "web" -msgstr "web" - -msgid "realtime" -msgstr "realtime" - -msgid "Those pairs are created by the following steps:" -msgstr "Those pairs are created by the following steps:" - -msgid "" -"Tokenizes user input query by TokenDelimit tokenizer that uses a space as " -"token delimiter. (e.g. \"search engine\" is tokenized to two tokens \"search" -"\" and \"engine\".)" -msgstr "" -"Tokenizes user input query by TokenDelimit tokenizer that uses a space as " -"token delimiter. (e.g. \"search engine\" is tokenized to two tokens \"search" -"\" and \"engine\".)" - -msgid "" -"Creates a pair that is consists of a token and original query for each token." -msgstr "" -"Creates a pair that is consists of a token and original query for each token." - -msgid "" -"If an user inputs \"search\" and cooccurrence search returns \"search engine" -"\" and \"web search realtime\" because \"search\" is in two input columns " -"and corresponding suggested word columns have \"search engine\" and \"web " -"search realtime\"." -msgstr "" -"If an user inputs \"search\" and cooccurrence search returns \"search engine" -"\" and \"web search realtime\" because \"search\" is in two input columns " -"and corresponding suggested word columns have \"search engine\" and \"web " -"search realtime\"." - -msgid "" -"Groonga provides :doc:`/reference/commands/suggest` command to use " -"suggestion. `--type suggest` option requests suggestion" -msgstr "" -"Groonga provides :doc:`/reference/commands/suggest` command to use " -"suggestion. `--type suggest` option requests suggestion" - -msgid "" -"For example, here is an command to get suggestion results by \"search\":" -msgstr "" -"For example, here is an command to get suggestion results by \"search\":" - -msgid "" -"Cooccurrence search uses learned data. They are based on query logs, access " -"logs and so on. To create learned data, groonga needs user input sequence " -"with time stamp and user submit input with time stamp." -msgstr "" -"Cooccurrence search uses learned data. They are based on query logs, access " -"logs and so on. To create learned data, groonga needs user input sequence " -"with time stamp and user submit input with time stamp." - -msgid "2011-08-10T13:33:23+09:00: search engine (submit)" -msgstr "2011-08-10T13:33:23+09:00: search engine (submit)" - -msgid "2011-08-10T13:33:28+09:00: web search realtime (submit)" -msgstr "2011-08-10T13:33:28+09:00: web search realtime (submit)" - -msgid "Groonga can be learned from the submissions by the following command::" -msgstr "Groonga can be learned from the submissions by the following command::" - -msgid "How to extract learning data" -msgstr "How to extract learning data" - -msgid "" -"The learning data is stored into item_DATASET and pair_DATASET tables. By " -"using select command for such tables, you can all extract learing data." -msgstr "" -"The learning data is stored into item_DATASET and pair_DATASET tables. By " -"using select command for such tables, you can all extract learing data." - -msgid "Here is the query to extract all learning data::" -msgstr "Here is the query to extract all learning data::" - -msgid "" -"Without '--limit -1', you can't get all data. In pair table, the valid value " -"of freq0, freq1 and freq2 column must be larger than 0." -msgstr "" -"Without '--limit -1', you can't get all data. In pair table, the valid value " -"of freq0, freq1 and freq2 column must be larger than 0." - -msgid "" -"Don't execute above query via HTTP request because enourmous number of " -"records are fetched." -msgstr "" -"Don't execute above query via HTTP request because enourmous number of " -"records are fetched." - -msgid "Tables" -msgstr "Tables" - -msgid "" -"Table in Groonga manages relation between ID and key. Groonga provides four " -"table types. They are ``TABLE_NO_KEY``, ``TABLE_HASH_KEY``, " -"``TABLE_PAT_KEY`` and ``TABLE_DAT_KEY``." -msgstr "" -"Table in Groonga manages relation between ID and key. Groonga provides four " -"table types. They are ``TABLE_NO_KEY``, ``TABLE_HASH_KEY``, " -"``TABLE_PAT_KEY`` and ``TABLE_DAT_KEY``." - -msgid "" -"All tables except ``TABLE_NO_KEY`` provides both fast ID search by key and " -"fast key search by ID. ``TABLE_NO_KEY`` doesn't support key. " -"``TABLE_NO_KEY`` only manages ID. So ``TABLE_NO_KEY`` doesn't provides ID " -"search and key search." -msgstr "" -"All tables except ``TABLE_NO_KEY`` provides both fast ID search by key and " -"fast key search by ID. ``TABLE_NO_KEY`` doesn't support key. " -"``TABLE_NO_KEY`` only manages ID. So ``TABLE_NO_KEY`` doesn't provides ID " -"search and key search." - -msgid "Characteristics" -msgstr "Characteristics" - -msgid "" -"Here is a chracteristic table of all tables in Groonga. (``TABLE_`` prefix " -"is omitted in the table.)" -msgstr "" -"Here is a chracteristic table of all tables in Groonga. (``TABLE_`` prefix " -"is omitted in the table.)" - -msgid "``DAT_KEY``" -msgstr "``DAT_KEY``" - -msgid "``HASH_KEY``" -msgstr "``HASH_KEY``" - -msgid "``NO_KEY``" -msgstr "``NO_KEY``" - -msgid "``PAT_KEY``" -msgstr "``PAT_KEY``" - -msgid "Data structure" -msgstr "Data structure" - -msgid "Double array trie" -msgstr "Double array trie" - -msgid "Hash table" -msgstr "Hash table" - -msgid "Patricia trie" -msgstr "Patricia trie" - -msgid "ID support" -msgstr "ID support" - -msgid "o" -msgstr "o" - -msgid "Key support" -msgstr "Key support" - -msgid "x" -msgstr "x" - -msgid "Value support" -msgstr "Value support" - -msgid "Key -> ID speed" -msgstr "Key -> ID speed" - -msgid "oo" -msgstr "oo" - -msgid "o: fast" -msgstr "o: fast" - -msgid "x: slow" -msgstr "x: slow" - -msgid "Update speed" -msgstr "Update speed" - -msgid "ooo" -msgstr "ooo" - -msgid "Size" -msgstr "Size" - -msgid "o: small" -msgstr "o: small" - -msgid "x: large" -msgstr "x: large" - -msgid "Key update" -msgstr "Key update" - -msgid "Common prefix search" -msgstr "Common prefix search" - -msgid "Predictive search" -msgstr "Predictive search" - -msgid "Range search" -msgstr "Range search" - -msgid "" -"``TABLE_NO_KEY`` is very fast and very small but it doesn't support key. " -"``TABLE_NO_KEY`` is a only table that doesn't support key." -msgstr "" -"``TABLE_NO_KEY`` is very fast and very small but it doesn't support key. " -"``TABLE_NO_KEY`` is a only table that doesn't support key." - -msgid "" -"You cannot use ``TABLE_NO_KEY`` for lexicon for fulltext search because " -"lexicon stores tokens as key. ``TABLE_NO_KEY`` is useful for no key records " -"such as log." -msgstr "" -"You cannot use ``TABLE_NO_KEY`` for lexicon for fulltext search because " -"lexicon stores tokens as key. ``TABLE_NO_KEY`` is useful for no key records " -"such as log." - -msgid "" -"``TABLE_HASH_KEY`` is fast but it doesn't support advanced search functions " -"such as common prefix search and predictive search." -msgstr "" -"``TABLE_HASH_KEY`` is fast but it doesn't support advanced search functions " -"such as common prefix search and predictive search." - -msgid "" -"``TABLE_HASH_KEY`` is useful for index for exact search such as tag search." -msgstr "" -"``TABLE_HASH_KEY`` is useful for index for exact search such as tag search." - -msgid "``TABLE_PAT_KEY`` is small and supports advanced search functions." -msgstr "``TABLE_PAT_KEY`` is small and supports advanced search functions." - -msgid "" -"``TABLE_PAT_KEY`` is useful for lexicon for fulltext search and index for " -"range search." -msgstr "" -"``TABLE_PAT_KEY`` is useful for lexicon for fulltext search and index for " -"range search." - -msgid "" -"``TABLE_DAT_KEY`` is fast and supports key update but it is large. It is not " -"suitable for storing many records. ``TABLE_DAT_KEY`` is a only table that " -"supports key update." -msgstr "" -"``TABLE_DAT_KEY`` is fast and supports key update but it is large. It is not " -"suitable for storing many records. ``TABLE_DAT_KEY`` is a only table that " -"supports key update." - -msgid "" -"``TABLE_DAT_KEY`` is used in Groonga database. Groonga database needs to " -"convert object name such as ``ShortText``, ``TokenBigram`` and table names " -"to object ID. And Groonga database needs to rename object name. Those " -"features are implemented by ``TABLE_DAT_KEY``. The number of objects is " -"small. So large data size demerit of ``TABLE_DAT_KEY`` can be ignored." -msgstr "" -"``TABLE_DAT_KEY`` is used in Groonga database. Groonga database needs to " -"convert object name such as ``ShortText``, ``TokenBigram`` and table names " -"to object ID. And Groonga database needs to rename object name. Those " -"features are implemented by ``TABLE_DAT_KEY``. The number of objects is " -"small. So large data size demerit of ``TABLE_DAT_KEY`` can be ignored." - -msgid "Record ID" -msgstr "Record ID" - -msgid "Record ID is assigned automatically. You cannot assign record ID." -msgstr "Record ID is assigned automatically. You cannot assign record ID." - -msgid "Record ID of deleted record may be reused." -msgstr "Record ID of deleted record may be reused." - -msgid "" -"Valid record ID range is between 1 and 268435455. (1 and 268435455 are valid " -"IDs.)" -msgstr "" -"Valid record ID range is between 1 and 268435455. (1 and 268435455 are valid " -"IDs.)" - -msgid "Persistent table and temporary table" -msgstr "Persistent table and temporary table" - -msgid "Table is persistent table or temporary table." -msgstr "Table is persistent table or temporary table." - -msgid "Persistent table" -msgstr "Persistent table" - -msgid "" -"Persistent table is named and registered to database. Records in persistent " -"table aren't deleted after closing table or database." -msgstr "" -"Persistent table is named and registered to database. Records in persistent " -"table aren't deleted after closing table or database." - -msgid "" -"Persistent table can be created by :doc:`/reference/commands/table_create` " -"command." -msgstr "" -"Persistent table can be created by :doc:`/reference/commands/table_create` " -"command." - -msgid "Temporary table" -msgstr "Temporary table" - -msgid "" -"Temporary table is anonymous. Records in temporary table are deleted after " -"closing table. Temporary table is used to store search result, sort result, " -"group (drilldown) result and so on. ``TABLE_HASH_KEY`` is used for search " -"result and group result. ``TABLE_NO_KEY`` is used for sort result." -msgstr "" -"Temporary table is anonymous. Records in temporary table are deleted after " -"closing table. Temporary table is used to store search result, sort result, " -"group (drilldown) result and so on. ``TABLE_HASH_KEY`` is used for search " -"result and group result. ``TABLE_NO_KEY`` is used for sort result." - -msgid "" -"The max number of records is 268435455. You cannot add 268435456 or more " -"records in a table." -msgstr "" -"The max number of records is 268435455. You cannot add 268435456 or more " -"records in a table." - -msgid "" -"The max number of a key size is 4096byte. You cannot use 4097byte or larger " -"key. You can use column instead of key for 4097byte or larger size data. " -"``Text`` and ``LargeText`` types supports 4097byte or larger size data." -msgstr "" -"The max number of a key size is 4096byte. You cannot use 4097byte or larger " -"key. You can use column instead of key for 4097byte or larger size data. " -"``Text`` and ``LargeText`` types supports 4097byte or larger size data." - -msgid "" -"The max number of total key size is 4GiB. You need to split a table, split a " -"database (sharding) or reduce each key size to handle 4GiB or more larger " -"total key size." -msgstr "" -"The max number of total key size is 4GiB. You need to split a table, split a " -"database (sharding) or reduce each key size to handle 4GiB or more larger " -"total key size." - -msgid "Token filters" -msgstr "Token filters" - -msgid "Groonga has token filter module that some processes tokenized token." -msgstr "Groonga has token filter module that some processes tokenized token." - -msgid "Token filter module can be added as a plugin." -msgstr "Token filter module can be added as a plugin." - -msgid "" -"You can customize tokenized token by registering your token filters plugins " -"to Groonga." -msgstr "" -"You can customize tokenized token by registering your token filters plugins " -"to Groonga." - -msgid "" -"A table can have zero or more token filters. You can attach token filters to " -"a table by :ref:`table-create-token-filters` option in :doc:`/reference/" -"commands/table_create`." -msgstr "" - -msgid "" -"Here is an example ``table_create`` that uses ``TokenFilterStopWord`` token " -"filter module:" -msgstr "" -"Here is an example ``table_create`` that uses ``TokenFilterStopWord`` token " -"filter module:" - -msgid "Available token filters" -msgstr "Available token filters" - -msgid "Here is the list of available token filters:" -msgstr "" - -msgid "``TokenFilterStopWord``" -msgstr "" - -msgid "``TokenFilterStem``" -msgstr "" - -msgid "" -"``TokenFilterStopWord`` removes stop words from tokenized token in searching " -"the documents." -msgstr "" - -msgid "" -"``TokenFilterStopWord`` can specify stop word after adding the documents " -"because it removes token in searching the documents." -msgstr "" - -msgid "The stop word is specified ``is_stop_word`` column on lexicon table." -msgstr "" - -msgid "Here is an example that uses ``TokenFilterStopWord`` token filter:" -msgstr "Here is an example that uses ``TokenFilterStopWord`` token filter:" - -msgid "``and`` token is marked as stop word in ``Terms`` table." -msgstr "" - -msgid "" -"``\"Hello\"`` that doesn't have ``and`` in content is matched. Because " -"``and`` is a stop word and ``and`` is removed from query." -msgstr "" - -msgid "``TokenFilterStem`` stems tokenized token." -msgstr "" - -msgid "Here is an example that uses ``TokenFilterStem`` token filter:" -msgstr "Here is an example that uses ``TokenFilterStem`` token filter:" - -msgid "" -"All of ``develop``, ``developing``, ``developed`` and ``develops`` tokens " -"are stemmed as ``develop``. So we can find ``develop``, ``developing`` and " -"``developed`` by ``develops`` query." -msgstr "" - -msgid "Tokenizers" -msgstr "Tokenizers" - -msgid "TODO: Write me." -msgstr "TODO: Write me." - -msgid "Here are the list of built-in tokenizers:" -msgstr "Here are the list of built-in tokenizers:" - -msgid "TokenBigram" -msgstr "TokenBigram" - -msgid "TokenBigramSplitSymbol" -msgstr "TokenBigramSplitSymbol" - -msgid "TokenBigramSplitSymbolAlpha" -msgstr "TokenBigramSplitSymbolAlpha" - -msgid "TokenBigramSplitSymbolAlphaDigit" -msgstr "TokenBigramSplitSymbolAlphaDigit" - -msgid "TokenBigramIgnoreBlank" -msgstr "TokenBigramIgnoreBlank" - -msgid "TokenBigramIgnoreBlankSplitSymbol" -msgstr "TokenBigramIgnoreBlankSplitSymbol" - -msgid "TokenBigramIgnoreBlankSplitAlpha" -msgstr "TokenBigramIgnoreBlankSplitAlpha" - -msgid "TokenBigramIgnoreBlankSplitAlphaDigit" -msgstr "TokenBigramIgnoreBlankSplitAlphaDigit" - -msgid "TokenDelimit" -msgstr "TokenDelimit" - -msgid "TokenDelimitNull" -msgstr "TokenDelimitNull" - -msgid "TokenTrigram" -msgstr "TokenTrigram" - -msgid "TokenUnigram" -msgstr "TokenUnigram" - -msgid "TokenMecab" -msgstr "" - -msgid "Tuning" -msgstr "Tuning" - -msgid "" -"There are some tuning parameters for improving Groonga performance or " -"handling a large database." -msgstr "" -"There are some tuning parameters for improving Groonga performance or " -"handling a large database." - -msgid "This section describes parameters." -msgstr "This section describes parameters." - -msgid "The max number of open files per process" -msgstr "The max number of open files per process" - -msgid "This parameter is for handling a large database." -msgstr "This parameter is for handling a large database." - -msgid "" -"Groonga creates one or more files per table and colum. If your database has " -"many tables and columns, groonga process needs to open many files." -msgstr "" -"Groonga creates one or more files per table and colum. If your database has " -"many tables and columns, groonga process needs to open many files." - -msgid "" -"System limits the max number of open files per process. So you need to relax " -"the limitation." -msgstr "" -"System limits the max number of open files per process. So you need to relax " -"the limitation." - -msgid "" -"Here is an expression that compute how many files are opened by groonga::" -msgstr "" -"Here is an expression that compute how many files are opened by groonga::" - -msgid "Here is an example schema::" -msgstr "Here is an example schema::" - -msgid "This example opens at least 11 files::" -msgstr "This example opens at least 11 files::" - -msgid "Memory usage" -msgstr "Memory usage" - -msgid "" -"Groonga maps database files onto memory and accesses to them. Groonga " -"doesn't maps unnecessary files onto memory until they are nneded." -msgstr "" -"Groonga maps database files onto memory and accesses to them. Groonga " -"doesn't maps unnecessary files onto memory until they are nneded." - -msgid "" -"If you access to all data in database, all database files are mapped onto " -"memory. If total size of your database files is 6GiB, your groonga process " -"uses 6GiB memory." -msgstr "" -"If you access to all data in database, all database files are mapped onto " -"memory. If total size of your database files is 6GiB, your groonga process " -"uses 6GiB memory." - -msgid "" -"Normally, your all database files aren't mapped onto memry. But is may be " -"occurred. It is an example case that you dump your database." -msgstr "" -"Normally, your all database files aren't mapped onto memry. But is may be " -"occurred. It is an example case that you dump your database." - -msgid "You must have memory and swap that is larger than database." -msgstr "You must have memory and swap that is larger than database." - -msgid "Linux" -msgstr "Linux" - -msgid "This section describes how to configure parameters on Linux." -msgstr "This section describes how to configure parameters on Linux." - -msgid "nofile" -msgstr "nofile" - -msgid "" -"You can relax the :ref:`tuning-max-n-open-files` parameter by creating a " -"configuration file ``/etc/security/limits.d/groonga.conf`` that has the " -"following content::" -msgstr "" -"You can relax the :ref:`tuning-max-n-open-files` parameter by creating a " -"configuration file ``/etc/security/limits.d/groonga.conf`` that has the " -"following content::" - -msgid "" -"If you run ``groonga`` process by ``groonga`` user and your groonga process " -"needs to open less than 10000 files, use the following configuration::" -msgstr "" -"If you run ``groonga`` process by ``groonga`` user and your groonga process " -"needs to open less than 10000 files, use the following configuration::" - -msgid "" -"The configuration is applied after your groonga service is restarted or re-" -"login as your groonga user." -msgstr "" -"The configuration is applied after your groonga service is restarted or re-" -"login as your groonga user." - -msgid "vm.overcommit_memory" -msgstr "vm.overcommit_memory" - -msgid "" -"This is :ref:`tuning-memory-usage` related parameter. You can handle a " -"database that is larger than your memory and swap by setting ``vm." -"overcommit_memory`` kernel parameter to 1. 1 means that Groonga can always " -"map database files onto memory. It is no problem until groonga touch mapped " -"database files that their size is larger than memory and swap. Groonga " -"recommends the configuration." -msgstr "" -"This is :ref:`tuning-memory-usage` related parameter. You can handle a " -"database that is larger than your memory and swap by setting ``vm." -"overcommit_memory`` kernel parameter to 1. 1 means that Groonga can always " -"map database files onto memory. It is no problem until groonga touch mapped " -"database files that their size is larger than memory and swap. Groonga " -"recommends the configuration." - -msgid "" -"See `Linux kernel documentation about overcommit <https://www.kernel.org/doc/" -"Documentation/vm/overcommit-accounting>`_ about ``vm.overcommit_memory`` " -"parameter details." -msgstr "" -"See `Linux kernel documentation about overcommit <https://www.kernel.org/doc/" -"Documentation/vm/overcommit-accounting>`_ about ``vm.overcommit_memory`` " -"parameter details." - -msgid "" -"You can set the configuration by putting a configuration file ``/etc/sysctl." -"d/groonga.conf`` that has the following content::" -msgstr "" -"You can set the configuration by putting a configuration file ``/etc/sysctl." -"d/groonga.conf`` that has the following content::" - -msgid "" -"The configuration can be applied by restarting your system or run the " -"following command::" -msgstr "" -"The configuration can be applied by restarting your system or run the " -"following command::" - -msgid "vm.max_map_count" -msgstr "vm.max_map_count" - -msgid "" -"This is :ref:`tuning-memory-usage` related parameter. You can handle a 16GiB " -"or more larger size database by increasing ``vm.max_map_count`` kernel " -"parameter. The parameter limits the max number of memory maps." -msgstr "" -"This is :ref:`tuning-memory-usage` related parameter. You can handle a 16GiB " -"or more larger size database by increasing ``vm.max_map_count`` kernel " -"parameter. The parameter limits the max number of memory maps." - -msgid "" -"The default value of the kernel parameter may be 65530 or 65536. Groonga " -"maps 256KiB memory chunk at one time. If a database is larger than 16GiB, " -"groonga reaches the limitation. (``256KiB * 65536 = 16GiB``)" -msgstr "" -"The default value of the kernel parameter may be 65530 or 65536. Groonga " -"maps 256KiB memory chunk at one time. If a database is larger than 16GiB, " -"groonga reaches the limitation. (``256KiB * 65536 = 16GiB``)" - -msgid "" -"You needs to increase the value of the kernel parameter to handle 16GiB or " -"more larger size database. For example, you can handle almost 32GiB size " -"database by ``65536 * 2 = 131072``. You can set the configuration by putting " -"a configuration file ``/etc/sysctl.d/groonga.conf`` that has the following " -"content::" -msgstr "" -"You needs to increase the value of the kernel parameter to handle 16GiB or " -"more larger size database. For example, you can handle almost 32GiB size " -"database by ``65536 * 2 = 131072``. You can set the configuration by putting " -"a configuration file ``/etc/sysctl.d/groonga.conf`` that has the following " -"content::" - -msgid "" -"Note that your real confiugration file will be the following because you " -"already have ``vm.overcommit_memory`` configuration::" -msgstr "" -"Note that your real confiugration file will be the following because you " -"already have ``vm.overcommit_memory`` configuration::" - -msgid "FreeBSD" -msgstr "FreeBSD" - -msgid "This section describes how to configure parameters on FreeBSD." -msgstr "This section describes how to configure parameters on FreeBSD." - -msgid "kern.maxfileperproc" -msgstr "kern.maxfileperproc" - -msgid "データ型" -msgstr "データ型" - -msgid "Groonga データ型" -msgstr "Groonga データ型" - -msgid "Groonga は、格納するデータの型を区別します。" -msgstr "Groonga は、格納するデータの型を区別します。" - -msgid "" -"Groongaのデータベースでは、テーブルの主キーや、カラムの値はいずれも何らかの型" -"に属します。また通常は、一つのテーブルの中の全てのレコードについて、カラムの" -"値は共通となります。" -msgstr "" -"Groongaのデータベースでは、テーブルの主キーや、カラムの値はいずれも何らかの型" -"に属します。また通常は、一つのテーブルの中の全てのレコードについて、カラムの" -"値は共通となります。" - -msgid "" -"主キーの型とカラムの型には、Groongaで予め定義済みの型か、ユーザが定義する型、" -"またはユーザが定義したテーブルを指定することができます。" -msgstr "" -"主キーの型とカラムの型には、Groongaで予め定義済みの型か、ユーザが定義する型、" -"またはユーザが定義したテーブルを指定することができます。" - -msgid "" -"主キーの型に他のテーブルを指定する場合は、そのテーブルは、主キーの型となる" -"テーブルのサブセットとなります。" -msgstr "" -"主キーの型に他のテーブルを指定する場合は、そのテーブルは、主キーの型となる" -"テーブルのサブセットとなります。" - -msgid "" -"カラムの型に他のテーブルを指定する場合は、そのカラムは、カラムの型となるテー" -"ブルの参照キーとなります。" -msgstr "" -"カラムの型に他のテーブルを指定する場合は、そのカラムは、カラムの型となるテー" -"ブルの参照キーとなります。" - -msgid "組込型" -msgstr "組込型" - -msgid "以下の型が組込型としてあらかじめ定義されています。" -msgstr "以下の型が組込型としてあらかじめ定義されています。" - -msgid "``Object``" -msgstr "``Object``" - -msgid "任意のテーブルに属する全てのレコードです。 [#]_" -msgstr "任意のテーブルに属する全てのレコードです。 [#]_" - -msgid "``Bool``" -msgstr "``Bool``" - -msgid "" -"ブーリアン型やブール型などと呼ばれる型であり、真偽値を表します。取り得る値は" -"trueとfalseです。（デフォルト値: false）" -msgstr "" -"ブーリアン型やブール型などと呼ばれる型であり、真偽値を表します。取り得る値は" -"trueとfalseです。（デフォルト値: false）" - -msgid "" -":doc:`/reference/commands/load` コマンドで値を格納するときは、false、0、空文" -"字列のいずれかを指定するとfalseになり、それ以外を指定するとtrueになります。" -msgstr "" -":doc:`/reference/commands/load` コマンドで値を格納するときは、false、0、空文" -"字列のいずれかを指定するとfalseになり、それ以外を指定するとtrueになります。" - -msgid "``Int8``" -msgstr "``Int8``" - -msgid "" -"8bit符号付き整数であり、-128以上127以下の整数を表します。（デフォルト値: 0）" -msgstr "" -"8bit符号付き整数であり、-128以上127以下の整数を表します。（デフォルト値: 0）" - -msgid "``UInt8``" -msgstr "``UInt8``" - -msgid "" -"8bit符号なし整数であり、0以上255以下の整数を表します。（デフォルト値: 0）" -msgstr "" -"8bit符号なし整数であり、0以上255以下の整数を表します。（デフォルト値: 0）" - -msgid "``Int16``" -msgstr "``Int16``" - -msgid "" -"16bit符号付き整数であり、-32,768以上32,767以下の整数を表します。（デフォルト" -"値: 0）" -msgstr "" -"16bit符号付き整数であり、-32,768以上32,767以下の整数を表します。（デフォルト" -"値: 0）" - -msgid "``UInt16``" -msgstr "``UInt16``" - -msgid "" -"16bit符号なし整数であり、0以上65,535以下の整数を表します。（デフォルト値: 0）" -msgstr "" -"16bit符号なし整数であり、0以上65,535以下の整数を表します。（デフォルト値: 0）" - -msgid "``Int32``" -msgstr "``Int32``" - -msgid "" -"32bit符号付き整数であり、-2,147,483,648以上2,147,483,647以下の整数を表しま" -"す。（デフォルト値: 0）" -msgstr "" -"32bit符号付き整数であり、-2,147,483,648以上2,147,483,647以下の整数を表しま" -"す。（デフォルト値: 0）" - -msgid "``UInt32``" -msgstr "``UInt32``" - -msgid "" -"32bit符号なし整数であり、0以上4,294,967,295以下の整数を表します。（デフォルト" -"値: 0）" -msgstr "" -"32bit符号なし整数であり、0以上4,294,967,295以下の整数を表します。（デフォルト" -"値: 0）" - -msgid "``Int64``" -msgstr "``Int64``" - -msgid "" -"64bit符号付き整数であり、-9,223,372,036,854,775,808以上" -"9,223,372,036,854,775,807以下の整数を表します。（デフォルト値: 0）" -msgstr "" -"64bit符号付き整数であり、-9,223,372,036,854,775,808以上" -"9,223,372,036,854,775,807以下の整数を表します。（デフォルト値: 0）" - -msgid "``UInt64``" -msgstr "``UInt64``" - -msgid "" -"64bit符号なし整数であり、0以上18,446,744,073,709,551,615以下の整数を表しま" -"す。（デフォルト値: 0）" -msgstr "" -"64bit符号なし整数であり、0以上18,446,744,073,709,551,615以下の整数を表しま" -"す。（デフォルト値: 0）" - -msgid "``Float``" -msgstr "``Float``" - -msgid "" -"IEEE 754形式の倍精度浮動小数点数であり、実数を表します。（デフォルト値: 0.0）" -msgstr "" -"IEEE 754形式の倍精度浮動小数点数であり、実数を表します。（デフォルト値: 0.0）" - -msgid "" -"IEEE 754形式の詳細については、 `IEEE 754 - Wikipedia <http://ja.wikipedia." -"org/wiki/IEEE_754>`_ や `IEEE 754: Standard for Binary Floating-Point " -"<http://grouper.ieee.org/groups/754/>`_ を参照してください。" -msgstr "" -"IEEE 754形式の詳細については、 `IEEE 754 - Wikipedia <http://ja.wikipedia." -"org/wiki/IEEE_754>`_ や `IEEE 754: Standard for Binary Floating-Point " -"<http://grouper.ieee.org/groups/754/>`_ を参照してください。" - -msgid "``Time``" -msgstr "``Time``" - -msgid "" -"日時を表す型であり、1970年1月1日0時0分0秒からの経過時間を、マイクロ秒単位で" -"64bit符号付き整数により表現します。（デフォルト値: 0）" -msgstr "" -"日時を表す型であり、1970年1月1日0時0分0秒からの経過時間を、マイクロ秒単位で" -"64bit符号付き整数により表現します。（デフォルト値: 0）" - -msgid "" -":doc:`/reference/commands/load` コマンドで値を格納するときは、1970年1月1日0時" -"0分0秒からの経過秒数を指定します。秒単位より詳細な日時を指定するには、小数を" -"使います。" -msgstr "" -":doc:`/reference/commands/load` コマンドで値を格納するときは、1970年1月1日0時" -"0分0秒からの経過秒数を指定します。秒単位より詳細な日時を指定するには、小数を" -"使います。" - -msgid "``ShortText``" -msgstr "``ShortText``" - -msgid "4,095バイト以下の文字列を表します。（デフォルト値: \"\"）" -msgstr "4,095バイト以下の文字列を表します。（デフォルト値: \"\"）" - -msgid "``Text``" -msgstr "``Text``" - -msgid "65,535バイト以下の文字列を表します。（デフォルト値: \"\"）" -msgstr "65,535バイト以下の文字列を表します。（デフォルト値: \"\"）" - -msgid "``LongText``" -msgstr "``LongText``" - -msgid "2,147,483,647バイト以下の文字列を表します。（デフォルト値: \"\"）" -msgstr "2,147,483,647バイト以下の文字列を表します。（デフォルト値: \"\"）" - -msgid "``TokyoGeoPoint``" -msgstr "``TokyoGeoPoint``" - -msgid "" -"旧日本測地系による経緯度であり、経度と緯度をミリ秒単位で表現した整数の組によ" -"り表現します。（デフォルト値: 0x0）" -msgstr "" -"旧日本測地系による経緯度であり、経度と緯度をミリ秒単位で表現した整数の組によ" -"り表現します。（デフォルト値: 0x0）" - -msgid "" -"度分秒形式でx度y分z秒となる経度・緯度は、(((x * 60) + y) * 60 + z) * 1000とい" -"う計算式でミリ秒単位へと変換されます。 :doc:`/reference/commands/load` コマン" -"ドで値を格納するときは、\"ミリ秒単位の経度xミリ秒単位の緯度\" もしくは \"経度" -"の小数表記x緯度の小数表記\" という文字列表現を使って指定します。経度と緯度の" -"区切りとしては、'x' のほかに ',' を使うことができます。" -msgstr "" -"度分秒形式でx度y分z秒となる経度・緯度は、(((x * 60) + y) * 60 + z) * 1000とい" -"う計算式でミリ秒単位へと変換されます。 :doc:`/reference/commands/load` コマン" -"ドで値を格納するときは、\"ミリ秒単位の経度xミリ秒単位の緯度\" もしくは \"経度" -"の小数表記x緯度の小数表記\" という文字列表現を使って指定します。経度と緯度の" -"区切りとしては、'x' のほかに ',' を使うことができます。" - -msgid "" -"測地系の詳細については、 `測地系 - Wikipedia <http://ja.wikipedia.org/wiki/" -"%E6%B8%AC%E5%9C%B0%E7%B3%BB>`_ を参照してください。" -msgstr "" -"測地系の詳細については、 `測地系 - Wikipedia <http://ja.wikipedia.org/wiki/" -"%E6%B8%AC%E5%9C%B0%E7%B3%BB>`_ を参照してください。" - -msgid "``WGS84GeoPoint``" -msgstr "``WGS84GeoPoint``" - -msgid "" -"世界測地系（World Geodetic System, WGS 84）による経緯度であり、経度と緯度をミ" -"リ秒単位で表現した整数の組により表現します。（デフォルト値: 0x0）" -msgstr "" -"世界測地系（World Geodetic System, WGS 84）による経緯度であり、経度と緯度をミ" -"リ秒単位で表現した整数の組により表現します。（デフォルト値: 0x0）" - -msgid "" -"度分秒形式からミリ秒形式への変換方法や :doc:`/reference/commands/load` コマン" -"ドにおける指定方法はTokyoGeoPointと同じです。" -msgstr "" -"度分秒形式からミリ秒形式への変換方法や :doc:`/reference/commands/load` コマン" -"ドにおける指定方法はTokyoGeoPointと同じです。" - -msgid "型に関する制限事項" -msgstr "型に関する制限事項" - -msgid "テーブルの主キーに指定できない型" -msgstr "テーブルの主キーに指定できない型" - -msgid "" -"Text型とLongText型については、テーブルの主キーに指定することはできません。" -msgstr "" -"Text型とLongText型については、テーブルの主キーに指定することはできません。" - -msgid "ベクターとして格納できない型" -msgstr "ベクターとして格納できない型" - -msgid "" -"Groongaのカラムは、ある型のベクターを保存することができます。しかし、" -"ShortText, Text, LongTextの３つの型についてはベクターとして保存したり出力した" -"りすることはできますが、検索条件やドリルダウン条件に指定することができませ" -"ん。" -msgstr "" -"Groongaのカラムは、ある型のベクターを保存することができます。しかし、" -"ShortText, Text, LongTextの３つの型についてはベクターとして保存したり出力した" -"りすることはできますが、検索条件やドリルダウン条件に指定することができませ" -"ん。" - -msgid "" -"テーブル型は、ベクターとして格納することができます。よって、ShortTextのベク" -"ターを検索条件やドリルダウン条件に使用したい場合には、主キーがShortText型の" -"テーブルを別途作成し、そのテーブルを型として利用します。" -msgstr "" -"テーブル型は、ベクターとして格納することができます。よって、ShortTextのベク" -"ターを検索条件やドリルダウン条件に使用したい場合には、主キーがShortText型の" -"テーブルを別途作成し、そのテーブルを型として利用します。" - -msgid "Object型はv1.2でサポートされます。" -msgstr "Object型はv1.2でサポートされます。" Deleted: doc/locale/en/LC_MESSAGES/server.po (+0 -528) 100644 =================================================================== --- doc/locale/en/LC_MESSAGES/server.po 2015-03-25 14:48:34 +0900 (dae77e4) +++ /dev/null @@ -1,528 +0,0 @@ -# -*- po -*- -# English translations for Groonga package. -# Copyright (C) 2009-2014, Brazil, Inc -# This file is distributed under the same license as the Groonga package. -# Kouhei Sutou <kou �� clear-code.com>, 2014. -# -msgid "" -msgstr "" -"Project-Id-Version: Groonga 4.0.1\n" -"Report-Msgid-Bugs-To: \n" -"PO-Revision-Date: 2015-01-27 19:16+0900\n" -"Last-Translator: Kouhei Sutou <kou �� clear-code.com>\n" -"Language-Team: English\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" - -msgid "Server" -msgstr "Server" - -msgid "GQTP" -msgstr "GQTP" - -msgid "TODO" -msgstr "TODO" - -msgid "See :doc:`/reference/executables/groonga`." -msgstr "See :doc:`/reference/executables/groonga`." - -msgid "HTTP" -msgstr "HTTP" - -msgid "Groonga provides two HTTP server implementations." -msgstr "Groonga provides two HTTP server implementations." - -msgid ":doc:`http/groonga`" -msgstr ":doc:`http/groonga`" - -msgid ":doc:`http/groonga-httpd`" -msgstr ":doc:`http/groonga-httpd`" - -msgid "" -":doc:`http/groonga` is a simple implemntation. It is fast but doesn't have " -"many HTTP features. It is convenient to try Groonga because it requires just " -"a few command line options to run." -msgstr "" - -msgid "" -":doc:`http/groonga-httpd` is a `nginx <http://nginx.org/>`_ based " -"implementation. It is also fast and has many HTTP features." -msgstr "" -":doc:`http/groonga-httpd` is a `nginx <http://nginx.org/>`_ based " -"implementation. It is also fast and has many HTTP features." - -msgid "Comparison" -msgstr "Comparison" - -msgid "" -"There are many differences between :doc:`groonga` and :doc:`groonga-httpd`. " -"Here is a comparison table." -msgstr "" -"There are many differences between :doc:`groonga` and :doc:`groonga-httpd`. " -"Here is a comparison table." - -msgid "groonga" -msgstr "groonga" - -msgid "groonga-httpd" -msgstr "groonga-httpd" - -msgid "Performance" -msgstr "Performance" - -msgid "o" -msgstr "o" - -msgid "Using multi CPU cores" -msgstr "Using multi CPU cores" - -msgid "o (by multi process)" -msgstr "o (by multi process)" - -msgid "o (by multi threading)" -msgstr "o (by multi threading)" - -msgid "Configuration file" -msgstr "Configuration file" - -msgid "optional" -msgstr "optional" - -msgid "required" -msgstr "required" - -msgid "Custom prefix path" -msgstr "Custom prefix path" - -msgid "x" -msgstr "x" - -msgid "Custom command version" -msgstr "Custom command version" - -msgid "Multi databases" -msgstr "Multi databases" - -msgid "Authentication" -msgstr "Authentication" - -msgid "Gzip compression" -msgstr "Gzip compression" - -msgid "POST" -msgstr "POST" - -msgid "HTTPS" -msgstr "HTTPS" - -msgid "Access log" -msgstr "Access log" - -msgid "Upgrading without downtime" -msgstr "Upgrading without downtime" - -msgid "" -"Both :doc:`groonga` and :doc:`groonga-httpd` are very fast. They can work " -"with the same throughput." -msgstr "" -"Both :doc:`groonga` and :doc:`groonga-httpd` are very fast. They can work " -"with the same throughput." - -msgid "" -"Groonga scales on multi CPU cores. :doc:`groonga` scales by multi " -"threading. :doc:`groonga-httpd` scales by multi processes." -msgstr "" -"Groonga scales on multi CPU cores. :doc:`groonga` scales by multi " -"threading. :doc:`groonga-httpd` scales by multi processes." - -msgid "" -":doc:`groonga` uses the same number of threads as CPU cores by default. If " -"you have 8 CPU cores, 8 threads are used by default." -msgstr "" -":doc:`groonga` uses the same number of threads as CPU cores by default. If " -"you have 8 CPU cores, 8 threads are used by default." - -msgid "" -":doc:`groonga-httpd` uses 1 process by default. You need to set " -"`worker_processes <http://nginx.org/en/docs/ngx_core_module." -"html#worker_processes>`_ directive to use CPU cores. If you have 8 CPU " -"cores, specify ``worker_processes 8`` in configuration file like the " -"following::" -msgstr "" -":doc:`groonga-httpd` uses 1 process by default. You need to set " -"`worker_processes <http://nginx.org/en/docs/ngx_core_module." -"html#worker_processes>`_ directive to use CPU cores. If you have 8 CPU " -"cores, specify ``worker_processes 8`` in configuration file like the " -"following::" - -msgid "" -":doc:`groonga` can work without configuration file. All configuration items " -"such as port number and the max number of threads can be specified by " -"command line. Configuration file is also used to specify configuration items." -msgstr "" -":doc:`groonga` can work without configuration file. All configuration items " -"such as port number and the max number of threads can be specified by " -"command line. Configuration file is also used to specify configuration items." - -msgid "" -"It's very easy to run groonga HTTP server because :doc:`groonga` requires " -"just a few options to run. Here is the most simple command line to start " -"HTTP server by :doc:`groonga`::" -msgstr "" -"It's very easy to run groonga HTTP server because :doc:`groonga` requires " -"just a few options to run. Here is the most simple command line to start " -"HTTP server by :doc:`groonga`::" - -msgid "" -":doc:`groonga-httpd` requires configuration file to run. Here is the most " -"simple configuration file to start HTTP server by :doc:`groonga-httpd`::" -msgstr "" -":doc:`groonga-httpd` requires configuration file to run. Here is the most " -"simple configuration file to start HTTP server by :doc:`groonga-httpd`::" - -msgid "" -":doc:`groonga` accepts a path that starts with ``/d/`` as command URL such " -"as ``http://localhost:10041/d/status``. You cannot change the prefix path ``/" -"d/``." -msgstr "" -":doc:`groonga` accepts a path that starts with ``/d/`` as command URL such " -"as ``http://localhost:10041/d/status``. You cannot change the prefix path ``/" -"d/``." - -msgid "" -":doc:`groonga-httpd` can custom prefix path. For example, you can use " -"``http://localhost:10041/api/status`` as command URL. Here is a sample " -"configuration to use ``/api/`` as prefix path::" -msgstr "" -":doc:`groonga-httpd` can custom prefix path. For example, you can use " -"``http://localhost:10041/api/status`` as command URL. Here is a sample " -"configuration to use ``/api/`` as prefix path::" - -msgid "" -"Groonga has :doc:`/reference/command/command_version` mechanism. It is for " -"upgrading groonga commands with backward compatibility." -msgstr "" -"Groonga has :doc:`/reference/command/command_version` mechanism. It is for " -"upgrading groonga commands with backward compatibility." - -msgid "" -":doc:`groonga` can change the default command veresion by ``--default-" -"command-version`` option. Here is a sample command line to use command " -"version 2 as the default command version::" -msgstr "" -":doc:`groonga` can change the default command veresion by ``--default-" -"command-version`` option. Here is a sample command line to use command " -"version 2 as the default command version::" - -msgid "" -":doc:`groonga-httpd` cannot custom the default command version yet. But it " -"will be supported soon. If it is supported, you can provides different " -"command version groonga commands in the same :doc:`groonga-httpd` process. " -"Here is a sample configuration to provide command version 1 commands under " -"``/api/1/`` and command version 2 comamnds under ``/api/2/``::" -msgstr "" -":doc:`groonga-httpd` cannot custom the default command version yet. But it " -"will be supported soon. If it is supported, you can provides different " -"command version groonga commands in the same :doc:`groonga-httpd` process. " -"Here is a sample configuration to provide command version 1 commands under " -"``/api/1/`` and command version 2 comamnds under ``/api/2/``::" - -msgid ":doc:`groonga` can use only one database in a process." -msgstr ":doc:`groonga` can use only one database in a process." - -msgid "" -":doc:`groonga-httpd` can use one or more databases in a process. Here is a " -"sample configuration to provide ``/tmp/db1`` database under ``/db1/`` path " -"and ``/tmp/db2`` database under ``/db2/`` path::" -msgstr "" -":doc:`groonga-httpd` can use one or more databases in a process. Here is a " -"sample configuration to provide ``/tmp/db1`` database under ``/db1/`` path " -"and ``/tmp/db2`` database under ``/db2/`` path::" - -msgid "" -"HTTP supports authentications such as basic authentication and digest " -"authentication. It can be used for restricting use of danger command such " -"as :doc:`/reference/commands/shutdown`." -msgstr "" -"HTTP supports authentications such as basic authentication and digest " -"authentication. It can be used for restricting use of danger command such " -"as :doc:`/reference/commands/shutdown`." - -msgid "" -":doc:`groonga` doesn't support any authentications. To restrict use of " -"danger command, other tools such as iptables and reverse proxy are needed." -msgstr "" -":doc:`groonga` doesn't support any authentications. To restrict use of " -"danger command, other tools such as iptables and reverse proxy are needed." - -msgid "" -":doc:`groonga-httpd` supports basic authentication. Here is a sample " -"configuration to restrict use of :doc:`/reference/commands/shutdown` " -"command::" -msgstr "" -":doc:`groonga-httpd` supports basic authentication. Here is a sample " -"configuration to restrict use of :doc:`/reference/commands/shutdown` " -"command::" - -msgid "" -"HTTP supports response compression by gzip with ``Content-Encoding: gzip`` " -"response header. It can reduce network flow. It is useful for large search " -"response." -msgstr "" -"HTTP supports response compression by gzip with ``Content-Encoding: gzip`` " -"response header. It can reduce network flow. It is useful for large search " -"response." - -msgid "" -":doc:`groonga` doesn't support compression. To support compression, reverse " -"proxy is needed." -msgstr "" -":doc:`groonga` doesn't support compression. To support compression, reverse " -"proxy is needed." - -msgid "" -":doc:`groonga-httpd` supports gzip compression. Here is a sample " -"configuration to compress response by gzip::" -msgstr "" -":doc:`groonga-httpd` supports gzip compression. Here is a sample " -"configuration to compress response by gzip::" - -msgid "" -"Note that `gzip_types *` is specified. It's one of the important " -"configuration. `gzip_types` specifies gzip target data formats by MIME " -"types. :doc:`groonga-httpd` returns one of JSON, XML or MessagePack format " -"data. But those formats aren't included in the default value of " -"`gzip_types`. The default value of `gzip_types` is `text/html`." -msgstr "" -"Note that `gzip_types *` is specified. It's one of the important " -"configuration. `gzip_types` specifies gzip target data formats by MIME " -"types. :doc:`groonga-httpd` returns one of JSON, XML or MessagePack format " -"data. But those formats aren't included in the default value of " -"`gzip_types`. The default value of `gzip_types` is `text/html`." - -msgid "" -"To compress response data from :doc:`groonga-httpd` by gzip, you need to " -"specify `gzip_types *` or `gzip_types application/json text/xml application/" -"x-msgpack` explicitly. `gzip_types *` is recommended. There are two reasons " -"for it. The first, groonga may support more formats in the future. The " -"second, all requests for the `location` are processed by groonga. You don't " -"need to consider about other modules." -msgstr "" -"To compress response data from :doc:`groonga-httpd` by gzip, you need to " -"specify `gzip_types *` or `gzip_types application/json text/xml application/" -"x-msgpack` explicitly. `gzip_types *` is recommended. There are two reasons " -"for it. The first, groonga may support more formats in the future. The " -"second, all requests for the `location` are processed by groonga. You don't " -"need to consider about other modules." - -msgid "" -"You can load your data by POST JSON data. You need follow the following " -"rules to use loading by POST." -msgstr "" -"You can load your data by POST JSON data. You need follow the following " -"rules to use loading by POST." - -msgid "`Content-Type` header value must be `application/json`." -msgstr "`Content-Type` header value must be `application/json`." - -msgid "JSON data is sent as body." -msgstr "JSON data is sent as body." - -msgid "Table name is specified by query parameter such as ``table=NAME``." -msgstr "Table name is specified by query parameter such as ``table=NAME``." - -msgid "" -"Here is an example curl command line that loads two users `alice` and `bob` " -"to `Users` table::" -msgstr "" -"Here is an example curl command line that loads two users `alice` and `bob` " -"to `Users` table::" - -msgid "Server packages" -msgstr "Server packages" - -msgid "" -"The package ``groonga`` is the mininum set of fulltext search engine. If you " -"want to use groonga for server use, you can install additional preconfigured " -"packages." -msgstr "" -"The package ``groonga`` is the mininum set of fulltext search engine. If you " -"want to use groonga for server use, you can install additional preconfigured " -"packages." - -msgid "There are two packages for server use." -msgstr "" - -msgid "``groonga-httpd`` (nginx and HTTP protocol based server package)" -msgstr "``groonga-httpd`` (nginx and HTTP protocol based server package)" - -msgid "" -"``groonga-server-gqtp`` (:doc:`/spec/gqtp` protocol based server package)" -msgstr "" -"``groonga-server-gqtp`` (:doc:`/spec/gqtp` protocol based server package)" - -msgid "" -"There is the reason why groonga supports not only GQTP but also two HTTP " -"server packages. :doc:`/spec/gqtp` - Groonga Query Transfer Protocol is " -"desined to reduce overheads and improve performance. But, GQTP is less " -"support of client library than HTTP protocol does. As HTTP is matured " -"protocol, you can take advantage of existing tool and there are many client " -"library (See `related projects <http://groonga.org/related-projects.html>`_ " -"for details). If you use ``groonga-httpd`` package, you can also take " -"benefits of nginx functionality." -msgstr "" -"There is the reason why groonga supports not only GQTP but also two HTTP " -"server packages. :doc:`/spec/gqtp` - Groonga Query Transfer Protocol is " -"desined to reduce overheads and improve performance. But, GQTP is less " -"support of client library than HTTP protocol does. As HTTP is matured " -"protocol, you can take advantage of existing tool and there are many client " -"library (See `related projects <http://groonga.org/related-projects.html>`_ " -"for details). If you use ``groonga-httpd`` package, you can also take " -"benefits of nginx functionality." - -msgid "" -"We recommend to use ``groonga-httpd`` at first, because it provides " -"fullfilling server functionality. If you have performance issues which is " -"derived from protocol overheads, consider to use ``groonga-server-gqtp``." -msgstr "" - -msgid "" -"In the previous versions, there is a ``groonga-server-http`` package (simple " -"HTTP protocol based server package). It is now marked as obsolete, please " -"use ``groonga-httpd`` packages instead. ``groonga-server-http`` package " -"became a transitional package for ``groonga-httpd``." -msgstr "" - -msgid "``groonga-httpd`` is a nginx and HTTP protocol based server package." -msgstr "``groonga-httpd`` is a nginx and HTTP protocol based server package." - -msgid "Preconfigured setting:" -msgstr "Preconfigured setting:" - -msgid "Default value" -msgstr "Default value" - -msgid "Item" -msgstr "Item" - -msgid "10041" -msgstr "10041" - -msgid "Port number" -msgstr "Port number" - -msgid "/var/log/groonga/httpd/acccess.log" -msgstr "/var/log/groonga/httpd/acccess.log" - -msgid "Access log path" -msgstr "Access log path" - -msgid "/var/log/groonga/http-query.log" -msgstr "/var/log/groonga/http-query.log" - -msgid "Error log path" -msgstr "Error log path" - -msgid "/var/lib/groonga/db/*" -msgstr "/var/lib/groonga/db/*" - -msgid "Database" -msgstr "Database" - -msgid "/etc/groonga/httpd/groonga-httpd.conf" -msgstr "/etc/groonga/httpd/groonga-httpd.conf" - -msgid "Start HTTP server" -msgstr "Start HTTP server" - -msgid "Starting groonga HTTP server(Debian/Ubuntu/CentOS)::" -msgstr "Starting groonga HTTP server(Debian/Ubuntu/CentOS)::" - -msgid "Starting groonga HTTP server(Fedora)::" -msgstr "Starting groonga HTTP server(Fedora)::" - -msgid "Stop HTTP server" -msgstr "Stop HTTP server" - -msgid "Stopping groonga HTTP server(Debian/Ubuntu/CentOS)::" -msgstr "Stopping groonga HTTP server(Debian/Ubuntu/CentOS)::" - -msgid "Restart HTTP server" -msgstr "Restart HTTP server" - -msgid "Restarting groonga HTTP server(Debian/Ubuntu/CentOS)::" -msgstr "Restarting groonga HTTP server(Debian/Ubuntu/CentOS)::" - -msgid "Restarting groonga HTTP server(Fedora)::" -msgstr "Restarting groonga HTTP server(Fedora)::" - -msgid "groonga-server-gqtp" -msgstr "groonga-server-gqtp" - -msgid "" -"``groonga-server-gqtp`` is a :doc:`/spec/gqtp` protocol based server package." -msgstr "" -"``groonga-server-gqtp`` is a :doc:`/spec/gqtp` protocol based server package." - -msgid "10043" -msgstr "10043" - -msgid "/var/log/groonga/groonga-gqtp.log" -msgstr "/var/log/groonga/groonga-gqtp.log" - -msgid ":ref:`process-log`" -msgstr ":ref:`process-log`" - -msgid "/var/log/groonga/gqtp-query.log" -msgstr "/var/log/groonga/gqtp-query.log" - -msgid ":ref:`query-log`" -msgstr ":ref:`query-log`" - -msgid "Configuration file for server setting (Debian/Ubuntu)::" -msgstr "Configuration file for server setting (Debian/Ubuntu)::" - -msgid "Configuration file for server setting (CentOS)::" -msgstr "Configuration file for server setting (CentOS)::" - -msgid "Start GQTP server" -msgstr "Start GQTP server" - -msgid "Starting groonga GQTP server(Debian/Ubuntu/CentOS)::" -msgstr "Starting groonga GQTP server(Debian/Ubuntu/CentOS)::" - -msgid "Starting groonga GQTP server(Fedora)::" -msgstr "Starting groonga GQTP server(Fedora)::" - -msgid "Stop GQTP server" -msgstr "Stop GQTP server" - -msgid "Stopping groonga GQTP server(Debian/Ubuntu/CentOS)::" -msgstr "Stopping groonga GQTP server(Debian/Ubuntu/CentOS)::" - -msgid "Stopping groonga GQTP server(Fedora)::" -msgstr "Stopping groonga GQTP server(Fedora)::" - -msgid "Restart GQTP server" -msgstr "Restart GQTP server" - -msgid "groonga-server-http" -msgstr "groonga-server-http" - -msgid "``groonga-server-http`` is a simple HTTP protocol based server package." -msgstr "" -"``groonga-server-http`` is a simple HTTP protocol based server package." - -msgid "" -"``groonga-server-http`` package is the transitional package since Groonga " -"4.0.8. Please use ``groonga-httpd`` instead." -msgstr "" - -msgid "/var/log/groonga/groonga-http.log" -msgstr "/var/log/groonga/groonga-http.log" - -msgid "Stopping groonga HTTP server(Fedora)::" -msgstr "Stopping groonga HTTP server(Fedora)::" Deleted: doc/locale/en/LC_MESSAGES/spec.po (+0 -797) 100644 =================================================================== --- doc/locale/en/LC_MESSAGES/spec.po 2015-03-25 14:48:34 +0900 (e329b92) +++ /dev/null @@ -1,797 +0,0 @@ -# -*- po -*- -# English translations for Groonga package. -# Copyright (C) 2009-2014, Brazil, Inc -# This file is distributed under the same license as the Groonga package. -# Kouhei Sutou <kou �� clear-code.com>, 2014. -# -msgid "" -msgstr "" -"Project-Id-Version: Groonga 4.0.1\n" -"Report-Msgid-Bugs-To: \n" -"PO-Revision-Date: 2014-05-23 12:44+0900\n" -"Last-Translator: Kouhei Sutou <kou �� clear-code.com>\n" -"Language-Team: English\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" - -msgid "Specification" -msgstr "Specification" - -msgid "GQTP" -msgstr "GQTP" - -msgid "" -"GQTP is the acronym of Groonga Query Transfer Protocol. GQTP is the original " -"protocol for groonga." -msgstr "" -"GQTP is the acronym of Groonga Query Transfer Protocol. GQTP is the original " -"protocol for groonga." - -msgid "Protocol" -msgstr "Protocol" - -msgid "" -"GQTP is stateful client server model protocol. The following sequence is one " -"processing unit:" -msgstr "" -"GQTP is stateful client server model protocol. The following sequence is one " -"processing unit:" - -msgid "Client sends a request" -msgstr "Client sends a request" - -msgid "Server receives the request" -msgstr "Server receives the request" - -msgid "Server processes the request" -msgstr "Server processes the request" - -msgid "Server sends a response" -msgstr "Server sends a response" - -msgid "Client receives the response" -msgstr "Client receives the response" - -msgid "You can do zero or more processing units in a session." -msgstr "You can do zero or more processing units in a session." - -msgid "" -"Both request and response consist of GQTP header and body. GQTP header is " -"fixed size data. Body is variable size data and its size is stored in GQTP " -"header. The content of body isn't defined in GQTP." -msgstr "" -"Both request and response consist of GQTP header and body. GQTP header is " -"fixed size data. Body is variable size data and its size is stored in GQTP " -"header. The content of body isn't defined in GQTP." - -msgid "GQTP header" -msgstr "GQTP header" - -msgid "GQTP header consists of the following unsigned integer values:" -msgstr "GQTP header consists of the following unsigned integer values:" - -msgid "Description" -msgstr "Description" - -msgid "Name" -msgstr "Name" - -msgid "Size" -msgstr "Size" - -msgid "1byte" -msgstr "1byte" - -msgid "Protocol type." -msgstr "Protocol type." - -msgid "``protocol``" -msgstr "``protocol``" - -msgid "Content type of body." -msgstr "Content type of body." - -msgid "``query_type``" -msgstr "``query_type``" - -msgid "2byte" -msgstr "2byte" - -msgid "Not used." -msgstr "Not used." - -msgid "``key_length``" -msgstr "``key_length``" - -msgid "``level``" -msgstr "``level``" - -msgid "Flags." -msgstr "Flags." - -msgid "``flags``" -msgstr "``flags``" - -msgid "Return code." -msgstr "Return code." - -msgid "``status``" -msgstr "``status``" - -msgid "4byte" -msgstr "4byte" - -msgid "Body size." -msgstr "Body size." - -msgid "``size``" -msgstr "``size``" - -msgid "``opaque``" -msgstr "``opaque``" - -msgid "8byte" -msgstr "8byte" - -msgid "``cas``" -msgstr "``cas``" - -msgid "All header values are encoded by network byte order." -msgstr "All header values are encoded by network byte order." - -msgid "The following sections describes available values of each header value." -msgstr "" -"The following sections describes available values of each header value." - -msgid "The total size of GQTP header is 24byte." -msgstr "The total size of GQTP header is 24byte." - -msgid "The value is always ``0xc7`` in both request and response GQTP header." -msgstr "The value is always ``0xc7`` in both request and response GQTP header." - -msgid "The value is one of the following values:" -msgstr "The value is one of the following values:" - -msgid "Value" -msgstr "Value" - -msgid "0" -msgstr "0" - -msgid "Free format." -msgstr "Free format." - -msgid "``NONE``" -msgstr "``NONE``" - -msgid "1" -msgstr "1" - -msgid "Tab Separated Values." -msgstr "Tab Separated Values." - -msgid "``TSV``" -msgstr "``TSV``" - -msgid "2" -msgstr "2" - -msgid "JSON." -msgstr "JSON." - -msgid "``JSON``" -msgstr "``JSON``" - -msgid "3" -msgstr "3" - -msgid "XML." -msgstr "XML." - -msgid "``XML``" -msgstr "``XML``" - -msgid "4" -msgstr "4" - -msgid "MessagePack." -msgstr "MessagePack." - -msgid "``MSGPACK``" -msgstr "``MSGPACK``" - -msgid "This is not used in request GQTP header." -msgstr "This is not used in request GQTP header." - -msgid "" -"This is used in response GQTP header. Body is formatted as specified type." -msgstr "" -"This is used in response GQTP header. Body is formatted as specified type." - -msgid "The value is bitwise OR of the following values:" -msgstr "The value is bitwise OR of the following values:" - -msgid "0x01" -msgstr "0x01" - -msgid "There are more data." -msgstr "There are more data." - -msgid "``MORE``" -msgstr "``MORE``" - -msgid "0x02" -msgstr "0x02" - -msgid "There are no more data." -msgstr "There are no more data." - -msgid "``TAIL``" -msgstr "``TAIL``" - -msgid "0x04" -msgstr "0x04" - -msgid "``HEAD``" -msgstr "``HEAD``" - -msgid "0x08" -msgstr "0x08" - -msgid "Be quiet." -msgstr "Be quiet." - -msgid "``QUIET``" -msgstr "``QUIET``" - -msgid "0x10" -msgstr "0x10" - -msgid "Quit." -msgstr "Quit." - -msgid "``QUIT``" -msgstr "``QUIT``" - -msgid "You must specify ``MORE`` or ``TAIL`` flag." -msgstr "You must specify ``MORE`` or ``TAIL`` flag." - -msgid "" -"If you use ``MORE`` flag, you should also use ``QUIET`` flag. Because you " -"don't need to show a response for your partial request." -msgstr "" -"If you use ``MORE`` flag, you should also use ``QUIET`` flag. Because you " -"don't need to show a response for your partial request." - -msgid "Use ``QUIT`` flag to quit this session." -msgstr "Use ``QUIT`` flag to quit this session." - -msgid "" -"Here are available values. The new statuses will be added in the future." -msgstr "" -"Here are available values. The new statuses will be added in the future." - -msgid "0: ``SUCCESS``" -msgstr "0: ``SUCCESS``" - -msgid "1: ``END_OF_DATA``" -msgstr "1: ``END_OF_DATA``" - -msgid "65535: ``UNKNOWN_ERROR``" -msgstr "65535: ``UNKNOWN_ERROR``" - -msgid "65534: ``OPERATION_NOT_PERMITTED``" -msgstr "65534: ``OPERATION_NOT_PERMITTED``" - -msgid "65533: ``NO_SUCH_FILE_OR_DIRECTORY``" -msgstr "65533: ``NO_SUCH_FILE_OR_DIRECTORY``" - -msgid "65532: ``NO_SUCH_PROCESS``" -msgstr "65532: ``NO_SUCH_PROCESS``" - -msgid "65531: ``INTERRUPTED_FUNCTION_CALL``" -msgstr "65531: ``INTERRUPTED_FUNCTION_CALL``" - -msgid "65530: ``INPUT_OUTPUT_ERROR``" -msgstr "65530: ``INPUT_OUTPUT_ERROR``" - -msgid "65529: ``NO_SUCH_DEVICE_OR_ADDRESS``" -msgstr "65529: ``NO_SUCH_DEVICE_OR_ADDRESS``" - -msgid "65528: ``ARG_LIST_TOO_LONG``" -msgstr "65528: ``ARG_LIST_TOO_LONG``" - -msgid "65527: ``EXEC_FORMAT_ERROR``" -msgstr "65527: ``EXEC_FORMAT_ERROR``" - -msgid "65526: ``BAD_FILE_DESCRIPTOR``" -msgstr "65526: ``BAD_FILE_DESCRIPTOR``" - -msgid "65525: ``NO_CHILD_PROCESSES``" -msgstr "65525: ``NO_CHILD_PROCESSES``" - -msgid "65524: ``RESOURCE_TEMPORARILY_UNAVAILABLE``" -msgstr "65524: ``RESOURCE_TEMPORARILY_UNAVAILABLE``" - -msgid "65523: ``NOT_ENOUGH_SPACE``" -msgstr "65523: ``NOT_ENOUGH_SPACE``" - -msgid "65522: ``PERMISSION_DENIED``" -msgstr "65522: ``PERMISSION_DENIED``" - -msgid "65521: ``BAD_ADDRESS``" -msgstr "65521: ``BAD_ADDRESS``" - -msgid "65520: ``RESOURCE_BUSY``" -msgstr "65520: ``RESOURCE_BUSY``" - -msgid "65519: ``FILE_EXISTS``" -msgstr "65519: ``FILE_EXISTS``" - -msgid "65518: ``IMPROPER_LINK``" -msgstr "65518: ``IMPROPER_LINK``" - -msgid "65517: ``NO_SUCH_DEVICE``" -msgstr "65517: ``NO_SUCH_DEVICE``" - -msgid "65516: ``NOT_A_DIRECTORY``" -msgstr "65516: ``NOT_A_DIRECTORY``" - -msgid "65515: ``IS_A_DIRECTORY``" -msgstr "65515: ``IS_A_DIRECTORY``" - -msgid "65514: ``INVALID_ARGUMENT``" -msgstr "65514: ``INVALID_ARGUMENT``" - -msgid "65513: ``TOO_MANY_OPEN_FILES_IN_SYSTEM``" -msgstr "65513: ``TOO_MANY_OPEN_FILES_IN_SYSTEM``" - -msgid "65512: ``TOO_MANY_OPEN_FILES``" -msgstr "65512: ``TOO_MANY_OPEN_FILES``" - -msgid "65511: ``INAPPROPRIATE_I_O_CONTROL_OPERATION``" -msgstr "65511: ``INAPPROPRIATE_I_O_CONTROL_OPERATION``" - -msgid "65510: ``FILE_TOO_LARGE``" -msgstr "65510: ``FILE_TOO_LARGE``" - -msgid "65509: ``NO_SPACE_LEFT_ON_DEVICE``" -msgstr "65509: ``NO_SPACE_LEFT_ON_DEVICE``" - -msgid "65508: ``INVALID_SEEK``" -msgstr "65508: ``INVALID_SEEK``" - -msgid "65507: ``READ_ONLY_FILE_SYSTEM``" -msgstr "65507: ``READ_ONLY_FILE_SYSTEM``" - -msgid "65506: ``TOO_MANY_LINKS``" -msgstr "65506: ``TOO_MANY_LINKS``" - -msgid "65505: ``BROKEN_PIPE``" -msgstr "65505: ``BROKEN_PIPE``" - -msgid "65504: ``DOMAIN_ERROR``" -msgstr "65504: ``DOMAIN_ERROR``" - -msgid "65503: ``RESULT_TOO_LARGE``" -msgstr "65503: ``RESULT_TOO_LARGE``" - -msgid "65502: ``RESOURCE_DEADLOCK_AVOIDED``" -msgstr "65502: ``RESOURCE_DEADLOCK_AVOIDED``" - -msgid "65501: ``NO_MEMORY_AVAILABLE``" -msgstr "65501: ``NO_MEMORY_AVAILABLE``" - -msgid "65500: ``FILENAME_TOO_LONG``" -msgstr "65500: ``FILENAME_TOO_LONG``" - -msgid "65499: ``NO_LOCKS_AVAILABLE``" -msgstr "65499: ``NO_LOCKS_AVAILABLE``" - -msgid "65498: ``FUNCTION_NOT_IMPLEMENTED``" -msgstr "65498: ``FUNCTION_NOT_IMPLEMENTED``" - -msgid "65497: ``DIRECTORY_NOT_EMPTY``" -msgstr "65497: ``DIRECTORY_NOT_EMPTY``" - -msgid "65496: ``ILLEGAL_BYTE_SEQUENCE``" -msgstr "65496: ``ILLEGAL_BYTE_SEQUENCE``" - -msgid "65495: ``SOCKET_NOT_INITIALIZED``" -msgstr "65495: ``SOCKET_NOT_INITIALIZED``" - -msgid "65494: ``OPERATION_WOULD_BLOCK``" -msgstr "65494: ``OPERATION_WOULD_BLOCK``" - -msgid "65493: ``ADDRESS_IS_NOT_AVAILABLE``" -msgstr "65493: ``ADDRESS_IS_NOT_AVAILABLE``" - -msgid "65492: ``NETWORK_IS_DOWN``" -msgstr "65492: ``NETWORK_IS_DOWN``" - -msgid "65491: ``NO_BUFFER``" -msgstr "65491: ``NO_BUFFER``" - -msgid "65490: ``SOCKET_IS_ALREADY_CONNECTED``" -msgstr "65490: ``SOCKET_IS_ALREADY_CONNECTED``" - -msgid "65489: ``SOCKET_IS_NOT_CONNECTED``" -msgstr "65489: ``SOCKET_IS_NOT_CONNECTED``" - -msgid "65488: ``SOCKET_IS_ALREADY_SHUTDOWNED``" -msgstr "65488: ``SOCKET_IS_ALREADY_SHUTDOWNED``" - -msgid "65487: ``OPERATION_TIMEOUT``" -msgstr "65487: ``OPERATION_TIMEOUT``" - -msgid "65486: ``CONNECTION_REFUSED``" -msgstr "65486: ``CONNECTION_REFUSED``" - -msgid "65485: ``RANGE_ERROR``" -msgstr "65485: ``RANGE_ERROR``" - -msgid "65484: ``TOKENIZER_ERROR``" -msgstr "65484: ``TOKENIZER_ERROR``" - -msgid "65483: ``FILE_CORRUPT``" -msgstr "65483: ``FILE_CORRUPT``" - -msgid "65482: ``INVALID_FORMAT``" -msgstr "65482: ``INVALID_FORMAT``" - -msgid "65481: ``OBJECT_CORRUPT``" -msgstr "65481: ``OBJECT_CORRUPT``" - -msgid "65480: ``TOO_MANY_SYMBOLIC_LINKS``" -msgstr "65480: ``TOO_MANY_SYMBOLIC_LINKS``" - -msgid "65479: ``NOT_SOCKET``" -msgstr "65479: ``NOT_SOCKET``" - -msgid "65478: ``OPERATION_NOT_SUPPORTED``" -msgstr "65478: ``OPERATION_NOT_SUPPORTED``" - -msgid "65477: ``ADDRESS_IS_IN_USE``" -msgstr "65477: ``ADDRESS_IS_IN_USE``" - -msgid "65476: ``ZLIB_ERROR``" -msgstr "65476: ``ZLIB_ERROR``" - -msgid "65475: ``LZO_ERROR``" -msgstr "65475: ``LZO_ERROR``" - -msgid "65474: ``STACK_OVER_FLOW``" -msgstr "65474: ``STACK_OVER_FLOW``" - -msgid "65473: ``SYNTAX_ERROR``" -msgstr "65473: ``SYNTAX_ERROR``" - -msgid "65472: ``RETRY_MAX``" -msgstr "65472: ``RETRY_MAX``" - -msgid "65471: ``INCOMPATIBLE_FILE_FORMAT``" -msgstr "65471: ``INCOMPATIBLE_FILE_FORMAT``" - -msgid "65470: ``UPDATE_NOT_ALLOWED``" -msgstr "65470: ``UPDATE_NOT_ALLOWED``" - -msgid "65469: ``TOO_SMALL_OFFSET``" -msgstr "65469: ``TOO_SMALL_OFFSET``" - -msgid "65468: ``TOO_LARGE_OFFSET``" -msgstr "65468: ``TOO_LARGE_OFFSET``" - -msgid "65467: ``TOO_SMALL_LIMIT``" -msgstr "65467: ``TOO_SMALL_LIMIT``" - -msgid "65466: ``CAS_ERROR``" -msgstr "65466: ``CAS_ERROR``" - -msgid "65465: ``UNSUPPORTED_COMMAND_VERSION``" -msgstr "65465: ``UNSUPPORTED_COMMAND_VERSION``" - -msgid "" -"The size of body. The maximum body size is 4GiB because ``size`` is 4byte " -"unsigned integer. If you want to send 4GiB or more larger data, use ``MORE`` " -"flag." -msgstr "" -"The size of body. The maximum body size is 4GiB because ``size`` is 4byte " -"unsigned integer. If you want to send 4GiB or more larger data, use ``MORE`` " -"flag." - -msgid "Example" -msgstr "Example" - -msgid "TODO" -msgstr "TODO" - -msgid "See also" -msgstr "See also" - -msgid "検索" -msgstr "検索" - -msgid "" -":doc:`/reference/commands/select` コマンドがqueryパラメータを使ってどのように" -"検索するのかを説明します。" -msgstr "" -":doc:`/reference/commands/select` コマンドがqueryパラメータを使ってどのように" -"検索するのかを説明します。" - -msgid "検索の挙動" -msgstr "検索の挙動" - -msgid "検索の挙動には以下の3種類あり、検索結果によって動的に使い分けています。" -msgstr "" -"検索の挙動には以下の3種類あり、検索結果によって動的に使い分けています。" - -msgid "完全一致検索" -msgstr "完全一致検索" - -msgid "非わかち書き検索" -msgstr "非わかち書き検索" - -msgid "部分一致検索" -msgstr "部分一致検索" - -msgid "" -"どのように検索の挙動を使い分けているかを説明する前に、まず、それぞれの検索の" -"挙動を説明します。" -msgstr "" -"どのように検索の挙動を使い分けているかを説明する前に、まず、それぞれの検索の" -"挙動を説明します。" - -msgid "" -"検索対象文書は複数の語彙にトークナイズ(分割)され、それぞれを単位とした語彙表" -"に索引を管理します。 検索キーワードも同一の方法でトークナイズされます。" -msgstr "" -"検索対象文書は複数の語彙にトークナイズ(分割)され、それぞれを単位とした語彙表" -"に索引を管理します。 検索キーワードも同一の方法でトークナイズされます。" - -msgid "" -"このとき、検索キーワードをトークナイズした結果得られる語彙の配列と同一の配列" -"を含む文書を検索する処理を完全一致検索と呼んでいます。" -msgstr "" -"このとき、検索キーワードをトークナイズした結果得られる語彙の配列と同一の配列" -"を含む文書を検索する処理を完全一致検索と呼んでいます。" - -msgid "" -"たとえば、TokenMecabトークナイザを使用した索引では「東京都民」という文字列は" -msgstr "" -"たとえば、TokenMecabトークナイザを使用した索引では「東京都民」という文字列は" - -msgid "東京 / 都民" -msgstr "東京 / 都民" - -msgid "" -"という二つの語彙の配列として格納されます。この索引に対して「東京都」という" -"キーワードで検索した時、このキーワードは、" -msgstr "" -"という二つの語彙の配列として格納されます。この索引に対して「東京都」という" -"キーワードで検索した時、このキーワードは、" - -msgid "東京 / 都" -msgstr "東京 / 都" - -msgid "" -"という二つの語彙の配列として処理されます。この語彙の並びは、「東京 / 都民」と" -"いう語彙の並びには一致しませんので、完全一致検索ではヒットしません。" -msgstr "" -"という二つの語彙の配列として処理されます。この語彙の並びは、「東京 / 都民」と" -"いう語彙の並びには一致しませんので、完全一致検索ではヒットしません。" - -msgid "" -"これに対して、TokenBigramトークナイザを使用した索引では「東京都民」という文字" -"列は" -msgstr "" -"これに対して、TokenBigramトークナイザを使用した索引では「東京都民」という文字" -"列は" - -msgid "東京 / 京都 / 都民 / 民" -msgstr "東京 / 京都 / 都民 / 民" - -msgid "" -"という四つの語彙の配列として格納されます。この索引に対して「東京都」という" -"キーワードで検索した時、このキーワードは、" -msgstr "" -"という四つの語彙の配列として格納されます。この索引に対して「東京都」という" -"キーワードで検索した時、このキーワードは、" - -msgid "東京 / 京都" -msgstr "東京 / 京都" - -msgid "" -"という二つの語彙の配列として処理されます。この語彙の並びは、「東京 / 京都 / " -"都民」という語彙の並びに含まれますので、完全一致検索でヒットします。" -msgstr "" -"という二つの語彙の配列として処理されます。この語彙の並びは、「東京 / 京都 / " -"都民」という語彙の並びに含まれますので、完全一致検索でヒットします。" - -msgid "" -"なお、TokenBigramトークナイザでは、アルファベット・数値・記号文字列については" -"bigramを生成せず、一つの連続したトークンとして扱います。たとえば、「楽しい" -"billiard」という文字列は、" -msgstr "" -"なお、TokenBigramトークナイザでは、アルファベット・数値・記号文字列については" -"bigramを生成せず、一つの連続したトークンとして扱います。たとえば、「楽しい" -"billiard」という文字列は、" - -msgid "楽し / しい / billiard" -msgstr "楽し / しい / billiard" - -msgid "" -"という三つの語彙の配列として格納されます。これに対して「bill」というキーワー" -"ドで検索した時、このキーワードは、" -msgstr "" -"という三つの語彙の配列として格納されます。これに対して「bill」というキーワー" -"ドで検索した時、このキーワードは、" - -msgid "bill" -msgstr "bill" - -msgid "" -"という一つの語彙として処理されます。この語彙の並びは「楽し / しい / " -"billiard」という語彙の並びには含まれないので、完全一致でヒットしません。" -msgstr "" -"という一つの語彙として処理されます。この語彙の並びは「楽し / しい / " -"billiard」という語彙の並びには含まれないので、完全一致でヒットしません。" - -msgid "" -"これに対して、TokenBigramSplitSymbolAlphaトークナイザではアルファベット文字列" -"についてもbigramを生成し、「楽しいbilliard」という文字列は、" -msgstr "" -"これに対して、TokenBigramSplitSymbolAlphaトークナイザではアルファベット文字列" -"についてもbigramを生成し、「楽しいbilliard」という文字列は、" - -msgid "楽し / しい / いb / bi / il / ll / li / ia / ar / rd / d" -msgstr "楽し / しい / いb / bi / il / ll / li / ia / ar / rd / d" - -msgid "" -"という十一の語彙の配列として格納されます。これに対して「bill」というキーワー" -"ドで検索した時、このキーワードは、" -msgstr "" -"という十一の語彙の配列として格納されます。これに対して「bill」というキーワー" -"ドで検索した時、このキーワードは、" - -msgid "bi / il / ll" -msgstr "bi / il / ll" - -msgid "" -"という三つの語彙として処理されます。この語彙の並びは「楽し / しい / いb / " -"bi / il / ll / li / ia / ar / rd / d」という語彙の並びに含まれるので、完全一" -"致でヒットします。" -msgstr "" -"という三つの語彙として処理されます。この語彙の並びは「楽し / しい / いb / " -"bi / il / ll / li / ia / ar / rd / d」という語彙の並びに含まれるので、完全一" -"致でヒットします。" - -msgid "" -"非わかち書き検索はパトリシア木で語彙表を構築している場合のみ利用可能です。" -msgstr "" -"非わかち書き検索はパトリシア木で語彙表を構築している場合のみ利用可能です。" - -msgid "" -"非わかち書き検索の挙動はTokenBigramなどN-gram系のトークナイザーを利用している" -"場合とTokenMecabトークナイザーを利用している場合で挙動が変わります。" -msgstr "" -"非わかち書き検索の挙動はTokenBigramなどN-gram系のトークナイザーを利用している" -"場合とTokenMecabトークナイザーを利用している場合で挙動が変わります。" - -msgid "" -"N-gram系のトークナイザーを利用している場合はキーワードで前方一致検索をしま" -"す。" -msgstr "" -"N-gram系のトークナイザーを利用している場合はキーワードで前方一致検索をしま" -"す。" - -msgid "" -"例えば、「bill」というキーワードで検索した場合、「bill」も「billiard」もヒッ" -"トします。" -msgstr "" -"例えば、「bill」というキーワードで検索した場合、「bill」も「billiard」もヒッ" -"トします。" - -msgid "" -"TokenMeCabトークナイザーの場合はわかち書き前のキーワードで前方一致検索をしま" -"す。" -msgstr "" -"TokenMeCabトークナイザーの場合はわかち書き前のキーワードで前方一致検索をしま" -"す。" - -msgid "" -"例えば、「スープカレー」というキーワードで検索した場合、「スープカレーバー」" -"（1単語扱い）にヒットしますが、「スープカレー」（\"スープ\"と\"カレー\"の2単" -"語扱い）や「スープカレーライス」（\"スープ\"と\"カレーライス\"の2単語扱い）に" -"はヒットしません。" -msgstr "" -"例えば、「スープカレー」というキーワードで検索した場合、「スープカレーバー」" -"（1単語扱い）にヒットしますが、「スープカレー」（\"スープ\"と\"カレー\"の2単" -"語扱い）や「スープカレーライス」（\"スープ\"と\"カレーライス\"の2単語扱い）に" -"はヒットしません。" - -msgid "" -"部分一致検索はパトリシア木で語彙表を構築していて、かつ、KEY_WITH_SISオプショ" -"ンを指定している場合のみ利用可能です。KEY_WITH_SISオプションが指定されていな" -"い場合は非わかち書き検索と同等です。" -msgstr "" -"部分一致検索はパトリシア木で語彙表を構築していて、かつ、KEY_WITH_SISオプショ" -"ンを指定している場合のみ利用可能です。KEY_WITH_SISオプションが指定されていな" -"い場合は非わかち書き検索と同等です。" - -msgid "" -"部分一致検索の挙動はTokenBigramなどN-gram系のトークナイザーを利用している場合" -"とTokenMecabトークナイザーを利用している場合で挙動が変わります。" -msgstr "" -"部分一致検索の挙動はTokenBigramなどN-gram系のトークナイザーを利用している場合" -"とTokenMecabトークナイザーを利用している場合で挙動が変わります。" - -msgid "Bigramの場合は前方一致検索と中間一致検索と後方一致検索を行います。" -msgstr "Bigramの場合は前方一致検索と中間一致検索と後方一致検索を行います。" - -msgid "" -"例えば、「ill」というキーワードで検索した場合、「bill」も「billiard」もヒット" -"します。" -msgstr "" -"例えば、「ill」というキーワードで検索した場合、「bill」も「billiard」もヒット" -"します。" - -msgid "" -"TokenMeCabトークナイザーの場合はわかち書き後のキーワードで前方一致検索と中間" -"一致検索と後方一致検索をします。" -msgstr "" -"TokenMeCabトークナイザーの場合はわかち書き後のキーワードで前方一致検索と中間" -"一致検索と後方一致検索をします。" - -msgid "" -"例えば、「スープカレー」というキーワードで検索した場合、「スープカレー」" -"（\"スープ\"と\"カレー\"の2単語扱い）や「スープカレーライス」（\"スープ\"と" -"\"カレーライス\"の2単語扱い）、「スープカレーバー」（1単語扱い）にもヒットし" -"ます。" -msgstr "" -"例えば、「スープカレー」というキーワードで検索した場合、「スープカレー」" -"（\"スープ\"と\"カレー\"の2単語扱い）や「スープカレーライス」（\"スープ\"と" -"\"カレーライス\"の2単語扱い）、「スープカレーバー」（1単語扱い）にもヒットし" -"ます。" - -msgid "検索の使い分け" -msgstr "検索の使い分け" - -msgid "" -"groongaは基本的に完全一致検索のみを行います。完全一致検索でのヒット件数が所定" -"の閾値以下の場合に限り、非わかち書き検索を行い、それでもヒット件数が閾値以下" -"の場合は部分一致検索を行います。（閾値のデフォルト値は0です。）" -msgstr "" -"groongaは基本的に完全一致検索のみを行います。完全一致検索でのヒット件数が所定" -"の閾値以下の場合に限り、非わかち書き検索を行い、それでもヒット件数が閾値以下" -"の場合は部分一致検索を行います。（閾値のデフォルト値は0です。）" - -msgid "" -"ただし、すでに検索結果セットが存在する場合はたとえヒット件数が閾値以下でも完" -"全一致検索のみを行います。" -msgstr "" -"ただし、すでに検索結果セットが存在する場合はたとえヒット件数が閾値以下でも完" -"全一致検索のみを行います。" - -msgid "" -"例えば、以下のようなクエリの場合は、それぞれの検索でヒット件数が閾値以下の場" -"合は完全一致検索、非わかち書き検索、部分一致検索を順に行います。::" -msgstr "" -"例えば、以下のようなクエリの場合は、それぞれの検索でヒット件数が閾値以下の場" -"合は完全一致検索、非わかち書き検索、部分一致検索を順に行います。::" - -msgid "" -"しかし、以下のように全文検索を行う前に検索結果セットが存在する場合は完全一致" -"検索のみを行います。（point > 3で閾値の件数よりヒットしている場合）::" -msgstr "" -"しかし、以下のように全文検索を行う前に検索結果セットが存在する場合は完全一致" -"検索のみを行います。（point > 3で閾値の件数よりヒットしている場合）::" - -msgid "" -"そのため、descriptionに「スープカレーライス」が含まれていても、「スープカレー" -"ライス」は「スープカレー」に完全一致しないのでヒットしません。" -msgstr "" -"そのため、descriptionに「スープカレーライス」が含まれていても、「スープカレー" -"ライス」は「スープカレー」に完全一致しないのでヒットしません。" Deleted: doc/locale/en/LC_MESSAGES/suggest.po (+0 -763) 100644 =================================================================== --- doc/locale/en/LC_MESSAGES/suggest.po 2015-03-25 14:48:34 +0900 (5129afe) +++ /dev/null @@ -1,763 +0,0 @@ -# -*- po -*- -# English translations for Groonga package. -# Copyright (C) 2009-2014, Brazil, Inc -# This file is distributed under the same license as the Groonga package. -# Kouhei Sutou <kou �� clear-code.com>, 2014. -# -msgid "" -msgstr "" -"Project-Id-Version: Groonga 4.0.1\n" -"Report-Msgid-Bugs-To: \n" -"PO-Revision-Date: 2014-05-23 12:44+0900\n" -"Last-Translator: Kouhei Sutou <kou �� clear-code.com>\n" -"Language-Team: English\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: en\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "Suggest" -msgstr "Suggest" - -msgid "" -"Groonga has the suggest feature. This section describes how to use it and " -"how it works." -msgstr "" -"Groonga has the suggest feature. This section describes how to use it and " -"how it works." - -msgid "Completion" -msgstr "Completion" - -msgid "This section describes about the following completion features:" -msgstr "This section describes about the following completion features:" - -msgid "How it works" -msgstr "How it works" - -msgid "How to use" -msgstr "How to use" - -msgid "How to learn" -msgstr "How to learn" - -msgid "The completion feature uses three searches to compute completed words:" -msgstr "The completion feature uses three searches to compute completed words:" - -msgid "Prefix RK search against registered words." -msgstr "Prefix RK search against registered words." - -msgid "Cooccurrence search against learned data." -msgstr "Cooccurrence search against learned data." - -msgid "Prefix search against registered words. (optional)" -msgstr "Prefix search against registered words. (optional)" - -msgid "Prefix RK search" -msgstr "Prefix RK search" - -msgid "" -"RK means Romaji and Katakana. Prefix RK search can find registered words " -"that start with user's input by romaji, katakana or hiragana. It's useful " -"for searching in Japanese." -msgstr "" -"RK means Romaji and Katakana. Prefix RK search can find registered words " -"that start with user's input by romaji, katakana or hiragana. It's useful " -"for searching in Japanese." - -msgid "" -"For example, there is a registered word \"日本\". And \"ニホン\" (it must be " -"katakana) is registered as its reading. An user can find \"日本\" by \"ni\", " -"\"二\" or \"に\"." -msgstr "" -"For example, there is a registered word \"日本\". And \"ニホン\" (it must be " -"katakana) is registered as its reading. An user can find \"日本\" by \"ni\", " -"\"二\" or \"に\"." - -msgid "" -"If you create dataset which is named as example by :doc:`/reference/" -"executables/groonga-suggest-create-dataset` command, you can update pairs of " -"registered word and its reading by loading data to '_key' and 'kana' column " -"of item_example table explicitly for prefix RK search." -msgstr "" -"If you create dataset which is named as example by :doc:`/reference/" -"executables/groonga-suggest-create-dataset` command, you can update pairs of " -"registered word and its reading by loading data to '_key' and 'kana' column " -"of item_example table explicitly for prefix RK search." - -msgid "Cooccurrence search" -msgstr "Cooccurrence search" - -msgid "" -"Cooccurrence search can find registered words from user's partial input. It " -"uses user input sequences that will be learned from query logs, access logs " -"and so on." -msgstr "" -"Cooccurrence search can find registered words from user's partial input. It " -"uses user input sequences that will be learned from query logs, access logs " -"and so on." - -msgid "For example, there is the following user input sequence:" -msgstr "For example, there is the following user input sequence:" - -msgid "input" -msgstr "input" - -msgid "submit" -msgstr "submit" - -msgid "s" -msgstr "s" - -msgid "no" -msgstr "no" - -msgid "se" -msgstr "se" - -msgid "sea" -msgstr "sea" - -msgid "sear" -msgstr "sear" - -msgid "searc" -msgstr "searc" - -msgid "search" -msgstr "search" - -msgid "yes" -msgstr "yes" - -msgid "e" -msgstr "e" - -msgid "en" -msgstr "en" - -msgid "eng" -msgstr "eng" - -msgid "engi" -msgstr "engi" - -msgid "engin" -msgstr "engin" - -msgid "engine" -msgstr "engine" - -msgid "enginen" -msgstr "enginen" - -msgid "no (typo!)" -msgstr "no (typo!)" - -msgid "Groonga creates the following completion pairs:" -msgstr "Groonga creates the following completion pairs:" - -msgid "completed word" -msgstr "completed word" - -msgid "" -"All user not-submitted inputs (e.g. \"s\", \"se\" and so on) before each an " -"user submission maps to the submitted input (e.g. \"search\")." -msgstr "" -"All user not-submitted inputs (e.g. \"s\", \"se\" and so on) before each an " -"user submission maps to the submitted input (e.g. \"search\")." - -msgid "" -"To be precise, this description isn't correct because it omits about time " -"stamp. Groonga doesn't case about \"all user not-submitted inputs before " -"each an user submission\". Groonga just case about \"all user not-submitted " -"inputs within a minute from an user submission before each an user submission" -"\". Groonga doesn't treat user inputs before a minute ago." -msgstr "" -"To be precise, this description isn't correct because it omits about time " -"stamp. Groonga doesn't case about \"all user not-submitted inputs before " -"each an user submission\". Groonga just case about \"all user not-submitted " -"inputs within a minute from an user submission before each an user submission" -"\". Groonga doesn't treat user inputs before a minute ago." - -msgid "" -"If an user inputs \"sea\" and cooccurrence search returns \"search\" because " -"\"sea\" is in input column and corresponding completed word column value is " -"\"search\"." -msgstr "" -"If an user inputs \"sea\" and cooccurrence search returns \"search\" because " -"\"sea\" is in input column and corresponding completed word column value is " -"\"search\"." - -msgid "Prefix search" -msgstr "Prefix search" - -msgid "" -"Prefix search can find registered word that start with user's input. This " -"search doesn't care about romaji, katakana and hiragana not like Prefix RK " -"search." -msgstr "" -"Prefix search can find registered word that start with user's input. This " -"search doesn't care about romaji, katakana and hiragana not like Prefix RK " -"search." - -msgid "" -"This search isn't always ran. It's just ran when it's requested explicitly " -"or both prefix RK search and cooccurrence search return nothing." -msgstr "" -"This search isn't always ran. It's just ran when it's requested explicitly " -"or both prefix RK search and cooccurrence search return nothing." - -msgid "" -"For example, there is a registered word \"search\". An user can find \"search" -"\" by \"s\", \"se\", \"sea\", \"sear\", \"searc\" and \"search\"." -msgstr "" -"For example, there is a registered word \"search\". An user can find \"search" -"\" by \"s\", \"se\", \"sea\", \"sear\", \"searc\" and \"search\"." - -msgid "" -"Groonga provides :doc:`/reference/commands/suggest` command to use " -"completion. `--type complete` option requests completion." -msgstr "" -"Groonga provides :doc:`/reference/commands/suggest` command to use " -"completion. `--type complete` option requests completion." - -msgid "For example, here is an command to get completion results by \"en\":" -msgstr "For example, here is an command to get completion results by \"en\":" - -msgid "Execution example::" -msgstr "Execution example::" - -msgid "How it learns" -msgstr "How it learns" - -msgid "" -"Cooccurrence search uses learned data. They are based on query logs, access " -"logs and so on. To create learned data, groonga needs user input sequence " -"with time stamp and user submit input with time stamp." -msgstr "" -"Cooccurrence search uses learned data. They are based on query logs, access " -"logs and so on. To create learned data, groonga needs user input sequence " -"with time stamp and user submit input with time stamp." - -msgid "" -"For example, an user wants to search by \"engine\". The user inputs the " -"query with the following sequence:" -msgstr "" -"For example, an user wants to search by \"engine\". The user inputs the " -"query with the following sequence:" - -msgid "2011-08-10T13:33:23+09:00: e" -msgstr "2011-08-10T13:33:23+09:00: e" - -msgid "2011-08-10T13:33:23+09:00: en" -msgstr "2011-08-10T13:33:23+09:00: en" - -msgid "2011-08-10T13:33:24+09:00: eng" -msgstr "2011-08-10T13:33:24+09:00: eng" - -msgid "2011-08-10T13:33:24+09:00: engi" -msgstr "2011-08-10T13:33:24+09:00: engi" - -msgid "2011-08-10T13:33:24+09:00: engin" -msgstr "2011-08-10T13:33:24+09:00: engin" - -msgid "2011-08-10T13:33:25+09:00: engine (submit!)" -msgstr "2011-08-10T13:33:25+09:00: engine (submit!)" - -msgid "" -"Groonga can be learned from the input sequence by the following command::" -msgstr "" -"Groonga can be learned from the input sequence by the following command::" - -msgid "How to update RK reading data" -msgstr "How to update RK reading data" - -msgid "" -"Groonga requires registered word and its reading for RK search, so load such " -"data in the advance." -msgstr "" -"Groonga requires registered word and its reading for RK search, so load such " -"data in the advance." - -msgid "" -"Here is the example to register \"日本\" which means Japanese in english." -msgstr "" -"Here is the example to register \"日本\" which means Japanese in english." - -msgid "Here is the example to update RK data to complete \"日本\"." -msgstr "Here is the example to update RK data to complete \"日本\"." - -msgid "Then you can complete registered word \"日本\" by RK input - \"nihon\"." -msgstr "" -"Then you can complete registered word \"日本\" by RK input - \"nihon\"." - -msgid "" -"Without loading above RK data, you can't complete registered word \"日本\" " -"by query - \"nihon\"." -msgstr "" -"Without loading above RK data, you can't complete registered word \"日本\" " -"by query - \"nihon\"." - -msgid "" -"As the column type of item_query table is VECTOR_COLUMN, you can register " -"multiple readings for registered word." -msgstr "" -"As the column type of item_query table is VECTOR_COLUMN, you can register " -"multiple readings for registered word." - -msgid "" -"This is the reason that you can also complete the registered word \"日本\" " -"by query - \"nippon\"." -msgstr "" -"This is the reason that you can also complete the registered word \"日本\" " -"by query - \"nippon\"." - -msgid "" -"This feature is very convenient because you can search registered word even " -"though Japanese IM is disabled." -msgstr "" -"This feature is very convenient because you can search registered word even " -"though Japanese IM is disabled." - -msgid "" -"If there are multiple candidates as completed result, you can customize " -"priority to set the value of \"boost\" column in item_query table." -msgstr "" -"If there are multiple candidates as completed result, you can customize " -"priority to set the value of \"boost\" column in item_query table." - -msgid "Here is the example to customize priority for RK search." -msgstr "Here is the example to customize priority for RK search." - -msgid "Correction" -msgstr "Correction" - -msgid "This section describes about the following correction features:" -msgstr "This section describes about the following correction features:" - -msgid "The correction feature uses three searches to compute corrected words:" -msgstr "The correction feature uses three searches to compute corrected words:" - -msgid "Similar search against registered words. (optional)" -msgstr "Similar search against registered words. (optional)" - -msgid "" -"Cooccurrence search can find registered words from user's wrong input. It " -"uses user submit sequences that will be learned from query logs, access logs " -"and so on." -msgstr "" -"Cooccurrence search can find registered words from user's wrong input. It " -"uses user submit sequences that will be learned from query logs, access logs " -"and so on." - -msgid "For example, there are the following user submissions:" -msgstr "For example, there are the following user submissions:" - -msgid "query" -msgstr "query" - -msgid "time" -msgstr "time" - -msgid "serach (typo!)" -msgstr "serach (typo!)" - -msgid "2011-08-10T22:20:50+09:00" -msgstr "2011-08-10T22:20:50+09:00" - -msgid "search (fixed!)" -msgstr "search (fixed!)" - -msgid "2011-08-10T22:20:52+09:00" -msgstr "2011-08-10T22:20:52+09:00" - -msgid "" -"Groonga creates the following correction pair from the above submissions:" -msgstr "" -"Groonga creates the following correction pair from the above submissions:" - -msgid "corrected word" -msgstr "corrected word" - -msgid "serach" -msgstr "serach" - -msgid "" -"Groonga treats continuous submissions within a minute as input correction by " -"user. Not submitted user input sequence between two submissions isn't used " -"as learned data for correction." -msgstr "" -"Groonga treats continuous submissions within a minute as input correction by " -"user. Not submitted user input sequence between two submissions isn't used " -"as learned data for correction." - -msgid "" -"If an user inputs \"serach\" and cooccurrence search returns \"search\" " -"because \"serach\" is in input column and corresponding corrected word " -"column value is \"search\"." -msgstr "" -"If an user inputs \"serach\" and cooccurrence search returns \"search\" " -"because \"serach\" is in input column and corresponding corrected word " -"column value is \"search\"." - -msgid "Similar search" -msgstr "Similar search" - -msgid "" -"Similar search can find registered words that has one or more the same " -"tokens as user input. TokenBigram tokenizer is used for tokenization because " -"suggest dataset schema created by :doc:`/reference/executables/groonga-" -"suggest-create-dataset` uses TokenBigram tokenizer as the default tokenizer." -msgstr "" -"Similar search can find registered words that has one or more the same " -"tokens as user input. TokenBigram tokenizer is used for tokenization because " -"suggest dataset schema created by :doc:`/reference/executables/groonga-" -"suggest-create-dataset` uses TokenBigram tokenizer as the default tokenizer." - -msgid "" -"For example, there is a registered query \"search engine\". An user can find " -"\"search engine\" by \"web search service\", \"sound engine\" and so on. " -"Because \"search engine\" and \"web search engine\" have the same token " -"\"search\" and \"search engine\" and \"sound engine\" have the same token " -"\"engine\"." -msgstr "" -"For example, there is a registered query \"search engine\". An user can find " -"\"search engine\" by \"web search service\", \"sound engine\" and so on. " -"Because \"search engine\" and \"web search engine\" have the same token " -"\"search\" and \"search engine\" and \"sound engine\" have the same token " -"\"engine\"." - -msgid "" -"\"search engine\" is tokenized to \"search\" and \"engine\" tokens. " -"(Groonga's TokenBigram tokenizer doesn't tokenize two characters for " -"continuous alphabets and continuous digits for reducing search noise. " -"TokenBigramSplitSymbolAlphaDigit tokenizer should be used to ensure " -"tokenizing to two characters.) \"web search service\" is tokenized to \"web" -"\", \"search\" and \"service\". \"sound engine\" is tokenized to \"sound\" " -"and \"engine\"." -msgstr "" -"\"search engine\" is tokenized to \"search\" and \"engine\" tokens. " -"(Groonga's TokenBigram tokenizer doesn't tokenize two characters for " -"continuous alphabets and continuous digits for reducing search noise. " -"TokenBigramSplitSymbolAlphaDigit tokenizer should be used to ensure " -"tokenizing to two characters.) \"web search service\" is tokenized to \"web" -"\", \"search\" and \"service\". \"sound engine\" is tokenized to \"sound\" " -"and \"engine\"." - -msgid "" -"Groonga provides :doc:`/reference/commands/suggest` command to use " -"correction. `--type correct` option requests corrections." -msgstr "" -"Groonga provides :doc:`/reference/commands/suggest` command to use " -"correction. `--type correct` option requests corrections." - -msgid "" -"For example, here is an command to get correction results by \"saerch\":" -msgstr "" -"For example, here is an command to get correction results by \"saerch\":" - -msgid "" -"Cooccurrence search uses learned data. They are based on query logs, access " -"logs and so on. To create learned data, groonga needs user submit inputs " -"with time stamp." -msgstr "" -"Cooccurrence search uses learned data. They are based on query logs, access " -"logs and so on. To create learned data, groonga needs user submit inputs " -"with time stamp." - -msgid "" -"For example, an user wants to search by \"search\" but the user has typo " -"\"saerch\" before inputs the correct query. The user inputs the query with " -"the following sequence:" -msgstr "" -"For example, an user wants to search by \"search\" but the user has typo " -"\"saerch\" before inputs the correct query. The user inputs the query with " -"the following sequence:" - -msgid "2011-08-10T13:33:23+09:00: s" -msgstr "2011-08-10T13:33:23+09:00: s" - -msgid "2011-08-10T13:33:23+09:00: sa" -msgstr "2011-08-10T13:33:23+09:00: sa" - -msgid "2011-08-10T13:33:24+09:00: sae" -msgstr "2011-08-10T13:33:24+09:00: sae" - -msgid "2011-08-10T13:33:24+09:00: saer" -msgstr "2011-08-10T13:33:24+09:00: saer" - -msgid "2011-08-10T13:33:24+09:00: saerc" -msgstr "2011-08-10T13:33:24+09:00: saerc" - -msgid "2011-08-10T13:33:25+09:00: saerch (submit!)" -msgstr "2011-08-10T13:33:25+09:00: saerch (submit!)" - -msgid "2011-08-10T13:33:29+09:00: serch (correcting...)" -msgstr "2011-08-10T13:33:29+09:00: serch (correcting...)" - -msgid "2011-08-10T13:33:30+09:00: search (submit!)" -msgstr "2011-08-10T13:33:30+09:00: search (submit!)" - -msgid "Introduction" -msgstr "Introduction" - -msgid "The suggest feature in Groonga provides the following features:" -msgstr "The suggest feature in Groonga provides the following features:" - -msgid "Suggestion" -msgstr "Suggestion" - -msgid "" -"Completion helps user input. If user inputs a partial word, Groonga can " -"return complete words from registered words." -msgstr "" -"Completion helps user input. If user inputs a partial word, Groonga can " -"return complete words from registered words." - -msgid "For example, there are registered words:" -msgstr "For example, there are registered words:" - -msgid "\"groonga\"" -msgstr "\"groonga\"" - -msgid "\"complete\"" -msgstr "\"complete\"" - -msgid "\"correction\"" -msgstr "\"correction\"" - -msgid "\"suggest\"" -msgstr "\"suggest\"" - -msgid "" -"An user inputs \"co\" and groonga returns \"complete\" and \"correction\" " -"because they starts with \"co\"." -msgstr "" -"An user inputs \"co\" and groonga returns \"complete\" and \"correction\" " -"because they starts with \"co\"." - -msgid "" -"An user inputs \"sug\" and groonga returns \"suggest\" because \"suggest\" " -"starts with \"sug\"." -msgstr "" -"An user inputs \"sug\" and groonga returns \"suggest\" because \"suggest\" " -"starts with \"sug\"." - -msgid "" -"An user inputs \"ab\" and groonga returns nothing because no word starts " -"with \"ab\"." -msgstr "" -"An user inputs \"ab\" and groonga returns nothing because no word starts " -"with \"ab\"." - -msgid "" -"Correction also helps user input. If user inputs a wrong word, groonga can " -"return correct words from registered correction pairs." -msgstr "" -"Correction also helps user input. If user inputs a wrong word, groonga can " -"return correct words from registered correction pairs." - -msgid "For example, there are registered correction pairs:" -msgstr "For example, there are registered correction pairs:" - -msgid "wrong word" -msgstr "wrong word" - -msgid "correct word" -msgstr "correct word" - -msgid "grroonga" -msgstr "grroonga" - -msgid "groonga" -msgstr "groonga" - -msgid "gronga" -msgstr "gronga" - -msgid "gronnga" -msgstr "gronnga" - -msgid "" -"An user inputs \"gronga\" and groonga returns \"groonga\" because \"gronga\" " -"is in wrong word and corresponding correct word is \"groonga\"." -msgstr "" -"An user inputs \"gronga\" and groonga returns \"groonga\" because \"gronga\" " -"is in wrong word and corresponding correct word is \"groonga\"." - -msgid "" -"An user inputs \"roonga\" and groonga returns nothing because \"roonga\" " -"isn't in wrong word." -msgstr "" -"An user inputs \"roonga\" and groonga returns nothing because \"roonga\" " -"isn't in wrong word." - -msgid "" -"Suggestion helps that user filters many found documents. If user inputs a " -"query, groonga can return new queries that has more additional keywords from " -"registered related query pairs." -msgstr "" -"Suggestion helps that user filters many found documents. If user inputs a " -"query, groonga can return new queries that has more additional keywords from " -"registered related query pairs." - -msgid "For example, there are registered related query pairs:" -msgstr "For example, there are registered related query pairs:" - -msgid "keyword" -msgstr "keyword" - -msgid "related query" -msgstr "related query" - -msgid "groonga search engine" -msgstr "groonga search engine" - -msgid "Google search" -msgstr "Google search" - -msgid "speed" -msgstr "speed" - -msgid "groonga speed" -msgstr "groonga speed" - -msgid "" -"An user inputs \"groonga\" and groonga returns \"groonga search engine\" " -"because \"groonga\" is in keyword column and related query column is " -"\"groonga search engine\"." -msgstr "" -"An user inputs \"groonga\" and groonga returns \"groonga search engine\" " -"because \"groonga\" is in keyword column and related query column is " -"\"groonga search engine\"." - -msgid "" -"An user inputs \"MySQL\" and groonga returns nothing because \"MySQL\" isn't " -"in keyword column values." -msgstr "" -"An user inputs \"MySQL\" and groonga returns nothing because \"MySQL\" isn't " -"in keyword column values." - -msgid "Learning" -msgstr "Learning" - -msgid "" -"The suggest feature requires registered data before using the feature. Those " -"data can be registered from user inputs. Gronnga-suggest-httpd and groonga-" -"suggest-learner commands are provided for the propose." -msgstr "" -"The suggest feature requires registered data before using the feature. Those " -"data can be registered from user inputs. Gronnga-suggest-httpd and groonga-" -"suggest-learner commands are provided for the propose." - -msgid "The suggestion feature uses a search to compute suggested words:" -msgstr "The suggestion feature uses a search to compute suggested words:" - -msgid "" -"Cooccurrence search can find related words from user's input. It uses user " -"submissions that will be learned from query logs, access logs and so on." -msgstr "" -"Cooccurrence search can find related words from user's input. It uses user " -"submissions that will be learned from query logs, access logs and so on." - -msgid "search engine" -msgstr "search engine" - -msgid "web search realtime" -msgstr "web search realtime" - -msgid "Groonga creates the following suggestion pairs:" -msgstr "Groonga creates the following suggestion pairs:" - -msgid "suggested words" -msgstr "suggested words" - -msgid "web" -msgstr "web" - -msgid "realtime" -msgstr "realtime" - -msgid "Those pairs are created by the following steps:" -msgstr "Those pairs are created by the following steps:" - -msgid "" -"Tokenizes user input query by TokenDelimit tokenizer that uses a space as " -"token delimiter. (e.g. \"search engine\" is tokenized to two tokens \"search" -"\" and \"engine\".)" -msgstr "" -"Tokenizes user input query by TokenDelimit tokenizer that uses a space as " -"token delimiter. (e.g. \"search engine\" is tokenized to two tokens \"search" -"\" and \"engine\".)" - -msgid "" -"Creates a pair that is consists of a token and original query for each token." -msgstr "" -"Creates a pair that is consists of a token and original query for each token." - -msgid "" -"If an user inputs \"search\" and cooccurrence search returns \"search engine" -"\" and \"web search realtime\" because \"search\" is in two input columns " -"and corresponding suggested word columns have \"search engine\" and \"web " -"search realtime\"." -msgstr "" -"If an user inputs \"search\" and cooccurrence search returns \"search engine" -"\" and \"web search realtime\" because \"search\" is in two input columns " -"and corresponding suggested word columns have \"search engine\" and \"web " -"search realtime\"." - -msgid "" -"Groonga provides :doc:`/reference/commands/suggest` command to use " -"suggestion. `--type suggest` option requests suggestion" -msgstr "" -"Groonga provides :doc:`/reference/commands/suggest` command to use " -"suggestion. `--type suggest` option requests suggestion" - -msgid "" -"For example, here is an command to get suggestion results by \"search\":" -msgstr "" -"For example, here is an command to get suggestion results by \"search\":" - -msgid "2011-08-10T13:33:23+09:00: search engine (submit)" -msgstr "2011-08-10T13:33:23+09:00: search engine (submit)" - -msgid "2011-08-10T13:33:28+09:00: web search realtime (submit)" -msgstr "2011-08-10T13:33:28+09:00: web search realtime (submit)" - -msgid "Groonga can be learned from the submissions by the following command::" -msgstr "Groonga can be learned from the submissions by the following command::" - -msgid "How to extract learning data" -msgstr "How to extract learning data" - -msgid "" -"The learning data is stored into item_DATASET and pair_DATASET tables. By " -"using select command for such tables, you can all extract learing data." -msgstr "" -"The learning data is stored into item_DATASET and pair_DATASET tables. By " -"using select command for such tables, you can all extract learing data." - -msgid "Here is the query to extract all learning data::" -msgstr "Here is the query to extract all learning data::" - -msgid "" -"Without '--limit -1', you can't get all data. In pair table, the valid value " -"of freq0, freq1 and freq2 column must be larger than 0." -msgstr "" -"Without '--limit -1', you can't get all data. In pair table, the valid value " -"of freq0, freq1 and freq2 column must be larger than 0." - -msgid "" -"Don't execute above query via HTTP request because enourmous number of " -"records are fetched." -msgstr "" -"Don't execute above query via HTTP request because enourmous number of " -"records are fetched." - -msgid "Tutorial" -msgstr "Tutorial" - -msgid "TODO..." -msgstr "TODO..." Deleted: doc/locale/en/LC_MESSAGES/troubleshooting.po (+0 -418) 100644 =================================================================== --- doc/locale/en/LC_MESSAGES/troubleshooting.po 2015-03-25 14:48:34 +0900 (359b09d) +++ /dev/null @@ -1,418 +0,0 @@ -# -*- po -*- -# English translations for Groonga package. -# Copyright (C) 2009-2014, Brazil, Inc -# This file is distributed under the same license as the Groonga package. -# Kouhei Sutou <kou �� clear-code.com>, 2014. -# -msgid "" -msgstr "" -"Project-Id-Version: Groonga 4.0.1\n" -"Report-Msgid-Bugs-To: \n" -"PO-Revision-Date: 2014-08-28 12:07+0900\n" -"Last-Translator: Kouhei Sutou <kou �� clear-code.com>\n" -"Language-Team: English\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" - -msgid "トラブルシューティング" -msgstr "トラブルシューティング" - -msgid "同じ検索キーワードなのに全文検索結果が異なる" -msgstr "同じ検索キーワードなのに全文検索結果が異なる" - -msgid "" -"同じ検索キーワードでも一緒に指定するクエリによっては全文検索の結果が異なるこ" -"とがあります。ここでは、その原因と対策方法を説明します。" -msgstr "" -"同じ検索キーワードでも一緒に指定するクエリによっては全文検索の結果が異なるこ" -"とがあります。ここでは、その原因と対策方法を説明します。" - -msgid "例" -msgstr "例" - -msgid "まず、実際に検索結果が異なる例を説明します。" -msgstr "まず、実際に検索結果が異なる例を説明します。" - -msgid "" -"DDLは以下の通りです。BlogsテーブルのbodyカラムをTokenMecabトークナイザーを" -"使ってトークナイズしてからインデックスを作成しています。::" -msgstr "" -"DDLは以下の通りです。BlogsテーブルのbodyカラムをTokenMecabトークナイザーを" -"使ってトークナイズしてからインデックスを作成しています。::" - -msgid "テスト用のデータは1件だけ投入します。::" -msgstr "テスト用のデータは1件だけ投入します。::" - -msgid "まず、全文検索のみで検索します。この場合ヒットします。::" -msgstr "まず、全文検索のみで検索します。この場合ヒットします。::" - -msgid "" -"続いて、範囲指定と全文検索を組み合わせて検索します（1285858800は2010/10/1 " -"0:0:0の秒表記）。この場合もヒットします。::" -msgstr "" -"続いて、範囲指定と全文検索を組み合わせて検索します（1285858800は2010/10/1 " -"0:0:0の秒表記）。この場合もヒットします。::" - -msgid "" -"最後に、範囲指定と全文検索の順番を入れ替えて検索します。個々の条件は同じです" -"が、この場合はヒットしません。::" -msgstr "" -"最後に、範囲指定と全文検索の順番を入れ替えて検索します。個々の条件は同じです" -"が、この場合はヒットしません。::" - -msgid "どうしてこのような挙動になるかを説明します。" -msgstr "どうしてこのような挙動になるかを説明します。" - -msgid "原因" -msgstr "原因" - -msgid "" -"このような挙動になるのは全文検索時に複数の検索の挙動を使い分けているからで" -"す。ここでは簡単に説明するので、詳細は :doc:`/spec/search` を参照してくださ" -"い。" -msgstr "" -"このような挙動になるのは全文検索時に複数の検索の挙動を使い分けているからで" -"す。ここでは簡単に説明するので、詳細は :doc:`/spec/search` を参照してくださ" -"い。" - -msgid "検索の挙動には以下の3種類があります。" -msgstr "検索の挙動には以下の3種類があります。" - -msgid "完全一致検索" -msgstr "完全一致検索" - -msgid "非わかち書き検索" -msgstr "非わかち書き検索" - -msgid "部分一致検索" -msgstr "部分一致検索" - -msgid "" -"groongaは基本的に完全一致検索のみを行います。上記の例では「東京都民に深刻なダ" -"メージを与えました。」を「東京都」というクエリで検索していますが、TokenMecab" -"トークナイザーを使っている場合はこのクエリはマッチしません。" -msgstr "" -"groongaは基本的に完全一致検索のみを行います。上記の例では「東京都民に深刻なダ" -"メージを与えました。」を「東京都」というクエリで検索していますが、TokenMecab" -"トークナイザーを使っている場合はこのクエリはマッチしません。" - -msgid "検索対象の「東京都民に深刻なダメージを与えました。」は" -msgstr "検索対象の「東京都民に深刻なダメージを与えました。」は" - -msgid "東京 / 都民 / に / 深刻 / な / ダメージ / を / 与え / まし / た / 。" -msgstr "東京 / 都民 / に / 深刻 / な / ダメージ / を / 与え / まし / た / 。" - -msgid "とトークナイズされますが、クエリの「東京都」は" -msgstr "とトークナイズされますが、クエリの「東京都」は" - -msgid "東京 / 都" -msgstr "東京 / 都" - -msgid "とトークナイズされるため、完全一致しません。" -msgstr "とトークナイズされるため、完全一致しません。" - -msgid "" -"groongaは完全一致検索した結果のヒット件数が所定の閾値を超えない場合に限り、非" -"わかち書き検索を行い、それでもヒット件数が閾値を超えない場合は部分一致検索を" -"行います（閾値は1がデフォルト値となっています）。このケースのデータは部分一致" -"検索ではヒットするので、「東京都」クエリのみを指定するとヒットします。" -msgstr "" -"groongaは完全一致検索した結果のヒット件数が所定の閾値を超えない場合に限り、非" -"わかち書き検索を行い、それでもヒット件数が閾値を超えない場合は部分一致検索を" -"行います（閾値は1がデフォルト値となっています）。このケースのデータは部分一致" -"検索ではヒットするので、「東京都」クエリのみを指定するとヒットします。" - -msgid "" -"しかし、以下のように全文検索前にすでに閾値が越えている場合（「updated_at < " -"1285858800」で1件ヒットし、閾値を越える）は、たとえ完全一致検索で1件もヒット" -"しない場合でも部分一致検索などを行いません。::" -msgstr "" -"しかし、以下のように全文検索前にすでに閾値が越えている場合（「updated_at < " -"1285858800」で1件ヒットし、閾値を越える）は、たとえ完全一致検索で1件もヒット" -"しない場合でも部分一致検索などを行いません。::" - -msgid "" -"そのため、条件の順序を変えると検索結果が変わるという状況が発生します。以下" -"で、この情報を回避する方法を2種類紹介しますが、それぞれトレードオフとなる条件" -"があるので採用するかどうかを十分検討してください。" -msgstr "" -"そのため、条件の順序を変えると検索結果が変わるという状況が発生します。以下" -"で、この情報を回避する方法を2種類紹介しますが、それぞれトレードオフとなる条件" -"があるので採用するかどうかを十分検討してください。" - -msgid "対策方法1: トークナイザーを変更する" -msgstr "対策方法1: トークナイザーを変更する" - -msgid "" -"TokenMecabトークナイザーは事前に準備した辞書を用いてトークナイズするため、再" -"現率よりも適合率を重視したトークナイザーと言えます。一方、TokenBigramなど、N-" -"gram系のトークナイザーは適合率を重視したトークナイザーと言えます。例えば、" -"TokenMecabの場合「東京都」で「京都」に完全一致することはありませんが、" -"TokenBigramでは完全一致します。一方、TokenMecabでは「東京都民」に完全一致しま" -"せんが、TokenBigramでは完全一致します。" -msgstr "" -"TokenMecabトークナイザーは事前に準備した辞書を用いてトークナイズするため、再" -"現率よりも適合率を重視したトークナイザーと言えます。一方、TokenBigramなど、N-" -"gram系のトークナイザーは適合率を重視したトークナイザーと言えます。例えば、" -"TokenMecabの場合「東京都」で「京都」に完全一致することはありませんが、" -"TokenBigramでは完全一致します。一方、TokenMecabでは「東京都民」に完全一致しま" -"せんが、TokenBigramでは完全一致します。" - -msgid "" -"このようにN-gram系のトークナイザーを指定することにより再現率をあげることがで" -"きますが、適合率が下がり検索ノイズが含まれる可能性が高くなります。この度合い" -"を調整するためには :doc:`/reference/commands/select` のmatch_columnsで使用す" -"る索引毎に重み付けを指定します。" -msgstr "" -"このようにN-gram系のトークナイザーを指定することにより再現率をあげることがで" -"きますが、適合率が下がり検索ノイズが含まれる可能性が高くなります。この度合い" -"を調整するためには :doc:`/reference/commands/select` のmatch_columnsで使用す" -"る索引毎に重み付けを指定します。" - -msgid "" -"ここでも、前述の例を使って具体例を示します。まず、TokenBigramを用いた索引を追" -"加します。::" -msgstr "" -"ここでも、前述の例を使って具体例を示します。まず、TokenBigramを用いた索引を追" -"加します。::" - -msgid "" -"この状態でも以前はマッチしなかったレコードがヒットするようになります。::" -msgstr "" -"この状態でも以前はマッチしなかったレコードがヒットするようになります。::" - -msgid "" -"しかし、N-gram系のトークナイザーの方がTokenMecabトークナイザーよりも語のヒッ" -"ト数が多いため、N-gram系のヒットスコアの方が重く扱われてしまいます。N-gram系" -"のトークナイザーの方がTokenMecabトークナイザーよりも適合率の低い場合が多いの" -"で、このままでは検索ノイズが上位に表示される可能性が高くなります。" -msgstr "" -"しかし、N-gram系のトークナイザーの方がTokenMecabトークナイザーよりも語のヒッ" -"ト数が多いため、N-gram系のヒットスコアの方が重く扱われてしまいます。N-gram系" -"のトークナイザーの方がTokenMecabトークナイザーよりも適合率の低い場合が多いの" -"で、このままでは検索ノイズが上位に表示される可能性が高くなります。" - -msgid "" -"そこで、TokenMecabトークナイザーを使って作った索引の方をTokenBigramトークナイ" -"ザーを使って作った索引よりも重視するように重み付けを指定します。これは、" -"match_columnsオプションで指定できます。::" -msgstr "" -"そこで、TokenMecabトークナイザーを使って作った索引の方をTokenBigramトークナイ" -"ザーを使って作った索引よりも重視するように重み付けを指定します。これは、" -"match_columnsオプションで指定できます。::" - -msgid "" -"この場合はスコアが11になっています。内訳は、Terms.blog_body索引（TokenMecab" -"トークナイザーを使用）でマッチしたので10、Bigram.blog_body索引（TokenBigram" -"トークナイザーを使用）でマッチしたので3、これらを合計して13になっています。こ" -"のようにTokenMecabトークナイザーの重みを高くすることにより、検索ノイズが上位" -"にくることを抑えつつ再現率を上げることができます。" -msgstr "" -"この場合はスコアが11になっています。内訳は、Terms.blog_body索引（TokenMecab" -"トークナイザーを使用）でマッチしたので10、Bigram.blog_body索引（TokenBigram" -"トークナイザーを使用）でマッチしたので3、これらを合計して13になっています。こ" -"のようにTokenMecabトークナイザーの重みを高くすることにより、検索ノイズが上位" -"にくることを抑えつつ再現率を上げることができます。" - -msgid "" -"この例は日本語だったのでTokenBigramトークナイザーでよかったのですが、アルファ" -"ベットの場合はTokenBigramSplitSymbolAlphaトークナイザーなども利用する必要があ" -"ります。例えば、「楽しいbilliard」はTokenBigramトークナイザーでは" -msgstr "" -"この例は日本語だったのでTokenBigramトークナイザーでよかったのですが、アルファ" -"ベットの場合はTokenBigramSplitSymbolAlphaトークナイザーなども利用する必要があ" -"ります。例えば、「楽しいbilliard」はTokenBigramトークナイザーでは" - -msgid "楽し / しい / billiard" -msgstr "楽し / しい / billiard" - -msgid "" -"となり、「bill」では完全一致しません。一方、TokenBigramSplitSymbolAlphaトーク" -"ナイザーを使うと" -msgstr "" -"となり、「bill」では完全一致しません。一方、TokenBigramSplitSymbolAlphaトーク" -"ナイザーを使うと" - -msgid "楽し / しい / いb / bi / il / ll / li / ia / ar / rd / d" -msgstr "楽し / しい / いb / bi / il / ll / li / ia / ar / rd / d" - -msgid "となり、「bill」でも完全一致します。" -msgstr "となり、「bill」でも完全一致します。" - -msgid "" -"TokenBigramSplitSymbolAlphaトークナイザーを使う場合も重み付けを考慮する必要が" -"あることはかわりありません。" -msgstr "" -"TokenBigramSplitSymbolAlphaトークナイザーを使う場合も重み付けを考慮する必要が" -"あることはかわりありません。" - -msgid "利用できるバイグラム系のトークナイザーの一覧は以下の通りです。" -msgstr "利用できるバイグラム系のトークナイザーの一覧は以下の通りです。" - -msgid "" -"TokenBigram: バイグラムでトークナイズする。連続する記号・アルファベット・数字" -"は一語として扱う。" -msgstr "" -"TokenBigram: バイグラムでトークナイズする。連続する記号・アルファベット・数字" -"は一語として扱う。" - -msgid "" -"TokenBigramSplitSymbol: 記号もバイグラムでトークナイズする。連続するアルファ" -"ベット・数字は一語として扱う。" -msgstr "" -"TokenBigramSplitSymbol: 記号もバイグラムでトークナイズする。連続するアルファ" -"ベット・数字は一語として扱う。" - -msgid "" -"TokenBigramSplitSymbolAlpha: 記号とアルファベットもバイグラムでトークナイズす" -"る。連続する数字は一語として扱う。" -msgstr "" -"TokenBigramSplitSymbolAlpha: 記号とアルファベットもバイグラムでトークナイズす" -"る。連続する数字は一語として扱う。" - -msgid "" -"TokenBigramSplitSymbolAlphaDigit: 記号・アルファベット・数字もバイグラムで" -"トークナイズする。" -msgstr "" -"TokenBigramSplitSymbolAlphaDigit: 記号・アルファベット・数字もバイグラムで" -"トークナイズする。" - -msgid "" -"TokenBigramIgnoreBlank: バイグラムでトークナイズする。連続する記号・アルファ" -"ベット・数字は一語として扱う。空白は無視する。" -msgstr "" -"TokenBigramIgnoreBlank: バイグラムでトークナイズする。連続する記号・アルファ" -"ベット・数字は一語として扱う。空白は無視する。" - -msgid "" -"TokenBigramIgnoreBlankSplitSymbol: 記号もバイグラムでトークナイズする。連続す" -"るアルファベット・数字は一語として扱う。空白は無視する。" -msgstr "" -"TokenBigramIgnoreBlankSplitSymbol: 記号もバイグラムでトークナイズする。連続す" -"るアルファベット・数字は一語として扱う。空白は無視する。" - -msgid "" -"TokenBigramIgnoreBlankSplitSymbolAlpha: 記号とアルファベットもバイグラムで" -"トークナイズする。連続する数字は一語として扱う。空白は無視する。" -msgstr "" -"TokenBigramIgnoreBlankSplitSymbolAlpha: 記号とアルファベットもバイグラムで" -"トークナイズする。連続する数字は一語として扱う。空白は無視する。" - -msgid "" -"TokenBigramIgnoreBlankSplitSymbolAlphaDigit: 記号・アルファベット・数字もバイ" -"グラムでトークナイズする。空白は無視する。" -msgstr "" -"TokenBigramIgnoreBlankSplitSymbolAlphaDigit: 記号・アルファベット・数字もバイ" -"グラムでトークナイズする。空白は無視する。" - -msgid "対策方法2: 閾値をあげる" -msgstr "対策方法2: 閾値をあげる" - -msgid "" -"非わかち書き検索・部分一致検索を利用するかどうかの閾値は--with-match-" -"escalation-threshold configureオプションで変更することができます。以下のよう" -"に指定すると、100件以下のヒット数であれば、たとえ完全一致検索でヒットしても、" -"非わかち書き検索・部分一致検索を行います。::" -msgstr "" -"非わかち書き検索・部分一致検索を利用するかどうかの閾値は--with-match-" -"escalation-threshold configureオプションで変更することができます。以下のよう" -"に指定すると、100件以下のヒット数であれば、たとえ完全一致検索でヒットしても、" -"非わかち書き検索・部分一致検索を行います。::" - -msgid "" -"この場合も対策方法1同様、検索ノイズが上位に現れる可能性が高くなることに注意し" -"てください。検索ノイズが多くなった場合は指定する値を低くする必要があります。" -msgstr "" -"この場合も対策方法1同様、検索ノイズが上位に現れる可能性が高くなることに注意し" -"てください。検索ノイズが多くなった場合は指定する値を低くする必要があります。" - -msgid "How to avoid mmap Cannot allocate memory error" -msgstr "How to avoid mmap Cannot allocate memory error" - -msgid "Example" -msgstr "Example" - -msgid "There is a case following mmap error in log file:" -msgstr "There is a case following mmap error in log file:" - -msgid "" -"2013-06-04 08:19:34.835218|A|4e86e700|mmap(4194304,551,432017408)=Cannot " -"allocate memory <13036498944>" -msgstr "" -"2013-06-04 08:19:34.835218|A|4e86e700|mmap(4194304,551,432017408)=Cannot " -"allocate memory <13036498944>" - -msgid "" -"Note that <13036498944> means total size of mmap (almost 12GB) in this case." -msgstr "" -"Note that <13036498944> means total size of mmap (almost 12GB) in this case." - -msgid "Solution" -msgstr "Solution" - -msgid "So you need to confirm following point of views." -msgstr "So you need to confirm following point of views." - -msgid "Are there enough free memory?" -msgstr "Are there enough free memory?" - -msgid "Are maximum number of mappings exceeded?" -msgstr "Are maximum number of mappings exceeded?" - -msgid "To check there are enough free memory, you can use vmstat command." -msgstr "To check there are enough free memory, you can use vmstat command." - -msgid "" -"To check whether maximum number of mappings are exceeded, you can " -"investigate the value of vm.max_map_count." -msgstr "" -"To check whether maximum number of mappings are exceeded, you can " -"investigate the value of vm.max_map_count." - -msgid "" -"If this issue is fixed by modifying the value of vm.max_map_count, it's " -"exactly the reason." -msgstr "" -"If this issue is fixed by modifying the value of vm.max_map_count, it's " -"exactly the reason." - -msgid "" -"As groonga allocates memory chunks each 256KB, you can estimate the size of " -"database you can handle by following formula:" -msgstr "" -"As groonga allocates memory chunks each 256KB, you can estimate the size of " -"database you can handle by following formula:" - -msgid "(database size) = vm.max_map_count * (memory chunks)" -msgstr "(database size) = vm.max_map_count * (memory chunks)" - -msgid "" -"If you want to handle over 16GB groonga database, you must specify at least " -"65536 as the value of vm.max_map_count:" -msgstr "" -"If you want to handle over 16GB groonga database, you must specify at least " -"65536 as the value of vm.max_map_count:" - -msgid "database size (16GB) = vm.max_map_count (65536) * memory chunks (256KB)" -msgstr "" -"database size (16GB) = vm.max_map_count (65536) * memory chunks (256KB)" - -msgid "" -"You can modify vm.max_map_count temporary by sudo sysctl -w vm." -"max_map_count=65536." -msgstr "" -"You can modify vm.max_map_count temporary by sudo sysctl -w vm." -"max_map_count=65536." - -msgid "" -"Then save the configuration value to ``/etc/sysctl.conf`` or ``/etc/sysctl.d/" -"*.conf``." -msgstr "" - -msgid "" -"See :doc:`/reference/tuning` documentation about tuning related parameters." -msgstr "" -"See :doc:`/reference/tuning` documentation about tuning related parameters." Deleted: doc/locale/en/LC_MESSAGES/tutorial.po (+0 -2283) 100644 =================================================================== --- doc/locale/en/LC_MESSAGES/tutorial.po 2015-03-25 14:48:34 +0900 (ccebeaf) +++ /dev/null @@ -1,2283 +0,0 @@ -# -*- po -*- -# English translations for Groonga package. -# Copyright (C) 2009-2014, Brazil, Inc -# This file is distributed under the same license as the Groonga package. -# Kouhei Sutou <kou �� clear-code.com>, 2014. -# -msgid "" -msgstr "" -"Project-Id-Version: Groonga 4.0.1\n" -"Report-Msgid-Bugs-To: \n" -"PO-Revision-Date: 2014-09-26 12:04+0900\n" -"Last-Translator: Kouhei Sutou <kou �� clear-code.com>\n" -"Language-Team: English\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" - -msgid "Execution example::" -msgstr "Execution example::" - -msgid "Tutorial" -msgstr "Tutorial" - -msgid "Various data types" -msgstr "Various data types" - -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." - -msgid "Overview" -msgstr "Overview" - -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`." - -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." - -msgid "First, let's create a table for this tutorial." -msgstr "First, let's create a table for this tutorial." - -msgid "Boolean type" -msgstr "Boolean type" - -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." - -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." - -msgid "Numeric types" -msgstr "Numeric types" - -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." - -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." - -msgid "String types" -msgstr "String types" - -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." - -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." - -msgid "Date and time type" -msgstr "Date and time type" - -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." - -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." - -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." - -msgid "Longitude and latitude types" -msgstr "Longitude and latitude types" - -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:" - -msgid "" -"\"longitude x latitude\" in milliseconds (e.g.: \"128452975x503157902\")" -msgstr "" -"\"longitude x latitude\" in milliseconds (e.g.: \"128452975x503157902\")" - -msgid "\"longitude x latitude\" in degrees (e.g.: \"35.6813819x139.7660839\")" -msgstr "\"longitude x latitude\" in degrees (e.g.: \"35.6813819x139.7660839\")" - -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\"." - -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." - -msgid "Reference types" -msgstr "Reference types" - -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." - -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." - -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." - -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." - -msgid "Vector types" -msgstr "Vector types" - -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." - -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." - -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." - -msgid "Drilldown by ``domain`` column" -msgstr "Drilldown by ``domain`` column" - -msgid "Drilldown" -msgstr "Drilldown" - -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 "" - -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." - -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?\"." - -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``." - -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." - -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." - -msgid "Here is the concrete examples how to use this feature." -msgstr "Here is the concrete examples how to use this feature." - -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." - -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\"." - -msgid "Here is a summary of above query." -msgstr "Here is a summary of above query." - -msgid "Group by" -msgstr "Group by" - -msgid "The number of group records" -msgstr "The number of group records" - -msgid "Group records means following records" -msgstr "Group records means following records" - -msgid ".org" -msgstr ".org" - -msgid "3" -msgstr "3" - -msgid "http://example.org/" -msgstr "http://example.org/" - -msgid "http://example.org/aba" -msgstr "http://example.org/aba" - -msgid "http://example.org/gat" -msgstr "http://example.org/gat" - -msgid ".net" -msgstr ".net" - -msgid "http://example.net/" -msgstr "http://example.net/" - -msgid "http://example.net/afr" -msgstr "http://example.net/afr" - -msgid "http://example.net/atv" -msgstr "http://example.net/atv" - -msgid ".com" -msgstr ".com" - -msgid "http://example.com/" -msgstr "http://example.com/" - -msgid "http://example.com/rab" -msgstr "http://example.com/rab" - -msgid "http://example.com/vdw" -msgstr "http://example.com/vdw" - -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." - -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." - -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." - -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." - -msgid "Drilldown with multiple column" -msgstr "Drilldown with multiple column" - -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." - -msgid "Sorting drildown results" -msgstr "Sorting drildown results" - -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." - -msgid "limits drildown results" -msgstr "limits drildown results" - -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 "" - -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 "" - -msgid "Tag search and reverse resolution of reference relationships" -msgstr "" - -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 "" - -msgid "" -"Tag search is very fast because Groonga use inverted index as data structure." -msgstr "" - -msgid "Tag search" -msgstr "" - -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 "" - -msgid "Let's create tables for movie information, then search the movies." -msgstr "" - -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 "" - -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 "" - -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 "" - -msgid "List up the movies that specific keywords are given." -msgstr "" - -msgid "" -"You can search by tags such as \"Variety\", \"Sports\" and \"Animation\"." -msgstr "" - -msgid "Reverse resolution of reference relationships" -msgstr "" - -msgid "" -"Groonga supports indexes for reverse resolution among tables. Tag search is " -"one of concrete examples." -msgstr "" - -msgid "" -"For example, you can search friendships by reverse resolution in social " -"networking site." -msgstr "" - -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 "" - -msgid "Let's show list of users who contains specified user in friend list." -msgstr "" - -msgid "Then drilldown the count which shows user is listed as friend." -msgstr "" - -msgid "" -"As you can see, it shows the results which follows reverse resolution of " -"reference relationship." -msgstr "" - -msgid "Geo location search with index" -msgstr "" - -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 "" - -msgid "" -"These indexes are also used when sorting the records with geo location " -"search." -msgstr "" - -msgid "Basic operations" -msgstr "Basic operations" - -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." - -msgid "Create a database" -msgstr "Create a database" - -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." - -msgid "Form::" -msgstr "Form::" - -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." - -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." - -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." - -msgid "Operate a database" -msgstr "Operate a database" - -msgid "The following shows how to operate an existing database." -msgstr "The following shows how to operate an existing database." - -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." - -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." - -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." - -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." - -msgid "Command format" -msgstr "Command format" - -msgid "Commands for operating a database accept arguments as follows::" -msgstr "Commands for operating a database accept arguments as follows::" - -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." - -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." - -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." - -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`." - -msgid "Basic commands" -msgstr "Basic commands" - -msgid ":doc:`/reference/commands/status`" -msgstr ":doc:`/reference/commands/status`" - -msgid "shows status of a Groonga process." -msgstr "shows status of a Groonga process." - -msgid ":doc:`/reference/commands/table_list`" -msgstr ":doc:`/reference/commands/table_list`" - -msgid "shows a list of tables in a database." -msgstr "shows a list of tables in a database." - -msgid ":doc:`/reference/commands/column_list`" -msgstr ":doc:`/reference/commands/column_list`" - -msgid "shows a list of columns in a table." -msgstr "shows a list of columns in a table." - -msgid ":doc:`/reference/commands/table_create`" -msgstr ":doc:`/reference/commands/table_create`" - -msgid "adds a table to a database." -msgstr "adds a table to a database." - -msgid ":doc:`/reference/commands/column_create`" -msgstr ":doc:`/reference/commands/column_create`" - -msgid "adds a column to a table." -msgstr "adds a column to a table." - -msgid ":doc:`/reference/commands/select`" -msgstr ":doc:`/reference/commands/select`" - -msgid "searches records from a table and shows the result." -msgstr "searches records from a table and shows the result." - -msgid ":doc:`/reference/commands/load`" -msgstr ":doc:`/reference/commands/load`" - -msgid "inserts records to a table." -msgstr "inserts records to a table." - -msgid "Create a table" -msgstr "Create a table" - -msgid "A :doc:`/reference/commands/table_create` command creates a new table." -msgstr "A :doc:`/reference/commands/table_create` command creates a new table." - -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." - -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." - -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." - -msgid "" -"The second element of the result indicates that the operation succeeded." -msgstr "" -"The second element of the result indicates that the operation succeeded." - -msgid "View a table" -msgstr "View a table" - -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." - -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." - -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." - -msgid "Create a column" -msgstr "Create a column" - -msgid "" -"A :doc:`/reference/commands/column_create` command creates a new column." -msgstr "" -"A :doc:`/reference/commands/column_create` command creates a new column." - -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." - -msgid "Load records" -msgstr "Load records" - -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." - -msgid "The following example loads nine records into the Site table." -msgstr "The following example loads nine records into the Site table." - -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." - -msgid "Let's make sure that these records are correctly stored." -msgstr "Let's make sure that these records are correctly stored." - -msgid "Get a record" -msgstr "Get a record" - -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." - -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." - -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." - -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/\"." - -msgid "Create a lexicon table for full text search" -msgstr "Create a lexicon table for full text search" - -msgid "Let's go on to how to make full text search." -msgstr "Let's go on to how to make full text search." - -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." - -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." - -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." - -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." - -msgid "Create an index column for full text search" -msgstr "Create an index column for full text search" - -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." - -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." - -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." - -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." - -msgid "Full text search" -msgstr "Full text search" - -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." - -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." - -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." - -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. [#]_" - -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." - -msgid "Specify output columns" -msgstr "Specify output columns" - -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 (',')." - -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." - -msgid "Specify output ranges" -msgstr "Specify output ranges" - -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." - -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." - -msgid "Sort a search result" -msgstr "Sort a search result" - -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." - -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." - -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." - -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." - -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." - -msgid "footnote" -msgstr "footnote" - -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." - -msgid "Additional information about lexicon for full text search" -msgstr "" - -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 "" - -msgid "TODO: Write document." -msgstr "" - -msgid "match_columns parameter" -msgstr "" - -msgid "Full-text search against multiple columns" -msgstr "" - -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 "" - -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 "" - -msgid "Creating column index against each column" -msgstr "" - -msgid "Here is the example which create column index against each column." -msgstr "" - -msgid "" -"First, create ``Blog1`` table, add ``title`` column which stores title " -"string, ``message`` column which stores content of blog entry." -msgstr "" - -msgid "" -"Then create ``IndexBlog1`` table for column indexes, add ``index_title`` " -"column for ``title`` column, ``index_message`` column for ``message`` column." -msgstr "" - -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 "" - -msgid "Let's try to search blog entries." -msgstr "" - -msgid "Creating one column index against multiple columns" -msgstr "" - -msgid "Groonga also supports one column index against multiple columns." -msgstr "" - -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 "" - -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 "" - -msgid "" -"Let's search same query in previous section. You can get same search results." -msgstr "" - -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." - -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." - -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." - -msgid "Full text search with specific index name" -msgstr "" - -msgid "TODO" -msgstr "" - -msgid "Nested index search among related table by column index" -msgstr "Nested index search among related table by column index" - -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." - -msgid "Here is the concrete example." -msgstr "Here is the concrete example." - -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." - -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." - -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." - -msgid "Here is the sample schema." -msgstr "Here is the sample schema." - -msgid "Here is the sample data." -msgstr "Here is the sample data." - -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." - -msgid "Query for searching the records described above::" -msgstr "Query for searching the records described above::" - -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." - -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.)" - -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." - -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." - -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." - -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." - -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." - -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." - -msgid "Indexes with Weight" -msgstr "" - -msgid "Let's create micro-blog" -msgstr "" - -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 "" - -msgid "Let's create table." -msgstr "" - -msgid "Users table" -msgstr "" - -msgid "" -"This is the table which stores user information. It stores name of user, " -"profile, list of follower and so on." -msgstr "" - -msgid "User ID" -msgstr "" - -msgid "``_key``" -msgstr "``_key``" - -msgid "User name" -msgstr "" - -msgid "``name``" -msgstr "``name``" - -msgid "List of following users" -msgstr "" - -msgid "``follower``" -msgstr "``follower``" - -msgid "List of favorite comments" -msgstr "" - -msgid "``favorites``" -msgstr "``favorites``" - -msgid "Current location of user (geolocation)" -msgstr "" - -msgid "``location``" -msgstr "``location``" - -msgid "Current location of user (string)" -msgstr "" - -msgid "``location_str``" -msgstr "``location_str``" - -msgid "User profile" -msgstr "" - -msgid "``description``" -msgstr "``description``" - -msgid "" -"Indexes for ``follower`` column in ``Users`` table. With this indexes, you " -"can search users who follows the person." -msgstr "" - -msgid "``followee``" -msgstr "``followee``" - -msgid "Comments table" -msgstr "" - -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 "" - -msgid "Comment ID" -msgstr "" - -msgid "Content of comment" -msgstr "" - -msgid "``comment``" -msgstr "``comment``" - -msgid "Posted date" -msgstr "" - -msgid "``last_modified``" -msgstr "``last_modified``" - -msgid "Comment which you reply to someone" -msgstr "" - -msgid "``replied_to``" -msgstr "``replied_to``" - -msgid "List of users who you reply to" -msgstr "" - -msgid "``replied_users``" -msgstr "``replied_users``" - -msgid "List of hash tags about comment" -msgstr "" - -msgid "``hash_tags``" -msgstr "``hash_tags``" - -msgid "Posted place (for geolocation)" -msgstr "" - -msgid "Person who write comment" -msgstr "" - -msgid "``posted_by``" -msgstr "``posted_by``" - -msgid "" -"Indexes for ``favorites`` column in ``Users`` table. With this indexes, you " -"can search the person who mark comment as favorite one." -msgstr "" - -msgid "``favorited_by``" -msgstr "``favorited_by``" - -msgid "HashTags table" -msgstr "" - -msgid "This is the table which stores hash tags for comments." -msgstr "" - -msgid "Hash tag" -msgstr "" - -msgid "" -"Indexes for ``Comments.hash_tags``. With this indexes, you can search list " -"of comments with specified hash tags." -msgstr "" - -msgid "``hash_index``" -msgstr "``hash_index``" - -msgid "Bigram table" -msgstr "" - -msgid "" -"This is the table which stores indexes for full text search by user " -"information or comments." -msgstr "" - -msgid "Word" -msgstr "" - -msgid "" -"Indexes of user information. This column contains indexes of user name " -"(``Users.name``), current location (``Users.location_str``), profile " -"(``Users.description``)." -msgstr "" - -msgid "``users_index``" -msgstr "``users_index``" - -msgid "Indexes about content of comments (``Comments.comment``)." -msgstr "" - -msgid "``comment_index``" -msgstr "``comment_index``" - -msgid "GeoIndex table" -msgstr "GeoIndex table" - -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." - -msgid "Indexes of location column for Users table" -msgstr "Indexes of location column for Users table" - -msgid "``users_location``" -msgstr "``users_location``" - -msgid "Indexes of location column for Comments table" -msgstr "Indexes of location column for Comments table" - -msgid "``comments_location``" -msgstr "``comments_location``" - -msgid "Loading data" -msgstr "" - -msgid "Then, load example data." -msgstr "" - -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 "" - -msgid "" -"``location`` column in ``Users`` table, ``location`` column in ``Comments`` " -"table use GeoPoint type. This type accepts \"[latitude]x[longitude]\"." -msgstr "" - -msgid "``last_modified`` column in ``Comments`` table use Time type." -msgstr "" - -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 "" - -msgid "Search" -msgstr "" - -msgid "Let's search micro-blog." -msgstr "" - -msgid "Search users by keyword" -msgstr "" - -msgid "" -"In this section, we search micro-blog against multiple column by keyword. " -"See :doc:`match_columns` to search multiple column at once." -msgstr "" - -msgid "" -"Let's search user from micro-blog's user name, location, description entries." -msgstr "" - -msgid "" -"By using \"New York\" as searching keyword for user, \"Bob\" who lives in " -"\"New York\" is listed in search result." -msgstr "" - -msgid "Search users by geolocation data (GeoPoint)" -msgstr "" - -msgid "" -"In this section, we search users by column data which use type of GeoPoint. " -"See :doc:`search` about GeoPoint column." -msgstr "" - -msgid "" -"Following example searches users who live in within 20km from specified " -"location." -msgstr "" - -msgid "" -"It shows that \"Bob\" and \"Charlie\" lives in within 20 km from station of " -"\"Grand Central Terminal\"." -msgstr "" - -msgid "Search users who follows specific user" -msgstr "" - -msgid "" -"In this section, we do reverse resolution of reference relationships which " -"is described at :doc:`index`." -msgstr "" - -msgid "" -"Following examples shows reverse resolution about ``follower`` column of " -"``Users`` table." -msgstr "" - -msgid "It shows that \"Alice\" and \"Charlie\" follows \"Bob\"." -msgstr "" - -msgid "Search comments by using the value of GeoPoint type" -msgstr "" - -msgid "" -"In this section, we search comments which are written within specific " -"location." -msgstr "" - -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 "" - -msgid "" -"Above query searches comments which are posted within 20 km from Central " -"Park in city of New York." -msgstr "" - -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 "" - -msgid "Search comments by keyword" -msgstr "" - -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 "" - -msgid "" -"By using 'Now' as a keyword, above query returns 2 comments. It also " -"contains count of 'Now' as the value of `_score`." -msgstr "" - -msgid "Search comments by keyword and geolocation" -msgstr "" - -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 "" - -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 "" - -msgid "Search comments by hash tags" -msgstr "" - -msgid "" -"In this section, we search comments which contains specific hash tags. Let's " -"use reverse resolution of reference relationships." -msgstr "" - -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 "" - -msgid "Search comments by user id" -msgstr "" - -msgid "In this section, we search comments which are posted by specific user." -msgstr "" - -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 "" - -msgid "Search user's favorite comments" -msgstr "" - -msgid "In this section, we search user's favorite comments." -msgstr "" - -msgid "Above query returns Bob's favorite comments." -msgstr "" - -msgid "Search comments by posted time" -msgstr "" - -msgid "" -"In this section, we search comments by posted time. See type of `Time` in :" -"doc:`data`." -msgstr "" - -msgid "Let's search comments that posted time are older than specified time." -msgstr "" - -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 "" - -msgid "Remote access" -msgstr "Remote access" - -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." - -msgid "Groonga Query Transfer Protocol (GQTP)" -msgstr "Groonga Query Transfer Protocol (GQTP)" - -msgid "How to run a GQTP server" -msgstr "How to run a GQTP server" - -msgid "" -"Groonga has a special protocol, named Groonga Query Transfer Protocol " -"(GQTP), for remote access to a database. The following form shows how to run " -"Groonga as a GQTP server." -msgstr "" -"Groonga has a special protocol, named Groonga Query Transfer Protocol " -"(GQTP), for remote access to a database. The following form shows how to run " ... truncated to 1.0MB
