Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Aug 10, 2012
  1. @upsidedwn

    Fix compatibility issues with the font patcher

    upsidedwn authored committed
    Fontpatcher was unable to patch the Consolas font. This is due to the
    fact that Consolas is 'not' strictly a mono spaced font - it has some
    glyphs which are 0 width. The added option '--fix-mono' fixes this issue
    by setting all 0 width glyphs to a common width.
    Windows does not seem to respect the font family name that fontforge
    uses.  Using the added option '--fix-win', the script will now set the
    font name to be the family name. In this manner, Windows will group
    these fonts under the same family. Windows still differentiates between
    different fonts of the same name by their weights, so having fonts of
    the same name is not a problem.
    Closes #61.
    Closes #194.
Commits on Apr 30, 2012
  1. @mgrubb

    Add update to SFNT Table for font renaming

    mgrubb authored committed
    On Mac (at least) the font was being grouped with the original font, and
    causing confusion for some programs.  This change updates the sfnt_names
    table 'Preferred Family' and 'Compatible Full' fields to match the
    new font name.  This will cause it to show up as it's own font in the
    list on Mac.
    Closes #136.
Commits on Jan 25, 2012
Commits on Jan 16, 2012
  1. Add info about the patched font wiki page

    Refs #13.
  2. Update font patcher

    This commit introduces some changes to how the font metrics are
    calculated as well as various fixes for glyph alignment and overlap. The
    update uses the Latin Extended-A and Box Drawing glyphs to determine the
    largest glyphs, this seems to be a quite reliable way of determining
    both the glyph height and the maximum width.
    An overlap property has been added to SYM_ATTR, the glyphs will be moved
    `font.em / 48` in the direction of the glyph alignment so it overlaps
    with the previous/next glyph. This is necessary for the block arrows so
    no gaps occur.
  3. Fix to allow multiple dots in font filenames

    Jonathan Henry authored
  4. Allow fontpatcher to output TrueType fonts

    Jonathan Henry authored
    Many TrueType fonts look like garbage if they are converted to PostScript
    outlines. This change allows TrueType fonts to be generated back as TrueType
    while any other format will be generated as OpenType.
Commits on Jan 15, 2012
  1. Fix fontpatcher to set proper width on new glyphs

    Jonathan Henry authored
    Gvim on Windows seems to only considers a font to be monospaced if every glyph
    has the same width; this setting appears to be unrelated to the glyph's
    bounding box.
  2. Update symbol font

Commits on Jan 13, 2012
  1. Update fontpatcher README

    Refs #13.
  2. Improve fontpatcher README

    This commit adds a detailed guide to font patching for both Linux and OS
    X users.
    Closes #13.
    Refs #20.
Commits on Jan 7, 2012
  1. Update fontpatcher README

  2. Only generate BDF or OTF fonts

    FontForge fails to generate valid PCF fonts, so pure bitmap fonts will
    need to be saved as BDF fonts. They may optionally be converted to PCF
    fonts at a later point using `bdftopcf`, but this is usually not
    TrueType fonts with or without bitmaps will always be stored as OTF
    fonts. This may later be updated to be configurable via a command-line
    This commit also changes how the output filename is generated. Only the
    filename of the original font up to the first period is used, and
    `-Powerline.[format]` is appended to this filename.
    Closes #9.
Commits on Jan 6, 2012
  1. Update fontpatcher README

    The Unicode code points are now monospaced.
Commits on Nov 22, 2011
  1. fontpatcher: Move outline glyphs slightly

    This resolves some antialiasing issues, especially for the arrow glyphs.
  2. fontpatcher: Update bitmaps

Commits on Nov 21, 2011
  1. fontpatcher: Update symbols

Commits on Nov 18, 2011
  1. Add font patcher

Something went wrong with that request. Please try again.