# How to overcome missing language analyzers?

**URL:** <https://discuss.elastic.co/t/how-to-overcome-missing-language-analyzers/211437>\
**Category:** Elasticsearch\
**Created:** [December 11, 2019, 9:08am UTC](https://discuss.elastic.co/t/how-to-overcome-missing-language-analyzers/211437 "2019-12-11T09:08:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ssklavos](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@ssklavos](https://discuss.elastic.co/u/ssklavos)\
**Post date:** [December 11, 2019, 9:08am UTC](https://discuss.elastic.co/t/how-to-overcome-missing-language-analyzers/211437/1 "2019-12-11T09:08:46Z")

</div>

What is the general approach/best practice when an analyzer is missing? We need to provide support for functionalities like stemming and there is a range of languages missing.  
I suppose this should be a common issue and despite we have found some plugins, they do not suffice. Should we consider implementing them somehow or there is some open/commercial support which can on demand provide plugins for missing analyzers?

_ **Language analysers missing:** _  
Eesti keel (et)- Estonian,  
Hrvatski (hr)- Croatian,  
Malti (mt) – Maltese,  
Nederlands (nl) – Netherlands,  
Polski (pl) – Polish,  
Slovenčina (sk) – Slovak,  
Slovenščina (sl) – slovenian

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 8, 2020, 9:08am UTC](https://discuss.elastic.co/t/how-to-overcome-missing-language-analyzers/211437/2 "2020-01-08T09:08:56Z")

</div>

Closed on January 8, 2020, 9:08am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.