#22716: The unique error message uses incorrect grammar
-------------------------------+--------------------------------------
     Reporter:  jdufresne      |                    Owner:  nobody
         Type:  Uncategorized  |                   Status:  closed
    Component:  Uncategorized  |                  Version:  1.6
     Severity:  Normal         |               Resolution:  invalid
     Keywords:                 |             Triage Stage:  Unreviewed
    Has patch:  0              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+--------------------------------------

Comment (by EvilDMP):

 Replying to [comment:2 jdufresne]:

 > I admit, I do no have perfect grammar. Nor do I have any particular
 style guide memorized. But, this usage is not a proper noun. I believe it
 is incorrect to claim it is. The current capitalization just looks odd to
 me as a native English speaker. Think about other ways you could use a
 model (person) and field name (first name):

 > * Please enter your First name. (capitalization looks odd)
 > * What is your First name? (capitalization looks odd)
 > * Person with First name already exists. (capitalization looks odd)
 > * Search by First name. (capitalization looks odd)
 > * His First name is "Jon". (capitalization looks odd)

 It's not a proper noun, it's ''something like a proper noun''. It's a
 technical term in the system.

 Your examples above are not all the same as this error message. When we
 refer to a field or its contents in writing, it's perfectly normal to
 capitalise the name of the field. The same goes for the names of menus,
 buttons and so on.

 > If you want to emphasize the field name in the sentence, why not simply
 do that?

 I think that would be useful as well.

 There is a problem with "Person with this Email already exists.", which is
 that it's an awkward locution that doesn't adequately convey what the
 nature of the problem. Even "A '''Person''' with this '''Email address'''
 already exists." would be an improvement (less awkward) but still leaves
 too much work to the user to figure out what the problem is and what they
 should do about it.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/22716#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.dd52bdc6e4d4e652793a2299e8d86b50%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to