in reply to Unicode::UTF8 and perl Unicode compatibility

1. Start, if possible, by upgrading to a currently supported version of Perl (5.18 is current; ActiveState lags with 5.16; most others known to me are at 5.18).

2. Try it with cases you anticipate. See if the output -- to file and to console (since the rendering in those two cases may not match) -- satisfies your needs.

3. Now get all wild and crazy. Use Perl to walk Unicode::UTF8 thru the character sets with which you need to deal. Do it again and again for major versions (but note that you could go insane trying to test every build of every Perl distro, especially those built by individuals from source with variant options enabled).

4. When complete -- and it should not take long, unless you have an insanely wide selection of needed sets -- you'll know the answer to your question, rather than having to rely on second hand info of whose validity you will likely have no way (other than the above) to evaluate.

5. Then, share your newfound knowledge with your own reply to this thread.


If you didn't program your executable by toggling in binary, it wasn't really programming!

  • Comment on Re: Unicode::UTF8 and perl Unicode compatibility

Replies are listed 'Best First'.
Re^2: Unicode::UTF8 and perl Unicode compatibility
by vsespb (Chaplain) on Aug 31, 2013 at 12:00 UTC
    Use Perl to walk Unicode::UTF8 thru the character sets with which you need to deal
    I am not sure how to walk. What can fail? Regexps? Character classes? String comparsion? Collations? Folder case? Normalization? I am not sure what new Unicode 6 introduced.

      "...how to walk.":   loops and arrays.

      "What can fail?....":   Answering that is with domain of the research plan outlined above... or, stated more simply, 'TITS, try it to see.'

      If I've misconstrued your question or the logic needed to answer it, I offer my apologies to all those electrons which were inconvenienced by the creation of this post.
        You are talking about testing something without knowing internals and without knowing what can fail.

        If that possible, one can test whole Perl source code without understanding it's internals, without reading documentation and without doing actual work. And will find all existing perl bugs in the end.
          A reply falls below the community's threshold of quality. You may see it by logging in.