Nmap Development mailing list archives
Re: [PATCH] Zenmap DiffCompare FontDescription causes error to be generated in zenmap.exe.log
From: David Fifield <david () bamsoftware com>
Date: Fri, 5 Sep 2008 22:26:16 -0600
On Sat, Sep 06, 2008 at 04:10:02AM +0100, jah wrote:
I'm getting a font error with zenmap svn on windows. From the zenmap.exe.log: <path>\zenmap.exe\zenmapGUI\App.py:183: PangoWarning: couldn't load font "Monospace Normal, Not-Rotated 9", falling back to "Sans Not-Rotated 9", expect ugly output. It happens when loading up a pair of scans in the Compare Results dialog. The font used for the contents of the Comparison text area in compare mode is, as the error says, not monospace.
Weird. I wonder why this hasn't been reported before. It has never happened to me on Windows. I can't remember the output of the graphical diff ever being in monospace. (The text diff is, but not the graphical diff.) See http://nmap.org/book/zenmap-compare.html#zenmap-fig-compare-example for a diagram I created that's not monospace.
From reading the docs at
http://pygtk.org/docs/pygtk/class-pangofontdescription.html#constructor-pangofontdescription it appears the "Monospace 9" is the correct way to get a 9-point monospace font. But I think the proportional font looks a lot better. I changed it to "Normal 9". Does that work for you? David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- [PATCH] Zenmap DiffCompare FontDescription causes error to be generated in zenmap.exe.log jah (Sep 05)
- Re: [PATCH] Zenmap DiffCompare FontDescription causes error to be generated in zenmap.exe.log David Fifield (Sep 05)