From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Emacs unicode merge changes to Gnus
Date: Fri, 15 Feb 2008 18:30:04 +0100 [thread overview]
Message-ID: <v98x1m3z6r.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <871w7fvymc.fsf@catnip.gol.com>
On Fri, Feb 15 2008, Miles Bader wrote:
> So, I still don't know what to do about this.
Sorry, I didn't have time to look into the coding system issue yet.
> [By default, I'll just commit those changes.]
I think all changes beside `gnus-ding-file-coding-system'
(`mm-universal-coding-system') are clear. I.e. proceed as I suggested
in my first reply <news:v9prv9rb28.fsf@marauder.physik.uni-ulm.de>:
- Merge "Add gbk and GB18030" changes
- Revert `mm-hack-charsets' removal in Emacs CVS (and don't merge it
to Gnus, of course).
- `rfc2104-hexstring-to-byte-list': I'm not sure. Unless someone
sees a problem now, merge it to Gnus.
> Miles Bader <miles.bader@necel.com> writes:
>> What about (1) using the coding: cookie, (2) change the coding system
>> used to be utf-8 if possible (no binary), and utf-8-emacs otherwise.
>>
>> That should more or less work correctly except when people have binary
>> junk, and that should be very rare (right...?).
>>
>> I guess it won't work for some other cases, like someone with CJK text
>> who switches from Emacs 23 to Emacs 21, but ...
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.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2008-02-15 17:30 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 [this message]
2008-02-15 21:59 ` Miles Bader
2008-02-16 0:39 ` Reiner Steib
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=v98x1m3z6r.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--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).