• Incorrect text rendering when in x86 64-bit precision mode. Filed as a cairo bug. The patch was something like this:
  

  -#define PANGO_UNITS(x) ((int)((x) * PANGO_SCALE))
  +#define PANGO_UNITS(x) ((int)((x) * PANGO_SCALE + 0.49999))

  (This probably would have been fixed by fixing the third bug in the list too.)
• Text is shifted off-by-one in Add to panel. Assigned to Pango, but libgnomecanvas highly suspected. Turned out it's a gdkpango bug. The patch was:

  -  cairo_move_to (cr, x / PANGO_SCALE, y / PANGO_SCALE);
  +  cairo_move_to (cr, (double)x / PANGO_SCALE, (double)y / PANGO_SCALE);

  After finding the bug, it became apparent that it only can happen if the next bug hits.
• Unhinted fonts are measured incorrectly and drawing problems occur as a result.

  +  /* fcfont's is_hinted controls metric hinting */
  +  PANGO_FC_FONT(cffont)->is_hinted =
  +    (cairo_font_options_get_hint_metrics(font_options) !=
  +     CAIRO_HINT_METRICS_OFF);

  Ironically I suggested this patch in December, but Owen said it wouldn't work AND the reporter said it didn't. It turned out this is the correct fix indeed.
• pango_layout_get_pixel_extents and pango_layout_get_pixel_size cause off-by-one metrics. This one was not reported and I opened myself, but was also raised in an email thread by Morten. I suspect the fix for this may have had some of the above bugs fixed, or maybe not. Anyway, it looks more correct now. The question to answer is how to round logical and ink rectangle metrics. The current code was simply rounding x, y, width, and height. Say your rounding function is f(.). There are two problems with this:
• First, f(x)+f(width) has twice the error of what you get for f(x+width). So I changed the width rounding to use (f(x+width) - f(x)) instead. Ditto for height.
  
• Next, shall we floor, round, or ceil? It used to round them all. Now we use separate functions for logical and ink extents.
  
  For ink rectangle, in Owen's words, the guarantee that we make is that you can render a layout onto a pixmap the size of its ink metrics and it won't get clipped. So I made it to floor x and y, and ceil x+width and y+height. The real thing looks like:

   int orig_x = ink_rect->x;
  int orig_y = ink_rect->y;
  
  ink_rect->x = PANGO_PIXELS_FLOOR (ink_rect->x);
  ink_rect->y = PANGO_PIXELS_FLOOR (ink_rect->y);
  
  ink_rect->width  = PANGO_PIXELS_CEIL (orig_x + ink_rect->width )
                   - ink_rect->x;
  ink_rect->height = PANGO_PIXELS_CEIL (orig_y + ink_rect->height)
                   - ink_rect->y;

  For logical rectangle, we are more interested that the rounded extents of adjacent chunks of text do not overlap or have any gaps. Which means, if x1+width1 = x2 before rounding, it should hold after rounding too. This means the same function f() should be used for x and x+width, and round() is the obvious choice here.
  
  I also audited gdkpango.c for places that roundings can be improved, not many more candidates, but there are a lot of PANGO_PIXELS and PANGO_SCALE occurences in gtk+/gtk. They all can use a pair of eyes, replacing some of them with PANGO_PIXELS_FLOOR or PANGO_PIXELS_CEIL.

¶ 9:56 PM