# Need use cases for entities

**URL:** <https://talk.commonmark.org/t/need-use-cases-for-entities/1005>\
**Category:** Uncategorized\
**Created:** [January 12, 2015, 5:40am UTC](https://talk.commonmark.org/t/need-use-cases-for-entities/1005 "2015-01-12T05:40:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vitaly](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/vitaly/32/396_2.png) [@vitaly](https://talk.commonmark.org/u/vitaly)\
**Post date:** [January 12, 2015, 5:40am UTC](https://talk.commonmark.org/t/need-use-cases-for-entities/1005/1 "2015-01-12T05:40:18Z")

</div>

Can anyone explain, why those huge list of entities is needed in real world? I’ve seen those only for HTML escaping & copyright sign.

I’d like to ship [simplified decoder](https://github.com/markdown-it/markdown-it/issues/6) for browser build. Or, may be, just reduced list of [current](https://github.com/markdown-it/markdown-it/blob/master/lib/common/entities.js) HTML5 set (generated from [http://www.w3.org/TR/html5/entities.json](http://www.w3.org/TR/html5/entities.json)). DOM decoder result vary on document type. Manualy reduced list not vary, but support much less entities than DOM.

Does it worth to spend time for light builds, or you know examples, when rare entities are used?