Closed
Bug 1067601
Opened 10 years ago
Closed 6 years ago
[Intex Cloud Fx][ZTE OPEN C] [1.3 ]Malayalam text in sites do not render properly
Categories
(Firefox OS Graveyard :: Gaia::Browser, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: guigs, Unassigned)
References
Details
(Whiteboard: [SUMO-b2g])
Attachments
(3 files)
https://support.mozilla.org/en-US/questions/1019279 On 1.3 tested: deepika.com does not render in some parts of the page http://malayalam.webdunia.com/ does render. Attachment of deepika.com
Reporter | ||
Updated•10 years ago
|
Summary: [Intex Cloud Fx] [1.3 ]Malaysian text in sites do not render properly → [Intex Cloud Fx][ZTE OPEN C] [1.3 ]Malaysian text in sites do not render properly
Reporter | ||
Updated•10 years ago
|
Reporter | ||
Updated•10 years ago
|
Summary: [Intex Cloud Fx][ZTE OPEN C] [1.3 ]Malaysian text in sites do not render properly → [Intex Cloud Fx][ZTE OPEN C] [1.3 ]Malayam text in sites do not render properly
Comment 1•10 years ago
|
||
It seems that there is no Malayalam font available in B2G Repository.(1) 1. https://github.com/mozilla-b2g/moztt
Comment 2•10 years ago
|
||
So adding fonts for Malayalam will fix the issue. I recommend adding font made by Noto. Need to be mentioned that, Noto made fonts for Malayalam(1) and the font is under Apache License, version 2.0. So proposing to add "Noto Sans Malayalam (Malayalam)" into Mozilla B2G. 1. http://www.google.com/fonts/earlyaccess
Reporter | ||
Updated•10 years ago
|
Summary: [Intex Cloud Fx][ZTE OPEN C] [1.3 ]Malayam text in sites do not render properly → [Intex Cloud Fx][ZTE OPEN C] [1.3 ]Malayalam text in sites do not render properly
Comment 3•10 years ago
|
||
Adding Patch into B2G adding Malayalam fonts.
Attachment #8490971 -
Flags: review?(jfkthame)
Comment 4•10 years ago
|
||
(In reply to rmcguigan from comment #0) > Created attachment 8489641 [details] > 2014-09-15-14-19-14.png > > https://support.mozilla.org/en-US/questions/1019279 > > On 1.3 tested: > deepika.com does not render in some parts of the page > http://malayalam.webdunia.com/ does render. > > Attachment of deepika.com deepika.com does not use Unicode for its Malayalam text; it's using a "hacked ASCII (or Latin-1)" encoding that must be dependent on a particular custom font. So adding any Unicode-compliant font will not help here. http://malayalam.webdunia.com/ looks like it is using Unicode correctly, so in this case yes, the problem is the lack of a Malayalam font on the device. (In reply to Safwan Rahman from comment #1) > It seems that there is no Malayalam font available in B2G Repository.(1) > 1. https://github.com/mozilla-b2g/moztt Not true: we currently have the Meera font for Malayalam; see https://github.com/mozilla-b2g/moztt/tree/master/Meera-06 and https://github.com/mozilla-b2g/moztt/blob/master/fonts.mk#L108. (In 1.3, we had Lohit Malayalam; see https://github.com/mozilla-b2g/moztt/blob/v1.3/fonts.mk. The change to Meera was requested by the community; see bug 1022322.) So the problem reported here must be caused by the vendor of the particular device(s) deciding to exclude the Malayalam font from their build, even though it was present in the master moztt repository. That's out of our hands, unfortunately, and will not be solved by simply adding more fonts to moztt.
Comment 5•10 years ago
|
||
delphine, can you comment on malayalam is a supported locale for 1.3?
Flags: needinfo?(lebedel.delphine)
Comment 6•10 years ago
|
||
:Bajaj, according to comment 4, Malayalam is supported in B2G. I can see Malayalam text clearly in my Keon 1.3. As kew said, the vendor excluded the malayalam font
Comment 7•10 years ago
|
||
As per https://github.com/mozilla-b2g/gaia/blob/v1.3/locales/languages_all.json I confirm Malayalam is supported as a 1.3 locale
Flags: needinfo?(lebedel.delphine)
Comment 8•10 years ago
|
||
(In reply to Safwan Rahman from comment #6) > :Bajaj, according to comment 4, Malayalam is supported in B2G. I can see > Malayalam text clearly in my Keon 1.3. As kew said, the vendor excluded the > malayalam font Alright, following up with vance who is the ZTE TAM to see why did partner exclude this font? Vance, this seems to be on Intex devices as well, (chk : https://support.mozilla.org/en-US/questions/1019279) so can we follow up with SPRD as well ?
Flags: needinfo?(vchen)
Comment 9•10 years ago
|
||
Wanted to add that as per Bug 1022322, Malayalam community decided to use Meera font in 2.1. Adding Anivar so he can possibly comment on this and give his input if needed
Updated•10 years ago
|
Flags: needinfo?(anivar.aravind)
Comment 10•10 years ago
|
||
Can someone provide screenshots of any unicode website such as ml.wikipedia.org from the specified device ? As per the initial comment ASCII website deepika is not working . It is not a bug because ASCII will not be supported with unicode font . It is an expected behaviour The initial comment also says Unicode website http://malayalam.webdunia.com/ does render. That means device have a malayalam font. Where is the proof for font missing ? Can someone provide screenshots? Moztt have Meera font as explained by jfkthame How we reached at a conclusion that font is missing on device ?
Flags: needinfo?(anivar.aravind)
Comment 11•10 years ago
|
||
Aniver, The user in Mentioned question could not see Malayalam text on his Intex. Can you please check with Intex? # https://support.mozilla.org/en-US/questions/1019279
Comment 12•10 years ago
|
||
Safwan, Thank you for the link . From the link it looks like font is removed by intex. OEM's removing most of Indian language fonts and locales was a common phenominon observed with many low cost device manufactures for android devices until few months back. They may be following same pattern for firefox as well. With google's push on Androidone this scenario is changing and all their devices coming with 17 Indian language support now . I feel a similar push from mozilla is needed to make sure that all 13 indian language locales and fonts currently present will be included with OEM providers like intex
Comment 13•10 years ago
|
||
Anivar, Thanks for your reply. It seems that in our build for low end Device like Tarako (Firefox OS 1.3T), there is Malayalam font is included(1). So its not fault from our end. I am sure that its issue about Intex. They removed the font while building. So we need to work together with them to resolve this issue. :bajaj, can you please talk with the Intex regarding this issue? 1. https://github.com/mozilla-b2g/moztt/tree/v1.3t/Lohit
Comment 14•10 years ago
|
||
It will be good to check on the availability of other indian language fonts on device as well . If Malayalam is missing, i am sure many more will be missing
Comment 15•10 years ago
|
||
Vance, it would also help to just adb shell ls /system/fonts on the actual device. Hoping you have access to one with adb debugging on.
Updated•10 years ago
|
Whiteboard: [SUMO-b2g]
Comment 16•10 years ago
|
||
While try to View Malayalam, the user see boxes instead of writing. It means that the font is missing from the Device.
Comment 17•10 years ago
|
||
Safwan, if you have access to an Intex device, could you provide a list of the font files that are installed, by running adb shell ls -l /system/fonts I'd like to see what other "customizations" they may have done here.
Flags: needinfo?(safwan.rahman15)
Comment 18•10 years ago
|
||
Jonathan, Sorry, I have not access to an Intex Device :(. I tried my best to get any person having it who would like to do the test, but, still I have not get any. The person who raise the problem in support forum, I have contacted with him personally. And he sent me this screenshot. I am trying my best to get any person having the device who can test this. I think QA team should have the device, therefore I have marked as "QAwanted", so still waiting for it.
Flags: needinfo?(safwan.rahman15)
Comment 19•10 years ago
|
||
As far as I know that the Intex Handset was built by spreadtrum chip. So I think, the Firefox OS build for Intex was also maid by spreadtrum. I think officials of Spreadtrum can say better if they have exclude the font. I am NI a official of Spreadtrum to see if he know any about it. Need to be mentioned that, in our B2G build for Tarako, we have the mentioned font. 1. 1. https://github.com/mozilla-b2g/moztt/tree/v1.3t/Lohit
Flags: needinfo?(james.zhang)
Comment 20•10 years ago
|
||
FirefoxOS v1.3 don't support Malayalam, and I think Index phone only support English/Hindi/Tamil/Bengali language and font.
Flags: needinfo?(james.zhang)
ni Marvin as well. Hi Marvin, could you confirm is Malayalam(മലയാളം) one of the supported language in Intex Cloud FX when we discussed the product requirement with Intex/SPRD?
Flags: needinfo?(vchen) → needinfo?(mkhoo)
Comment 22•10 years ago
|
||
no, we did not claim Malayalam is supported for 1.3T. BR, Marvin
Flags: needinfo?(mkhoo)
Comment 23•10 years ago
|
||
marvin, Malayalam font should be supported because the font is in 1.3T Repository. Can you please check?
Flags: needinfo?(mkhoo)
Comment 24•10 years ago
|
||
Hi Safwan, First of all, as mentioned, we do not claim Malayalam is support in 1.3T, and we do not roll out this for 1.3T as customer did not request it. for this bug, i suggest team to follow up the fixes, once Malayalam front is ensure "ready", we can consider this locale for upcoming product. BR, Marvin
Flags: needinfo?(mkhoo)
Comment 25•10 years ago
|
||
Hi Marvin, Malayalam is supported in 1.3T.(1) check the Moztt repository of 1.3T. As its already fixed, I think it should be also in the Handset of Intex! So, the question is, its available in 1.3T but why not available in the handset of Intex? 1. https://github.com/mozilla-b2g/moztt/blob/v1.3t/fonts.mk
Flags: needinfo?(mkhoo)
Comment 26•10 years ago
|
||
The issue we're running into is the difference between * localizations support on UI * localizations support in keyboards/input methods * ability to display content on the web in different languages. In particular in India, I think it's an unfortunate decision to cut down the viewable content to the small list of languages for which we thought we could lift product and IME localizations.
Comment 27•10 years ago
|
||
"We do not roll out this for 1.3T as customer did not request it". moreover, when you said is available, are you the owner to ensure "available" means "ready to ship"? thanks!
Flags: needinfo?(mkhoo)
Comment 28•10 years ago
|
||
dupe of bug 1077803 ?
Comment 29•10 years ago
|
||
Please elaborate on what is it that you would like qawanted to test. (qawanted tag was added on comment 14.5) Note that we (QAwanted team in QAnalysts) currently only support testing on Flame 2.0 to Flame 2.2 central.
Flags: needinfo?(safwan.rahman15)
Comment 30•10 years ago
|
||
Pi wei, I wanted to QA in Intex. As it seems to be affected, I think qawanted tag should be removed.
Flags: needinfo?(safwan.rahman15)
Keywords: qawanted
Comment 31•10 years ago
|
||
Comment on attachment 8490971 [details] [review] Patch to add Malayalam Script Font support on B2G Removing r? flag here, as the issue isn't with the collection of fonts we have present in moztt, but rather with device vendors deciding to exclude some of the fonts from their build. We can't fix this in moztt, it can only be fixed by the vendor. An alternative (or additional) fix would be to provide "font packages" that can be added by on demand, to supplement what the vendor chose to ship. See bug 648548 for the comparable issue on Android; we could consider something like that for FxOS if this is a major problem, but it would require standing up the infrastructure to run a "font package server". Another option might be font packages that users can manually install from the Marketplace to enhance their device in order to support additional languages. I'm not sure how much work would be needed to make this possible -- I assume a standard FxOS app can't just add fonts to a system directory for all apps to use, so some kind of special mechanism or permission would be needed.
Attachment #8490971 -
Flags: review?(jfkthame)
Comment 32•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•