Initial Korean-Centered Public Pages Expanded to Support 11 Major Languages
Initially centered on Korean, we expanded major public pages to 11 languages and organized brand names, feature names, and pricing guidance by language.
This post records the limitation from the initial public release when Korean was the default and public pages in other languages were not sufficiently prepared. When feature descriptions, pricing, and account guidance exist in only one language, overseas users have difficulty accurately understanding the product. Later, we expanded major public pages to 11 languages.
Multilingual support is not just translating sentences but delivering the same product contract in all languages.
What Changed in This Update
- Supports English, 한국어, 日本語, 简体中文, 繁體中文, Deutsch, Français, Español, Italiano, Português (Brasil), and Русский environments.
- Organized public text for the homepage, pricing, feature guides, and major account screens by language.
- Product proper nouns like 5BY.AI, 5by Tools, Pack, Saved, Anchor, and Handoff are maintained with consistent contracts.
- Organized search exposure information such as language-specific title, Open Graph, and canonical to match public paths.
- Applied criteria to review locale keys together when adding new text so specific languages are not omitted.
How to Verify
- Select the desired language from the homepage language selector.
- Navigate through pricing, feature guides, and account pages to check that the language is maintained.
- Check that product proper nouns and feature meanings are not translated differently across languages.
- Record missing or awkward text with the page and language together and leave feedback.
Example in Actual Usage Flow
For example, to check whether this limitation is still valid, the user selects the desired language from the homepage language selector. They navigate through pricing, feature guides, and account pages to check that the language is maintained. If needed, they record missing or awkward text with the page and language together and leave feedback. Also, the following should be used as the boundary for determining the latest status. Support for 11 languages does not mean complete translation of all developer notes and user-generated content. Following this flow prevents misunderstanding past limitation records and current provided scope as the same status.
Before and After the Change
Known limitations, if the state at the time of publication and the current state are not distinguished, old notices can remain as current facts. In this update, initially centered on Korean, we expanded major public pages to 11 languages and organized brand names, feature names, and pricing guidance by language. We recorded the parts where the limitation persists, parts subsequently resolved, and the latest verification path together so changes over time can be checked.
Scope and Things to Note
- Support for 11 languages does not mean complete translation of all developer notes and user-generated content.
- The AI Provider's own language support and 5BY.AI's public page translation scope are different.
- Proper nouns where feature contracts could become ambiguous are not arbitrarily localized.
- When new pages and text are added, translation omissions may occur and continuous review is needed.
Why This Change Matters in the Overall 5BY.AI Structure
When resolving the initial language limitation, what mattered most was not translation volume but meaning consistency. Regardless of which language is viewed, the same product structure and user control principles are maintained so that 5BY.AI is not described differently as a note app or automatic judgment system.
Criteria for Verifying This Update
- Whether the limitation is still valid or has been resolved in subsequent updates should be distinguished chronologically.
- Features not provided should not be communicated as usable through workarounds.
- When the limitation status changes, existing records should not be deleted but connected with the resolution path and latest notice.