Feedback: Thai Romanization in "Explain" feature (Missing Tone Marks)

Hi Clozemaster Team,

I’m a regular user of the Thai course and other languages and I’ve been finding the “Explain” feature on mobile incredibly helpful. However, I’ve noticed a consistent issue for Thai: the Romanization/transliteration provided by the AI explanation frequently omits tone marks.
Currently, tone marks are missing roughly 75% of the time. While the transliteration of sounds is helpful, Thai is a tonal language where deciphering the tone is the most difficult variable for learners to master. Because the rules for determining tone in the Thai script (consonant class + syllable type + tone mark) are so complex, having the Romanization consistently show the tone is essential for learning. I’ve also occasionally seen the tone wrong, suggesting that the AI is trying to guess the tone from first principles rather than pull from authoritative resources.

Request:
Could you please adjust the prompt for the “AI Explain” function to strictly require tone marks in all Romanized text?

  • Priority: Consistent tone marks (e.g., mâi vs mǎi) are more important to learners than which specific transliteration system (RTGS, Paiboon, etc.) is used. Currently, it often switches between them but that’s not as important… can discuss after tones resolved.
  • Goal: Ensure the AI output always includes the tonal markers to help bridge the gap between reading the script and speaking correctly, and ideally pulls them from authoritative resources rather than attempting “read” the tone itself.
    Thank you for the amazing tool—it’s been a game-changer for my Thai studies!
    Best regards,
    ArepaVirus