# -*- po -*-
# English translations for Mroonga package.
# Copyright (C) 2009-2026, Mroonga Project
# This file is distributed under the same license as the Mroonga package.
# Automatically generated, 2026.
#
msgid ""
msgstr ""
"Project-Id-Version: Mroonga mrn_version\n"
"Report-Msgid-Bugs-To: \n"
"PO-Revision-Date: 2026-03-30 08:04+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\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 "Wrapper mode"
msgstr "Wrapper mode"

msgid "Here we explain how to use wrapper mode of Mroonga"
msgstr "Here we explain how to use wrapper mode of Mroonga"

msgid "Dropped support wrapper mode with MySQL 8.0 or later."
msgstr "Dropped support wrapper mode with MySQL 8.0 or later."

msgid "How to use wrapper mode"
msgstr "How to use wrapper mode"

msgid ""
"In wrapper mode, Mroonga works in wrapping an existing storage engine. To "
"specify the wrapped storage engine, we use SQL comment like ``COMMENT = "
"'engine \"InnoDB\"'`` for now."
msgstr ""
"In wrapper mode, Mroonga works in wrapping an existing storage engine. To "
"specify the wrapped storage engine, we use SQL comment like ``COMMENT = "
"'engine \"InnoDB\"'`` for now."

msgid ""
"For now, a primary key is mandatory in wrapper mode. That is not the case "
"with storage mode."
msgstr ""
"For now, a primary key is mandatory in wrapper mode. That is not the case "
"with storage mode."

msgid ""
"Wrapper mode supports the followings, that are not supported in storage mode "
"for now."
msgstr ""
"Wrapper mode supports the followings, that are not supported in storage mode "
"for now."

msgid "null value"
msgstr "null value"

msgid ""
"transaction (if storage engine supports. Note that rollback causes mismatch "
"of indexes, it may affects search results, so recreate index of Mroonga in "
"such a case.)"
msgstr ""
"transaction (if storage engine supports. Note that rollback causes mismatch "
"of indexes, it may affects search results, so recreate index of Mroonga in "
"such a case.)"

msgid "How to use full text search"
msgstr "How to use full text search"

msgid ""
"After confirming the installation, let's create a table. The important point "
"is to specify Mroonga by ``ENGINE = Mroonga``. ::"
msgstr ""
"After confirming the installation, let's create a table. The important point "
"is to specify Mroonga by ``ENGINE = Mroonga``. ::"

msgid "We put data by INSERT. ::"
msgstr "We put data by INSERT. ::"

msgid "Try full text search. ::"
msgstr "Try full text search. ::"

msgid "Yes, full text search works."
msgstr "Yes, full text search works."

msgid "How to get search score"
msgstr "How to get search score"

msgid ""
"We often want to display more relevant results first in full text search. We "
"use search score in such case."
msgstr ""
"We often want to display more relevant results first in full text search. We "
"use search score in such case."

msgid ""
"We can get search score by MySQL's standard way [#score]_, i.e. we use "
"MATCH...AGAINST in one of columns in SELECT or ORDER BY."
msgstr ""
"We can get search score by MySQL's standard way [#score]_, i.e. we use "
"MATCH...AGAINST in one of columns in SELECT or ORDER BY."

msgid "Let's try. ::"
msgstr "Let's try. ::"

msgid ""
"The result having the search word ``fine`` more, i.e. ``id = 3`` message "
"having the higher search score, is displayed first. And you also get search "
"score by using MATCH AGAINST in SELECT phrase."
msgstr ""
"The result having the search word ``fine`` more, i.e. ``id = 3`` message "
"having the higher search score, is displayed first. And you also get search "
"score by using MATCH AGAINST in SELECT phrase."

msgid "You can use ``AS`` to change the attribute name. ::"
msgstr "You can use ``AS`` to change the attribute name. ::"

msgid "How to specify the parser for full text search"
msgstr "How to specify the parser for full text search"

