You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Documentation: Update IntelliJ IDEA Setup Instructions #416
For some reason, IntelliJ IDEA (v2020.3.2) does not recognize the fonts directory on Windows (10), so Cascadia Code will not show up by default in the font selection after default font installation.
A workaround which worked for me is to put the TFT-Files into the fonts directory of the IntelliJ IDEA installation, which is defaultly at the following path:
C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.3.2\jbr\lib\fonts
Thanks for the feedback! This appears to be an issue with how JetBrains IntelliJ IDEA registers what is a 'valid' font and is due to the metadata changes we made to Cascadia Code with the most recent release. While installing the font into the fonts directory of IntelliJ IDEA is a viable work around, it is on JetBrains to make sure their system is working correctly.
To give an update, it turns out that one of the name tables I updated is not compatible with the mechanism that JetBrains uses to load fonts into their software. After reviewing the situation, I decided to roll back the change as that'll let you (and anyone else!) be able to use the font faster. However, I've suggested to JetBrains that they need to fix their code :).
Activity
aaronbell commentedon Feb 18, 2021
Thanks for the feedback! This appears to be an issue with how JetBrains IntelliJ IDEA registers what is a 'valid' font and is due to the metadata changes we made to Cascadia Code with the most recent release. While installing the font into the fonts directory of IntelliJ IDEA is a viable work around, it is on JetBrains to make sure their system is working correctly.
I have filed a bug with them here.
zekroTJA commentedon Feb 18, 2021
Ah okay, that explains why it worked perfectly with my older installation of IntelliJ with an older version of Cascadia Code.
Tank you! :)
aaronbell commentedon Feb 24, 2021
To give an update, it turns out that one of the name tables I updated is not compatible with the mechanism that JetBrains uses to load fonts into their software. After reviewing the situation, I decided to roll back the change as that'll let you (and anyone else!) be able to use the font faster. However, I've suggested to JetBrains that they need to fix their code :).
I'll push a fix in the next release.
Fix issues in the Feb update (#410)
Update Cascadia Code to 2102.25
Update Cascadia Code to 2102.25 (#9295)
Update Cascadia Code to 2102.25 (#9295)
Update Cascadia Code to 2102.25 (#9295)