# -*- po -*-
# English translations for Groonga package.
# Copyright (C) 2009-2025 Groonga Project
# This file is distributed under the same license as the Groonga package.
# Automatically generated, 2025.
#
msgid ""
msgstr ""
"Project-Id-Version: Groonga 15.0.2\n"
"Report-Msgid-Bugs-To: \n"
"PO-Revision-Date: 2025-02-21 09:46+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 "Scorer"
msgstr "Scorer"

msgid "Summary"
msgstr "Summary"

msgid "Groonga has scorer module that customizes score function. Score function computes score of matched record. The default scorer function uses the number of appeared terms. It is also known as TF (term frequency)."
msgstr "Groonga has scorer module that customizes score function. Score function computes score of matched record. The default scorer function uses the number of appeared terms. It is also known as TF (term frequency)."

msgid "TF is a fast score function but it's not suitable for the following cases:"
msgstr "TF is a fast score function but it's not suitable for the following cases:"

msgid "Search query contains one or more frequently-appearing words such as \"the\" and \"a\"."
msgstr "Search query contains one or more frequently-appearing words such as \"the\" and \"a\"."

msgid "Document contains many same keywords such as \"They are keyword, keyword, keyword ... and keyword\". Search engine spammer may use the technique."
msgstr "Document contains many same keywords such as \"They are keyword, keyword, keyword ... and keyword\". Search engine spammer may use the technique."

msgid "Score function can solve these cases. For example, `TF-IDF <https://en.wikipedia.org/wiki/Tf%E2%80%93idf>`_ (term frequency-inverse document frequency) can solve the first case. `Okapi BM25 <https://en.wikipedia.org/wiki/Okapi_BM25>`_ can solve the second case. But their are slower than TF."
msgstr "Score function can solve these cases. For example, `TF-IDF <https://en.wikipedia.org/wiki/Tf%E2%80%93idf>`_ (term frequency-inverse document frequency) can solve the first case. `Okapi BM25 <https://en.wikipedia.org/wiki/Okapi_BM25>`_ can solve the second case. But their are slower than TF."

msgid "Groonga provides TF-IDF based scorer as :doc:`/reference/scorers/scorer_tf_idf` but doesn't provide Okapi BM25 based scorer yet."
msgstr "Groonga provides TF-IDF based scorer as :doc:`/reference/scorers/scorer_tf_idf` but doesn't provide Okapi BM25 based scorer yet."

msgid "You don't need to resolve scoring only by score function. Score function is highly depends on search query. You may be able to use metadata of matched record."
msgstr "You don't need to resolve scoring only by score function. Score function is highly depends on search query. You may be able to use metadata of matched record."

msgid "For example, Google uses `PageRank <https://en.wikipedia.org/wiki/PageRank>`_ for scoring. You may be able to use data type (\"title\" data are important rather than \"memo\" data), tag, geolocation and so on."
msgstr "For example, Google uses `PageRank <https://en.wikipedia.org/wiki/PageRank>`_ for scoring. You may be able to use data type (\"title\" data are important rather than \"memo\" data), tag, geolocation and so on."

msgid "Please stop to think about only score function for scoring."
msgstr "Please stop to think about only score function for scoring."

msgid "Usage"
msgstr "Usage"

msgid "This section describes how to use scorer."
msgstr "This section describes how to use scorer."

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 "Sample schema:"
msgstr "Sample schema:"

msgid "Execution example::"
msgstr "Execution example::"

msgid "Sample data:"
msgstr "Sample data:"

msgid "You can specify custom score function in :ref:`select-match-columns`. There are some syntaxes."
msgstr "You can specify custom score function in :ref:`select-match-columns`. There are some syntaxes."

msgid "For score function that doesn't require any parameter such as :doc:`/reference/scorers/scorer_tf_idf`::"
msgstr "For score function that doesn't require any parameter such as :doc:`/reference/scorers/scorer_tf_idf`::"

msgid "You can specify weight::"
msgstr "You can specify weight::"

msgid "For score function that requires one or more parameters such as :doc:`/reference/scorers/scorer_tf_at_most`::"
msgstr "For score function that requires one or more parameters such as :doc:`/reference/scorers/scorer_tf_at_most`::"

msgid "You can use different score function for each :ref:`select-match-columns`::"
msgstr "You can use different score function for each :ref:`select-match-columns`::"

msgid "Here is a simplest example:"
msgstr "Here is a simplest example:"

msgid "``Groonga! Groonga! Groonga! Groonga is very fast!`` contains 4 ``Groonga``. If you use TF based scorer that is the default scorer, ``_score`` is ``4``. But the actual ``_score`` is ``2``. Because the ``select`` command uses TF-IDF based scorer ``scorer_tf_idf()``."
msgstr "``Groonga! Groonga! Groonga! Groonga is very fast!`` contains 4 ``Groonga``. If you use TF based scorer that is the default scorer, ``_score`` is ``4``. But the actual ``_score`` is ``2``. Because the ``select`` command uses TF-IDF based scorer ``scorer_tf_idf()``."

msgid "Here is an example that uses weight:"
msgstr "Here is an example that uses weight:"

msgid "``Groonga! Groonga! Groonga! Groonga is very fast!`` has ``22`` as ``_score``. It had ``2`` as ``_score`` in the previous example that doesn't specify weight."
msgstr "``Groonga! Groonga! Groonga! Groonga is very fast!`` has ``22`` as ``_score``. It had ``2`` as ``_score`` in the previous example that doesn't specify weight."

msgid "Here is an example that uses scorer that requires one argument. :doc:`/reference/scorers/scorer_tf_at_most` scorer requires one argument. You can limit TF score by the scorer."
msgstr "Here is an example that uses scorer that requires one argument. :doc:`/reference/scorers/scorer_tf_at_most` scorer requires one argument. You can limit TF score by the scorer."

msgid "``Groonga! Groonga! Groonga! Groonga is very fast!`` contains 4 ``Groonga``. If you use normal TF based scorer that is the default scorer, ``_score`` is ``4``. But the actual ``_score`` is ``2``. Because the scorer used in the ``select`` command limits the maximum score value to ``2``."
msgstr "``Groonga! Groonga! Groonga! Groonga is very fast!`` contains 4 ``Groonga``. If you use normal TF based scorer that is the default scorer, ``_score`` is ``4``. But the actual ``_score`` is ``2``. Because the scorer used in the ``select`` command limits the maximum score value to ``2``."

msgid "Here is an example that uses multiple scorers:"
msgstr "Here is an example that uses multiple scorers:"

msgid "The ``--match_columns`` uses ``scorer_tf_idf(title)`` and ``scorer_tf_at_most(content, 2.0)``. ``_score`` value is sum of them."
msgstr "The ``--match_columns`` uses ``scorer_tf_idf(title)`` and ``scorer_tf_at_most(content, 2.0)``. ``_score`` value is sum of them."

msgid "You can use the default scorer and custom scorer in the same ``--match_columns``. You can use the default scorer by just specifying a match column:"
msgstr "You can use the default scorer and custom scorer in the same ``--match_columns``. You can use the default scorer by just specifying a match column:"

msgid "The ``--match_columns`` uses the default scorer (TF) for ``title`` and :doc:`/reference/scorers/scorer_tf_at_most` for ``content``. ``_score`` value is sum of them."
msgstr "The ``--match_columns`` uses the default scorer (TF) for ``title`` and :doc:`/reference/scorers/scorer_tf_at_most` for ``content``. ``_score`` value is sum of them."

msgid "Built-in scorers"
msgstr "Built-in scorers"

msgid "Here are built-in scores:"
msgstr "Here are built-in scores:"
