electerm multi-language support pack.
🇺🇸 🇨🇳 🇧🇷 🇷🇺 🇪🇸 🇫🇷 🇹🇷 🇭🇰 🇯🇵
git clone git://github.com/electerm/electerm-locales.git
cd electerm-locales
npm i
cp config.sample.js config.js
npm start
# automatic sync locales/* to ../electerm/node_modules/electerm-locales/locales/ for test
# and add pre-push hook, do lint and test before every pushnpm run test
# test only make sure all locale file keys and orders are match.Just use locales/en_us.js as a example, fork this repo, add your edit, then submit a pull request.
Make sure you run npm run test before push.
To make the work easier, I have created a script to help creating a language file, it uses google translate API to translate all entry and create a new language file.
# use
# lang={language code} node bin/create-new-lang.js
# then it will create a {language code}_{language code}.js in locales folder
# for example:
# this will create a German language file `locales/de_de.js`
lang=de node bin/create-new-lang.js
# then you can review and edit to make sure every entry is rightYou can certainly translate it one by one, I also provide a script to do it.
# entry="{level one entry name}" name="{the prop name}" text="{the text in original language}" original="{language code, default is en}" node bin/add-new-entry.js
# check https://github.com/hua1995116/google-translate-open-api/blob/master/src/language.ts for language code
# example:
entry=setting name=saveTerminalLogToFile text="save terminal log to file" original=en node bin/add-new-entry.js
# then it will add saveTerminalLogToFile entry to all language file in setting namespace with google translatecp sample.env .env
# then edit .env, add socks proxy- 🇺🇸English: @zxdong262
- 🇨🇳简体中文: @zxdong262
- 🇧🇷Português do Brasil: @Meirinaldo Júnior
- 🇷🇺русский: @Vasiliy
- 🇪🇸Español: Federico Pereira fpereira@cnsoluciones.com
- 🇫🇷Français: @Damien Mosse
- 🇹🇷Türkçe: @Nazım Gediz Aydındoğmuş
- 🇭🇰繁体中文: @ycku
- 🇯🇵日本語: @hououinkami
https://github.com/electerm/electerm-locales/graphs/contributors