User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release) Build ID: 20140506152807 Steps to reproduce: 1. Opened http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-aurora-android-l10n/ 2. Downloaded http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-aurora-android-l10n/fennec-31.0a2.or.android-arm.apk and installed in an Android phone 3. Opened Firefox Aurora and opened websites in tabs Actual results: Odia conjuncts were not displayed because of lack of rendering engine Expected results: Conjuncts should have been displayed correctly

Can you attach a screenshot showing a website? The settings UI you posted is not Gecko rendering that, that's Android.

Tested in Android version 4.2.2 (Samsung Galaxy S DUOS 2). Observation: Found no rendering issue for the same page.

Rendering issues are there only for system/interface messages. Visited Odia Wikipedia (https://or.wikipedia.org) from the same phone. There are no rendering issues.

Do other applications on the device display Odia correctly? It sounds to me like the Gecko rendering is OK, but the Java Android UI code doesn't handle Odia on 4.1. I don't think there's anything we can reasonably do about that; the only "fix" is to update the device to a newer version of Android that supports Odia shaping, as we're dependent on the OS text display for these parts of the interface.

Hi Jonathon, yes all other apps and websites display Odia perfectly. In fact the interface messages of other apps (the ones which have localized versions) display correctly except Firefox Aurora. So, I do not think it is a problem with the OS. I am reopening this thread.

(In reply to psubhashish@gmail.com from comment #5) > Hi Jonathon, yes all other apps and websites display Odia perfectly. In fact > the interface messages of other apps (the ones which have localized > versions) display correctly except Firefox Aurora. So, I do not think it is > a problem with the OS. I am reopening this thread. Hmm, that's interesting. The fact that it renders correctly within web pages but not in the Firefox UI shows that it's a problem with the Java side of the app, and not with Gecko itself. I wonder whether we're using older Java text APIs, or something like that. cc'ing a couple more of the Mobile guys who might know something about that code.

Mass change to move Firefox for Android::Readability bugs to block bug 1129033. Filter on readability-mass-move.

Hi, Is this issue still reproducible? Thank you!

Hi, I rephrase my previous question: does this issue reproduce on Release/Nightly build? Thanks!

Due to the lack of additional info, I'll close this issue as Incomplete. If someone can provide more information regarding this issue, please feel free to reopen it, thanks.