Gnus development mailing list
 help / color / mirror / Atom feed
From: Didier Verna <verna@inf.enst.fr>
Subject: Re: test charset / encoding
Date: 28 Sep 1999 09:54:20 +0200	[thread overview]
Message-ID: <qyjbtanh3o3.fsf@metheny.enst.fr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "27 Sep 1999 20:45:57 +0200"

Lars Magne Ingebrigtsen wrote:

> (mm-find-mime-charset-region (point-min) (point-max))
> => (iso-8859-1)
> 
> If not, something is wrong somewhere in the bowels of that function,
> or somewhere in its vicinity.


        => nil

        Aaaaaaaaaaaaaaaaaaaaaaaaarghhhhhhhhhhhhhhhhhhhhhhhhh

I've got it. It's the 'enable-multibyte-character under XEmacs problem again.
Now look, this really makes me furious :-( I think I will finally patch XEmacs
to ditch this (*&^@#%^ variable.

        The problem: this variable is here (in XEmacs) only for compatibility
with GNU Emacs (ie., just to be bound), but it is *MEANINGLESS*. However, some
code do take it into account which leads to bogus behavior (w3 for instance,
from the picons code turns it to nil somewhere). What we have here is another
example of fuckage due to this variable[1]. The first problem I encountered
was japaneese not displayed at all.


Lars: if I patch gnus to remove any use of this variable under XEmacs, will
you accept it ?

Bill: s/gnus/w3/


Footnotes: 
[1]  Steve, I hope you're convinced now.

-- 
    /     /   _   _       Didier Verna        http://www.inf.enst.fr/~verna/
 - / / - / / /_/ /     ENST, INFRES C201.1       mailto:verna@inf.enst.fr
/_/ / /_/ / /__ /        46 rue Barrault        Tel.   +33 (1) 45 81 73 46
                       75013 Paris, France      Fax.   +33 (1) 45 81 31 19


  reply	other threads:[~1999-09-28  7:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-27 18:29 Didier Verna
1999-09-27 18:45 ` Lars Magne Ingebrigtsen
1999-09-28  7:54   ` Didier Verna [this message]
1999-11-05 23:02     ` Lars Magne Ingebrigtsen
1999-09-28  8:00   ` Didier Verna

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=qyjbtanh3o3.fsf@metheny.enst.fr \
    --to=verna@inf.enst.fr \
    /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).