Using mintty, the screenshot shows "Meslo LG S DZ" but the other "Meslo"-fonts, "Droid Sans Mono", "Bitstream Vera Sans Mono" and "DejaVu Sans Mono" also look like this.

🎯 Subject of the issue

Initial issue description (from 23/May/2018) I use Meslo LG M for Powerline and want to use the Nerd Fonts patched version. I tried all Meslo LG M in the repository, but none of them appeared in the gnome-terminal's fonts list. they were listed in the system, thought (in the fonts application).

I also downloaded the original ones, without any patches, and they got listed.

Anyone has any clue about how to fix this?

Update 24/May/2018 I have also tried Droid Sans, and it is not being listed too. I downloaded Terminator to see if it lists them, and it did.

Update 31/May/2018 With other people experiencing the same issue with other fonts, the issue's title was updated from "Meslo fonts not being listed on gnome-terminal" to the current one, as suggested by @gargoyle.

🔧 Your Setup

• Meslo LG M forPowerline, trying to change to Meslo LG M Nerd Fonts
• Gnome terminal
• Ubuntu 18.04

Not sure what happened, but since updating my fonts to include the new icons, I'm getting some weird spacing between the powerline glyphs and regular text.

Using other fonts that have powerline support do not have this issue.

OS : Arch linux

been trying to completed the download for 2..0GB file size for 9 hours, but it keep on close-up the download connect around 1.5 -1.7GB, with the message below

curl: (18) transfer closed with 1529402169 bytes remaining to read

possible to make it resumeable? so that once the transfer closed up, it will be resume again

These small modifications to the font patching script take the separate font styles into account when generating the font family and font name of the generated fonts. This ideally consolidates all of the fonts under a single font family each as a unique font style when the patched fonts are installed.

I'm not fully aware of the standards used with regards to the dashes in the different strings that are assumed in this pull request so additional normalization may need to be done in order to prevent these changes from causing problems on fonts that have non-standard or incorrect metadata. I'm happy to put research into this if this is a desired modification to the script.

Great project Ryan. Thanks for including Hack with your patched releases.

It looks like your patching approach is removing the hints from the Hack ttf variants. This could lead to issues for some Linux distros and all Windows users. They are simple to restore if you would like to modify your releases (or for anyone who wants to do this on their own).

Use the following approach prior to the font installs:

• Install ttfautohint
• Grab our autohint.sh script and ttfautohint Control Instructions Files (Hack-*-TA.txt) from this directory of the Hack repository https://github.com/chrissimpkins/Hack/blob/master/postbuild_processing/tt-hinting
• Modify the infile and outfile paths in the autohint.sh shell script based upon the Nerd Fonts release file names (and outfile path of your choice)
• chmod +x autohint.sh
• Execute ./autohint.sh to restore the hints.

These hints may/likely will change with new Hack releases so it is necessary to use Control Instruction Files that are part of the same Hack release that you patch.

🎯 fi shows as a telphone with Inconsolata NF

Type file, and you see <telephone symbol>li

🔧 Your Setup

• sudo scoop install inconsolata-nf
• windows terminal
• Windows 10 .19041

★ Optional

Description

TL;DR - See "What does this Pull Request (PR) do?" below

I was having problems getting many of the monospace fonts to work under windows. Specifically, the fonts were not being detected as monospace, so they wouldn't work under MobaXterm or GVim.

Unfortunately, getting things to work properly with both Windows and MacOS turned out to require a lot of trial and error.

Some of the fun I discovered:

OTF formatted monospace fonts are detected as such by Windows. So, initially I added the option to modify the extension, forced the fonts I wanted to be OTF, and called it a day. Unfortunately, I discovered that TTF fonts converted to OTF had a strange problem with MacOS. Specifically glyph number 0xE0C8 would be somehow skipped, and all subsequent glyphs would be mis-numbered.

To get TTF fonts detected properly as monospace under Windows, I found that EVERY glyph must be assigned the same width. This includes empty/blank glyphs, and often requires the source font glyphs to be modified in this way.

