Model and form fields should have a translated verbose_name/label #4753
Description
Is your feature request related to a problem? Please describe.
Most model fields do not define a verbose_name (though a few do), which means they appear untranslated if they somehow end up displayed on a page (for example via a ModelForm). The same goes for form fields and their label.
Describe the solution you'd like
I would suggest adding an explicit verbose_name for all model fields, and a label for all form fields, and if possible a linter rule that prevents new untranslated fields from being added to the codebase.
Priority
- Medium (slowing you down)
Affected roles
Arguably all roles are affected, but this is more of an issue for applicants who are the ones most likely to see those untranslated strings, and who might not know English.