Re: What determines the available font sizes?

[Peter Dyballa <Peter_Dyballa@Web.DE>]

Am 08.06.2005 um 17:37 schrieb David Reitter:

> On 8 Jun 2005, at 16:24, Peter Dyballa wrote:
>>
>> Maybe this way:
>>
>>     (create-fontset-from-fontset-spec
>>     "-*-monaco-medium-r-*-*-0-*-*-*-*-*-fontset-10pt_monaco,
>>               
>> latin-iso8859-1:-*-monaco-medium-r-normal--10-100-75-75-m-100-mac- 
>> roman,
>
>
> Sure that'll include the font, but not in an arbitrary size, will it?
> Arbitrary as in: I set the size, not as in: Emacs or whoever choses  
> some size.
>
> How do I set the size for it then?
>

I hoped you would do some experiments with the fontset definition -- I  
did some time ago when I tried to re-write and enhance my own fontset  
definitions and so I found that Cyrillic and Central European glyphs  
could scale from some points (almost invisible 5) up to 50. The other  
Latin glyphs only scaled in discrete steps, hence I think of those  
bloody bitmaps! One cure could be to clean up Monaco.dfont from the  
bitmapped fonts ...


There can be other reasons too. Pfaedit tells me:

	Warning: Glyph 284 is named Gcedilla which should mean it is mapped to
	 Unicode U+0122, but Glyph 360 already has that encoding.
	Bad lookup table format=8, first=32 cnt=778 total glyphs in font=810

Could be this makes the use of the scalable TT glyphs impossible ...

Here's one of my stripped-down lines:

           cyrillic-iso8859-5:-*-monaco  
cy-medium-r-normal--63-*-*-*-m-*-mac-*,

Bitstream Courier, i.e.  
-*-courier-medium-r-normal--*-*-*-*-m-*-mac-roman, is easy scalable.

--
Greetings

   Pete

The day Microsoft makes something that doesn't suck is the day they  
start selling vacuum cleaners.