Repository navigation
Incorrectly rendered in Jetbrains Webstorm 2019.2.3 #150
Description
Environment
Cascadia Code version number: 1910.04
Application (with version) used to display text: Jetbrains Webstorm 2019.2.3
OS platform and version: Windows 10
Screen resolution (i.e. 220dpi): 3840x2160
Any other software?
Steps to reproduce
Change the font setting in Webstorm to use Cascadia Code
Expected behavior
The text of the opened files should be rendered in a readable format
Actual behavior
Almost only strange characters are rendered (see attached screenshot)
Cascadia Code rendered in Webstorm:
Cascadia Code rendered in VSCode:
Activity
aaronbell commentedon Oct 9, 2019
I'm not able to repro this bug on my device.
It looks like there's some really weird swapping happening. Can you try uninstalling the font, redownloading, and re-installing? It might also be worth checking your customization in Webstorm.
aaronbell commentedon Oct 9, 2019
This may also be related to: microsoft/terminal#2979
DHowett-MSFT commentedon Oct 9, 2019
I dunno? On account of the version in Terminal is the same as the one in this repository, it isn’t likely to be why Webstorm/Goland aren’t happy with it.
aaronbell commentedon Oct 9, 2019
Maurits Lourens (@mslourens) Do you have a version of Terminal installed? And which version is it?
If he hasn't updated, it could be an older version that still has the older version, I wonder.
ForNeVeR commentedon Oct 9, 2019
These bugs usually happen when there're multiple versions of same font installed in the system.
Cascadia_1.ttf, something like that)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; please report such cases to JetBrains)
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 still persists, please tell JetBrains about that (preferably in a new YouTrack ticket).
In any case, nothing's wrong with the font itself: it is either an OS issue (with Windows Font Cache) or a JetBrains IDE / runtime issue. It is non-actionable from the font authors' side.
mslourens commentedon Oct 9, 2019
Friedrich von Never (@ForNeVeR) the steps you provided fixed the issue! Thanx all for your quick response. I will close the issue now.
Sherlock-Holo commentedon Oct 9, 2019
Friedrich von Never (@ForNeVeR) I try to delete
Cascadia.ttfandCascadia_0.ttffrom%LOCALAPPDATA%\Microsoft\Windows\Fonts\, it says system is using it.How can I do to delete them
ForNeVeR commentedon Oct 9, 2019
Sherlock Holo (@Sherlock-Holo), first of all: have you deleted the fonts in the "official" way, via Windows Fonts directory? After you've done that, they sometimes will delete automatically after restart. And sometimes you'll be able to delete them manually after system restart.
Sherlock-Holo commentedon Oct 9, 2019
Friedrich von Never (@ForNeVeR) I can't see this font in windows/fonts directory here
and I found it in
%LOCALAPPDATA%\Microsoft\Windows\Fonts\Sherlock-Holo commentedon Oct 10, 2019
I delete the font, uninstall windows terminal from UWP setting and reboot and install again, it works well now
miloush commentedon Aug 15, 2020
Any idea how having multiple versions of a font results in the mess in OP's screenshot?
ForNeVeR commentedon Aug 15, 2020
This is due to a bug in JVM font handling. As far as I understand it while debugging the issue, it somehow messes up the font metadata and the actual font glyphs: it uses the metadata from one font version, and the glyphs from another one, and they rarely match up.