msgid ""
"MySQL has the following syntax to specify the parser [#parser]_ for full "
"text search. ::"
msgstr ""
"MySQL has the following syntax to specify the parser [#parser]_ for full "
"text search. ::"

msgid ""
"To use this syntax, you need to register all parsers in MySQL beforehand. On "
"the other hand, Groonga can dynamically add a tokenizer, that is a parser in "
"MySQL. So if use this syntax in Mroonga, tokenizers that are added in "
"Groonga dynamically cannot be supported. We think that this limitation "
"decreases the convenience, and we choose our own syntax using COMMENT like "
"the following. ::"
msgstr ""
"To use this syntax, you need to register all parsers in MySQL beforehand. On "
"the other hand, Groonga can dynamically add a tokenizer, that is a parser in "
"MySQL. So if use this syntax in Mroonga, tokenizers that are added in "
"Groonga dynamically cannot be supported. We think that this limitation "
"decreases the convenience, and we choose our own syntax using COMMENT like "
"the following. ::"

msgid ""
"``COMMENT`` in ``FULLTEXT INDEX`` is only supported MySQL 5.5 or later. If "
"you use MySQL 5.1, use ``mroonga_default_parser`` variable described below."
msgstr ""
"``COMMENT`` in ``FULLTEXT INDEX`` is only supported MySQL 5.5 or later. If "
"you use MySQL 5.1, use ``mroonga_default_parser`` variable described below."

msgid "You can specify one of following values as the tokenizer."
msgstr "You can specify one of following values as the tokenizer."

msgid "Available tokenizers"
msgstr "Available tokenizers"

msgid "Tokenizer"
msgstr "Tokenizer"

msgid "Description"
msgstr "Description"

msgid "``off``"
msgstr "``off``"

msgid ""
"(``Deprecated``) It does not tokenize at all. Use ``off`` if you want to "
"treat ``content`` as is. For example, this value is used for prefix search."
msgstr ""
"(``Deprecated``) It does not tokenize at all. Use ``off`` if you want to "
"treat ``content`` as is. For example, this value is used for prefix search."

msgid "``none``"
msgstr "``none``"

msgid ""
"It does not tokenize at all. Use ``none`` if you want to treat ``content`` "
"as is. For example, this value is used for prefix search."
msgstr ""
"It does not tokenize at all. Use ``none`` if you want to treat ``content`` "
"as is. For example, this value is used for prefix search."

msgid "``TokenBigram``"
msgstr "``TokenBigram``"

msgid ""
"It tokenises in bigram. But continuous alphabets, numbers or symbols are "
"treated as a token. So there can exist tokes with 3 letters or more. It is "
"to reduce noises."
msgstr ""
"It tokenises in bigram. But continuous alphabets, numbers or symbols are "
"treated as a token. So there can exist tokes with 3 letters or more. It is "
"to reduce noises."

msgid "This is the default value."
msgstr "This is the default value."

msgid "``TokenMecab``"
msgstr "``TokenMecab``"

msgid "It tokenises using MeCab. Groonga should be built with MeCab support."
msgstr "It tokenises using MeCab. Groonga should be built with MeCab support."

msgid "``TokenBigramSplitSymbol``"
msgstr "``TokenBigramSplitSymbol``"

msgid ""
"It tokenises in bigram. Unlike ``TokenBigram``, continuous symbols are not "
"treated as a token, but tokenised in bigram."
msgstr ""
"It tokenises in bigram. Unlike ``TokenBigram``, continuous symbols are not "
"treated as a token, but tokenised in bigram."

msgid ""
"When you use ``TokenBigramSplitSymbol`` instead of ``TokenBigram``, ``\"!?"
"\"`` can match ``\"!?!?!?\"`` in ``\"Is it really!?!?!?\"``. But when you "
"use ``TokenBigram``, only ``\"!?!?!?\"`` can match as well."
msgstr ""
"When you use ``TokenBigramSplitSymbol`` instead of ``TokenBigram``, ``\"!?"
"\"`` can match ``\"!?!?!?\"`` in ``\"Is it really!?!?!?\"``. But when you "
"use ``TokenBigram``, only ``\"!?!?!?\"`` can match as well."

