- From: arabicdeconstructor via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Jan 2020 18:31:02 +0000
- To: public-i18n-archive@w3.org
arabicdeconstructor has just created a new issue for https://github.com/w3c/alreq: == Inline dagger alif and hamza == I have been searching online for unicode/rendering solutions for displaying fully vowelized Arabic text. So for example, I'm trying to find a solution to display "dagger alif" after a character if it already has a fatha. And also a way to write inline hamza correctly. Example:  I have found a few fonts that handle the dagger alif correctly (Calibri Arabic, Arabic Typesetting, Amiri, KFGQPC Hafs but not KFGQPC Uthman Taha Naskh) by just using u+0670 Arabic superscript alef directly after a fatha. For the inline hamza, it seems all fonts require a tatweel u+0640 and then a Arabic hamza above u+0654. A tatweel also solves the dagger alif issue in words like هَـٰذَا but not if the character does not join as in ذَٰلِكَ. I am sometimes able to get around it by combining the dagger alif with a no-break space (NBSP, NNBSP, ZWNBSP, word joiner u+2060) but this is quite flaky and does not always render correctly. I am looking for a simplified Arabic font similar to Calibri Arabic that I can use inline with English text without increasing line spacing a whole lot. Unfortunately Calibri Arabic is only easily accessible to Windows users. I was wondering if there is a good solution for the problem so that I can use with more easily available simplified Arabic web fonts. By the way there is some existing discussion regarding these issues but I’m not sure if there is any resolution: https://lists.arabeyes.org/archives/general/2004/June/msg00309.html https://unicode.org/L2/L2013/13226-koran-ortho.pdf Please view or discuss this issue at https://github.com/w3c/alreq/issues/213 using your GitHub account
Received on Wednesday, 29 January 2020 18:31:03 UTC