Yes, the data really has to be passed on the command line - this is a several year old and established script that I can't change the semantics of. ikegami's reply populated @ARGV inside the script rather than passing the text on the command line, which should avoid any issues there.
print()ing the string before passing it to decode_utf8 gives "l'été sera chaud". Decoding it gives "l'�t� sera chaud".
I've found a solution that seems to fix the problem, although it is rather hacky. Appending n spaces to the string before write()ing it, where n is the number of non-ASCII characters inside the string, seems to fix the issue without polluting the eventual output.
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.