It would be an interesting feature, though I'm not sure if doable with our architecture.

For large applications supporting many languages, an editor could load translations dynamically based on the current localization. However, currently, it's not possible as we don't know the base URL for the i18n resources. Also, we would need to think about how the translations should be loaded before the editor starts. There's also a question if the editor should be able to change the localization at runtime (though it's a much larger topic).

I'm most afraid of the delay that would start occurring - loading the translation file before the editor starts. For sure, running a script with translations before the editor script is much faster than loading the editor, running it, and waiting for the translation script to be downloaded and run.

We would need to think about all cases - like integrations with Angular, Vue, Reacts apps, multiple editors localized differently on the same page, etc.

If you'd like to see this feature implemented, add a 👍 reaction to this post.