{"version":"2.1.267","anchor":"file-encoding-problem-reporting-for-reads-utf-16leutf-8-de","canonical_anchor":"file-encoding-problem-reporting-for-reads-utf-16leutf-8-de","heading":"File-encoding problem reporting for reads (UTF-16LE\/UTF-8 detection + replacement-char and undecodable diagnostics)","tier":"notice","area":"File Reading","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/file-encoding-problem-reporting-for-reads-utf-16leutf-8-de","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### File-encoding problem reporting for reads (UTF-16LE\/UTF-8 detection + replacement-char and undecodable diagnostics)\n\nFile reads now detect encoding problems and report exactly where a broken or undecodable character occurs\n\n**What**\n\nWhen Claude Code reads a file, new internal logic detects the file's text encoding (distinguishing UTF-16LE from UTF-8 by checking for a byte-order mark), then scans for the first replacement character (the symbol that appears when a byte sequence can't be properly decoded as text) or the first byte that can't be decoded at all. If either is found, the read now returns a structured result identifying the problem kind, the encoding, and the exact line and column where it occurs, instead of just returning garbled text.\n\n**Why**\n\nThis gives clearer diagnostics when a file has encoding issues, pinpointing exactly where the problem is rather than leaving Claude (or the user) to guess why a file's contents look corrupted.\n\n- Area: File Reading\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}