On Feb 16, 2015 10:35 AM, "Eric Firing" <ef...@ha...> wrote: > > On 2015年02月16日 8:16 AM, Benjamin Root wrote: > > I am in the final rounds of edits for my book and a question has come up > > between me and the editors. When should the matplotlib be capitalized? > > > > 1) never > > 2) mostly never (even in the beginning of a sentence), except when used > > in a title > > 3) usually never, except at the beginning of a sentence and in titles > > 4) capitalize when referring to the project, not capitalized when > > referring to the package > > 5) usually capitalize like a proper noun except in code examples > > > > Thoughts? > > Ben Root > > Do numpy and scipy have a consistent policy that could be used as a > model? Not that I'm aware of. I tend to write "numpy" in prose (somewhere in the 1-3 range in Ben's terminology) because that's what I write in code. But as I recently discovered, when writing for a general audience (e.g., "people reading your job application") it is crucial to write NumPy so that it doesn't look like it's pronounced nump-ee. :-) Matplotlib cleverly avoids that particular problem through its surfeit of stops, but if we want a general cross-project rule then it might be a hint. -n