msgid "``TokenBigramSplitSymbolAlpha``"
msgstr "``TokenBigramSplitSymbolAlpha``"

msgid ""
"It tokenise in bigram. In addition to ``TokenBigramSplitSymbol``, continuous "
"alphabets are not treated as a token either, but tokenised in bigram."
msgstr ""
"It tokenise in bigram. In addition to ``TokenBigramSplitSymbol``, continuous "
"alphabets are not treated as a token either, but tokenised in bigram."

msgid ""
"When you use ``TokenBigramSplitSymbolAlpha`` instead of ``TokenBigram``, "
"``\"real\"`` can match ``\"Is it really?\"``. But when you use "
"``TokenBigram``, only ``\"really\"`` can match as well."
msgstr ""
"When you use ``TokenBigramSplitSymbolAlpha`` instead of ``TokenBigram``, "
"``\"real\"`` can match ``\"Is it really?\"``. But when you use "
"``TokenBigram``, only ``\"really\"`` can match as well."

msgid "``TokenBigramSplitSymbolAlphaDigit``"
msgstr "``TokenBigramSplitSymbolAlphaDigit``"

msgid ""
"It tokenise in bigram. In addition to ``TokenBigramSplitSymbolAlpha``, "
"continuous numbers are not treated as a token either, but tokenised in "
"bigram. So any kind of characters are treated equally in bigram."
msgstr ""
"It tokenise in bigram. In addition to ``TokenBigramSplitSymbolAlpha``, "
"continuous numbers are not treated as a token either, but tokenised in "
"bigram. So any kind of characters are treated equally in bigram."

msgid ""
"When you use ``TokenBigramSplitSymbolAlphaDigit`` instead of "
"``TokenBigram``, ``\"567\"`` can match ``\"090-0123-4567\"``. But when you "
"use ``TokenBigram``, only ``\"4567\"`` can match as well."
msgstr ""
"When you use ``TokenBigramSplitSymbolAlphaDigit`` instead of "
"``TokenBigram``, ``\"567\"`` can match ``\"090-0123-4567\"``. But when you "
"use ``TokenBigram``, only ``\"4567\"`` can match as well."

msgid "``TokenBigramIgnoreBlank``"
msgstr "``TokenBigramIgnoreBlank``"

msgid "It tokenise in bigram. Unlike ``TokenBigram``, it ignores white spaces."
msgstr ""
"It tokenise in bigram. Unlike ``TokenBigram``, it ignores white spaces."

msgid ""
"When you use ``TokenBigramIgnoreBlank`` instead of ``TokenBigram``, ``\"みな"
"さん\"`` can match ``\"み な さ ん 注 目\"``. But when you use "
"``TokenBigram``, only ``\"み な さ ん\"`` can match as well."
msgstr ""
"When you use ``TokenBigramIgnoreBlank`` instead of ``TokenBigram``, ``\"みな"
"さん\"`` can match ``\"み な さ ん 注 目\"``. But when you use "
"``TokenBigram``, only ``\"み な さ ん\"`` can match as well."

msgid "``TokenBigramIgnoreBlankSplitSymbol``"
msgstr "``TokenBigramIgnoreBlankSplitSymbol``"

msgid ""
"It tokenise in bigram. Unlike ``TokenBigramSplitSymbol``, it ignores white "
"spaces."
msgstr ""
"It tokenise in bigram. Unlike ``TokenBigramSplitSymbol``, it ignores white "
"spaces."

