プロジェクト

全般

プロフィール

Vote #80396

完了

Improvement of the German translation

Admin Redmine さんが3年以上前に追加. 3年以上前に更新.

ステータス:
Closed
優先度:
通常
担当者:
-
カテゴリ:
Translations_12
対象バージョン:
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
12
version_id:
152
issue_org_id:
32238
author_id:
291
assigned_to_id:
332
comments:
13
status_id:
5
tracker_id:
3
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[Closed]

説明

Hi,

I have revised the German translation and made minor changes to 51 items.

Patches for @trunk@ and @4.0-stable@ are attached.

Thanks,
Thomas


journals

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?
--------------------------------------------------------------------------------
I've attached a revision of Thoma's patch which is fixing the mixed use of "Ticket" and "Aufgabe" (issue and task). While testing I found the result very pleasing and I think it improves the UX of the module quite a lot. I decided to go with "Ticket" as it is a more universal term. IMHO flexibility is a very strong selling point for Redmine over the most SaaS solutions nowadays.

There is a request for that change in #32515, too. Perhaps we should think about also fixing this for the other locales.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
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".
--------------------------------------------------------------------------------
I've tested the patch attachment:trunk-de.yml.v2.patch against the current trunk and it still applies with no conflicts. I think the patch is a great improvement for the over all user experience and we should apply it to the next version.
--------------------------------------------------------------------------------
Updated the patch for r19602. Translation for strings "must_contain_*" has already been applied in r19572.
--------------------------------------------------------------------------------
Committed the patch. Thank you for your contribution.
--------------------------------------------------------------------------------


related_issues

relates,New,32515,locales: the "task" should be named as "issue"

Admin Redmine さんが3年以上前に更新

  • カテゴリTranslations_12 にセット
  • 対象バージョン4.2.0_152 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0