896809 - Thai font not displaying on Galaxy S IV 4

Status: RESOLVED WORKSFORME

(Firefox for Android Graveyard :: General, defect)

Description

[Kevin Brosnan [Ex-Mozilla]]

Attachment: 2013-07-21-05-31-06-18de68.png

User from the forums reports that Thai text does not show up when using Firefox for Android. Other browsers display Thai text without issue.

Setting needinfo as a reminder to look into this.

Comment 1

[Aaron Train [:aaronmt]]

Attachment: Galaxy S4 (Google Edition, 4.3) - Screenshot (WFM)

Works for me, note I'm running GE 4.3 on my S4.

Found this for those on TouchWiz:

http://cellphoneforums.net/google-android/t362305-galaxy-s4-doesn%3Bt-display-thai-language.html#axzz2ZpZRQv1R

http://www.sammobile.com/forum/showthread.php?t=12055

Comment 2

[Aaron Train [:aaronmt]]

Is Thai available in TouchWiz? MV should have S4's now.

Comment 3

[Kevin Brosnan [Ex-Mozilla]]

I can't reproduce this. Though it may be a specific model that is not the international phone we have.

Comment 4

[Oleksiy Rashevsky]

I have exactly the same issue across all applications on Galaxy S4 (Android version 4.2.2, Baseband version I9505ZHUBMF4) The Thai characters are missing in the system fonts which is affecting all applications on the phone.

Comment 5

[Aaron Train [:aaronmt]]

Resolution appropriate is invalid as this is something that the vendor would need to address for the phone itself.

Comment 6

[Andrew Williamson [:eviljeff]]

Before I log a different bug, can I clarify some things about what I'm experiencing v.s. what would be a vendor issue.
* only Firefox is missing Thai letters -  the built in browser and facebook app (among others) show them.
* the device itself supports Thai language both in UX and keyboard.  I.e. I can type in Thai on the keyboard in Firefox which then come out as squares.

Note: I'm moco and acquired the device via servicenow last week - its the standard international model.

Comment 7

[Kevin Brosnan [Ex-Mozilla]]

Andrew a new bug would be best. The issue here was reported against a different phone model.

Comment 8

[[:philipp]]

this came up in the forum again: https://support.mozilla.org/en-US/questions/976190

Comment 9

[Kevin Brosnan]

Tracking as we are looking at these markets.

Comment 10

[Andrew Williamson [:eviljeff]]

