discourse/config/initializers/100-i18n.rb

# frozen_string_literal: true

# order: after 02-freedom_patches.rb

require 'i18n/backend/discourse_i18n'
require 'i18n/backend/fallback_locale_list'

I18n.backend = I18n::Backend::DiscourseI18n.new
I18n.fallbacks = I18n::Backend::FallbackLocaleList.new
I18n.config.missing_interpolation_argument_handler = proc { throw(:exception) }
I18n.reload!
I18n.init_accelerator!(overrides_enabled: ENV['DISABLE_TRANSLATION_OVERRIDES'] != '1')

unless Rails.env.test?
  MessageBus.subscribe("/i18n-flush") do
    I18n.reload!
    ExtraLocalesController.clear_cache!
  end
end
DEV: enable frozen string literal on all files This reduces chances of errors where consumers of strings mutate inputs and reduces memory usage of the app. Test suite passes now, but there may be some stuff left, so we will run a few sites on a branch prior to merging 2019-05-02 18:17:27 -04:00			`# frozen_string_literal: true`

FEATURE: Localization fallbacks (server-side) The FallbackLocaleList object tells I18n::Backend::Fallbacks what order the languages should be attempted in. Because of the translate_accelerator patch, the SiteSetting.default_locale is not guaranteed to be fully loaded after the server starts, so a call to ensure_loaded! is added after the locale is set for the current user. The declarations of config.i18n.fallbacks = true in the environment files were actually garbage, because the I18n.default_locale was SiteSetting.default_locale, so there was nothing to fall back to. derp 2015-07-15 12:04:45 -04:00			`# order: after 02-freedom_patches.rb`

Refactor to our own Discourse I18n backend This removes some monkey patches and makes testing easier. It will also support database backed I18n changes. 2015-11-13 15:42:01 -05:00			`require 'i18n/backend/discourse_i18n'`
FIX: Server didn't use default_locale as fallback locale 2018-01-22 08:42:12 -05:00			`require 'i18n/backend/fallback_locale_list'`

Refactor to our own Discourse I18n backend This removes some monkey patches and makes testing easier. It will also support database backed I18n changes. 2015-11-13 15:42:01 -05:00			`I18n.backend = I18n::Backend::DiscourseI18n.new`
FIX: Server didn't use default_locale as fallback locale 2018-01-22 08:42:12 -05:00			`I18n.fallbacks = I18n::Backend::FallbackLocaleList.new`
Always use locale fallback on server 2015-09-02 15:28:50 -04:00			`I18n.config.missing_interpolation_argument_handler = proc { throw(:exception) }`
DEV: Rails 6 compatability Without forcing a reload on start internal state in the accelerator can be off. In Rails 5 not translation is being called so this is not an issue but in 6 it is called earlier on. 2019-04-29 03:12:47 -04:00			`I18n.reload!`
FIX: Failed to restore backups from versions without translation overrides Rails calls I18n.translate during initialization and by default translation overrides are used. Database migrations would fail if the system tried to migrate from an old version that didn't have the `translation_overrides` table with all its columns yet. This makes restoring really old backups work again. Running `DISABLE_TRANSLATION_OVERRIDES=1 rake db:migrate` will allow you to upgrade such an old database as well. 2020-03-12 13:43:27 -04:00			`I18n.init_accelerator!(overrides_enabled: ENV['DISABLE_TRANSLATION_OVERRIDES'] != '1')`
Refresh I18n customizations on change 2015-11-17 16:14:42 -05:00
FEATURE: Can override any translation via an admin interface 2015-11-23 16:45:05 -05:00			`unless Rails.env.test?`
FEATURE: Load translation overrides without JS `eval` 2019-11-04 20:15:44 -05:00			`MessageBus.subscribe("/i18n-flush") do`
			`I18n.reload!`
			`ExtraLocalesController.clear_cache!`
			`end`
FEATURE: Can override any translation via an admin interface 2015-11-23 16:45:05 -05:00			`end`