Manage your font collection with Font Manager

Already available in both Maverick and Debian sid, it provides many interesting features.

I’m talkin’ about Font Manager, a small application written in C and Python by Jerry Casiano, which allows users to easily install, remove and compare font files on own system.

Here are few nice screenshots:

To install the application, as usual type:

sudo apt-get install font-manager

Let me know what you think! 😉


13 thoughts on “Manage your font collection with Font Manager

  1. dino99


    installed on maverick but cant find it into menu, is that normal ( hey, im a human beeing and im used to click on menu as its now the 21th century)

    1. quadrispro Post author

      Yep, a choice of upstream.
      An excerpt from upstream’s ChangeLog:

      Automatically try to move any customizations found in ~/.fonts.conf to ~/.config/font-manager/local.conf instead of simply overwriting them. You should still edit local.conf directly and not rely on this.

        1. JC

          It should. Those paths are not “hard-coded”, the application asks glib which directories to use.

          If glib doesn’t return the right directories, please file an issue on the homepage so I can find a way to do this that respects user settings.

    2. JC

      For the most part, this application is targeted at users who may not know or care that ~/.fonts.conf even exists. 😉

      Also, for those that do, there’s a notice in ~/.fonts.conf about it.

  2. Pingback: » Blog Archive » Font Manager, para gestionar tu colección de fuentes

  3. xeen

    The program seems quite nice, but there are still a few issues. One is performance, while starting the program it produces a lot of IO before finally displaying a progressbar that shows the fonts being loaded. While the “loading without a progress bar phase” the program is unresponsive. Same applies to “autoscan for font directories”. This feature detected some folders I did not want to be scanned. Since there is no multiple selection, I removed those one by one. When closing the pref dialog, the program was still busy refreshing the main window over and over (presumably for each remove command I had issued).

    I found the “toggle buttons” at the bottom very confusing – why not switch automatically to “compare fonts” mode when selecting multiple fonts and offer browser/manage as tabs? On the other hand en/disable selected families isn’t toggleable, altough it would make sense there. Find as you type for the font listing would be a nice feature as well (and would get rid of the search toggle button… a filter feature might be useful though). Also, why is the “font size scrollbar” positioned so far away from the “font size spin button”?

    Apart from thise minor issues the program looks great. Seems to be a good candidate to replace open office when looking for fonts 🙂

    1. JC

      About performance, without knowing how many fonts you have installed and what kind of hardware you’re running, I can’t really comment on that, other than to say that I haven’t really experienced what you describe.

      Please remember that it’s targeted at average desktop users, so if you have a huge amount of fonts or require advanced features it’s probably not right for you.

      As far as the interface goes, if you would like you can file an issue and include a mockup of what you want to see along with why it makes better sense or improves usability. Of course I can’t guarantee that I will agree or implement it but I can guarantee that I will consider it.

  4. Bill Johnson

    *Much* faster then fontypython when loading my font collection. Took 1.5 minutes to find/load 3016 otf files (~700 families in a dedicated font folder), 2 minutes to find/load 2749 ttf files (~2200 families, dedicated directory), and 0.5 minutes to find/load 1022 pfb files (~1600 families (?), dedicated directory) which is really quite fast. For reference this is an AMD Turion(tm) X2 Dual-Core Mobile RM-75 on a 64-bit system with 4GB of RAM. I expect it is slower when scanning a large number of directories. The only complaint in this regard is the delay before showing the progress dialog (mentioned above). I have noticed some redrawing issues in the viewing window after scrolling but these go away when I toggle workspaces.

    The interface is nice but you might compare it to the other font managers and editors in debian. They have some good ideas as well. As someone else stated, a menu bar would be nice. Wouldn’t be too difficult to move the icons from the bottom left and add a few options (load, quit, etc.) to the bar. Either way this didn’t really slow me down, just something people are used to seeing.

    I was able to crash the program when scanning a folder of Type1 fonts. The error reported the function that crashed but not the file that caused the crash. More detailed errors or a debug mode would help in pinpointing the problem. I was able to pinpoint the problem anyway though. Here’s the file (sendspace):

    Note: the supplied name and email are fake. If you need to contact me reply here.

    1. JC

      Thanks for finding and posting the file that causes it. 🙂

      I’m not sure a more detailed error message is even possible here, looks like the crash happens immediately after calling a glib function from our C extension. I’ll look into better handling for font naming issues as time allows.

      For now, here’s a working copy of the font you posted.

      As far as the menubar suggestion, I’m not convinced yet, I am getting there as more options are added, but I still don’t believe that “Everyone else is doing it” is a good enough reason.

      Personally, I always think it silly when I see a menubar with one or two entries in it or a statusbar that never does anything, how pointless.

  5. Bill Johnson

    I found the explanation for my counting confusion. The above times and family numbers come from a scan of each of the following directories separately. I didn’t consider that there might be some overlap. A breakdown of the files in their folders:

    OpenType folder: (otf, 3016); (ttf, 0), (pfb, 0);
    TrueType folder: (otf, 3); (ttf, 2749); (pfb, 1022);
    Type1 folder: (otf, 0); (ttf, 3); (pfb, 4235);


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.