Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update How-To-Add-Translations.md #1153

Merged
merged 1 commit into from
Oct 31, 2023
Merged

Update How-To-Add-Translations.md #1153

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/How-To-Add-Translations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
This document outlines how to add support for various local languages in Phoenix.

Phoenix currently supports over 35 languages and are mostly automatically translated with AWS/Google translate.
Phoenix currently supports over 35 languages, primarily through automatic translations using AWS/Google Translate.

## Quick start

Expand All @@ -22,7 +22,7 @@ This folder contains all the localised strings. Each sub folder corresponds to a
A special folder called the `root` folder houses the reference english translations from which all other locale
translations are derived. The `root` folder has three main files:
1. `strings.js` - The full list of translated text.
2. `strings-app.js` - The list of language code to localised language name mapping. This will be used in the switch
2. `strings-app.js` - The list of language code to localized language name mapping. This will be used in the switch
language dialogue in debug menu.
3. `urls.js` - local specific URLs.

Expand Down Expand Up @@ -69,4 +69,4 @@ Say we want to add a new language translation `ko`. We have to do the following

Once the code is checked in, the translation will be auto generated.

> NB: For internal devs, You may manually generate the translation with `npm run _translateStrings` if you have the necessary keys for translation.
> NB: For internal developers, You may manually generate the translation with `npm run _translateStrings` if you have the necessary keys for translation.
Loading