Hi bOB,
Please check my comments below
On Sun, Dec 2, 2012 at 4:29 AM, boB Stepp <robertvst...@gmail.com> wrote:
> On Thu, Nov 29, 2012 at 8:08 AM, Charles DeRykus <dery...@gmail.com>
> wrote:
>
> >
> >> even when warnings is turned OFF, you will get the unwanted warning
> >>
> >
> > Just a guess because I don't know what chcp is all about...
> > but it might be informational rather than an actual warning.
> >
>
> I think that you are correct about this. The Windows command console
> apparently does not default to supporting Unicode, but instead to
> ASCII. Googling, I was not able to change this default behavior.
> However, chcp 65001 (change code point) apparently can be used to
> enable the command console to display UTF-8. The active code page
> comment seems to be system generated for informational purposes as far
> as I can tell. I was hoping someone could tell me how to change the
> default display mode of the Windows command console, but perhaps that
> is impossible to do.
>
It is very possible, just in 3 steps.
Here is what you had always wanted to do:
1. Open up your command Prompt, then
2. You will need to change your cmd font to "Lucida Console", because
other fonts don't contain all the codepoints.
So, to do this, Right-click on the bar of the cmd Prompt, click on
Properties, then on Fonts tab, select "Lucida Console",
3. Ordinarily, if you type "chcp" on the cmd Prompt, you will get this
: *Active
code page: 850*
The current Active code. To display Unicode however, you will need to
change that to *65001*.
So, you might change it by typing "chcp 65001" on your cmd Prompt or do it
in your Perl script, using a backtick.
Here is how your script now looks:
use warnings;
use strict;
use utf8;
`chcp 65001`;
binmode STDOUT, ":encoding(UTF-8)";
print "\x{03B1}\x{03C9}\n";
--
Tim
