[cairo] Trying to figure out some rasterization problems

James Cloos cloos at jhcloos.com
Tue Apr 23 14:15:51 PDT 2013

>>>>> "DK" == David Kastrup <dak at gnu.org> writes:

DK> There is quite a bit of variation in stem lengths (they are adjusted
DK> for collision avoidance, cross stem etc).  Fixed fonts are pretty
DK> much out, generating fonts on the fly is somewhat easier to suggest
DK> than implemented.

You can grab the code cairo uses to convert a cairo user font into cff
(for pdf) and type1 (for ps) fonts.  It should be a very usable basis
for lilypond to do the same.

It doesn't generate hints, but most renderers these days seem to ignore
type1/cff hints and autofit anyway.  It should cover everything else.
You'll just need a good glyph naming convention.

Postscript forms might rasterize once and blit to each destination; if
so that also should ensure constant width stems.  But that heavily
depends on how the rasterizer works, of course.

Directly generating pdf when that is desires also is a good idea.

Perhaps the LuaTeX code might provide a good basis for direct pdf
output.  (To be clear, I don't mean generating TeX, but using something
based on  Taco's code in lilypond.)

James Cloos <cloos at jhcloos.com>         OpenPGP: 1024D/ED7DAEA6

More information about the cairo mailing list