Re: OT: rant, was: Re: e-mail encoding/formatting
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday, May 4 at 07:42 PM, quoth markus reichelt:
> I presume that you did not use a per mailing list config? I do, but
> then again I solely partake in mailing lists about unix systems.
I do when I have to.
>> have a suggestion of a standard, widely supported charset to use
>> that has the correct characters, I'm all ears.
>
> Well, I'm not an ISO-specialist, but perhaps some guru will jump in;
> I sure hope so. Especially when it comes to curly quotes written on a
> UTF-8 system with mutt, and displayed correctly (via substitutes) on
> a non-UTF-8 terminal in mutt, I'm very happy with any ISO-8859
> charset being used either as orig (read: end user) charset or as
> primary send_charset.
HEH. Well, I could stick to ISO-8859-13 (Baltic Rim), which is the
only ISO-8859 charset that has both. However, something tells me
that's hardly portable.
> I just wonder about you using a send_charset setting of iso-8859-1
> and if the problems of ??? quotes would disappear w/o //TRANSLIT;
> because whenever you used curly quotes ??? would appear instead.
> Maybe getting rid of the us-ascii in Default:
> "us-ascii:iso-8859-1:utf-8" would do the trick. Then again, what
> would happen to those actually using us-ascii? I don't know but
> assume again some ???. I see some FAQ issues rise once again, because
> //TRANSLIT may not work in all cases, sadly.
Not quite. Mutt does not downgrade your charset for you, and it merely
uses the first charset that would encode all of the characters in your
mail message; so removing us-ascii from send_charset would achieve
nothing more than preventing me from sending messages marked as
us-ascii even if my message contained no non-ascii characters.
Interestingly, even setting my send_charset to "us-ascii//TRANSLIT"
doesn't ensure that my outbound messages are in strictly us-ascii.
~Kyle
- --
Nonsense. Space is blue and birds fly through it.
-- Heisenberg
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFEWlK8BkIOoMqOI14RAoFTAJ9qjuitqP5MEyhSf0yXGLw8T7iibgCfWtSP
DSUaX/GV5DfyBDCs14ybhxg=
=XQoI
-----END PGP SIGNATURE-----