Oort: Font-Encoding Problem?

Oort: Font-Encoding Problem?

[Marcus Frings]

Hello,

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"

Nevertheless sending text in us-ascii works - only text with umlauts
fail.
Since I don't think that this "bug" hasn't been discovered within the
last weeks I guess I might have to change some options in my
.emacs/.gnus-configuration files.

I've tried to find a solution for it by searching at www.google.com,
groups.google.com and ding-archive but unfortunately it was not really
successful so far.

Any ideas?

Kind 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!

Re: Oort: Font-Encoding Problem?

[Kai Großjohann]

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.

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.

Thanks,
kai
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)

Re: Oort: Font-Encoding Problem?

[Marcus Frings]

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!

Re: Oort: Font-Encoding Problem?

[Jesper Harder]

Marcus Frings <iam-est-hora-surgere@fuckmicrosoft.com> writes:

>> 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"
>
> Here is the output:
>
> Signaling: (malformed-list 8bit)
>   assq(iso-8859-1 8bit)
>   (cdr (assq charset mm-body-charset-encoding-alist))

What do get when you do `C-h v mm-body-charset-encoding-alist'?  

It should be an association list, which it doesn't appear to be for you.
Did you customize the option?

Re: Oort: Font-Encoding Problem?

[Marcus Frings]

Saturday, November 16, 2002, 11:17:26 PM, you wrote:

> Marcus Frings <iam-est-hora-surgere@fuckmicrosoft.com> writes:
>> Signaling: (malformed-list 8bit)
>>   assq(iso-8859-1 8bit)
>>   (cdr (assq charset mm-body-charset-encoding-alist))

> What do get when you do `C-h v mm-body-charset-encoding-alist'?  

This is the output:

`mm-body-charset-encoding-alist' is a variable declared in Lisp.
  -- loaded from "mm-bodies.el"

Value: 8bit

> It should be an association list, which it doesn't appear to be for you.
> Did you customize the option?

Yes, before I used (setq mm-body-charset-encoding-alist (quote 8bit))
which really worked fine all the time.
But I think I have found the solution. Christoph's mail helped me and
pulled me into the right direction. 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. With these options I tried to send
a posting to de.test and I succeeded. Since I am really not a Lisp guru
I would like to know if these settings are correct/fine.

Thanks in advance to Kai, Christoph and you for your excellent and fast
help.

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!

Re: Oort: Font-Encoding Problem?

[Christoph Conrad]

Hi Marcus,

    > Signaling: (malformed-list 8bit) assq(iso-8859-1 8bit)

Looks like mm-body-charset-encoding-alist is set to '8bit. This
should be a list, see the doc string for the variable.

Best regards,
cu, -cc-
-- 
Computers are useless.  They can only give you answers.
     Pablo Picasso

Re: Oort: Font-Encoding Problem?

[Jesper Harder]

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. With these options I tried to
> send a posting to de.test and I succeeded. Since I am really not a
> Lisp guru I would like to know if these settings are correct/fine.

Yes, that looks fine.  

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'

-- 
Cheers,
Jesper Harder

Re: Oort: Font-Encoding Problem?

[Marcus Frings]

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!

Re: Oort: Font-Encoding Problem?

[Kai Großjohann]

Marcus Frings <iam-est-hora-surgere@fuckmicrosoft.com> writes:

> Are there any (dis)advantages using add-to-list instead of setq?

That's impossible to answer.  They just do different things.  With
(setq foo '(a b c)) you set the variable foo to that value.  With
(add-to-list 'foo 'a) you add an element to the list foo.

It depends on the circumstances whether you want to delete the old
entries or just add new ones.

That said, I find that I usually just add items to alists because
usually the alists will do a useful job for most cases, so I just
need to modify one case or two.  Also, I then profit from new entries
into the alist in newer versions of the software.  Note that Lisp
traverses alists from the beginning and uses the first matching
item.  And add-to-list adds an item to the beginning.  This means
that even if there is an item in the alist already, the item you add
will take precedence.

Does this make sense?

kai
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)

Re: Oort: Font-Encoding Problem?

[Marcus Frings]

Kai Großjohann wrote:
  
[Explanation snipped]
> Does this make sense?

Yes, it does. Thank you for the explanation.

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!