Redmine

Since I don't understand German, I am not sure if this change is appropriate. I want people who understand Geman to review the patch.

I think the patches look good and are a great improvement of the current translation. My only concern is the translation of the diff label. As it is only used in the SCM context and the word diff is quite common in the jargon of programmers I'm not sure if it's appropriate to change it to Vergleich (Comparison). I've added some more native speakers as watchers to hopefully get more feedback from others.

While I am generally fine with the translation of diff, since Vergleich imho is pretty spot on in it's meaning, I have two other remarks :)

• I have a problem with the mixed use of Ticket and Aufgabe. While either would be fine with me as word for the English ticket, I find it bad to mix both of them. The patch introduces such a mixed use for open_issue_with_closed_parent. I admit at least another such mixed use is currently present (cant_link_an_issue_with_a_descendant), as I'm typing this on my phone I can't check for other occurrences right now. I admit that Unteraufgabe is a much nicer word than Unterticket, but maybe that's just a sign that we should generally rename Ticket to Aufgabe ;)
• text_mercurial_repository_note - I think there should not be a space in the z.B. acronym.

Jens Krämer wrote:

• I have a problem with the mixed use of Ticket and Aufgabe. While either would be fine with me as word for the English ticket, I find it bad to mix both of them. The patch introduces such a mixed use for open_issue_with_closed_parent. I admit at least another such mixed use is currently present (cant_link_an_issue_with_a_descendant), as I'm typing this on my phone I can't check for other occurrences right now. I admit that Unteraufgabe is a much nicer word than Unterticket, but maybe that's just a sign that we should generally rename Ticket to Aufgabe ;)

I personally like the word Ticket more since it describes the functionality in an abstract way which is not tied to the purpose like Aufgabe, Auftrag, Vorgang. But I'm also fine with Aufgabe as most Tickets are assignments anyway. :-)

• text_mercurial_repository_note - I think there should not be a space in the z.B. acronym.

The acronym z.B. without the space is the deprecated form. The up to date notation is the one that Thomas has proposed. https://www.duden.de/rechtschreibung/z__B_

Looks good to me!

I admit that Unteraufgabe is a much nicer word than Unterticket, but maybe that's just a sign that we should generally rename Ticket to Aufgabe ;)

I totally agree and I think we can just do it like in the original English version, where issue and subtask are also used side by side.

I personally like the word Ticket more since it describes the functionality in an abstract way which is not tied to the purpose

I agree

Please assign this issue to me when the final translation patch is ready.

How is the current status of the patch? Could someone provide a final patch?

Oh by the way... I replaced the term "Unteraufgaben" with "Untergeordnete Tickets" which sounds nicer than "Unterticket" and looks way better in the details view when it gets shown above "Verlinkte Tickets".