Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

Re: (RFC) PostScript::Glyph::MapToUnicode - my first (intended-to-be) CPAN module

by PodMaster (Abbot)
on Aug 19, 2003 at 09:24 UTC ( #284829=note: print w/replies, xml ) Need Help??

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 and PostScript::ISOLatin1Encoding, 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 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.

  • Comment on Re: (RFC) PostScript::Glyph::MapToUnicode - my first (intended-to-be) CPAN module

Replies are listed 'Best First'.
Re^2: (RFC) PostScript::Glyph::MapToUnicode - my first (intended-to-be) CPAN module
by Aristotle (Chancellor) on Aug 19, 2003 at 15:42 UTC

    Thanks for the pointers.

    =head2 would be better appropriate than =item indeed. I don't know why that didn't occur to me.

    I know the PostScript encoding modules, but they don't do the same. They offer the reverse mapping only, and only as a static table. Due to the sheer mass of glyph names possible with the uni- and u-notation it is infeasible to do it that way for this module. Besides, I need the opposite mapping direction from what they do.

    I'll have to think some more about the glyph list. I'll probably put that off for the first revision of the module.

    Good point about CPAN's RT.

    Makeshifts last the longest.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://284829]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (4)
As of 2017-11-25 12:33 GMT
Find Nodes?
    Voting Booth?
    In order to be able to say "I know Perl", you must have:

    Results (355 votes). Check out past polls.