Bug
Copying Agent response text out of Switchboard corrupts certain Unicode characters. Clipboard content shows mojibake instead of the actual glyph.
Observed mapping
| Expected |
Got (clipboard) |
… (ellipsis, U+2026) |
‚Ħ |
— (em dash, U+2014) |
— |
→ (right arrow, U+2192) |
‚Üí |
Likely cause
Pattern matches double-encoding mojibake: UTF-8 bytes for these chars get misread as Windows-1252/Latin-1 somewhere in the copy pipeline, then re-encoded as UTF-8 on top of that.
Example: … = UTF-8 E2 80 A6. Read as CP1252 → …. Re-encode that string as UTF-8 → ‚Ħ. Same transform reproduces the — and → cases.
Suspect a spot in the copy handler (or a lib it calls) that does a Latin-1/CP1252 decode on already-UTF-8 bytes before writing to clipboard.
Repro
- Get an Agent response containing
…, —, or →.
- Copy it (button or manual select+copy — note which).
- Paste into plain-text editor.
- Chars show as
‚Ħ, ‚Äî, ‚Üí instead of originals.
Expected
Clipboard content matches on-screen text exactly.
Bug
Copying Agent response text out of Switchboard corrupts certain Unicode characters. Clipboard content shows mojibake instead of the actual glyph.
Observed mapping
…(ellipsis, U+2026)‚Ħ—(em dash, U+2014)‚Äî→(right arrow, U+2192)‚ÜíLikely cause
Pattern matches double-encoding mojibake: UTF-8 bytes for these chars get misread as Windows-1252/Latin-1 somewhere in the copy pipeline, then re-encoded as UTF-8 on top of that.
Example:
…= UTF-8E2 80 A6. Read as CP1252 →…. Re-encode that string as UTF-8 →‚Ħ. Same transform reproduces the—and→cases.Suspect a spot in the copy handler (or a lib it calls) that does a Latin-1/CP1252 decode on already-UTF-8 bytes before writing to clipboard.
Repro
…,—, or→.‚Ħ,‚Äî,‚Üíinstead of originals.Expected
Clipboard content matches on-screen text exactly.