Minimal view in Write-progress should not depend on code page settings

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

When trying to output unicode characters with Write-Progress, they all show up as ?-marks. Using the same text/variable with Write-Host works fine.

Expected behavior

$str = '🦄❤️🌈阳山伟伟'
$count = 1
While ($count -lt 100) {
	Write-Progress -Status $str -PercentComplete $count -Activity "`u{1F4A9}"
	$count++
	Start-Sleep -Milliseconds 10
}

Actual behavior

Both -Status and -Activity texts output `?` instead of the actual characters.

Error details

No response

Environment data

Name                           Value
----                           -----
PSVersion                      7.2.7
PSEdition                      Core
GitCommitId                    7.2.7
OS                             Microsoft Windows 10.0.22623
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visuals

[jhoneill]

Yes that is going be part of the same problem.
Internally .NET strings are UTF16 Something like 💃 which is 0x01f483 can’t be represented as a 16 bit number so it becomes two 16 bit ones. 0xd83d and 0xdc83 - this range identifies numbers which need to be combined - the we subtract d800 from one and dc00 from the other and the output is 0x10000 + 0x400 * 3d + 83

When the string with [0xd83d] [0xdc83] is output it’s merged back to [0x01f483] and 💃 is printed. However if something says “I need to insert an ANSI escape Sequence after the first character” then we get
`e[7m [0xd83d] `e[0m [0xdc83] For reverse, first char, reset, second char. Which gives nonsense output. This doesn’t impact most unicode because most of the characters are 16 bit values, but it will hit unicode emojis

[jhoneill]

@kimipsen Actually that does indicate a problem. Can you please edit the title (see below) And thanks for doing the extra step to find the cause.

This should not depend on the codepage selected. On one computer I have that setting and can’t repro the issue. On the computer I am using now (provide by the client I’m working for and set up by their IT people without giving me admin rights) the issue DOES repro and chcp says I’m using code page 437 - just like I used on DOS 3.1 in the 1980s 😃

There if I select classic view for progress

all good. The terminal , powershell, and Write-Progress can all display UTF 16 strings correctly. If I switch to minimal view something like the € sign which is not in code page 437 or the ellipsis (…) which is a two-byte unicode character both cause failures with the minimal view

This issue should be have title like Minimal view in Write-progress should not depend on code page settings . It can’t output characters which classic view CAN output I would say that is a bug.