Paul B. Gallagher wrote: > BIll Spikowski wrote: > >> I'm experimenting on three different machines and the results are >> inconsistent. >> >> Setting a "monospace" font and font size always results in that font >> and size being used in the Compose windows, but I can't figure out why >> it's so inconsistent as to the preview pane. >> >> I understand that this setting won't affect incoming emails that were >> composed in HTML, but it's inconsistent even on what I believe are >> plain-text emails. How can I tell which are in plain text for sure? >> One idea is that some incoming emails might look like plain text >> because they appear in Courier New, my choice of monospace font, but >> actually be HTML. > > Depending on the sender's settings, sometimes messages are sent in both > plain text and HTML. Depending on the recipient's settings, one or the > other of those will be displayed. > > If you examine the "source code" of such a message (with the message > open, do CTRL-U), you'll see something like this (ellipses indicate > omissions for the sake of clarity): > > Content-type: multipart/alternative; boundary="gobbledygook" > Content-language: en-us > ... > > This is a multi-part message in MIME format. > > --gobbledygook > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > > ... > > --gobbledygook > Content-Type: text/html; charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > ... > > In this example, the sending machine marked the first copy of the > message as plain text and the second copy as HTML. I've used the word > "gobbledygook" to represent the alphabet soup you'll actually see for > the boundary. > > I'm not sure how SM handles such messages, but I would expect plain-text > settings to apply if the rules say to display the message as plain text, > and HTML settings to apply if the rules say to display the message as > HTML. But I can't figure out how to specify these rules. > > Another possibility is that some of your senders may have specified > non-Western encodings. If you look carefully at > Edit | Preferences | Appearance | Fonts > you will find that Monospace can be set differently for different > encodings. For example, I have Western monospace set to Courier New, but > Korean monospace set to GulimChe. So if a sender specifies Korean > encoding, I'll see it in GulimChe instead of Courier New. You can also > set different sizes for different encodings. > > Two other places you may want to look: > > 1) Edit | Preferences | Mail & Newsgroups | Message Display > > There's an option: > Plain text messages > Font: (•) Fixed width (o) Variable width > > So you could set it to display plain-text messages with proportional > font(s), but AFAIK the default is fixed-width. > > 2) Edit | Preferences | Mail & Newsgroups | Composition > There's an option: > Defaults for HTML Messages: > Font: [Variable Width] > > You can pull down [Fixed Width] or a specific font from the list.
This is incredibly helpful! On my office computer, I had specified "variable width" for displaying plain text messages; that's why they showed up in Charter BT instead of Courier New. I had completely forgotten about CTRL-U! Next time messages show up strange, I'll able to figure out how they were sent. And now that I know about CTRL-0, I'll always know whether the current zoom level is the default, or the result of my recent efforts. My only regret is that this information is buried in a string on another subject, where it may be hard for others to find.... _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
