Guys, let me be frank with you:
My team and I use Cursor in the evolution of legacy Java projects, and due to the initial configurations of these projects, based on Eclipse, ever since we started using Cursor as a Coding Agent, we’ve had issues with the encoding being Cp1252 for “.java” files and ISO-8859-1 for web files (html, jsp, xml, css, js).
We are forced to use Eclipse and Cursor in parallel in our development, due to the deficiencies of VS Code/Cursor tools compared to Eclipse, but this isn’t the biggest problem.
When the agent is editing the components, even if the workspace has the settings pointing to the correct encoding, the file is completely overwritten, disregarding the original encoding and breaking the project’s localized strings. The rework is infuriating, because the tool should be an accelerator, not a cause of problems.
I’ve already tried to work around the problem in several ways: creating rules in the project with the EditorConfig plugin, avoiding the use of multi-root workspaces (which is counterproductive to our needs), reinforcing the prompt, ensuring better workspace or project configurations; however, none of this matters, as the prompt doesn’t consider any of it.
I’ve been evaluating the possibility of requesting the prompt to create code that implements my requirements, instead of it doing it itself, but that’s a waste of tokens/money.
All I ask of you is that you dedicate more attention to this. It doesn’t seem to me that this fix is so big and impactful that it will hinder the delivery of your product, but I guarantee that not doing it tarnishes the product’s image, demonstrating how much you ignore the needs of your customers.
- Agent Write/StrReplace tools encode non-ASCII content as GBK on disk despite files.encoding=utf8
- It’s about the Chinese garbled text issue in the source code generated by the Cursor editor, can you take a look and fix it?
The links above only appear in a simple internet search, but I’m sure that if we delve deeper, we’ll find complaints in many other places. And of course, many people have already stopped using your tool because of the neglect in resolving something that has been clear for a long time. Is it really that difficult to focus efforts on fixing such an obvious issue?