[BACK]Return to Notes CVS log [TXT][DIR] Up to [cvs.NetBSD.org] / src / games / fortune

File: [cvs.NetBSD.org] / src / games / fortune / Notes (download)

Revision 1.2, Thu Mar 23 08:28:26 1995 UTC (26 years, 10 months ago) by cgd
Branch: MAIN
CVS Tags: yamt-pf42-baseX, yamt-pf42-base4, yamt-pf42-base3, yamt-pf42-base2, yamt-pf42-base, yamt-pf42, yamt-pagecache-tag8, yamt-pagecache-base9, yamt-pagecache-base8, yamt-pagecache-base7, yamt-pagecache-base6, yamt-pagecache-base5, yamt-pagecache-base4, yamt-pagecache-base3, yamt-pagecache-base2, yamt-pagecache-base, yamt-pagecache, wrstuden-revivesa-base-3, wrstuden-revivesa-base-2, wrstuden-revivesa-base-1, wrstuden-revivesa-base, wrstuden-revivesa, wrstuden-fixsa-newbase, wrstuden-fixsa-base-1, wrstuden-fixsa-base, wrstuden-fixsa, wrstuden-devbsize-base, wrstuden-devbsize-19991221, wrstuden-devbsize, tls-maxphys-base, tls-maxphys, tls-earlyentropy-base, tls-earlyentropy, riastradh-xf86-video-intel-2-7-1-pre-2-21-15, riastradh-drm2-base3, riastradh-drm2-base2, riastradh-drm2-base1, riastradh-drm2-base, riastradh-drm2, prg-localcount2-base3, prg-localcount2-base2, prg-localcount2-base1, prg-localcount2-base, prg-localcount2, phil-wifi-base, phil-wifi-20200421, phil-wifi-20200411, phil-wifi-20200406, phil-wifi-20191119, phil-wifi-20190609, phil-wifi, pgoyette-localcount-base, pgoyette-localcount-20170426, pgoyette-localcount-20170320, pgoyette-localcount-20170107, pgoyette-localcount-20161104, pgoyette-localcount-20160806, pgoyette-localcount-20160726, pgoyette-localcount, pgoyette-compat-merge-20190127, pgoyette-compat-base, pgoyette-compat-20190127, pgoyette-compat-20190118, pgoyette-compat-1226, pgoyette-compat-1126, pgoyette-compat-1020, pgoyette-compat-0930, pgoyette-compat-0906, pgoyette-compat-0728, pgoyette-compat-0625, pgoyette-compat-0521, pgoyette-compat-0502, pgoyette-compat-0422, pgoyette-compat-0415, pgoyette-compat-0407, pgoyette-compat-0330, pgoyette-compat-0322, pgoyette-compat-0315, pgoyette-compat, perseant-stdc-iso10646-base, perseant-stdc-iso10646, netbsd-9-base, netbsd-9-2-RELEASE, netbsd-9-1-RELEASE, netbsd-9-0-RELEASE, netbsd-9-0-RC2, netbsd-9-0-RC1, netbsd-9, netbsd-8-base, netbsd-8-2-RELEASE, netbsd-8-1-RELEASE, netbsd-8-1-RC1, netbsd-8-0-RELEASE, netbsd-8-0-RC2, netbsd-8-0-RC1, netbsd-8, netbsd-7-nhusb-base-20170116, netbsd-7-nhusb-base, netbsd-7-nhusb, netbsd-7-base, netbsd-7-2-RELEASE, netbsd-7-1-RELEASE, netbsd-7-1-RC2, netbsd-7-1-RC1, netbsd-7-1-2-RELEASE, netbsd-7-1-1-RELEASE, netbsd-7-1, netbsd-7-0-RELEASE, netbsd-7-0-RC3, netbsd-7-0-RC2, netbsd-7-0-RC1, netbsd-7-0-2-RELEASE, netbsd-7-0-1-RELEASE, netbsd-7-0, netbsd-7, netbsd-6-base, netbsd-6-1-RELEASE, netbsd-6-1-RC4, netbsd-6-1-RC3, netbsd-6-1-RC2, netbsd-6-1-RC1, netbsd-6-1-5-RELEASE, netbsd-6-1-4-RELEASE, netbsd-6-1-3-RELEASE, netbsd-6-1-2-RELEASE, netbsd-6-1-1-RELEASE, netbsd-6-1, netbsd-6-0-RELEASE, netbsd-6-0-RC2, netbsd-6-0-RC1, netbsd-6-0-6-RELEASE, netbsd-6-0-5-RELEASE, netbsd-6-0-4-RELEASE, netbsd-6-0-3-RELEASE, netbsd-6-0-2-RELEASE, netbsd-6-0-1-RELEASE, netbsd-6-0, netbsd-6, netbsd-5-base, netbsd-5-2-RELEASE, netbsd-5-2-RC1, netbsd-5-2-3-RELEASE, netbsd-5-2-2-RELEASE, netbsd-5-2-1-RELEASE, netbsd-5-2, netbsd-5-1-RELEASE, netbsd-5-1-RC4, netbsd-5-1-RC3, netbsd-5-1-RC2, netbsd-5-1-RC1, netbsd-5-1-5-RELEASE, netbsd-5-1-4-RELEASE, netbsd-5-1-3-RELEASE, netbsd-5-1-2-RELEASE, netbsd-5-1-1-RELEASE, netbsd-5-1, netbsd-5-0-RELEASE, netbsd-5-0-RC4, netbsd-5-0-RC3, netbsd-5-0-RC2, netbsd-5-0-RC1, netbsd-5-0-2-RELEASE, netbsd-5-0-1-RELEASE, netbsd-5-0, netbsd-5, netbsd-4-base, netbsd-4-0-RELEASE, netbsd-4-0-RC5, netbsd-4-0-RC4, netbsd-4-0-RC3, netbsd-4-0-RC2, netbsd-4-0-RC1, netbsd-4-0-1-RELEASE, netbsd-4-0, netbsd-4, netbsd-3-base, netbsd-3-1-RELEASE, netbsd-3-1-RC4, netbsd-3-1-RC3, netbsd-3-1-RC2, netbsd-3-1-RC1, netbsd-3-1-1-RELEASE, netbsd-3-1, netbsd-3-0-RELEASE, netbsd-3-0-RC6, netbsd-3-0-RC5, netbsd-3-0-RC4, netbsd-3-0-RC3, netbsd-3-0-RC2, netbsd-3-0-RC1, netbsd-3-0-3-RELEASE, netbsd-3-0-2-RELEASE, netbsd-3-0-1-RELEASE, netbsd-3-0, netbsd-3, netbsd-2-base, netbsd-2-1-RELEASE, netbsd-2-1-RC6, netbsd-2-1-RC5, netbsd-2-1-RC4, netbsd-2-1-RC3, netbsd-2-1-RC2, netbsd-2-1-RC1, netbsd-2-1, netbsd-2-0-base, netbsd-2-0-RELEASE, netbsd-2-0-RC5, netbsd-2-0-RC4, netbsd-2-0-RC3, netbsd-2-0-RC2, netbsd-2-0-RC1, netbsd-2-0-3-RELEASE, netbsd-2-0-2-RELEASE, netbsd-2-0-1-RELEASE, netbsd-2-0, netbsd-2, netbsd-1-6-base, netbsd-1-6-RELEASE, netbsd-1-6-RC3, netbsd-1-6-RC2, netbsd-1-6-RC1, netbsd-1-6-PATCH002-RELEASE, netbsd-1-6-PATCH002-RC4, netbsd-1-6-PATCH002-RC3, netbsd-1-6-PATCH002-RC2, netbsd-1-6-PATCH002-RC1, netbsd-1-6-PATCH002, netbsd-1-6-PATCH001-RELEASE, netbsd-1-6-PATCH001-RC3, netbsd-1-6-PATCH001-RC2, netbsd-1-6-PATCH001-RC1, netbsd-1-6-PATCH001, netbsd-1-6, netbsd-1-5-base, netbsd-1-5-RELEASE, netbsd-1-5-PATCH003, netbsd-1-5-PATCH002, netbsd-1-5-PATCH001, netbsd-1-5-BETA2, netbsd-1-5-BETA, netbsd-1-5-ALPHA2, netbsd-1-5, netbsd-1-4-base, netbsd-1-4-RELEASE, netbsd-1-4-PATCH003, netbsd-1-4-PATCH002, netbsd-1-4-PATCH001, netbsd-1-4, netbsd-1-3-base, netbsd-1-3-RELEASE, netbsd-1-3-PATCH003-CANDIDATE2, netbsd-1-3-PATCH003-CANDIDATE1, netbsd-1-3-PATCH003-CANDIDATE0, netbsd-1-3-PATCH003, netbsd-1-3-PATCH002, netbsd-1-3-PATCH001, netbsd-1-3-BETA, netbsd-1-3, netbsd-1-2-base, netbsd-1-2-RELEASE, netbsd-1-2-PATCH001, netbsd-1-2-BETA, netbsd-1-2, netbsd-1-1-base, netbsd-1-1-RELEASE, netbsd-1-1-PATCH001, netbsd-1-1, mjf-devfs2-base, mjf-devfs2, minoura-xpg4dl-base, minoura-xpg4dl, matt-premerge-20091211, matt-nb8-mediatek-base, matt-nb8-mediatek, matt-nb6-plus-nbase, matt-nb6-plus-base, matt-nb6-plus, matt-nb5-pq3-base, matt-nb5-pq3, matt-nb5-mips64-u2-k2-k4-k7-k8-k9, matt-nb5-mips64-u1-k1-k5, matt-nb5-mips64-premerge-20101231, matt-nb5-mips64-premerge-20091211, matt-nb5-mips64-k15, matt-nb5-mips64, matt-nb4-mips64-k7-u2a-k9b, matt-mips64-premerge-20101231, matt-mips64-base2, matt-mips64-base, matt-mips64, matt-armv6-prevmlocking, matt-armv6-nbase, matt-armv6-base, matt-armv6, localcount-20160914, keiichi-mipv6-base, keiichi-mipv6, jym-xensuspend-nbase, jym-xensuspend-base, jym-xensuspend, is-mlppp-base, is-mlppp, hpcarm-cleanup-nbase, hpcarm-cleanup-base, hpcarm-cleanup, fvdl_fs64_base, cube-autoconf-base, cube-autoconf, comdex-fall-1999-base, comdex-fall-1999, cjep_sun2x-base1, cjep_sun2x-base, cjep_sun2x, cjep_staticlib_x-base1, cjep_staticlib_x-base, cjep_staticlib_x, cherry-xenmp-base, cherry-xenmp, bouyer-socketcan-base1, bouyer-socketcan-base, bouyer-socketcan, bouyer-quota2-nbase, bouyer-quota2-base, bouyer-quota2, agc-symver-base, agc-symver, abandoned-netbsd-4-base, abandoned-netbsd-4, HEAD
Changes since 1.1: +3 -0 lines

