Steps to reproduce
Starting from Windows insider build 16188, Edge has covered almost all we need for viewing PDF. But there is still a little problem.
ff will be rendered into a single ligature
ﬀ. Modern PDF viewers like Adobe Reader, SumatraPDF all render it back to
The problem is that if Edge doesn’t handle them, when we copy text from Edge, we will get
ﬀ. And there is a potential problem when searching such word.
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Steven K.”
Changed Assigned To to “Rick J.”
Changed Assigned To to “Amit K.”
Changed Status to “Won’t fix”
Thank you for providing this information about the issue. Edge is doing the right thing in preserving the ligatures in their form and not treating them as separate letters. Currently, we do not plan to release a fix for this problem.
The MS Edge Team
This problem affect the “read aloud” feature greatly.
It is nearly impossible to read a PDF that was compiled using LaTeX.
If you are not willing to fix this issue on the rendering level, maybe you are willing that these special tokens will be recognized and respected by your narrators?
By the way, here are more information about TeX ligatures: https://tex.stackexchange.com/a/33481
Currently using Microsoft Edge 42.17134.1.0.
Thanks for consideration,