Sanskrit Manuscripts : Jayamaṅgalā


Sanskrit Manuscripts

<p style='text-align: justify;'>This leaf, bearing the folio number 80, is a fragment of the <i>Jayamaṅgalā</i> of Yaśodhara (possibly, fl. 13th century), a commentary on the <i>Kāmasūtra</i> of Vātsyāyana Mallanāga . At some point in the history of manuscript <a target='_blank' class='externalLink' href='/view/MS-ADD-02251-00001/1'>Add.2151.1</a>, containing the same text, this folio was inserted by mistake in place of the original f. 80. The latter is still preserved in the same bundle as an extra folio at the end (together with another fragment, Add.2151.3). Interestingly, <a target='_blank' class='externalLink' href='/view/MS-ADD-02251-00001/1'>Add.2151.1</a> and <a target='_blank' class='externalLink' href='/view/MS-ADD-02251-00002/1'>Add.2251.2</a> are clearly written by the same hand and are on the same kind of palm leaf, which explains how the exchange might have taken place. Despite bearing the folio number 80, it roughly corresponds to f. 50 of <a target='_blank' class='externalLink' href='/view/MS-ADD-02251-00001/1'>Add.2151.1</a>, namely a much earlier section of the text (Jayamaṅgalā ad Kāmasūtra 1.5.7-12). This suggests that the copyist may have made two copies of the same text, possibly around the same time, one (<a target='_blank' class='externalLink' href='/view/MS-ADD-02251-00001/1'>Add.2151.1</a>) with the commentary alone and the other, to which this folio belonged, in which the commentary was preceded by the main text. This might explain the discrepancy in folio numbers between the two folios containing the same section.</p>

Want to know more?

Under the 'More' menu you can find , any transcription and translation we have of the text and find out about downloading or sharing this image.

No Contents List Available
No Metadata Available


If you want to share this page with others you can send them a link to this individual page:
Alternatively please share this page on social media

You can also embed the viewer into your own website or blog using the code below: