Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc reference: add a document for the escalate() function #1429

Merged
merged 20 commits into from
Oct 14, 2022

Conversation

komainu8
Copy link
Member

@komainu8 komainu8 commented Oct 12, 2022

No description provided.

@komainu8 komainu8 marked this pull request as ready for review October 12, 2022 09:03
@komainu8
Copy link
Member Author

@kou @HashidaTKS Could you review this PR?
@yoshimotoyuk Could you review about English?

"方法はオーバヘッドが大きい方法です。"

msgid ""
"However, ``escalte`` is for any full text search by inverted index. "
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

44行目と49行目が同じ意味には取れないです。
複数のindexに対応することが逆引き検索という事になるのであれば大丈夫だと思います。
数が複数の逆引き全文検索をまとめてできるということならmultiple full text searchだと思います。

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

「数が複数の逆引き全文検索をまとめてできる」ということを言いたいのでmultiple full text searchに変更します。

msgstr "``escalate`` は一つ以上の引数を持ちます::"

msgid ""
"``CONDITION_N`` and ``THRESHOLD_N`` are pair. However, the last condition "
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

もしlast conditionが最後の引数条件という意味なら、英語的には parameter入れておいた方が分かりやすい気がします。

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

↑のコメント受けて、 last condition と書くのがわかりにくい気がしたので、 CONDITION_ みたいに引数名を直接書くようにしました。

@yoshimotoyuk
Copy link
Contributor

This is a memo.... for future
Generally 「条件」 translate to condition in those documents. and It is correct but it may be more explainable to choose different words.
Like....
検索条件 :search criteria
必要条件(動作させるのに必須な条件): requirement
制限条件 (資格など必要条件): qualification
ref) https://www.linkedin.com/pulse/construction-general-conditions-vs-requirements-fullcircleconsulting

@komainu8
Copy link
Member Author

一通り修正しました。

msgstr "戻り値"

msgid "``escalate`` returns whether a record is matched or not as boolean."
msgstr "``escalte`` は対象レコードがマッチしたかどうかを真偽値で返します。"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
msgstr "``escalte`` は対象レコードがマッチしたかどうかを真偽値で返します。"
msgstr "``escalate`` は対象レコードがマッチしたかどうかを真偽値で返します。"

"of results that we search with ``CONDITION_N`` in more than ``THRESHOLD_N``, "
"``escalate`` doesn't evaluate next condition."
msgstr ""
"``CONDITION_N`` で検索した結果が ``THRESHOLD_N`` 以下の場合、 ``escalte`` は"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"``CONDITION_N`` で検索した結果が ``THRESHOLD_N`` 以下の場合、 ``escalte`` は"
"``CONDITION_N`` で検索した結果が ``THRESHOLD_N`` 以下の場合、 ``escalate`` は"

"方法はオーバヘッドが大きい方法です。"

msgid ""
"However, ``escalte`` is for multiple full text search by inverted index. "
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"However, ``escalte`` is for multiple full text search by inverted index. "
"However, ``escalate`` is for multiple full text search by inverted index. "

msgstr ""
"しかし、 ``escalate`` は複数のインデックスにも対応しています。そのため、厳密"
"に検索するインデックスを使った検索とゆるく検索するインデックスを使った検索を"
"一つのクエリーで実行できます。``escalte`` を使うことによって、オーバーヘッド"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"一つのクエリーで実行できます。``escalte`` を使うことによって、オーバーヘッド"
"一つのクエリーで実行できます。``escalate`` を使うことによって、オーバーヘッド"

Therefore, for example, if we can't get record in a search with a index that execute search strictly, we need to search with a index that execute search loosely once again.
This procedure has many overhead.

However, ``escalte`` is for multiple full text search by inverted index.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
However, ``escalte`` is for multiple full text search by inverted index.
However, ``escalate`` is for multiple full text search by inverted index.

@HashidaTKS
Copy link
Contributor

typo修正系のcommitが消えてしまっているように見えるのですが、確認頂けないでしょうか?


msgid ""
"A condition that we specify ``CONDITION_1`` is always executed. Therefore, "
"``CONDITION_1`` has not a threshold as pair."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"``CONDITION_1`` has not a threshold as pair."
"``CONDITION_1`` doesn't have a threshold as pair."


