It is quite difficult to try to sell something opensource to management when there is profanity (or other "unprofessional" wording) in the documentation. Personnally, I do not have a problem with them (my wetware filters work pretty well), but the old "be conservative in what you generate, and liberal in what you accept" axiom is appropriate here. If I am recommending something, I feel it should also reflect on how I would code as well.

A few examples of what I have taken into consideration when recommending OS / Free software:

• Emacs comes with a few man pages that I would be "professionally embarrased" to have my management find.
• NSIS has some minor stuff in its documentation that I would not want to release to our customers ("installer that doesn't suck"), and IIRC, some stuff that raised my filters.

I guess I would agree with one of the previous posts that states "not to put anything in your code you wouldn't want the customer to find."

My $0.02.

--MidLifeXis

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.