Hartmut Figge wrote:
IRRITATING SPAMMER:
Hartmut Figge wrote:
Hartmut Figge:
├── [2.0M Jun 30 2015] lightning-4.4a1.en-US.linux-x86_64.xpi
Hm. My SM has chosen us-ascii instead of utf-8 for unknown reasons.
Well, it too is a SM-Trunk. *g* So forget the garbage at the beginning
of the lines. No important information.
It's Simple Text in a Newsgroup.
We'd presumably all have to set our clients to utf-8 in order to
interpret ├──, the two Euro question is: is it worth it? Nope.
Nothing needs to be done if Content-Type and Content-Transfer-Encoding
are correct. My SM-Trunk should have detected the presence of utf-8
chars in the message and used the proper declarations.
As to override the false us-ascii with the correct utf-8, well, isn't is
nice to know the garbage isnt't important? ;)
Hartmut
I just saved approx.20MB by compacting
--
https://facebook.com/gerardjan.vinkesteijn
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
SeaMonkey/2.49.3
Build identifier: 20180403170715
Fedora 20 Linux
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
