You miss the point. Yes, those dictionary-ish things will tell you
what to look for, but they won't tell you
how to look. You can't just blindly search and replace, you need to parse the files. And to figure out what bits of code to change you need to understand the documentation - see for example
GD::Graph, where at most you would want to change some headings but you most definitely DON'T want to change the word colour (or color) anywhere else.
This CAN NOT be reliably automated. What might be worthwhile would be grepping over your CPAN mirror, finding all mentions of /colou?r/ and friends, manually checking that there really is a problem, and then notifying authors and perhaps submitting patches. And repeating this occasionally to catch any new modules, while being careful not to repetitively annoy authors who don't consider this to be important. Considering how much work is involved here, you might want to talk about it on the perl-qa list before doing anything.
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.