{"version":"2.1.290","anchor":"path-validator-rejects-ufffd-replacement-characters","canonical_anchor":"path-validator-rejects-ufffd-replacement-characters","heading":"Paths containing the Unicode replacement character are rejected","tier":"notice","area":"File Paths","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/path-validator-rejects-ufffd-replacement-characters","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Paths containing the Unicode replacement character are rejected\n\nA path check now rejects entries containing the Unicode replacement character, the \ufffd that marks garbled text\n\n**Unclear.** Which feature uses this path check is not known.\n\n**What**\n\nA check on path entries already rejected control characters. It now also rejects the Unicode replacement character (U+FFFD, usually shown as \ufffd), which appears when text was decoded with the wrong encoding.\n\n**Why**\n\nPath names garbled by a wrong encoding are now refused instead of being accepted.\n\n- Area: File Paths\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}