On Tuesday, April 9, 2002, at 02:04 , Anton Tagunov wrote:
Other items in my '[PATCH]s and questions [Encode] 1.30' mail were:
- a consmetic patch to Supported.pod
This one must be the most acceptable by pumpkins since it has no piece
of code :)
- a question whether
Encoder.pm
sub data{
- my ($self, $data) = shift;
+ my ($self, $data) = (shift, shift);
Encoder is undergoing a major overhaul. It was just a placeholder of an
idea but now you can use it practically. To show that, t/Encoder.t is
added.
- a couple of ideas on general design (maybe not for 5.8):
($name = lc $name) =~ tr/- //d;
in find_encoding or getEncoding?
I'll think about it but the priority is low.
- jisx0208-raw vs jis0208-raw?
Welllll, We don't have to be *that* pedantic, methinks. Besides I
don't want to screw the MANIFEST file at this stage.
Promised changes in 1.31 is right after my sig.
Dan
! lib/Encode/Encoder.pm
+ t/Encoder.t
Encode::Encoder, once just a placeholder of an idea, is now much more
practical. See t/Encode.t to find how practical it can be.
+ lib/Encode/Config.pm
! Encode.pm
my false laziness at Encode.pm is fixed. Now %ExtModules are set
in Encode::Config and they are all literally, not programatically
set. My false laziness was resulting many encodings missing from
%ExtModules.
! lib/Encode/Unicode.pm
! t/Unicode.t
BOM for 32LE was bogus as noted by Anton. t/Unicode.t is fixed
so that it does not rely Encode::Unicode for BOM values
Message-Id: <FFEC33E9-4AFB-11D6-B415-00039301D480(_at_)dan(_dot_)co(_dot_)jp>