kelea99
commented
1 year ago PO Priority: This is one of two top figgy priorities for the Large 3 year project for Middle East Manuscripts. After discussion with project team, it would be great to see this through to completion by the end of the 3 year project (2024)
eliotjordan
Summary
The project lead on an MSS project requires metadata to reflect what is on the manuscript. There is one particular word that users are not able to represent properly because an unwanted ligature is automatically displayed and there is no current work-around. This shows up all over the place, but is demonstrated in Structure Manager in the highlight reel (see link below).
Impact
The issue misrepresents what is in the manuscripts, and does not allow them to complete their task.
Priority recommendation
Sudden Priority Justification
Not a sudden priority.
Expected behaviour
A user enters the word "Allah" in an Arabic typeface without a ligature, and after they save it, the word still displays without the ligature.
Actual behaviour
A user enters the word "Allah" in an Arabic typeface without a ligature that indicates a double consonant. It looks as intended when entered, but after saving it the word shows up differently, with the "sheddha" (sp?) ligature displayed even though it was not entered. This also happens even in the browser location bar, so it may be that this is a font issue and a matter of choosing one that allows this.
Steps to reproduce behaviour
See highlight reel around 2:57
Screenshots
See highlight reel around 2:57
Relevant Info
Perhaps this thread can shed some light. It may simply be a font issue.