- [ ] add ‘ka’ to supported languages
- [ ] add ‘ka’ to `locale-data` from `react-intl`
- [ ] bump minor version to indicate new language
- [ ] sync translations for new langage
- [ ] Add Khmer (km) to the menu as ‘ភាសាខ្មែរ’ (alphabetizesd as ‘phi…’ from wikipedia: natively ភាសាខ្មែរ phiəsaa khmae Khmer pronunciation: [pʰiə.ˈsaː kʰmae])
- [ ] import km locale-data
- [ ] Update translations for editor and www
as of react-intl 2.8.0 māori (mi) locale data is included in `react-intl/locale-data`. Use that instead of a custom locale.
Also remove unnecessary `es-419` custom locale, `es-419` is already included in the default `es.js` locale-data.
* bumped minor version
* added localeMap for converting between transifex locales and the ones used by Scratch (e.g., pt-br - pt_BR)
* using the transifex node package to automatically sync translations
* added scripts:
* sync_tx_src: uploads an en.json source file, for use by client packages
* sync_tx_translations: downloads gui translations, used by this repo, flattens Chrome i18n json into plain key-value json.
* sync_tx_blocks: same as above, but blocks need slightly different handling
* validate_translations: check the translation json files for basic translation errors
* tx_util - methods shared by sync and validate
* simplified build-data because jsons have already been flattened
* added new npm tasks
Add newly completely languages to the menu:
* Azerbaijani - was already importing locale as parent of Abkhaz, changed comment
* Hungarian, Pollish, Russian,
Create editor folder for all the editor components:
* blocks - from scratch-blocks
* extensions - from scratch-vm
* interface - from scratch-gui
* paint-editor - from scratch-paint.
Update the transifex config, initilaize with the english sources.
Export a combined editor-msgs.js in addition to individual files.
Renamed paint to paint-editor to match the name in transifex.
Breaking change - bumped major version to 2.
Restructured to support multiple components. Package default is just localeData for currently supported locales including the name for each language.
messages for each component are exported as separate files in locales. Clients of l10n will need to import messages for each of the compents used and combine them.
