[BUG] Chat rendering in VS Code does not distinguish no-break spaces (U+00A0, U+202F) from regular spaces
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
When I request Claude to generate text with Unicode no-break spaces (either the normal no-break space (U+00A0) or the narrow no-break space (U+202F, used in French typography before ; : ? ! » «)), the chat UI renders them with a regular space (U+0020), both visually and through a copy-paste.
This makes rendering of French text pretty bad, as lines will break before these double-punctuation marks, e.g. :
- in Claude Code app, version 1.52386.6 (612f3f) 2026-09-13T00:45:40.000Z
<img width="363" height="150" alt="Image" src="https://github.com/user-attachments/assets/c57a3517-e2b6-463d-953a-a252370f0b34" />
- in VS Code extension, version 2.1.272 :
<img width="426" height="78" alt="Image" src="https://github.com/user-attachments/assets/b52e5398-feed-479c-b510-127646a97228" />
Said otherwise, no-break spaces render identically to a plain space, with the rendering breaking line just before the punctuation mark, which is harder to read (and a bit ugly).
What Should Happen?
The no-break space should prevent line-wrapping between the word and the following punctuation.
Error Messages/Logs
n/aSteps to Reproduce
- Ask Claude to output a sentence using French typography rules, e.g.:
Le module a été mis à jour ; vérifier si cela répond à votre besoin : sinon, précisez ce qui manque !
with narrow no-break spaces (U+202F) before ; and !, and a normal no-break space (U+00A0) before :.
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
1.52386.6
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
WSL (Windows Subsystem for Linux)
Additional Information
I do not use Claude in the terminal, only through Chat interfaces; so not sure how the Terminal/Shell question is relevant.