Michael James Gratton f10f898ab0 Always use UTF-8 for encoding non-ASCII/ISO-8859-1 headers. Bug 753870. ... While message bodies are always sent as UTF-8, non ASCII/ISO-8859-1 headers were being encoded using GMime's default heuristics. This uses some less-well-supported charsets and causing some rendering issues in other less tolerant client. Since we assume UTF-8 support for the body, assume it for headers as well. * src/engine/rfc822/rfc822.vala (Geary.RFC822.init): Set GMime user charsets to UTF-8. * bindings/vapi/gmime-2.6.vapi (GMime): Fix binding for g_mime_set_user_charsets.		2016-06-30 15:29:39 +10:00
..
metadata	Bump minimum WebKitGTK version to 2.4, remove bindings for older versions.	2016-05-20 16:29:28 +10:00
vapi	Always use UTF-8 for encoding non-ASCII/ISO-8859-1 headers. Bug 753870.	2016-06-30 15:29:39 +10:00