-
Notifications
You must be signed in to change notification settings - Fork 0
Sentence case vs Title Case #27
Comments
@peterdesmet sentence case TL;DR |
Thanks, I agree, it is indeed simpler. TDWG standard names will remain capitalized:
But what about the following terms:
My preference would be that those are lowercase. E.g. in a title or sentence:
Or as sentence case menu items:
|
@peterdesmet I agree that Standard names should remain capitalized. I would suggest the following (I have not made things 3 deep, but could see advantages to this in some cases). Still noodling here, but... About
Executive Committee†
Policies and Statements
Process and Procedures
†Technically, the Exec includes FSc (as well as Regional Reps, which might be encouraged to have more of a presence on the website). However, there are a bunch of historical background things currently as cards hanging off of the Exec page, which we want to be able to preserve under a history (likely its own new section). †† should this be "Branding Guidelines" with the logos as resources? |
Thanks for the suggestion on the about menu.
I would have all bolded letters above be lowercase. |
@peterdesmet yes it was intentional because these are proper names for groups and policies. I don't think that these named entities should be lower case because we are referring to a particular entity/proper name (TDWG Executive Committee) not just any old exec. These are different from other sorts of titles for headings, to me. If I were to refer to the Executive Committee (meaning TDWG Exec) or the Program Committee (not the concept of a program committee), there is a difference. It is harder for the reader to know if you don't capitalize these. The practice of putting everything e e cummings is not a comfortable space for me. |
+1 for capitalizing proper nouns (names). The problem I have is determining what is part of the name; e.g.,
On Gail's menu items and grouping: Overall, I like the grouping and order; would just suggest that "Contributing to website" and "Logos" aren't the same kind of Process and Procedures as the "TDWG Process" and "Review Manager Guidelines". Those are names of documents. Also, if Steve Baskauf's suggestion is developed, "Procedures" might become a top-level menu item. I don't think "Incorporation and Status" is the name of something, so leave status lowercase, right? |
I agree with Stan that we should define how to capitalize those groups ( I would not capitalize roles and policies, as that can get unwieldy, so I prefer In the menu Gail suggests, I would thus write (capitalizion changes only):
|
@peterdesmet I am OK with the capitalization changes you list just above and the idea of having a clear list of how groups should be capitalized. I think that if you refer to a specific person in a role, that this should be capitalized, however (e.g., Ely Wallis is Deputy Chair of TDWG; Holly Little is Representative for North America). Similarly, referring to TDWG's Code of Conduct, I would capitalize it because it is not just a code of conduct but our Code of Conduct. You mention that "TDWG process" is also the title of an IG, but this document is an output from that IG. You could change the wording to TDWG framework, but I think that is more opaque to the reader. |
To my understanding, the "TDWG Process" is a named thing, like our
Constitution, so Process should be capitalized.
…On Fri, Nov 25, 2022 at 3:31 PM Peter Desmet ***@***.***> wrote:
I agree with Stan that we should define how to capitalize those groups (Functional
Subcommittee vs Functional subcommittee, Interest Group vs Interest group).
I think in most cases we have chosen to capitalize both, and we could stick
to that, but we should have a clear list.
I would not capitalize roles and policies, as that can get unwieldy, so I
prefer deputy chair, convener, representative, code of conduct. The
context is almost always clear in sentences.
In the menu Gail suggests, I would thus write (capitalizion changes only):
Incorporation and status
Policies and statements
Terms of use
Code of conduct
Diversity and inclusion
Liability disclaimer and release - COVID-19
Process and procedures
TDWG process (arguable, since also IG?)
Review manager guidelines
—
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACKZUDIW3JAIZ36ORLNZLA3WKFD6BANCNFSM6AAAAAASLHAIMA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Note: my preference would be to not capitalize roles, as I find it rather unwieldy to have:
But I can adapt. 😄 Most of all, can you (@gkampmeier or @stanblum) provide a list of words that should be consistently capitalized? That should help me and others in reviewing/contributing content for the website. |
@peterdesmet @stanblum I've started a Google doc in the TDWG docs > Guidelines > Capitalizations Guidelines - TDWG Website. Suggestions for how it should be organized are welcomed. |
I have tried to stick to the rules in the document:
|
@gkampmeier @stanblum What is the recommendation for titles on the TDWG website? Titles are page titles, page headings (h2, h3), and menu items.
Currently a mix of the two is used. See https://medium.com/@jsaito/making-a-case-for-letter-case-19d09f653c98 for the benefits of each.
The text was updated successfully, but these errors were encountered: