Re: interaction between tr and s (was Re: tr question -- probably wrong list to ask, but ...)

At 17:03 +0900 12/1/07, Joel Rees wrote:
>Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>Message-Id: <[email protected]>
>Content-Transfer-Encoding: 7bit
>From: Joel Rees <[email protected]>

At 11:43 +0900 12/1/07, Joel Rees wrote:
>Content-Type: text/plain; charset=ISO-2022-JP; delsp=yes; format=flowed
>Message-Id: <[email protected]>
>Content-Transfer-Encoding: 7bit
>From: Joel Rees <[email protected]>

I had some intermittent problems reading your postings using Eudora-5 on this Mac 8500 running OS9.1 which I prefer for email.

The $line =~ tr/+/ /; showed up as $line =? tr/+/ /;  and I got a couple of yen marks.  I blamed it on lack of unicode support. Looking back I see a couple of Content headers in your email that bother me They both say simple 7 bit ASCII but then they also have divers encodings stated which really are about how to use the eighth bit.

There is also the big-endian / little-endian consideration which has reared its ugly head with the introduction of Intel machines running Mac OS.

Is it possible that some of the failure to decode %xx encoded stuff is associated with development on one machine followed by execution on another? Is UTF-8 input coming from the likes of Apache a possible source of failure? Pack may need to allow for endian-ness of a specific machine.

-- 

--> From the U S of A, the only socialist country that refuses to admit it. <--