Jermolene
Add localisable strings for plugins
Hi @araname thank you for this.
Are the new language sub-plugins being built into the plugin library?
I'm worried about the new naming convention of the language sub-plugins. Existing code elsewhere is expecting names of the format <publisher-name>/<plugin-name>.
Also, having to install separate language plugins seems inconvenient for the user. I wonder if we'd be better off packaging the strings in the main language plugins. In other words, the main ko-KR language plugin would incorporate the language strings for all of the core library plugins. That way, a Korean user would just need to install the one Korean plugin, and then can freely install and uninstall other plugins, and get the translated version where available.
The alternative seems to be to engineer the mechanisms and UI for complex relationships between plugins.
I'd be in favor of modularity, especially since any of this would only apply to core plugins:
- provide a means to define dependent plugins
- dependent plugin selection / suggestions can be constrained by pre-defined criteria, e.g. plugin language = wiki language
Close with wont-fix in favour of https://github.com/TiddlyWiki/TiddlyWiki5/pull/8957
