Arabic characters are not displayed properly in desktop tab



Firefox for Android Graveyard
7 years ago
7 years ago


(Reporter: csuciu, Unassigned)





(3 attachments)



7 years ago
Created attachment 563715 [details]
Desktop tab screenshot

Mozilla/5.0 (Android;Linux armv7l;rv:10.0a1)Gecko/20110929 Firefox/10.0a1 Fennec/10.0a1
Device: HTC Desire
OS: Android 2.2.

1. On desktop client (Firefox 6.0.2) go to
2. On device, start nightly, download and instal the arabic language pack, then set up a sync with the desktop client
3. On device, wait till sync ends, open awesome screen and check the desktop tab.

Expected: The link visited at step 1 should be properly displayed - Page title and link

Actual: The arabic characters from the page title are not displayed correctly.

Note: The same page title is properly displayed in the ULR bar and All Pages tab.

Please see the attached screenshots.

Comment 1

7 years ago
Created attachment 563716 [details]
All Pages tab screenshot
Can you test with is Israel -> Hebrew and not Arabic.

Comment 3

7 years ago
Made a mistake when added the first link in bug.
Actually, this is the link that I used: This link also appears in the attached screenshots.
Can the stock browser render the page correctly?

Comment 5

7 years ago
(In reply to Kevin Brosnan [:kbrosnan] from comment #4)
> Can the stock browser render the page correctly?

The page is rendered correctly by the stock browser and by Fennec. The only problem is that the Title of this page is not displayed correctly under Fennec's desktop tab after sync.
CC-ing some folks who might shed a light on this.
This looks like a problem with missing charset metadata - the desktop tab is treating the UTF-8 text in the Arabic titles as if it's an 8-bit encoding (most likely Latin-1).
Created attachment 564579 [details]
screenshot - Romanian

It seems that's the same issue for the Romanian Language pack.

Mozilla/5.0 (Android;Linux armv7l;rv:10.0a1)Gecko/20111004
Firefox/10.0a1 Fennec/10.0a1
Device: Samsung Galaxy S
OS: Android 2.2
You need to log in before you can comment on or make changes to this bug.