Bug 450690

Summary: console in F9 is not unicode complaint when locale set to UTF-8
Product: [Fedora] Fedora Reporter: Adam Pribyl <covex>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: medium    
Version: 9CC: alsadi, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-14 00:56:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
console with unicode text in f9
none
utf8 test sentece none

Description Adam Pribyl 2008-06-10 13:40:31 UTC
Description of problem:
In F8 when LANG was set to UTF-8 then the console was set to unicode with
"unicode_start" in /etc/profile.d/lang.sh. In F9 this is not done, code for
setting console to unicode is missing.

Version-Release number of selected component (if applicable):
initscripts-8.76.2-1.i386

How reproducible:
Always

Steps to Reproduce:
1. switch to console vt1 (Alt+F1)
2. try to cat any text with UTF-8 chars - the result is quite strange
3. start unicode_start - text is immediately rendered correctly
4. start unicode_stop - comparing to 2. the result is different
  
Additional info:
Acctualy I do not care about 4, but 3 should be probably also done somewhere in F9.

Comment 1 Bill Nottingham 2008-06-10 13:59:43 UTC
Can you attach your /etc/sysconfig/i18n? I can't reproduce this in testing here.

Comment 2 Adam Pribyl 2008-06-11 20:03:32 UTC
Created attachment 308985 [details]
console with unicode text in f9

I can reporduce this with en_US.UTF-8 and cs_CZ.UTF-8. Behaviour is the same
for both when I try to display text with UTF-8 chars - in this case those are
czech accented letters. See attached screenshot with steps 2,3,4.

Comment 3 Adam Pribyl 2008-06-11 20:09:13 UTC
Please note, that this is only correctly displayed in step 3. (Mostly correct -
I do not understand why those accented letters are brigher...) Interesting thing
is that starting unicode_start changes already displayed text, while issuing
unicode_stop does not - step 4.

Comment 4 Bill Nottingham 2008-06-11 20:17:35 UTC
Just to make sure, cestina.txt is actually in UTF-8? (Not to ask the obvious...) 

I've been testing with /usr/share/doc/pango-*/HELLO.txt.

With your PNG... is this with baremetal or with virtualization of some sort?

Comment 5 Adam Pribyl 2008-06-12 11:54:31 UTC
Created attachment 309052 [details]
utf8 test sentece

Yes it is UTF-8 (attached now) - this is czech test sentece containing most of
the accented letters.

The PNG is from virualized HW (VirtualBox) but my real console gives the same
output. I used it only to capture screenshot. I can make pictures with digital
camera too. I tried also the pango HELLO file now and the result is pretty
similar. Just the czech string for Hello is not very good to demostrate this
problem because it has only one "special" character. When cating the HELLO.txt
e.g. arabic is not correctly displayed. After starting unicode_start the text
is corrected. 

I noticed also now, that when I switch from console to Xorg and back to
console, then the text is not displayed correctly anymore. I have to
unicode_start again..

Comment 6 Adam Pribyl 2008-06-18 20:43:47 UTC
In F8 there is in /etc/profile.d/lang.sh this code:

   if [ -n "$LANG" ]; then
      case $LANG in
        *.utf8*|*.UTF-8*)
        if [ "$TERM" = "linux" ]; then
            if [ "$consoletype" = "vt" ]; then
                if [ -x /bin/unicode_start ] && /sbin/consoletype fg ; then
                        for langfile in /etc/sysconfig/i18n $HOME/.i18n ; do
                                [ -f $langfile ] && . $langfile
                        done
                        /bin/unicode_start $SYSFONT $SYSFONTACM
                fi

that handles the unicode_start execution. This is not present if F9. How should
this be done in F9? Is it really not needed?

Comment 7 Muayyad Alsadi 2008-10-10 21:10:45 UTC
I confirm this bug in F9

Comment 8 Bill Nottingham 2008-10-14 00:56:00 UTC

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