When using the windows-compatible named fonts on MacOS, I found that some font families where not being handled properly. Different weights of the same font would conflict with each other. This was caused by the font name being the identical across the font weights. I solved this by tweaking how the windows name is generated, and ensure it is unique for each font weight. IMHO, it would be better to have only one naming convention that works everywhere. This would eliminate half of the binary fonts and generation time.

I also wanted to preserve the aspect ratio of the glyphs when generating a monospace font, but wanted the powerline separators to remain line-height. After trial and error, I found that setting the ymax/ymin/height based upon the os2 parameters to be more consistent than scanning the line-draw characters.

I ended up doing some minor refactoring (normalizing indent amounts, removing unused variables, etc) in the process, so I completely understand if my changes are too drastic for a pull.

Requirements / Checklist

• [x] Read the Contributing Guidelines
• [x] Read or at least glanced at the FAQ
• [x] Read or at least glanced at the Wiki
• [x] Scripts execute without error (if necessary):
  • If any of the scripts were modified they have been tested and execute without error, e.g.:
    • ./font-patcher Inconsolata.otf --fontawesome --octicons --pomicons
    • ./gotta-patch-em-all-font-patcher\!.sh Hermit
• [ ] Extended the README and documentation if necessary, e.g. You added a new font please update the table

What does this Pull Request (PR) do?

Improves generation of monospace fonts so they properly work under windows

How should this be manually tested?

Generate some fonts.

Any background context you can provide?

See description.

What are the relevant tickets (if any)?

Screenshots (if appropriate or helpful)

Subject of the issue

Text and glyphs at 14pt:

text at 14pt, glyphs at 18pt:

The glyphs seem to be either shifted on x and y axis, or just their size doesn't match text, or even both.

Your Setup

OSX, iTerm2, tmux.

Subject of the issue

I've been trying all day today to patch correctly Monaco and Menlo Nerd Complete **Mono**, but I've failed spectacularly. I've been trying different options provided by the script but I wasn't able to a correctly display font on my terminal.

First, I've tried to patch the original font from my fonts folder (System/Library/Fonts/), but I wasn't able to make it in a way to display the correct glyphs or correctly aligned.

Then, I found that @taohex already has done the patching, thus I downloaded the fond and tried to transform to mono, the closest thing I've been able to yield is this

As you can see the Powerline extra symbols are slightly bigger than the fond, and I can't figure out how to fix it.

I've got the same result with the Menlo font.

If you can lend me a hand I would be grateful. I also think that, if possible, if you can add those fonts to the repository would be great. Monaco is the default font of rStudio and now it's possible to call the terminal from within the app so I would like to use zsh with nerd fonts to make similar to my setup in iTerm2.

Your Setup

• I'm trying to patch mainly Monaco and also Menlo.
• I use iTerm2 as my main terminal, but I'm trying to patch Monaco because I want to use it on rStudio. I need the fonts in mono because rStudio uses only mono fonts.
• I'm using Mac OS X 10.11.6 El Capitan and I've dowloaded fontforge with homebrew.

🗹 Requirements

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

🎯 Subject of the issue

Experienced behavior: The CaskaydiaCove Font linked in the release 2.1.0 doesn't contain German umlauts.

Expected behavior: The CaskaydiaCove Font should contain German umlauts as the original Cascadia Code Font does contain them. Furthermore, running fontforge -script font-patcher src/unpatched-fonts/CascadiaCode/Regular/CascadiaCode-Regular.otf -c --mono --out . generates a font which contains German umlauts as well.

Example symbols: German Umlauts are affected. However, I'm not sure whether there are more accent characters which are affected.

• German umlauts äöü

Update: All accent characters are missing

🔧 Your Setup

• Which font are you using (e.g. Anonymice Powerline Nerd Font Complete.ttf)?
  • Caskaydia Cove Regular Nerd Font Complete Mono
  • Where did you get the file from (download link, self patched, source downloaded from link...)
    • This repo's v2.1.0 download: https://github.com/ryanoasis/nerd-fonts/releases/tag/v2.1.0
