Language barrier?

Scott_Sauyet · August 21, 2025, 1:44pm

Perhaps some variant of this icon?:

Scott_Sauyet · August 21, 2025, 2:01pm

We discussed something like this in #12099 (sorry, quite long), but never reached a consensus. At some point I will go back to that project and try to get something working.

XLBilly · August 21, 2025, 11:22pm

IMO language support for plugins is related to this PR:

github.com/TiddlyWiki/TiddlyWiki5

Introducing bundled sub plugins

TiddlyWiki:master ← TiddlyWiki:intrinsic-sub-plugins

opened 09:36AM - 18 Feb 25 UTC

Jermolene

+852 -226

# Introduction This PR introduces "bundled sub-plugins" a new feature that al…lows plugins to contain further sub-plugins that are processed in the same way as top level plugins. This change is intended to address several related needs: * Shipping plugins with multiple translations, without having to package them as separate plugins (this PR is intended to fix #8435) * Making plugins as separate sub-components that can be independently disabled and overridden by end users * Shipping themes, languages and normal plugins together as a single container plugin with no dependencies # Usage To create a sub-plugin, add the plugin tiddler as a payload tiddler within the parent plugin. Any shadow tiddler with their type set to `application/json` and also has a `plugin-type` field will be processed as a sub-plugin. Under Node.js, sub-plugins are created by placing a `plugin.info` file in a subdirectory of the parent plugin folder. # Progress * [x] Update plugin switching logic to accommodate sub-plugins * [ ] Dynamic handling of changes to `$:/config/Plugins/Disabled/*` tiddlers * [ ] Update control panel listing of installed plugins to indicate sub-plugins * [ ] Filter operator to retrieve the sub-plugins of a plugin * [ ] `is[subplugin]` filter operator * [ ] Update the demo CodeMirror embedded translation to use real language strings. We should put a call out for translators * [ ] Update control panel "add plugin" dialogue to show sub-plugins * [ ] User documentation updates * [ ] Documentation updates for wikitext authors * [ ] Update the Translators plugin so that it can be used to create language sub-plugins as well as creating core translations # Backwards Compatibility The existing term "sub-plugin" refers to a plugin that is subordinate to a parent plugin. Currently, the only way to create a sub-plugins is to set their `parent-plugin` field to the title of their parent plugin. The plugin library listing displays sub-plugins hierarchically under an expandable button. The plugin library also automatically installs the parent plugin of sub-plugins (along with any plugins listed in the `dependents` field). This PR will eventually add the hierarchical display to the listing of installed plugins. There are no breaking changes to the internal JavaScript API. # Subtleties and gotchas * Sub-plugins cannot currently contain further sub-plugins. * Disabling the parent plugin via the `$:/config/Plugins/Disabled/` mechanism always disables all the sub-plugins. If the parent plugin is enabled then the sub-plugins can be individually disabled via the same mechanism * Sub-plugins with a given title are independent of any tiddler or shadow tiddler with the same title. In particular, that means that sub-plugins cannot be overridden by creating a tiddler of the same title. # Open Questions * Should we require plugins that contain sub-plugins to be specifically marked (eg by a special field)? It would avoid the problem whereby any existing plugins that contain plugins as payload tiddlers would unexpectedly be loaded.