View Single Post
Old 07-06-2019, 03:58 PM   #224
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Released v1.17.0!

A fair amount of goodies in this one .

Error handling in the CLI tool is now extra verbose.

In the OT/TTF font rendering codepath, you can now get information about the line-breaking computation pass (c.f., the docs and the discussion in the Kobo FBInk thread).

Also on the OT/TTF side of things, the font size can now be specified as a decimal, which should allow finer-grained control over the final rendering .

On the fixed-cell font rendering side of things, Spleen has been updated to 1.0.5, and a couple of Amiga fonts have been imported (Topaz+ A1200 & MicroKnight+), as well as the VGA variant (8x16) of the IBM font.
The LF glyph is now always replaced by a space, to account for fonts where it is visible.

There's a bunch of minor performance improvements all over, but especially for the fixed-cell font rendering.

Of particular interest to users of legacy (< K4) Kindle devices (hi, @PoP! ), this one finally fixes a bunch of issues related to the quirkiness involved with dealing with a 4bpp framebuffer.
The most visible example I could find was overlay mode, in the fixed-cell font rendering, with an odd font scaling multiplier. It'd lead to bogus colors on the edges of glyphs.
(While it affected more stuff, the most common codepaths were using a couple of workarounds to paper over the underlying issue ;p. This release fixes it for good).
NiLuJe is offline   Reply With Quote