{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreie2tbmnaptuqoi74yhq4eqzxnhqvjpm2t4dbypikho5kgjhh5azgm",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mp4satybt7r2"
  },
  "path": "/t/gpt-4-1-character-encoding-issues/1236017?page=2#post_33",
  "publishedAt": "2026-06-25T15:18:37.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "GPT-4o returning malformed Unicode like \\u0000e6 instead of æ — encoding bug?",
    "Bugs",
    "@OpenAI_Support",
    "@OpenAIAPIhelper"
  ],
  "textContent": "Hi following your long discussions, I believe that it’s due to a restriction in OpenAI’s endpoint, which does not allow unicode escape sequences, except those for control characters.\n\nSee more with my original post:\n\nGPT-4o returning malformed Unicode like \\u0000e6 instead of æ — encoding bug? Bugs\n\n> We did an investigation and are confident that it is not from the tokenizer/tokenization. Instead, the endpoints seem to ban the generation of escaped Unicode sequence, other than control characters (0x0000-0x001f and 0x007f). But this is an undocumented behaviour, we still need confirmation from @OpenAI_Support @OpenAIAPIhelper Three things to work this around now: → Set ensure_ascii=False in your Python json.dumps() calls; → Remove \\uXXXX examples from your prompts; → Avoid asking to gener…",
  "title": "GPT 4.1 Character Encoding Issues?"
}