msgid ""
"When you use ``TokenBigramIgnoreBlankSplitSymbol`` instead of "
"``TokenBigramSplitSymbol``, ``\"???\"`` can match ``\"! ? ???\"``. But when "
"you use ``TokenBigramSplitSymbol``, only ``\"? ??\"`` can match as well."
msgstr ""
"When you use ``TokenBigramIgnoreBlankSplitSymbol`` instead of "
"``TokenBigramSplitSymbol``, ``\"???\"`` can match ``\"! ? ???\"``. But when "
"you use ``TokenBigramSplitSymbol``, only ``\"? ??\"`` can match as well."

msgid "``TokenBigramIgnoreBlankSplitSymbolAlpha``"
msgstr "``TokenBigramIgnoreBlankSplitSymbolAlpha``"

msgid ""
"It tokenise in bigram. Unlike ``TokenBigramSplitSymbolAlpha``, it ignores "
"white spaces."
msgstr ""
"It tokenise in bigram. Unlike ``TokenBigramSplitSymbolAlpha``, it ignores "
"white spaces."

msgid ""
"When you use ``TokenBigramIgnoreBlankSplitSymbolAlpha`` instead of "
"``TokenBigramSplitSymbolAlpha``, ``\"ama\"`` can match ``\"I am a pen.\"``. "
"But when you use ``TokenBigramSplitSymbolAlpha``, only ``\"am a\"`` can "
"match as well."
msgstr ""
"When you use ``TokenBigramIgnoreBlankSplitSymbolAlpha`` instead of "
"``TokenBigramSplitSymbolAlpha``, ``\"ama\"`` can match ``\"I am a pen.\"``. "
"But when you use ``TokenBigramSplitSymbolAlpha``, only ``\"am a\"`` can "
"match as well."

msgid "``TokenBigramIgnoreBlankSplitSymbolAlphaDigit``"
msgstr "``TokenBigramIgnoreBlankSplitSymbolAlphaDigit``"

msgid ""
"It tokenise in bigram. Unlike ``TokenBigramSplitSymbolAlphaDigit``, it "
"ignores white spaces."
msgstr ""
"It tokenise in bigram. Unlike ``TokenBigramSplitSymbolAlphaDigit``, it "
"ignores white spaces."

msgid ""
"When you use ``TokenBigramIgnoreBlankSplitSymbolAlphaDigit`` instead of "
"``TokenBigramSplitSymbolAlphaDigit``, ``\"9001\"`` can match ``\"090 0123 "
"4567\"``. But when you use ``TokenBigramSplitSymbolAlphaDigit``, only ``\"90 "
"01\"`` can match as well."
msgstr ""
"When you use ``TokenBigramIgnoreBlankSplitSymbolAlphaDigit`` instead of "
"``TokenBigramSplitSymbolAlphaDigit``, ``\"9001\"`` can match ``\"090 0123 "
"4567\"``. But when you use ``TokenBigramSplitSymbolAlphaDigit``, only ``\"90 "
"01\"`` can match as well."

msgid "``TokenDelimit``"
msgstr "``TokenDelimit``"

msgid "It tokenise by splitting with a white space."
msgstr "It tokenise by splitting with a white space."

msgid ""
"``\"movie horror topic\"`` will be tokenised as ``\"movie\"``, "
"``\"horror\"``, ``\"topic\"``."
msgstr ""
"``\"movie horror topic\"`` will be tokenised as ``\"movie\"``, "
"``\"horror\"``, ``\"topic\"``."

msgid "``TokenDelimitNull``"
msgstr "``TokenDelimitNull``"

msgid "It tokenise by splitting with a null character (``\\\\0``)."
msgstr "It tokenise by splitting with a null character (``\\\\0``)."

msgid ""
"``\"movie\\\\0horror\\\\0topic\"`` will be tokenised as ``\"movie\"``, "
"``\"horror\"``, ``\"topic\"``."
msgstr ""
"``\"movie\\\\0horror\\\\0topic\"`` will be tokenised as ``\"movie\"``, "
"``\"horror\"``, ``\"topic\"``."

msgid "``TokenUnigram``"
msgstr "``TokenUnigram``"

