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.
|Genre:||Health and Food|
|Published (Last):||23 December 2007|
|PDF File Size:||12.94 Mb|
|ePub File Size:||18.89 Mb|
|Price:||Free* [*Free Regsitration Required]|
Search everywhere only in this topic.
If you missed it, I posted a sketch outline of how I would like to rewrite the documentation:. Anyway, I’m going to get started slowly rewriting it all to fit in that scheme. The focus is getting started on making fonts, so some fontorge detail will be pulled out and stuck in other articles and so on.
Looking at the original website innot much has changed but it’s gotten very much inflated and needs to be restructured. So that’s what I’d like to focus on. While Fohtforge rewriting I’ll be redoing the screenshots. 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.
But as to the theme in question should it be: I’ve been using the egtk theme from elementary and that would be my preference. Part of this is developer documentation. And would someone volunteer to write some kind of style guides for source itself.
Design With FontForge
On Mon, Aug 13, at In reply to fontforgs post by Brian Zick. IMO, the screenshots should use the default theme. 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. Discussions will include endpoint security, mobile security and the latest in malware threats.
In reply to this post by Nathan Willis On 13 August In reply to this post by Khaled Hosny I agree the screenshots should show the default theme, and that the default theme should change before creating the fonntforge 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? It’s a standard length for books It would take a reasonable time to read the whole thing i.
I’ll keep that in mind for sure. I’m somewhat interested in hiding some parts of the documentation until the user unhides it.
This is for both dumbed down explanations and advanced or only partly related topics. I think we need to decide exactly what the scope and purpose of these separate documents are. Pretty much the whole process from introduction to fontforge and terminology to the final, working font.
Outside the scope is making fonts that look good. A bit like the “tutorial” now, but covering things more clearly. I’m not sure exactly what the fontfoege or contents of the will be like, but the purpose, to document things the developers need to know, is clear The Adwaita theme I made should be updated a bit to use some of the new options, and it needs to be mxnual for a few other reasons regardless.
Both the Adwaita and Sky themes are good candidates for a new default theme. I am going to admit fontforhe I prefer the Adwaita theme because fontfotge more “vanilla” in flavor than the Sky theme. But I also made it, so take that with a grain of salt. Also, Adwaita has succeeded Clearlooks what the Sky theme integrates with in Gnome 3.
So that should also be considered. In reply to this post by Dave Crossland. Sky is a better starting point IMO. Looks more generic and has better “contrast distribution” to me, of course – this means I see clearly what I need to see distinct, and I’m not hit by excessive contrast where it’s unneeded.
I guess Adwaita users have different views ; I added lots of mxnual tricks into my Clearlooks theme, but guess that’s not that’s what you meant by ‘polishing’ it: The more well done themes, the better. That said, I also made fontcorge theme to match Ubuntu Precise: Also, as I stated before, I object to trying to merge the user manual, help reference, and develop docs into a single outline.
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. I would say it roughly breaks down by user fonttorge which I know is frighteningly similar to one of those weird “UI designer” buzzword approaches: A user new to Fontforge.
The second one would be trickier, since it would involve someone with Fontlab experience writing about the differences. Might could cover that with parallel sub-chapters: A user currently using Fontforge. Someone looking to contribute code.
Possibly scripts, possibly fontfkrge.
fontforge(1) – Linux man page
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 its a corner case. 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 would put a lot of the advanced terminology topics in the same category Same with Panose, weight-classes, etc. We’d probably have a hard time finding two people that agree on exactly where to draw those lines, of course. 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.
In reply to this post by Michal Nowakowski. It should be out properly in a few weeks: But, I shall say I’m not sure it’s gonna happen. On Mon, Aug 13, at 1: What I would like to 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.
Then the bibliography would just be collecting all of these into one page. On Mon, Aug 13, at 4: And the index really should be covering the whole site I think. If you missed it, I posted a sketch outline of how I would like to rewrite the documentation: It would be better to host it internally like Git than on Google Docs, though. A few immediate observations.
fontforge(1) – Linux man page
This is missing sections on: 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. That’s a lengthy process: Especially when you throw in things like Spiro. One of the major failing of the current documentation is that it doesn’t address any of this, and just throws dontforge basic “here are the tools” descriptions.
That said, glad to see that we’re starting the discussion in earnest, cause it’s overdue. In reply to this post by Nathan Willis-4 On 13 August In reply to this post by Khaled Hosny-2 On 13 August I’m also curious where the magic number of pages comes from.
I see what you mean. Should we then purposely group them? Brian Live Security Virtual Conference Exclusive live event will cover mnaual the ways today’s security and threat landscape has changed and how IT managers can respond. In reply to this post by Dave Crossland W dniu What do you envision the bibliography covering?
That is exactly what I’m suggesting. Yeah; otherwise we’ll end up with indices, which sort of sounds like a recipe for reader confusion.
Categorizing the links will probably keep the different subjects straight. Free forum by Nabble.