Rotten Fruit Disease Pathogen Identification that Isolated from Betel Nut  

Zhaofen Huang , Liu Xie
Haide Institute of Tropical Agricultural Resources, Sanya, 572025
Haide Institute of Tropical Agricultural Resources, Sanya, 572025
Author    Correspondence author
Molecular Pathogens, 2010, Vol. 1, No. 2   
Received: 19 Nov., 2010    Accepted: 03 Dec., 2010    Published: 10 Dec., 2010
© 2010 BioPublisher Publishing Platform
Abstract

In this study, pathogen Ar8904 Ar8905 were isolated from rotten betelnut in Taiwan Province, pathogen Ar8801, Ar8802, Ar8904 were isolated from rotten betel nut in Hainan Province and pathogen Ar8901, Ar892 were isolated from rotten betel nut in Yunnan Province. Several contrast experiments for the seven strains showed that the morphology, cultural characteristics, host range, pathogenicity and symptom characteristics of the 7 strains are very similar. Therefore, according to modern classification criteria of the colletotrichum, we could determinate that these pathogens isolated from Taiwan province, Yunnan province and Hainan province are the same species of colletotrichum. The rotten fruit disease of betel nut i is caused by the colletotrichum.

Keywords
Betel nut; Conidia; Pathogen; Colletotrichum

(The advance publishing of the abstract of this manuscript does not mean final published, the end result whether or not published will depend on the comments of peer reviewers and decision of our editorial board.)
The complete article is available as a Provisional PDF if requested. The fully formatted PDF and HTML versions are in production.
Molecular Pathogens
• Volume 1
View Options
. PDF
Associated material
. Readers' comments
Other articles by authors
. Zhaofen Huang
. Liu Xie
Related articles
. Betel nut
. Conidia
. Pathogen
. Colletotrichum
Tools
. Post a comment

503 Service Unavailable

Service Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Additionally, a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request.