4 ms·
Not sure what you're talking about; FogBugz sends UTF-8 email.
by spolsky 15y ago
Not sure what you're talking about; FogBugz sends UTF-8 email.
- solutionyogi 15y agoI just looked at my FogBugz email from today morning, it is indeed using CP1252 character set. See: http://i.imgur.com/nV3V6.png http://i.imgur.com/nV3V6.png I think this could be because you use messagelabs.com to send out the emails.
- spolsky 15y agoweird. I'll check into that. It used to be UTF-8.
- tedunangst 15y agoIt sends CP1252 emails if all the characters used fit. If they don't, it uses UTF8. That way, people with old mailers can still read them (more realistically, people reading the raw email can read them out of the database or from traffic dumps), because .NET has a tendency to base64 encode the body the instant you set charset to UTF8, and I don't unbase64 in my head. Try including the funny character of your choice in an email. It should show up just fine.
- solutionyogi 15y agoYou are right. I created another test case with Chinese character and the email is now UTF-8. See: http://i.imgur.com/LeaX8.png http://i.imgur.com/LeaX8.png I think this is a very good compromise.
- jwr 15y agoI'm talking about this: Received: from mxny1.fogcreek.com (mxp11.fogcreek.com [64.34.80.172]) by […] Received: from hbny4 (hbny4.fogcreek.local [10.2.0.48]) by mxny1.fogcreek.com (Postfix) with ESMTP id 2386295B33 for […]; Tue, 10 Jan 2012 19:18:45 -0500 (EST) Priority: normal Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1250 Content-Transfer-Encoding: quoted-printable Message-Id: <20120111001845.2386295B33@mxny1.fogcreek.com>