Community Localization

[theachoem]

StoryPad Localization

Our app currently supports the following languages, with translations provided by Google Translate:

Arabic, German, English, Spanish (Latin America), Spanish (Spain), French, Hindi, Indonesian, Italian, Japanese, Khmer, Korean, Polish, Portuguese, Thai, Vietnamese & Chinese (Simplified).

If your language is not listed, or you spot any translation glitches, feel free to suggest improvements in our Google Sheet below:

How You Can Help

1. Open the Google Sheet linked above.
2. Find your language and suggest improvements, corrections, or better translations.
3. If you see any translation errors or feel a translation can be better, add your suggestions!
4. We’ll review the updates and apply them in the app with the next release.

Thank you for helping us make StoryPad better for users around the world!

[iljinjung]

Hi! 👋
I'm a native Korean speaker and would love to help improve the Korean localization of StoryPad. 🇰🇷

I’ve checked the current translations and noticed some parts that could be more natural and user-friendly for Korean users.
I’ll review and suggest improvements directly in the Google Sheet you provided.

Let me know if there's anything specific I should keep in mind when editing!
Thanks for the awesome project 🙌

[theachoem]

Hi @iljinjung 👋

Thanks for your interest in contributing to the Korean localization of StoryPad! 🇰🇷

If you're planning to make many translations, a good approach is to duplicate the original Google Sheet and make your edits there. Once you're done, you can send it to us, and we'll copy the updates into the project.

If you'd like to contribute via GitHub, you can replace the link in bin/localize file, then run bin/localize --clean. This will download all the translation files to your VS Code, where you can make changes and submit a PR.

Let us know if you have any questions!

[iljinjung]

Thanks for your guide — it’s been super helpful!

I’m almost done with the Korean translations, but I ran into a small issue and wanted to ask before wrapping up.
I tried using \n to break lines in some translated strings (especially for onboarding messages), but it doesn’t seem to actually create a line break in the app.

Here’s a screenshot showing what I mean:

Also, just to share — I’ve been referencing Toss’s UX Writing Principles throughout the translation process to keep the tone natural, concise, and consistent across all UI text.

Let me know if there’s a recommended way to handle line breaks, or if you have any feedback on the translations!

Thanks again 🙏

[theachoem]

@iljinjung Line breaks are tricky in translations because \n gets escaped.

What we can do is to manually convert \\n to \n:

tr("my-translation").replaceAll("\\n", "\n");

I like the UX principles you've shared. I will check it in more detail and possibly, improve the overall app experience base on that.

[theachoem]

@iljinjung I got a new line to work, turns out, we just need to enter a new line in Google Sheets directly using command + enter key :D

---

[iljinjung]

I’ll take some time, but I’m planning to work on Japanese and Chinese next as well! 😆