Avoiding Common Mistakes in Writing Botanical Names

Botanical names look deceptively simple. One misplaced capital letter or missing comma can flip Clematis into Clematitis, turning a garden vine into a medical condition.

Precision here is not pedantry; it is the difference between ordering seeds for a prized perennial and accidentally cultivating a federally listed noxious weed. The rules below show exactly where writers slip up and how to stay on the safe side of the Latin.

Master the Hierarchy: Genus, Species, Infraspecifics

Every plant carries a nested address. Genus is the surname, species is the given name, and infraspecific ranks—subspecies, variety, forma—act like middle initials.

Write them left-to-right in descending order, never skipping a rank. Quercus robur is acceptable; Quercus robur subsp. robur is clearer when two subspecies exist.

Omitting an intermediate rank is a silent error. If you cite Salvia officinalis var purpurascens, you must first confirm that no subspecies sits between the species and the variety.

Italicization Scope

Only the Latin ranks themselves are italicized. The connecting terms “subsp.”, “var.”, “f.”, and “cv.” stay upright to signal their grammatical role.

Screen readers and search engines rely on this visual cue. A fully italicized string forces assistive tech to spell out “subsp” as if it were Latin, garbling pronunciation.

Capitalization After a Rank

Epithets are always lowercase, even when derived from a person’s name. Camellia japonica honours Japan, not a botanist named Japonica.

The exception is cultivar epithets, which are capitalized and quoted. Rosa ‘Peace’ is correct; Rosa peace is horticultural nonsense.

Don’t Invent Latin

Trade labels and Etsy listings are factories of fake Latin. “Succulentus sparklyus” is funny until a customs officer seizes the shipment for undocumented taxonomy.

If no published name exists, use the placeholder term “sp.” for a single unknown species or “spp.” for several. Attach a temporary code or collection number, e.g. Peperomia sp. Uruapan 2019-17.

This keeps databases clean and prevents the accidental christening of a nomen nudum—an invalid name that later blocks legitimate publication.

When Provisional Names Leak

Provisional nicknames germinate in private forums. Once a photo tagged “Begonia ‘Marmaduke’” reaches Instagram, retailers copy the label, and the informal epithet spreads like bindweed.

Publishers should cross-check every name against the International Plant Names Index (IPNI) or World Flora Online before going to print. A five-minute lookup can save years of retraction headaches.

Watch the Gender Agreement

Latin adjectives must match the gender of the genus. Alba (white) becomes albus when transferred from a feminine Salvia to a masculine Salvinia.

Combinations are automatically corrected on transfer, but older literature keeps the original spelling. Copy-pasting without checking leads to persistent mismatches like Brassica albus instead of Brassica alba.

Gender is discoverable in the protologue or through databases such as Tropicos, which flag “gender unresolved” for ambiguous cases.

Compound Epithets

Hyphenated epithets such as pseudo-acorus look unusual but are valid. Never merge the parts into “pseudoacorus”; the hyphen signals that the prefix is false, not a separate genus.

Search algorithms treat the hyphen as a space, so both halves remain discoverable. Deleting it collapses the semantic distinction and buries the entry in unrelated results.

Handle Authors’ Names with Consistency

The authority citation—the abbreviated botanist surname after the plant name—attributes ownership and date of publication. Echinacea purpurea (L.) Moench tells us Linnaeus first described it, but Moench later recombined it.

Omitting the authority is acceptable in popular writing, yet including it once and then dropping it mid-article confuses citation indexes. Decide early whether your piece is scholarly or conversational, then stay in that lane.

When shortening, never delete parentheses. The brackets preserve the historical sequence of recombination and prevent software from spawning duplicate taxonomic records.

Standard Abbreviations

Authors’ names follow globally agreed abbreviations maintained at IPNI. “L.” for Linnaeus is sacred; writing “Linn.” breaks every linking algorithm from GBIF to JSTOR.

Dual-authored names use an ampersand, not “and”. ×Aranda Hort. ex W. Mill. & Turrill fits the mold; spelling out “and” creates a new, non-existent authority string.

Respect the Hybrid Sign

The multiplication sign “×” is not a lowercase letter x. It is Unicode U+00D7, distinct in kerning and weight.

Font substitution on mobile devices can replace the proper glyph with a malformed letter, so embed the character explicitly or use HTML entity ×.

Place the sign immediately before the hybrid genus or epithet with no space. ×Fatshedera lizei is correct; × Fatshedera introduces an unwanted gap that breaks alphabetization.

Nothotaxa Below Genus

