Bug 468081

I'm not seeing this problem.  Are you correct in that this is happening in text mode on rawhide?  I checked graphical mode as well, just to be sure, and didn't see a problem there either.

Created attachment 321192 [details]
Screen capture - Rawhide [Running] - Sun xVM VirtualBox.png

For the record, I used http://ftp.iasi.roedu.net/mirrors/fedora.redhat.com/linux/development/i386/os/images/boot.iso dated October 21.

I just tried it in a virtual machine and it seems to display the characters alright there but with some odd highlighting. On the laptop that I was installing, the intallation procedure started in vesa text mode and probably that's why the characters are displayed as squares.

Is this somehow related to the fact that șȘțȚ have codes over 256 ?

(In reply to comment #2)
> 
> Is this somehow related to the fact that șȘțȚ have codes over 256 ?

Answering to myself: this couldn't be because ăîâ are displayed the same way and they have codes under 256.

I remember reading somehwere about how this font fiddled with the highlighting to get more space for characters ...

Hello all,

At least in my installation of Fedora 10 rawhide these characters are not displayed correctly (they used to be in earlier versions of Fedora 9, but recently ceased to do so).

The exact Unicode codes (UTF-8) of these Romanian characters - the CORRECT ONES - are:

0218
0219
021A
021B

What we need is (at least) the following two packages included in ANY Romanian installation (and used by default):

terminus-font-console
terminus-font-x11

As far as I know, there are other font packages with correct Romanian characters in them, too (comma-below, not cedilla-below).


Regards,
Răzvan

Hi,

So what is the request for kbd package? Lat2-Terminus16 font is part of kbd since 1.12-28, Romanian keymaps were fixed release or two before that.

Did you see how the diacritics appear highlighted in the screen capture: https://bugzilla.redhat.com/attachment.cgi?id=321192 ? Is there nothing to be done do avoid that ?

On a laptop, those didn't appear at all. I'll try again with a more recent boot.iso and come back with a screenshot.

Alex, looking at the screenshot you've mentioned in comment #6, it seems there are cedilla-below diacritics, not the correct comma-below ones. Am I right ?

Răzvan

(In reply to comment #7)
> Alex, looking at the screenshot you've mentioned in comment #6, it seems there
> are cedilla-below diacritics, not the correct comma-below ones. Am I right ?
> 

That's my fault, I haven't switched the translations to the correct comma below. I'll try to fix that as soon as I can.

This bug has been triaged

This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Hello,

Is this bug still present after latest updates of Fedora 10 (as of January 29th, 2009) ?

Regards,
Răzvan

I saw that diacritic appeared highlighted (as Alexandru mentioned in Comment #6) during install. I reproduced it on Fedora 10. But I believe that correct font with comma-bellow is used. So the problem is highlighting.

I didn't find a reason, except the statement in setfont manpage (Alexandru mentioned it in Comment #3):
Note: if a font has more than 256 glyphs, only 8 out of 16  colors  can
be  used  simultaneously. It can make console perception worse (loss of
intensity and even some colors).

But then I wonder why only some characters are highlighted?

If Anaconda really uses Lat2-Terminus16 (and it should use it, because that's what we fixed time ago) - I don't know any other way how to solve it (within kbd package), than try using different font - but AFAIK Lat2-Terminus16 is the only one font that meets your criteria, again, we worked on it time ago...

This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.