# Special Character conflict with Transifex keyboards

**URL:** https://community.transifex.com/t/special-character-conflict-with-transifex-keyboards/96
**Category:** Translators Forum
**Created:** [October 5, 2018, 8:55pm UTC](https://community.transifex.com/t/special-character-conflict-with-transifex-keyboards/96 "2018-10-05T20:55:19Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![pjrobertson](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/pjrobertson/32/2182_2.png) [@pjrobertson](https://community.transifex.com/u/pjrobertson)
#### Post date: [May 11, 2022, 12:30am UTC](https://community.transifex.com/t/special-character-conflict-with-transifex-keyboards/96/6 "2022-05-11T00:30:52Z")

</div>

Thanks for the response! Perhaps I haven’t explained my problem clearly enough.

I have strings that need to be translated that contains the following UTF-8 character: `↩`

However, the parser is converting `↩` to \r. This means, that if I ever want to use the literal `↩` character in my translated strings, I cannot - they always get converted to \r.

In my mind, the parser should be able to detect if a user has entered the `↩` character, and then **not** convert it to \r.

Although never mind, I will just add a new build step in my build process to convert all \r to `↩` in the .strings files

**EDIT:** see here for what I mean: [Update strings files (change \r to ↩) · quicksilver/Quicksilver@8e73d9c · GitHub](https://github.com/quicksilver/Quicksilver/commit/8e73d9cdcec3aa80f3642e1405f65135cd183ba7)

---

_[View the full topic](https://community.transifex.com/t/special-character-conflict-with-transifex-keyboards/96)._