Bug 180417 - CJKI text installation should be in english
Summary: CJKI text installation should be in english
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Cantrell
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks: FC6Blocker 171491 202738
TreeView+ depends on / blocked
 
Reported: 2006-02-08 00:49 UTC by Lawrence Lim
Modified: 2014-03-26 00:53 UTC (History)
6 users (show)

Fixed In Version: anaconda-11.1.0.84-1.i386.rpm
Clone Of:
Environment:
Last Closed: 2006-08-29 05:48:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
screenshot of anaconda stage 2 with Traditoinal Chinese selected (59.24 KB, image/png)
2006-02-08 00:50 UTC, Lawrence Lim
no flags Details
Message box showing that CJKI is not avaiable for stage 2 (14.50 KB, image/jpeg)
2006-08-22 07:20 UTC, A S Alam
no flags Details
Next page after warning (126.94 KB, image/jpeg)
2006-08-22 07:24 UTC, A S Alam
no flags Details

Description Lawrence Lim 2006-02-08 00:49:03 UTC
Description of problem:
Selecting any of the CJK language for installation has display error during
Stage 2 of installation. (see screenshot) No problem when selecting English as
the language for installation.

Version-Release number of selected component (if applicable):
anaconda-10.91.4-1.i386.rpm

How reproducible:
Always

Steps to Reproduce:
1.enter linux text at the prompt
2.select Chinese, Japanes or Korean as the language for installation
3.
  
Actual results:
see screenshot

Expected results:
installation proceed in english

Additional info:

Comment 1 Lawrence Lim 2006-02-08 00:50:24 UTC
Created attachment 124345 [details]
screenshot of anaconda stage 2 with Traditoinal Chinese selected

Comment 2 Leon Ho 2006-02-14 06:16:19 UTC
Seems this is unusable. marking this as FC5Blocker.

Comment 3 Rahul Sundaram 2006-02-20 11:04:27 UTC

These bugs are being closed since a large number of updates have been released
after the FC5 test1 and test2 releases. Kindly update your system by running yum
update as root user or try out the third and final test version of FC5 being
released in a short while and verify if the bugs are still present on the system
.Reopen or file new bug reports as appropriate after confirming the presence of
this issue. Thanks

Comment 4 Warren Togami 2006-02-21 05:58:38 UTC
Solution: If CJKI language in text install, set LANG=en_US.UTF-8?


Comment 5 David Cantrell 2006-02-21 16:17:18 UTC
I think there's a problem with bogl, but I don't know enough about it to figure
it out quickly.  See the error with bogl and the /dev/fb0 error in loader2?

I modified lang-table to use en_US.UTF-8 for Chinese, Japanese, and Korean. 
Running a text mode install now has reabable text in English, which is probably
better than the screenshot above for FC5 final.

I'll close this one, but I'm opening another bug about bogl because I think
that's the real problem.

Comment 6 Bill Nottingham 2006-02-21 17:26:00 UTC
Does this change what anaconda *writes*?

Comment 7 Warren Togami 2006-02-21 17:57:47 UTC
To be clear, this is an issue for also Indic langauage text-mode installs.

if (CJKI && text install)
then *view* English during the text install
     write the actual language in configs
else
    Install in graphical mode viewing the native language
endif

Comment 8 David Cantrell 2006-02-21 22:56:36 UTC
OK, all languages listed in lang-table as having a font of bterm or none will
now display en_US.UTF-8 during installation in text mode.  The
/etc/sysconfig/i18n file is still written with the selected language, so once
you reboot you should be seeing the correct language in firstboot and X and so
on.  Graphical installation mode is unaffected.

Changes committed to CVS, new anaconda building.  Going home.

Comment 9 Lawrence Lim 2006-03-02 23:49:34 UTC
Not sure if it is a regression due to this bug. Noticed the following traceback
at the beginning of stage 2 during text installing with korean language support.

anaconda-10.92.14-1.i386.rpm

03:45:36 CRITICAL: Traceback (most recent call last):
  File "/usr/bin/anaconda", line 1214, in ?
    intf.run(id, dispatch)
  File "/usr/lib/anaconda/text.py", line 455, in run
    "%s display is unavailable in text mode.  "
