Bug 116712 - Font rendering in YaST [hmm] improvable
Summary: Font rendering in YaST [hmm] improvable
Status: RESOLVED WORKSFORME
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: RC 1
Hardware: PC All
: P5 - None : Minor
Target Milestone: ---
Assignee: E-mail List
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-13 08:53 UTC by Hans-Peter Jansen
Modified: 2006-08-17 11:35 UTC (History)
1 user (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hans-Peter Jansen 2005-09-13 08:53:31 UTC 
Since RC1 doesn't suffer from obvious major flaws from what I can tell, it's 
time to complain about minor issues: 
 - the rendering of monospace fonts is much to small relative to the others 
 - generally the width of character "1" is still smaller than the other 
   numbers, which leads to disturbing jitter of certain messages (especially  
   in detailed progress dialog during installation)
Comment 1 Klaus Kämpf 2005-09-13 09:49:45 UTC 
That sounds like Qt frontend -> sh
Comment 2 Stefan Hundhammer 2005-09-13 20:57:56 UTC 
That is _clearly_ a Qt problem.
Comment 3 Dirk Mueller 2005-09-14 06:15:56 UTC 
font sizes is a Qt problem? YaST hardcodes font sizes -> YaST problem  
  
jitter in certain messages -> wrong font problem.   
  
Qt doesn't make sure that a declared-to-be-fixed font is indeed fixed, that 
would be dead slow. instead it just paints bigger chunks, and relies on the 
font not being broken. this is > factor 10 faster than drawing each character 
individually.  
 
therefore, you have to fix yast.
Comment 4 Stefan Hundhammer 2005-09-14 13:22:51 UTC 
Huh?  
  
During installation (and _only_ there) we explicitly set the size (and only 
the size) of our default (proportional) font and of our heading font - and 
that also only because Qt on its own simply _never_ gets this right. We don't 
do anything with any monospaced or other font. 
 
But as always, it's way easier to simply claim something so that we have to 
(again) prove our innocence (like in the Wild West - guilty until proven 
otherwise) and ping-pong a bug back rather than try to fix anything...
Comment 5 Dirk Mueller 2006-08-17 11:35:51 UTC 
There is no bug here that can be fixed in Qt. Qt renders the font you want. if you want a font that claims to be a certain size but is not and is not even fixed width even though it was marked as such, then it will render it that way. 

Garbage in - Garbage out. Fix your YaST.