FS#55852 - [chromium] macOS font (.dfont) support
Attached to Project:
Arch Linux
Opened by Mantas Mikulėnas (grawity) - Tuesday, 03 October 2017, 16:06 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 21 November 2017, 02:52 GMT
Opened by Mantas Mikulėnas (grawity) - Tuesday, 03 October 2017, 16:06 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 21 November 2017, 02:52 GMT
|
Details
Arch's freetype2 has FT_CONFIG_OPTION_MAC_FONTS enabled, but
the bundled Chromium freetype2 does not. This results in
weird things happening when the text is about to be rendered
using a Mac font file, see <https://crbug.com/766154>.
If possible please enable this option.
|
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Tuesday, 21 November 2017, 02:52 GMT
Reason for closing: Upstream
Additional comments about closing: As per my original comments, I will not be changing the configuration of bundled libraries.
Tuesday, 21 November 2017, 02:52 GMT
Reason for closing: Upstream
Additional comments about closing: As per my original comments, I will not be changing the configuration of bundled libraries.
Comment by
Evangelos Foutras (foutrelis) -
Saturday, 07 October 2017, 14:26 GMT
Comment by
Eli Schwartz (eschwartz) - Monday,
09 October 2017, 20:47 GMT
Comment by
Evangelos Foutras (foutrelis) -
Monday, 09 October 2017, 20:54 GMT
It's up to upstream to adjust the configuration of bundled
libraries. Assuming Chrome behaves the same way, I don't consider
this something that needs to be fixed downstream in Arch.
It sounds like the issue is that the configuration of the bundled
library is somehow disagreeing with the system copy of freetype2,
so how *should* Chromium adjust the configuration?
Chromium is using its bundled copy of freetype which is configured
by upstream. The system freetype isn't used at all so its
configuration is irrelevant.