David Taylor 880311dd4d FEATURE: Support for localized themes (#6848) ... - Themes can supply translation files in a format like `/locales/{locale}.yml`. These files should be valid YAML, with a single top level key equal to the locale being defined. For now these can only be defined using the `discourse_theme` CLI, importing a `.tar.gz`, or from a GIT repository. - Fallback is handled on a global level (if the locale is not defined in the theme), as well as on individual keys (if some keys are missing from the selected interface language). - Administrators can override individual keys on a per-theme basis in the /admin/customize/themes user interface. - Theme developers should access defined translations using the new theme prefix variables: JavaScript: `I18n.t(themePrefix("my_translation_key"))` Handlebars: `{{theme-i18n "my_translation_key"}}` or `{{i18n (theme-prefix "my_translation_key")}}` - To design for backwards compatibility, theme developers can check for the presence of the `themePrefix` variable in JavaScript - As part of this, the old `{{themeSetting.setting_name}}` syntax is deprecated in favour of `{{theme-setting "setting_name"}}`		2019-01-17 11:46:11 +00:00
..
helpers	FIX: Relative links in templates should work with subfolders	2018-11-07 11:35:04 +01:00
lib	FEATURE: Support for localized themes (#6848)	2019-01-17 11:46:11 +00:00
resolver.js.es6	DEV: introduces prettier for es6 files	2018-06-15 17:03:24 +02:00