mirror of
https://github.com/discourse/discourse.git
synced 2024-11-24 12:42:57 +08:00
880311dd4d
- 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"}}`
28 lines
836 B
Ruby
28 lines
836 B
Ruby
class ThemeTranslationOverride < ActiveRecord::Base
|
|
belongs_to :theme
|
|
|
|
after_commit do
|
|
theme.clear_cached_settings!
|
|
theme.remove_from_cache!
|
|
theme.theme_fields.where(target_id: Theme.targets[:translations]).update_all(value_baked: nil)
|
|
end
|
|
end
|
|
|
|
# == Schema Information
|
|
#
|
|
# Table name: theme_translation_overrides
|
|
#
|
|
# id :bigint(8) not null, primary key
|
|
# theme_id :integer not null
|
|
# locale :string not null
|
|
# translation_key :string not null
|
|
# value :string not null
|
|
# created_at :datetime not null
|
|
# updated_at :datetime not null
|
|
#
|
|
# Indexes
|
|
#
|
|
# index_theme_translation_overrides_on_theme_id (theme_id)
|
|
# theme_translation_overrides_unique (theme_id,locale,translation_key) UNIQUE
|
|
#
|