Interspecific hybrids within one genus receive the hybrid epithet only. Quercus ×turneri is the product of Q. ilex and Q. robur.

Triple crosses are still written with a single sign. Do not stack glyphs like ××; the rules treat complex ancestry as a single nothotaxon.

Tag Cultivars Correctly

Cultivar epithets are never Latinized. They are vernacular, can include numbers, and must be wrapped in single quotes.

Chrysanthemum ‘Bronze Fascination’ is right; Chrysanthemum Bronze Fascination without quotes implies a botanical variety, triggering regulatory audits for invasive plant lists.

Trade designations, often called “selling names,” follow different punctuation. They are presented in small capitals without quotes, e.g. Lavandula angustifolia Lady, distinguishing marketing from horticultural identity.

Group Names

When several cultivars share a trait, use the Group category. Brassica oleracea Italica Group covers all broccoli cultivars, streamlining seed certification paperwork.

Group is capitalized but not italicized, and it follows the last cultivar epithet if both are cited. Brassica oleracea ‘Calabrese’ Italica Group keeps hierarchy intact.

Avoid False Subspecies

Writers often invent subspecies to describe regional color forms. A blue-flowered population of Phlox paniculata is still Phlox paniculata unless a peer-reviewed monograph validates the split.

Submitting such informal variants to herbaria creates ghost taxa that clog revision workflows. Editors should demand either a literature citation or deletion of the rank.

Geographical Overloading

Adding “var. californica” to any plant found in California is tempting shorthand. The epithet may already exist for a different taxon, producing a later homonym that is automatically illegitimate.

Check the eFloras regional checklist before coining geography-based names. A single match prevents years of nomenclatural wrangling.

Keep Diacritics Intact

Portuguese and French place names supply many specific epithets. Joáo loses its tilde when stripped to “Joao”, corrupting pronunciation and etymology.

Unicode normalization can convert composed characters to decomposed pairs, breaking search indexes. Store names in NFC form and validate with a Latin-1 supplement regex.

Transcription from Non-Latin Scripts

Chinese phonetic renderings often carry macrons or breves. Cinnamomumzeylanicum’ traces back to Sinhala “zeylanica”, where the retroflex maps to a simple “l” in botanical Latin.

Do not re-insert non-Latin glyphs into the epithet; the original protologue already standardized the spelling. Adding diacritics retroactively creates an isonym that has no standing.

Update Spelling After Reclassification

When DNA barcoding moves a species to a different genus, the epithet’s ending may need adjustment. Sedum telephioides becomes Hylotelephium telephioides because the neuter ending agrees with the new genus.

Online archives lag behind revisions. Cross-reference Plants of the World Online for the current placement before republishing a decade-old article.

Automated Replace-All Risks

A global search that swaps every “Caryopteris” for “Tripora” will mangle sentences discussing the history of the transfer itself. Use boundary-limited regex with negative lookahead to protect narrative context.

Cite Specimens, Not Just Names

A name without a voucher specimen is folklore. Herbarium acronyms—NY, K, PE—anchor the concept to a physical plant pressed, barcoded, and photographed.

When profiling a new cultivar, list at least one herbarium sheet and the repository’s catalog number. This satisfies cultivar registration authorities and gives future taxonomists a baseline for comparison.

Digital Object Identifiers

Modern herbaria assign DOIs to each sheet. Linking https://doi.org/10.1234/k.567890 lets readers zoom to 40× magnification of the type specimen within seconds.

Include the DOI in the caption, not buried in the acknowledgments. Search engines index figure captions at higher weight than body text, boosting the article’s authority score.

Recognize Nameless Wild Relatives

Landrace peppers in rural Mexico often lack formal epithets. Referring to them as Capsicum annuum oversimplifies their distinct genepool.

Use the informal formula Capsicum annuum Landrace ‘Chilcostle’ with single quotes to signal cultivated status without claiming botanical novelty. This keeps options open for future taxonomic description.

Farmer’s Varietal Codes

Some villages track chili heat levels by seed lot numbers. Translating “Seed 43” into ‘Chil43’ in single quotes respects local knowledge while fitting international cultivar syntax.

Future-Proof with Versioned Databases

Taxonomy is versioned software. The World Checklist of Selected Plant Families releases annual updates; citing the 2022.1 release pins your article to a frozen state even after 2023 shuffles names.

Embed the version string in metadata: wcsp:2022.1:aceae:12345. Machine parsers can then auto-update tables while flagging human-readable text for review.

Static PDFs never age well. Export HTML with microdata tags so that taxonomy widgets can refresh names without altering your prose.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *