https://bugs.winehq.org/show_bug.cgi?id=44826
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #60864|0 |1 is obsolete| | Attachment #60865|0 |1 is obsolete| |
--- Comment #18 from Nikolay Sivov bunglehead@gmail.com --- Created attachment 68992 --> https://bugs.winehq.org/attachment.cgi?id=68992 patch
This is the first iteration. Like I said it does not have fallback support for fonts with missing or incomplete feature set.
What's worth testing:
- Arabic rendering in general for obviously misplaced shapes; - multiple diacritic marks. AFAIK there are some formalized rules for visual stacking order, it would be interesting to see what happens on Windows too; - interaction with user features. Office allows additional features to be applied by the user, like stylistic sets. If that normally applies to Arabic fonts, it would be good to know if it's broken in some way.