reid@glacier.UUCP (Brian Reid) (11/30/85)
The way you submit to mod.recipes is to mail the recipe to the
moderator. The moderator's mailbox is
glacier!mod-recipes.UUCP,
if you believe in that kind of address, or
{hplabs, decwrl, bellcore, sun}!glacier!mod-recipes
if you believe in the other kind of address. The addresses
mod-recipes@Glacier.ARPA
and mod-recipes@Glacier.STANFORD.EDU
also work, if you know how to mail to them.
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 STRUCTURE 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 formatting yourself, then great! That will save the
editor a lot of time. Some hints for how to do it are in a later section of
this documentation. If you don't know about xroff/troff/nroff but you do
want to be helpful, then you can help a lot by doing this:
1 Put your recipe in the standard sequence:
- Title and 1-line description
- Introductory commentary, explaining (if possible) where you got
the recipe from.
- list of ingredients, using "Tbsp.", "tsp.", "cup", "oz", and "lb",
- Numbered sequence of recipe steps.
- Notes (if any). Comments on how you like to make it, or ingredient
availability, etc.
- your signature file. I'll put as much of it as will fit into
the outgoing recipe.
2 Don't put any tab characters (^I) in the file. They confuse troff
something terrible, and I'll just have to take them out.
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.
You can also submit evaluations, modifications, suggestions, or bug-fixes to
existing recipes.
COPYRIGHT NOTES
It's important that you 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.
While the main purpose of the USENET cookbook is to let us all make our own
custom cookbooks, we can't ignore the reality of the copyright law. Surely
you have noticed that every modern book says ``No part of this publication
may be reproduced, 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 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 recipe, 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 not the recipe itself.
DO YOUR OWN FORMATTING
If you put formatting commands in the recipes that you submit, they will go
out more quickly, since the editor won't have to do it. It's easy to learn
how.
The basic principle is to use as few commands as possible, and in general to
use only commands that are defined in the manual macros or the recipe macro
package. Various processing programs search through these files and look for
string matches on things like ".IG" and ".RZ".
Print out a few of the recipe source files from /usr/spool/news/mod/recipes,
and then use /usr/local/bin/rctypeset or rcnroff to produce formatted
versions of them. Have that at hand when you are formatting your recipe. You
can test your formatting by using rctypeset or rcnroff on your draft versions
before you submit the recipe.
A ``skeleton'' recipe follows. .RH is the recipe header command; it must be
the first line of each recipe and it must have 4 arguments.
"RECIPE-ID" is the file name under which the recipe will be stored; it must
be 14 characters or less. The "?" is a "what kind of recipe" code from the
code table below.
.RH MOD.RECIPES-SOURCE RECIPE-ID ? "22 Nov 85"
.RZ "RECIPE TITLE" "One-line description of it"
Introductory comments; use .PP for new paragraph.
.IH "Serves 13" <-- Ingredients Header
.IG "1/2 cup" "butter" <-- Ingredient (please use quotes)
.IG "1" "onion"
(medium to large, chopped fine. Don't try to use instant onion
in this recipe)
.PH <-- Procedure header
.SK 1 <-- Procedure step
Preheat oven to 600 degrees <-- Text for that step
.SK 2 <-- and so forth.
.NX <-- Notes header
Notes (commentary) goes here; use .PP to separate paragraphs.
.WR <-- Wrapup
Signature information goes here. A copy of your .signature file is OK,
but remember that there will already be one at the end of your message,
so if that's what you want, then just put the word ".signature" here.
You can also use the following -man macros; see man(7) for the complete
list.
.I "italic words"
.B "boldface words"
.SM "small words"
.PP <-- paragraph break
.PD <distance> <-- paragraph distance
.IP "indented paragraph".
.RS <-- relative start: move things to the right
.RE <-- relative end: move things left again
You can also use these nroff/troff commands:
.if, .ds,.br,.nf,.fi, and .ta.
CATEGORY CODES
M Main dish SL Salad
A Appetizer or snack SP Soup
B Bread/cake/pasta D Dessert
L Beverage (Liquid)
The suffix ``V'' on any category means that it is vegetarian; for example, a
vegetarian main dish recipe would be marked ``MV''.reid@glacier.UUCP (Brian Reid) (12/07/85)
[This message has been reposted because some of the major backbone sites
managed to lose its previous posting]
The way you submit to mod.recipes is to mail the recipe to the
moderator. The moderator's mailbox is
glacier!mod-recipes.UUCP,
if you believe in that kind of address, or
{hplabs, decwrl, bellcore, sun}!glacier!mod-recipes
if you believe in the other kind of address. The addresses
mod-recipes@Glacier.ARPA
and mod-recipes@Glacier.STANFORD.EDU
also work, if you know how to mail to them.
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 STRUCTURE 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 formatting yourself, then great! That will save the
editor a lot of time. Some hints for how to do it are in a later section of
this documentation. If you don't know about xroff/troff/nroff but you do
want to be helpful, then you can help a lot by doing this:
1 Put your recipe in the standard sequence:
- Title and 1-line description
- Introductory commentary, explaining (if possible) where you got
the recipe from.
- list of ingredients, using "Tbsp.", "tsp.", "cup", "oz", and "lb",
- Numbered sequence of recipe steps.
- Notes (if any). Comments on how you like to make it, or ingredient
availability, etc.
- your signature file. I'll put as much of it as will fit into
the outgoing recipe.
2 Don't put any tab characters (^I) in the file. They confuse troff
something terrible, and I'll just have to take them out.
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.
You can also submit evaluations, modifications, suggestions, or bug-fixes to
existing recipes.
COPYRIGHT NOTES
It's important that you 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.
While the main purpose of the USENET cookbook is to let us all make our own
custom cookbooks, we can't ignore the reality of the copyright law. Surely
you have noticed that every modern book says ``No part of this publication
may be reproduced, 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 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 recipe, 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 not the recipe itself.
DO YOUR OWN FORMATTING
If you put formatting commands in the recipes that you submit, they will go
out more quickly, since the editor won't have to do it. It's easy to learn
how.
The basic principle is to use as few commands as possible, and in general to
use only commands that are defined in the manual macros or the recipe macro
package. Various processing programs search through these files and look for
string matches on things like ".IG" and ".RZ".
Print out a few of the recipe source files from /usr/spool/news/mod/recipes,
and then use /usr/local/bin/rctypeset or rcnroff to produce formatted
versions of them. Have that at hand when you are formatting your recipe. You
can test your formatting by using rctypeset or rcnroff on your draft versions
before you submit the recipe.
A ``skeleton'' recipe follows. .RH is the recipe header command; it must be
the first line of each recipe and it must have 4 arguments.
"RECIPE-ID" is the file name under which the recipe will be stored; it must
be 14 characters or less. The "?" is a "what kind of recipe" code from the
code table below.
.RH MOD.RECIPES-SOURCE RECIPE-ID ? "22 Nov 85"
.RZ "RECIPE TITLE" "One-line description of it"
Introductory comments; use .PP for new paragraph.
.IH "Serves 13" <-- Ingredients Header
.IG "1/2 cup" "butter" <-- Ingredient (please use quotes)
.IG "1" "onion"
(medium to large, chopped fine. Don't try to use instant onion
in this recipe)
.PH <-- Procedure header
.SK 1 <-- Procedure step
Preheat oven to 600 degrees <-- Text for that step
.SK 2 <-- and so forth.
.NX <-- Notes header
Notes (commentary) goes here; use .PP to separate paragraphs.
.WR <-- Wrapup
Signature information goes here. A copy of your .signature file is OK,
but remember that there will already be one at the end of your message,
so if that's what you want, then just put the word ".signature" here.
You can also use the following -man macros; see man(7) for the complete
list.
.I "italic words"
.B "boldface words"
.SM "small words"
.PP <-- paragraph break
.PD <distance> <-- paragraph distance
.IP "indented paragraph".
.RS <-- relative start: move things to the right
.RE <-- relative end: move things left again
You can also use these nroff/troff commands:
.if, .ds,.br,.nf,.fi, and .ta.
CATEGORY CODES
M Main dish SL Salad
A Appetizer or snack SP Soup
B Bread/cake/pasta D Dessert
L Beverage (Liquid)
The suffix ``V'' on any category means that it is vegetarian; for example, a
vegetarian main dish recipe would be marked ``MV''.
--
Brian Reid decwrl!glacier!reid
Stanford reid@SU-Glacier.ARPA