When working with CSV files in PowerShell with special characters you might encounter an issue where special characters (e.g., em dashes —) are incorrectly represented as a question mark inside a diamond �. This common issue arises due to PowerShell’s default encoding not matching the encoding used in the CSV file. Problem Statement The root of this problem lies in the encoding mismatch. Encoding is a method of converting characters into a format that can be easily stored or transmitted.