The inputs w.r.t Indian languages for Mobile Ok checker redevelopment are as follows:
Image format support : PNG image format needs to be included in the checklist
PNG (Portable Network Graphics) which support binary transparency and alpha channel transparency is being used widely in Mobile Phones. The image support for PNG has increased substantially, as per the statistics of mobile devices in the market. W3C recommended only GIF89a and JPEG support in MWBP 1.0Based on the market production ,PNG has covered majority of the market production.
Page weight : Minimum 40-50KB for Indian languages
Mobile devices are now able to handle larger web pages. The improvements in the underlying network, browser rendering and available memory in devices have led to support of handling larger web pages. So the 20Kb standard needs to be revised. The fact that mobile devices have now have better supports some following problems still exists:-
· It still has only limited types of content support by means of processing and display.
· Mobile data transfer also costs money depending on bandwidth usage.
Based on the size of Indian language content and loading time, it is proposed to update the page weight for Indian languages. The tests should first check the language tag define in the applications. Based on the language tag , it should assign the page weight for Indian languages and then display the error/warning if applicable.
Fonts
Mobile devices often have few fonts and limited support for font sizes and effects (bold, italic, underline etc.) As a result of this, the use of font size, face or effect, for example to highlight an answer or a stressed word, may not achieve the desired effect. Moreover, effects like underline in case of Indian languages actually create more confusion rathe r then add to the effect. So one must check for it and at least provide a warning. For the Default Delivery Context do not use font related styling. As far as possible Web Open Font Format (WOFF) fonts should be used to address these limitations.
The inputs w.r.t Indian languages for Mobile Ok checker redevelopment are as follows:
Image format support : PNG image format needs to be included in the checklist
PNG (Portable Network Graphics) which support binary transparency and alpha channel transparency is being used widely in Mobile Phones. The image support for PNG has increased substantially, as per the statistics of mobile devices in the market. W3C recommended only GIF89a and JPEG support in MWBP 1.0Based on the market production ,PNG has covered majority of the market production.
Page weight : Minimum 40-50KB for Indian languages
Mobile devices are now able to handle larger web pages. The improvements in the underlying network, browser rendering and available memory in devices have led to support of handling larger web pages. So the 20Kb standard needs to be revised. The fact that mobile devices have now have better supports some following problems still exists:-
· It still has only limited types of content support by means of processing and display.
· Mobile data transfer also costs money depending on bandwidth usage.
Based on the size of Indian language content and loading time, it is proposed to update the page weight for Indian languages. The tests should first check the language tag define in the applications. Based on the language tag , it should assign the page weight for Indian languages and then display the error/warning if applicable.
Fonts
Mobile devices often have few fonts and limited support for font sizes and effects (bold, italic, underline etc.) As a result of this, the use of font size, face or effect, for example to highlight an answer or a stressed word, may not achieve the desired effect. Moreover, effects like underline in case of Indian languages actually create more confusion rathe r then add to the effect. So one must check for it and at least provide a warning. For the Default Delivery Context do not use font related styling. As far as possible Web Open Font Format (WOFF) fonts should be used to address these limitations.