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

Overpass Mono Duplication issue between Bold and SemiBold variants #265

Closed
Thammachart opened this issue May 8, 2018 · 5 comments
Closed

Comments

@Thammachart
Copy link

🎯 Subject of the issue

macOS's Font Book states that there is duplication in the Overpass Mono Nerd Font between Bold and SemiBold variants.

This issue exist on both Monospaced and Non-Monospaced glyphs versions.

Out of my observation, these two variants share the same PostScript Name on each version

  • OverpassMonoNerdFontComplete-Bold on Non-Monospaced version
  • OverpassMonoNerdFontCompleteM-Bold on Monospaced version

This issue does not exist on the upstream font (Overpass Mono)

🔧 Your Setup

  • Overpass Mono Bold Nerd Font Complete.otf
  • Overpass Mono SemiBold Nerd Font Complete.otf
  • Overpass Mono Bold Nerd Font Complete Mono.otf
  • Overpass Mono SemiBold Nerd Font Complete Mono.otf
  • macOS High Sierra 10.13.4

★ Optional

Non-Monospaced version

Bold Non-Mono

SemiBold Non-Mono

Monospaced version

Bold Mono

SemiBold Mono

@ryanoasis
Copy link
Owner

Thanks (especially for the details) 👍

Disclaimer: I cannot give any ETA, but this project will keep moving forward little by little! 😄

@alexbarton
Copy link

Probably this is related to #257?

@MarioRicalde
Copy link

I think this is the issue: #257 (comment)

@Finii
Copy link
Collaborator

Finii commented Jan 30, 2023

The family naming is broken, it has been fixed (use --makegroups when patching). It the moment only in effect for some selected fonts, but v3.0.0 will have it for all fonts. Closing this already.

@Finii Finii closed this as completed Jan 30, 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 Aug 14, 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

5 participants