Hello @Highboy
Thanks for your response.
My original goal was to have a Base64 encoded string to be decoded using a PowerShell script.
The Emojis are contained in a user-created file, and I need to restore the file to its exact original state (binary match required).
Since PAD itself does not provide any action to encode / decode Base64, we have to use an external script written in PowerShell / Python / JavaScript / VBScript.
Since Emojis are just UTF-8 characters, they should be able to be displayed via the standard output of the console if handled properly.
When I experimented, I noticed that the results were different depending on the terminal software used, even if it was the same version of PowerShell.
[Windows PowerShell v5.1]

INPUT: Mojibake
OUTPUT: 4 bytes chars are mojibake, but can display 3 bytes char properly.
[Windows Terminal + Windows PowerShell v5.1]

INPUT: Mojibake
OUTPUT: Can display both 4 bytes chars and 3 bytes char. Looks fine.
[Windows Terminal + PowerShell v7.1.5]

INPUT: Perfect
OUTPUT: Perfect
[PowerShell code]
$food = "🍣 U+1F363"
$drink = "🍺 U+1F37A"
$multi = "✖ U+2716"
$dinner = "I would like to have $food $multi $drink."
Write-Output $dinner
As a workaround for the time being, I have confirmed that no garbled characters are generated in the output string by using VBScript to process Base64 decoding, but I would like to know how I can get the same result in PowerShell.