Geez. You are using "Terminal.app", right? What font are you using? I use Monaco, and I see the £ symbol just fine. In case it helps, here are what I guess would be the relevant shell environment variables -- if you type "env" as a command, you should see similar things (I don't actually know what TERM_PROGRAM_VERSION and __CF_USER_TEXT_ENCODING are about): 
$ env
TERM_PROGRAM=Apple_Terminal
TERM=xterm-color
SHELL=/bin/bash
TERM_PROGRAM_VERSION=133
__CF_USER_TEXT_ENCODING=0x3B28:0:0
...

$ perl -v

This is perl, v5.8.6 built for darwin-thread-multi-2level
(with 3 registered patches, see perl -V for more detail)
...

$ perl -e 'binmode STDOUT,":utf8"; print "sign: \xa3\n"'              
sign: £

[download]
The fact that you're seeing just the escaped-octal-digit rendition of the byte values suggests that it's not strictly a perl problem.

In reply to Re^3: £ symbols by graff
in thread £ symbols by Yoda_Oz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.