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

Newlines in messages are ignored #147

Open
m-urban opened this issue May 30, 2016 · 5 comments
Open

Newlines in messages are ignored #147

m-urban opened this issue May 30, 2016 · 5 comments
Labels

Comments

@m-urban
Copy link

m-urban commented May 30, 2016

Hi there,

I wanted to report an issue that I recently discovered: Whenever I am forcing a linebreak in a message (\n), an empty message will be sent instead. E.g.

Line1
Line2

Line4

will become "". Also

Line1
Line2

will result in an empty message.

I have noticed that this issue affects both the purple-facebook and telegram-purple plugins, which leads me to think that it's either a problem with libpurple or spectrum. In case that it's a problem with libpurple, I'll be happy to file a bug report with them.
The message itself will be sent, however, which I can see in facebook's webinterface. It will appear as an empty message, though.

@m-urban m-urban changed the title Newline in message body resulting in empty message Newline in message body results in empty message May 30, 2016
@vitalyster
Copy link
Collaborator

To be sure it is our problem - try the same with pidgin or finch

@m-urban
Copy link
Author

m-urban commented May 30, 2016

Uh. This is ugly. It seems that Messages.app on the Mac is playing a major role in this problem. Since I had it installed already, I just tried Adium as a client and the messages came through ok-ish. BUT: Adium seems to send the test message

Line1
Line2

Line4

as

    Line1 Line2  Line4

I tried both Telegram and facebook and both show this very same behavior.

So it seems, Apple didn't get the newline character right for Jabber accounts in their Messages.app (btw. this works fine for their proprietary iMessages…). But still, newlines seem to be misinterpreted somewhere along the way between Adium→spectrum→Telegram/facebook. Could this be a problem with spectrum at all?

@vitalyster
Copy link
Collaborator

@m-urban answer is still the same - try to set up pidgin or finch (or adium, if it supports telegram or facebook purple plugin) with the plugin account (without spectrum!) and check if problem still exists

@m-urban
Copy link
Author

m-urban commented May 30, 2016

So I tried Adium with the telegram-purple plugin and the newline is interpreted and sent correctly. I wasn't able to test the purple-facebook plugin in the same way because it's not availble for Adium.

EDIT: I mean I tried Adium with the telegram-purple plugin directly without spectrum as a gateway.

@vitalyster vitalyster added the Bug label May 30, 2016
@m-urban m-urban changed the title Newline in message body results in empty message Newlines in messages are ignored Jun 4, 2016
@Programie
Copy link
Contributor

Is there already any progress in this issue?

I'm having the same issue with different transports (Facebook and Steam), both via the libpurple backend. Is this an issue caused by libpurple or Spectrum?

I can reproduce this issue with Gajim on Linux as well as with Conversations on Android, so the client shouldn't be the issue.

Whenever I send a message with multiple lines, all line breaks are replaced by spaces which can look pretty strange in some cases.

My current workaround is to send each line as a separate message which can be really annoying for the recipient.

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

No branches or pull requests

3 participants