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):||25 December 2004|
|PDF File Size:||13.94 Mb|
|ePub File Size:||9.18 Mb|
|Price:||Free* [*Free Regsitration Required]|
On Mon, Aug 13, at 4: That being said, I think we should polish the Sky theme a bit more making it as GTK3 as possibleand make it the default theme. Yeah; otherwise we’ll end up with indices, contforge sort of sounds like a recipe for reader confusion. A bit like the “tutorial” now, but covering things more clearly.
fontforge(1) – Linux man page
Looks more generic and has better “contrast distribution” to me, of contforge – this means I see clearly what I need to see distinct, and I’m not hit by excessive contrast where it’s unneeded. In reply to this post by Dave Crossland. What do you envision the bibliography covering? Looking at the original website innot much has changed but it’s gotten very fontfkrge inflated and needs to be restructured.
In reply to this post by Michal Nowakowski. So that’s what I’d like to focus on. I am going to admit that I prefer the Adwaita theme because it’s more “vanilla” in flavor than the Sky theme. Both the Adwaita and Sky themes are good candidates for a new default theme. Especially when you throw fontforgf things like Spiro.
I’ve been using the egtk theme from fontforg and that would be my preference. This is missing sections on: What I would like fontorge do is have a “further reading” at the end of chapters and articles, and contain links to sites, and books to read, related to the chapter or article. I guess Adwaita users have different views ; I added lots of its tricks into fontforrge Clearlooks theme, but guess that’s not that’s what you meant by ‘polishing’ it: We’d probably have a hard time finding two people that agree on exactly where to draw those lines, of course.
But its a corner case. I’m somewhat interested in hiding some parts of the documentation until the user unhides it.
They won’t be updated at the same speed nor likely by the same people and keeping them in one document makes it tempting to omit topics thinking that the reader can just look it up in another section.
But as to the theme in question should it be: On Mon, Aug 13, at 1: It should be out properly in a few weeks: Sky is a better starting point IMO. And would someone volunteer to write some kind of ,anual guides for source itself.
Design With FontForge
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. I think they all need to be using one resource file and window decoration, so that it retains unity through the whole thing and avoids confusion.
This is for both dumbed down explanations and advanced or only partly related topics. Anyway, I’m going to get started slowly rewriting it all to fit in that scheme.
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 making distribution builds scripts etc ; we could probably cover that in FAQ links into the Manual. But, I shall say I’m not sure it’s gonna happen. And the index really should be covering the whole site I think.
In reply to this post by Khaled Hosny-2 On 13 August 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.
Should we then purposely group them? It would take a reasonable time to read the whole thing i. I would put a lot of the advanced terminology topics in the same category One of the major failing of the current documentation is that it doesn’t address any of this, and just throws out basic “here are the tools” descriptions. So that should also be considered. Same with Panose, weight-classes, etc. The more well done themes, the better.
That’s a lengthy process: