$OutputEncoding to the rescue

re: $OutputEncoding to the rescue

soregasi — Tue, 12 Dec 2006 06:23:11 GMT

In this day and age, why would you default to ASCII? I can understand the history of CMD and the difficult in changing it now, but PowerShell is a clean break. It would have been an excellent opportunity to fully enable Unicode (by default).

re: $OutputEncoding to the rescue

Jeffrey L. Whitledge — Tue, 12 Dec 2006 07:07:25 GMT

Why are we still mucking about with codepages in 2006? Why can’t we just use Unicode in Powershell/CMD?

re: $OutputEncoding to the rescue

hayate — Tue, 12 Dec 2006 07:20:28 GMT

Hah!

It seems that Wei Wu U are Chinese.

So am I.

re: $OutputEncoding to the rescue

Rei Miyasaka — Tue, 12 Dec 2006 08:24:15 GMT

Why isn't it UTF8 or the current codepage by default?

If there's a reason for it to be ASCII, I presume there must be a problem with other encodings.

What are those problems?

re: $OutputEncoding to the rescue

oidon — Mon, 25 Dec 2006 03:19:31 GMT

I'd really like to hear a response to these questions. The biggest flaw in CMD is its dependency on legacy encodings, and that heritage seems to still be alive in PowerShell. Unless there is rational reason, this seems like a major flaw.

re: $OutputEncoding to the rescue

Remi — Thu, 28 Dec 2006 21:32:34 GMT

There also seems to be a Codepage issue when using edit.exe from powershell.

all keys are remapped to what seems like a random section of a keymap (possibly greek, i thought i saw a capital phi in there)

How would you go about changing the codepage before you start edit.exe?

re: $OutputEncoding to the rescue

Rick — Wed, 23 May 2007 01:18:58 GMT

I have a set of multi-language websites to dynamically generate off a common MS Access database.

Access can handle unicode text and I have fields of English and Korean, Japanese, Chinese equivalents for things.

My OS (dual booted XP PRo and Vista home prem) have the languages setup via language bar - primary is English (United States)

I can't get Powershell to use the unicode encoding.

e.g. (サウスホキアンガ) looks like this (????????

PsSH > [Console]::OutputEncoding

IsSingleByte : True

BodyName : IBM437

EncodingName : OEM United States

HeaderName : IBM437

WebName : IBM437

WindowsCodePage : 1252

IsBrowserDisplay : False

IsBrowserSave : False

IsMailNewsDisplay : False

IsMailNewsSave : False

EncoderFallback : System.Text.InternalEncoderBestFitFallback

DecoderFallback : System.Text.InternalDecoderBestFitFallback

IsReadOnly : True

CodePage : 437

Is there another source of object values other than [Console]::OutputEncoding ??

RickW

re: $OutputEncoding to the rescue

Jacques Beaurain — Fri, 25 May 2007 17:20:37 GMT

This just worked for me for getting UTF8 Unicode:

$OutputEncoding = New-Object -typename System.Text.UTF8Encoding

re: $OutputEncoding to the rescue

King Kong — Fri, 05 Oct 2007 03:47:42 GMT

Hi, how do you get to display Chinese fonts, or for that matter any Unicode typefaces, in your shell?

Thanks.