Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Miles Bader <miles@gnu.org>
Cc: ding@gnus.org
Subject: Re: Emacs unicode merge changes to Gnus
Date: Sat, 16 Feb 2008 01:39:03 +0100	[thread overview]
Message-ID: <v9r6fd3fbs.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87tzk9zxsq.fsf@catnip.gol.com> (Miles Bader's message of "Sat, 16 Feb 2008 06:59:01 +0900")

On Fri, Feb 15 2008, Miles Bader wrote:

> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>> Emacs 23 still has `emacs-mule' as coding system.  Does it allow to
>> encode everything?  If so, we might use `emacs-mule' instead of
>> `utf-8-emacs'.  If not, we could recommend setting
>> `mm-auto-save-coding-system' to `emacs-mule' for those who want to use
>> Gnus in Emacs 23 and Emacs 21/22.
>
> Emacs 23 still supports emacs-mule (and AFAIK, it encodes "everything"),
> though in general I think it's better to move away from it when possible
> (utf-8 and utf-8-emacs are readable by other programs in non-binary
> cases, and by older versions in "many" cases).

For drafts, I can imagine to read the files with other programs, but
for ~/.newsrc.eld?

> So there are really three independent questions (patch hunks :-):
>
>   1) Should gnus write the cookie?   (obviously yes, I think)
>
>   2) Should Gnus stop forcing the coding system when it reads the file?
>      (i.e., should Gnus let coding: do its job)
>
>   3) Should Gnus switch to utf-8-emacs as the default coding system for
>      writing files?
>
> It seems like the safest thing, if you're worried about "back switchers"
> (as well as users of older Emacs versions using CVS Gnus) is to apply
> hunks (1) and (2) but not (3); that should at least set things up for an
> easier switch to utf-8 in the future when it's deemed more acceptable.

Sounds reasonable.  Please apply (1) and (2).

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



  reply	other threads:[~2008-02-16  0:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06  2:30 Miles Bader
2008-02-06 22:10 ` Reiner Steib
2008-02-06 22:44   ` Miles Bader
2008-02-06 23:06     ` Reiner Steib
2008-02-06 23:22       ` Miles Bader
2008-02-06 23:27   ` Katsumi Yamaoka
2008-02-07  8:24     ` Reiner Steib
2008-02-07  9:19       ` Katsumi Yamaoka
2008-02-07 10:24         ` Miles Bader
2008-02-15  0:42           ` Miles Bader
2008-02-15 17:30             ` Reiner Steib
2008-02-15 21:59               ` Miles Bader
2008-02-16  0:39                 ` Reiner Steib [this message]
2008-02-20  0:29                   ` Miles Bader
2008-02-20 19:34                     ` Reiner Steib
2008-02-26 21:17                       ` Reiner Steib
2008-02-20  0:30                   ` Miles Bader
2008-02-20 19:23                     ` Reiner Steib
2008-02-23 18:07                       ` Reiner Steib
2008-02-24  1:41                         ` Miles Bader

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=v9r6fd3fbs.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=miles@gnu.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).