|
Bugzilla – Full Text Bug Listing |
| Summary: | Font rendering in YaST [hmm] improvable | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Hans-Peter Jansen <hpj> |
| Component: | YaST2 | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | hpj |
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Hans-Peter Jansen
2005-09-13 08:53:31 UTC
That sounds like Qt frontend -> sh That is _clearly_ a Qt problem. 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. 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... 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. |