[Previous by date - ICSEB-VI]
[Next by date - Gender of species names?]
[Previous by subject - Galtonia (a test case?)]
[Next by subject - Gender of species names?]
Date: Thu, 18 Apr 2002 11:27:11 +0200
From: David Marjanovic <david.marjanovic@gmx.at>
To: PhyloCode mailing list <phylocode@ouvaxa.cats.ohiou.edu>
Subject: Gender of species names?
This is a multi-part message in MIME format.
--Boundary_(ID_wiF+G19FejXlfFsaf+zWZA)
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: quoted-printable
In his gigantic critique of an early version of the PhyloCode, Michael =
J. Benton http://palaeo.gly.bris.ac.uk/phylocode/biolrev.html moans "the =
obvious problem of frequently re-used specific epithets (e.g. the =
snoeshow hare, Lepus americanus, the Rocky Mountain goat, Oreamnos =
americanus, the American black bear, Ursus americanus, the moose, Alces =
americana, the pronghorn, Antilocapra americana, the American marten, =
Martes americana, which all become americanus)" which, he writes, can be =
solved by e. g. adding numbers to the names.
What will happen to gender endings under PhyloCode? I haven't =
seen any mentioning of this problem anywhere else so far. Could we leave =
them "uncodified" so that they can be adapted to whatever clade address =
is used in front of them?
BTW, I've written an even bigger critique of Benton's critique, and one =
of Platnick's critique =
(http://www.systass.org/meetings/agm-address-dec2001.html), and put them =
on a website that I must repair... the two editors I use, MS Word and MS =
FrontPage Express, are amazingly incompatible and have ruined much of =
the layout. I'll post the URLs later. -- You can certainly guess almost =
every word I wrote anyway. :-)
--Boundary_(ID_wiF+G19FejXlfFsaf+zWZA)
Content-type: text/html; charset="iso-8859-1"
Content-transfer-encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4912.300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2><FONT face=3DArial>In his gigantic critique of an =
early version=20
of the PhyloCode, Michael J. Benton </FONT><A=20
href=3D"http://palaeo.gly.bris.ac.uk/phylocode/biolrev.html"><FONT=20
face=3DArial>http://palaeo.gly.bris.ac.uk/phylocode/biolrev.html</FONT></=
A><FONT=20
face=3DArial> moans "the obvious problem of frequently re-used =
specific=20
epithets (e.g. the snoeshow hare, <U>Lepus americanus</U>, the Rocky =
Mountain=20
goat, <U>Oreamnos americanus</U>, the American black bear, <U>Ursus=20
americanus</U>, the moose, <U>Alces americana</U>, the pronghorn, =
<U>Antilocapra=20
americana</U>, the American marten, <U>Martes americana</U>, which all =
become=20
<U>americanus</U>)" which, he writes, can be solved by e. g. adding =
numbers=20
to the names.</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2> =
What will=20
happen to gender endings under PhyloCode? I haven't seen any mentioning =
of this=20
problem anywhere else so far. Could we leave them "uncodified" so that =
they can=20
be adapted to whatever clade address is used in front of =
them?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>BTW, I've written an even bigger =
critique of=20
Benton's critique, and one of Platnick's critique (<A=20
href=3D"http://www.systass.org/meetings/agm-address-dec2001.html">http://=
www.systass.org/meetings/agm-address-dec2001.html</A>), and=20
put them on a website that I must repair... the two editors I =
use, MS=20
Word and MS FrontPage Express, are amazingly incompatible and have =
ruined much=20
of the layout. I'll post the URLs later. -- You can certainly guess =
almost every=20
word I wrote anyway. :-)</FONT></DIV></BODY></HTML>
--Boundary_(ID_wiF+G19FejXlfFsaf+zWZA)--