Regression in Unicode handling in Xcode 27 text editor

Thank you for this bug. The screenshot was not attached to the FB number. Is that the screenshot you posted here is the one you wanted to post on the bug? Any chance you can upload to the FB the screenshots in Xcode 26 vs Xcode 27 so is clear the issue?

You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label "Resolution." We're unable to share any updates on specific reports on the forums.

For more details on when you'll see updates to your report, please see What to expect after submission.

Albert  WWDR

Apologies. Attached both the above image and one from Xcode 26 (both on macOS 27). Both are configured to use the same font, but I don't think that's the issue.

For posterity, here is how it looks in 26:

Thanks for sharing this! You can rest assured that we work hard to exhaustively handle all kinds of Unicode cases.

In this situation, it appears that the intentional feature to decompose ZWJ-composed Unicode glyphs may be mistakenly turned on all the time instead of only when you choose "show invisibles." This is a display-layer problem, not one with text storage or processing, so it should not affect your ability to use Xcode with strings in any other ways.

Thank you for the update! Hopefully, it's a quick one to fix.