(In reply to Kevin Brosnan [:kbrosnan] from comment #7)
> Andrew a new bug would be best. The issue here was reported against a
> different phone model.

bug 934962

Comment 11

[Andrew Williamson [:eviljeff]]

fwiw, this bug went away when I did a system update to 4.3

Comment 12

[Mark Finkle (:mfinkle) (use needinfo?)]

John - Do you have any phone that might have this issue? Or can you ask around to find such a phone.

Comment 13

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

(In reply to Mark Finkle (:mfinkle) from comment #12)
> John - Do you have any phone that might have this issue? Or can you ask
> around to find such a phone.

I (and RelEng) do not, but ATeam or L10N would be my next guess.

Comment 14

[Jonathan Griffin (:jgriffin)]

I don't know of any in the A-team, Tony's team might have one.

Comment 15

[Zac C (:zac)]

I'm a Firefox OS guy, I definitely don't have one :)

Comment 16

[Axel Hecht [:Pike]]

Stas might be able to test, but I'm not sure if he'll be able to do extensive tests - it's not his phone.

CCing arky.

Johnathan, is there something on your mind that would be worth testing or gathering as data if we got a phone that reproduced the behavior in https://support.mozilla.org/en-US/questions/976190 ?

Comment 17

[Tony Chung [:tchung]]

(In reply to Jonathan Griffin (:jgriffin) from comment #14)
> I don't know of any in the A-team, Tony's team might have one.

The S4 that QA has is what Kevin couldn't reproduce in comment 3, because its not the international model.

Comment 18

[Aaron Train [:aaronmt]]

Also the Google Play Editions on stock Android 4.2 which have now upgraded to 4.3, the version I have, does not have this issue whatsoever.

Comment 19

[Jonathan Kew [:jfkthame]]

The behavior in the screenshot (attachment 779522 [details]) is what I'd expect to see if there's no font with Thai characters available on the device.

However, comments 0 and 4 indicate that other applications on the device -do- show Thai, which suggests that there -is- at least one font with Thai characters. So perhaps there's something about that font that prevents Firefox using it?

:eviljeff, if you could pull the complete contents of the /system/fonts directory of your device and attach as a zip file, I'd be interested to see exactly what's there.

Comment 20

[Andrew Williamson [:eviljeff]]

ADB wasn't being co-operative so I used a file manager app on the phone and uploaded them to google drive:
https://drive.google.com/#folders/0BxAobiprZ9buSkhEeDNfanZRN3c - you can download them from there as a zip file if you want them all.

Note this is after the 4.3 update fixed the issue so it may have been more useful before.

Comment 21

[Jonathan Kew [:jfkthame]]

(Ugh - I see they're shipping a non-Unicode-compliant font for Myanmar. That's sad.)

Regarding the Thai issue, though, I'd really need to see the font collection -prior- to the update in order to try and diagnose why we were failing. Is it possible to temporarily revert your phone to 4.2 in order to reproduce this? Anyone else around with such a device?

Comment 22

[Ryuu]

Follow from:
https://support.mozilla.org/en-US/questions/976190

This comes from 4.2.2 with adb pull
http://www.mediafire.com/download/uiwc894n15ud3cm/4.2.2_system_fonts.rar
Hope this help.

Comment 23

[Kevin Brosnan [Ex-Mozilla]]

Put the files from comment 22 on http://people.mozilla.org/~kbrosnan/tmp/896809/

Comment 24

[Jonathan Kew [:jfkthame]]

(In reply to Kevin Brosnan [:kbrosnan] from comment #23)
> Put the files from comment 22 on
> http://people.mozilla.org/~kbrosnan/tmp/896809/

The file there isn't accessible (presumably a permission issue), but I downloaded it from the location in comment 22.

In the 4.2.2 archive, there's a font "GS_Thai_111220.ttf" that includes Thai characters; in the 4.3 collection (comment 20) this has been replaced by "SamsungThai.ttf". So apparently Firefox is failing to use the older GS_Thai_111220 for some reason, but I haven't yet pinpointed the reason.

Leaving needinfo? on myself for now as a reminder to look further.

Comment 25

[Mark Finkle (:mfinkle) (use needinfo?)]

Gentle ping...

Comment 26

[Jonathan Kew [:jfkthame]]

I don't have the specific device in question for testing, but I have a Nexus 10 running Android 4.2. So to try and investigate, I hacked my Fennec build to ignore the DroidSansThai.ttf font that's present on my device, and confirmed that I get .notdef squares for Thai text.

Then I added the GS_Thai_111220.ttf font from the 4.2.2 archive (comment #22), figuring that I could try to debug why it doesn't work in Gecko... but... surprise, it works just fine. Thai renders without problems.

So I don't know why it apparently wasn't working for people with the Galaxy device. Maybe if I had an actual device in hand that exhibits the problem, it'd be possible to investigate more, but otherwise I don't think there's much I can do.

Given that the issue is apparently fixed by a system update, it's not clear to me whether it's really worth spending more time on this, or trying to get a problem device over here for debugging? Or can we assume that most users are likely to get the system update anyhow, so they won't run into the issue?

Comment 27

[Aaron Train [:aaronmt]]

System update 4.4 is already in the works for the S4, so that's another update, so I would imagine that this is wontfix.

Comment 28

[Staś Małolepszy :stas]

(In reply to Axel Hecht [:Pike] from comment #16)
> Stas might be able to test, but I'm not sure if he'll be able to do
> extensive tests - it's not his phone.

I tested on my mom's GT-I9505, 4.2.2, JDQ39.I9505XXUBMF4 and I couldn't reproduce.  I tested on th.wikipedia.org and google.com/?hl=th and both showed Thai fonts.

Comment 29

[arky [:arky]]

(In reply to Staś Małolepszy :stas from comment #28)
> (In reply to Axel Hecht [:Pike] from comment #16)
> > Stas might be able to test, but I'm not sure if he'll be able to do
> > extensive tests - it's not his phone.
> 
> I tested on my mom's GT-I9505, 4.2.2, JDQ39.I9505XXUBMF4 and I couldn't
> reproduce.  I tested on th.wikipedia.org and google.com/?hl=th and both
> showed Thai fonts.

Thai Wikipedia uses web fonts?

@font-face {
  font-family: "Autonym";
  font-style: normal;
  src: local("Autonym"), url("https://bits.wikimedia.org/static-current/extensions/UniversalLanguageSelector/data/fontrepo/fonts/Autonym/Autonym.woff?version=20131112") format("woff"), url("https://bits.wikimedia.org/static-current/extensions/UniversalLanguageSelector/data/fontrepo/fonts/Autonym/Autonym.ttf?version=20131112") format("truetype");
}

Comment 30

[Jonathan Kew [:jfkthame]]

(In reply to arky [:arky] from comment #29)
> (In reply to Staś Małolepszy :stas from comment #28)
> > (In reply to Axel Hecht [:Pike] from comment #16)
> > > Stas might be able to test, but I'm not sure if he'll be able to do
> > > extensive tests - it's not his phone.
> > 
> > I tested on my mom's GT-I9505, 4.2.2, JDQ39.I9505XXUBMF4 and I couldn't
> > reproduce.  I tested on th.wikipedia.org and google.com/?hl=th and both
> > showed Thai fonts.
> 
> Thai Wikipedia uses web fonts?
> 
> @font-face {
>   font-family: "Autonym";
>   font-style: normal;
>   src: local("Autonym"),
> url("https://bits.wikimedia.org/static-current/extensions/
> UniversalLanguageSelector/data/fontrepo/fonts/Autonym/Autonym.
> woff?version=20131112") format("woff"),
> url("https://bits.wikimedia.org/static-current/extensions/
> UniversalLanguageSelector/data/fontrepo/fonts/Autonym/Autonym.
> ttf?version=20131112") format("truetype");
> }

The "Autonym" webfont is just there for the list of language names; it's a subsetted, multi-script font that supports only the characters needed for the actual language names, not full coverage for the various scripts. So it isn't used for the article text, etc.

Comment 31

[Mark Finkle (:mfinkle) (use needinfo?)]

Marking WFM. Re-open if this appears to still be a big issue.

Comment 32

[Andrew Williamson [:eviljeff]]

fwiw, does http://www.thai2english.com/dictionary/hello.html work for you also?