Some pixel font rasterize incorrect about fontdue HOT 4 CLOSED

oh god zpix has 22,000 glyphs. I'll look into those issues thanks!

For reference, 12pt is 16px. It looks like those fonts use a recommend size in points, but fontdue consumes pixels. 1 px = .75 pt. I think RustType uses points as well. I don't have a good reason to be using pixels other than convenience right now though.

from fontdue.

As for the lines, it is unfortunate. The issue is rounding errors with single precision floats and I'm looking into ways to fix it. I have a TODO for this in code right now here.

I can render it correctly, but it introduces errors at higher sizes right now due to precision loss.

from fontdue.

I pushed a change to resolve this here c4bd8a0.

from fontdue.

    /// Retrieves the layout metrics and rasterized bitmap for the given character. If the caracter
    /// isn't present in the font, then the layout and bitmap for the font's default character is
    /// returned instead.
    pub fn rasterize(&self, character: char, px: f32) -> (Metrics, Vec<u8>) {
        self.rasterize_indexed(self.lookup_glyph_index(character), px)
    }

So this function's param px is pixel, but not point?
The right way to use fontdue rasterize is use pixel?

The Zpix font recommend size unit is actually pixel.

Fontdue rasterized Zpix in 12px is great! It retained the hard border so make the pixel style.

Opposite rusttype can not rasterized Zpix in 12px as well (looks like linear filter?). That's why I gave up on it. I have making the pixel style game, so there is a way to make text as pixel style is very important.

For the game develope, use pixel unit is more convenient for me.

from fontdue.