Rob wrote:
Daniel <[email protected]> wrote:
On 30/05/14 13:23, Hartmut Figge wrote:
Geoff Welsh:
Hartmut Figge wrote:
It should suffice to select for Western and Unicode.
It /should/ suffice to choose ONE font that I like to (or can easily)
read, and have all messages I select appear in that font
For SM, the diplayed font depends on the Character Encoding of the message.
So, Hartmut, this must mean that somewhere with-in the message header,
the font in which it was composed *must* be listed, doesn't it??
Not the font. But the characterset, yes.
Note that this area of Seamonkey/Thunderbird is very buggy.
It has worked reasonably well in the past, but lately some complicated
bugs have been introduced by people overhauling certain parts of the
program, and later they claim that the software is unmaintainable and
needs to be rewritten.
That is all fine, but it would have been better if it had been left alone
and working as it was before a replacement is ready to be deployed.
One thing I noticed in Thunderbird was that changing the font for the
compose window in the preferences had no effect. I had to change it in
about:config to get it to stay the way I wanted it. With SeaMonkey,
putting the font type I want in the userContent.css file works.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
