-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
German translations of principles and glossary #58
Conversation
Beautiful and spot on translation, I am very much impressed (having tried myself). Maybe we shouldn't use country icons to represent languages? There are also German speakers who don't live in Germany... |
Thank you, and good catch: I've removed to flag. |
Total der Hammer! Going to go through this later today, but my German is only at a B1/B2 level so I'll need some help from @schlomo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all looks good to me. We should have another person look through it though before merging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if you would have to define "IST-Zustand" if you already define "SOLL-Zustand", but it should be common knowledge.
We were unsure how far we should deviate from the original source. There were a few details we struggled with in English and the English glossary e.g. also only explains the "desired state". In the end we decided to start with a translation as close as possible to the source but we'd surely be open for a more general discussion as well. |
yes. I just remembered, that this is a translation. Nevermind. my fault. |
Okay to merge? @scottrigby |
Nice work everyone! 🇩🇪😀 @christianh814 we could create a 1.1.0 release that includes this translation. Corrections to translations could be in patch versions. @heubeck only suggestion is adding Co-authored-by commit trailer lines for each person you already credited in the commit message! Do you have their names and GitHub emails/anonymous emails? We have done this with PRs representing precious group efforts: https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors |
Co-authored-by: Michael Rempel <mrempel23@gmail.com> Co-authored-by: Bernd Stübinger <bernd.stuebinger@gmx.de> Co-authored-by: Richard Steinbrück <richard.steinbrueck@googlemail.com> Co-authored-by: Tung Beier <beiertu@mediamarktsaturn.com> Co-authored-by: Jochen Bürkle <buerkle@mediamarktsaturn.com> Co-authored-by: Jan Knieling <knieling_jan@hotmail.com> Co-authored-by: Kevin Fritz <fritzk@mediamarktsaturn.com> Signed-off-by: Florian Heubeck <heubeck@mediamarktsaturn.com>
Thank you @scottrigby, we did the co-authored now properly. |
FYI, there are also technical reasons for not using flag emojis to denote language, as apparently Windows doesn't support that, see https://youtu.be/_mZBa3sqTrI?t=2915 by @dylanbeattie I cannot validate this since I lack a suitable test environment, but I thought that it might help here to know about this. |
Thank you, everyone! Really impressed by the collective effort here 👏 🎉💪 |
Addresses #53
Solves #52
Contributors:
@mrempel23
@stuebingerb
@steinbrueckri
@beiertu-mms
@buerkle-mms
@Aldimann
@kharf
@heubeck
Yours sincerely
Java User Group Ingolstadt and Friends