Adding folders of fonts to a Pog

Hello world,
I was asked in an email the other day if I could add a function to gather all the fonts in a given folder into a Pog. While this is a cool idea for a future release, it's possible right now from the command-line. Lemme show you how.

Open a console/terminal (like konsole or gnome-terminal). I will use square brackets [ ] to surround the command you can type but don't type the brackets. I will use ~/somefonts as the example folder you want to use.

The idea is to build a pog, which is a plain text file containing full paths to each font file. Okay, let's start:

1. Use [cd ~/.fontypython] to go where the pogs live.
2. [echo "not installed" > newpog.pog] You can use any name you want. Just make *sure* you don't overwrite some other pog!
3. [find ~/somefonts -iname "*.ttf" >> newpog.pog] That will go and find the ttfs (you can change that to say "*.otf" but Type1 fonts might be more tricky) and then it will append them to the 'newpog.pog' file you just started.
4. If you want to add other fonts from other folders, just use the same find command, but change the path. Make sure you use 2 ">" symbols (>>) because that means append-to.

Right, that's it. Now open fonty and go look at newpog:
[fontypython newpog]

You can also install those fonts with:
[fontypython -i newpogs]

Have a look at [fontypython --help]

Simple, I hope ;)
\d

Fonty Python - Type1 issues

Type1 is a PITA
I got my first bug report today and that has led me to see that my code to handle Type1 fonts is more than a little fragile.

Right now, if you point it at .pfb files, then all should be well. I am trying to gather information about the other filetypes (like pfa and afm, pfm etc.) to see which ones I should bother with.

There will be a FP update once that's all done.

In the meantime, please let me have your error output as well as a listing of the folder/pog that caused the error. The more info I have about what you were doing when things went wrong, the better.
If fonts crash FP, you can also compress and send me the fonts that did the deed.

\d

Fonty Python 0.3.2 update released

Fonty gets a tiny upgrade - version 0.3.2
I have changed the way the help files are stored so that they can now be localized. The setup.py file had to change a little too, but there are no radical changes to the way the app works. This is a 'help file only' update.

Dowload from here
\d

Fonty Python 0.3.1 update

Update released - Fonty Python 0.3.1

A few fixes have been made:

• Fixed img height/width bugs in help file. It scrolls smoothly now.
• Fixed startup bug when last folder viewed no longer has any fonts.
• Fixed some text in strings.
• Improved the setup.py system to use i18n, strings and fpversion modules.
• Added Italian translation (Thanks to Pietro Battiston.)

You can get it from Savannah

\d

Fonty Python 0.3.0 released

Fonty Python now supports TTF, OTF, Type1 and TTC fonts.

I don’t have a lot of time to develop and Fonty languished for most of 2007 before I could get a solid week to spend upgrading the code.
It now supports a wider range of fonts and has been localized. There are some teething problems with the language thing, and I am not sure that all the new fonts types will work properly - but it’s out as version 0.3.0.

You can go to: https://savannah.nongnu.org/projects/fontypython/ to get the app.

We also have a wiki on: webfactional

I have some questions (posted on the list) regarding i18n and how to manage the admin surrounding po/mo files as well as how best to bundle it all up into a release. I’m hoping for some input either on this blog or on the the mailing list: fontypython@googlegroups.com

\d