[Development] Removal of xlib plugin - a possible disaster.

[Thiago Macieira]

On terça-feira, 20 de março de 2012 07.21.37, jiang.jiang at nokia.com wrote:
> Hi Thiago,
> 
> On Mar 19, 2012, at 9:50 PM, ext Thiago Macieira wrote:
> >> That started happening sometime between 17 Feb. and now, FWIW; I
> >> suspect it's quite recent.  At least the default font choice has
> >> gotten better.
> > 
> > It's a horrible choice now. Creator uses by default the font "Monospace"
> > in Qt 4.x. For whatever reason, in Qt 5 that font (an alias) is not
> > present.
> It should just work. In Qt 5 we do have the logic to use fontconfig to
> convert aliases like "Monospace" into actual fonts mapped into your system,
> like "Courier". I will try it with a recent xcb build now.

That's the point: I don't want it to convert. I want to configure my system to 
use "Monospace" and let fontconfig decide which font that is. If I were to 
change my fontconfig settings, the applications should change too.

More importantly: I don't think the conversion is working properly. The system 
default is "Monospace", which is mapped to "DejaVu Mono", but on first start 
Creator showed with a very different font and really hard to read.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
     Intel Sweden AB - Registration Number: 556189-6027
     Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20120320/d25d21df/attachment.sig>