You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
plugin.info is a JSON (I'm not sure what it become after install, but should be a JSON tiddler too?), so instead of use field like name::fr-FR, we should use
Hi @linonetwo the contents of plugin.info is flattened into tiddler fields as plugins are loaded, which implies that the language processing would have to be done as the plugin was constructed under Node.js. So, I think it would be more useful if the available translations were all retained so that the single file configuration of TiddlyWiki could also choose the best language to use.
Is your feature request related to a problem? Please describe.
Discussed on feat: t macro and docs #7821 (comment)
Describe the solution you'd like
plugin.info is a JSON (I'm not sure what it become after install, but should be a JSON tiddler too?), so instead of use field like
name::fr-FR
, we should useDescribe alternatives you've considered
I'm afraid flatten field like
name::fr-FR
will make a long list and difficult to maintain.Additional context
Make everything fully international.
The text was updated successfully, but these errors were encountered: