# Adding char\_filter into language analyzer

**URL:** <https://discuss.elastic.co/t/adding-char-filter-into-language-analyzer/220818>\
**Category:** Elasticsearch\
**Created:** [February 25, 2020, 10:13am UTC](https://discuss.elastic.co/t/adding-char-filter-into-language-analyzer/220818 "2020-02-25T10:13:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dbakti7](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dbakti7/32/42250_2.png) [@dbakti7](https://discuss.elastic.co/u/dbakti7)\
**Post date:** [February 25, 2020, 10:14am UTC](https://discuss.elastic.co/t/adding-char-filter-into-language-analyzer/220818/1 "2020-02-25T10:14:00Z")

</div>

Is there a way to extend language analyzer with char\_filter without having to reimplement the whole analyzer?  
We are trying to add html\_strip char\_filter into language analyzed fields, following [https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-lang-analyzer.html#english-analyzer](https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-lang-analyzer.html#english-analyzer), we can achieve it by having some custom analyzer:

```
"rebuilt_english": {
    "tokenizer": "standard",
    "filter": [
        "english_possessive_stemmer",
        "lowercase",
        "english_stop",
        "english_stemmer"
    ],
    "char_filter": [
        "html_strip"
    ]
},

```

but because we have many different language analyzers in the same mapping, following this approach is pretty tedious and results in very long mapping file (have to reimplement every single analyzer).  
Is there any way to extend language analyzer with char\_filter without having to reimplement it?

---

<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:** [March 24, 2020, 10:14am UTC](https://discuss.elastic.co/t/adding-char-filter-into-language-analyzer/220818/2 "2020-03-24T10:14:07Z")

</div>

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