FS#6112 - Tool 'km' does not handle codepage font files properly
Attached to Project:
Arch Linux
Opened by Dennis Herbrich (gyroplast) - Saturday, 30 December 2006, 23:01 GMT
Opened by Dennis Herbrich (gyroplast) - Saturday, 30 December 2006, 23:01 GMT
|
Details
The handy little tool '/bin/km' as supplied on the 0.8 Alpha
isos,
used to choose keymap and a console font with a GUI, uses a method to scan for fonts that is unsuitable in it's current state. Line 37 of the script contains the following code: for i in `find $BASEDIR/consolefonts -follow -name "*.gz" | sed '|^.*/||g' | sort`; do Unfortunately, this also includes codepage font files, usually marked by a filename pattern of *.cp.gz. These codepage font files really include three different font sizes of the same font, and must therefore be loaded by the setfont command with the size option, ie. setfont -16 880.cp.gz OR setfont -8 880.cp.gz The calls to setfont later in the script on lines 54 and 56 do not use this size option for obvious reasons, and therefore the user is presented with appropriate error messages when trying to load any of the console fonts ending on .cp.gz. Fix considerations: That's a bit tricky. Ideally, the user would be presented in the font menu three distinct choices of each codepage font, each representing one of the available sizes, and another call to setfont handling these choices accordingly. This would require some more conditional logic than just the little find command used right now, and might make the script a bit clumsy to look at, but seems like the user-friendliest choice to me. Alternatives are removing the *.cp.gz files altogether from the menu, or forcing a hardcoded font size in these cases, or whatever else strikes your fancy. See Task #6111 for another bug in the list of fonts presented in the menu. |
This task depends upon