OSX doesn't seem to support the fallback option from what I'm reading, and some terminals/OS have rendering issues where I assume fallback strategy won't be enough? Besides adding the glyphs to merge into a base font, how much work/time can be involved to fix those offset/size issues I've seen around the place? These official patched versions seem quite outdated:, not sure how much that matters. Rendering wise, if fallback works would be effectively the same as having those glyphs patched together as a single font or are there potential differences? 50+ patched and ready to use programming fonts. Small things like the difference between 0 vs o or l vs 1 and large things like the readability of the font is key to your productivity and strain on your eyes. Choosing a font to use in your editor is a very important step in your workflow that many developers don't think twice about.

With the fallback strategy, is the only benefit this repo provides a font map? I noticed some of the fonts haven't been updated in a while like with other repo's. Popular glyph collections: Font Awesome, Octicons, Material Design Icons. Top 11 Programming Fonts for your Text Editor and Terminal. Would you know if the Awesome bit was referring to this repo or Font Awesome? I came across this SourceCodePro + Powerline + Awesome Regular font, it seems to be custom patch by the user. Probably not the right place, but few questions. Alternatives to the penguin glyph would be nice :)