|Think about Loose Coupling|
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.
In reply to Re^2: (RFC) PostScript::Glyph::MapToUnicode - my first (intended-to-be) CPAN module