https://bugs.documentfoundation.org/show_bug.cgi?id=157922
--- Comment #9 from خالد حسني <[email protected]> --- (In reply to medmedin2014 from comment #8) > (In reply to خالد حسني from comment #5) > > A workaround is to strip the AAT table from the font, using something like > > (ttx comes from FontTools Python package): > > > > $ ttx -x morx -x feat -x prop -x lcar AALMAGHRIBI.ttf > > $ ttx AALMAGHRIBI.ttx > > > > This should result in a AALMAGHRIBI#1.ttf file, installing it instead of the > > original AALMAGHRIBI.ttf file should fix the issue. > > I'm not an expert in fonts, but the effect of removing such part from the > font wouldn't disable some advanced font capabilities ? These tables are unused by MS text layout engine, so stripping them makes the font behave like it does in MS applications, which seems to be the only platform it was tested against (the font is broken also om macOS unless the tables I mentioned are removed). > Some extreme and complex usage of that Maghrebi font is the writing of whole > Muhammadi Qur’an, with the narration of Warsh on the authority of Nafi’, and > I think (not sure) it was primarily done on Apple software to benefit from > those complex font features. > > https://play.google.com/store/apps/details?id=info.vacof.quranma The screenshots of this app show handwritten calligraphy nit a computer font (look at the same letter, e.g. isolated alef, at different places and you will see variations that result from handwriting). -- You are receiving this mail because: You are the assignee for the bug.
