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.
|Published (Last):||15 July 2008|
|PDF File Size:||19.99 Mb|
|ePub File Size:||1.26 Mb|
|Price:||Free* [*Free Regsitration Required]|
But as to the theme in question should it be: I’m also curious where the magic number of pages comes from. I see what you mean.
fontforge(1) – Linux man page
Especially when you throw in things like Contforge. I think we need to decide exactly what the scope and purpose of these separate documents are. Sky is a better starting point IMO. I agree the screenshots should show the default theme, and that the default theme should change before creating the screenshots: I’ve been using the egtk theme from elementary and that would be my preference.
Developer – Fontforge manual
So that should also be considered. In reply to this post by Dave Crossland W dniu Manusl bit like the “tutorial” now, but covering things more clearly.
In reply to this post by Brian Zick. The focus is getting started on making fonts, so some extra detail will be pulled out and stuck in other articles and so on. 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. Someone looking to contribute code.
In reply to this post by Michal Nowakowski. That’s a lengthy process: If you missed it, I posted a sketch outline of how I would like to rewrite the documentation:. A user new to Fontforge. In reply to this post by Dave Crossland. Yeah; otherwise we’ll end up with indices, which sort of sounds like a recipe for reader confusion. On Mon, Aug 13, at Pretty much the whole process from introduction to fontforge and terminology to the final, working font.
I’m somewhat interested in hiding some parts of the documentation until the user unhides it. Looking at the original website innot much has changed but it’s gotten very much inflated and needs to be restructured. The only other use case I can think of that isn’t covered is someone who needs to use FF once, for one task, like generating a font from source, or fontforgee distribution builds scripts etc ; we could probably cover that in FAQ links into the Manual.
I’ll keep that in mind for sure. Also, Adwaita has succeeded Fontofrge what the Sky theme integrates with in Gnome 3. In reply to this post by Nathan Willis-4 On 13 August But, I shall say I’m not sure it’s gonna manua. I am going to admit that I prefer the Adwaita theme because it’s more “vanilla” in flavor than the Sky theme.
Might could cover that with parallel sub-chapters: I agree about the scope stuff; I personally think we ought 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. Part of this is developer documentation. Manuaal think they all need to rontforge using one resource file and window decoration, so that it retains unity through the whole thing and avoids confusion.
Outside the scope is making fonts that look good.
On Mon, Aug 13, at 1: On 13 August Should we then purposely group them? In the rosiest of all possible worlds, we’d contribute that sort of material to OFLB’s Majual while working on the FF manual; obvious risk is it could still get out of sync. 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.
And would someone volunteer to write some kind of style guides for source itself. I kanual put a lot of the advanced terminology topics in the same category What do you envision the bibliography covering? On Mon, Aug 13, at 4: It would be better to host it internally like Git than on Google Docs, though. Same with Panose, weight-classes, etc. Also, as I stated before, I object to trying to merge the user manual, help reference, and develop docs into a single outline.
Search everywhere only in this topic. The more well done themes, the better. It’s a standard length for books But I also made it, so take that with a grain of salt.
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 few immediate observations. While I’m rewriting I’ll be redoing the screenshots.