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

Patched Fira Code height does not match original font on Windows Terminal #885

Closed
3 tasks done
brneor opened this issue Aug 19, 2022 · 11 comments
Closed
3 tasks done

Comments

@brneor
Copy link

brneor commented Aug 19, 2022

🗹 Requirements

  • I have searched the issues for my issue and found nothing related and/or helpful
  • I have searched the FAQ for help
  • I have searched the Wiki for help

🎯 Subject of the issue

Experienced behavior:

Patched Fira Code shows different height from original font (and older release 'Fura Code') on Windows Terminal when set to specific font size. Happens with both regular and retina variant when font size is set to 9.

Expected behavior:

Patched Fira Code should match the original font height.

🔧 Your Setup

  • Fira Code Regular Nerd Font Complete Windows Compatible.ttf
    • Tried source downloaded from link and self patched.
  • Windows Terminal (release and preview)
  • Windows 11

★ Screenshots (Optional)

Original Fira Code:
image

Patched Fira Code:
image

Old FuraCode (from 2.1 release):
image

@Finii
Copy link
Collaborator

Finii commented Aug 19, 2022

Suspect #761

Maybe that should also go into 2.2.0 🤔

@brneor
Copy link
Author

brneor commented Aug 19, 2022

@Finii I can try this branch and report back

@brneor
Copy link
Author

brneor commented Aug 19, 2022

@Finii patched the font using the suggested branch and everything looks almost fine now! Tried both regular and retina variants.

image

FiraCode NF Retina still looks of in bold (but also old FuraCode).

Regular:
image

Retina:
image

@brneor
Copy link
Author

brneor commented Jan 19, 2023

@Finii @ryanoasis this got partially fixed in a recent release. The bold issue in "Retina" variant still persists. Just FYI.

@Finii
Copy link
Collaborator

Finii commented Jan 27, 2023

Thanks for the feedback.

@Finii Finii added this to the v3.0.0 milestone Jan 27, 2023
@Finii
Copy link
Collaborator

Finii commented Jan 27, 2023

Marked this 3.0.0 to not forget it 😬

@Finii Finii modified the milestones: v3.0.0, v3.0.1 May 5, 2023
@Finii
Copy link
Collaborator

Finii commented May 8, 2023

Ah, I think now I get it...

You know that Retina is just a weight, like Regular, Light, Bold, or Heavy?

Plus only Regular, Italic, Bold and BoldItalic form a classic RIBBI group.

If you use Retina the application does not have a Bold version of that. It either has to create one on the fly (also done with missing Italic variants that are Obliqued automatically if need be), or you need to have a separate setting for 'which font to take for <Bold>'.

From the images it seems that Windows Terminal takes some backup font instead.

As there is no Retina-Bold (whatever that would mean, its the same as to say the weight is Light-Heavy?!), there is nothing we can do here.

With some terminals you can adjust all 4 fonts individually in the settings. But I guess that is not possible with Windows Terminal. What one could do is creating a RIBBI group from Retina and Bold, but that would involve changing the font's metadata.

Then I tried to output bold text in the ordinary Windows Terminal and could not manage it at all. There is the 'Use really bold and not bright color' setting, but that still did not work.

So I can not really reproduce, but Retina just does not have an associated 'Bold', whatever the Terminal is doing in your case. What does it do if you select a script font that does not have bold neither italic?

I fear the problem in your case is that you use Fedora in this Windows Linux Subsystem, and that muddles up all the font engines (I guess).

I take this off 3.0.1 again, and am inclined to close it. But maybe you have more information.

@Finii Finii removed this from the v3.0.1 milestone May 8, 2023
@brneor
Copy link
Author

brneor commented May 8, 2023

@Finii thank you for the explanation.

I tried to reproduce the issue again so I could provide more information but looks like it does not happen in v3.0... But IIRC, it happened in Windows Terminal when using just powershell.

@Finii
Copy link
Collaborator

Finii commented May 8, 2023

I searched Windows Terminal and there we several (closed) Issues about BOLD, maybe it was a bug there.

So I close this now, feel free to reopen if it re-surfaces :-)

@Finii Finii closed this as completed May 8, 2023
@Finii
Copy link
Collaborator

Finii commented May 8, 2023

With closing we are in the one digit Issues range 🎉

image
Bugs of Nerd Fonts and the time to close them; left side is Dec. 2014, right side is May 2023

image
Zoom into last days

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 Nov 13, 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