Re: [GD-DEVEL] Re: gd2 & fontconfig/freetype fail to find fonts on Mac OS X (macports)

[Mojca M. <moj...@gm...>]

On Thu, Apr 16, 2009 at 00:53, Manfred Schwarb wrote:
> On Mon, Apr 13, 2009 at 5:56 PM, Ethan Merritt wrote:
>>
>> This looks very promising, and I think we should
>> use it to try both the old (GDFONTPATH) and new (fontconfig) mechanisms
>> when looking for a user-specified font.
>
> Sorry to spoil the party -
>
> Does this mean, not even the ugly work-around to set
> GDFONTPATH=/dev/null to get the builtin fixed fonts of libgd
> will work any more?
>
> I really would like to have a possibility to use the builtin fonts.
>
> The simplest thing would be to treat the libgd font names special?
>
> I.e. if the the font name is one of
> "tiny","small","medium","large","giant" treat them special,
> skip font lookup and directly use the respective libgd builtin fonts?
>
> I.e. the use would then be as
> ...
> set term png font "small"
> ...

Hello,

Enabling fontconfig search by deafault doesn't mean that one should
disable the built-in fonts. At least in my opinion it still makes
sense to allow using them without having to issue an error. The
keywords "tiny" "small" etc. to trigger built in fonts make perfect
sense to me and you don't even need the work-around. When one sets
    font ",15"
this could mean "use true type using fontconfig" while small could
trigger the built-in fonts.

(I didn't have to use the ugly workaround to set GDFONTPATH to
/dev/null since it didn't work anyway and I always get the built-in
fonts. Because neither fonts nor graphics have been anti-aliased and
because setting "arial" didn't work out-of-the-box, I always thought
that I was unable to compile GD library support properly.)

Mojca