Union Catalogue of Manuscripts from the Islamicate World

RAS Persian 315. (Library, Royal Asiatic Society of Great Britain and Ireland)

Persian Manuscripts


Summary of Contents: 1 copy of Minu Khirad by Marzban (Rawani? so in pencil on the second flyleaf. See notes.).

Marzban, apparently the author's name, appears at the end of the first poem and in the heading of the second. Probably also on f9a, where it may be implied that he came from Rawar. First flyleaf, verso: From the Atash Bahman Fire Temple, built at Surat by Peshtanji Kalabhai Wakeel?. Presented by his son Nausheerwanji? to John Romer. March 1856 (The year may be in the Samvat calendar.) Second flyleaf, recto: a) note of ownership of ... Bahramji? Nausheerwanji? ... b) line of Devanagiri-type script. The title is written in pencil in English of the second flyleaf, recto. This is not the Persian translation of the Zoroastrian work of that name (e.g. Ethe No 2986). The MSS consists of two poems, the first consisting mainly of a series of question put by a wise man to Khirad (Wisdom). The second gives an account of some of the activiies of the Sasanian king Anushirwan, of the end of the Sasanian dynasty and negotiations between 'Ali and the Mubads ending in his making a treaty with the Persians. Headings in red.

Incipit: Bi-nam-i khudawand-i jall u jalal
Language(s): Persian.


None found.
Entered in the Donations Register for April 5 1856.

Physical Description

Form: codex
Extent: Folios 121
Dimensions (leaf): 10 × 5.75 in.


13 lines on a page in double column




Red leather European-stile binding with tooled decoration and marbled doublures.


Provenance and Acquisition

Presented by John Romer.


Visitors are welcome to consult manuscripts in the library by prior appointment. Information on access is available on the library page of the Society's web site at www.royalasiaticsociety.org and appointments can be arranged by e-mailing library@royalasiaticsociety.org


Comment on this record

Please fill out your details.

How are we using your feedback? See our privacy policy.