Re: [tw5] How to do plugin translations

Well, the macro was designed to help autonomous translation for devs or users in a easy and clearly distinct way from <>. It's transparent for users and doesn't use bundled tiddlers. I'm a bit agnostic about the best convention to adopt. I'm sure that there would be better advice here around (or

Re: [tw5] How to do plugin translations

All right. So i18n can support whatever domain I configure it to, but then that brings me back to my original question. What would be the most appropriate domain to use. *$:/plugins/vendor_name/plugin_name/...* or *$:/language/vendor_name/plugin_name/...* Convention suggests the first, but

Re: [tw5] How to do plugin translations

Just to be complete about this, see usage for Feather Icons Plugin , i18n tiddlers are - ... - $:/plugins/sycom/feather-icons/i18n/en-GB - $:/plugins/sycom/feather-icons/i18n/en-GB/macrosIntro -

Re: [tw5] How to do plugin translations

Hello, The behaviour is somewhat different with the domain parameter : your translations will be in domain/i18n/lg-LG Default value is $:/ but it's up to you and might be $:/plugins/plugin_vendor/plugin_name and your translations will be in $:/plugins/plugin_vendor/plugin_name/i18n/lg-LG

Re: [tw5] How to do plugin translations

So that looks like an interesting macro which addresses the problem of localization for now. Except it doesn't seem to answer the question of what the ultimate standard would become. Your macro encourages a " *$:/i18n/language/title*" naming convention. That means language tiddlers inside my

Re: [tw5] How to do plugin translations

Hello, You may find this thread on tiddlywikidev useful: https://groups.google.com/forum/#!topic/tiddlywikidev/fu0QFcs9O_U Cheers Sylvain @sycom -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving

Re: [tw5] How to do plugin translations

Hi Jeremy, I'm looking into this too. While your response make good sense to me, I do have one question: Given the mechanism of the $tw.Language module, and how plugin language translations could theoretically be separate from the plugins they're translating, wouldn't the most appropriate

Re: [tw5] How to do plugin translations

Hi Ilya > I am completely lost with plugin translations. The core doesn’t currently support translations for plugins, I’m afraid. That doesn’t stop you making a plugin that has multiple translations, but it means that you have to roll your own, including building an equivalent of the `lingo`

[tw5] How to do plugin translations

I am completely lost with plugin translations. The core has `lingo` macro. So I tried to use it as follows: languages/ru-RU/Note.multids: ``` title: $:/language/plugins/plugin_vendor/plugin_name/ Note: New Note ``` I used it in tiddlers as follows ``` \define lingo-base()