On 10/11/2013 2:19 PM, Daniel Santos wrote: > Hello guys. I see that this bug is fairly old, but as a person recently > introduced to Kicad, I must tell you that the font appearance was an > immediate turn-off! I know this sounds bubble-gum, twitter-ish, gen-me > shallow, but first appearances really have a profound impact on the > *perception* of quality. > > It's been a while since I've played with fonts, but I agree that the > font should not be compiled in and one should definately NOT have to > manually draw a font! In fact, by zooming in on the schematic view and > not researching at all, I could tell that the font was custom made from > straight lines. So in other words, it's obvious.
If you read all of messages in this bug report, I don't think anyone would disagree with you that the stroke fonts are less than ideal. They do allow us to guarantee the accuracy of the output. > > It is my uneducated opinion that we *should* be able to use some > existing font library to transform vector fonts into the language of > gerber without too much problem, although I can't comment on what it > would take to make the change in kicad. IMHO, the design should have > abstracted the font from the start, although I realize the importance of > sometimes "just getting a product done" and accepting costs like hard- > coded fonts. I doubt there is anything easy about using "some existing font library" to transform them into the gerber format unless you don't care about accuracy or someone else is doing the work ( which I find are always the easiest tasks to do :) ). If it was easy, someone would have done it by now. KiCad is getting to the point where there are not many easy tasks left to do. Most of the wishlist issues are very significant development efforts that require some financial incentive to motivate developers to work on them or high quality patches that don't require a huge amount of lead developer time to commit. While I agree that there is a difference between rendering fonts in the schematic editor where the output accuracy isn't as critical as the board font rendering, Pcbnew and Eeschema share common font rendering code so it's not that easy to replace. > > Is anybody still working on this? > I don't think anyone ever worked on this other than take a look at the effort involved. If you are feeling motivated, by all means give it a try. We are always looking for motivate developers who are willing to work with the KiCad development team. Wayne -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/668145 Title: Font preferences not available anymore, internal font changed To manage notifications about this bug go to: https://bugs.launchpad.net/kicad/+bug/668145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
