RE: "makefiles" vs. "Makefiles" vs. "make files"

Subject: RE: "makefiles" vs. "Makefiles" vs. "make files"
From: Lesli Ritchie <Lesli -dot- Ritchie -at- mediware -dot- com>
To: Monique Semp <monique -dot- semp -at- earthlink -dot- net>, TechWR-L <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 20 Nov 2015 13:44:36 +0000

Hi Monique,

According to the Microsoft Manual of Style it's makefiles. (lower case, one word)

Lesli

-----Original Message-----
From: techwr-l-bounces+lesli -dot- ritchie=mediware -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+lesli -dot- ritchie=mediware -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of Monique Semp
Sent: Thursday, November 19, 2015 10:00 PM
To: TechWR-L
Subject: "makefiles" vs. "Makefiles" vs. "make files"

Hello, TechWR-L-ers,

So for building instructions that are applicable to a huge variety of operating systems (and so they wonât all use the usual Linux make utility, but they will all use the supplied Makefile.<os> or Makefile.<product> pre-configured make files), how would it be best to refer to the group of supplied make files:

* makefiles
* Makefiles
* make files

The last (âmake filesâ) is certainly the most generic. But given that the actual filenames are all âMakefile.<something>â, I can see the logic for referring to them as âMakefilesâ. But if the reference isnât at the start of the sentence, the upper-case makes it appear more as a proper noun, which isnât what I want to convey. (Although the actual Make utility is always uppercase, as in this Wikipedia article: https://en.wikipedia.org/wiki/Make_(software). And this same article seems to use âmakefileâ, lowercase, to refer to these things generically. So thatâs what Iâm leaning toward.)

Thoughts?

-Monique
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as Lesli -dot- Ritchie -at- mediware -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives


References:
"makefiles" vs. "Makefiles" vs. "make files": From: Monique Semp

Previous by Author: Re: FM (2015) text insets - no track text edits when imported...
Next by Author: Re: FrameMaker does NOT update links . . . .
Previous by Thread: Re: "makefiles" vs. "Makefiles" vs. "make files"
Next by Thread: Re: "makefiles" vs. "Makefiles" vs. "make files"


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads