I have some source files that contain a lot of smart/curly quotes; where it’s presentational text where it’s weird to use the foot/inch marks commonly used as quotes in ASCII.
It is impossible to work with those files in Cursor and Sonnet 3.5. It seems that Sonnet 3.5 can understand that there are smart quotes in the text but it does not seem able to output smart quotes so any Composer edit to a file results in all of the smart quotes becoming inch/foot marks. This often makes a file syntactically invalid as it will change a line such as const text = 'We can’t do this' into const text = 'We can't do this'.
I’ve tried this directly on claude.ai and it makes the same mistake as in chat (see images below). I also tried chatting with OpenAI models which didn’t seem to exhibit the same issue.
I sense that this is really a bug at Anthropic’s end, although I do wonder if this could be patched at the Cursor end somehow, at least for lines that are not really being modified other than the quotes changing.
Either way it makes it pretty much impossible to use Cursor to work with large chunks of our codebases with the Sonnet model that seems otherwise to have the best results.
Hey, can you try adding a .cursorrules file, and specify the quote you want in there? This might be enough to get the AI to start outputting the quote mark you want!
Sometimes, when I’m making a completely unrelated change to the file, the composer goes through and edits all instances of curly (typographic) apostrophes within the file, even when the task composer is asked to complete something unrelated to this section of the file.
e.g. I ask it to update “section 2” of a HTML file (unrelated to apostrophes), and it will go through and update all of my typographic apostrophes in “section 1” of the file as well as making my requested edits to “section 2”.
I haven’t been able to overcome this completely, but I have minimised the issue by adding the following to my Rules for AI:
ALL user-facing text MUST use the typographic apostrophe ’ instead of ’ (e.g., it’s instead of it’s, we’ll instead of we’ll).
If a typographic apostrophe exists within a word, it MUST be retained.
I can’t get it to do it when explicitly asked in a chat window, so don’t believe that a cursor rules file will fix this. I’ll give it a shot though with @jake’s suggestion.
The problem as I understand it is that the Sonnet 3.5 model is literally unable to output a smart quote - even when asked to do only that (see the last screenshot where it describes the two different types of quote and puts the straight quotes as example characters for both cases).
It can “see” them, but it literally can’t “say” them. Perhaps the clue is in the phrase “typographic” apostrophes.
I think you might be right that it’s literally incapable of doing it. And that actually makes a lot of sense.
Although my testing in .cursorrules has resulted in improvements, these improvements are from Claude not editing parts of the file that it’s not supposed to, i.e. no longer swapping existing straight apostrophes to typographic apostrophes in other parts of the file that are outside what I’m trying to edit.
But when the edit does involve part of the code with a typographic apostrophe - for example, getting it to say “we’ll be back soon” on the front end - I haven’t had any luck.
(knowing this is actually consoling, as I was beginning to doubt my prompt engineering skills).
Oddly enough, I’m getting different results from using the LLM UIs directly vs Cursor.
With Claude, it returns straight quotes via the UI or via Cursor. But with OpenAI, it returns curly quotes via the ChatGPT UI (and in it’s response in the composer window), but then can’t apply those changes.
