Marijn van Putten Profile picture
Sep 28, 2020 16 tweets 4 min read Read on X
Great conversation between @dbru1 and Asma Hilali about quranic manuscripts but to me one detail remained a bit vague, it is addressed in the title: "Did the Quran exist early as a book?"

The answer to this should, unequivocally be: Yes. Yes it did.

Thread 🧵
One of the questions posed in the conversation is "where is Uthman's codex?" and "where are the regional codices?"

We might actually have them, but the fragments we have simply do not come with labels.

But even if we didn't this does not mean they aren't CERTAINLY a reality.
We do not own the autograph of Sībawayh's al-Kitāb, are we to assume al-Kitāb never existed and Sībawayh did not write it? Of course not. And this is true for the vast majority of the Classical Arabic literature (or any literature in manuscript traditions).
You do need to own a physical copy of the ancestral manuscript to prove, beyond any shadow of a doubt that there was an ancestral manuscript from which all manuscripts descend. 2 almost identical manuscripts, reproducing various orthographic idiosyncrasies must share an ancestor.
All Quranic manuscripts (with the exception of the Sanaa Palimpsest) are so similar that they can only have arrived through careful copying upon copying from a single ancestral text, e.g. these 2 pages of Or. 2165 and the Birmingham fragment are identical save 1 letter!
The field of text criticism is concerned with reconstructing such shared ancestral texts. It's in many ways similar to how we can trace DNA. Even if you and your cousin never knew your grandparents, and didn't even know you're related the similarities in genome would give it away
Even if you would no longer have access to your grandparants' DNA, it would of course be absurd to suggest that just because they DNA is not extant, the grandparents did not exist at all.

Manuscript reproduction is more like asexual reproduction, but the point remains the same.
Through textual criticism, we can prove there was a common ancestor, we can prove that there were (at least) four original copies made, distributed to Medina, Basra, Kufa and Syria. Through C14-dating and other methods we can prove this happened very early on (around 650 CE).
There are manuscripts with much greater dissimilarities between different text types than the Quran which are universally accepted to have a common ancestor. The concept of a 'lost' but nevertheless certain archetype is also clearly attested in the stemmatics of the Hebrew Bible
Comparing the Quran to the Hebrew Bible, it would not be fair to equate the Uthmanic archetype to any of these (lost) nodes. The differences between the different Quranic manuscripts are smaller than even the Masoretic Text (Mt), whose existence of an archetype is simply accepted
While we still lack a true critical edition of the Uthmanic text type, we should not overstate its necessity either. The modern print Qurans, which base themselves on medieval works on Quranic orthography, actually come very close to reproducing the ancestral rasm.
It is possible to highlight several hundred orthographic variants which the modern print qurans get 'wrong', but most of the spellings it actually gets right. It's only a bit too liberal with writing the alif, if you would remove those you'd have something close to the Kufan copy
To get a sense of the impressive and careful copying from the archetype, check out my article "The Grace of God", which looks at one of these many orthographic idiosyncrasies that are carefully and consistently reproduced across early manuscripts.

doi.org/10.1017/S00419…
If you enjoyed this thread, and you want to support me, right now it is extra appreciated. My contract at Leiden has ended, and I'm currently between jobs so extra support is greatly appreciated!
My Ko-Fi: ko-fi.com/phdnix
My Patreon: patreon.com/PhDniX


Awkward typo in this tweet, I hope you were not all super confused. This should read: You *don't need... etc.
you *DON'T

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Marijn van Putten

Marijn van Putten Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @PhDniX

Apr 21
In my book "Quranic Arabic" I argue that if you look closely at the Quranic rasm you can deduce that the text has been composed in Hijazi Arabic (and later classicized into more mixed forms in the reading traditions). Can we identify dialects in poetry?
I think this is possible to some extent, yes. And so far this has really not been done at all. Most of the time people assume complete linguistic uniformity in the poetry, and don't really explore it further.
But there are a number of rather complex issues to contend with:
As @Quranic_Islam already identified, there are some philological problems that get in the way in poetry that aren't there for the Quran: I would not trust a hamzah being written in a written down poem. This might be classicization. So it's hard to test for this Hijazi isogloss.
Read 13 tweets
Apr 17
Last year I was asked to give a talk at the NISIS Autumn School about the textual history of the Quran. Here's a thread summarizing the points of that presentation. Specifically the presentation addresses some of Shoemaker's new objections on the Uthmanic canonization. Image
Traditionally, the third caliph ʿUṯmān is believed to have standardized the text.

