The WebFonts extension includes a Persian font, IranianSans.

Gerrit change 34300

[ Taking this bug, +i18n, +patch-in-gerrit, component set to 'extension setup' ]

Should this be done for the other "fa" projects, too?

This hasn't been discussed in the other projects, as far as I know. We generally don't extrapolate the community decisions of one "fa" project to the other. So the short answer is "no".

Thank you for the clarification.

We'll take in account for future requests Persian projects have independent communities.

Srikanth, can you please check it's all ok and then assign to Niklas if/when ready for next deployment?

please set it's default setting to
$wgWebFontsEnabledByDefault = False;
because it has bug on rendering some of Persian glyph and till now many user disabled it!
i.e.it renders ﭘ like ﻳ also it has problem with other glyphs which has dot
with this change the user how want use it he can activate it himself.

Can somebody from community help reporting the bugs in upstream? Does not look llike a complex bug to fix. Once fixed we can deploy this in Persian Wiki. Disabling by webfonts by default does not help anybody.

It is the font's bug also these fonts are not suitable for Reading Farsi they are useful for printed text.
also it shows . under ت because for font design!
Till there is not free font like tahoma that is suitable for reading please Disable it. here http://fa.wikipedia.org/wiki/%D9%88%DB%8C%DA%A9%DB%8C%E2%80%8C%D9%BE%D8%AF%DB%8C%D8%A7:%D9%82%D9%87%D9%88%D9%87%E2%80%8C%D8%AE%D8%A7%D9%86%D9%87/%D9%81%D9%86%DB%8C
we have many bug reports that they requested to disable this tool!

Reza, I see ﭘ (P, 3 dots) differently from ﻳ (Y, 2 dots).

We'll probably disable WebFonts for now if we cannot fix it quickly, but we want to understand the issue precisely to fix it thoroughly. Can you please say which operating system are you using and which browser version, and maybe also post a screenshot? Thanks!

nzmoihue wrote:

Chrome 25/Windows 8: http://i.imgur.com/kYXWw.png
Firefox 20/Windows 8: http://i.imgur.com/whsJX.png
Opera 12.11/Windows 8: http://i.imgur.com/okLVz.png
IE 10/Windows 8: http://i.imgur.com/mUjSv.png

Compare "چرا" (third word in second line from right). IE 10 is rendering that well but rest of browsers are unable to do it.

I propose disabling extension by default (as reza said) but there are other fonts that we can use with suitable license: http://www.google.com/webfonts/earlyaccess IMO adding Droid Arabic Naskh would be great for both arwiki and fawiki but of-course community must decide about put this font as default. Also Lateef is another font that I think is near to our expectations. Please add them as options in font selecting tool.

Created attachment 11422
webfont-fa screenshot

Attached:

Also I made a testcase in http://fa.wikipedia.org/wiki/%DA%A9%D8%A7%D8%B1%D8%A8%D8%B1:SPhotographer/screenshot

excuse me for other email :)
I made this screenshot in chrome 25/windows 8

Santhosh > the extension has already been deployed, this is how these bugs have been spotted by the Persian Wikipedia community.

Gerrit change 35145 to temporarily disable the extension.

I've reviewed some of the complaints mentioned here. It seems like they are partly due to the Iranian Sans font itself, but also partly related to the browsers used in Windows operating system (especially Windows 8).

I'm marking this bug as LATER, because we need to try alternative fonts, and run more tests in more OS's and browsers before deploying it again. We also need to understand when the bug is not related to the extension or Web Font (but the OS's font rendering limitations), and whether the community is willing to deploy it selectively for certain OS's.

Hey it's said somewhere that RESOLVED LATER is deprecated IIRC.

please only set
$wgWebFontsEnabledByDefault = False;
not totally disable!
https://gerrit.wikimedia.org/r/#/c/35145/1/wmf-config/InitialiseSettings.php
as Huji said we should test other fonts for solving this bug

[ Reopeing bug. ]

RESOLVED LATER is a deprecated keyword we're currently removing from Bugzilla.

Please review http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/65116

(In reply to comment #17)

please only set
$wgWebFontsEnabledByDefault = False;
not totally disable!
https://gerrit.wikimedia.org/r/#/c/35145/1/wmf-config/InitialiseSettings.php
as Huji said we should test other fonts for solving this bug

reza1615 > wouldn't it make more sense to test these other fonts on a testing environment and not in the production wiki?

other fonts (that ebraminio said) http://www.google.com/webfonts/earlyaccess
are works much better
1-our community had consensus so it is much better to respect their opinion but with minor effect!
2-In my opinion if we disable it no one care to solve it's bug :)

I got a discussion on IRC with Mardetanha ([[fa:کاربر:Mardetanha]]). He confirms he would prefer to disable it from fa.wikipedia and have an extension test elsewhere to test and fix issues.

mardetanha.wiki wrote:

Confirmed

Endorsed.

Extension has been disabled for now on fawiki.

(In reply to comment #15)

we need to try alternative fonts, and run more tests in more OS's and browsers

-> setting low priority

nzmoihue wrote:

It is enabled now through ULS and we are using a web font as a fallback font for Persian Wikipedia per the community consensus that applied in another bug. Thanks to your efforts Huji for developing the original web fonts extension for MediaWiki.

(In reply to comment #26)

It is enabled now through ULS and we are using a web font as a fallback font
for Persian Wikipedia per the community consensus that applied in another
bug.
Thanks to your efforts Huji for developing the original web fonts extension
for
MediaWiki.

I am flattered to be mentioned here, but I am not really the person who developed the original WebFonts extension for MW. Most of the work on that extension has been done by Raimond Spekking, Santhosh Thottingal, Siebrand Mazeland, Niklas Laxström and Amir E. Aharoni.