{"version":"2.1.290","anchor":"unicode-and-filename-hardening","canonical_anchor":"unicode-and-filename-hardening","heading":"Better handling of non-English characters in file names and displayed text","tier":"notice","area":"Terminal UI","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/unicode-and-filename-hardening","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Better handling of non-English characters in file names and displayed text\n\nClaude Code now strips broken characters from displayed text and normalises file names before suggesting similar ones\n\n**Unclear.** How noticeable these fixes are in everyday use is not clear.\n\n**What**\n\n- Cleaned-up text: when Claude Code removes invisible control characters from text it shows, it now also removes \"lone surrogates\", broken halves of characters that need two parts to display.\n\n- Similar file suggestions: when a file is not found and Claude Code looks for one with a similar name, it now puts names into a single standard Unicode form first, so the same name typed with different character encodings matches.\n\n- Uppercasing: a helper now uppercases a non-English letter only when the result is still a single character.\n\n**Why**\n\nThese are small fixes for file names that use non-English characters and for text Claude Code cleans before showing it.\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}