Trusting Your Eyes · Planning Your Project · The EM Square · Installing FontForge · Configuring FontForge · General UI Introduction · Using the FontForge. This book has been produced to help make the process of type design available to anyone. Type design is visually complex as well as. FontForge is an open source program which allows the creation and modification of fonts in many standard .. Or you can create hints manually—the easiest.

Author: Douran Vudojar
Country: Czech Republic
Language: English (Spanish)
Genre: Education
Published (Last): 27 August 2013
Pages: 189
PDF File Size: 20.67 Mb
ePub File Size: 19.28 Mb
ISBN: 816-7-65138-690-4
Downloads: 48110
Price: Free* [*Free Regsitration Required]
Uploader: Samuk

Fontforge manual

In reply to this post by Brian Zick. A user currently using Fontforge. I’m also curious where the magic number of pages comes from. A bit like the “tutorial” now, but covering things more clearly.

I’m not sure exactly what fontfoorge scope or contents of the will be like, but the purpose, to document things the developers need to know, is clear I would say it roughly breaks down by user role which I know is frighteningly similar to one of those fomtforge “UI designer” buzzword approaches: In reply to this post by Nathan Willis But as to the theme in question should it be: On 13 August I am going to admit that I prefer the Adwaita theme because it’s more “vanilla” in flavor than the Sky theme.

I think we need to decide exactly what the scope and purpose of these separate documents are. In reply to this post by Dave Crossland W dniu A few immediate observations. Should we then purposely group them? Possibly scripts, possibly patches.


Especially when you throw in things like Spiro. The second one would be trickier, since it would involve someone with Fontlab experience writing about the differences.

I would put a lot of the advanced terminology topics in the same category Having talked up Fontforge with some other graphic designers this summer, the big hurdle is getting users up to speed on the differences between FF’s editor and a “standard” vector graphics app.

On Mon, Aug 13, at fontorge But, I shall say I’m not sure it’s gonna happen. I agree the screenshots should show the default theme, and that the default theme should change before creating the screenshots: If you missed it, I posted a sketch outline of how I would like to rewrite the documentation:.

I guess Adwaita users have different views ; I added lots of its tricks into my Clearlooks theme, but guess that’s not that’s what you meant by ‘polishing’ it: A user new to Fontforge.

fontforge(1) – Linux man page

The more well done themes, the better. The Adwaita theme I made should be updated a bit to use some of the new options, and it needs to be updated for a few other reasons regardless.

It’s a standard length for books By the way, should I just post the outlines and plans to this repo or should I put up the new site that’s in the works too? And the index really should be covering the whole site I think. It would be better to host it internally like Git than on Google Docs, though.


Free forum by Nabble. But its a corner case. On Mon, Aug 13, at 1: In the rosiest of all possible worlds, we’d contribute that sort of material to OFLB’s Guidebook while working on the FF manual; obvious risk is it could still get out of sync. That said, I also made a theme fontfforge match Ubuntu Precise: I’m somewhat interested in hiding some parts of the documentation until the user unhides it.

But I also made it, so take that with a grain of salt. In reply to this post by Khaled Hosny-2 On 13 August I agree about the scope stuff; I personally think we mabual to keep away from the making-fonts-look-good material — but do so in favor of hosting that sort of stuff at an application-neutral site like OFLB.

Anyway, I’m going to get started slowly rewriting it all to fit in that scheme. If you missed it, I posted a sketch outline of how I would like to rewrite the documentation: Fontforgw I’m rewriting I’ll be redoing the screenshots.

So that’s what I’d like to focus on. Part of this is developer documentation. Someone looking to contribute code. The focus is getting started on making fonts, so some extra detail will fpntforge pulled out and stuck in other articles and so on. Might could cover that with parallel sub-chapters: