From: TeXitoi <texitoi@NOSPAMtexitoi.homelinux.org>
Subject: Re: coding system for outgoing messages
Date: 07 Apr 2005 10:10:42 +0200 [thread overview]
Message-ID: <873bu33t31.fsf@localhost.localdomain> (raw)
In-Reply-To: <v9psx7njc4.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <reinersteib+from-uce@imap.cc> writes:
> On Wed, Apr 06 2005, TeXitoi wrote:
>
> > (setq mm-coding-system-priorities '(iso-8859-1 iso-8859-15 utf-8))
> >
> > (so the same thing), but I have that in my .emacs, emacs was reloaded,
> > and this post is in utf-8 :(
>
> In your Gnus version (Gnus 5.9 from Emacs 21.[34]) need Emacs coding
> systems names (`mule-utf-8', `iso-latin-*', ...) instead of MIME
> charset names (`utf-8', `iso-8859-*', ...) in
> `mm-coding-system-priorities'. As this behavior obviously is
> irritating, we have fixed it to allow both in the 5.10.x series.
thanks a lot, it (almost) work : I've
(setq mm-coding-system-priorities
'(iso-latin-1 iso-latin-9 mule-utf-8))
that work for latin-0 and latin-9, but if I post in japanese, it's in
shift-jp (I think, I'm not expert in japanese codings), and if I mix
accents and japanese charset, it want to user différent mime part. an
idea to fix this (cosmetic) problem?
--
Guillaume Pinot http://wwwetu.utc.fr/~pinotgui/
« L'amour, c'est comme le nombre Pi. Naturel, irrationnel et très
important. » -- Lisa Hoffman
() Campagne du ruban ascii -- contre les mails en html
/\ Contre les pièces jointes Microsoft
next prev parent reply other threads:[~2005-04-07 8:10 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 15:22 bitstream vera sans mono ugly in gnus Peter Petersen
2005-03-13 21:39 ` Frank Schmitt
2005-03-14 11:00 ` Peter Petersen
2005-03-14 12:19 ` Frank Schmitt
2005-03-14 13:57 ` Peter Petersen
2005-03-14 14:49 ` Aidan Kehoe
2005-03-14 14:54 ` Aidan Kehoe
2005-03-14 15:42 ` Peter Petersen
2005-03-14 15:57 ` Aidan Kehoe
2005-03-14 23:45 ` Miles Bader
2005-03-14 17:29 ` Jochem Huhmann
2005-03-14 23:58 ` Miles Bader
2005-03-15 20:25 ` Stefan Monnier
2005-03-15 21:56 ` Frank Thieme
2005-03-16 4:39 ` Stefan Monnier
2005-03-26 0:04 ` Frank Thieme
2005-03-17 18:43 ` Peter K. Lee
2005-03-20 23:26 ` Peter Petersen
2005-03-21 0:19 ` Peter Petersen
2005-03-21 0:45 ` Aidan Kehoe
2005-03-21 1:21 ` Peter Petersen
2005-03-21 1:29 ` Johan Bockgård
2005-04-05 21:24 ` trouble with emacs -nw -f gnus and character sets Peter Petersen
2005-04-05 22:16 ` Peter Petersen
2005-04-06 5:50 ` Steinar Børmer
2005-04-06 6:09 ` Steinar Børmer
2005-04-06 20:02 ` thanks, but new problem: utf-8 on a virtual text console Peter Petersen
2005-04-06 20:19 ` TeXitoi
2005-04-06 21:47 ` Peter Petersen
2005-04-06 21:20 ` coding system for outgoing messages (was: thanks, but new problem: utf-8 on a virtual text console) Reiner Steib
2005-04-06 21:56 ` TeXitoi
2005-04-06 23:04 ` coding system for outgoing messages Peter Petersen
2005-04-07 7:20 ` Reiner Steib
2005-04-07 8:10 ` TeXitoi [this message]
2005-04-07 9:52 ` Reiner Steib
2005-04-07 10:20 ` TeXitoi
2005-03-26 23:37 ` bitstream vera sans mono ugly in gnus Stefan Monnier
2005-03-27 18:38 ` Peter Petersen
2005-03-29 5:38 ` Donald Arseneau
2005-03-29 8:06 ` xterm-mouse-mode (was: bitstream vera sans mono ugly in gnus) Reiner Steib
2005-03-17 21:34 ` bitstream vera sans mono ugly in gnus Neil Woods
2005-03-15 16:44 ` Frank Thieme
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=873bu33t31.fsf@localhost.localdomain \
--to=texitoi@nospamtexitoi.homelinux.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).