Re: [ft] Another problem with X11 PCF fonts and 2.7.1, now with bisect

[Markus Unterwaditzer]

PS: In fact I think this patch only has its place in a potential freetype 3.0.

On Mon, Jan 09, 2017 at 12:51:00PM +0100, Markus Unterwaditzer wrote:
> On Mon, Jan 09, 2017 at 12:29:17PM +0100, Werner LEMBERG wrote:
> > 
> > > Great, thank you! What is the default of the compile-time option?
> > 
> > It's `on' since I still think it's an improvement.
> 
> I think this behavior is problematic. A version number of the form x.y.z (with
> a changed z) colloquially implies that this release does not contain
> backwards-incompatible changes. This is obviously not the case here.
> 
> While I think about your solution, I think it actually worsens the problem. 
> Now
> it is not guaranteed that my configuration will ever be usable across
> distributions, since the packager of Debian may have made a different choice
> w.r.t. this parameter than the packager of Fedora.
> 
> So here's what I propose:
> 
> - Release a 2.7.2 based off the tag VER-2-7-1 that reverts this patch without
>   adding anything to reinstantiate this behavior.
> 
> - Save the patch for a later, larger release (either 2.8 or 3.0, depending on
>   the versioning scheme you choose)
> 
> Otherwise I think it's very likely that either a.) some distributions disable
> this feature and some don't b.) some font authors blank those additional 
> fields
> to ensure a consistent name across platforms. Neither is desirable.
> 
> Thanks,
> Markus
> > 
> > 
> >     Werner
> > 
> > _______________________________________________
> > Freetype mailing list
> > address@hidden
> > https://lists.nongnu.org/mailman/listinfo/freetype