# ¿Cuál es el problema con la llamada a PrettyText.markdown?
**URL:** https://meta.discourse.org/t/what-is-the-problem-with-prettytext-markdown-call/84674
**Category:** Development
**Created:** [5 Abril, 2018 21:11 UTC](https://meta.discourse.org/t/what-is-the-problem-with-prettytext-markdown-call/84674 "2018-04-05T21:11:49Z")
**Posts on this page:** 3
**Page:** 2
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [16 Abril, 2018 01:52 UTC](https://meta.discourse.org/t/what-is-the-problem-with-prettytext-markdown-call/84674/23 "2018-04-16T01:52:19Z")
hmmm that is by design and a slightn bug. `❤️:phone:` and `a:phone:` and `ث:phone:` are all not meant to expand emoji. We only allow emoji expansion after a punctuation or space.
The autocomplete throws stuff off a bit and we should fix that. I don’t want to put lots of special case logic here for mixed emoji central.
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [18 Abril, 2018 00:10 UTC](https://meta.discourse.org/t/what-is-the-problem-with-prettytext-markdown-call/84674/24 "2018-04-18T00:10:57Z")
I think if the emoji-image converter greedily grabs VS16 (as well as the force-not-emoji variation selector) it’ll solve the problem, because you’ll end up with a `❤️` right?
---
### Author:  [@ballistic](https://meta.discourse.org/u/ballistic)
#### Post date: [25 Abril, 2018 23:57 UTC](https://meta.discourse.org/t/what-is-the-problem-with-prettytext-markdown-call/84674/25 "2018-04-25T23:57:20Z")
What is the downside of keeping the Unicode emojis? (skip emoji escape)
From my test, it is OK.
[Previous page](https://meta.discourse.org/t/what-is-the-problem-with-prettytext-markdown-call/84674.md?page=1)