Open Bug 723966 Opened 8 years ago Updated 8 years ago

Rendering of Indian language on Web pages is not correct in Fennec, while native (android) browser do properly

Categories

(Core :: Layout: Text and Fonts, defect)

All
Android
defect
Not set

Tracking

()

People

(Reporter: amanpreet.alam, Unassigned)

References

Details

Attachments

(3 files)

while browsing various local Indian websites, Rendering for Firefox Mobile is bad to read, while in-built browser rendering web context good enough. I tested on Samsung Note/Galaxy SII (and other) and SE Neo V. 
http://www.bbc.co.uk/hindi/

http://www.google.co.in/ (select Indic locales to test)

Android Version - 2.3.5 or 2.3.6 (may be outside India Mobile don't have font or language support).

language: Hindi (hi_IN), Punjabi (pa_IN), Gujarati (gu_IN).

Attachment shows Rendering Issue with Orange
Is this a font rendering issue? or is the translation wrong?
Your screenshot was a built-in Firefox page, but you list fomr websites in comment 0, so I assume this is a rendering issue.

Can you make some screenshots of the web content too?
(In reply to Mark Finkle (:mfinkle) from comment #1)
> Is this a font rendering issue? or is the translation wrong?

it is Rendering Issue.
This is a known issue - there's no Indic support yet in the harfbuzz shaping engine we're using (see bug 619524), so no Indic languages will display properly.

(I believe most devices outside the Indian market - and even some within it - don't have any such support in the native browser either, but recently some manufacturers have started to provide it in their builds.)
Component: General → Layout: Text
Product: Fennec Native → Core
QA Contact: general → layout.fonts-and-text
Version: Firefox 11 → Trunk
Depends on: 758236
#758236 fixed (Last Resolved: 2012-06-02 11:46:27). Waiting for 15 build to test.
with Firefox 15.0a1 (2012-05-12), Rendering for Punjabi and Hindi (only tested) is quite good. All text is readable
Attached image Hindi Screenshot
Hindi Screenshot
Depends on: 780409
You need to log in before you can comment on or make changes to this bug.