From: Marcus Frings <iam-est-hora-surgere@fuckmicrosoft.com>
Subject: Re: Oort: Font-Encoding Problem?
Date: Sun, 17 Nov 2002 11:25:50 +0100 [thread overview]
Message-ID: <19437485731.20021117112550@gmx.net> (raw)
In-Reply-To: <m3heegncil.fsf@defun.localdomain>
Jesper Harder wrote:
> Marcus Frings <protagonist@gmx.net> writes:
>> I changed the option to
>> (setq mm-body-charset-encoding-alist
>> '((iso-8859-15 . 8bit)
>> (iso-8859-1 . 8bit)))
>> and everything works fine again now.
> Yes, that looks fine.
Thank you.
> In general, if you're not exactly sure about how to set an option it's
> sometimes better to use the customize interface -- this makes errors
> less likely. E.g. try
> `M-x customize-option mm-body-charset-encoding-alist'
Well, usually I do exactly like that but during my first steps with Gnus
I took public configuration files from webpages and this old option I
used before came from such a file. I guess an alternative to my way is
this:
;; http://www.zonix.de/div/el/gnus_message.html
;; Force 8bit-Encoding
(add-to-list 'mm-body-charset-encoding-alist '(iso-8859-1 . 8bit))
(if (mm-coding-system-p 'iso-8859-15)
(add-to-list 'mm-body-charset-encoding-alist '(iso-8859-15 . 8bit)))
Are there any (dis)advantages using add-to-list instead of setq? I
assume that this is going to be my last question regarding this topic
for my problem seems to be solved. Just being curious... :-)
Regards,
Marcus
--
Fickle minds, pretentious attitudes and ugly | PGP-Key: [DH/DSS] 4096-bit
make-up on ugly faces... The Gothgoose | Key-ID: 0xE10F502E
Of The Week: http://www.gothgoose.net | Encrypted mails welcome!
next prev parent reply other threads:[~2002-11-17 10:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 19:38 Marcus Frings
2002-11-16 21:05 ` Kai Großjohann
2002-11-16 21:45 ` Marcus Frings
2002-11-16 22:17 ` Jesper Harder
2002-11-16 23:26 ` Marcus Frings
2002-11-17 2:41 ` Jesper Harder
2002-11-17 10:25 ` Marcus Frings [this message]
2002-11-17 11:54 ` Kai Großjohann
2002-11-17 19:48 ` Marcus Frings
2002-11-16 23:31 ` Christoph Conrad
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19437485731.20021117112550@gmx.net \
--to=iam-est-hora-surgere@fuckmicrosoft.com \
--cc=protagonist@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).