comment on

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 by Aristotle
in thread (RFC) PostScript::Glyph::MapToUnicode - my first (intended-to-be) CPAN module by Aristotle

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


more useful options
	PerlMonks