- Jul 21, 2017
-
-
chrisgarrity authored
move all locale data (react-intl/locale-data and gui messages) into locale.js. This also makes switching to an external node package easier because the package just needs to export the same thing as locale.js.
-
- Jul 19, 2017
-
-
chrisgarrity authored
Added language-selector component and container. Replaced lib/intl.jsx with reducers/intl.js and added updateIntl to handle language changes. Moved languages.json into src
-
- Jul 18, 2017
-
-
chrisgarrity authored
-
chrisgarrity authored
Generate `locale/messages.json` from available languages in `translations`. If there are no translations for a given language (from `languages.json`) it just skips it, react-intl will use the default english strings. Just using English, French and Spanish for testing right now.
-
- Jul 17, 2017
-
-
chrisgarrity authored
Making the script easier to reuse later.
-
chrisgarrity authored
Using babel-plugin-react intl to extract messages from sources that use react-intl. It creates one file per component, that’s not ideal for translators. Transifex supports several different json formats. We picked the chrome i18n json format because it includes the ‘description’ and displays that to translators as instructions in the transifex UI.
-