You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(which expands phonetic matching to languages other than English),
14
+
http://en.wikipedia.org/wiki/Caverphone[Caverphone] for matching names in New
15
+
Zealand, the
16
+
https://en.wikipedia.org/wiki/Daitch–Mokotoff_Soundex#Beider.E2.80.93Morse_Phonetic_Name_Matching_Algorithm[Beider-Morse] algorithm, which adopts the Soundex algorithm
17
+
for better matching of German and Yiddish names, and the
18
+
http://de.wikipedia.org/wiki/K%C3%B6lner_Phonetik[Kölner Phonetik] for better
19
+
handling of German words.
20
+
21
+
The thing to take away from this list is that phonetic algorithms are fairly
22
+
crude, and ((("languages", "phonetic algorithms")))very specific to the languages they were designed for, usually
23
+
either English or German. This limits their usefulness. Still, for certain
24
+
purposes, and in combination with other techniques, phonetic matching can be a
25
+
useful tool.
26
+
27
+
First, you will need to install ((("Phonetic Analysis plugin")))the Phonetic Analysis plug-in from
28
+
https://www.elastic.co/guide/en/elasticsearch/plugins/current/analysis-phonetic.html on every node
29
+
in the cluster, and restart each node.
30
+
31
+
Then, you can create a custom analyzer that uses one of the
32
+
phonetic token filters ((("phonetic matching", "creating a phonetic analyzer")))and try it out:
0 commit comments