From 442475840c83457e65685b93ed9e657898962a42 Mon Sep 17 00:00:00 2001 From: "bryner%brianryner.com" Date: Thu, 14 Oct 2004 18:51:33 +0000 Subject: [PATCH] Back out 238598 until I can convince myself that XftTextExtents does something reasonable when given a nbsp character, in the case where the font doesn't have it. --- gfx/src/gtk/nsFontMetricsXft.cpp | 7 ------- 1 file changed, 7 deletions(-) diff --git a/gfx/src/gtk/nsFontMetricsXft.cpp b/gfx/src/gtk/nsFontMetricsXft.cpp index d1aaa8a08fc..eab00d586c0 100644 --- a/gfx/src/gtk/nsFontMetricsXft.cpp +++ b/gfx/src/gtk/nsFontMetricsXft.cpp @@ -902,13 +902,6 @@ nsFontMetricsXft::CacheFontMetrics(void) nsFontXft * nsFontMetricsXft::FindFont(PRUint32 aChar) { - // If we have an NBSP character, we can treat it as a normal space. - // This helps because some fonts don't claim to support NBSP, and we waste - // time looking for a font that does. The only difference is for - // line-breaking, and that has already been done for us in layout. - - if (aChar == 0xa0) - aChar = ' '; // If mPattern is null, set up the base bits of it so we can // match. If we need to match later we don't have to set it up