In this series, we will consider how Arabic is and could be represented in a digital world. Our first, and likely most spectacular example is Muṣḥaf Masqaṭ al-Iliktrūnī, available at mushafmuscat.om.
This website is a showcase for the technology developed by DecoType, a company specialized in Arabic digital typography, in collaboration with the state of Oman. Just like a ruler would be a patron of the arts in medieval times and order a master calligrapher to make a lavish copy of the Koran, so Oman, in our time, ordered a masterful digital execution of that.
The website, then, should be enjoyed much like a coffee table book, as a showcase of the capabilities of DecoType’s technology, and much less as a rendering of the Koran that you should use intensively. What points to this is the ultra clean interface which gives no hints as how to use the website. (Some pointers given below).
At the heart of the philosophy of the DecoType technology is the intention that Arabic should be displayed as it ought to be, in accordance with the rules of orthography in so far as they are agreed upon. In fact, DecoType’s technology could easily be parsed to any other script, but Arabic is a particularly good example of its strengths. As we saw in a previous post, displaying Arabic in a digital environment is fraud with challenges and impossibilities. DecoType is able to circumvent all of those issues introduced by movable type and unicode. How they do it is fairly simple; instead of transmitting the text as text and allowing the computer of the user (called client side) to display that text by use of a font, they render the text into vector graphics (server side) and send those graphics. Niftily, they also send the text (in unicode) and invisibly transpose it over the graphics, so that you can still select the text and copy and paste it.
The result is a beautiful rendering of the Arabic text, and most importantly, an interface for the user to change the appearance of the words. By clicking a word, the possible permutations become visible – and only those shapes are visible which the ‘script grammar’ would allow.
The upside of this technique is obvious: there is ultimate flexibility in how to present the text and there is ultimate guarantee that the end user will see it the exact same way. When you need to be very precise, as is the case with a text with the importance of the Koran, this is a good way of doing it.
The downside is that the computers of both server and end-user need to crunch more numbers to display the text. Using Mushaf Muscat is a slow experience, regularly with loading times of several seconds. This has since the first publication improved much, and obviously if this technology would be implemented in text editing software the entire rendering process would happen on your own computer which solves the speed issue.
It seems to me, then, that for now its main advantage lies with publishers. The technology is used to print Arabic as correctly as possible. This is also clear from the fact that the website displays the Arabic in a traditional page-by-page display. Text on a computer has no need for pages. It can be chopped up in arbitrary lengths or shown all at once in one long, scrollable column. Mushaf Muscat is still thinking in pages, and concerned about the appearance of Arabic, not with the interactivity or usability. To call this an “electronic mushaf” is therefore, in my opinion, a misnomer. This is the same way publishers call a PDF version of a hard copy an “e-book”, whereas this label should be reserved for truly electronic books in a format such as EPUB or MOBI. It is, then, publishers mostly who can (and should) take advantage of DecoType’s technology.
Some notes on how to use it
On the right you can quickly jumpt to a juz of the Koran. At the top-right, the circular device allows you to jump to a specific sura. At the left you can go to a page, an aya (it will jump), or a sura-aya combination (highlighted in red). At the bottom-left, the triangle controls color codes for different parts of the Arabic text, the rasm, vocalization, and recital aids. There are also buttons to turn on/off additional signs. At the very bottom you are supposed to be able to download/upload a part of the Koran, but I do not think it is working.
When you click on the blue border you enter a zoomed mode showing both pages. Clicking on a page zooms in on that page. At the top-right you can exit these views.
The most important element of the interface is the ability to click any word. This will pop-out an elaborate menu in which you can select variations of writing the word, as far as the rules of the script grammar allow it.
Here is a video detailing some of these features:
And here is a long talk by Thomas Milo, owner of DecoType. Other talks by him are highly recommended too:
This post was edited on December 20, 2018, after a conversation with Thomas Milo.
The attached article may provide a perspective to the project.
For all clarity, I pasted the article in the Details box, in order to be able to communicate.
https://oumma.com/premiere-mondiale-coran-numerique-presente-a-mascate-oman/
Two minor remarks:
«… but its integration in, say, Microsoft Word, is not to be expected …»
Actually, this is something to blame Microsoft, Google, Apple for, not DecoType.
«The technology is used to print Arabic as correctly as possible. …»
This is imprecise. The technology is meant to lay out Arabic text correctly. Whether the laid out text, in a subsequent step, is sent to a screen or sent to a printer – the technology does not care. Two separate aspects, not one.
«… This is also clear from the fact that the website displays the Arabic in a traditional page-by-page display. Text on a computer has no need for pages.»
Again, two separate aspects, not one. There is no one-to-one correlation between ‹print vs screen› and ‹pagination vs scrolling›. When displaying text on screen, e.g. on a website, the designer may choose either ‹pagination› or ‹scrolling› for navigation. Neither of these is inherently more suited than the other. (Googling for these terms, ‹pagination› and ‹scrolling›, you will find that this is a rather old debate. https://thrivehive.com/pagination-vs-scrolling-great-website-debate/ lists advantages and disadvantages for each of them.) Hence if you conclude that
«To call this an “electronic mushaf” is therefore, in my opinion, a misnomer.»
then you are reading too much into a mere design decision. (I heard that there is a scrolling mode too.)
Thank you for these excellent remarks.
The Mushaf Muscat are 3 view modes:
1. Manuscript with flower-separated verses (default)
2. Printed edition mode (with number-separated verses): by clicking the margins
3. interactive mode: by clicking any white area.
View modes 1 and 2 are in _codex_ (not “pagination”) format, view 3 is in _scroll_ format.
The pages are fixed following the Mushaf Medina format, not because of a technical constraint. To support these fixed pages with their considerable variation in the amount text, a very powerful page formatting engine had to be developed.
This is a work in progress. It’s now presentable, but what’s on display are just a first few brush strokes.
This lecture at Stanford University, for a Silicon Valley audience, describes in short the interface, the underlying scholarly research as well as its technical characteristics.
[video src="https://www.decotype.com/oman/2017-08_Stanford_Face-Interface.mp4" /]
Thank you, really great stuff!
Finally, the Berlin-Brandenburg Academy of Sciences put the Corpus Coranicum Vorlesung 2017 online, that I was invited to present:
https://www.bbaw.de/mediathek/archiv-2017/corpus-coranicum-lecture-2017