-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Improve multiple strings in en-US locale #26213
Conversation
I kept sending pull requests that consisted of one-line changes. It's time to settle this once and for all. (Maybe.)
I understand that all of these changes at once make for a stressful review process, but I figured that incremental fixes (as I have done so far) probably take up more resources on both ends here. I tried to go for being consistent; I think my biggest hesitation here involved the way I appended the word "successfully". I'm a details person; I hope that this will make Gitea look more polished. I will not be available in the next few days (as in, it might take at least 12 hours for me to see replies), so feel free to merge any suggestions without my permission. |
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Thanks for the additional recommendations and sorry for that regex fail, really goes on to show how this is super subjective work. |
options/locale/locale_en-US.ini
Outdated
@@ -691,7 +691,7 @@ emails = Email Addresses | |||
manage_emails = Manage Email Addresses | |||
manage_themes = Select default theme | |||
manage_openid = Manage OpenID Addresses | |||
email_desc = Your primary email address will be used for notifications and other operations. | |||
email_desc = Your primary email address will be used for notifications and Git operations made using the web interface. |
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.
The sentence reads strange, because IMO:
- Not only "Git operations made using the web interface", but all related "Git operations"
- Not only notifications, but I think there are also emails for verification or password recovery?
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 only "Git operations made using the web interface", but all related "Git operations"
If I make a commit using a secondary email that is not primary, my primary email address will not be used. Unless if you mean pull requests.
Not only notifications, but I think there are also emails for verification or password recovery?
Good point.
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 only "Git operations made using the web interface", but all related "Git operations"
If I make a commit using a secondary email that is not primary, my primary email address will not be used.
I see your point and I misunderstood it before. I think it means "this email will be used as the committer email for web Git operations"
email_desc = Your primary email address will be used for notifications and Git operations made using the web interface. | |
email_desc = Your primary email address will be used for notifications and as the committer email for web Git operations. |
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.
I'll change it to web-based, I think it's very much clear as day and I don't think it will confuse more advanced users that would presumably use the tea
CLI tool later on.
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.
Keep in mind, there's many users (myself included, 2 months ago) that do not get that hiding the email address results in a noreply email address being used - this should be mentioned somewhere. It's why I made that change with the padlock - the recommendation to add a tooltip that someone made to the PR (as well as a previous commit that would never make emails accessible to everyone on the Internet) has vastly improved the situation, as people are less likely to hide it. Maybe a tooltip over the "Hide Email Address" option could help later.
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.
32ce04c makes the text much longer, but I think that the consequences of email-related settings are very well defined. I hope that we won't have to revisit this later down the line.
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.
The sentence will be used for .... and, provided that it is not hidden, web-based Git operations
reads a little difficult to me. But I am not a native English speaker, so I can't comment on it (aka, no more option from my side).
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 don't think I can come up with a better combination of being accurate, easy to read and being transparent. I'm not a native speaker either, and we have to consider that many will use the software in this locale despite not being native speakers, so I'm definitely open to recommendations.
Asked all three of you for reviews because I either want a final confirmation that I addressed some comments correctly or because there have been a LOT of changes ever since the "Approval". I apologize in advance for the duplicated effort. I tried my best not to address the parameter problems for the moment, as that seems like an entirely separate issue that is out of my reach as a contributor. |
options/locale/locale_en-US.ini
Outdated
@@ -3369,17 +3372,17 @@ settings.delete.success = The package has been deleted. | |||
settings.delete.error = Failed to delete the package. | |||
owner.settings.cargo.title = Cargo Registry Index | |||
owner.settings.cargo.initialize = Initialize Index | |||
owner.settings.cargo.initialize.description = To use the Cargo registry a special index git repository is needed. Here you can (re)create it with the required config. | |||
owner.settings.cargo.initialize.description = A special index Git repository is needed to use the Cargo registry. Using this option will (re-)create it with all required configurations. |
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.
Isn't configuration
a word like sheep
or fish
whose plural is its singular?
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 is correct. Bear in mind that I work on this PR very late at night so that I can actually handle the mundane-ness of it, which is good for progress but still results in many little errors. I'll fix 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.
Hm,
- https://www.merriam-webster.com/dictionary/configuration (
configurations
example used) - https://www.wordhippo.com/what-is/the-plural-of/configuration.html
I think we are both right, but it may be the case that using plural in the first place makes the idea that is meant to be conveyed here too inaccurate.
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 tried something else here: faf68dc
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.
Thank you for inviting me to review, while I am not an English native speaker, I think people understand English better could help.
I think it's default behaviour of crowdin to invalidate existing translation when the primary value changes. This is this option which by default is not set, so I assume we don't set it (but I can't be sure because without a |
Can we merge this? We could infinitely continue adding stuff here if we wanted, but I think we should merge |
* upstream/main: [skip ci] Updated translations via Crowdin fix artifact merging chunks path with correct slash on Windows (go-gitea#26400) Use flex classes in package settings (go-gitea#26314) Improve multiple strings in en-US locale (go-gitea#26213) Refactor "editorconfig" (go-gitea#26391) fix generated source URL on rendered files (go-gitea#26364) Remove unnecessary template helper DisableGravatar (go-gitea#26386)
I kept sending pull requests that consisted of one-line changes. It's time to
settle this once and for all. (Maybe.)
setting better, so that the user does not have to consult
the docs.
interchangeably, e.g.
e-mail
andemail
.e.g.
Confirm Password
instead ofRe-Type Password
.(e.g. cancelled -> canceled)