[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sylpheed
Subject:    [sylpheed:25354] Re: [PATCH] do not use US-ASCII if there are
From:       Stefaan A Eeckels <Stefaan.Eeckels () ecc ! lu>
Date:       2005-07-11 9:05:01
Message-ID: 20050711110501.636ae2db.Stefaan.Eeckels () ecc ! lu
[Download RAW message or body]

On Mon, 11 Jul 2005 12:44:40 +0400
Antony Dovgal <tony2001@phpclub.net> wrote:

> On Mon, 11 Jul 2005 10:30:20 +0200 Stefaan A Eeckels <Stefaan.Eeckels@ecc.lu>
> wrote:
> 
> > On Mon, 11 Jul 2005 12:18:57 +0400 Antony Dovgal <tony2001@phpclub.net>
> > wrote:
> > 
> > > On Mon, 11 Jul 2005 13:52:21 +0900 Hiroyuki Yamamoto <hiro-y@kcn.ne.jp>
> > > wrote:
> > > 
> > > > I've tested it with unmodified version, and there was no problem (see
> > > > this message's Subject).
> > > 
> > > You mean this?  "Re: [sylpheed:25347] Re: [PATCH] do not use US-ASCII if
> > > there are non-ascii symbols inthe subject (Test: ____)" See this "____" ?
> > > This is exactly what I'm talking about =)
> > 
> > I had no problem with Hiroyuki's Subject: | Subject: [sylpheed:25347] Re:
> > [PATCH] do not use US-ASCII if there are | non-ascii symbols in the subject
> > (Test: æøåü)
> > 
> > which is encoded as follows: (Test: =?ISO-8859-1?B?5vjl/Ck=?= The fact that
> > the Content-Type header says "US-ASCII" had no influence on the rendering
> > of the Subject.
> > 
> > There is no need for correspondence between the encoding in the body and
> > the encoding in the Subject. 
> 
> Right. But this is in case where there is encoding set in the subject.  (and
> for some reason it didn't work for me even in the latter case).

> >Are you sure you don't have locale setting problems on your machine?
> 
> Not sure I understood this, could you plz elaborate?  How my locale could be
> related to decoding a subject (if it still works fine when decoding body)?
> Btw, my locale ru_RU.UTF8 and there were no problems with sylpheed2 until
> beta 3 or so.

The encoding in the Subject ensures that it doesn't contain non-ASCII
characters which would violate the RFC. How =?ISO-8859-1?B?5vjl/Ck=?=
is rendered by the receiving MUA is its problem. On my machine,
sylpheed has no problems rendering the ISO-8859-1 characters in the
Subject even though the Content-Header is US-ASCII. Therefore, sylpheed
is correctly instructing the display to show the Subject and body (or
it would work for me either).

In your case, these correct instructions don't result in the correct 
characters. The Subject is displayed with a different font than the
body. If you did see the accented characters in the copy of Hiroyuki's
Subject in my message, it follows that the font you use for Sylpheed's
interface isn't capable of rendering ISO-8859-1 characters, whereas the
font used in the Message view (which would usually be non-proportional)
has the appropriate characters. 

Did you perchance change your system font recently?

Take care,

-- 
Stefaan
-- 
As complexity rises, precise statements lose meaning,
and meaningful statements lose precision. -- Lotfi Zadeh 

[prev in list] [next in list] [prev in thread] [next in thread]