Update de web translation for 3.8.0

[hoffie]

Hi @Helondeth, @ewarning,

We are getting ready for the 3.8.0 release and have created the translate3_8_0 branch (full diff).

Because the English is still going through large changes, we are not expecting translations of anything other than the following pages:

• Home page
• Setup (renamed from Getting-Started)
• Installation pages for each supported platform (Windows, Mac, Linux)

While you are of course welcome to translate more than this, please be aware that you may have to re-translate for the next release.

We would be happy if you updated the translations for de until 2021-05-15.

Please

• Start your work in your fork on a branch based on jamuluswebsite's translate3_8_0 branch.
• Update the language-specific files using your favorite editor (or directly on Github),
• Commit and push your changes to your fork,
• Open a Pull Request with your translations to the translate3_8_0 branch with the subject Update de web translation for 3.8.0,
• Link your PR(s) to this issue by including Fixes #456 in the PR content.

Note: The term "Central server" has been replaced with "Directory server"

This Issue is assigned to multiple people. Please coordinate who will translate what part.

Suggested commit and PR message:

Update de web translation for 3.8.0

Fixes #456

Feel free to use this Issue to discuss anything you need prior to making any PR (and in your native language if needed).

Further documentation can be found in TRANSLATING.md.

Thanks for contributing to Jamulus!

[ewarning]

Hello @hoffie,
I’ve never contributed with GitHub before, I’m trying to figure out where do I have to upload the files, and how should they be named. Maybe you can help me on this. Let’s say for instance, I’ll start with Installation for Mac. Is it under

translate_3_8_0 / jamuluswebsite / wiki / de /

• de-Installation-for-Macintosh.md / Documentation release v3.7.0 (Documentation release v3.7.0 #341)

??

Thanks!

[jujudusud]

Hi @ewarning .
The first thing to do is reading the new README.md file in the changes branch : https://github.com/jamulussoftware/jamuluswebsite/tree/changes
After that if your are familiar with git, you should just use it as usual.

The files to translate are located in the translate3_8_0 branch in your language directory (and some others are in data or root directory).
Those files have to be translate at the same level as the en files in changes branch.

[ewarning]

@jujudusud Many thanks!

[jujudusud]

Don't hesitate if you have any other questions about the process.

[ewarning]

Okay, it was no easy task but I managed to put things together! Questions:

• Why can’t I tag @Helondeth here, who is also doing the german translation?
• When commiting changes to my own fork before pulling, is there a naming convention? I see for example
  Documentation release v3.7.0 (Documentation release v3.7.0 #341)

Thanks for now, more questions will probably appear

[hoffie]

Cool! :)

Why can’t I tag @Helondeth here, who is also doing the german translation?

What do you mean by tag? By mentioning him with the @ syntax he should get a notification.

When commiting changes to my own fork before pulling, is there a naming convention?

If you mean the branch name, it doesn't matter too much. You could call it translate3_8_0_german for example.
If you mean the commit message, it would be helpful to use something like this:

Update DE translation for 3.8.0

Fixes #456

You can and should use the same text when opening the Pull Request. This will automatically link it to this issue.

[ewarning]

Thanks again @hoffie,

okay, I was confused, because when I type @h his name does not appear in the dropdown.

@Helondeth: I started working on the Setup and on Installation on macOS if you don’t mind.

[jujudusud]

Hi all, I have this image for the screenshots :

[ewarning]

@jujudusud Thanks. Another question, how do you guys work, here in the website or with the GitHub software? What would be best in terms of productivity?

[jujudusud]

I'm working with git because I can have a local "copy" of the repository and work offline with my ordinary tools (nano for the text, pinta for images ... etc). Because I use my ordinary tools, I am more productive than with another stranger tool.
But, I you feel good with web UI of github, it's great and powerfull.
The only things that I do with Github web UI are forking a repository, fetching my fork with upstream when necessary and creating issues and pull requests.