merge with Lite, new RCS id conventions, etc.

#	$NetBSD: Notes,v 1.2 1995/03/23 08:28:26 cgd Exp $
#	@(#)Notes	8.1 (Berkeley) 5/31/93

	The fortunes contained in the fortune database have been collected
	haphazardly from a cacophony of sources, in number so huge it
	boggles the mind.  It is impossible to do any meaningful quality
	control on attributions, or lack thereof, or exactness of the quote.
	Since this database is not used for profit, and since entire works
	are not published, it falls under fair use, as we understand it.
	However, if any half-assed idiot decides to make a profit off of
	this, they will need to double check it all, and nobody not involved
	of such an effort makes any warranty that anything in the database
	bears any relation to the real world of literature, law, or other

	By default, fortune retrieves its fortune files from the directory
/usr/share/games/fortune.  A fortune file has two parts: the source file
(which contains the fortunes themselves) and the data file which describes
the fortunes.  The data fil always has the same name as the fortune file
with the string ".dat" concatenated, i.e. "fort" is the standard fortune
database, and "fort.dat" is the data file which describes it.  See
strfile(8) for more information on creating the data files.
	Fortunes are split into potentially offensive and not potentially
offensive parts.  The offensive version of a file has the same name as the
non-offensive version with "-o" concatenated, i.e. "fort" is the standard
fortune database, and "fort-o" is the standard offensive database.  The
fortune program automatically assumes that any file with a name ending in
"-o" is potentially offensive, and should therefore only be displayed if
explicitly requested, either with the -o option or by specifying a file name
on the command line.
	Potentially offensive fortune files should NEVER be maintained in
