aboutsummaryrefslogtreecommitdiffstats
path: root/em-format/e-mail-formatter.h
Commit message (Collapse)AuthorAgeFilesLines
* Use CamelMimeFilterToHTMLFlags enum type where appropriate.Matthew Barnes2013-02-071-2/+3
|
* Bug #692009 - text/css always formatted as attachmentMilan Crha2013-01-241-0/+1
| | | | | | | Might be the final change for this bug, the two previous commits were not using the right approach, causing regression in rendering of text/* parts which were not named in the list of excluded content types for a 'raw' formatting.
* Consolidate base utility libraries into libeutil.Matthew Barnes2012-12-131-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Evolution consists of entirely too many small utility libraries, which increases linking and loading time, places a burden on higher layers of the application (e.g. modules) which has to remember to link to all the small in-tree utility libraries, and makes it difficult to generate API documentation for these utility libraries in one Gtk-Doc module. Merge the following utility libraries under the umbrella of libeutil, and enforce a single-include policy on libeutil so we can reorganize the files as desired without disrupting its pseudo-public API. libemail-utils/libemail-utils.la libevolution-utils/libevolution-utils.la filter/libfilter.la widgets/e-timezone-dialog/libetimezonedialog.la widgets/menus/libmenus.la widgets/misc/libemiscwidgets.la widgets/table/libetable.la widgets/text/libetext.la This also merges libedataserverui from the Evolution-Data-Server module, since Evolution is its only consumer nowadays, and I'd like to make some improvements to those APIs without concern for backward-compatibility. And finally, start a Gtk-Doc module for libeutil. It's going to be a project just getting all the symbols _listed_ much less _documented_. But the skeletal structure is in place and I'm off to a good start.
* EMailFormatterContext: Clearify the flags type.Matthew Barnes2012-12-081-3/+3
| | | | We define the header flags as an enum type, so use the enum type.
* EMailFormatterHeader: Clarify the flags type.Matthew Barnes2012-12-081-2/+2
| | | | We define the header flags as an enum type, so use the enum type.
* EMailFormatterContext: Keep a reference to EMailPartList.Matthew Barnes2012-12-081-5/+1
| | | | | Replace the individual components of an EMailPartList with a reference on the EMailPartList itself in EMailFormatContext. Easier to manage.
* EMailFormatter: Simplify context allocation.Matthew Barnes2012-12-081-12/+10
| | | | | | | | | | Replace the create_context() and free_context() class methods with a "context_size" class member defaulting to sizeof(EMailFormatterContext). EMailFormatter will use "context_size" to allocate a zero-filled slab of heap memory. Since EMailFormatterQuote is currently the only thing that overrides the "context_size" (to append a "qf_flags" member), let's keep this simple.
* Highlighting of text parts and source codesDan Vrátil2012-07-251-0/+2
| | | | | | | | | | This adds 'Format as' submenu to the preview pane context menu. The submenu is available only for text/plain parts or parts with a source code (we support about 40 various types). Using the 'highlight' utility, the formatter processes the part and highlights the source code it contains. (discussion in bug #680026)
* Fix displayed message headersDan Vrátil2012-06-081-0/+2
| | | | | | | | | The new formatter was ignoring selected headers, always displaying only From, To, Subject and Date (default headers). Handling of the currently displayed headers has been moved to EMailConfigFormatHTML extension, because it is related to configuration of EMailFormatter, rather then EMailReader.
* Mail formatter rewriteDan Vrátil2012-06-061-0/+266
All mail-parsing and formatting code has been moved to em-format. Parsing is handeled by EMailParser class, formatting by EMailFormatter. Both classes have registry which hold extensions - simple classes that do actual parsing and formatting. Each supported mime-type has it's own parser and formatter extension class.