all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Reiner Steib <reinersteib+from-uce@imap.cc>
Subject: Re: Encodings in message
Date: Fri, 04 Nov 2005 16:25:17 +0100	[thread overview]
Message-ID: <v9oe50cu5e.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: u0tkbll04sdnl.fsf_-_@merleau.ntc.nokia.com

On Fri, Nov 04 2005, Marc Girod wrote:

> In mails and news postings, which I process using Gnus, I tend to see
> all the characters correctly (most of them anyway), but to send while
> replying, what my correspondents see as garbage.
>
> Indeed, looking at my messages with:
>
>   (find-charset-region (point) (mark))
>
> I often notice different charsets.
>
> My question: how to force using only one (iso8859-1 -- forgetting the
> few non supported characters)?

Instead of such a brute force destruction of information, you should
analyze the problem.  But "see as garbage" is not a sufficient
description to even guess what could be wrong.

If you use Gnus/5.9 Emacs/21.2 as your headers suggest, I'd strongly
recommend to upgrade at least to Emacs 21.4.  The Gnus version (also
labeled 5.9) of Emacs 21.4 provides `mm-coding-system-priorities':

,----[ <f1> v mm-coding-system-priorities RET ]
| mm-coding-system-priorities is a variable defined in `mm-util.el'.
| Its value is 
| (iso-8859-1 iso-8859-2 iso-8859-15 mule-utf-8)
| 
| Documentation:
| Preferred coding systems for encoding outgoing messages.
| 
| More than one suitable coding system may be found for some text.
| By default, the coding system with the highest priority is used
| to encode outgoing messages (see `sort-coding-systems').  If this
| variable is set, it overrides the default priority.
`----

Even better than using Emacs 21.4 + Gnus 5.9 would be to upgrade to
Gnus 5.10 available from www.gnus.org.

Unfortunately the latest stable release is still 5.10.6 although the
stable branch in CVS ("v5-10") contains lots of bug fixes to warrant a
release 5.10.7.  Maybe I should tickle Lars again.  :-)

Bye, Reiner.

Followup-To: gnu.emacs.gnus set, since this is Gnus specific.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

      reply	other threads:[~2005-11-04 15:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 14:37 wikipedia and UTF8 coding (emacs21) Uwe Brauer
2005-11-03 15:49 ` Peter Dyballa
2005-11-03 16:33 ` Stefan Monnier
2005-11-03 18:45   ` Uwe Brauer
2005-11-03 19:04     ` Peter Dyballa
2005-11-03 19:09       ` Uwe Brauer
2005-11-03 19:43         ` Peter Dyballa
     [not found]         ` <mailman.13846.1131047004.20277.help-gnu-emacs@gnu.org>
2005-11-03 20:30           ` Uwe Brauer
2005-11-04 12:35           ` Reiner Steib
     [not found]       ` <mailman.13841.1131044962.20277.help-gnu-emacs@gnu.org>
2005-11-22 19:49         ` Stefan Monnier
2005-12-02 17:58           ` font problem persists (was: wikipedia and UTF8 coding (emacs21)) Uwe Brauer
2005-12-02 20:08             ` Peter Dyballa
2005-12-03  2:21             ` font problem persists Stefan Monnier
2005-12-05 17:30               ` Uwe Brauer
     [not found]             ` <mailman.17688.1133554097.20277.help-gnu-emacs@gnu.org>
2005-12-05 17:25               ` Uwe Brauer
2005-11-04 12:34     ` wikipedia and UTF8 coding (emacs21) Reiner Steib
2005-11-22 19:46     ` Stefan Monnier
2005-11-23 20:55       ` Reiner Steib
     [not found]       ` <mailman.16628.1132865580.20277.help-gnu-emacs@gnu.org>
2005-11-25  4:29         ` Stefan Monnier
2005-11-03 17:09 ` Denis H. G.
     [not found] ` <mailman.13812.1131033002.20277.help-gnu-emacs@gnu.org>
2005-11-03 18:32   ` Reiner Steib
2005-11-04 20:22     ` Uwe Brauer
2005-11-22 19:40       ` Stefan Monnier
2005-11-06 10:16     ` using emacs 21 (was: " Uwe Brauer
2005-11-06 10:48       ` Peter Dyballa
2005-11-06 10:59       ` Peter Dyballa
2005-11-04 14:05   ` Encodings in message (was: wikipedia and UTF8 coding (emacs21)) Marc Girod
2005-11-04 15:25     ` Reiner Steib [this message]

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=v9oe50cu5e.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+from-uce@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.