clear text on the system.  They are rotated (see caesar(6)) 13 positions.
To create a new, potentially offensive database, use caesar to rotate it,
and then create its data file with the -x option to strfile(8).  The fortune
program automatically decrypts the text when it prints entries from such
	Anything which would not make it onto network prime time programming
(or which would only be broadcast if some discredited kind of guy said it)
MUST be in the potentially offensive database.  Fortunes containing any
explicit language (see George Carlin's recent updated list) MUST be in the
potentially offensive database.  Political and religious opinions are often
sequestered in the potentially offensive section as well.  Anything which
assumes as a world view blatantly racist, mysogynist (sexist), or homophobic
ideas should not be in either, since they are not really funny unless *you*
are racist, mysogynist, or homophobic.
	The point of this is that people have should have a reasonable
expectation that, should they just run "fortune", they will not be offended.
We know that some people take offense at anything, but normal people do have
opinions, too, and have a right not to have their sensibilities offended by
a program which is supposed to be entertaining.  People who run "fortune
-o" or "fortune -a" are saying, in effect, that they are willing to have
their sensibilities tweaked.  However, they should not have their personal
worth seriously (i.e., not in jest) assaulted.  Jokes which depend for their
humor on racist, mysogynist, or homophobic stereotypes *do* seriously
assault individual personal worth, and in an general entertainment medium
we should be able to get by without it.

	This file describes the format for fortunes in the database.  This
is done in detail to make it easier to keep track of things.  Any rule given
here may be broken to make a better joke.

[All examples are indented by one tab stop -- KCRCA]

Numbers should be given in parentheses, e.g.,

	(1)	Everything depends.
	(2)	Nothing is always.
	(3)	Everything is sometimes.

Attributions are two tab stops, followed by two hyphens, followed by a
space, followed by the attribution, and are *not* preceded by blank
lines.  Book, journal, movie, and all other titles are in quotes, e.g.,

	$100 invested at 7% interest for 100 years will become $100,000, at
	which time it will be worth absolutely nothing.
			-- Lazarus Long, "Time Enough for Love"

Attributions which do not fit on one (72 char) line should be continued
on a line which lines up below the first text of the attribution, e.g.,

			-- A very long attribution which might not fit on one
			   line, "Ken Arnold's Stupid Sayings"

Single paragraph fortunes are in left justified (non-indented) paragraphs
unless they fall into another category listed below (see example above).
Longer fortunes should also be in left justified paragraphs, but if this
makes it too long, try indented paragraphs, with indentations of either one
tab stop or 5 chars.  Indentations of less than 5 are too hard to read.

Laws have the title left justified and capitalized, followed by a colon,
with all the text of the law itself indented one tab stop, initially
capitalized, e.g.,

	A Law of Computer Programming:
		Make it possible for programmers to write in English and
		you will find the programmers cannot write in English.

Limericks are indented as follows, all lines capitalized:

	A computer, to print out a fact,
	Will divide, multiply, and subtract.
		But this output can be
		No more than debris,
	If the input was short of exact.

Accents precede the letter they are over, e.g., "`^He" for e with a grave
accent.  Underlining is done on a word-by-word basis, with the underlines
preceding the word, e.g., "__^H^Hhi ____^H^H^H^Hthere".

No fortune should run beyond 72 characters on a single line without good
justification (er, no pun intended).  And no right margin justification,
either.  Sorry.  For BSD people, there is a program called "fmt" which can
make this kind of formatting easier.

Definitions are given with the word or phrase left justified, followed by
the part of speech (if appropriate) and a colon.  The definition starts
indented by one tab stop, with subsequent lines left justified, e.g.,

	Afternoon, n.:
		That part of the day we spend worrying about how we wasted
	the morning.

Quotes are sometimes put around statements which are funnier or make more
sense if they are understood as being spoken, rather than written,
communication, e.g.,

	"All my friends and I are crazy.  That's the only thing that
	keeps us sane."

Ellipses are always surrounded by spaces, except when next to punctuation,
and are three dots long.

	"... all the modern inconveniences ..."
			-- Mark Twain

Human initials always have spaces after the periods, e.g, "P. T.  Barnum",
not "P.T. Barnum".  However, "P.T.A.", not "P. T. A.".

All fortunes should be attributed, but if and only if they are original with
somebody.  Many people have said things that are folk sayings (i.e., are
common among the folk (i.e., us common slobs)).  There is nothing wrong with
this, of course, but such statements should not be attributed to individuals
who did not invent them.

Horoscopes should have the sign indented by one tab stop, followed by the
dates of the sign, with the text left justified below it, e.g.,

		AQUARIUS (Jan 20 - Feb 18)
	You have an inventive mind and are inclined to be progressive.  You
	lie a great deal.  On the other hand, you are inclined to be
	careless and impractical, causing you to make the same mistakes over
	and over again.  People think you are stupid.

Single quotes should not be used except as quotes within quotes.  Not even
single quotes masquerading as double quotes are to be used, e.g., don't say
``hi there'' or `hi there' or 'hi there', but "hi there".  However, you
*can* say "I said, `hi there'".

A long poem or song can be ordered as follows in order to make it fit on a
screen (fortunes should be 19 lines or less if at all possible) (numbers
here are stanza numbers):

	11111111111111111111			22222222222222222222
	11111111111111111111			22222222222222222222
	33333333333333333333			22222222222222222222
	33333333333333333333			44444444444444444444
	33333333333333333333			44444444444444444444