Porters,
I am releasing Encode 1.77 to accommodate the up-and-coming changes
to bleedperl that makes tr/// free of eval qq{} under "use encoding"
pragma. This problem was addressed by me as;
> From: Dan Kogai <[EMAIL PROTECTED]>
> Date: Thu Oct 3, 2002 20:31:13 Asia/Tokyo
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: tr/// and use encoding
> Message-Id: <[EMAIL PROTECTED]>
Whole Package -- to be uploaded to CPAN soon:
http://www.dan.co.jp/~dankogai/Encode-1.77.tar.gz
Patch against bleedperl (242 lines) for Hugo:
http://www.dan.co.jp/~dankogai/current-1.77.diff.gz
And here is the Changes. This one also includes minor alias fix by
Autrijus.
$Revision: 1.77 $ $Date: 2002/10/06 03:27:02 $
! t/jperl.t
* Modified to accomodate up and comming patch by Inaba-san that
will fix tr/// needing eval qq{}
Message-Id: <[EMAIL PROTECTED]>
! encoding.pm
* pod fixes/enhancements to reflect the changes above
! lib/Encode/Alias.pm
"Encode::TW is correct, Encode::Alias not." - /Autrijus/
Message-Id: <[EMAIL PROTECTED]>
Note this update alone will NOT fix the tr/// vs. use encoding problem
noted above, the real fix needs to be applied to bleedperl (regcomp.c
and such). The patch was already made available by Inaba Hiroto
<[EMAIL PROTECTED]> (IsP for short)and my preliminary tests already
show that it works with a minor fix to ext/Encode/t/jperl.t. Hence the
update to Encode prior to bleedperl patch.
Here is the proposed schedule before IsP goes into bleedperl;
On Sunday, Oct 6, 2002, at 12:10 Asia/Tokyo, Jarkko Hietaniemi wrote:
>> Okay, how about the schedule below?
>>
>> 0) I release IsP-safe Encode 1.77 to CPAN. All I have to do is to
>> comment out the local(${^ENCODE}) black magic so it is still test-safe
>> under perl 5.8.0
>>
>> 1) Hugo to sync bleedperl w/ Encode 1.77
>>
>> 2) New *.t for IsP under somewhere OTHER THAN ext/Encode/t.
>> lib/nihongo.t, maybe? that is to test thoroughly what IsP brings.
>> That test suite does not have to run on stock perl 5.8.0
>>
>> 3) With enough assurance w/ the test suite above, IsP goes into
>> bleedperl.
>
> Sounds good to me.
The Encode update complies step 0. Though this update is primarily for
bleedperl, it is perl 5.8.0-safe.
Please allow some time before step 2-3. I would like Inaba-san's help
on 2 and I am rather busy recently....
Dan the Encode Maintainer
