Paul B. Gallagher wrote, on 10 Oct 16 17:36:

It seems that SeaMonkey correctly detects the encoding when opening
messages in the "message pane", but doesn't actually use that encoding
until the next message is opened, and doesn't detect the encoding at all
when opening them in a separate window (just using the last-detected
encoding from the message pane).

That also affects opening previously saved drafts. So, for example:
- Start composing a message with UTF-8 encoding (like Paul, that's my
default) and include a character not covered by the standard ASCII set
(in my case, usually "£")  ...

Interesting. What you call "standard ASCII" is what we used to call
"high ASCII." The first 128 characters (up to ... xyz{|}~€  in Windows
Character Map) are the most basic, and the last 127 (beginning with
‚ƒ„…†‡ˆ‰Š‹ŒŽ) sometimes cause trouble. The high ASCII set also
includes the accented Western characters mentioned by the OP, such as
àáâãäåæçèéê..., but not Eastern European characters such as ăĺčďů.

At any rate, if high ASCII is causing problems, that suggests that SM is
trying for some reason to make do with a seven-bit encoding instead of
eight bits.

And what are implications of that?

(Sorry, but I'm rather lost in all these details: I've worked with computers since the '70s, but always tried to avoid the technical parts... still do, but that's the only way to get some things I want done, done)

Also, I remember that part in my previous message in this thread:

I (...)  have no correspondents who use anything except Unicode
and what I THOUGHT could be "Western" characters -- but what's
that:  Is that an euphemism for "English"?  Portuguese, Spanish,
French, all use "Western characters", IMHO; but I suspect the
former (ie, "Western") actually means "English"...

Assuming that's true, then in my case there would be 3 types of
text encoding: Western/English, Unicode (and I don't know if 'all
Unicodes are created equal'), and "other Western codes", like
Portuguese, Spanish, French, etc.

not to mention things like "MIME Encoding", which I don't see any option for anywhere in SM except that "Preferences | Mail & Newsgroups | Text Encoding" option: "For messages that contain 8-bit characters, use 'quoted printable' MIME Encoding" (yes, I know it's in Windows itself; but I thought SM was referring to something one could change inside it).

To be honest, I've got to the point where I barely notice this and just
automatically tap F8 a couple of times when a message isn't displayed
correctly. That it's become an automatic reaction isn't a particularly
good sign, but that may be a workaround until the problem is fixed
properly.

That F8's a good tip, thanks.

As I said in another message, I'll try that out after I clean up my draft, and see if it only works with the message pane, or also for new windows...

--
Thanks beforehand for your attention, and I hope to hear from you soon.

s) Alexander Yudenitsch   <ale...@postpro.net>



_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to