Vista - add-content -encoding unicode has strange outcome...

When I use add-content with -encoding unicode, I get question marks in the
file:

James Gentile@xxxxxx::C:\nobitbrains\Media\movielist$ add-content -encoding
unicode "list.txt" "test"
James Gentile@xxxxxx::C:\nobitbrains\Media\movielist$ type list.txt
test
James Gentile@xxxxxx::C:\nobitbrains\Media\movielist$ add-content -encoding
unicode "list.txt" "test"
James Gentile@xxxxxx::C:\nobitbrains\Media\movielist$ type list.txt
test
?test

I need to use unicode because I am logging filenames and sometimes these
filenames have foreign characters. Notepad doesn't display the question
marks, however. Is it just the way the 'type' command is constructed then?

James R. Gentile wrote:Plenty of programs don't display unicode characters correctly. The Windows
console subsystem is one of them.

--
$signature = "Hal Rottenberg, MVP - Admin Frameworks"
$projects = @{ title = "Blog Author"; url = "http://halr9000.com" },
@{ title = "Co-host"; url = "http://powerscripting.net" },
@{ title = "Community Director"; url = "http://PowerShellCommunity.org" },
@{ title = "Psi Webmaster"; url = "http://psi-im.org" }