Thank you for all the additional details everyone shared regarding this issue.
We’ve rolled out a fix that addresses escaped unicode characters, to bring output formatting more in-line with our previous models.
However, we understand that there are additional issues raised in this discussion regarding incorrect unicode characters or invalid unicode characters being produced by the model. Unfortunately, we do not anticipate this new fix to fully address these issues. We are still working on it, alongside other model improvements, but can’t provide a timeline at this time.