Last modified: 2013-04-22 16:17:11 UTC
Please enable the WebFonts extension on the Burmese Wikipedia (mywiki). There are multiple fonts already in WebFonts for Burmese, and enabling it would be very beneficial because it seems a lot of operating systems lack support for the Burmese characters. See http://my.wikipedia.org/wiki/Wikipedia:%E1%80%9C%E1%80%80%E1%80%BA%E1%80%96%E1%80%80%E1%80%BA%E1%80%9B%E1%80%8A%E1%80%BA%E1%80%86%E1%80%AD%E1%80%AF%E1%80%84%E1%80%BA_%28%E1%80%A1%E1%80%AD%E1%80%AF%E1%80%84%E1%80%BA%E1%80%92%E1%80%AE%E1%80%9A%E1%80%AC%29#Solving_the_font_problem:_WebFonts for the local discussion. Thank you.
We have some concerns about the font rendering and we are trying to sort those out.
(In reply to comment #1) > We have some concerns about the font rendering and we are trying to sort those > out. Masterpiece Uni Sans is AAT based and OSX only. Padauk-Regular is graphite and uniscribe based. It can be used in Pango(linux) and Windows. Myanmar3,Yunghkio are Uniscribe based and can be used in Windows and Linux pango. Font developers sorted out to add both AAT and uniscribe tables on single font and succeeded on Myanmar3 latest version (http://code.google.com/p/myanmar3source/downloads/detail?name=mm3-multi-os%2816-08-2011%29.ttf&can=2&q=) and Tharlon font (http://code.google.com/p/tharlon-font/downloads/detail?name=TharLon.p2.f2.mac.ttf&can=2&q=). I advise you either to add new font or update existing fonts.
Created attachment 10241 [details] Screenshot of text rendered using Masterpiece Uni sans
Created attachment 10242 [details] Screenshot of text rendered using Myanmar3 font
Created attachment 10243 [details] Screenshot of text rendered using Padauk
Created attachment 10244 [details] Screenshot of text rendered using Yunghkio
Hello Maung Maung San, In my Debian(unstable/experimental version) with Pango 1.29, I get the rendering as shown in the screenshots attached to the bug. Looking at the rendering, I can see only Masterpiece Uni sans rendering well. In the Bug comment you said "Masterpiece Uni Sans is AAT based and OSX only.", But when opened the font using fontforge I saw both AAT and Opentype tables.( I hope you meant Opentype tables by Uniscribe tables). AAT is not very important in the context of webfonts. Fonts with opetype tables, wrapped in TTF/OTF/WOFF/EOT formats is enough. Do you agree with my observation that only one font worked properly in Pango? I am yet to check Tharlon font. Page used for testing: https://translatewiki.net/wiki/User:Santhosh.thottingal/Myanmar?setlang=my Note that if your system has locally installed version of any of the fonts , they have priority and fonts from server will not be used.
In the screenshots, padauk is the only working font (with the bug of squeezed eng glyphs). Masterpiece uni sans is only showing glyphs in sequence and not correct. Yes, when i mean the aat and uniscribe, they are method used for adding opentype tables. They work differently in character reordering though. If i were to choose only one font, i will choose tharlon since it can render correctly in multi oses (at least, windows, osx and ubuntu) and have extra script supports for ethnic minority.
(In reply to comment #8) > In the screenshots, padauk is the only working font (with the bug of squeezed > eng glyphs). Masterpiece uni sans is only showing glyphs in sequence and not > correct. Yes, when i mean the aat and uniscribe, they are method used for > adding opentype tables. They work differently in character reordering though. > If i were to choose only one font, i will choose tharlon since it can render > correctly in multi oses (at least, windows, osx and ubuntu) and have extra > script supports for ethnic minority. Thanks, I have added TharLon font now, And recreated all WOFF font formats for other fonts, and now the rendering is different than my screenshots earlier and looks better too. Could you please verify? If it works, and if you think it can be the default font, we can do so. It is also desirable to remove not so important fonts also. https://translatewiki.net/wiki/User:Santhosh.thottingal/Myanmar?setlang=my can be used for testing.
Working pretty well. Confirmed. (In reply to comment #9) > (In reply to comment #8) > > In the screenshots, padauk is the only working font (with the bug of squeezed > > eng glyphs). Masterpiece uni sans is only showing glyphs in sequence and not > > correct. Yes, when i mean the aat and uniscribe, they are method used for > > adding opentype tables. They work differently in character reordering though. > > If i were to choose only one font, i will choose tharlon since it can render > > correctly in multi oses (at least, windows, osx and ubuntu) and have extra > > script supports for ethnic minority. > > Thanks, I have added TharLon font now, And recreated all WOFF font formats for > other fonts, and now the rendering is different than my screenshots earlier and > looks better too. > > Could you please verify? If it works, and if you think it can be the default > font, we can do so. It is also desirable to remove not so important fonts also. > > https://translatewiki.net/wiki/User:Santhosh.thottingal/Myanmar?setlang=my can > be used for testing.
(In reply to comment #10) > Working pretty well. Confirmed. Thanks. Now we need to know what are the fonts need to be provided(I assume not all fonts need to be available in the context of wiki). And which should be the default font?
Tharlon as default and Myanmar3 and Padauk as addon should be enough.
(In reply to comment #12) > Tharlon as default and Myanmar3 and Padauk as addon should be enough. r114249 did that. Changes available in translatewiki.net too.
*** Bug 33716 has been marked as a duplicate of this bug. ***
Can WebFonts be enabled, or are there still issues holding back deployment?
Bump. Is this extension ready for deployment to mywiki?
Note that on my.wiktionary.org they specify @font-face on https://my.wiktionary.org/wiki/MediaWiki:Common.css so therefore I can see the fonts correctly there without WebFonts. We could deploy WebFonts there as well and remove the local css.
(In reply to comment #17) > Note that on my.wiktionary.org they specify @font-face on > https://my.wiktionary.org/wiki/MediaWiki:Common.css so therefore I can see the > fonts correctly there without WebFonts. We could deploy WebFonts there as well > and remove the local css. The local css has been removed <https://my.wiktionary.org/?diff=429363&oldid=344024>. Active users of the wiki have already votes for implementing it on my.wiki so they're surely ok with that.
add [[:my:wikt:]] would be my comment too
Since it seems to be ready for deployment since months, I have submitted the configuration change in https://gerrit.wikimedia.org/r/#/c/20727/ for both the Wikipedia and Wiktionary.
Bug assigned to code submitter.
merged and pushed out to cluster
