Bug 134198 - indic script being written to console at startup
indic script being written to console at startup
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
: i18n
Depends On:
Blocks: Indic
  Show dependency treegraph
Reported: 2004-09-30 00:48 EDT by Jens Petersen
Modified: 2014-03-16 22:48 EDT (History)
3 users (show)

See Also:
Fixed In Version: 7.86-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-30 09:24:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jens Petersen 2004-09-30 00:48:31 EDT
Description of problem:
When the system locale is set to an Indic one,
the startup messages from initscripts are appearing
translated in the native language, but we don't have
Indic fonts on the console....

Could you please fall back to English messages on the console
for all the Indian and Bangladeshi locale, like we currently
do for CJK.

How reproducible:
every time

Steps to Reproduce:
1. Set system locale to Indic one.
2. (re)boot
3. watch the messages on the console (before rhgb).
Actual results:
Boxes appear instead of Indic script.

Expected results:
English text.
Comment 1 Bill Nottingham 2004-09-30 01:07:33 EDT
What specific locales?

We could just get a better console font that has indic. :)
Comment 2 Jatin Nansi 2004-09-30 01:24:52 EDT
Its going to be really difficult to get the console to display indic.
The font is the least of the problems. The following locales should
have messages in english:


in some places, with some tools, the encoding (.UTF-8) is not set, so
you just get the part before the '.' This broken behaviour is also
bugzillaed, but i would recommend to check for both instances.
Comment 3 Bill Nottingham 2004-09-30 09:24:37 EDT
Fixed in CVS, will be in 7.86-1.

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