https://bugs.documentfoundation.org/show_bug.cgi?id=163475
Eyal Rozenberg <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected], | |[email protected] --- Comment #2 from Eyal Rozenberg <[email protected]> --- I suggest we distinguish between the following: 1. The ability to render individual letters (like a ك or a ف) with some extension 2. The ability to indicate/force an extension of an individual letter (i.e. the equivalent of using the tatweel unicode character between letters, indicating the use of tatweel between them) - at the level of plain text and/or an ODF document 3. The user's ability to force tatweel of a letter - by typing or using something in the application UI 4. Justification algorithms which take into account the possibility of single-letter tatweel, in addition to inter-letter tatweel and other measures (spacing increases, slight narrowing of letters, hyphenation for scripts which support it etc.; see Laszlo Nemeth' talk in LOCon 2024 [1]). Lets clarify what we already have, what we're missing, what we (or rather, developers) should focus on, and in what order. Right now this issue looks a little messy to me. [1] : https://events.documentfoundation.org/libreoffice-conference-2024/talk/QEDSF7/ -- You are receiving this mail because: You are the assignee for the bug.
