On 10 September 2015 at 02:41, Keith Packard wrote:
> Emil Velikov writes:
>
>> From a very quick look, only fontstruct.h seems to be used. If truly
>> so, one can rework it (rename or fold into libxfont2.h, rename the
>> symbols ?) and drop the rest
Emil Velikov writes:
> Had a long hard look at the Archlinux repos and did not see (m)any
> libxfont users outside of xserver. Would you/others know if they're
> still a thing or they share the same faith as the print server :-)
There really shouldn't be any other than
On 09/10/15 10:44 AM, Keith Packard wrote:
Emil Velikov writes:
Had a long hard look at the Archlinux repos and did not see (m)any
libxfont users outside of xserver. Would you/others know if they're
still a thing or they share the same faith as the print server :-)
Alan Coopersmith writes:
> mkfontdir is now a wrapper around mkfontscale which doesn't use libXfont,
> just libfontenc & libfreetype.
Oh, nice. I hadn't realized that.
> bdftopcf could probably be similarly rewritten to use FreeType directly.
We'd have to provide
Emil Velikov writes:
> From a very quick look, only fontstruct.h seems to be used. If truly
> so, one can rework it (rename or fold into libxfont2.h, rename the
> symbols ?) and drop the rest from libXfontinclude_HEADERS.
fontstruct.h comes from proto/fontsproto
Hi Keith,
On 2 September 2015 at 22:30, Keith Packard wrote:
> This eliminates the weak symbol adventures and makes all of the calls
> back to the X server or Font server go through a table of functions
> instead, clarifying the required API.
>
> As this is a rather major
On Wed, Sep 9, 2015 at 18:30:55 +0100, Emil Velikov wrote:
> In parallel to Matt's question - if we do opt for a separate library
> (libXfont2), the headers will clash with libXfont's.
>
> From a very quick look, only fontstruct.h seems to be used. If truly
> so, one can rework it (rename or
This eliminates the weak symbol adventures and makes all of the calls
back to the X server or Font server go through a table of functions
instead, clarifying the required API.
As this is a rather major change to the API for the library, it now
installs itself as libXfont2 instead of libXfont, and
On Wed, Sep 2, 2015 at 2:30 PM, Keith Packard wrote:
> This eliminates the weak symbol adventures and makes all of the calls
> back to the X server or Font server go through a table of functions
> instead, clarifying the required API.
>
> As this is a rather major change to the