NameError: name 'oldlang' is not defined

03:45:36 INFO    : in run, screen = <snack.SnackScreen instance at 0xb7d6ca2c>


Comment 10 David Cantrell 2006-03-03 16:42:21 UTC
Hmmm...possible.  Looking in to it now.

Comment 11 David Cantrell 2006-03-03 19:38:30 UTC
This isn't happening to me on today's rawhide.  What language and keymap are you
selecting for text mode?

Comment 12 Lawrence Lim 2006-03-06 00:17:23 UTC
RE: Comment #11
Still happen for me in today's rawhide (rawhide-20060305) anaconda-10.92.16-1.
Checked again with 'Japanese' and 'Hindi' as language, both using 'us' keymap.

Comment 13 David Cantrell 2006-03-06 14:59:12 UTC
When booting rawhide, I get these messages when I select Japanese or Hindi and
the US keymap:

ja_JP.UTF-8 display is unavailable in text mode.  The installation will continue
in English.

hi_IN.UTF-8 display is unavailable in text mode.  The installation will continue
in English.

The installation proceeds in text mode, but in English.  The target system is
setup with the selected language though.

How are you getting rawhide to boot on your system?  Perhaps there are some
differences there that I'm not seeing.  I've done network and CD boots to test
this and it's working as it should.

Comment 14 Lawrence Lim 2006-03-06 23:02:00 UTC
RE: Comment #13.

My bad, should have mentioned that the problem is at Stage 2 of the installation
process. Everything works correctly in Stage 1 of the installation process.

Comment 15 David Cantrell 2006-03-07 14:56:53 UTC
But it's still working in stage 2.  You select Japanese or Hindi with a US
keymap and the installation proceeds all the way through in English.

Are you sure you're booting with rawhide?  This problem has been fixed.

Comment 16 A S Alam 2006-06-14 09:21:39 UTC
Envirnemt: 
------------
Rawhide Build 13June2006
--------------


Showing Following Error for ja_JP locale (us keyboard)
---------------
Traceback (most recent call last):
 File "/usr/bin/anaconda", line 959, in ?
anaconda.intf,run(anaconda)
File "/usr/bin/anaconda/text.py", line 455, in run
"%s display is unavailable in tet mode. " 
NameError: name 'oldlang' is not defined"
---------------------------

also, Button Showing SQUARE and text is broken



Comment 17 Bill Nottingham 2006-06-14 16:50:23 UTC
Please open a new bug; this is unrelated to the previous issue.

Comment 18 A S Alam 2006-08-15 07:53:03 UTC
Selected Japanese or Hindi with a US
keymap and Showing message about "<LANG> display is unavailable in text mode.
The Installation will continue in English", but it is next start in
Japanese/Hindi (as showing squares instead of characters).


Envirnemt: 
------------
Rawhide Build 14August2006
--------------

Comment 19 Chris Lumens 2006-08-17 15:28:17 UTC
This should be fixed in the next build of anaconda.

Comment 20 A S Alam 2006-08-22 07:20:38 UTC
Created attachment 134615 [details]
Message box showing that CJKI is not avaiable for stage 2

Message box showing that CJKI is not avaiable for stage 2 (Hindi installation)

Comment 21 A S Alam 2006-08-22 07:24:26 UTC
Created attachment 134616 [details]
Next page after warning

Comment 22 A S Alam 2006-08-22 07:26:58 UTC
it shows warning message, but installation continue in selected langauge 
(tested with following:
---
anaconda-11.1.0.83-1 (21August Build)
Hindi/Japanese
---

Reopening bug

Comment 23 A S Alam 2006-08-29 05:48:02 UTC
Install contine in English in stage 2. Problem fixed.
Tested with following version:
anaconda-11.1.0.84-1.i386.rpm  

Comment 24 Caius Chance 2006-09-11 03:40:53 UTC
According to the .spec file, this bug has been fixed in 10.92.6-1:

-----

It should have been fixed in current RHEL-5 branch and has been contained in the
RHEL5-Server-Beta1-RC.

-----

Please anyone have a test installation on the RHEL5-Beta1-RC.


Note You need to log in before you can comment on or make changes to this bug.