Android 5.0 doesn't ship a Oriya supported font

NEW
Unassigned

Status

()

4 years ago
4 years ago

People

(Reporter: aaronmt, Unassigned)

Tracking

(Depends on: 1 bug)

36 Branch
ARM
Android
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

4 years ago
Created attachment 8526151 [details]
screenshot.png

See screenshot

D/GeckoPreferences(15689): onLocaleChanged: or
V/GeckoPreferences(15689): Setting activity title to ଭାଷା
D/GeckoPreferenceFragment(15689): Locale changed: or
D/GeckoLocaleList(15689): Building locales list. Current locale: or
E/GeckoConsole(15689): Locale:Changed: or
(Reporter)

Comment 1

4 years ago
Created attachment 8526153 [details]
screenshot.png
(Reporter)

Updated

4 years ago
See Also: → bug 1075550
Heads up on this, how do we want to treat this?
Blocks: 648548
Flags: needinfo?(jbeatty)
The span of font support on Android devices is so wide, that I don't think we need to treat this immediately. As more devices from more manufacturers update to 5.0, the font support will be where the locale users are currently. 

Let's tag the devices that this currently affects in this bug and monitor the support as more manufacturers update. If the problem becomes more ubiquitous, then we need to address it.

The current set of devices running 5.0 are Google Nexus 6 & 9. Any others I'm missing?
Flags: needinfo?(jbeatty)
(Reporter)

Comment 4

4 years ago
Much more than that (general listing here http://www.androidpit.com/android-5-0-lollipop-phone-update-news)
Are Motorola devices now running separate mods from the Nexus devices? If so, then I still think that only the Nexus devices will be affected. If not, then it's Motorola and Nexus. 

The other manufacturer mods seem to ship with an Oriya font, which is why we haven't logged issues with this before. I'll raise this issue with the Oriya community and sort out the best way we can determine an accurate impact scope before we proceed.
tracking-fennec: ? → +
Depends on: 1075550
The fix we'll probably take for this is Bug 1075550, which we are already tracking, so let's clear the flag for this one.
tracking-fennec: + → ---
See Also: bug 1075550
Shouldn't this bug rather be depending on bug 648548 than blocking it? The possibility to download missing Oriya fonts is already handled in the WIP patches and test server (https://github.com/fred-wang/mozilla-font-server/blob/master/fonts.json#L72).
Flags: needinfo?(kbrosnan)
Actually, neither blocking nor blocks! This is about application font support, not web content.

I'd eventually like for us to address that, but I don't think we'll get that capability when Bug 648548 lands.
No longer blocks: 648548
Flags: needinfo?(kbrosnan)
See Also: → bug 648548
(Reporter)

Updated

4 years ago
See Also: → bug 1075550
You need to log in before you can comment on or make changes to this bug.