Random note: http://w3.impa.br/~diego/projects/GanEtAl14/ describes a way
of dealing with intersections, around section 3.2 I think.
On Mon, Jun 1, 2020 at 9:47 PM Werner LEMBERG wrote:
>
> >> However there is an issue with the program, the glyphs which
> >> contain intersecting contours have
That sounds very good.
Personally I'd be very happy to see the header inclusion macros gone where
possible, because they confuse both users and IDEs. I would also be very
happy to see meson support, because it seems to be gaining usage nicely and
I do find it nicer than CMake.
I'd be a bit sad
Since the range is small and fixed, fixed point format, or (signed)
normalized integers, will have superior quality compared to floats using
same number of bits.
Several image formats, including PNG, do support 16-bit images.
Then there is KTX image format, with reference code at
I managed to align outline stroked glyph bitmap with non-outline, 'normal'
glyph bitmap.
But I get unexpected outline glyph rendering results:
* Ubuntu-R.ttf as font, size set to 16, outline thickness 8.
* I have included ASCII dump of glyphs below. I can now align these, but
there is unexpected
I render glyph twice, first to get bitmap of 'normal' glyph, and second to
get bitmap with outline stroke.
I need to combine these to a single two-channel bitmap.
But the bitmaps have different sizes. How do can I render normal and
outline to matching bitmaps?
Or would it be possible to get such
When I run `pkg-config --modversion freetype2` on my Ubuntu 20.04, I get
weird version number: `23.1.17`. This does not look like a freetype version
number at all to me. Meanwhile, `apt show libfreetype6` gives me `Version:
2.10.1-2`. Could someone explain what this pkg-config version number is?
