Re: including fontconfig utilities to windows binary packages

[Tatsuro M. <tma...@ya...>]

----- Original Message -----

> From: Allin Cottrell 
> To: Ethan A Merritt 
> Cc: gnuplot-beta Tatsuro MATSUOKA  bmaerkisch
 Date: 2018/5/3, Thu 02:57
> Subject: Re: including fontconfig utilities to windows binary packages
> 
> On Wed, 2 May 2018, Ethan A Merritt via gnuplot-beta wrote:
> 
>>  On Tuesday, May 1, 2018 7:56:54 PM PDT Tatsuro MATSUOKA wrote:
>>>  I propose that we include fontconfig utilities to windows binary 
> packages.
>> 
>>  I do not know how fontconfig works on Windows.
>> 
>>  On linux fontconfig keeps track of all the fonts installed on the system,
>>  so installing it for only one program would not make sense.
>>  If you include fontconfig with a gnuplot binary for Windows, would you
>>  also have to include lots of fonts?  If so I don't think we want to do 
> that.
> 
> No, surely not. And insofar as we're talking about terminals based on the 
> pango/cairo/glib stack on Windows, there's no need to involve fontconfig (or 
> freetype) at all. The pango backends that are needed are just Cairo and Win32 
> (the Win32 backend being an alternative to freetype + fontconfig that taps into 
> native Windows font management).
> 
> Allin Cottrell

gd also requires fontconfig/freetype if one use standard syntax for fonts
for current gnuplot.

If one compiles libraries of pango/cairo/glib in standard way on windows or use libraries supplied by 
Msys2 + MinGW w64, freetype and  fontconfig is linked and 
gnuplot uses fontconfig/freetype libraries.

As I wrote, unlike unix system, each application has their on fontconfig setting like octave for windows and MiKTeX.

Therefore I had made proposal

Tatsuro