Hi everybody,
please, is that possible to make an OT feature that behaves like standard ligature feature, but when the ligature is shown it can be copied? When 'fl' is turned into ligature, the letters 'f' and 'l' are copied, in my case I need to copy the ligature itself. So in this 'fl' example I would be pasting 'fl' (U+FB02) after copying the ligature and not 'fl' (U+0066 U+006C) as it is normally. Thanks for any ideas for workarounds as I guess it won't go purely OT.
0
Comments
yes I thought so, but there must be a work-around for this, no?
Why do you need them copied as 0xFB02, btw?
My suggestion involved changing the text input as well. It should affect everything... unless the app/OS is so clever as to map from U+FB02 back to the component characters, without the help of the initial text stream or the font in doing so.
Entirely possible, but not typical, in my experience.
Also, not all ligatures have a Unicode value. Actually it's quite the opposite: your example "fl" is one of the very few (and a decision oft regretted ever since). The OT feature you describe is exactly the reason why ligatures don't require unique Unicode codepoints. It also means they are absolutely font-dependent.
The original poster’s description assumes and requires that the ligature be encoded. But it is a good point that only a few have a “real” Unicode (five common Latin ligatures, plus some for other writing systems). We do not know if the font has more than those, or not. That would be an important clarification.