msgid ""
"It tokenises in unigram. But continuous alphabets, numbers or symbols are "
"treated as a token. So there can exist tokes with 2 letters or more. It is "
"to reduce noises."
msgstr ""
"It tokenises in unigram. But continuous alphabets, numbers or symbols are "
"treated as a token. So there can exist tokes with 2 letters or more. It is "
"to reduce noises."

msgid "``TokenTrigram``"
msgstr "``TokenTrigram``"

msgid ""
"It tokenises in trigram. But continuous alphabets, numbers or symbols are "
"treated as a token. So there can exist tokes with 4 letters or more. It is "
"to reduce noises."
msgstr ""
"It tokenises in trigram. But continuous alphabets, numbers or symbols are "
"treated as a token. So there can exist tokes with 4 letters or more. It is "
"to reduce noises."

msgid ""
"You can specify the default tokenizer by passing ``--with-default-"
"tokenizer`` option in ``configure`` when you build Mroonga. ::"
msgstr ""
"You can specify the default tokenizer by passing ``--with-default-"
"tokenizer`` option in ``configure`` when you build Mroonga. ::"

msgid ""
"Or you can set ``mroonga_default_tokenizer`` variable in my.cnf or by SQL. "
"If you specify it in my.cnf, the change will not be lost after restarting "
"MySQL, but you need to restart MySQL to make it effective. On the other "
"hand, if you set it in SQL, the change is effective immediately, but it will "
"be lost when you restart MySQL."
msgstr ""
"Or you can set ``mroonga_default_tokenizer`` variable in my.cnf or by SQL. "
"If you specify it in my.cnf, the change will not be lost after restarting "
"MySQL, but you need to restart MySQL to make it effective. On the other "
"hand, if you set it in SQL, the change is effective immediately, but it will "
"be lost when you restart MySQL."

msgid "my.cnf::"
msgstr "my.cnf::"

msgid "SQL::"
msgstr "SQL::"

msgid "How to specify the normalizer"
msgstr "How to specify the normalizer"

msgid ""
"Mroonga uses normalizer corresponding to the encoding of document. It is "
"used when tokenizing text and storing table key."
msgstr ""
"Mroonga uses normalizer corresponding to the encoding of document. It is "
"used when tokenizing text and storing table key."

msgid ""
"It is used ``NormalizerMySQLGeneralCI`` normalizer when the encoding is "
"``utf8_general_ci`` or ``utf8mb4_general_ci``."
msgstr ""
"It is used ``NormalizerMySQLGeneralCI`` normalizer when the encoding is "
"``utf8_general_ci`` or ``utf8mb4_general_ci``."

msgid ""
"It is used ``NormalizerMySQLUnicodeCI`` normalizer when the encoding is "
"``utf8_unicode_ci`` or ``utf8mb4_unicode_ci``."
msgstr ""
"It is used ``NormalizerMySQLUnicodeCI`` normalizer when the encoding is "
"``utf8_unicode_ci`` or ``utf8mb4_unicode_ci``."

msgid "It isn't used normalizer when the encoding is ``utf8_bin``."
msgstr "It isn't used normalizer when the encoding is ``utf8_bin``."

msgid ""
"Here is an example that uses ``NormalizerMySQLUnicodeCI`` normalizer by "
"specifying ``utf8_unicode_ci``.::"
msgstr ""
"Here is an example that uses ``NormalizerMySQLUnicodeCI`` normalizer by "
"specifying ``utf8_unicode_ci``.::"

msgid "Mroonga has the following syntax to specify Groonga's normalizer::"
msgstr "Mroonga has the following syntax to specify Groonga's normalizer::"

msgid ""
"See `Groonga's documentation about normalizer <https://groonga.org/docs/"
"reference/normalizers.html>`_ for more details."
msgstr ""
"See `Groonga's documentation about normalizer <https://groonga.org/docs/"
"reference/normalizers.html>`_ for more details."

msgid "Here is an example that uses ``NormalizerAuto`` normalizer::"
msgstr "Here is an example that uses ``NormalizerAuto`` normalizer::"

