Great fonts! I really enjoy them. What would you recommend me if I want to create pixel font?...
1 year ago(+6)
Thanks so much! Glad you like them :)
There's two different tools I used to make these, both of which are fantastic, and I can highly recommend. These are:
- BitFontMaker2
This one is how I got started, and it's incredibly easy to get set up with a really intuitive interface. I'd particularly recommend this if you're just getting into pixel fonts - it's really quick to learn, and you can see great results in no time!
I'd highly recommend - Pixel Font Converter by YellowAfterlife
A little more complex, and with a correspondingly steeper learning curve, but has a lot of useful features, including unlimited support for all unicode glyphs, kerning pairs and the ability to set metadata for your font.
This requires creating a glyph sheet in your image editor of choice, uploading it to Pixel Font Converter and setting all input, output and metadata parameters in order to generate the intended result.
If you're interested in playing around with this one, some of my more recent fonts include glpyh sheets and JSON files which are compatible with Pixel Font Converter allowing you to import them and try things out to see how it all works :)
I haven't looked into color fonts, but it might be a good way to play with anti aliasing? I'll have to look into it at some stage
The main features I use are:
- Kerning pairs
- Exporting/importing JSON settings for quick updates
- The way glyphs are set is incredibly intuitive, and it's extremely quick to set up the set of glyphs I provide as standard for my fonts
I inspected your several last fonts and didn't saw any reasons to use the "pixel contour type" option which is default for now. It is a workaround which trace any shapes correctly but with a cost of increased file complexity. Your last fonts aren't affected by the bug so you can use normal "outline contour type" (maybe I overlooked some affected symbols ¯\_(ツ)_/¯).
To enable outline contours you need to press output->contour type->outline. You can see the difference in my previous comment where you see g from squares which is a result of pixel contour and another where you see solid shapes which is produced by outline contour.
Why it happened? I am not sure that but it looks like you just used the utility like before but in the update was added pixel contour type which is default from that moment...
I am almost sure I understood which symbols are affected (and didn't found in you last font such symbols) and even reason of the bug but we can't know it for sure because the app is proprietary and it isn't possible to just change the code and immediately see the result