From aeb9ff37d6683236300b0325d65c6ca0ec66c7ed Mon Sep 17 00:00:00 2001 From: Kuang-che Wu Date: Sun, 7 Dec 2014 14:32:05 +0800 Subject: make sqlite3 full-text search tokenizer configurable. OpenStreetMap is an international project. "icu" or other non-default tokenizer may be more suitable for some locales. For example, "icu" tokenizer is better than the default ("simple") for Chinese. We don't want to force all to recompile sqlite3 in order to use "icu" tokenizer, so make it configurable in taginfo-config.json. --- taginfo-config-example.json | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'taginfo-config-example.json') diff --git a/taginfo-config-example.json b/taginfo-config-example.json index 3936308..2c225b2 100644 --- a/taginfo-config-example.json +++ b/taginfo-config-example.json @@ -95,7 +95,13 @@ // Minimum number of relations per type to make this // relation type "interesting", ie. to make it show // up as a relation type. - "min_count_relations_per_type": 100 + "min_count_relations_per_type": 100, + // Tokenizer for sqlite full-text search. Complex or custom + // tokenizers, e.g., icu and unicode61, may be more suitable for + // some locales. You may need newer sqlite3 or to recompile + // sqlite3 to use those tokenizers. + // See http://www.sqlite.org/fts3.html#tokenizer for detail. + "tokenizer": "simple" } }, "logging": { -- cgit v1.2.3