feature: update German (de) translation to 2.6.4

[retostauss]

Just to try the suggested steps in the TiddlyWikiClassic Google group ...

[YakovL]

Hi Reto, great! You have successfully made an edit and a PR, now let's make it mergeable:

• add the other changes (although they are not very important): add an empty search placeholder and either comment the line with action: saveChanges (to keep backwards compatibility with versions below 2.6.3) or remove the , action: saveChanges bit;
• update the slices:
  • minimal approach: set Version and CoreVersion to 2.6.4;
  • a new approach (I'd use this one for now because of robustness – now version number duplication): remove CoreVersion slice, update Version, add the translated "Description" slice (would be "Beschreibung", right?);
  • a new approach that seems more flexible: remove CoreVersion slice, update Version, add the translated "Description" slice, mention the version number in "Description" and "Beschreibung" (see an example here).

Some explanations regarding the slices:

• CoreVersion slice prevents a plugin from being run on earlier versions of TW, so if we increase it, we remove backwards compatibility, that's why it's preferrable to remove it;
• Version slice is used for distinguishing versions of a plugin (a translation): keeping it equal to the supported core version is fine as long as you don't make corrections and things like that. For instance, if the translation has Version 2.9.4 and you find a typo in it, you have to bump a version so that others can see it's a new one (including via EEP), but that's not an update for the core 2.9.5 (which is not released yet), so this may be inconvenient;
• that's why in ru translation, I haven't switched Version to correspond the core version, instead it's to track changes, and the version is inside the Description/Описание slices. It's not great that it's repeated twice (easy to miss this when updating), but it's ok;
• adding a translated "Description" is entirely optional, but sounds like a good practice for end users: if they wanted a translation, then it'll be more convenient for them to see that this is it.

Feel free to use the minimal approach for now, to get confident about the updating process first.

[YakovL]

Another note: to do more commits to this PR, you just need to:

• open your fork (https://github.com/retostauss/translations/);
• select this branch (translate-264, https://github.com/retostauss/translations/tree/translate-264);
• open it in github.dev again (https://github.dev/retostauss/translations/tree/translate-264);
• edit the file, then commit and push again.

[retostauss]

OMG, Yakov, you are so incredibly patient and helpful - your huge extra effort to describe everything in this detail is my motivation for now ;-)

I followed the steps, hope it fits now.

[YakovL]

Great! One last bit: since you have removed the action: saveChanges bit, the translation will break the "save" button in backstage before 2.6.3, so it's better to keep the ~CoreVersion slice, but set it to 2.6.3. On the other hand, there's hardly a user who uses TW below 2.6.3, so I'll merge this PR and you can add ~CoreVersion in the next PR if you like.

Thanks! Would be lovely if you go on with this to update the translation to later versions. Now, as you've made an update to your master branch that's not merged yet, I suggest to either continue with updates in the translate-264 branch (after merging, they will no longer come to this PR, you'll need a new one) or create another branch from translate-264 (not from master) – you can specify that in the new branch UI:

Once we finish and merge the other PR, you'll be able to make new branches from master again, without them having unwanted commits (unwanted in the sense "changes that are logically different should be separated into different PRs")

[retostauss]

It is my intention to update the German translation to the current TWc version - to get more practice. And I will add again ~CoreVersion in the next PR.