Summary

[David Hyatt]

I actually hacked our own API into QFont to support multiple families 
(I made a QFontFamily object).  I would love to know what the official 
API is going to be so that we can massage our code into the appropriate 
format (so that it can be merged in to your trunk).

QFontMetrics also needs to be able to work with multiple fonts, in an 
extremely complicated fashion.  The rule in CSS is that if you have 
something like:

<span style="font-family: a,b,c">[glyphs from a] [glyphs from c]</span>

The font metrics for the <span> should include ONLY the fonts used by 
the <span> in the metrics computations, so e.g., fm.ascent() would be 
the max of the ascents of fonts A and C.  Even if B is supported by the 
system, it should not be used.

Something to think about if you have plans to extend QFontMetrics to 
also work with multiple families.

Our QFontMetrics in Safari isn't right yet at the moment.

dave

On Wednesday, February 19, 2003, at 11:15 PM, Lars Knoll wrote:

> Hi ,
>
> thanks for summing the conference up. I think you got most points. I 
> have some
> comments on parts of the points:
>
>>   re: rendering/font.cpp: its clear that we never reach a common 
>> codebase
>>   here. I'll just rename our file to font_x11.cpp soon in CVS, Safari
>>   can just fork the complete file and name it font_darwin.cpp or 
>> whatever.
>
> With Qt-3.2 out codebase will get simpler aswell, as QFont in 3.2 can 
> do CSS
> style name matching of a list of families. I think the safari code 
> already
> relies on this being handledd by the OS.
>