On Donnerstag, 14. Mai 2015 10:52:30 CEST, Jan Kundrát wrote:
On Thursday, 14 May 2015 05:39:23 CEST, Thomas Lübking wrote:
We'd require an explicit save button if this is considered a
supported condition/environment.
I thought that NETWM was pretty widespread; IMHO it's fine to
rely on it
1st of all: trojita operates on top of Qt, not some FDO protocol directly
=)
2nd: every "modern" ("maintained") WM supports at least a subset of EWMH,
this includes the major desktops, lightweight solutions like fluxbox or
openbox, tiling WMs like awesome and afair lately even ancient relics like
fvwm and ICEWM =)
xmonad apparently "only" optionally, but in gerenal it's something that one
can (and Qt apparently "does") reasonably expect.
Personally i'm far more concerned about relying on the user (inc. me) to
"save before you close".
src/UiUtils/PlainTextFormatter.cpp). The actual font to use is
guessed by systemMonospaceFont() in src/Gui/Util.cpp. Looking at
that gem, I can see that it isn't exactly rock-solid :).
The problem w/ monospace fonts is that they're not necessarily ideal for
reading mass text. On Hi-Res, i'd *personally* prefer some (Semi-)Serif and
on low-res a regular grotesque with variable glyph metrics.
Monospace is only useful if the mail contains some ascii art (ie. paintings
with pipes, dashes and underscores ;-)
Unfortunately, I've no good idea how to reliably perform that via some
non-html markup, eg. markdown would have code inside "```" tags but unlike
*bold* /italic/ and _underscore_ that's not a common mechanism in mails, so
it will be rarely used and rather hit false positives :-(
For a short rant:
I always wished one would have defined a very basic sgml/html subset for
simple mail markup (w/ the guarantee that the other side does not send or
receive full blown html - in random colors, font sizes ... and marquee) in
the early times... :-(
Cheers,
Thomas