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

List:       sylpheed
Subject:    [sylpheed:25328] Re: [PATCH] do not use US-ASCII if there are non-ascii symbols in
From:       Daichi Kawahata <daichi.k () aioros ! ocn ! ne ! jp>
Date:       2005-07-09 2:21:43
Message-ID: 20050709112143.28c9effd.daichi.k () aioros ! ocn ! ne ! jp
[Download RAW message or body]

On Sat, 9 Jul 2005 02:47:31 +0400
Antony Dovgal wrote:

> Also, starting from the same moment(?), non-ASCII "to" & "reply-to"
> headers are garbled by sylpheed when I click Reply/Reply to All.
> All non-ASCII letters there just turn into '_', while body is fine 
> (and subject is fine too, after the patch =)). 
> 
> From what I can see, this happens because compose_parse_header()
> calls conv_unmime_header() with NULL encoding, which is of course
> wrong, as the original letter I'm replying to has it's own character
> set and I'd like to see it working =)

Firstly I'd like to say these 8bit character in the header part have
been bothering me long time before, so I also have been looking for a
better workaround as non-programmer. If possible, please take a look
at the [sylpheed:24149], [sylpheed:24152], [sylpheed:24150], as you
can see, there had discussion in which Godwin had referred to RFC 2822.

Sorry in advance, probably it sounds noisy, but my question to the
others (esp. RFC guru) starts from here, is that also related with
RFC 2047? in other words, is it allowed parsing a 8bit string with
self-implemented function? as far as I know, even Outlook uses 'B'
encoding for non-ASCII character appearing in the header. In addition
I've already seen related modifying at the:

    2005-03-03

            * use Content-Type's charset as a fallback encoding of
              broken header strings (thanks to Sergey Pinaev).

but thinking that still I have to see broken header as well as you,
does not the above workaround work at all? My main confusion is that
I really don't know whether it was fault on Sylpheed or on a MUA
sending mail with non-encoded 8bit header (at Subject, Sender).

I'm indeed confusing about that in these days.

> does anybody mind if I add --enable-debug switch to the configure ?
> It's quite unconvenient to edit src/Makefile to get "-02" removed
> and get "-Wall" inserted. Also, it would be nice to have several
> levels of debug which would differ by they debug output.

If you ware talking about just compile-time flags, you can set CFLAGS
before running configure ('-O2 -g -W -Wall -Wformat=2 -fno-var-tracking'
are the mine). For me, it doesn't seem they're forced to over-write by
autofiles. Probably what you'd like to say is that over-writing user
defined CFLAGS and turning debug codes in the Sylpheed on by using
'--enable-debug' switch though.

Regards,
-- 
Daichi

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