• Which terminal emulator are you using (e.g. iterm2, urxvt, gnome, konsole)?
  • Windows Terminal
• Are you using OS X, Linux or Windows? And which specific version or distribution?
  • Windows

★ Screenshots (Optional)

Ordinary characters compared to their accent counterparts

The same in Windows Terminal

🗹 Requirements

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

🎯 Subject of the issue

Experienced behavior: CaskaydiaCove Windows Compatible NF does not show up for conhost.exe, and only the Mono fonts (no ligatures) show up for Windows Terminal. Looking at existing bugs, this has been reported quite a few times and was apparently fixed, though subsequent comments say it still occurs.

Looking at #994 it seems this could be because OTF isn't well-supported. Could a TTF download be offered as well, if not a combination of OTF and TTF. IIRC, some fonts used to be distributed that way: both in an archive, though I may be thinking of a different forge.

Expected behavior: CaskaydiaCove NF fonts show up everywhere I'd like to use them: conhost.exe, wt.exe, code.exe, etc.

Example symbols: N/A

🔧 Your Setup

• Which font are you using (e.g. Anonymice Powerline Nerd Font Complete.ttf)?
  • Several in a font family e.g., "Caskaydia Cove Nerd Font Complete Windows Compatible Regular.otf"
• Where did you get the file from (download link, self patched, source downloaded from link...)
  • This site via direct download.
• Which terminal emulator are you using (e.g. iterm2, urxvt, gnome, konsole)?
  • conhost.exe and wt.exe
• Are you using OS X, Linux or Windows? And which specific version or distribution?
  • Windows

★ Screenshots (Optional)

Regarding using font patcher, does it have dependencies and need that the whole repository be cloned? Please add some information to the readme page.

🗹 Requirements

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

🎯 Subject of the issue

Experienced behavior: No icon (other icons work, atleast most of them)

Expected behavior: Should be rendered Example symbols:

nf-seti-go2

🔧 Your Setup

• Which font are you using (e.g. Anonymice Powerline Nerd Font Complete.ttf)? nerd-fonts-jetbrains-mono v2.2.2
• Where did you get the file from (download link, self patched, source downloaded from link...)
  • arch repos
• Which terminal emulator are you using (e.g. iterm2, urxvt, gnome, konsole)?
  • alacritty
• Are you using OS X, Linux or Windows? And which specific version or distribution?
  • Linux, Arch

★ Screenshots (Optional)

🎯 Subject of the issue

Experienced behavior: The package manager instructions for installing Hack for Fedora say to enable the heliocastro/hack-fonts copr project, but it doesn't exist.

Expected behavior: N/A

Example symbols: N/A

🔧 Your Setup

None of these are applicable as you can't install it.

★ Screenshots (Optional)

N/A

[why] When we crate a font we take the OriginalName, add "Nerd Font" and which patches we applied, and add "Mono" if --mono has been specified:

OriginalName Nerd Font Complete Mono
OriginalName Nerd Font plus Weather Mono

But the 'Mono' part is quite important, but this scheme will put it in a place where it is easily out of view or has been removed (to keep the name short).

This truncation is especially bad on Windows Compatiple and when the user installs both the 'Nerd Font' and the 'Nerd Font Mono':

SomeVeryLongFontName Nerd Font Complete
SomeVeryLongFontName Nerd Font Complete Mono

become after truncation

SomeVeryLongFontName Nerd Font Comp.ttf
SomeVeryLongFontName Nerd Font Comp.ttf

[how] Always put the "Mono" directly after "Nerd Font" and all the other name components come later.

Requirements / Checklist

• [x] Read the Contributing Guidelines
• [x] Verified the license of any newly added font, glyph, or glyph set

What does this Pull Request (PR) do?

Change the Family/Full/File name of all Nerd Font Mono fonts: Pull the Mono directly after the Nerd Font

How should this be manually tested?

Any background context you can provide?

What are the relevant tickets (if any)?

Screenshots (if appropriate or helpful)