OmarKhled
commented
8 months ago Verses (ayat) are handed to react in the (quran-uthmani-min) form (if multiple verses, then they're joined into a one string using the waqfa character - more on that later). Then the ayah gets segmented into small segments that each are displayed at it's respected time (timings of verse and segments are handed to react as well).
The segmentation of ayah is done using a string split operation that splits on these conditions (ordered by priority):
- there's a waqfa caharcter
,
,
(we joined ayahs with a waqfa character earlier so that there is a split on ayahs)
- there are N consecutive words with no waqfa (N is a constant determined by the screen size)
Let's take this ayah as an example:
after segmentation (suppose N = 5), it would look like this:
We can retrieve English translation for each ayah from alquran.cloud API. but, after retrieving translation of ayah, the translation should be mapped to the splitted segments, that when each segment is displayed on screen, it's translation is displayed as well.
The ayat mapping process is the most Indirect task in this issue.
If you have any recommendations for the mapping process, I'm all ears!
Currently Tafakor Quran verses (ayats) are only displayed in Arabic, targeting only Arab speakers. I believe that supporting English translation as well would contribute to the spread for more wider audience.
Brief action plan: