How to disable Studio automatically combining letters into ligatures?

I recently upgraded from Studio 2019 to 2022. I suddenly realized that Studio is automatically combining "fi" and "ti" into one-character ligatures (and probably others too). It happens as I type, and it's also done on the imported text. It's not there in the original. I see that it only happens with certain fonts.

I don't want this. It makes it difficult to edit, since I'm always expecting to be able to delete one of the letters or type inbetween them. Also, I don't know if my client wishes this. I haven't been able to figure out how to turn this off. Searching turns up nothing. Can anyone help?

emoji
Parents
  • Hello there, this is a bug on our side. For some reasons, yet unknown and out of our control, as the font API is the same that is used by MS Word, we get the two letters merged by default into a ligature. Until we investigate this properly, a workaround would be to place the caret at the tail end and press backspace to delete the "i" character, then type in what you want and add back manually the "i" letter. 

    One thing to note: if you were to use an actual ligature, not the mistake the API does here, then you wouldn't be able to type in between the two letters or delete them separately as they are treated as one and we currently support what the font has setup as default. This is the same for MS Word, with the exception that they have indeed a possibility to turn this off.

    emoji
  • Thanks for your reply and your suggestion.

    I must correct you about Word: I'm using Word 2019 with ligatures enabled. (I see that it's a ligature, which is different from when ligatures are turned off.) Nevertheless, when I move the cursor through the ligature, it's two steps (not one). I can position the cursor in between the ligature and type (or delete). I can also use the delete key to delete the first letter.

    So I'm not sure what you mean by "not the mistake the API does here". The mistake the API does is indeed that it's not like Word. If you thought that the behavior you describe is correct (which it isn't), then I wonder what you meant that the mistake in Studio currently is? Just that you can't turn off ligatures separately?

    emoji
Reply
  • Thanks for your reply and your suggestion.

    I must correct you about Word: I'm using Word 2019 with ligatures enabled. (I see that it's a ligature, which is different from when ligatures are turned off.) Nevertheless, when I move the cursor through the ligature, it's two steps (not one). I can position the cursor in between the ligature and type (or delete). I can also use the delete key to delete the first letter.

    So I'm not sure what you mean by "not the mistake the API does here". The mistake the API does is indeed that it's not like Word. If you thought that the behavior you describe is correct (which it isn't), then I wonder what you meant that the mistake in Studio currently is? Just that you can't turn off ligatures separately?

    emoji
Children
No Data