Back to notes
๐งDevelopment๐ชChallenging
Building Multi-language Support System
August 25, 2025
4 min
Building a multi-language support system for the Park Labs website. Supporting 3 languages: Korean, English, Japanese. Using next-intl.
Adding i18n to the website.
Since uranai-musume targets Japan and I'm thinking about going global eventually, figured I should set up the multi-language structure from the start.
๐ ๏ธ Progress
1. next-intl setup complete
/ko, /en, /ja routing structure
Separate message files per language
Language selector implemented
2. Translation work
Korean โ
English โ
Japanese โ
The translations themselves were quick, but applying them to every component is surprisingly tedious
3. Stuff I struggled with
Next.js params changed to Promise type and type errors blew up. Spent a while digging through the official docs to fix it.
Combining SSG with i18n routing was tricky. You have to generate all locale combinations in generateStaticParams, which I didn't know at first so I hit build errors a few times.
Configuring locale redirects on Cloudflare Pages was also a headache.
๐ Why 3 languages?
Japanese: Essential for the uranai-musume project
English: Preparing for global expansion
Lucky that Korean and Japanese have similar word order. English translation is the hardest part.
If I'd tried to add multi-language support later, it would've been a nightmare. Glad I did it from the start.
#i18n#multilingual#next-intl#internationalization#Japan#English