home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Complete Bookshop
/
CompleteWorkshop.iso
/
mmast
/
mmconv14
/
whatsnew.140
< prev
Wrap
Text File
|
1993-09-04
|
4KB
|
110 lines
This version owes a debt to Fran McGee on FIDO. She made a comment
about the amount of work that got me thinking. I think you will find
MMCONV version 14 to be much more user friendly than preceding versions as
a result. It also means that MMCONV13 will have only a brief career...
The conclusion was:
And you got me thinking with your comment...
I think I can modify MMCONV to handle any length ingredient
line. Just have to require no spaces between ingredients line
and one space before directions. This would be generally
present in most recipes anyway. If not present would be much
more straightforward than figuring out if the removing 10 blanks
or so at start of line (which MMCONV does) would make the
ingredient line less than 45 characters.
Also would avoid the problem of short initial direction lines
like: Preheat oven to 350. (MMCONV thinks its an ingredient
which is not too horrible, but not 'neat').
I like it! Thanks for getting me started thinking about this.
But couldn't you have sent this before I put MMCONV13.zip on
Sempervirens last night?
User (and non-user even) suggestions are great. I modified
MMCONV13 to support a -x parameter that makes it just look for
From: and Date: (caseblind) in the file to determine origin and
date based on someone else's complaint and suggestion. This
should enable it to handle most message formats. At worse, you
just have to change some field to be From: or Date: rather than
an alternative. I had been avoiding pursuing a more difficult
suggestion of user defined headers in a file. This approach was
simple.
Both of you gave me that "Now why didn't I think of that?" or
"why the heck did I do it that way?" feeling.
Above was this morning.
I just modified MMCONV as discussed above. It is wonderful!!
You've cut the editing required down to a minimum. Basically
just put in needed headers (on unmarked recipes) and add a
couple of blank lines. I need to test this for a few days on a
variety of recipes. But thanks for a great notion!!
---------------------------------------------------------------------
You must have some sort of ingredients. If there are none in the
recipe, just stick in none with a blank line following before the
directions and you're set.
ver 1.4
- Eliminate character count as guide to ingredient line;
instead use first blank line as demarcation.
- Skip Pileggi headings:
Qty Measurement Ingredient
___---- --------
- Recognize Pileggi ____ as end of recipe
- combine clove or cloves with following word correctly
A point by point discussion of these items:
- Eliminate character count as guide to ingredient line;
instead use first blank line as demarcation.
You no longer have to divide up long ingredient lines. MMCONV will
format them for you. If there are blank lines within ingredients, they
should be removed. If there is no blank between ingredients and
directions, add one.
You must have some sort of ingredients. If there are none in the
recipe, just stick in none with a blank line following before the
directions and you're set.
- Skip Pileggi headings:
Qty Measurement Ingredient
___---- --------
Pileggi puts a lot of recipes out with these two odd headings. MMCONV
will now skip them and process ingredients.
- Recognize Pileggi ____ as end of recipe
Pileggi uses ___ rather than --- at end of his recipes. Difficult to
spot as not a match. So changed MMCONV to respond to it.
- combine clove or cloves with following word correctly
I got tired of clove(s) followed by several spaces splitting the
line. Or having to take out the spaces. I don't want to use CL for
cloves since MM regards as centiliters. So I added processing to close up
the spacing for cloves. That is:
3 cloves garlic processes to 3 cloves garlic appropriately
spaced.