[cairo] Userfont hinting

[Behdad Esfahbod]

(CC'ing cairo list)

On Tue, 2008-05-06 at 11:18 +0100, Peter Clifton wrote:
> 
> Aside from this, what were your plans for the branch? In gEDA, working
> on adding big features like this, I'd normally get a working tree, then
> play patch acrobatics to make a stgit patch series which adds the
> functionality with some divine knowledge of how it must work, such that
> each commit is self-sufficient, and that git bisect can work without
> breakage.

This is the plan.  I managed to finish the merge myself as I was left in
the middle of conflict resolution and didn't know how to back out, so
just did it.

Tonight I plan to break it down to a series of commits and go ahead and
push it to master.

In the mean time I found that I may need to tweak a few things to allow
supporting subpixel rendering with user fonts in the future.  I don't
like where the thinking got me (which was, making cairo-scaled-font.c do
subpixel rendering if the backend doesn't support it).  But in the mean
time I'm going to make the following change:

  - After the render_glyph function returns, we'll inspect its set font
options and use that to decide what kind of image surface to use.  If it
has hinting off, we use A1.  If it has subpixel on, we'll use ARGB32.
So this will make the scaled font options decide the glyph format
automatically, but if your user font render functions decides to, it can
override that decision.  This affects our longer term plan to support
ARGB glyphs there are not subpixel masks, but real colored glyphs...


So yeah, look for user-fonts merging tomorrow.

-- 
behdad
http://behdad.org/

"Those who would give up Essential Liberty to purchase a little
 Temporary Safety, deserve neither Liberty nor Safety."
        -- Benjamin Franklin, 1759