If the issue is on Cursor’s side, it might be addressed in a future update, I hope.
If the problem originates from the LLM model, I think there are two things you may try for now:
- Specify UTF-8 encoding in your files (HTML or JavaScript I guess) by adding the
charsetattribute, and ensure the files are saved with UTF-8 encoding. - In Cursor Settings, add a prompt to the ‘Rule for AI’ section, such as: “Retain all Korean comments in their original form.” This will encourage the model to preserve Korean comments during code generation.