Re: Monspace font as squares

On Thursday, 15 November 2018 13:02:46 CET Antoine Hoarau wrote:
> It works ! Thanks you !
> Antoine

Thanks for the quick feedback.

The patch is in, and will be part of KDevelop 5.3.1 (to be released).

Regards,
Kevin

> Le jeu. 15 nov. 2018 à 12:16, Kevin Funk <[email protected]> a écrit :
> > On Friday, 2 November 2018 21:19:46 CET Friedrich W. H. Kossebau wrote:
> > > Am Freitag, 2. November 2018, 20:23:13 CET schrieb Friedrich W. H.
> > 
> > Kossebau:
> > > > Am Freitag, 2. November 2018, 19:46:17 CET schrieb Antoine Hoarau:
> > > > > I'm using AppImage yes.
> > > > > In the Appimage Kdev5, if I change the font to anything else it
> > > > > works
> > > > > fine,
> > > > > except the build windows that seems stick with monospace.
> > > > > Is there any way to change the build windows font ?
> > > > 
> > > > No, the font in the build windows is currently hardcoded to use the
> > > > system's fixed font
> > 
> > (QFontDatabase::systemFont(QFontDatabase::FixedFont),
> > 
> > > > which is queried from the platform thene integration plugin.
> > > > Which might be something based on QGenericUnixTheme, which sets a
> > > > QFont
> > > > initialized with the family "monospace" (&
> > > > setStyleHint(QFont::TypeWriter);).
> > > > 
> > > > See
> > 
> > https://code.woboq.org/qt5/qtbase/src/platformsupport/themes/genericunix/
> > 
> > > > qgenericunixthemes.cpp.html
> > > > 
> > > > Not sure if that theme is really in use, but it might be. Also unsure
> > 
> > how
> > 
> > > > the resolution then happens, if that string is passed 1:1 to
> > 
> > fontconfig.
> > 
> > > > Can you tell what the result of "fc-match monospace" is on the normal
> > > > commandline and what in the embedded shell/konsole of KDevelop?
> > > 
> > > Another possible reason found meanwhile is that possibly the
> > 
> > libfontconfig
> > 
> > > (2.8 as from centos 6) as used for the appimage and linked by the qt qpa
> > > plugin used in the appimage is not able to read some newer format of the
> > > font config files as supported by fontconfig >= 2.11 (as used on ubuntu
> > > 16.04).
> > 
> > That's a good explanation I think.
> > 
> > @Antoine, could you try the following:
> > 
> > ./KDevelop-5.3.0-x86_64.AppImage --appimage-extract
> > cd squashfs-root
> > rm rm usr/lib/libfontconfig.so.1
> > ./AppRun
> > 
> > I've already filed a patch [1], but if you can confirm that works for you
> > that'd be great.
> > 
> > Regards,
> > Kevin
> > 
> > 
> > [1] https://phabricator.kde.org/D16893
> > 
> > > A possible solution might be not to use the stock libfontconfig from
> > 
> > centos
> > 
> > > 6 for the appimage build, but also provide sources from a recent version
> > 
> > of
> > 
> > > libfonrconfig which also supports reading the old config format, so both
> > > old and the new non-backward compatible font config file formats are
> > > supported. Cmp. e.g. https://github.com/OpenShot/openshot-qt/issues/1775
> > > 
> > > Superficially researched by reading other bug reports on a quick web
> > 
> > search,
> > 
> > > just dumping here to sync with what was said on irc.
> > > 
> > > Cheers
> > > Friedrich
> > 
> > --
> > Kevin Funk | [email protected] | http://kfunk.org


-- 
Kevin Funk | [email protected] | http://kfunk.org

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQQ2TvpfY5VykH05KZnGTPVrE8rOXQUCW+1rRgAKCRDGTPVrE8rO
XcATAKCRufVbrQS6HJ7IVmDi/3s+QMoEbgCgrNoX4HWkGP+1DfStQQuUYxJpQ50=
=GhPV
-----END PGP SIGNATURE-----