Cursor returns UTF-8 code despite Windows-1252 configuration

Thanks for the info.
About unlocking old versions, that’s not my call, but I’ll pass the request to the team. I get the logic. If the current version breaks things and downgrade isn’t possible, it leaves users stuck.

Bug status: The team is aware. A few threads about this are active right now. Windows-1252, EUC-KR, and other encodings. The bug affects multiple languages and projects.

What you can try right now (if you haven’t already):

  • Use CTRL+K (inline edit) instead of Agent. For some users it works better with non-standard encodings.

If those options don’t work either, let me know.

Related threads (if helpful): Issue with Agent Corrupting Korean Characters (EUC-KR Encoding) during Auto-Edits, Encoding changing when editing EUC-KR files