On 11/17/2012 08:26 PM, Michael Heydekamp wrote: ...
Furthermore, the option "Compose HTML messages" has apparently four options now, the last one ("on forward or reply to HTML message") not being localized (yet?) Or is it a duplicate to "on reply to HTML message only"?.
Last but not least, in very few and exceptional cases I'd indeed like to compose a HTML message when replying to a HTML message. Currently I see no other way than to change the option "Compose HTML messages", create the reply, and then reset "Compose HTML messages" back to "Never" (which I then sometimes forget, of course, and which is not too comfortable).
...
All this seems to get fairly messy. I would have thought the compose style option should be a fairly clear-cut option: 'text' or 'HTML'.
Just an FYI as Mozilla Thunderbird is often quoted as a reference for how clients can function.
In Thunderbird, I have 'text' as my default compose method.
Text is used, per default, upon compose and reply (irrelevant of what is being displayed (text/HTML)).
You can 'simply' switch your compose style by 'shift-clicking' the 'Write' or 'Reply' buttons and it will, in my case, switch to HTML (or text if HTML is default).
This could be used as a documented UI option for choosing compose/response style (plus tool-tip). I believe that the default should be that that the user has selected in their preferences. Making a HTML reply just because I am viewing a HTML message is not following the users composition preferences.
This would solve most of the above stated issues in a simple and consistent manner. It could also be argued that multiple sub-options for HTML would then no longer be needed.
Regards
Chris