#3827: Correct Plural Form for words that end in "y".
-------------------------------------------+--------------------------------
          Reporter:  [EMAIL PROTECTED]  |         Owner:  adrian
            Status:  reopened              |     Milestone:        
         Component:  django-admin.py       |       Version:  SVN   
        Resolution:                        |      Keywords:        
             Stage:  Unreviewed            |     Has_patch:  0     
        Needs_docs:  0                     |   Needs_tests:  0     
Needs_better_patch:  0                     |  
-------------------------------------------+--------------------------------
Changes (by mikeblake):

  * status:  closed => reopened
  * version:  0.96 => SVN
  * resolution:  wontfix =>

Comment:

 Could this be re-investigated on the grounds that:

 a) There's not much documentation on the verbose_name_plural setting (at
 least none that's obvious under Model or admin).

 b) Most frameworks tend to append ies instead of ys (CakePHP, Ruby etc) as
 a matter of simplicity for the developer.

 c) English is the de-facto standard, otherwise we wouldn't be using an
 automatic plural 's' in the first place. Heck, the entire framework is
 english based - may as well do it right.

 d) Non-English speakers can utilise the verbose_name_plural if required.

 e) Making the development process 'easier', and less trawling through
 search engines, would certainly help the framework's credibility.

 f) It will be harder to make a 'significant' change like this later -
 better to do it before it's too late.


 I respect the comment made by Adrian but it's more of a matter of
 convenience than annoying non-english speakers (which can be covered in
 point c).

 As an interim solution, to save the average developer time finding the
 'solution' to this problem, could verbose_name_plural be explained more
 evidently in the documentation or by the manage scripts when creating new
 models?

 Would it be possible to have a more permanent fix in place, if my above
 points are agreed to, before version 1.0 to limit future incompatability?

-- 
Ticket URL: <http://code.djangoproject.com/ticket/3827#comment:2>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to