[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

lucidatypewriter warning, examine.C patch and comments

From: Žarko Živanov
Subject: lucidatypewriter warning, examine.C patch and comments
Date: Tue, 08 May 2012 19:35:11 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20120313 Lightning/1.0b2 Thunderbird/3.1.20

1. When running DDD on newer distros (Ubuntu), the following warning can be 
seen upon starting:

Warning: Could not load font "-*-lucidatypewriter-medium-*-*-*-*-120-*-*-*-*-iso8859-*", 
using font "fixed" instead
Warning: Could not load font "-*-lucidatypewriter-medium-r-*-*-*-120-*-*-*-*-iso8859-*", 
using font "fixed" instead
Warning: Could not load font "-*-lucidatypewriter-bold-*-*-*-*-120-*-*-*-*-iso8859-*", 
using font "fixed" instead

After that, DDD is started with small and relatively ugly font. The problem is that on these 
distros, there is no iso8859 variant of lucidatypewriter, it is replaced by some other iso number 
(I forgot which). Problematic function is in fonts.C file: string fallbackfont(DDDFont font). By 
simply replacing string "iso8859" in font description with "*", the problem is 

2. One patch I submitted for examine.C doesn't work on AMD processors because 
of wrong detection of CPU. On line 199 there is an if like this:
    if (GDB == gdb->type() && gdb->cpu == cpu_intel) {
and the code is executed only if CPU is detected as cpu_intel. AMD CPUs (at 
least, their Sempron processors) are NOT detected as cpu_intel, and therefore, 
the code inside if will never be executed. Temoprarily, I changed above if to
    if (GDB == gdb->type()) {
This solves the AMD problem, but the real problem is in CPU detection, and I 
don't know how to fix that.

3. When I submitted my patch for review, there were still some comments in 
Serbian in it. They were copied to examine.C. Please, remove them, they are not 
international. If there is an interest, I could make english comments.

I don't know is DDD still maintained, but if it is, please include this in its 

Best regards,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]