# Cologne vs. koelnerphonetic - What's the difference? **URL:** \ **Category:** Elasticsearch\ **Created:** [May 6, 2020, 5:52am UTC](https://discuss.elastic.co/t/cologne-vs-koelnerphonetic-whats-the-difference/231268 "2020-05-06T05:52:05Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Clemens\_Lackner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/clemens_lackner/32/67768_2.png) [@Clemens\_Lackner](https://discuss.elastic.co/u/Clemens_Lackner)\ **Post date:** [May 6, 2020, 5:52am UTC](https://discuss.elastic.co/t/cologne-vs-koelnerphonetic-whats-the-difference/231268/1 "2020-05-06T05:52:05Z")
We're currently adding phonetic search support to our application by extending our elasticsearch mappings. As we have a german customer, we want to apply the **cologne phonetic algorithm**. When I check the available phonetic encoders (see [https://www.elastic.co/guide/en/elasticsearch/plugins/current/analysis-phonetic-token-filter.html](https://www.elastic.co/guide/en/elasticsearch/plugins/current/analysis-phonetic-token-filter.html)), I see that there are **two encoders which very likely refer to the same algorithm** -\> namely " **koelnerphonetik**" and " **cologne**". Both seem to be based upon the cologne phonetic algorithm. I am a little bit confused by these two encoders as they appear to be the same. Is there a specific reason for having these two encoders? How can I identify which encoder **fits better for me**? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 3, 2020, 5:52am UTC](https://discuss.elastic.co/t/cologne-vs-koelnerphonetic-whats-the-difference/231268/2 "2020-06-03T05:52:11Z")
Closed on June 3, 2020, 5:52am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.