in reply to
(RFC) PostScript::Glyph::MapToUnicode - my first (intended-to-be) CPAN module
You got typo (head1 ne =head1).
Also, I prefer =head(2|3|4) instead of =item for function listings ;)
You're missing a $VERSION variable (but I assume you're gonna add this as soon as you create a distribution -- when you do, it'd be a good idea to include a LICENSE file containing the licenses -- ExtUtils::ModuleMaker ).
I'd like to point out to you PostScript::ISOLatin9Encoding
which are similar to your module (PostScript::UnicodeEncoding?).
However you decide to deal with the actual glyph file,
it might be a good idea to attempt to download it during make time, and append it to your module.
If you choose to prompt the user, but sure to use ExtUtil::MakeMaker's prompt
and not roll your own (cause it detects if Makefile.PL is being run interactively or not -- very important).
And on a final note, I'd like to suggest that you remove your email and make a note of http://rt.cpan.org like so.
|MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"|
|I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).|
|** The third rule of perl club is a statement of fact: pod is sexy.|