🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: mod.recipes
Article #526

How to submit a recipe (last updated 15 Dec 86)

#526
From: recipes
Date: Sat, 28 Feb 1987 09:08
154 lines
7884 bytes
RECIPES(5)          UNIX Programmer's Manual           RECIPES(5)

NAME
     recipes - USENET Cookbook (mod.recipes) format and submit-
     ting procedure.

SYNOPSIS
     Mail your recipe to mod-recipes@decwrl. Try not to plagiar-
     ize.  If you want to put in your own troff commands, use the
     Unix manual macros.

DESCRIPTION
     Mod.recipes is a ``moderated newsgroup''. This means that
     you mail your submissions to the moderator, and he distri-
     butes them.  The moderator's mailbox is
          decwrl!mod-recipes,
     if you believe in that kind of address, or
          {ihnp4, decvax, ucbvax, glacier}!decwrl!mod-recipes
     if you believe in the other kind of address. The address
          mod-recipes@decwrl.DEC.COM
     also works, if you know how to mail to it.

     If your netnews administrator has set things up properly and
     if you are running the right news software, you can just
     post to mod.recipes as you would any other group, but your
     posting will be mailed to the moderator insted of being
     placed directly in the newsgroup.

HOW TO FORMAT A RECIPE
     Every recipe that goes out will be formatted with a small
     set of troff commands. If you don't know any troff, then
     just send the text of your recipe. If you can do the format-
     ting yourself, then please do! That will save the editor a
     lot of time, and your recipe will go out sooner.  Some hints
     for how to do it are in a later section of this document.
     If you don't know about xroff/troff/nroff but you do want to
     be helpful, then you can help a lot by doing these things:

     (1)  Put your recipe in the standard sequence:

     (2)  Don't put any tab characters (^I) in the file if you
          can possibly avoid it.  They do strange things on
          typesetters.

     (3)  If you are a troff wizard, please don't use any of that
          wizardry in these recipes. If you stick to the set of
          commands used in the Unix manual macros (see man(7)),
          and the set of commands that are part of the USENET
          Cookbook package (see following section), then things
          should work OK.
          There are plenty of places in troff where you can get
          away with not using quotes around macro arguments.
          Please use quotes, even when they are redundant, such
          as in ``.IG "1" "onion"''  This is because the indexing

          and cross-referencing programs expect to find the
          quotes, even though troff can work without them.

HOW TO WRITE A RECIPE
     Please try to put your recipe in the standard sequence. Dif-
     ferent cookbooks use different standards. This is the
     sequence that the USENET Cookbook uses.

          (a)  Title and 1-line description. The 1-line descrip-
               tion will be used to index the recipe, so make it
               as descriptive as possible. Avoid words like
               ``delicious'' or ``yummy''. We expect all of these
               recipes to be delicious.

          (b)  Introductory commentary, explaining (if possible)
               where you got the recipe from and what you like
               about it. If you got the recipe from a cookbook,
               give the title and author of that cookbook.

          (c)  List of ingredients, using ``Tbsp'', ``tsp'',
               ``cup'', ``oz'', and ``lb'' for English units, or
               ``ml'', ``dl'', ``l'', ``g'', and ``kg'' for
               metric units. Stay away from ``pint'', ``quart'',
               and ``gallon'', because they have different mean-
               ings in different countries. Do not use 1-letter
               abbreviations for US measures: don't use "c" for
               "cup" or "T" for "Tbsp". An ``oz'' is a The
               ingredients should be listed in the order they
               will be used. Don't capitalize ingredient names
               unless they are proper nouns. Avoid terms like ``1
               box'' or ``1 can'' or ``1 package'', because pack-
               aging conventions vary widely from place to place.
               If you must say ``1 can of soup'', then at least
               tell me how big you think a can of soup is.

          (d)  Numbered sequence of recipe steps. Be very careful
               to mention every ingredient somewhere. The most
               common mistake made in recipes is to omit one or
               more ingredients from the procedure steps.

          (e)  Notes (if any). Comments on how you like to make
               it, ingredient availability, comments about
               specific brands, etc.

          (f)  Your ``signature''. This should include your name
               and net address, the organization that you are a
               part of, and the name of the city it is in. It can
               also include other frivolity or foolishness if you
               like; I'll include as much of it as will fit on
               the page unless it is offensive.

COPYRIGHT NOTES
     Tell us where you got the recipe from. It's ok if you
     cribbed it from a book or magazine or newspaper, but if you
     copy exactly the words that you found there, there might be
     a problem with copyright violation.  The copyright of a
     recipe is not on the formula, but on the words. If you have
     copied the words out of a copyrighted cookbook, then you are
     infringing its copyright.

     While the main purpose of the USENET cookbook is to let us
     all make our own custom cookbooks, we can't ignore the real-
     ity of the copyright law. Surely you have noticed that every
     modern book says ``No part of this publication may be repro-
     duced, stored in a retrieval system, or transmitted, in any
     form or by any means, electronic, ..., or otherwise without
     the prior written permission of the publisher.''

     Copyright law is complex, and only a lawyer who specializes
     in copyright can reliably advise you on whether or not you
     are violating it, but in general if you rewrite a recipe, in
     your own words, even if you don't change the formula, then
     you are not infringing the copyright by submitting that
     recipe to the network. The copyright is on the words that
     explain the recipe, and on the title of the recipe, not the
     formula itself.

     The USENET Cookbook itself is copyrighted. Every recipe is
     sent out with a copyright notice, and the macros that print
     the cookbooks add a copyright notice to the bottom of each
     page. The purpose of this is to prevent unauthorized commer-
     cial use of the USENET Cookbook.

CATEGORY CODES
         M     Main dish           SL    Salad
         A     Appetizer or snack  SP    Soup
         B     Bread/cake/pasta    D     Dessert
         L     Beverage (Liquid)   V     Vegetable dish
     The suffix ``V'' on any category means that it is

     vegetarian; for example, a vegetarian main dish recipe would
     be marked ``MV''.

SEE ALSO
     cookbook(1), rn(1)

AUTHOR
     Brian Reid, DEC Western Research Laboratory
Technical Details
Message-ID: <8344@decwrl.DEC.COM>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watnot!watmath!clyde!cbatt!gatech!lll-lcc!pyramid!decwrl!recipes

Show Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watnot!watmath!clyde!cbatt!gatech!lll-lcc!pyramid!decwrl!recipes
From: recipes@decwrl.UUCP
Newsgroups: mod.recipes
Subject: How to submit a recipe (last updated 15 Dec 86)
Message-ID: <8344@decwrl.DEC.COM>
Date: Sat, 28-Feb-87 04:08:59 EST
Article-I.D.: decwrl.8344
Posted: Sat Feb 28 04:08:59 1987
Date-Received: Sun, 1-Mar-87 13:36:48 EST
Sender: recipes@decwrl.DEC.COM
Organization: DEC Western Research Laboratory, Palo Alto, CA
Lines: 154
Keywords: automatic monthly posting 4 of 8
Approved: reid@decwrl.UUCP