CLIM mail archive
[Prev][Next][Index][Thread]

text-style to font mapping algorithm

    Date: Fri, 4 Dec 1992 12:30 EST
    From: Meir Laker <meir@watson.ibm.com>


    I have not yet received a reply to the following from Lucid.  So, I am
    submitting it also to the CLIM mailing list for help.  The question I
    pose regarding the CLIM algorithm for mapping text-styles to fonts is
    germane to all platforms and should be of interest to all readers.

    I have 2 questions / bugs:

    1. The text style '(:sans-serif :roman :normal) maps to:

       -linotype-helvetica-medium-r-normal--16-120-100-100-p-86-iso8859-2

    rather than to:

       -adobe-helvetica-medium-r-normal--14-140-75-75-p-77-iso8859-1

    even though the adobe font precedes the linotype font in the font path.

    This seems to indicate that somehow CLIM believes the linotype font to
    be a better mapping than the adobe font.  Could it be that the pixel
    size of 16 is "preferred" over 14 for :normal text-size?  What exactly
    is the algorithm used to map text styles to fonts in Lucid CLIM?


    2. According to the CLIM documentation, the :text-size attribute can
    be specified in "printer's points".  If so, the following would seem
    to be errors:

       A. '(:sans-serif :roman 14) maps to
	   -adobe-helvetica-medium-r-normal--18-180-75-75-p-98-iso8859-1
	   which is a point size of 180

       B. '(:sans-serif :roman 140) maps to
	   -adobe-courier-medium-r-normal--12-120-75-75-m-70-iso8859-1
	   which is a point size of 120.

    The latter case certainly seems wrong as it is seriffed.

Though the text size can be specified in printers points, that doesn't
mean that a particular CLIM back end will map that text style to a
device-specific font of that size.  It would be nice if it did but this
is not always possible.

0,,
References:
Main Index | Thread Index