Cannot write special characters / _fixText does not work?
null-von-sushi opened this issue · 5 comments
If I write " don't " into the notification, it changes it to " don't ".
I have no idea what this is causing. I looked at the extension (not that I understand any of it), but afaik "_fixText()" in extension.js should prevent this, no?
System:
Antergos with kernel 4.7.4-1
Pidgin 2.11.0 (libpurple 2.11.0)
Using Telegram Account thanks to telegram-purple 1.3.0-1
If any other information is needed I will be happy to provide that.
I can't see how " don't " differs from " don't ".
Can you take screenshot, please?
Outgoing text is passed to GLib.markup_escape_text.
Err, sorry about that. It seems Github changed the second "don't" (I wrote d-o-n-&-a-p-o-s-;-t, but as soon as I click 'update comment' github transforms the text into the normal, readable word "don't".
Anyways, here is the screenshot of what happens:
I think is relative to telegram-purple. Can you please check it with other protocols?
I can confirm that this is an issue with the GNOME shell extension, rather than telegram-libpurple. I can send apostrophes with Pidgin just fine; only messages sent through the gnome shell extension get HTML entities inserted.
@darthoctopus Looks like pidgin has special behavior about ': https://bitbucket.org/pidgin/main/commits/1929fae118e5fbf1a71836531caddd63ed385fab
I think avoiding escaping ' on replying via extension may help.