--- Begin Message ---
Package: tkfont
Version: 1.1-1
Severity: wishlist
Here are a list of suggestions sent to the original author, but which
bounced back into my mailbox.
> * restricting display according to XLFD parts (just like xfontsel)
> would be nice. This would be really useful, as xfontsel doesn't have
> scrollbars in its menus, and I sometimes have to inspect directories
> with > 200 fonts.
> * editting fonts.dir should IMHO not be allowed, as changes would be
> overwritten by mkfontdir. I think only fonts.alias should be edited.
> * uncompile pcf => bdf (eg. using a font server and asking him the pcf
> data.)
> * it would be nice to be able to sort the fonts according to XLFD
> fields. Right now it can be damn difficult to find closely-related
> fonts. (restricting display, as already suggested would already help
> much in this respect)
> * specifying custom sizes for scalable fonts should be easier than
> editing the bottom line.
> You seem to be puzzled by the last XLFD field. As far as I can tell,
> the actual font-encoding is defined by both of the 2 last fields. Eg
> you can have a latin1 font (ending in -iso8859-1) and a latin2 font
> (-iso8859-2), as well as others (-iso2022-0, -iso2022-1, etc.).
>
> The XLFD standard (from X docs, on any X mirror) calls them
>
> * "charset registry" is the registration authority (namespace handle
> by the X consortium) eg: "iso8859", "iso2022", etc.
> * "charset encoding" has only a meaning when associated with the
> registry, and is defined by this authority.
>
> You may find many interesting informations in this document.
--
Yann Dirson <ydirson@a2points.com> | Stop making M$-Bill richer & richer,
alt-email: <dirson@univ-mlv.fr> | support Debian GNU/Linux:
debian-email: <dirson@debian.org> | more powerful, more stable !
http://www.a2points.com/homepage/3475232 | Check <http://www.debian.org/>
--- End Message ---