All ttf files are OK.
And otf files of https://github.com/powerline/fonts are OK.
But otf files of this project cannot be opened on Windows7.
Does anyone else has this problem?

I know with enough googling someone can figure out how to install the patched fonts, but it would be nice to provide this in the README. Right now, I reloaded my font-cache and I still can't access the new fonts, so it really isn't as easy to setup as it could be.

Even better would be to create an install script that would let you select fonts that would auto download and install.

I found an easier workflow on OSX to patch fonts:

brew install fontforge
fontforge -script font-patcher /path/to/the/font

doing that you don't have to install older python only to patch fonts, as "fontforge" has already an embedded python environment

I'm trying to use M+ 1m light Plus Nerd File Types Mono Plus Font Awesome Plus Octicons Plus Pomicons with the https://github.com/bhilburn/powerlevel9k prompt for zsh. It has mappings to https://github.com/gabrielelana/awesome-terminal-fonts, which I assumed would work with nerd-fonts. This seems not to be the case, as some of the icons don't work: Powerlevel9k/powerlevel9k#95.

I'm new to powerline/nerd-fonts/etc, so I'm not sure why this is the case? Is this project mapping codepoints differently than awesome-terminal-fonts? What's the formula for constructing that mapping, and what's the best way for me to sync up powerline9k with the nerd-fonts font I'd like to use?

splitting Investigate and fix Terminess (Terminus) and ProggyClean glyph issues #16 into 2 issues (#16 and this one)

I've tried it both in gvim and terminal vim (URxvt), where it looks the same:

FiraCode

Basically FiraMono with programming ligatures.

This has actually already been patched by someone and posted online 😄 but it would be nice to add this font officially.

add pomicon glyphs per gabrielelana/pomicons/issues/2

• add option to add pomicons
• re-patch all fonts with a version that includes pomicons

The official unpatched PragmataPro supports many ligatures for programming. Using the font produced by the patcher produces file type icons, but ligatures are lost.

Hi,
First of all thanks a lot for this project.
Recently, I tried to patch the font Fantasque Sans Mono.
The problem is that on ArchLinux the fontforge library has bindings for python3 by default( python3 is the default python). So, running with ./font-patcher ... didn't work.
I had to use the fontforge program directly - fontforge -script font-patcher --fontawesome --careful FantasqueSansMonoRegular.ttf.
But the script is in python2. Using 2to3 on the file gave an attribute error. I found the problem and everything worked.

I suggest including a python3 version of the script in the repo. I am attaching it - it will save a lot of hassle for many people.

Besides, how about including Fantasque Sans Mono in the default patched fonts set ?

font-patcher.txt

Installing multiple font variants (bold, semibold, light, etc) on OSX using fontbook results in warnings and the font variants are all in separate "font families" ..

I tried installing multiple patched fonts (both Hack and Source Code Pro) so that should rule out that a single patched font is causing the issue.

As can be seen in the screenshot, multiple font families are created for the font variants while I expect a single font family named Sauce Code Pro containing all the variants. Also all the fonts are named: "NerdFontCompleteMono"

I hope we can sort this out because I really want to use the awesome glyphs in my setup

Hello,

I would like to know if these fonts also include the powerline extra symbols. I have tested some of theme with xfd but I didn't see any "flames" or other powerline extra symbols.

Thank you very much in advance :)

I've noticed that glyph names are lost when patching fonts. For example, if I take the Octicons font as a source of glyphs and patch another font with it (with the --octicons option), then all the glyph names (e.g. octoface or mark-github or repo-forked for some of the standard GitHub glyphs) are lost and instead replaced by Unicode glyph codes (e.g. uniF008 for octoface).

Is there a chance to retain those names? They are very useful in finding specific glyph codes (remembering a name is much easier than remembering a code, especially since codes can change between font versions, while name is usually more stable).
Thank you!

First, thanks for the project, it has significantly improved my development experience.

With the 0.6.0 release the Sauce Code Pro Powerline fonts appears to have vanished from under patched-fonts. Was that intentional?

Thank again!

I tried both Mono and double width without any success.

or same references is well appreciated.

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.

Font fixes and updates to coincide with ryanoasis/vim-devicons#13

The Hack project released v2.015 a little while ago, which greatly improved some glyphs and rendering. Having it in nerd-fonts would be great.

Fonts that are mono before patching should remain so after patching

terminals where the issue is apparent (not comprehensive):

• urxvt
• gnome terminal

issue links:

• ryanoasis/vim-devicons#11
• ryanoasis/vim-devicons#21

Partially following up on #42 and also continuing my thoughts after dealing with #56 may I offer a few thoughts on how to reduce the staggering complexity in the number of fonts produced by the patcher?

With short names (e.g. "NC" instead of "Nerd Font Complete") Windows version is never needed.
Also, we could also get rid of most of thee complexity with variations.

Currently, you have two conflicts among glyph sets:

1. 'Custom SetiUI' (52 glyphs) and 'Devicons' (198)
2. 'FontAwesome' (609) and 'Octicons' (164)
   For the 1st there is no variation, 'SetUI' takes precedence. For the 2nd you either shift 'Octicons' if 'FA' is present or just have 'Octicons' in default positions without 'FA'.

So, in your scheme, only two fonts are needed:
2a) complete with 'Octicons' shifted and 'FA' in default position and
2b) complete with 'Octicons' in default position and 'FA' shifted

• either completely or
• have 'FA' glyphs following 'Octicons' range remain in their spot (~400 glyphs) and only shifting first ~200 (bigger than 164 above since 'Octicons' has a lot of holes in its range)

That's it in the current implementation!

Personally, I'd prefer in the 1st conflict to prioritize 'Devicons' to make it match the intended codepoints and allow using well-established reference tables (https://vorillaz.github.io/devicons/#/dafont) and then just shift 'SetiUI' to right after 'Devicons'

In order to make packages for each of the patched fonts it would be nice to provide a separate download link (I think releases in github might be able to release just one dir as well so as to do it per font) per font so that each package won't clone the entire repo for each of the fonts.

Target and patch Monoid

Hi again. ;)

This time the codepoints for octoicons seem to be wrong. Haven't found a pattern there. If I do an echo "\uF020" "\uF000" "\uF001" "\uF005" "\uF0B2", none of the correct symbols show up:

Ignore the wrong symbols in the theme..

Tested with NerdFonts 0.5.0 Knack Plus Nerd File Types Plus Font Awesome Plus Octicons Plus Pomicons with iTerm2 on OSX Yosemite.

from: ryanoasis/vim-devicons/issues/57

reported issues in 3270 font. probably most, if not all fonts

need to validate and test the fonts 😟

This isn't a huge problem, but might be easy to fix.

After installing all the patched fonts under OSX, many of them show up as duplicate fonts in the Font Book app.

Not sure if this is the exact cause, but I noticed when inspecting these fonts that the "Unique name" value is unchanged between variations of the same font.

https://pcaro.es/p/hermit/

need a script to repatch all of the different fonts and versions

So far,

Seem to be working: 20141231, 20150228

Seem to not working: 20120731

The Pomicons.otf file appears to be missing from the repo:

% /usr/bin/python ./font-patcher ~/.fonts/Input/Input_Fonts/Input/Input-Regular_\(InputMono-Regular\).ttf
The glyph named Tcommaaccent is mapped to U+021A.
But its name indicates it should be mapped to U+0162.
The glyph named Delta is mapped to U+0394.
But its name indicates it should be mapped to U+2206.
The glyph named Omega is mapped to U+03A9.
But its name indicates it should be mapped to U+2126.
The glyph named tcommaaccent is mapped to U+021B.
But its name indicates it should be mapped to U+0163.
The glyph named mu is mapped to U+03BC.
But its name indicates it should be mapped to U+00B5.
The requested file, Pomicons.otf, does not exist
Traceback (most recent call last):
  File "./font-patcher", line 92, in <module>
    pomicons = fontforge.open("glyph-source-fonts/Pomicons.otf")
EnvironmentError: Open failed

Is this an oversight or due to licensing?

Hello! I'm trying to patch Inconsolata, but any parameter I give to font-patcher causes a seg fault. Below are the package versions I'm using. I'd appreciate if you could tell me if there's anything I'm missing.

$ python --version
Python 2.7.9

$ fontforge --version
Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors.
 License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
 with many parts BSD <http://fontforge.org/license.html>. Please read LICENSE.
 Based on sources from 20:50 BST  1-Apr-2015-D.
 Based on source from git with hash:
fontforge 20:50 BST  1-Apr-2015
libfontforge 20150401

$ ./font-patcher unpatched-sample-fonts/Inconsolata/Inconsolata\ for\ Powerline.otf
[1]    82858 segmentation fault  ./font-patcher

Currently both font file names and internal font names are a bit unwieldy.
The file names are too big and font names are unique for each style, which prevents Font Book from displaying them under one family group.
I understand the need to differentiate between many variants, though would prefer a simple
SourceCodePro-Medium-mNOP instead of
Sauce Code Pro Medium Plus Nerd File Types Mono Plus Octicons Plus Pomicons
for file names and something similar for font names (e.g. Source Code Pro mNOP font family while retaining original style names like Regular instead of Book).

Would it be possible to adjust the naming convention during conversion or allow some user input (e.g. sourcing a file with "original font names:new font names" that could be used for naming instead)? I'm most interested in font names since file names are much easier to change.
Thank you!

This is going to make new releases take a lot less time (less painful).

Hi there.
What shall I do to fix 'stretching' effect?
example:

emulator: gnome terminal
font: droid sans mono for powerline plus nerd file types mono 12

Also, I will be very grateful if someone describe how to patch default ubuntu mono font. :)

Originally discovered in: ryanoasis/vim-devicons#58

https://github.com/chrissimpkins/Hack/releases :)

