[bug #20252] [gnu.org #336933] RFC2047 header encoding bug

2007-08-04 Thread Earl Hood
Update of bug #20252 (project mhonarc): Open/Closed:Open = Closed Fixed Release: = N/A ___ Reply to this item at:

[bug #20252] [gnu.org #336933] RFC2047 header encoding bug

2007-08-04 Thread Earl Hood
Follow-up Comment #14, bug #20252 (project mhonarc): My guess the following bug (fixed in v2.6.11) is the source of the problem: https://savannah.nongnu.org/bugs/?11187 Since it appears the problem is fixed in a later version of mhonarc, I'm going to close this item. If the problem persists

[bug #20252] [gnu.org #336933] RFC2047 header encoding bug

2007-08-03 Thread Ward Vandewege
Follow-up Comment #12, bug #20252 (project mhonarc): We are still running MHonarc 2.6.10 on the GNU lists server. I've just tested the conversion of the message with ./mhonarc -single input output.html which generates the faulty encoding with 2.6.10, but does the right thing with 2.6.16.

[bug #20252] [gnu.org #336933] RFC2047 header encoding bug

2007-07-17 Thread Egmont Koblinger
Follow-up Comment #11, bug #20252 (project mhonarc): Isn't it the same as bug #11187? Sounds similar at least. (That one was fixed in mhonarc 2.6.11 while gnu.org uses 2.6.10.) ___ Reply to this item at:

[bug #20252] [gnu.org #336933] RFC2047 header encoding bug

2007-06-28 Thread Robert Millan
Follow-up Comment #9, bug #20252 (project mhonarc): Tried that, and got the same result (with 0xe4). However, this is latin1, and can't possibly work. As Jeff said: Note the combination of Chinese, English, and umlauts; unicode is the only answer. The HTML generated at lists.gnu.org seems

[bug #20252] [gnu.org #336933] RFC2047 header encoding bug

2007-06-27 Thread Earl Hood
Follow-up Comment #8, bug #20252 (project mhonarc): Just download mhonarc from www.mhonarc.org, install, and run. Mhonarc is independent of any MTA. To convert a single message, you can do: mhonarc -single message.822 message.html I ran the above on the sample attached message, and the

Re: [bug #20252] [gnu.org #336933] RFC2047 header encoding bug

2007-06-26 Thread Jeff Breidenbach
[ -savannah because I am lazy ] Ok, well we do have proof that mhonarc is capable of doing the right thing on the exact same message. I use the TEXTENCODE resource to send everything to UTF-8, which is probably the recommended mhonarc way of doing things these days anyway.

[bug #20252] [gnu.org #336933] RFC2047 header encoding bug

2007-06-26 Thread Earl Hood
Follow-up Comment #6, bug #20252 (project mhonarc): For me to do an accurate analysis, I first need access to the original raw mail message. Then, it will help to know what resource settings are being used for the archive in question since some resources affect how mhonarc process character

[bug #20252] [gnu.org #336933] RFC2047 header encoding bug

2007-06-26 Thread Robert Millan
Follow-up Comment #7, bug #20252 (project mhonarc): I'm attaching a raw copy of the message that generated the bad html. I don't have a mhonarc install to test it. Is it possible to install and process a single message right-away without setting up MTA integration, etc? (file #13182)

Re: [bug #20252] [gnu.org #336933] RFC2047 header encoding bug

2007-06-26 Thread Jeff Breidenbach
I don't have a mhonarc install to test it. Is it possible to install and process a single message right-away without setting up MTA integration, etc? Yes. As a side note #1 I have the names of 564 gnu.org and nongnu.org mailing lists that have been hand checked and determined to be completely