Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convert ASCII to Emoji preference does not appear to be honored. #26681

Closed
poandlsl opened this issue Aug 25, 2022 · 3 comments · Fixed by #27038
Closed

Convert ASCII to Emoji preference does not appear to be honored. #26681

poandlsl opened this issue Aug 25, 2022 · 3 comments · Fixed by #27038

Comments

@poandlsl
Copy link

Description:

Convert ASCII to Emoji preference does not appear to be honored. After disabling this preference, users still experience ASCII being converted to emojis automatically.

Steps to reproduce:

  1. Disable 'Convert ASCII to Emoji' in My Account > Preferences > Messages
  2. Send a message containing an ASCII emoticon (:) or The final score was 0:3)
  3. Witness :) convert to 😃 and The final score was 0:3 convert to 'The final score was 😇'

Expected behavior:

When 'Convert ASCII to Emoji' is disabled, no ASCII should be converted to emojis.

Actual behavior:

ASCII characters are converted to emojis, despite the disabled setting.

Server Setup Information:

  • Version of Rocket.Chat Server: 5.0.0
  • Operating System: Rocky Linux 8.6
  • Deployment Method: docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: 14.19.3
  • MongoDB Version: 4.4.15

Client Setup Information

  • Desktop App or Browser Version: Rocketchat Desktop Client 3.8.7 and Firefox 103.0
  • Operating System: Ubuntu 20.04

Additional context

Relevant logs:

@dudanogueira
Copy link
Contributor

Hi! I Can confirm this bug.

We have been changing the Message Parser, and did a Community Open Call about it:
https://www.youtube.com/watch?v=zhPF9LpTR94&t=1046s

Thanks for pointing out!

@postwarbreakout
Copy link

postwarbreakout commented Sep 1, 2022

Same here. We have bots that send file paths and that's a total mess now.
Even simple backslashes just disappear: c:\temp\tempfile becomes "C😕temptempfile".
Is expect this to be fixed soon as it seems to be acknowledged by a dev now?

@postwarbreakout
Copy link

postwarbreakout commented Sep 2, 2022

By browsing through similar issues, I found a workaround which fixed things for us: #26475 (comment)
Doesn't work in the Android app though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants