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):||14 November 2013|
|PDF File Size:||2.34 Mb|
|ePub File Size:||12.39 Mb|
|Price:||Free* [*Free Regsitration Required]|
In reply to this post by Fontfroge Crossland. Brian Live Security Virtual Conference Exclusive live event will cover all the ways today’s security and threat landscape has changed and how IT managers can respond.
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.
That said, glad to see that we’re starting the discussion in earnest, cause it’s overdue. The focus is getting started on making fonts, so some extra detail will be pulled out and stuck in other articles and so on. If you missed it, I posted a sketch outline of how I would like to rewrite the documentation:.
In reply to this post by Nathan Willis-4 On 13 August That is exactly what I’m suggesting. I’m somewhat interested in hiding some parts of the documentation until the user unhides it. Categorizing the links will probably keep mabual different subjects straight. 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.
Both the Adwaita and Sky themes are good candidates for a new default theme. In reply to this post by Dave Crossland W dniu 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? On Mon, Aug 13, at It would be better to host it internally like Git than on Google Docs, though. In reply to this post by Michal Nowakowski.
Should we then purposely group them? 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.
Design With FontForge
I agree the screenshots should show the default theme, and that the default theme should change before creating the screenshots: Yeah; otherwise we’ll end up with indices, which sort of sounds like a recipe for reader confusion. That said, I also made a theme to match Ubuntu Precise: I’ll keep that in mind for sure. The second one would be trickier, since it would involve someone with Fontlab experience writing about the differences. Anyway, I’m going mnaual get started slowly rewriting it all to fit in that scheme.
Part of this is developer documentation. I would put a lot of the advanced terminology topics in the same category On 13 August And the index really should be covering the whole site I think.
Developer – Fontforge manual
While I’m rewriting I’ll be redoing the screenshots. 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 fontforye chapter or article.
Sky is a better starting point IMO. Discussions will include endpoint security, mobile security and the latest in malware threats. 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.
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. It would take a reasonable time to read the whole thing i.
fontforge(1) – Linux man page
In reply to this post by Brian Zick. What do you envision the bibliography covering? In reply to this post by Khaled Hosny Possibly scripts, possibly patches. And would someone volunteer to write some kind of style guides for source itself. This is missing sections on: Also, as I stated before, I object to trying to merge the user manual, help reference, and develop docs into a single outline.
I see what you mean. So that should also be considered. Especially when you throw in things like Spiro.