11.3Srillig# $NetBSD: Notes,v 1.3 2024/09/08 09:36:47 rillig Exp $ 21.2Scgd# @(#)Notes 8.1 (Berkeley) 5/31/93 31.2Scgd 41.1ScgdWarning: 51.1Scgd The fortunes contained in the fortune database have been collected 61.1Scgd haphazardly from a cacophony of sources, in number so huge it 71.1Scgd boggles the mind. It is impossible to do any meaningful quality 81.1Scgd control on attributions, or lack thereof, or exactness of the quote. 91.1Scgd Since this database is not used for profit, and since entire works 101.1Scgd are not published, it falls under fair use, as we understand it. 111.1Scgd However, if any half-assed idiot decides to make a profit off of 121.1Scgd this, they will need to double check it all, and nobody not involved 131.1Scgd of such an effort makes any warranty that anything in the database 141.1Scgd bears any relation to the real world of literature, law, or other 151.1Scgd bizzarrity. 161.1Scgd 171.1Scgd==> GENERAL INFORMATION 181.1Scgd By default, fortune retrieves its fortune files from the directory 191.1Scgd/usr/share/games/fortune. A fortune file has two parts: the source file 201.1Scgd(which contains the fortunes themselves) and the data file which describes 211.1Scgdthe fortunes. The data fil always has the same name as the fortune file 221.1Scgdwith the string ".dat" concatenated, i.e. "fort" is the standard fortune 231.1Scgddatabase, and "fort.dat" is the data file which describes it. See 241.1Scgdstrfile(8) for more information on creating the data files. 251.1Scgd Fortunes are split into potentially offensive and not potentially 261.1Scgdoffensive parts. The offensive version of a file has the same name as the 271.1Scgdnon-offensive version with "-o" concatenated, i.e. "fort" is the standard 281.1Scgdfortune database, and "fort-o" is the standard offensive database. The 291.1Scgdfortune program automatically assumes that any file with a name ending in 301.1Scgd"-o" is potentially offensive, and should therefore only be displayed if 311.1Scgdexplicitly requested, either with the -o option or by specifying a file name 321.1Scgdon the command line. 331.1Scgd Potentially offensive fortune files should NEVER be maintained in 341.1Scgdclear text on the system. They are rotated (see caesar(6)) 13 positions. 351.1ScgdTo create a new, potentially offensive database, use caesar to rotate it, 361.1Scgdand then create its data file with the -x option to strfile(8). The fortune 371.1Scgdprogram automatically decrypts the text when it prints entries from such 381.1Scgddatabases. 391.1Scgd Anything which would not make it onto network prime time programming 401.1Scgd(or which would only be broadcast if some discredited kind of guy said it) 411.1ScgdMUST be in the potentially offensive database. Fortunes containing any 421.1Scgdexplicit language (see George Carlin's recent updated list) MUST be in the 431.1Scgdpotentially offensive database. Political and religious opinions are often 441.1Scgdsequestered in the potentially offensive section as well. Anything which 451.1Scgdassumes as a world view blatantly racist, mysogynist (sexist), or homophobic 461.1Scgdideas should not be in either, since they are not really funny unless *you* 471.1Scgdare racist, mysogynist, or homophobic. 481.1Scgd The point of this is that people have should have a reasonable 491.1Scgdexpectation that, should they just run "fortune", they will not be offended. 501.1ScgdWe know that some people take offense at anything, but normal people do have 511.1Scgdopinions, too, and have a right not to have their sensibilities offended by 521.1Scgda program which is supposed to be entertaining. People who run "fortune 531.1Scgd-o" or "fortune -a" are saying, in effect, that they are willing to have 541.1Scgdtheir sensibilities tweaked. However, they should not have their personal 551.1Scgdworth seriously (i.e., not in jest) assaulted. Jokes which depend for their 561.1Scgdhumor on racist, mysogynist, or homophobic stereotypes *do* seriously 571.3Srilligassault individual personal worth, and in a general entertainment medium 581.1Scgdwe should be able to get by without it. 591.1Scgd 601.1Scgd==> FORMATTING 611.1Scgd This file describes the format for fortunes in the database. This 621.1Scgdis done in detail to make it easier to keep track of things. Any rule given 631.1Scgdhere may be broken to make a better joke. 641.1Scgd 651.1Scgd[All examples are indented by one tab stop -- KCRCA] 661.1Scgd 671.1ScgdNumbers should be given in parentheses, e.g., 681.1Scgd 691.1Scgd (1) Everything depends. 701.1Scgd (2) Nothing is always. 711.1Scgd (3) Everything is sometimes. 721.1Scgd 731.1ScgdAttributions are two tab stops, followed by two hyphens, followed by a 741.1Scgdspace, followed by the attribution, and are *not* preceded by blank 751.1Scgdlines. Book, journal, movie, and all other titles are in quotes, e.g., 761.1Scgd 771.1Scgd $100 invested at 7% interest for 100 years will become $100,000, at 781.1Scgd which time it will be worth absolutely nothing. 791.1Scgd -- Lazarus Long, "Time Enough for Love" 801.1Scgd 811.1ScgdAttributions which do not fit on one (72 char) line should be continued 821.1Scgdon a line which lines up below the first text of the attribution, e.g., 831.1Scgd 841.1Scgd -- A very long attribution which might not fit on one 851.1Scgd line, "Ken Arnold's Stupid Sayings" 861.1Scgd 871.1ScgdSingle paragraph fortunes are in left justified (non-indented) paragraphs 881.1Scgdunless they fall into another category listed below (see example above). 891.1ScgdLonger fortunes should also be in left justified paragraphs, but if this 901.1Scgdmakes it too long, try indented paragraphs, with indentations of either one 911.1Scgdtab stop or 5 chars. Indentations of less than 5 are too hard to read. 921.1Scgd 931.1ScgdLaws have the title left justified and capitalized, followed by a colon, 941.1Scgdwith all the text of the law itself indented one tab stop, initially 951.1Scgdcapitalized, e.g., 961.1Scgd 971.1Scgd A Law of Computer Programming: 981.1Scgd Make it possible for programmers to write in English and 991.1Scgd you will find the programmers cannot write in English. 1001.1Scgd 1011.1ScgdLimericks are indented as follows, all lines capitalized: 1021.1Scgd 1031.1Scgd A computer, to print out a fact, 1041.1Scgd Will divide, multiply, and subtract. 1051.1Scgd But this output can be 1061.1Scgd No more than debris, 1071.1Scgd If the input was short of exact. 1081.1Scgd 1091.1ScgdAccents precede the letter they are over, e.g., "`^He" for e with a grave 1101.1Scgdaccent. Underlining is done on a word-by-word basis, with the underlines 1111.1Scgdpreceding the word, e.g., "__^H^Hhi ____^H^H^H^Hthere". 1121.1Scgd 1131.1ScgdNo fortune should run beyond 72 characters on a single line without good 1141.1Scgdjustification (er, no pun intended). And no right margin justification, 1151.1Scgdeither. Sorry. For BSD people, there is a program called "fmt" which can 1161.1Scgdmake this kind of formatting easier. 1171.1Scgd 1181.1ScgdDefinitions are given with the word or phrase left justified, followed by 1191.1Scgdthe part of speech (if appropriate) and a colon. The definition starts 1201.1Scgdindented by one tab stop, with subsequent lines left justified, e.g., 1211.1Scgd 1221.1Scgd Afternoon, n.: 1231.1Scgd That part of the day we spend worrying about how we wasted 1241.1Scgd the morning. 1251.1Scgd 1261.1ScgdQuotes are sometimes put around statements which are funnier or make more 1271.1Scgdsense if they are understood as being spoken, rather than written, 1281.1Scgdcommunication, e.g., 1291.1Scgd 1301.1Scgd "All my friends and I are crazy. That's the only thing that 1311.1Scgd keeps us sane." 1321.1Scgd 1331.1ScgdEllipses are always surrounded by spaces, except when next to punctuation, 1341.1Scgdand are three dots long. 1351.1Scgd 1361.1Scgd "... all the modern inconveniences ..." 1371.1Scgd -- Mark Twain 1381.1Scgd 1391.1ScgdHuman initials always have spaces after the periods, e.g, "P. T. Barnum", 1401.1Scgdnot "P.T. Barnum". However, "P.T.A.", not "P. T. A.". 1411.1Scgd 1421.1ScgdAll fortunes should be attributed, but if and only if they are original with 1431.1Scgdsomebody. Many people have said things that are folk sayings (i.e., are 1441.1Scgdcommon among the folk (i.e., us common slobs)). There is nothing wrong with 1451.1Scgdthis, of course, but such statements should not be attributed to individuals 1461.1Scgdwho did not invent them. 1471.1Scgd 1481.1ScgdHoroscopes should have the sign indented by one tab stop, followed by the 1491.1Scgddates of the sign, with the text left justified below it, e.g., 1501.1Scgd 1511.1Scgd AQUARIUS (Jan 20 - Feb 18) 1521.1Scgd You have an inventive mind and are inclined to be progressive. You 1531.1Scgd lie a great deal. On the other hand, you are inclined to be 1541.1Scgd careless and impractical, causing you to make the same mistakes over 1551.1Scgd and over again. People think you are stupid. 1561.1Scgd 1571.1ScgdSingle quotes should not be used except as quotes within quotes. Not even 1581.1Scgdsingle quotes masquerading as double quotes are to be used, e.g., don't say 1591.1Scgd``hi there'' or `hi there' or 'hi there', but "hi there". However, you 1601.1Scgd*can* say "I said, `hi there'". 1611.1Scgd 1621.1ScgdA long poem or song can be ordered as follows in order to make it fit on a 1631.1Scgdscreen (fortunes should be 19 lines or less if at all possible) (numbers 1641.1Scgdhere are stanza numbers): 1651.1Scgd 1661.1Scgd 11111111111111111111 1671.1Scgd 11111111111111111111 1681.1Scgd 11111111111111111111 22222222222222222222 1691.1Scgd 11111111111111111111 22222222222222222222 1701.1Scgd 22222222222222222222 1711.1Scgd 33333333333333333333 22222222222222222222 1721.1Scgd 33333333333333333333 1731.1Scgd 33333333333333333333 44444444444444444444 1741.1Scgd 33333333333333333333 44444444444444444444 1751.1Scgd 44444444444444444444 1761.1Scgd 44444444444444444444 1771.1Scgd 1781.1Scgd 179