Nmap Development mailing list archives
Re: [PATCH] Zenmap DiffCompare FontDescription causes error to be generated in zenmap.exe.log
From: jah <jah () zadkiel plus com>
Date: Sat, 06 Sep 2008 15:36:10 +0100
On 06/09/2008 05:26, David Fifield wrote:
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.
You're right, it never has been monospace. It was the error message that made me think that it should be monospace.
From reading the docs athttp://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?
Normal 9 works lovely - no errors. Regards, jah _______________________________________________ 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)
- Re: [PATCH] Zenmap DiffCompare FontDescription causes error to be generated in zenmap.exe.log jah (Sep 06)
- Re: [PATCH] Zenmap DiffCompare FontDescription causes error to be generated in zenmap.exe.log David Fifield (Sep 05)