Closed
Bug 1167496
Opened 9 years ago
Closed 9 years ago
emoji characters are mangled in emails
Categories
(Bugzilla :: Email Notifications, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: glob, Unassigned)
References
Details
if an emjoi character is used in a comment, the character is incorrectly displayed in email.
eg. poop is rendered as 💩
Comment 1•9 years ago
|
||
Note that, while emojis are being introduced in 5.0, this is not worthy of blocker status. Turning the feature off isn't necessary either, but we should either list it in the release notes as a known bug, or purposefully not mention emojis as a new feature.
Comment 2•9 years ago
|
||
(In reply to Byron Jones ‹:glob› from comment #0)
> if an emjoi character is used in a comment, the character is incorrectly
> displayed in email.
Could you check something for me? Does this problem also happen if the recipient of the bugmail wants emails as plain text only? Because I realized that my realname is incorrectly displayed in HTML+text bugmails but is displayed correctly in plain text only bugmails. Maybe that's the same issue.
Comment 3•9 years ago
|
||
(In reply to Byron Jones ‹:glob› from comment #0)
> eg. poop is rendered as 💩
Actually, Thunderbird displays this in the source code of the email, but it's displayed correctly in Thunderbird itself. Also, my realname is displayed correctly when the comment contains such characters, else it's not. Do we sniff the email content before sending it to find non-ASCII characters in it or something like that?
oops, this looks like an issue with my email client (postbox). viewing the same message in gmail correctly shows emojis.
(In reply to Frédéric Buclin from comment #3)
> Also, my realname is
> displayed correctly when the comment contains such characters, else it's
> not. Do we sniff the email content before sending it to find non-ASCII
> characters in it or something like that?
that's probably bug 714724. i should have a new patch for that soon.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•