Gnus development mailing list
 help / color / mirror / Atom feed
From: Mike FABIAN <mfabian@suse.de>
Cc: xemacs-beta@xemacs.org
Subject: Re: Status of XEmacs' (21.5) UTF-8 capabilities
Date: Wed, 11 Feb 2004 16:37:51 +0100	[thread overview]
Message-ID: <s3tptclzkxc.fsf@magellan.suse.de> (raw)
In-Reply-To: <v9u130lya7.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon, 12 Jan 2004 21:14:40 +0100")

[-- Attachment #1: Type: text/plain, Size: 346 bytes --]

Reiner Steib <4.uce.03.r.s@nurfuerspam.de> さんは書きました:

> Is Steffen Lorch's (he did the tests with XEmacs) and my assumption
> correct, that (Gnus with) XEmacs cannot post UTF-8 articles?

You need to patch Gnus v5.10.6 a little bit. Attached is the small patch
for Gnus v5.10.6 which I use to make XEmacs be able to post in UTF-8:


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: mm-util.el.patch --]
[-- Type: text/x-patch, Size: 634 bytes --]

Index: mm-util.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/mm-util.el,v
retrieving revision 6.53
diff -u -r6.53 mm-util.el
--- mm-util.el	6 Jan 2003 04:31:23 -0000	6.53
+++ mm-util.el	31 Jan 2003 21:35:17 -0000
@@ -541,7 +541,9 @@
     (if (and (memq 'iso-2022-jp-2 charsets)
 	     (memq 'iso-2022-jp-2 hack-charsets))
 	(setq charsets (delq 'iso-2022-jp charsets)))
-    charsets))
+    (if (> (length charsets) 1)
+	'(utf-8) 
+      charsets)))
 
 (defmacro mm-with-unibyte-buffer (&rest forms)
   "Create a temporary buffer, and evaluate FORMS there like `progn'.

[-- Attachment #3: Type: text/plain, Size: 100 bytes --]


-- 
Mike FABIAN   <mfabian@suse.de>   http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。

  reply	other threads:[~2004-02-11 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-12 20:14 Reiner Steib
2004-02-11 15:37 ` Mike FABIAN [this message]
2004-02-11 16:16   ` Mike FABIAN

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=s3tptclzkxc.fsf@magellan.suse.de \
    --to=mfabian@suse.de \
    --cc=xemacs-beta@xemacs.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).