However, in critical scholarship of the '70s the historicity of this view came to be questioned.

How can we really be sure that what the tradition tells us is correct?
Image
Image
This skepticism wasn't wholly unwarranted at the time. The Uthmanic canonization really had been uncritically accepted, not based on any material evidence.

But we now have access to many manuscripts, beautifully digitized, we can test the historicity of these claims! Image
Read 27 tweets
Apr 13
The canonical Kufan readers Ḥamzah and al-Kisāʾī read the word ʾumm "mother" or ʾummahāt "mothers" with a kasrah whenever -ī or -i precedes, e.g.:
Q43:4 fī ʾimmi l-kitābi
Q39:6/Q53:32 fī buṭūni ʾimma/ihātikum

This seems random, but there is a general pattern here! 🧵 Image
This feature was explained al-Farrāʾ in a lengthy discussion at the start of his Maʿānī. This makes sense: al-Farrāʾ was al-Kisāʾī's student who in turn was Ḥamzah's. Surprisingly in "The Iconic Sībawayh" Brustad is under the misapprehension that this is not a canonical variant.

Image
Image
Image
This is irregular, such a vowel harmony does not occur in cases with other words that starts with ʾu-. For example, Q13:30 is just fī ʾummatin, not **fī ʾimmatin.

However this irregular reading is part of a larger pattern of vowel harmony accross guttural consonants.
Read 15 tweets
Mar 20
Those who have read my book on Quranic Arabic may have noticed that I translate The Arabic word luġah as "linguistic practice", rather than "dialect" which is how many people commonly translate it.

This is for good reason: among the Arab grammarians it did not mean dialect! 🧵 Image
In Modern Standard Arabic, luġah basically just means "language", as can be seen, e.g. on the Arabic Wikipedia page on the Dutch Language which calls it al-luġah al-hūlandiyyah.

This modern use gets projected onto the early Arab grammarians like Sībawayh and al-Farrāʾ. Image
But, they clearly do not mean that to the early grammarians. This is clear from statements like Sībawayh saying: faʿil forms that have a guttural consonant as second radical have four "luġāt": faʿil, fiʿil, faʿl and fiʿl.

In English a word or word-form cannot "have" a dialect. Image
Read 10 tweets
Dec 26, 2023
A great irony of the whole "Muhammad is in the song of songs!" debacle, is that in basically all early sources that write vowels (Greek, Coptic, Sassanian, Syriac) but also in many modern languages (e.g. Turkish) his name appears to have been commonly been pronounced Maḥma/id. Image
Maḥmad would be a perfect match for the word-form found in the song of songs. But to give into that would of course be to allow for the Quran what they so readily consider acceptable for Hebrew, and are not willing to grant that. Double standards, plain and simple.
Because there is so much 7th-9th c. material that *clearly* attest to the prophet being called Maḥmad, even in Muslim documents, there is really no doubt that quite some muslims were calling him Maḥmad. There is no evidence the song of songs maḥămaddim was ever muḥammad.
Read 5 tweets
Dec 23, 2023
I made some diagrams of al-Dānī's ʾisnāds to the seven eponymous readers in the Taysīr. I thought it'd be nice to go through them, and give a couple of comments about them. So here I give a quick thread with some commentaries. Image
Notable first is that al-Dānī explicitly transmits each readings from two transmitters in two different modes of transmission:
riwāyah: a formal transmission of the specifities of the reading.
tilāwah: a full recitation of the Quran to their teacher which is validated that way.
These days tilāwah eclipses riwāyah so much that (if I am not mistaken) people essentially given up on formal riwāyah ʾisnāds altogether. But al-Dānī (and with him many early authors close to him) seem to give both, even (or especially?) in a learner's manual like the Taysīr.
Read 20 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(