ÆØÅ -- QP in subject

ÆØÅ -- QP in subject

[Thomas Skogestad]

Dammit. My 5.8.8 CVS did this the way I want. I want legible headers!

Then I updated my CVS, Oort! But, see subject. 5.8.7 "works".
(Press C-u g if you don't understand what I mean.)

-- 
thomas.skogestad@jusstud.uio.no
http://www.messengers-of-messiah.org/~csebold/emacs/why.phtml

Re: ÆØÅ -- QP in subject

[Kai Großjohann]

I just did a CVS update less than five minutes ago, and your subject
looks fine to me.  (It contains three Scandinavian characters, an AE
ligature, an O slash, and an A ring.)

kai
-- 
The passive voice should never be used.

Re: ÆØÅ -- QP in subject

[Thomas Skogestad]

* Kai Großjohann

| I just did a CVS update less than five minutes ago, and your subject
| looks fine to me. (It contains three Scandinavian characters, an AE
| ligature, an O slash, and an A ring.)

Uhm. Subject is:

 Subject: =?iso-8859-1?q?=C6=D8=C5?= -- QP in subject

I want:
 
 Subject: Re: ÆØÅ -- QP in subject

-- 
thomas.skogestad@jusstud.uio.no
http://quimby.gnus.org/circus/problem.gif
http://www.messengers-of-messiah.org/~csebold/emacs/why.phtml

Re: ÆØÅ -- QP in subject

[Kai Großjohann]

On 19 Apr 2001, Thomas Skogestad wrote:

> I want:
>  
>  Subject: Re: ÆØÅ -- QP in subject

This is what I see.  Dunno why it fails for you.

kai
-- 
The passive voice should never be used.

Re: ÆØÅ -- QP in subject

[Per Abrahamsen]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> On 19 Apr 2001, Thomas Skogestad wrote:
> 
> > I want:
> >  
> >  Subject: Re: ÆØÅ -- QP in subject
> 
> This is what I see.  Dunno why it fails for you.

He doesn't want to _see_ ÆØÅ.  He wants to _send_ ÆØÅ using unencoded
Latin-1.  

This is a bad idea, because news (and perhaps also mail) is moving
towards unencoded UTF8 in headers, and using unencoded Latin-1 is just
going to make the transition more painful.

Re: ÆØÅ -- QP in subject

[Bjørn Mork]

Thomas Skogestad <tskogest@jusstud.uio.no> writes:
> * Kai Großjohann
> 
> | I just did a CVS update less than five minutes ago, and your subject
> | looks fine to me. (It contains three Scandinavian characters, an AE
> | ligature, an O slash, and an A ring.)

Whether æ is a ligature is language dependant. It's a character in
Scandinavian languages.

> Uhm. Subject is:
> 
>  Subject: =?iso-8859-1?q?=C6=D8=C5?= -- QP in subject
> 
> I want:
>  
>  Subject: Re: ÆØÅ -- QP in subject

C-h v gnus-group-posting-charset-alist


Bjørn

Re: ÆØÅ -- QP in subject

[Thomas Skogestad]

* Bjørn Mork

| C-h v gnus-group-posting-charset-alist

Which is

gnus-group-posting-charset-alist's value is 
(("^\\(no\\|fr\\)\\.[^,]*\\(,[ 	\n]*\\(no\\|fr\\)\\.[^,]*\\)*$" iso-8859-1
  (iso-8859-1))
 ("^\\(fido7\\|relcom\\)\\.[^,]*\\(,[ 	\n]*\\(fido7\\|relcom\\)\\.[^,]*\\)*$" koi8-r
  (koi8-r))
 (message-this-is-mail nil nil)
 (message-this-is-news nil t))

Not sure what to do with this...

-- 
thomas.skogestad@jusstud.uio.no
http://www.messengers-of-messiah.org/~csebold/emacs/why.phtml

Re: ÆØÅ -- QP in subject

[Florian Weimer]

Thomas Skogestad <tskogest@jusstud.uio.no> writes:

> | C-h v gnus-group-posting-charset-alist

> Not sure what to do with this...

Use 'customize-variable' and read the documentation, in particular:

| Note that any value other than nil for HEADER infringes some RFCs, so
| use this option with care.

Re: ÆØÅ -- QP in subject

[Dmitry Paduchih]

>>>>> "KG" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

KG> On 19 Apr 2001, Thomas Skogestad wrote:
>> I want:
>> 
>> Subject: Re: ÆØÅ -- QP in subject
KG> This is what I see.  Dunno why it fails for you.

I guess it is server of your mailing list who decodes the Subject.
The following setting would allow sending of unencoded Subject, but it
fails due to use of message-options:

(add-to-list 'rfc2047-header-encoding-alist '("Subject"))

                Dmitry

Re: ÆØÅ -- QP in subject

[Kai Großjohann]

On 19 Apr 2001, Dmitry Paduchih wrote:

>>>>>> "KG" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE>
>>>>>> writes:
> 
> KG> This is what I see.  Dunno why it fails for you.
> 
> I guess it is server of your mailing list who decodes the Subject.

Gnus decodes it.  I didn't realize that Thomas wants to send unencoded
subjects, I thought he was saying that Gnus didn't decode them.

kai
-- 
The passive voice should never be used.

Re: ÆØÅ -- QP in subject

[Dmitry Paduchih]

>>>>> "PA" == Per Abrahamsen <abraham@dina.kvl.dk> writes:

PA> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

[...]

PA> He doesn't want to _see_ ÆØÅ.  He wants to _send_ ÆØÅ using unencoded
PA> Latin-1.  

PA> This is a bad idea, because news (and perhaps also mail) is moving
PA> towards unencoded UTF8 in headers, and using unencoded Latin-1 is just
PA> going to make the transition more painful.

Well, probably it is a bad idea... But it would be worse idea to use
unencoded UTF8 in the newsgroup or a mailing list where nobody uses it...

                Dmitry

Re: ÆØÅ -- QP in subject

[Per Abrahamsen]

Dmitry Paduchih <paduch@imm.uran.ru> writes:

> Well, probably it is a bad idea... But it would be worse idea to use
> unencoded UTF8 in the newsgroup or a mailing list where nobody uses it...

Yes, in the transition period using MIME encoded headers is the least
bad option.

Re: ÆØÅ -- QP in subject

[Dmitry Paduchih]

>>>>> "PA" == Per Abrahamsen <abraham@dina.kvl.dk> writes:

PA> Dmitry Paduchih <paduch@imm.uran.ru> writes:
>> Well, probably it is a bad idea... But it would be worse idea to use
>> unencoded UTF8 in the newsgroup or a mailing list where nobody uses it...

PA> Yes, in the transition period using MIME encoded headers is the least
PA> bad option.

I'm agree. RFC2047 is a great thing. :-) Unfortunately, it is fringe
at some places. Say, in the hierarchy of fido7.*.

                Dmitry

Re: ÆØÅ -- QP in subject

[Dmitry Paduchih]

Hi Thomas,

try the following:

;;; Hm.
(add-to-list 'rfc2047-header-encoding-alist '("Subject" . none))

It works -- look at the Subject. It may be broken indeed since I do
use another charset, but it doesn't contain any encoding.

                Dmitry

Re: ÆØÅ -- QP in subject

[Doug Alcorn]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> How difficult would it be to have font-lock in message mode
> distinguish between header and body?
> 

I've often thought that the "--text follows this line--" could be used
somehow in this endeavor.  If you just assumed header lines were above
it and body lines were below it it would solve a number of problems
(like wrong fontification of lines that begin with "foo:" in the
body).  It seems like the same kind of code that treats everything
below "^--" as a signature could be used for this.
-- 
(__) Doug Alcorn <doug@lathi.net> http://www.lathi.net chat:lathinet@yahoo|aol
oo / PGP 02B3 1E26 BCF2 9AAF 93F1  61D7 450C B264 3E63 D543
|_/  If you're a capitalist and you have the best goods and they're
     free, you don't have to proselytize, you just have to wait.

Re: ÆØÅ -- QP in subject

[Charles Sebold]

On 26 Nisan 5761, Doug Alcorn wrote:

> I've often thought that the "--text follows this line--" could be used
> somehow in this endeavor.  If you just assumed header lines were above
> it and body lines were below it it would solve a number of problems
> (like wrong fontification of lines that begin with "foo:" in the
> body).  It seems like the same kind of code that treats everything
> below "^--" as a signature could be used for this.

I think the font lock and related stuff for message mode (for composing,
which does not treat signatures differently as far as I can tell) and
that for gnus-article-mode or whatever it is that display articles is
very different and not easily converged.  (I seem to recall this from a
discussion about different colors for different levels of citation a few
months back.)
-- 
Charles Sebold
Random Answer to a Gnus Very Frequently Asked Question:
 To see old posts, enter the group with C-u RET from the *Groups* buffer.
--
27th of Nisan, 5761
--
Seen on someone's helpdesk log, quoted in comp.os.vms:

  VT510 HAD FLAMES COMING OUT THE BACK.
  NO FURTHER TROUBLESHOOTING NEEDED.