Can you switch to the original Source Code Pro instead of Sauce Code. Adobe appear to have designed the powerline symbols into the recent version of Source Code Pro.

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.

Support more fonts:

• 3270
• AurulentSansMono
• BitstreamVeraSansMono
• HeavyData
• Lekton
• MPlus
• ProFont

Running The following produces a error.

./font-patcher -s --fontawesome --octicons --pomicons --powerline --powerlineextra --careful PragamataPro.ttf

updating glyph: <Glyph Branch in font PragmataProNerdFontCompleteMono> Branch putting at: E0A0
updating glyph: <Glyph LN in font PragmataProNerdFontCompleteMono> LN putting at: E0A1
updating glyph: <Glyph padlock_closed in font PragmataProNerdFontCompleteMono> padlock_closed putting at: E0A2
updating glyph: <Glyph HardRightArrow in font PragmataProNerdFontCompleteMono> HardRightArrow putting at: E0B0
updating glyph: <Glyph SoftRightArrow in font PragmataProNerdFontCompleteMono> SoftRightArrow putting at: E0B1
updating glyph: <Glyph HardLeftArrow in font PragmataProNerdFontCompleteMono> HardLeftArrow putting at: E0B2
updating glyph: <Glyph SoftLeftArrow in font PragmataProNerdFontCompleteMono> SoftLeftArrow putting at: E0B3
updating glyph: <Glyph uniE0A3 in font DroidSansMonoForPowerlinePlusNerdFileTypesMono> uniE0A3 putting at: uniE0A3
Traceback (most recent call last):
  File "./font-patcher", line 423, in <module>
    copy_glyphs(sourceFont, symbolsPowerlineExtraRange1Start, symbolsPowerlineExtraRange1End, powerlineExtraSymbols, symbolsPowerlineExtraRange1Start, symbolsPowerlineExtraRange1End, True)
  File "./font-patcher", line 327, in copy_glyphs
    codepoint = int("0x" + copiedToSlot, 16)
ValueError: invalid literal for int() with base 16: '0xuniE0A3'

Running the same line without --careful it completes without error.

can also add fonts that (for patched fonts) https://github.com/Yggdroot/indentLine#font-patching ?

per: ryanoasis/vim-devicons/issues/75

Hi there!

When I use "Sauce Code Powerline Plus Nerd File Types Mono Plus Font Awesome Plus Octicons" the codepoints starting from f00f are off by one.
Example: The codepoint for home-icon on the table is f015. This should be the correct one, but if I do an echo "\uF015" it shows the wrong symbol. In the patched version the home-symbol has the codepoint F014. This is the case for all subsequent glyphs (seems to get worse with ongoing icons).

After updating and trying to use some of the new Font Awesome glyphs, I noticed that in many of the patched fonts these glyphs display around twice as big as they should. Seems to only affect Font Awesome glyphs.

Interestingly, with a few of the patched fonts they show up normal size, but some of the other glyphs (like the > < symbols used by PowerLine) show up half-size.

Any interest in looking into and attempting to add ligatures to fonts without?

20 new fonts included.
https://fortawesome.github.io/Font-Awesome/whats-new/

Roboto Mono

Hi! It looks like you're distributing modified fonts. Some of them have licensing requirements that appear to not be met. A (non-exhaustive) list follows.

Anonymous (renamed to Anonymice?):
OFL - a copy of the copyright+license has to be included with all distributions. Modifications/originals must be released under the OFL.
http://www.marksimonson.com/fonts/view/anonymous-pro
http://scripts.sil.org/cms/scripts/page.php?item_id=OFL-FAQ_web

Droid Sans:
Apache v2.0 - a copy of the copyright+license has to be included with all distributions.
http://www.google.com/fonts/specimen/Droid+Sans
https://www.apache.org/licenses/LICENSE-2.0.html

Liberation (renamed to Literation?):
I'm assuming you've got a recent version, which would be under the OFL - old versions are under the GPL.
OFL - a copy of the copyright+license has to be included with all distributions. Modifications/originals must be released under the OFL.
https://fedorahosted.org/liberation-fonts/
http://scripts.sil.org/cms/scripts/page.php?item_id=OFL-FAQ_web

PragmataPro:
PragmataPro is not free software and the author hasn't ever made it available in a particularly permissive form. Also worth noting - you appear to have an older (buggy) version of PragmataPro which is missing certain ligatures added in 0.820.
http://www.fsd.it/fonts/pragmatapro.htm
http://www.fsd.it/fonts/eula.htm

Proggy:
Appears to be public domain?
http://upperbounds.net/

Source Code (renamed to Sauce Code?):
OFL - a copy of the copyright+license has to be included with all distributions. Modifications/originals must be released under the OFL.
https://github.com/adobe-fonts/source-code-pro
https://github.com/adobe-fonts/source-code-pro/blob/master/LICENSE.txt

Ubuntu Mono:
UFL - fonts and derivatives may only be redistributed under the UFL.
http://font.ubuntu.com/licence/