German translation for ExtensionsExplorerPlugin completed

[retostauss]

Translated the rest of the lingo and tested it successfully - as far as I could.

[retostauss]

Unfortunately I did not follow the usual commit message best practice ... did not find out how to change that.

[YakovL]

Great work, congratulations! I'll merge this one, but it's better to add Source to the translation, so that EEP can update it once it's modified. I'll also think about the infrastructure for translations, may be EEP should automatically detect and suggest translations (to the same language as the core translation) when they are available

[retostauss]

... but it's better to add Source to the translation, so ...

Are you doing this?

I'll also think about the infrastructure for translations, may be EEP should automatically detect and suggest translations (to the same language as the core translation) when they are available

That would be nice.

What about the distribution of this translation tiddler? How and where will it be published? Where and how can I obtain it officially?

[YakovL]

Are you doing this?

Done this a minute ago, yes.

What about the distribution of this translation tiddler?

I haven't decided what would be a good option, but let me add some considerations:

• first, you can always copy the translation from the repo manually: that will work for you as you know where to look, and updates will be delivered by EEP automatically. You can also include it into your custom collection if you want to share with friends;
• one option of "making available" is to add it into the YlExtensionsCollection. It doesn't feels a good option as typically it's not the plugin author who knows another language and creates the translation, it should be more decentralized;
• a more sane option is TranslationsCollection. Not sure if this is a good idea to mix it with core translations, but as currently we don't have many other translations, this may be the way to go. But, if a user can install it via EEP, does they really need a translation? This doesn't seem to make much sense for EEP, seems reasonable for other extensions.
• finally, a good option would be to make EEP do the custom job for translations: at some point, check for each extension (with ExtensionName), if a core translation is installed (say, de), check https://github.com/TiddlyWiki/translations/blob/master/locales/extensions/ExtensionName/locale.de.js and install if it's available. Not sure yet what "at some point" should be: it may be on startup (optionally, like the update availability checks), a separate button (may be even in a separate Translations tab). But this will take time, and I have higher-priority tasks even for EEP (for instance, separating tabs Installed/Explore or adding search).

Let me know if you have some comments on this