From f853b695de6bad0d59153211cdb63bea6722976e Mon Sep 17 00:00:00 2001 From: Simon Tatham Date: Sun, 16 Aug 2015 09:29:47 +0100 Subject: [PATCH] Remove an outdated comment. I've just noticed the comment in gtkfont.c that said wouldn't it be nice to find a way to avoid the GDK pixmap-stretching code when using Pango fonts. We now do support this, but we support it in gtkwin.c rather than gtkfont.c - because we do it using a Cairo transformation matrix, so it still takes place at the level above Pango rather than in Pango proper. (I never did find out whether Pango itself included facilities to arbitrarily stretch a font.) Hence, this comment is useless now. Discard. --- unix/gtkfont.c | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/unix/gtkfont.c b/unix/gtkfont.c index bb315d7c..0fcc4d4b 100644 --- a/unix/gtkfont.c +++ b/unix/gtkfont.c @@ -34,16 +34,6 @@ * - it would be nice to have a display of the current font name, * and in particular whether it's client- or server-side, * during the progress of the font selector. - * - * - it would be nice if we could move the processing of - * underline and VT100 double width into this module, so that - * instead of using the ghastly pixmap-stretching technique - * everywhere we could tell the Pango backend to scale its - * fonts to double size properly and at full resolution. - * However, this requires me to learn how to make Pango stretch - * text to an arbitrary aspect ratio (for double-width only - * text, which perversely is harder than DW+DH), and right now - * I haven't the energy. */ #if !GLIB_CHECK_VERSION(1,3,7)