Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Documentation: Update IntelliJ IDEA Setup Instructions #416

Closed
zekroTJA opened this issue Feb 18, 2021 · 3 comments · Fixed by #410
Closed

Documentation: Update IntelliJ IDEA Setup Instructions #416

zekroTJA opened this issue Feb 18, 2021 · 3 comments · Fixed by #410

Comments

@zekroTJA
Copy link

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

It would be really nice if this would be added to the Installation Instructions for IntelliJ in the Wiki Page.
@aaronbell
Copy link
Collaborator

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
Copy link
Author

Ah okay, that explains why it worked perfectly with my older installation of IntelliJ with an older version of Cascadia Code.
Tank you! :)

@aaronbell
Copy link
Collaborator

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.

@aaronbell aaronbell mentioned this issue Feb 24, 2021
Merged
7 tasks
DHowett pushed a commit that referenced this issue Feb 25, 2021
@aaronbell
Fix issues in the Feb update (#410)
f91a925 
A small set of fixes that resolves a couple of new bugs introduced in the latest version, plus other fixes I have been working on. 

## PR Checklist
* [x] Closes #406 - updated anchor type to lock with the other equals-related ligatures
* [x] Closes #408 - corrected component used for glyph to align with Unicode
* [x] Closes #412 - updated locl features removing iacute_j ligature and Catalan substitution
* [x] Closes #414 - increased overlaps of middle glyph for arrow ligatures
* [x] Closes #415 - reduces width of macronbelow
* [x] Closes #416 - rolls back name ID 4 modification as JetBrains cannot process it correctly
* [x] Closes #428 - rolls back variation of the underline to prevent MVAR table generation

## Detailed Description of the Pull Request / Additional comments

Full changelist:
- Repositioned tilde in related ligatures. Previously it was higher than the standard one.
- Added missing vietnamese anchors on acute and grave (futureproofing). 
- Corrected / made consistent greater & less positioning in </> and <$> related ligatures.
- Otherwise reviewed hinting
DHowett added a commit to microsoft/terminal that referenced this issue Feb 25, 2021
@DHowett
Update Cascadia Code to 2102.25
90936fe 
This update fixes some issues in Cascadia Code's February update:

microsoft/cascadia-code#406 - updated anchor type to lock with the other equals-related ligatures
microsoft/cascadia-code#408 - corrected component used for glyph to align with Unicode
microsoft/cascadia-code#412 - updated locl features removing iacute_j ligature and Catalan substitution
microsoft/cascadia-code#414 - increased overlaps of middle glyph for arrow ligatures
microsoft/cascadia-code#415 - reduces width of macronbelow
microsoft/cascadia-code#416 - rolls back name ID 4 modification as JetBrains cannot process it correctly
microsoft/cascadia-code#428 - rolls back variation of the underline to prevent MVAR table generation

Full changelist:
* Repositioned tilde in related ligatures. Previously it was higher than the standard one.
* Added missing vietnamese anchors on acute and grave (futureproofing).
* Corrected / made consistent greater & less positioning in </> and <$> related ligatures.
* Otherwise reviewed hinting
@DHowett DHowett mentioned this issue Feb 25, 2021
Merged
DHowett added a commit to microsoft/terminal that referenced this issue Feb 25, 2021
@DHowett
Update Cascadia Code to 2102.25 (#9295)
cb03b97 
This update fixes some issues in Cascadia Code's February update:

microsoft/cascadia-code#406 - updated anchor type to lock with the other equals-related ligatures
microsoft/cascadia-code#408 - corrected component used for glyph to align with Unicode
microsoft/cascadia-code#412 - updated locl features removing iacute_j ligature and Catalan substitution
microsoft/cascadia-code#414 - increased overlaps of middle glyph for arrow ligatures
microsoft/cascadia-code#415 - reduces width of macronbelow
microsoft/cascadia-code#416 - rolls back name ID 4 modification as JetBrains cannot process it correctly
microsoft/cascadia-code#428 - rolls back variation of the underline to prevent MVAR table generation

Full changelist:
* Repositioned tilde in related ligatures. Previously it was higher than the standard one.
* Added missing vietnamese anchors on acute and grave (futureproofing).
* Corrected / made consistent greater & less positioning in </> and <$> related ligatures.
* Otherwise reviewed hinting
DHowett added a commit to microsoft/terminal that referenced this issue Feb 25, 2021
@DHowett
Update Cascadia Code to 2102.25 (#9295)
f5f330a 
This update fixes some issues in Cascadia Code's February update:

microsoft/cascadia-code#406 - updated anchor type to lock with the other equals-related ligatures
microsoft/cascadia-code#408 - corrected component used for glyph to align with Unicode
microsoft/cascadia-code#412 - updated locl features removing iacute_j ligature and Catalan substitution
microsoft/cascadia-code#414 - increased overlaps of middle glyph for arrow ligatures
microsoft/cascadia-code#415 - reduces width of macronbelow
microsoft/cascadia-code#416 - rolls back name ID 4 modification as JetBrains cannot process it correctly
microsoft/cascadia-code#428 - rolls back variation of the underline to prevent MVAR table generation

Full changelist:
* Repositioned tilde in related ligatures. Previously it was higher than the standard one.
* Added missing vietnamese anchors on acute and grave (futureproofing).
* Corrected / made consistent greater & less positioning in </> and <$> related ligatures.
* Otherwise reviewed hinting

(cherry picked from commit cb03b97)
DHowett added a commit to microsoft/terminal that referenced this issue Feb 25, 2021
@DHowett
Update Cascadia Code to 2102.25 (#9295)
507a846 
This update fixes some issues in Cascadia Code's February update:

microsoft/cascadia-code#406 - updated anchor type to lock with the other equals-related ligatures
microsoft/cascadia-code#408 - corrected component used for glyph to align with Unicode
microsoft/cascadia-code#412 - updated locl features removing iacute_j ligature and Catalan substitution
microsoft/cascadia-code#414 - increased overlaps of middle glyph for arrow ligatures
microsoft/cascadia-code#415 - reduces width of macronbelow
microsoft/cascadia-code#416 - rolls back name ID 4 modification as JetBrains cannot process it correctly
microsoft/cascadia-code#428 - rolls back variation of the underline to prevent MVAR table generation

Full changelist:
* Repositioned tilde in related ligatures. Previously it was higher than the standard one.
* Added missing vietnamese anchors on acute and grave (futureproofing).
* Corrected / made consistent greater & less positioning in </> and <$> related ligatures.
* Otherwise reviewed hinting

(cherry picked from commit cb03b97)
@FUJonathan FUJonathan mentioned this issue Sep 3, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix issues in the Feb update aaronbell/cascadia-code
2 participants
@aaronbell @zekroTJA