René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"TextDecoder incorrectly decodes 0x92 and several other characters for Windows-1252","articleBody":"### Version\n\nv23.6.0, v22.13.0\n\n### Platform\n\n```text\nDarwin xxx 24.1.0 Darwin Kernel Version 24.1.0: Thu Oct 10 21:00:32 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6030 arm64\n\n(but no problems reproducing it on Linux amd64 or arm64/)\n```\n\n### Subsystem\n\n_No response_\n\n### What steps will reproduce the bug?\n\n```\nconst decoded = new TextDecoder(\"Windows-1252\").decode(new Uint8Array([146])).charCodeAt(0);;\nconsole[decoded === 8217 ? 'error' : 'log'](`Expected 8217 got ${decoded}`);\n```\n\n146 is now decoded as 146, not 8217. This still worked in v23.3.0 and v22.12.0 - might be related to the fix for https://github.com/nodejs/node/issues/56219 ?\n\n\n\n### How often does it reproduce? Is there a required condition?\n\nIt always fails\n\n### What is the expected behavior? Why is that the expected behavior?\n\nhttps://web.archive.org/web/20151027124421/https://msdn.microsoft.com/en-us/library/cc195054.aspx shows 0x92 should indeed be 0x2019\n\n\n### What do you see instead?\n\nsomething else\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/unilynx","@type":"Person","name":"unilynx"},"datePublished":"2025-01-10T09:23:56.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":15},"url":"https://github.com/56542/node/issues/56542"}