04.09.2013 Views

Biblical Medical Plants - Macquirelatory.com

Biblical Medical Plants - Macquirelatory.com

Biblical Medical Plants - Macquirelatory.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Format of This Book<br />

It is only natural that a believer in evolution would have an evolving format. The current format<br />

has evolved from my CRC Handbook of Medicinal Herbs, 2nd edition, which had evolved from my<br />

public domain Father Nature’s Farmacy, online at the USDA. There are some new features here.<br />

Lead Line: The lead line for each species remains pretty much the same. Common name<br />

— (Scientific name Author) followed by an X, a +, ++, or +++ representing the rather<br />

subjective safety scores, as in the past (X = don’t take it, + = OK but probably not as safe<br />

as coffee, ++ = OK and probably as safe as coffee, and +++ = OK and probably safer than<br />

coffee); then the taxonomic family to which the species belongs. Family names are always<br />

in capital letters and end in “ACEAE.” Like allopaths, health announcers, and reporters,<br />

I reserve the right to change my mind as new information <strong>com</strong>es in, positive or negative.<br />

I assembled this information, based on the published literature — no prescription implied<br />

or intended.<br />

Synonyms: The next line may list some outdated synonyms, scientific names that at some<br />

time in the past also have been applied to this species.<br />

Notes: The NOTES paragraph almost always begins with biblical quotes from various translations<br />

of the Bible (KJV = King James Version; RSV = Revised Standard Version, NWT<br />

= New World Translation). It is amazing how many uncopyrighted versions of the Bible in<br />

many languages are available on the Internet. And it is amazing how often the plant names<br />

(usually underlined in the quotation) are differently translated in the various versions.<br />

After these quotes follows a concise paragraph or two <strong>com</strong>menting on points of interest.<br />

Common Names: Here I have <strong>com</strong>piled many, but by no means all, <strong>com</strong>mon names, often<br />

flagged as to language or country of origin. First <strong>com</strong>es a name in alphabetical order<br />

with a parenthetical citation of the country and/or language name or abbreviation. The<br />

country/language names/abbreviations always have the initial letter capitalized and subsequent<br />

letters in lowercase. These are followed by three-letter abbreviations (all capital<br />

letters) of the source(s), sometimes supplemented by journal citations or PubMed abstracts<br />

preceded by an X, to tell readers where I found these names. Sometimes one of the references,<br />

most frequently KAB, will list more than a hundred <strong>com</strong>mon names, from various<br />

parts of India and elsewhere, including dozens of Sanskrit names. In some such cases, I<br />

took at least one name from that source from each country or language. Few users will<br />

want to study all these <strong>com</strong>mon names unless it is a country they plan to visit. With an<br />

electronic version of the database, they could generate the names pertinent to the country<br />

they plan to visit. Often, the name itself will tell something about the plant or its medicinal<br />

uses. I have elected to use the standardized <strong>com</strong>mon names (Scn.) endorsed by the American<br />

Herbal Products Association (AH2) as the pivotal <strong>com</strong>mon name in the lead line for<br />

the entry. Occasionally, AH2 would offer an optional alternative <strong>com</strong>mon name, which I<br />

have abbreviated Ocn. (= other <strong>com</strong>mon name). Where there was no standardized <strong>com</strong>mon<br />

name, I often use the abbreviation Nscn. (= no standardized <strong>com</strong>mon name). In such<br />

cases, not un<strong>com</strong>mon in this biblical edition, I have consulted the USDA nomenclaturists<br />

and their database, trying to ensure that they and I will agree, and this might later influence<br />

the American Herbal Products Association should they decide to add some of these<br />

to a revised edition of their standardized <strong>com</strong>mon name book. With these <strong>com</strong>mon names

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!