Special character cuts off text

[polsvoice]

I found out that a certain character will truncate the text in a post. The character is erased, as well as everything after it. It's not immediately obvious, though, because it only happens after the page is reloaded.
Here are the steps I used.

1. Create a post with the text:
   I am a 😔 meat popsicle
2. Hit the Preview button. The preview will show:
   I am a 😔 meat popsicle
3. Hit the Share button. The post will read:
   I am a  meat popsicle
   (The special character has been replaced with the generic square icon.)
4. Reload the page. The post now reads:
   I am a

[goobertron]

Hmm, smileys are not supported in Diaspora, as far as I'm aware. A couple of pods have provided some smileys which can be used in Diaspora posts, but they are not part of the core code.

Which pod are you using?

[polsvoice]

JoinDiaspora. If they aren't supported, I don't think that they would appear in previews...and they certainly shouldn't erase text. What I would expect to see, for an unsupported character, is the generic square icon (which you see when you hit Share, in step 3).

[jhass]

@goobertron note this is a unicode character, so technically not much different from an ä or even a 1.

That said I can't reproduce on develop with FF 31. However the post is displayed truncated on Geraspora.

@denschub can you check if f0799b400dd40132131a1a9cba9272d8 is truncated in the database please?

[denschub]

All I can see in the database:

"I am a "

[jhass]

It's perfectly fine in my DB. Maybe a MySQL issue?

[denschub]

I'm able to reproduce this on Geraspora.

[polsvoice]

For further reference, it's Unicode character U+1F614 (aka "Pensive Face").
http://www.fileformat.info/info/unicode/char/1f614/index.htm

[goobertron]

Ah, that's what confused me.

[svbergerem]

I can't reproduce this on develop with MariaDB. Maybe #5530 fixed this?

[jhass]

Mmh, quite possible. Did anybody ever reproduce this on PostgreSQL?

[dimaursu]

@svbergerem #5530 should definitely fixed this kind of inconsistency, that is if you are running the version after the merge, of course. This issue should be closed. I should note that I also tested on MariaDB, but it shouldn't make much difference.

[denschub]

Closing; working on MySQL and PostgreSQL with 0.5.0.0.