Tafheem-ul-Quran - Abul Ala Maududi

Ayah by Ayah

Download Links

Download simple.sqlite Download translation-with-inline-footnote.sqlite Download translation-with-inline-footnote.json Download translation-text-chunk.json Download translation-with-footnote-tags.sqlite Download translation-text-chunk.sqlite Download simple.json Download translation-with-footnote-tags.json

Tafheem-ul-Quran - Abul Ala Maududi translation for Surah Al-'Ankabut — Ayah 51

Jump to Ayah

← Previous Next →

29:51

أَوَلَمۡ يَكۡفِهِمۡ أَنَّآ أَنزَلۡنَا عَلَيۡكَ ٱلۡكِتَٰبَ يُتۡلَىٰ عَلَيۡهِمۡۚ إِنَّ فِي ذَٰلِكَ لَرَحۡمَةٗ وَذِكۡرَىٰ لِقَوۡمٖ يُؤۡمِنُونَ ٥١

Does it not suffice for them (as a Sign) that We revealed to you the Book that is recited to them?¹ Surely there is mercy and good counsel in it for those who believe.²

Footnotes

[1] The Arabic word used isayat(singularayah). Ayahmeans ‘sign’ or ‘proof’. It is also used to denote the unit of text in the Qur’an,like ‘verse’ in poetry or ‘sentence’ in prose.Each such unit isconsidered a ‘sign’from God.
[2] That is, “A Book like the Quran has been sent down to you in spite of your being unlettered. Is it not by itself a great miracle which should convince the people of your Prophethood? Do they yet need another miracle after this? The other miracles were the miracles for those who witnessed them. But this miracle is ever present in front of them. It is being recited before them almost daily; they can witness it as and when they like.” Even after such an assertion and argument by the Quran the audacity of those who try to prove that the Prophet (peace be upon him) was literate is astonishing. The fact, however, is that the Quran here has presented in clear terms the Prophet’s (peace be upon him) being illiterate as a strong proof of his prophethood. The traditions which lend support to the claim that the Prophet (peace be upon him) could read and write, or had learned reading and writing later in life, stand rejected at first glance, for no tradition opposed to the Quran can be acceptable. Then these traditions in themselves are too weak to become the basis for an argument. One of these is a tradition from Bukhari that when the peace treaty of Hudaibiya was being written down, the representative of the disbelievers of Makkah objected to the word Rasul-Allah being added to the name of the Prophet (peace be upon him). At this the Prophet ordered the writer (Ali, may Allah be pleased with him) to cross out the word Rasul-Allah and write Muhammad bin Abdullah instead. Ali refused to cross out Rasul-Allah. Then the Prophet (peace be upon him) took it in his own hand, struck out the word himself and wrote Muhammad bin Abdullah.
[3] But this tradition from Bara bin Azib appears at four places in Bukhari and at two places in Muslim and everywhere in different words:
[4] Qira’at: Ibn ʻAmer read it as: “. . . surely, they have no faith . . .”

Translations are available in both JSON and SQLite database formats. Some translation has footnotes as well, footnotes are embedded in the translation text using sup HTML tag. To support a wide range of applications, including websites, mobile apps, and desktop tools, we provide multiple export formats for translations.

Available export formats:

1. Nested Array Structure

Translations are grouped by Surah. Each Surah is an array containing translations for each Ayah in order. This format export translations as simple text, no formatting, no footnotes.

[
  ["translation of 1:1", "translation of 1:2"], ...
  ["translation of 2:1", "translation of 2:2"]
]

2. Key-Value Structure

Each translation is stored with the Ayah reference (e.g. 1:1) as the key and the translated text as the value. This format also exports translations as simple text, no formatting, no footnotes etc.

{
  "1:1": "translation of 1:1",
  "1:2": "translation of 1:2",
  ...
  "114:6": "translation of 114:6"
}

Translations with Footnotes

Translations with footnotes are available in three more formats:

1. Footnotes as Tags Format

Footnotes are embedded using a <sup> tag with a foot_note attribute. Footnote contents are stored separately under f key.

{
  "88:17": {
    "t": "Do the disbelievers not see how rain clouds are formed <sup foot_note=\"77646\">1</sup>",
    "f": {
      "77646": "The word ibl can mean 'camel' as well as 'rain cloud'..."
    }
  }
}

2. Inline Footnote Format

Footnotes are inserted directly using double square brackets e.g([[this is footnote]])

{
  "88:17": "Do the disbelievers not see how rain clouds are formed [[The word ibl can mean 'camel' as well as 'rain cloud'...]]"
}

3. Text Chunks Format

In chunks export format, text is divided into chunks. Each chunk could be a simple text or an object. Object can be either footnote or a formatting tag. This format is useful for applications can't directly render the HTML tags. Here is an example of Bridges` translation for Surah An-Nas , Ayah 6:

Above translation will be exported in chunks as:

<i class="s">(from the whisperers)</i>among the race of unseen beings<sup foot_note="81506">1</sup>and mankind.”


      [
      {"type":"i","text":"(from the whisperers)"}, // first chunk, should be formatted as italic
      "among the race of unseen beings", //second chunk in simple text
      {"type":"f","f":"81506","text":"1"}, // third chunk is a footnote,
      "and mankind.”"
      ]