AI inserted chapters, etc uses typography characters and breaks RTF export
t
tom nash
RTF transcript export with AI-generated content produces corrupted characters
Description:
When exporting a transcript as RTF from the Mac desktop app, any AI-generated content (for example, from Add Chapters) that includes smart punctuation results in corrupted characters in standard editors.
Steps to Reproduce:
1. Open Descript (Mac desktop).
2. Generate or edit a transcript using an AI tool (e.g., Add Chapters).
3. Export transcript → RTF.
4. Open the exported RTF in macOS TextEdit or Microsoft Word.
Expected Result:
All punctuation (curly quotes, non-breaking hyphens, en/em dashes) displays correctly.
Actual Result:
Unicode typography characters appear as garbled text (mojibake), for example:
• Curly single quote (‘) → ‘
• Curly single quote (’) → ’
• Non-breaking hyphen (‑) → ‑
ASCII characters (straight quotes, standard hyphens) display correctly.
Additional Notes:
• Exporting the same transcript as Markdown (.md) or DOCX does not reproduce this issue, indicating a problem in the RTF export encoding or Unicode handling in Descript.
• This occurs immediately upon opening the RTF; no copying or pasting is involved.
Environment:
• Descript Mac desktop app (latest version)
• macOS [insert version]
• Test editors: TextEdit, Microsoft Word
Impact:
Breaks transcripts that contain AI-generated content and forces manual encoding fixes, making RTF export unreliable for workflows that require Unicode-safe punctuation.