Hey @sy0001 ,
Thank you for bringing this to our attention.
Could you please share a sample of the string (with non-Latin characters and numbers) that you’re trying to use? We’d like to investigate this specific use case further. From our end, we’re able to generate slugs in other languages, so seeing the exact input will help us pinpoint any issue with the slug generation process.
Looking forward to your example so we can investigate and assist accordingly.
Thread Starter
ss
(@sy0001)
Thank you for your quick response.
I’ve tested the Course URL field using titles that contain only Korean or Japanese characters, and here are the results:
Korean-only examples (completely removed):
- “캔바 강의” → Slug becomes: (empty)
- “썸네일 디자인 2025” → Slug becomes:
2025
Japanese-only examples (partially preserved or removed):
- “サムネイル講座” → Slug becomes:
講座
- “デザイン講義2025” → Slug becomes:
講義2025
It seems that:
- Korean Hangul is entirely stripped during slug generation.
- Some Japanese characters like Kanji are partially retained, but Katakana or Hiragana are often removed.
Since many international users create courses using non-Latin scripts,
we believe the slug generation process should support Unicode more gracefully
— either by transliteration or allowing such characters to remain.
Thank you!
Hey @sy0001 ,
Thank you for sharing the examples. We have verified them from our end and escalated the matter to the development team for review. We hope to see a resolution in a future update.
Thank you.