Re: master d8da850: Document cairo-related fallout to font-backend settings

[T.V Raman]

Stefan Kangas <address@hidden> writes:

Also, perhaps update frames.texi to indicate that ftcr and ftcrhb are
mutually incompatible. Having both doesn't appear to hurt right now, but
 might perhaps cause issues later?> Robert Pluim <address@hidden> writes:
>
>> The correct choice depends on how their Emacs has been built; ftcr and
>> ftcrhb are mutually exclusive [1](see my earlier update to the elisp
>> manual). I guess we could say something like this:
>
> Indeed, I read that after I wrote the above.
>
>> -Cairo.  Use either 'ftcr' or 'ftcrhb' instead for FreeType and
>> -FreeType + HarfBuzz respectively.  'x' is still a valid backend.
>> -
>> +Cairo.  Use 'ftcrhb' if your Emacs was built with HarfBuzz support,
>> +and 'ftcr' otherwise.  You can this determine by checking
>> +'system-configuration-features'.  'x' is still a valid backend.
>
> Thank you, that is much better.  Please install.
>
>> [1]  My master plan to remove as many different variations as possible
>>      seems to get shot down every time I suggest it :-)
>
> BTW, if 'ftcr' only works when built without HarfBuzz, and 'ftcrhb'
> only works with HarfBuzz, can't we just use 'ftcr' and detect HarfBuzz
> automatically for the user?
>
> Best regards,
> Stefan Kangas
>

--