Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-doc-dev] Capitalization

I do not think we should capitalize "View", "Menu" etc.  In the UI, we 
generally do not capitalize such terms except where dictated by menu and 
title casing rules).
E.g. see the Perspectives pref page.

Also, the title of the view is just e.g. "Tasks".  Adding a capitalized 
"View" next to it in the doc suggests that the name shown in the UI is 
"Tasks View".

The Nick human





Kevin McGuire/Ottawa/IBM@IBMCA
Sent by: platform-doc-dev-admin@xxxxxxxxxxx
03/18/2003 02:08 PM
Please respond to platform-doc-dev

 
        To:     platform-doc-dev@xxxxxxxxxxx
        cc: 
        Subject:        Re: [platform-doc-dev] Capitalization




It would be good to have a style guide with these points captured.  It 
doesn't have to be extensive, just a place to keep such decisions where 
people can refer back to them. 

I actually don't know if it should be "Tasks View" or "Tasks view", but 
I'm happy with you just picking one since it means we can achieve some 
consistency. 





John Arthorne/Ottawa/IBM@IBMCA 
Sent by: platform-doc-dev-admin@xxxxxxxxxxx 
03/18/2003 01:44 PM 
Please respond to platform-doc-dev 
        
        To:        platform-doc-dev@xxxxxxxxxxx 
        cc:         
        Subject:        [platform-doc-dev] Capitalization 




Another area where there is inconsistency is in capitalization.  Most 
section titles in the table of contents and headings within pages are 
sentence case, but some aren't.  I've been converting everything to 
sentence casing wherever I've seen inconsistencies, but I wanted to make 
sure we agree on it. 

A much trickier case is proper nouns.  I believe things like "Tasks View", 
"File Menu", and "Export Wizard" are all proper nouns, and as such both 
words should always be capitalized.  The documentation more commonly uses 
"Tasks view", "File menu", and "Export wizard", but I think this is not 
correct.  Correct me if I'm wrong here, but unless I hear otherwise I'll 
correct these problems where I see them. 





Back to the top