Gnus development mailing list
 help / color / mirror / Atom feed
From: Marcus Frings <iam-est-hora-surgere@fuckmicrosoft.com>
Subject: Re: Oort: Font-Encoding Problem?
Date: Sat, 16 Nov 2002 22:45:32 +0100	[thread overview]
Message-ID: <1545428605.20021116224532@gmx.net> (raw)
In-Reply-To: <84lm3tb4zj.fsf@lucy.cs.uni-dortmund.de>

Kai Großjohann wrote:
  
> Marcus Frings <protagonist@gmx.net> writes:
>> I upgrade Oort via CVS daily. Since 2002-11-01 I'm having problems with
>> writing texts in iso-8859-1. If I downgrade to an Oort version from
>> 2002-10-31 everything works fine again. When I want to write a posting
>> with German umlauts and send it I receive following messages:
>> XEmacs 21.4.10 (Win32): "Malformed list: 8bit"
>> Emacs 21.2.1 (Debian): "Wrong type argument: listp, 8bit"

> This change seems to be the candidate for trouble:
> 2002-11-01  Jesper Harder  <harder@ifa.au.dk>
>         * mm-bodies.el (mm-body-encoding): Don't return 8bit for 7bit
>         charset.

I agree. I had read this entry in the changelog, too, but I was not sure
if this one causes the bug.

> But I don't understand the code.  Could you M-x load-library RET
> mm-bodies.el RET (the .el is important), then M-x
> toggle-debug-on-error RET, then reproduce the error message?  That
> should give you a backtrace, which you please post here.

Here is the output:

Signaling: (malformed-list 8bit)
  assq(iso-8859-1 8bit)
  (cdr (assq charset mm-body-charset-encoding-alist))
  (eq (quote 7bit) (cdr (assq charset mm-body-charset-encoding-alist)))
  (not (eq (quote 7bit) (cdr ...)))
  (and (not mm-use-ultra-safe-encoding) (not longp) (not (eq ... ...)) (or (eq t ...) (memq charset ...) (eq charset mail-parse-charset)))
  (cond ((and ... ... ...) bits) ((and ... ... ... ...) bits) (t (let ... ... ... encoding)))
  (let ((bits ...) (longp ...)) (require (quote message)) (cond (... bits) (... bits) (t ...)))
  mm-body-encoding(iso-8859-1 nil)
  mml-generate-mime-1((part (type . "text/plain") (contents . "ignore no reply\nä ö ü\n\nGruß,\nMarcus\n\n\n")))
  mml-generate-mime()
  message-encode-message-body()
  message-send-news(nil)
  message-send-via-news(nil)
  message-send(nil)
  message-send-and-exit(nil)
  call-interactively(message-send-and-exit)
   
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!





  reply	other threads:[~2002-11-16 21:45 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 [this message]
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
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=1545428605.20021116224532@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).