Melba's Jammin' wrote:
> In article >,
> "Jinx Minx" > wrote:
>
>> I'm on this committe that wants to put together a cookbook that it can sell
>> for a small profit. Has anyone here does this before that can offer up
>> advice how best to go about it? Places we can get it printed inexpensively
>> but aren't cheaply made, free software or websites we can use to put it
>> together, etc. I use Mastercook at home and it says you can "print your own
>> cookbook", but I've never used it for that purpose so I'm not sure whether
>> it's a good choice for a larger project like this. We're just getting
>> started on this project so I'd like for us to start out on the right foot.
>> Suggestions? Do's? Dont's?
>>
>> Jinx
>
> Oooh, fun! I've been thinking about one for a reunion but am not sure
> I've got the time in the next 2-1/2 months.
>
> Set standards and stick to them at risk of annoying someone;
> Insist that recipes be submitted in the format you want, ingredients
> listed in the order they are mentioned in the method;
>
> Use the same abbreviations (or no abbreviations) throughout;
>
> Make sure your proofreaders are literate ‹ good intentions are not
> enough;
>
> Have someone proofread what the proofreaders approved * you wouldn't
> believe the number of changes made to the rfc cookbook after **the
> proofread** version (galley proofs) came back from the printer. We were
> damned lucky that the guy didn't charge us a boatload of money for
> making the corrections that needed to be made;
>
> don't let anyone refer to No. 3, No. 303, etc. sizes for canned goods;
>
> Dummy up a cookbook with, say, 20 recipes in it, from your MC files.
> Follow their instructions and try out different layouts and paper sizes,
> etc.
>
> And I could go on and on and on.
>
>

And make sure the ingredients appear in the directions! And that
the ingredients mentioned in the directions are all in the list.

--
Jean B.