Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+from-uce@imap.cc>
Cc: bugs@gnus.org, Ding List <ding@gnus.org>
Subject: Re: Encoding buffer before sending does translate umlauts to question marks
Date: Thu, 13 Oct 2005 18:38:48 +0200	[thread overview]
Message-ID: <v94q7le5if.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87br1twm8y.fsf@ID-24456.user.uni-berlin.de> (Christoph Conrad's message of "Thu, 13 Oct 2005 15:58:37 +0200")

On Thu, Oct 13 2005, Christoph Conrad wrote:

> No Gnus v0.4
> GNU Emacs 22.0.50.1 (i686-pc-linux-gnu)
>  of 2005-10-02 on brabbelbox
> 200 news.online.de InterNetNews NNRP server INN 2.3.5 ready (posting ok).
>
> Hello,
>
> i can't remember that i changed gnus configuration. Effect since one
> week is: Latin 1 mule encoded umlauts are encoded correctly in the
> outgoing mail, Latin 9 umlauts in the same mail are translated to '?'
> (question marks).
[...]
> The problem reveals on windows, which i use in the company. This bug
> report is written on GNU/Linux. The prefer-coding-system is iso-8859-1,
> the set-language-environment "Latin 9".

Thanks for you report.  The hint "one week" was very useful.  I have
installed a fix.  You you please try again after "cvs up"?

The introduction of `mm-charset-override-alist' was buggy.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



       reply	other threads:[~2005-10-13 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87br1twm8y.fsf@ID-24456.user.uni-berlin.de>
2005-10-13 16:38 ` Reiner Steib [this message]
2005-10-13 17:57   ` Christoph Conrad
2005-10-13 20:26     ` Reiner Steib
2005-10-14  6:56       ` Christoph Conrad
2005-10-17 10:03   ` Encoding buffer before sending does translate umlauts to question 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=v94q7le5if.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+from-uce@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=bugs@gnus.org \
    --cc=ding@gnus.org \
    /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).