From 3f303b9cb51306e1f70e2024a31a48a9901585a0 Mon Sep 17 00:00:00 2001 From: Po Lu Date: Wed, 10 Jan 2024 11:38:54 +0800 Subject: [PATCH] ; Minor edits to PROBLEMS and sfnt.c * etc/PROBLEMS: Improve description of issues with Droid Sans Mono. * src/sfnt.c (sfnt_poly_edges_exact): Remove extraneous undef. --- etc/PROBLEMS | 15 ++++++++------- src/sfnt.c | 2 -- 2 files changed, 8 insertions(+), 9 deletions(-) diff --git a/etc/PROBLEMS b/etc/PROBLEMS index 7a5f029af65..5166907e463 100644 --- a/etc/PROBLEMS +++ b/etc/PROBLEMS @@ -3408,14 +3408,15 @@ this and many other problems do not exist on the regular X builds. TrueType fonts incorporate instruction code executed by the font scaler (the component responsible for transforming outlines into -bitmap images capable of being displayed onscreen), in order that -features of each glyph might be aligned to pixel boundaries -intelligently, preventing faintness while maintaining the shape of its -features. The substandard instruction code provided by the monospace -font distributed with Android misplaces features of such glyphs as "E" -and "F" between point sizes of 16 and 24, resulting in noticeable +bitmap images capable of being displayed onscreen) to align features +of each glyph to pixel boundaries while maintaining their shape, in +order to alleviate visual imperfections produced by scaling. The +substandard instruction code provided by the Android "Droid Sans Mono" +font misplaces features of glyphs containing, as components, "E" and +"F", between PPEM sizes of 16 and 24, resulting in noticeable whitespace inconsistencies with other glyphs. Furthermore, the -vertical stem in the glyph "T" is positioned too far to the left. +vertical stem in the glyph "T" is positioned too far to the left at +PPEM sizes of 12. The remedy for this is to replace the instruction code with automatically generated code from the FreeType project's "ttfautohint" diff --git a/src/sfnt.c b/src/sfnt.c index 0666bb17cf0..f4c023f35c6 100644 --- a/src/sfnt.c +++ b/src/sfnt.c @@ -5474,8 +5474,6 @@ be as well. */ next = next->next; xfree (last); } - -#undef ONE_PIXEL } /* Apply winding rule to the coverage value VALUE. Convert VALUE to a -- 2.39.2