-
Notifications
You must be signed in to change notification settings - Fork 807
Double installation issue
Does your Cascadia Code look something like the above where glyphs overlap one another? This is a common problem when multiple versions of the font are installed in the system. Thanks to ForNeVer for an analysis and fix for this problem copied below.
- It could happen if you have both TTF and OTF versions of the same font
- It could happen if you have multiple versions of the same TTF font, which could happen in this case:
- you have some program that uses the font
- you're trying to update the font
- Windows is unable to do that (because the font file is still open), so it leaves the old file forever
- the updated font gets installed with the new name (e.g.
Cascadia_1.ttf
, something like that) - It could happen if the Windows font cache is corrupted (extremely rare, I wasn't able to observe that in the wild and only causes in specific circumstances in my lab environment)
How to fix that issue:
-
Check if you have multiple system-wide installations of the font:
dir C:\Windows\Fonts\Cascad*
-
Check if you have multiple user-specific installations of the font:
dir %LOCALAPPDATA%\Microsoft\Windows\Fonts\Cascad*
(if you have both system-wide and the user-specific font, it could cause the issue, too)
If you really have multiple font versions installed, then close all programs that could use them, then uninstall the font in question, and manually clean up the remaining font files; after that, install the font to only one place (either system or user).
-
If everything seems okay but the font still looks wrong, you could try to flush the Windows Font Cache
If the issue persists, please contact the software developer where the issue is being observed and report the bug.
In any case, nothing's wrong with the font itself.
If you continue to run into issues, please feel free to reach out to the team!