<!-- SBZ_reproduce  -->
Install beta4 from CDs.

* This comment was added by mail.
Qt problem.

YaST2 uses the following glyphs for symbols:


qt/src/CVS/Base/YUIQt.cc:

YCPString
YUIQt::glyph( const YCPSymbol & glyphSymbol )
{
    string sym = glyphSymbol->symbol();
    QChar unicodeChar;

    // Hint: Use 'xfd' to view characters available in the Unicode font.

    if      ( sym == YUIGlyph_ArrowLeft		)	unicodeChar = QChar( 0x2190 );
    else if ( sym == YUIGlyph_ArrowRight	)	unicodeChar = QChar( 0x2192 );
    else if ( sym == YUIGlyph_ArrowUp		)	unicodeChar = QChar( 0x2191 );
    else if ( sym == YUIGlyph_ArrowDown		)	unicodeChar = QChar( 0x2193 );
    else if ( sym == YUIGlyph_CheckMark		)	unicodeChar = QChar( 0x2714 );
    else if ( sym == YUIGlyph_BulletArrowRight	)	unicodeChar = QChar( 0x279c );
    else if ( sym == YUIGlyph_BulletCircle	)	unicodeChar = QChar( 0x274d );
    else if ( sym == YUIGlyph_BulletSquare	)	unicodeChar = QChar( 0x274f );
    else return YCPString( "" );

    QString qstr( unicodeChar );

    return YCPString( toUTF8( qstr ) );
}


To make this work, Adrian could make these glyphs required in Qt
if a symbol font is requested.

*** Bug 61312 has been marked as a duplicate of this bug. ***

not really a bug, just a question who is asked which font is the best ... 
 
I do prefer MiscellaneousSymbols fonts with tics over others now. 

<!-- SBZ_reopen -->Reopened by mfabian@suse.de at Thu Sep 30 12:16:45 2004, took initial reporter aj@suse.de to cc

Still doesn't work with beta5.

Works for me.

* This comment was added by mail.
aj> Works for me.

I installed in Japanese. Could this be locale dependent?

only if any additional font claims to have this glyph, but doesn't have it 
actually. 

Mike, this works for me now.  Could you check this again, please? 

* This comment was added by mail.
aj> Mike, this works for me now.  Could you check this again, please?

It did not work for me with Beta5 when installing in Japanese.

That's bad - so, what can we do?  Is it just the tics that are missing 
or is more broken? 

Mike, please show the bug in action on monday. 

* This comment was added by mail.
aj> That's bad - so, what can we do?  Is it just the tics that are missing 
aj> or is more broken?

With the SLP install in Japanese, only the tics were broken,
everything else was fine.

Created attachment 24564 [details]
installation-steps-dialog-000.png

screen shot from an installation in Japanese of SuSE Linux 9.2 RC1.
Screen resolution 

At the left of the screen, the tics are visible. But in the centre of the
screen on box is visible where a symbol character should be.

I think it is probably a good idea to add the 8 symbol characters YaST2 uses 
(see comment #2) to the "SUSE" fonts (extensions of the Bitstream Vera fonts
made by Adrian).

* This comment was added by mail.
I just installed SuSE Linux 9.2 RC3 in Japanese using 1024x768 pixels
resolution during the installation.

The tics were OK.

Looks like it depends on the resolution whether the tics are OK or
not.

This is not so surprising because the Gnu Unifont is a bitmap font
(not scalable). At high resolutions (1600x1200) Qt apparently refuses
to use the Gnu Unifont for the tics but uses the SUSE Sans instead
which doesn't have the tics.

not critical  

Hello!

Due to the proposal from Andreas Jaeger, this bug will be closed as WONTFIX,
because there was no change to this bug for more than 2 months by now which
indicates a very low activity. 

If this bug is of relevance for the current release or should be kept open due
to another (not obvious reason), please reopen it ans state a reason for your
decision.

Please also check if the status-information for this bug is correct at all
correct if you reopen it. Generally the product-version should be elevated to
the current release in this case. Sorry if this causes you any inconvenience.

Kind regards,
the BNC-Screening-Team

Move bug to SuSE 10.1.

*** This bug has been marked as a duplicate of 97959 ***