-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Inconsistent history event names #9824
Comments
Consistently use noun + verb past. Fixes WeblateOrg#9824
Consistently use noun + verb past. Fixes WeblateOrg#9824
Consistently use noun + verb past. Fixes WeblateOrg#9824
#10135 tries to consolidate this, reviews welcome. |
Consistently use noun + verb past. Fixes WeblateOrg#9824
I have been confused by these inconsistent event names for a long time while translating. If #10135 is implemented (changing all these event names to noun + verb past participle, that is passive voice), is it still necessary to imply that was someone who did these events in translations? |
Typically there is someone who did the action. But there are also automated events (automatic translation) or actors outside Weblate (changes in the repository). |
Consistently use noun + verb past. Fixes WeblateOrg#9824
Consistently use noun + verb past. Fixes WeblateOrg#9824
Consistently use noun + verb past. Fixes WeblateOrg#9824
Consistently use noun + verb past. Fixes WeblateOrg#9824
Consistently use noun + verb past. Fixes #9824
Thank you for your report; the issue you have reported has just been fixed.
|
Describe the issue
The name of history events are inconsistent, see this section. Some examples:
They should be consistent like "Something happened" (noun + verb past):
I already tried
Steps to reproduce the behavior
Open this section
or
Open
/changes/browse/PROJECT/COMPONENT/
to see all events in the GUI.Expected behavior
No response
Screenshots
No response
Exception traceback
No response
How do you run Weblate?
weblate.org service
Weblate versions
No response
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: