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
..
gmime-2.6	Transfer Yorba copyrights to Software Freedom Conservancy	2016-05-06 08:33:37 -04:00
enchant.vapi	Added support to change the spell-checking language.	2016-06-09 15:36:39 +10:00
gmime-2.6.vapi	Always use UTF-8 for encoding non-ASCII/ISO-8859-1 headers. Bug 753870.	2016-06-30 15:29:39 +10:00
libnotify.vapi	Can't bld w/ Vala 0.22.1 WebKitGTK 2.2.2: Closes #7694, Closes #7695	2013-11-15 16:53:18 -08:00
libsecret-1.vapi	Closes #5549 Closes #5813 Closes #5633 Port to LibSecret (ssh!)	2013-04-10 18:28:59 -07:00
Makefile	Closes #6209 Precise support for GIR WebKitGTK binding. Rolls back to deprecated context menu in composer for compatibility with WebKitGTK 1.8	2013-01-15 13:04:30 -08:00