Bug 120131 - Please include Bangla/Bengali during the installation process
Summary: Please include Bangla/Bengali during the installation process
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
(Show other bugs)
Version: rawhide
Hardware: All Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2004-04-06 10:21 UTC by Jamil Ahmed
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-21 12:36:07 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jamil Ahmed 2004-04-06 10:21:56 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 
7.23  [en]

Description of problem:
The translation of the essential packages for the Bangla/Bengali 
language, at the time of this writing, is more then 90%, thus it 
should be included and supported during the installation process of 
Fedora Core 2.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. start anaconda installer

Actual Results:  Bangla/Bengali is not present in the list of 

Expected Results:  Bangla/Bengali should be among the installation 

Additional info:

Comment 1 Jeremy Katz 2004-04-06 18:48:41 UTC
I need the following information:
1) Confirmation that we ship a working font to display the language in
X.  If it's a language with all new glyphs (which I believe Bengali is),
then I need to know what package the font comes from and which font to
use so that it will actually display in the installer
2) The following information for the lang-table
  * console keyboard map to use
  * default time zone (eg, America/New York)
  * console font to use
  * default locale
  * keyboard mapping to use in X

Comment 2 Jamil Ahmed 2004-04-08 06:19:54 UTC
1) Bengali fonts are suppose to included in FC by Owen Taylor 
<otaylor redhat com>. See the urls below,


The fonts should be in the stage2.img fs in the installer cd.
MuktiNarrow font looks ugly when you enable hinting.
This can be avoided by inserting the following lines in, 

        <match target="font">
                <test name="family">
                        <string>Mukti Narrow</string>
                <edit name="hinting">

2)Here is the information for the lang-table

Full language name...: Bangla/Bengali (Bangladesh)
Short name...........: bn
Default Locale.......: bn_BD.UTF-8
Default keyboard map.: en
Console font.........: default
Timezone.............: GMT+6  Asia/Dhaka

Full language name...: Bangla/Bengali (India)
Short name...........: bn
Default Locale.......: bn_IN.UTF-8
Default keyboard map.: en
Console font.........: default
Timezone.............: GMT+530  Asia/Calcutta

Comment 3 Sayamindu Dasgupta 2004-04-08 06:57:52 UTC
Some comments (sorry for the spam):

1. The keyboard layout should be en (or is it US?) in all cases (since
you can't have passwd and stuff like that in Bangla yet
2. The default console font should be whatever that used for English
install - since no console font has Bengali glyphs. I think the font
in that case would be latarcyrheb-sun16
3. Bengali is written in the Bengali script as বাà¦à¦²à¦¾ 

Comment 4 Sayamindu Dasgupta 2004-04-08 18:59:26 UTC
By the way, the SRPM for the bengali font is at

Apparently, the FreeType autohinter cannot handle Indic fonts
correctly.  Freetype with bytecode interpreter enabled works fine. I
don't suppose Fedora will be enabling that - so the best solution will
be disable autohinting for the MuktiNarrow font by adding the lines as
suggested by Jamil in comment #2.

Comment 5 Jeremy Katz 2004-04-14 20:57:30 UTC
Added to lang-table and pull in fonts. 
http://people.redhat.com/~katzj/anaconda/anaconda-bengali.png is
running in test mode

As far as the auto-hinting change, this would need to be done on a
global basis for the distro, so filing against fontconfig to get that
done would be the best approach.

Comment 6 Jamil Ahmed 2004-04-15 04:58:17 UTC
I am getting "Page Not Found 404" @



Comment 7 Sayamindu Dasgupta 2004-04-15 07:28:40 UTC
Bug filed against fontconfig (bug #120915). Thanks for all the help :-)

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