msgid ""
"``THRESHOLD_N`` is optional. However, when ``CONDITION_N`` exist "
"``THRESHOLD_N`` is required. (However, ``CONDITION_1`` has not a threshold "
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"``THRESHOLD_N`` is required. (However, ``CONDITION_1`` has not a threshold "
"``THRESHOLD_N`` is required. (However, ``CONDITION_1`` doesn't have a threshold "

THRESHOLD_N, CONDITION_N)

``CONDITION_N`` and ``THRESHOLD_N`` are pair.
However, ``CONDITION_1`` has not a threshold as pair. Because this condition is always executed.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
However, ``CONDITION_1`` has not a threshold as pair. Because this condition is always executed.
However, ``CONDITION_1`` doesn't have a threshold as pair. Because this condition is always executed.

``THRESHOLD_N``
~~~~~~~~~~~~~~~

``THRESHOLD_N`` is optional. However, when ``CONDITION_N`` exists ``THRESHOLD_N`` is required. (However, ``CONDITION_1`` has not a threshold as pair.)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
``THRESHOLD_N`` is optional. However, when ``CONDITION_N`` exists ``THRESHOLD_N`` is required. (However, ``CONDITION_1`` has not a threshold as pair.)
``THRESHOLD_N`` is optional. However, when ``CONDITION_N`` exists ``THRESHOLD_N`` is required. (However, ``CONDITION_1`` doesn't have a threshold as pair.)

``CONDITION_1`` is required.

A condition that we specify ``CONDITION_1`` is always executed.
Therefore, ``CONDITION_1`` has not a threshold as pair.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Therefore, ``CONDITION_1`` has not a threshold as pair.
Therefore, ``CONDITION_1`` doesn't have a threshold as pair.

komainu8 and others added 4 commits October 13, 2022 14:05
@komainu8
Copy link
Member Author

komainu8 commented Oct 13, 2022

typo修正系のcommitが消えてしまっているように見えるのですが、確認頂けないでしょうか?

すみません。上書きしてしまったみたいです。

追加の指摘も修正しました。

"り大きい場合、 ``escalate`` は次の条件を評価しません。"

msgid "``THRESHOLD_N`` is a positive number such 0 and 29."
msgstr "``THRESHOLD_N`` は 0 や 29 のような正の数です。"
Copy link
Contributor

@HashidaTKS HashidaTKS Oct 14, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

細かい話なのですが、0は正の数ではないので、「正の数」ではなく「0以上の数値」が正しそうに思いました。

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

0以上の整数としました。

"``THRESHOLD_N``, ``escalate`` doesn't evaluate ``CONDITION_N``."
msgstr ""
"``CONDITION_N-1`` で検索した結果が ``THRESHOLD_N`` 以下の場合、 ``escalate`` "
"は次の条件を評価します。``CONDITION_N-1`` で検索した結果が ``THRESHOLD_N`` よ"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"は次の条件を評価します。``CONDITION_N-1`` で検索した結果が ``THRESHOLD_N`` よ"
"は ``CONDITION_N`` を評価します。``CONDITION_N-1`` で検索した結果が ``THRESHOLD_N`` よ"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

↑の通り修正しました。

msgstr ""
"``CONDITION_N-1`` で検索した結果が ``THRESHOLD_N`` 以下の場合、 ``escalate`` "
"は次の条件を評価します。``CONDITION_N-1`` で検索した結果が ``THRESHOLD_N`` よ"
"り大きい場合、 ``escalate`` は次の条件を評価しません。"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"り大きい場合、 ``escalate`` は次の条件を評価しません"
"り大きい場合、 ``escalate`` は ``CONDITION_N`` を評価しません"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

↑の通り修正しました。

@komainu8
Copy link
Member Author

追加の指摘を修正しました。

@HashidaTKS
Copy link
Contributor

ご対応ありがとうございます。私からは以上となります。

+1

@komainu8 komainu8 merged commit 5549ad1 into master Oct 14, 2022
@komainu8 komainu8 deleted the add-a-document-for-escalate branch October 14, 2022 06:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants