[Groonga-commit] groonga/groonga at b552f1a [master] doc: improve description about substitution table and normalizer

Back to archive index

Kouhei Sutou null+****@clear*****
Thu Aug 27 12:53:48 JST 2015


Kouhei Sutou	2015-08-27 12:53:48 +0900 (Thu, 27 Aug 2015)

  New Revision: b552f1a4d253e13d7a1a5a9adbdafcf449e51eb3
  https://github.com/groonga/groonga/commit/b552f1a4d253e13d7a1a5a9adbdafcf449e51eb3

  Message:
    doc: improve description about substitution table and normalizer

  Modified files:
    doc/source/reference/commands/select.rst

  Modified: doc/source/reference/commands/select.rst (+6 -3)
===================================================================
--- doc/source/reference/commands/select.rst    2015-08-27 12:53:19 +0900 (917b330)
+++ doc/source/reference/commands/select.rst    2015-08-27 12:53:48 +0900 (db89737)
@@ -691,9 +691,12 @@ Here is a sample substitution table to show a simple
 ``"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
-``NormalizerAuto`` option. If the option is used, substitute target word is
-matched in case insensitive manner.
+OR (senna))"``.
+
+Normally, it's good idea that substitution table uses a
+normalizer. For example, if normalizer is used, substitute target word
+is matched in case insensitive manner. See
+:doc:`/reference/normalizers` for available normalizers.
 
 Note that those synonym values include the key value such as
 ``"mroonga"`` and ``"groonga"``. It's recommended that you include the
-------------- next part --------------
HTML����������������������������...
Download 



More information about the Groonga-commit mailing list
Back to archive index