i18n

[versusbassz]

The textdomain name: entity-viewer (the same as the slug of the plugin) Also:

• [x] the plugin has to be compatible with translate.wordpress.org
• [x] add filter/setting to disable i18n if it's necessary --- filter vsm/is_plugin_allowed

Docs

• https://developer.wordpress.org/plugins/internationalization/
• https://developer.wordpress.org/block-editor/how-to-guides/internationalization/
• https://pippinsplugins.com/use-wp_localize_script-it-is-awesome/

Misc

• https://translate.wordpress.org/locale/ru/default/wp-plugins/?s=smtp

[versusbassz]

Mostly done. I decided to use a custom transport for js-strings, for now. Maybe, it will be replaced with native approaches in the future.

Will test after the release (and during 0.4.0 version development).