Well, that bit in the pod about matching GB characters was based on personal experience. Access to Perl 5.8's character-set transliteration and unicode-based character semantics for matches (not to mention the very handy "\p" unicode-based character classes) was the main reason I had to write this tool in the first place. The other bells and whistles (handling compressed data, controlling the input record separator) were after-thoughts -- once I started using this thing on real (multi-language, multi-coded) text data, those other things were just handy and easy to add. But the Encode module was crucial.
Maybe some people have tricks to search for a specific GB (or Big5, or Shif-JIS) character using plain-old "grep", but I couldn't figure a way to make it trustworhty for such things, and doing it with Perl just made sense.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.