telegramdesktop / tdesktop

Telegram Desktop messaging app
https://desktop.telegram.org/
Other
26.43k stars 5.25k forks source link

greek characters sent through ifttt bot aren't displayed properly #10047

Closed patrickdrd closed 3 years ago

patrickdrd commented 3 years ago

Steps to reproduce

  1. create an applet in ifttt to monitor a rss feed or a twitter account containing greek characters
  2. send the results to telegram (action)
  3. open any telegram app (android/desktop/web), the result is the greek characters are displayed as following

image

(the bottom part is the preview)

Expected behaviour

greek characters should display properly and not with α and β etc

Actual behaviour

greek characters display with α and β except the accented characters such as ά, έ, ή etc, these are displayed perfectly fine! I contacted ifttt as well for the issue and they replied:

That's also really useful information regarding the characters with tonos. Just from doing a quick check, I can see that these don't appear to have HTML entities and use decimal and hex codes instead. This may still end up being reliant on how Twitter/Telegram displays these characters

and birdie who helps with ifttt on discord replied:

the issue what i thought before, telegram decoding symbols on their side, converting them to entitles that was seen in test with α

Version of Telegram Desktop: this happens for a long while, because I had reported it a year and a half back when I had the same problem sending google calendar to telegram with the exactly same results and I think it's time it gets fixed :)

happy new year!

Aokromes commented 3 years ago

not telegram desktop issue.

patrickdrd commented 3 years ago

really? I think it's all telegram issue: Android, desktop and web!!!

Aokromes commented 3 years ago

it looks more server side to me.

patrickdrd commented 3 years ago

ah, ok now I agree

ilya-fedin commented 3 years ago

it looks more server side to me.

This is a IFTTT's bot issue

github-actions[bot] commented 3 years ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.