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.

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

FiraCode NF Retina not being recognized as a distinct font #744

Closed
mtsitzer opened this issue Dec 30, 2021 · 11 comments
Closed

FiraCode NF Retina not being recognized as a distinct font #744

mtsitzer opened this issue Dec 30, 2021 · 11 comments

Comments

@mtsitzer
Copy link

mtsitzer commented Dec 30, 2021

I'm seeing an issue with FiraCode NF Retina not being recognized as a distinct font.

After installing FiraCode NF (all faces), I see this:

This suggests its part of the FiraCode NF Family
image

But when I go into the fonts folder, I don't see Retina as a distinct font, nor do I see it as part of the family
image

Compare this with the standard (non Nerd Font) Fira Code:
image

Also, why does the standard Fira Code install give me specific font face options but FiraCode NF is singluar?
In MS Word:
image

Originally posted by @mtsitzer in #440 (comment)

@Finii
Copy link
Collaborator

Finii commented Dec 30, 2021

Word would be fixed with #717, at the moment the font grouping is wrong and all weights get the same name 😒

The Retina is not a separate font in the Fira we have in the src/unpatched-fonts/ I believe. Where exactly did you download your Fira-Originals?

If Retina has to be a different face, this could be fixed, but the original Fira I have does not suggest that.

See #717's name_parser_test2.known_issues line 82ff, the lines with - are current patching, the > are original font, + how it should look like.

image

Edit: Add last paragraph and image

@mtsitzer
Copy link
Author

I got the originals from https://github.com/tonsky/FiraCode
image

@Finii
Copy link
Collaborator

Finii commented Dec 30, 2021

Hmm, 6.2 has this naming scheme:
image

Retina is no other typographic Family here. It's also not called 'Retina Medium'; not sure why it turns up as such in your font folder (never looked into the font folder).

Apart from grouping, you real issue is that you can not access 'Retina' in VS, right?

@mtsitzer
Copy link
Author

mtsitzer commented Dec 30, 2021

Correct --- and in other applications as well (such as Word, Windows Terminal, etc.)

Interestingly, I'm checking on another PC (with Fira Code 5.2 Installed), and I see the same breakdown
image

image

@Finii
Copy link
Collaborator

Finii commented Dec 30, 2021

They (Fira) say Retina is a weight ;-)

image

I personally have no clue what Retina means.

@mtsitzer
Copy link
Author

Here's some description for Retina:
tonsky/FiraCode#872 (comment)

@Finii
Copy link
Collaborator

Finii commented Dec 30, 2021

Correct --- and in other applications as well (such as Word, Windows Terminal, etc.)

Unfortunately the fix is ... not hard but involves changing a lot fonts. In principle the PR (#717) is ready but I wanted to add more documentation and explanation stuff.

If you can self patch, maybe use that branch (git checkout feature/rewrite-setup_font_names) and patch with --parser given to font-patcher. That will result in more accurate naming...

@Finii
Copy link
Collaborator

Finii commented Dec 30, 2021

Here's some description for Retina

Ah great! Thank you!

So Retina is the Apple-Fanboy name for Book :-D

@mtsitzer
Copy link
Author

I'm good to wait for you to finalize 717. I just followed the rabbit hole a littler further than I'd intended, and figured I should make an issue out of it.

As for the "Retina" name --- yeah, I guess so (I don't use any apple products haha).

@Finii
Copy link
Collaborator

Finii commented Jan 13, 2023

Self-Patch this with --makegroups.
This will be the repo wide default with v3.0.0.

@Finii Finii closed this as completed Jan 13, 2023
@github-actions
Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a new issue, complete the issue template with all the details necessary to reproduce, and mention this issue as reference.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants