On 2019/05/16 15:57, Jeffrey L. Taylor wrote:
Anyone know of a way to force Thunderbird to use ASCII only for outgoing e-mails? I'm trying to get rid of the hard-space (0xA0) for the first of two spaces after a period. Some e-mail and maybe mail servers don't handle it well. It is replaced by two question marks on the other end.
I've used the config editor to set mailnews.send_default_charset to ASCII (ends up 8bit in e-mail header) and 7bit. Neither works.
--- BTW, you are talking about two separate things. One is text/html and the other is the character set. I don't know about the latest tb versions, but I don't think TB ever shipped with ASCII support -- it was always internationalized supporting 8-bit fonts and unicode. Under TB Options (I think under edit or Tools menu), There is a section for Display that shows Fonts & Encodings where you can choose western or unicode (suggested in most cases, though Mac uses an incompatible unicode ordering from the rest of the industry). It should display ok, but interoperability in being able to search & edit docs between Mac and any other system may sometimes suffer, but that shouldn't have anything to do with your issue. There is also, under 'composition' a setting for what to do with messages that contain 8-bit characters -- and whether to use 'quoted printable' MIME encoding. That might solve your problem, but also at some possible compatibility issue with some mailers (not mail servers). AFAIK, all mail servers today handle 8bit, and chances are, clients that don't appear to handle things like the funny spacing are usually doing so because the users have internationalization turned off and/or their client not matching their local environment. A basic icky thing you could do, is setup a mail alias on your system that will remove those 0xA0's or change them to regular spaces and could be configured to look for what address to send them to. It would be a bit of work to get it running, but it would be similar to running a procmail or spam filter over incoming email, but in this case, it would be a filter for outgoing email. I certainly wouldn't make it an automatic option, since unicode is too useful and is the default on all the major vendors. BSD has taken their unicode one step further. They are dropping any internationalizations that don't use UTF-8 (or so I heard). So no more 8-bit locales with local encodings....they either have a UTF-8 version that works or they work in another language. It ***could be*** you having unicode turned off -- and your client is sending that space in 8-bit encoding!!... Just checked your email is sending the space character in western-locale encoding, not unicode. That's why other readers can't read it -- they are set for unicode. I would seriously suggest you force, at least, your outgoing email to unicode. It's an option on the fonts and encodings page gotten to at the bottom of your Display tab under "options". -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org