> If anyone has any suggestions on how to handle a
> largish character mapping table [...]
For those who aren't familiar with the MARC 21 alternate character set
repertoires (specifically, the East Asian ideographs), by "largish", Ed
is talking on the order of a table containing upwards of 16,000
mappings.
> Perhaps at the very least I can include some
> information about DB_File difficulties prominently in the
> documentation in the new version.
That would definitely be helpful. It would also be helpful if error
messages that get kicked out during an automated install ("perl -MCPAN
-e 'install MARC::Charset'") due to missing DB_File prereq components
were more informative as to the problem. Below are the error messages
that users get now:
BEGIN failed--compilation aborted at lib/MARC/Charset.pm line
12.
Compilation failed in require at Makefile.PL line 7.
BEGIN failed--compilation aborted at Makefile.PL line 7.
Running make test
Make had some problems, maybe interrupted? Won't test
Running make install
Make had some problems, maybe interrupted? Won't install
I'm probably starting to sound nit-picky, but please understand that
it's only because I think MARC::Charset is a great module and I'd like
for more people to be using it. :-)
-- Michael
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Ed Summers
> Sent: Monday, December 05, 2005 12:14 PM
> To: perl4lib@perl.org
> Subject: Re: MARC-8 to UTF-8 conversion
>
> On 12/5/05, Doran, Michael D <[EMAIL PROTECTED]> wrote:
> > Sooooo... this is all very interesting (and I've definitely learned
> > something here), but like I suggested previously, this level of
digging
> > may be a bit beyond the "casual" Perl user. ;-)
>
> Yep, point taken. I'm guessing you are right: when you built perl from
> source it couldnt't find BerkeleyDB so didn't install DB_File. Good to
> know for the future. If anyone has any suggestions on how to handle a
> largish character mapping table when someone does a:
>
> use MARC::Charset;
>
> I'm open to suggestions. Perhaps at the very least I can include some
> information about DB_File difficulties prominently in the
> documentation in the new version.
>
> Thanks!
> //Ed
>
