You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by omehegan on 13 Aug 2012 19:18 UTC as Trac ticket #1488606
When replying to some messages which have apostrophes in them (e.g. they use the word "it's" or something), the apostrophes will be stripped in the quoted message text when composing the reply (so you end up with "its").
I see this in both Firefox and Chrome, and have seen it for the last several versions of Roundcube. I am currently on 0.8.0 and still seeing it.
It does not happen with all messages. I have two examples at the moment, one which has the issue and one which does not. Looking at their headers, I only see one difference which might be relevant. The GOOD message has Content-Type: text/plain; charset="us-ascii". The BAD message has Content-Type: multipart/alternative; boundary=f46d04016d8721cf5904c7283a8d. The problem message is coming from Gmail, and I would think their messages would be somewhat standards-compliant...
Let me know if there's anything else I can do to help debug this.
Reported by omehegan on 13 Aug 2012 19:18 UTC as Trac ticket #1488606
When replying to some messages which have apostrophes in them (e.g. they use the word "it's" or something), the apostrophes will be stripped in the quoted message text when composing the reply (so you end up with "its").
I see this in both Firefox and Chrome, and have seen it for the last several versions of Roundcube. I am currently on 0.8.0 and still seeing it.
It does not happen with all messages. I have two examples at the moment, one which has the issue and one which does not. Looking at their headers, I only see one difference which might be relevant. The GOOD message has Content-Type: text/plain; charset="us-ascii". The BAD message has Content-Type: multipart/alternative; boundary=f46d04016d8721cf5904c7283a8d. The problem message is coming from Gmail, and I would think their messages would be somewhat standards-compliant...
Let me know if there's anything else I can do to help debug this.
Migrated-From: http://trac.roundcube.net/ticket/1488606
The text was updated successfully, but these errors were encountered: