-
Notifications
You must be signed in to change notification settings - Fork 269
add missing german localization for v8.37 #664
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
Conversation
Add the missing keys in the German translation file.
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.
A couple of comments. Mostly to keep in line with other translations. If you feel like existing translations are incorrect, then changing those is also fine.
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.
I would go with "Fetche Text.BranchCM.Merge
and Text.BranchCM.PullInto
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.
Indentation
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.
Since the translation for Github is without "eine" aswell. Would also be fine if you add "eine" for the Github version.
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.
Same as the other one.
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 seems a bit odd and also does not translate the "(...) use it in this repo(...)". I would translate this a bit more freely.
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.
Did you mean it like this?
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.
We used "gestagte" before, e.g. Text.Hotkeys.Repo.Commit
, Text.Stash.OnlyStagedChanges
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.
Very nice comments!
Please resolve the conflicts with PR #665.
Hi,
thanks for your comment. Hopefully I didn't mess things up, I am not used to Github's browser editor.
3b4e037
into
sourcegit-scm:develop
@Stern1710 were you planning to include my other suggestions? Otherwise I could also create a new PR for that.
@NilsPvR Hey, I am not 100% sure what you are exactly referring to. I have committed your changes to the source code already, but forgot (and/or didn't know) to mark them as resolved on Github. Sorry.
If you are referring to something else, please feel free to create a new PR and I will gladly help, when needed.
Obviously, I could be lost in translation and just don't get it how Github exactly works with their way of resolving issues.
Edit: Well, I think I somehow f-ed this up? Which I am somewhat unsure on how I did it, when I clearly remembered the browser editor having marked all the suggestions as asccepted. Guess I never stop learning :D
@Stern1710 yee the merge commit looked good that's why I gave thumbs up. But the other suggestions seem to have gotten lost then 🤷♂️ 😅
- mostly code review suggestions from sourcegit-scm#664 - ClearAllCommitsFilter is not an action of deleting (löschen)
Uh oh!
There was an error while loading. Please reload this page.
Add the missing keys in the German translation file.
Question: What do you deem the best way to truly test out where each of the individual keys is used inside the software (like which parts, where to access on theGUI, etc)?