msgid "How to get snippet (Keyword in context)"
msgstr "How to get snippet (Keyword in context)"

msgid ""
"Mroonga provides functionality to get keyword in context. It is implemented "
"as :doc:`/reference/udf/mroonga_snippet` UDF."
msgstr ""
"Mroonga provides functionality to get keyword in context. It is implemented "
"as :doc:`/reference/udf/mroonga_snippet` UDF."

msgid "Logging"
msgstr "Logging"

msgid "Mroonga outputs the logs by default."
msgstr "Mroonga outputs the logs by default."

msgid ""
"Log files are located in MySQL's data directory with the filename  ``groonga."
"log``."
msgstr ""
"Log files are located in MySQL's data directory with the filename  ``groonga."
"log``."

msgid "Here is the example of the log. ::"
msgstr "Here is the example of the log. ::"

msgid ""
"The default log level is NOTICE, i.e. we have important information only and "
"we don't have debug information etc.)."
msgstr ""
"The default log level is NOTICE, i.e. we have important information only and "
"we don't have debug information etc.)."

msgid ""
"You can get the log level by ``mroonga_log_level`` system variable, that is "
"a global variable. You can also modify it dynamically by using SET phrase. ::"
msgstr ""
"You can get the log level by ``mroonga_log_level`` system variable, that is "
"a global variable. You can also modify it dynamically by using SET phrase. ::"

msgid "Available log levels are the followings."
msgstr "Available log levels are the followings."

msgid "NONE"
msgstr "NONE"

msgid "EMERG"
msgstr "EMERG"

msgid "ALERT"
msgstr "ALERT"

msgid "CRIT"
msgstr "CRIT"

msgid "ERROR"
msgstr "ERROR"

msgid "WARNING"
msgstr "WARNING"

msgid "NOTICE"
msgstr "NOTICE"

msgid "INFO"
msgstr "INFO"

msgid "DEBUG"
msgstr "DEBUG"

msgid "DUMP"
msgstr "DUMP"

msgid "See :ref:`server-variable-mroonga-log-level` about details."
msgstr "See :ref:`server-variable-mroonga-log-level` about details."

msgid ""
"You can reopen the log file by FLUSH LOGS. If you want to rotate the log "
"file without stopping MySQL server, you can do in the following procedure."
msgstr ""
"You can reopen the log file by FLUSH LOGS. If you want to rotate the log "
"file without stopping MySQL server, you can do in the following procedure."

msgid ""
"change the file name of ``groonga.log`` (by using OS's mv command etc.)."
msgstr ""
"change the file name of ``groonga.log`` (by using OS's mv command etc.)."

msgid ""
"invoke \"FLUSH LOGS\" in MySQL server (by mysql command or mysqladmin "
"command)."
msgstr ""
"invoke \"FLUSH LOGS\" in MySQL server (by mysql command or mysqladmin "
"command)."

msgid "Next step"
msgstr "Next step"

msgid ""
"Now, you can use Mroonga as wrapper mode! If you want Mroonga to be faster, "
"see also :doc:`/reference/optimizations`."
msgstr ""
"Now, you can use Mroonga as wrapper mode! If you want Mroonga to be faster, "
"see also :doc:`/reference/optimizations`."

msgid "Footnotes"
msgstr "Footnotes"

msgid ""
"`MySQL 5.1 Reference Manual :: 11 Functions and Operations :: 11.7 Full-Text "
"Search Functions <http://dev.mysql.com/doc/refman/5.1/ja/fulltext-search."
"html>`_"
msgstr ""
"`MySQL 5.1 Reference Manual :: 11 Functions and Operations :: 11.7 Full-Text "
"Search Functions <http://dev.mysql.com/doc/refman/5.1/ja/fulltext-search."
"html>`_"

msgid "In Groonga, we call it a 'tokenizer'."
msgstr "In Groonga, we call it a 'tokenizer'."
