Bug 139531 (FIREFOX_PANGO)

Patches are in the tree.  Waiting on beehive at this point.

-> in the tree now.

After the pango has been disabled, it cause some indic characters not
able to be display properly. Enabled pango manually works.

At the moment, with no pango enabled, pa_IN  looks like this.
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=108182&action=view

Created attachment 108186 [details]
proposed patch to enable Pango for Indic locales only

firefox-1.0-10.EL4, waiting on beehive.

Oh, and thunderbird-1.0-0.2.rc1 too

Had to quick look, at the moment in firefox-1.0-12.EL4, I can view
hi_IN and pa_IN with no difficulties. However, for bn_IN, gu_IN and
ta_IN, I cant see the pages properly.

Chris,
Could you please have a quick look?

bn_IN
http://www.banglalive.com
gu_IN
http://www.sambhaav.com
hi_IN
http://www.bbc.co.uk/hindi
pa_IN
http://guca.sourceforge.net/pa
ta_IN
http://vikatan.com

bn_IN
http://www.banglalive.com

This page has a problem with the web site itself:

http-equiv="Content-Type" content="text/html; charset=iso-8859-1"

It's _not_ iso-8859-1.  I can't figure out what the actual encoding
is, but I know this is wrong.

gu_IN
http://www.sambhaav.com

Same problem:

META http-equiv=Content-Type content="text/html; charset=x-user-defined"

I've never seen this on a real live web site before.  What's the real
charset?  What font does it expect you to have?  Probably this one:

style="font-family: shree750; font-size: 14pt; color: #0000FF"

hi_IN
http://www.bbc.co.uk/hindi

This appears to render just fine (one of my test pages, actually)
(UTF-8 encoding)

pa_IN
http://guca.sourceforge.net/pa

This appears to render fine here.  (UTF-8 encoding)

ta_IN
http://vikatan.com

ISO-8859-1 encoding.  I think that's a lie, once again.  Do you know
the encoding so I can force it?

The three that don't work for me are all mis-configured.  Probably
assuming some configuration that local users use.

the bn, ta, and gu websites listed above do not use unicode. they
actually use acsii, with special fonts which have the glyphs from
their corresonding languages mapped to ascii / english characters.
This works well on windows, when you have the font installed. It
breaks completely on linux.

Try these sites:
gu_IN:  http://www.utkarsh.org/html/gujarati/index_guj.htm

bn_IN:  http://www.bengalinux.org/bn/index.php

ta_IN:  http://www.zhakanini.org (the site seems to be down rite now)

We would need to build custom decoders for those fonts.  I don't know
where to find that information.

there are very many such fonts & sites with custom encodings. I really
dont think us building custom decoders for the fonts is a good idea.
we need to encourage the sites to move to unicode.

Moving to RHEL4 U1 varies trackers. Chris, let me know if the
assignment needs be swapped.

Ping?

Current Status:
RHEL-4 pango is enabled by default only in indic languages.
MOZ_ENABLE_PANGO can be used to enable it in other languages.

FC3 and FC4 pango is enabled by default in all languages.
MOZ_DISABLE_PANGO can be used to disable.

I suppose this bug is staying open until pango is enabled in all languages and
all distributions?  In that case this should be a tracker bug for all pango
firefox issues.  If not it should be closed now.

Good question - I think this should be tried as a RHEL4 pango tracker.

There are still bugs, I would not try to put this into U2 at this time.  Needs
more shaking out in Fedora.

*** Bug 167159 has been marked as a duplicate of this bug. ***

Making this the Firefox Pango tracker, with all Firefox Pango related bugs as
'blocking' this report.  This does not mean that all of these bugs need to be
fixed before Firefox Pango is enabled in RHEL, however most of the important
ones should be.

- Pango now works with Arabic and Hebrew.
- Pango is absolutely necessary for Indic languages.
- Pango is *NICE* for Japanese and possibly other CJK languages in allowing bold
text where previously bold was not possible with Xft.

User blizzard's account has been closed

Since this bugzilla report was filed, we have seriously upgraded Gecko-related
packages, which may have resolved this issue. Users who have experienced this
problem are encouraged to upgrade their system to the latest version of their
distribution available.

Please, confirm to us that this bug is reproducible on the latest upgrade of the
supported distribution (that's RHEL, or Fedora 7, 8, and Rawhide).

Setting the bug to NEEDINFO. If I won't get confirmation of reproducability in
30 days, the bug will be closed as INSUFFICIENT_DATA.

[This is mass-changing of bugs which seem to be too old and irrelevant anymore;
we are sorry, if this bug should not be incldued.]

Petersen what is the status of this?

No change in under Firefox 2

It looks like this is not going to get fixed until we move to Firefox 3,
which I don't know will happen for RHEL 4?

We're moving to Firefox now (for RHEL-4.7). Can it be closed then?

Is pango enabled by default for all languages in Firefox 3?

(In reply to comment #34)
> We're moving to Firefox now (for RHEL-4.7). Can it be closed then?

Yes, I think it can be closed then.

(In reply to comment #35)
> Is pango enabled by default for all languages in Firefox 3?

It should be.

*** Bug 483520 has been marked as a duplicate of this bug. ***

I tested firefox with following version on RHEL4 and with en_US locale,
Rendering for language is Good:
firefox-3.0.10-1.el4

Verify

it is part of following release:
Red Hat Enterprise Linux AS release 4 (Nahant Update 8)