#5775 NORM Never A: It is basically impossible to install bitmapped fonts.
Zarro Boogs per Child
bugtracker at laptop.org
Sun Dec 30 11:17:05 EST 2007
#5775: It is basically impossible to install bitmapped fonts.
-----------------------------+----------------------------------------------
Reporter: karmaflux | Owner: bernie
Type: defect | Status: new
Priority: normal | Milestone: Never Assigned
Component: x window system | Version:
Keywords: font, xfs, xorg | Verified: 0
Blocking: | Blockedby:
-----------------------------+----------------------------------------------
X.org, as started by olpc-dm, uses -fp built-ins. The only font built-in
is an unreadably small instance of "fixed." Attempting to add a fontpath
with xset results in the following error message:
{{{
xset: bad font path element (#61), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
}}}
regardless of the directory permissions, the presence of fonts.dir, or
whether you start X from olpc-dm, or boot into runlevel 4 and manually
initiate X. Adding a FontPath in a "Files" section in /etc/X11/xorg.conf
results in a
{{{
Could not init font path element /usr/share/X11/fonts/100dpi/, removing
from list!
}}}
line in /var/log/Xorg.0.log.
I know that bitmapped fonts are not a priority. However, lots of legacy
x11 software is essentially unavailable to XO users with the current
configuration. Is there a compelling reason to break font handling? What
is being gained from this? May we not at least look at having built-in
fonts which are more appropriately sized for the XO's resolution?
--
Ticket URL: <http://dev.laptop.org/ticket/5775>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system
More information about the Bugs
mailing list