Subject: Re: PC-PINE 4.60 charset bug.

From: Mark Crispin <[email-masked]>
Date: Tue, 1 Jun 2004 13:45:08 -0700 (Pacific Daylight Time)

Thank you for reporting this problem.

This problem has already been called to our attention, and will be fixed 
in Pine 4.61.  Since you use PC-Pine, regrettably there is no patch for 
the problem in 4.60.  I could give you a patch for UNIX Pine 4.60 if you 
like.

On Sun, 30 May 2004, Alexander V Alekseev wrote:

> 		Hello!
>
> 	I've installed 4.60 in addition to 4.58.
> Nothing in configuration changed. My character set is
>
> character-set=WINDOWS-1251
>
> 	Pine 4.58 automatically recoded other russian charsets
> (as koi8-r) to windows-1251. But 4.60 only displays
> charset warning and nothing changes. 4.58 still work OK.
>
> 	Any ideas?
>
> 		Bye. Alex.
> -- 
> -----------------------------------------------------------------
> For information about this mailing list, and its archives, see: 
> http://www.washington.edu/pine/pine-info/
> -----------------------------------------------------------------
>

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.

---

From: Alexander V Alekseev <[email-masked]>
Date: Wed, 2 Jun 2004 11:12:17 +0400 (MSD)

Hello!

> the problem in 4.60.  I could give you a patch for UNIX Pine 4.60 if you 
	Under Linux I use iconv patch, which works much better.

		Bye. Alex.

--

---

From: Mark Crispin <[email-masked]>
Date: Wed, 2 Jun 2004 02:27:16 -0700 (PDT)

> 	Under Linux I use iconv patch, which works much better.

The iconv() patch does not work in many cases in which the code in 4.60 
does.  Nor is iconv() available on the other ports of UNIX where Pine 
runs.

-- Mark --

---

From: Alexander V Alekseev <[email-masked]>
Date: Wed, 2 Jun 2004 14:04:04 +0400 (MSD)

Hello!

> does.  Nor is iconv() available on the other ports of UNIX where Pine 
	I don't know as for non-cyrillic charsets, but for Russian
mail native pine code doesn't work well. Half a year ago it didn't
decode mime Subject, From and other headers. I couldn't read UTF-8.
	I had to use DISPLAY-FILTERS, but postponed-mail was filtered
twice. So I started to look for other mail client, or some way to
use pine.

	So, if want to support iconv()-uncapable systems, why no to
emulate iconv for them with your own code with current capabilities?
You cannot make charset translation better than iconv(). Its developers
already did it for you. Why not to use it?

		Bye. Alex.

--

---

From: Mark Crispin <[email-masked]>
Date: Wed, 2 Jun 2004 09:52:04 -0700 (PDT)

> decode mime Subject, From and other headers. I couldn't read UTF-8.

Pine 4.58 should convert between 8-bit (e.g. Russian) character sets 
without problem, and Pine 4.60 should read UTF-8 email.

Unfortunately, conversion between 8-bit character sets was broken in Pine 
4.60, and none of our beta testers reported this problem until after Pine 
4.60 was released.  The bug was simple -- one line that needs to be 
deleted -- and will be fixed in 4.61.

> emulate iconv for them with your own code with current capabilities?

I started writing Pine's internal code long before iconv() existed.  That 
internal code has been used for searching for years.

> already did it for you. Why not to use it?

Pine's internal character set code does more than iconv().  Among other 
things, the iconv() patch deletes support for character sets that I use!

-- Mark --

---

From: Bob Rasmussen <[email-masked]>
Date: Wed, 2 Jun 2004 10:11:14 -0700 (PDT)

> things, the iconv() patch deletes support for character sets that I use!

Which ones?

And are you referring to Kaindl's iconv() patch?

Regards,
....Bob Rasmussen,   President,   Rasmussen Software, Inc.

personal e-mail: [email-masked]
 company e-mail: [email-masked]
          voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
            fax: (US) 503-624-0760
            web: http://www.anzio.com

---

From: Kenneth Crudup <[email-masked]>
Date: Wed, 2 Jun 2004 13:38:40 -0700 (PDT)

On Wed, 2 Jun 2004, Mark Crispin wrote:

> 4.60, and none of our beta testers reported this problem until after Pine 4.60
> was released.  The bug was simple -- one line that needs to be deleted

<ahem>

Some of us always build Pine from source, ya know.

	-Kenny

-- 
Kenneth R. Crudup  Sr. SW Engineer, Scott County Consulting, Los Angeles
H: 3630 S. Sepulveda Blvd. #138, L.A., CA 90034-6809      (888) 454-8181
W: 26601 Agoura Road, Calabasas, CA 91302-1959            (818) 444-3685

---

From: Steve Hubert <[email-masked]>
Date: Thu, 3 Jun 2004 11:28:43 -0700 (PDT)

> Some of us always build Pine from source, ya know.

Here ya go. Patch for conversion bug is attached.

Steve