Bug 199997

Summary:	Wrong character/encoding/charset for displaying default selection in boot loader settings
Product:	[openSUSE] openSUSE 10.2	Reporter:	Matthias Hopf <mhopf>
Component:	Installation	Assignee:	Mike Fabian <mfabian>
Status:	RESOLVED FIXED	QA Contact:	Stanislav Visnovsky <visnov>
Severity:	Minor
Priority:	P5 - None	CC:	kde-maintainers, suse-beta
Version:	Alpha 3
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Matthias Hopf 2006-08-17 15:13:47 UTC

During installation, when selecting the boot load settings, the current default selection is marked, but the character shows the rectangle for a unknown character.

This is cosmetics and doesn't change behavior. But it is the same for a couple of years now.

Note that I'm installing the system in English (default selection).

Comment 1 Philipp Thomas 2006-11-17 15:18:14 UTC

Seems to be locale dependent, as setting to german gets you the expected character.

Comment 2 Mike Fabian 2006-11-17 19:56:46 UTC

I investigated a little bit with Philipp Thomas and we found
that it depends on the screen resolution. On some resolutions,
Qt3 used "Efont Biwidth:pixelsize=16" (b16.pcf.gz) and this
font doesn't have the Checkmark.

For other resolutions, where the required font sizes differs from 16
pixel, Qt3 uses "DejaVu Sans" which has the check mark glyphs.

This is a Qt3 problem, Qt3 should always prefer "DejaVu Sans",
independent of the size, I don't know why Qt3 prefers the bitmap font
sometimes.

Although I think this is a Qt3 problem, I could work around it by
adding the checkmark (and the other special symbol glyphs used by
Yast2) to b16.pcf.gz as well.

Comment 3 Mike Fabian 2006-11-19 20:42:04 UTC

kde-maintainers: do you think there is any hope fixing Qt3 not to use
bitmap fonts if a scalable font is available which supports the same
glyphs (unless the bitmap font is explicitely requested of course)?

Or should I add the missing glyphs to b16.pcf.gz?

Comment 4 Stephan Kulow 2006-11-20 12:13:54 UTC

fixing qt3 will be very hard, adding the missing glyphs should be pretty straightforward. And I sure hope a qt3 yast is going to die soonish - and Qt4 has a completly different engine. 

So either WONTFIX or fix the font

Comment 5 Matthias Hopf 2006-11-20 14:14:53 UTC

As this is a qt3 problem and not a pressing issue, I suggest WONTFIX.

Comment 6 Mike Fabian 2006-11-20 16:31:05 UTC

For a list of the needed glyphs for YaST2 see bug #74601 comment #21.

Comment 7 Mike Fabian 2006-11-21 18:41:11 UTC

Improved efont-unicode package submitted to stable.  All the halfwidth
fonts contain all the special symbol glyphs used by YaST2 now.
-------------------------------------------------------------------
Tue Nov 21 19:00:19 CET 2006 - mfabian@suse.de

- Bugzilla #199997: Add the special glyphs needed by YaST2
  to the halfwidth fonts. 

-------------------------------------------------------------------

Closing as FIXED.