Money Quote :
It would be nice to reconcile everything, but changing a core module name, and breaking a chunk of contributions, is harder than changing the UI label.
I hope that in a near future all of the good all technology wordiness is "invisible" at the level of the end-user interface. So focusing on UI hopefully will bring better ways for "masking" the complexity. / liza -- Liza Sabater, Publisher culturekitchen.com dailygotham.com AIM cultkitdiva MOB 646.552.7365 --------- Original Message -------- From: development@drupal.org To: development@drupal.org <development@drupal.org> Subject: Re: [development] Taxonomy labeling changes Date: 14/11/07 10:09
On Nov 14, 2007 12:27 PM, Michelle Cox <mcox@charter.net> wrote: > On 11/14/2007 2:09:58 PM, Neil Drumm (drumm@delocalizedham.com) wrote: > >Avoid use of "Taxonomy" in the UI. The overall system, despite the > >module name, is "Categories." > > I took a quick peek on my site and the only place I see it called > "Categories" is on the menu label and the title of this page: > ?=admin/content/taxonomy . Note the URL to that page. Seems to me like the > overall system is "Taxonomy" with a half attempt to change it to > "Categories" that failed. What's wrong with rolling it back while we think > about what best to call it in 7?
And the heading of the fieldset on node/add/{content type with more than one vocabulary}. The name of the overall system simply is not used a whole lot. This naming system applies for Drupal 4.5 through 5, and may be changed for Drupal 6.
We have quite a few precedents for using different labels in UI from what we use in the API or URLs: - node is content - path is URL alias - watchdog is log These differences happen and are okay. It would be nice to reconcile everything, but changing a core module name, and breaking a chunk of contributions, is harder than changing the UI label.
-- Neil Drumm http://delocalizedham.com
________________________________________________ Message sent using UebiMiau 2.7.10