[Date Prev][Date Next][Thread Prev][Thread Next][Thread Index]
Re: [XaraXtreme-dev] Current/default font
- From: Alex Bligh <alex@xxxxxxxxxxx>
- Date: Thu, 27 Jul 2006 16:12:22 +0100
- Subject: Re: [XaraXtreme-dev] Current/default font
Martin Wuerthner wrote:
But if we do not always do it, why do it at all? Just to avoid a
single font attribute that contains the name of a font that is not
installed? We will have lots of them in the tree anyway simply by
loading a document containing fonts that are not installed. We do not
do "hard" font substition, just "soft" font substitution, i.e., the
text remains in the unknown font but when it is displayed the default
font is used instead.
I had been presuming the implementation time of either option would
be the same.
IE (in PsuedoCode)
FixFontAttributeIfUnusedAndUninstalled(CurrentAttribute);
becomes
FixFontAttributeIfUnusedAndUninstalled(CurrentAttribute);
FixFontAttributeIfUnusedAndUninstalled(DefaultAttribute);
Somewhere during the long discussion at GP it became obvious we needed
to fix both. I now can't remember why. Anyone else? But if the
implementation time is the same, why not, now we know it's harmless?
Alex