Skip to main content
11 events
when toggle format what by license comment
Nov 20, 2019 at 15:00 history tweeted twitter.com/StackSoftEng/status/1197167872314871808
S Nov 12, 2019 at 4:03 history edited Theraot CC BY-SA 4.0
Grammar fixed
S Nov 12, 2019 at 4:03 history suggested Łukasz D. Tulikowski CC BY-SA 4.0
Grammar fixed
Nov 11, 2019 at 16:24 review Suggested edits
S Nov 12, 2019 at 4:03
Nov 11, 2019 at 1:57 answer added Lance Pollard timeline score: 5
Nov 10, 2019 at 17:27 comment added Jim DeLaHunt In the above, "don't rendering" should be "font rendering". Auto-correct let me down, then I lost internet connectivity for long enough to lose my chance to edit.
Nov 10, 2019 at 17:19 comment added Jim DeLaHunt You ask "how the font rendering engine renders Arabic text", as if there is only one "don't rendering engine". In fact, there are multiple such engines (e.g. the current Windows engine, older Windows engines, the current macOS engine, the current Android engine, the extremely fine engine from DecoType, etc. etc.) There could be different best answers for each of these engines. Additionally, there is an Arabic writing tradition based on calligraphy, which will differ from the approximations by the various engines. I don't think this question has a single factual answer.
Nov 10, 2019 at 15:25 review Close votes
Nov 18, 2019 at 3:05
Nov 10, 2019 at 14:55 answer added gnasher729 timeline score: 1
Nov 10, 2019 at 14:48 comment added gnasher729 This is not "justified according to Western conventions", it is "justified according to the code in one specific typesetting system". Which typesetting system is it? TextEdit on my Mac definitely stretches the glyphs for Arabic text, not the spaces, and so does Pages. You can expect the same on most macOS and iOS applications, and I wouldn't be surprised if Android got it right as well.
Nov 10, 2019 at 14:16 history asked Lance Pollard CC BY-SA 4.0