Tafheem-ul-Quran - Abul Ala Maududi translation for Surah An-Naml

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 An-Naml — Ayah 21

Jump to Ayah

← Previous Next →

27:21

لَأُعَذِّبَنَّهُۥ عَذَابٗا شَدِيدًا أَوۡ لَأَاْذۡبَحَنَّهُۥٓ أَوۡ لَيَأۡتِيَنِّي بِسُلۡطَٰنٖ مُّبِينٖ ٢١

I will inflict a severe punishment on him or maybe even slaughter him unless he comes forth with a convincing reason (for his absence)."¹

Footnotes

[1] The Qur’an always uses verb ‘to bring’ rather than verb ‘to give’ in association with charity; this should be pondered by the reader.
[2] Some people of the modern time say that the hud-hud (hoopoe) does not mean the bird commonly known by this name, but is the name of a man who was an officer in the army of Solomon. This claim is not based on any historical research in which they might have found a person named hud-hud included in the list of the officers of the government of the Prophet Solomon (peace be upon him), but they base their claim on the argument that the custom of naming human beings after animals is prevalent in Arabic as in other languages and was also found in Hebrew. Moreover, the work that has been ascribed to the hud-hud in the following verses and its conversation with the Prophet Solomon (peace be upon him) can, according to them, be only performed by a human being. But if one keeps in view the context in which this thing occurs in the Quran, it becomes evident that this is no commentary of the Quran but its distortion. After all, why should the Quran put the intellect and intelligence of man to the test by using enigmatic language? Why should it not clearly say that a soldier of the Prophet Solomon’s (peace be upon him) cavalry, or platoon, or communication department, was missing, whom he ordered to be searched out, and who came and gave this news and whom he dispatched on such and such a mission? Instead, it uses such language that the reader, from the beginning to the end, is compelled to regard it as a bird. Let us, in this connection, consider the parts in their sequence as presented in the Quran.

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.”"
      ]