Last modified: 2013-12-09 09:40:57 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 2361 - Support dynamic fonts (CSS 3 @font-face, ttf/otf/eot, web fonts, WOFF)
Support dynamic fonts (CSS 3 @font-face, ttf/otf/eot, web fonts, WOFF)
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Language setup (Other open bugs)
unspecified
All All
: Low enhancement with 9 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
http://ta.wikipedia.org
: i18n
: 25220 32063 (view as bug list)
Depends on: 18692
Blocks: 32578
  Show dependency treegraph
 
Reported: 2005-06-09 08:48 UTC by Santhosh Guru
Modified: 2013-12-09 09:40 UTC (History)
19 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Contains the .EOT file and the proposed new monobook.php (49.30 KB, application/octet-stream)
2005-06-09 08:56 UTC, Santhosh Guru
Details
CSS file (623 bytes, text/css)
2005-12-27 04:26 UTC, Santhosh Guru
Details
Dynamic Font File (45.67 KB, application/octet-stream)
2005-12-27 04:29 UTC, Santhosh Guru
Details

Description Santhosh Guru 2005-06-09 08:48:42 UTC
The Tamil wikipedia as such is not dynamic fonts enabled. So if it is viewed in
a computer where the specified fonts are not available, the characters are
unintelligible. So can you enable dynamic fonts for the Tamil Wikipedia.

I have the dynamic font file (.EOT file) , for the Tamil font. I also know the
file (/skins/monobook.php) where to go and do the change for enabling the
dynamic fonts. 

Any developer who is going to take this issue can just send a mail to
santhoshguru@gmail.com , I will send the .EOT file and my recommended changes
that has to be done in the .PHP file.

Thanks,
Santhosh
Comment 1 Santhosh Guru 2005-06-09 08:56:26 UTC
Created attachment 597 [details]
Contains the .EOT file and the proposed new monobook.php

I have attached the dynamic font file (THENEE.EOT), a style sheet
(dynamic-font.css), a PHP file (monobook.php) and a Readme.txt file which has
what to do.

(I was not aware of the create attachment functionality, thats why I has asked
to mail me and get the file from me. But now I have attached all the required
files in the ZIP file)
Comment 2 Brion Vibber 2005-06-09 08:59:14 UTC
Is there any copyright and license information for the font file? It needs to be public domain or 
reasonably GPL-compatible for us to redistribute it.

What's the expected browser compatibility? How would it affect browsers that don't support that 
system?
Comment 3 Santhosh Guru 2005-06-09 09:17:16 UTC
(In reply to comment #0)
> The Tamil wikipedia as such is not dynamic fonts enabled. So if it is viewed in
> a computer where the specified fonts are not available, the characters are
> unintelligible. So can you enable dynamic fonts for the Tamil Wikipedia.
> 
> I have the dynamic font file (.EOT file) , for the Tamil font. I also know the
> file (/skins/monobook.php) where to go and do the change for enabling the
> dynamic fonts. 
> 
> Any developer who is going to take this issue can just send a mail to
> santhoshguru@gmail.com , I will send the .EOT file and my recommended changes
> that has to be done in the .PHP file.
> 
> Thanks,
> Santhosh

(In reply to comment #2)
> Is there any copyright and license information for the font file? It needs to
be public domain or 
> reasonably GPL-compatible for us to redistribute it.
> 
> What's the expected browser compatibility? How would it affect browsers that
don't support that 
> system?
> 

The EOT file is a public domain file. There will not be any copyright issues
regarding that. 
The browsers that wouldnot support the EOT file will not displaying the text as
we see it (without the EOT file in the supported browser).

To put more clearly, if the browser doesnot support the EOT file, the default
font of the browser will be taken. 
Comment 4 Ævar Arnfjörð Bjarmason 2005-12-15 21:25:22 UTC
please supply unified diffs and attachments rather than a ZIP file
Comment 5 Santhosh Guru 2005-12-27 04:24:17 UTC
1. The font definition file: Copy the attached 'thenee.eot' file to the
following location: /skins/monobook/.

2. An add-on stylesheet that calls for this font file and adds the required
declarations to various html element tags. Copy the 'dynamic-font.css' file to
the same location: /skins/monobook/.

In the line number 55 of the file /skins/MonoBook.php, after the following line

<!--[if IE 6]><style type="text/css">@import "<?php $this->text('stylepath')
?>/<?php $this->text('stylename') ?>/IE60Fixes.css";</style><![endif]-->

insert the following code

<!-- Start of the code -->
<?php
#Begin
# Dynamic font style sheet  hack by Kasi Arumugam April 13, 2005 
?>
  <!--[if IE]><style type="text/css">@import "<?php $this->text('stylepath')
?>/<?php $this->text('stylename') ?>/dynamic-font.css";</style><![endif]-->
<?php
#End
?>
<!-- End of the code -->
Comment 6 Santhosh Guru 2005-12-27 04:26:38 UTC
Created attachment 1236 [details]
CSS file
Comment 7 Santhosh Guru 2005-12-27 04:29:45 UTC
Created attachment 1237 [details]
Dynamic Font File
Comment 8 lɛʁi לערי ריינהארט 2005-12-27 10:25:42 UTC
Dear Santhosh!

Thanks for the help at [[ta:project:Font_help]]. Would it be possible to create
a section containing both a screen shot and a sample text to be displayed side
by side?

I think either at a sentence equivalent to "The quick brown fox jumps over the
lazy dog." or another text containing all characters. This will help people to
see if all required characters are display properly or not.

Thanks in advance!

best regards reinhardt [[user:gangleri]]

P.S. Please verify if this request is only related to installations at WikiMedia
foundations projects or if it is necessary / suitable for all MediaWiki
installion using Tamil as content language. Please verify also if this request
is related only to "OS" Windows XP and "Hardware" PC. Please change "Product",
"Component", "OS", "Hardware" if necessary.
Comment 9 lɛʁi לערי ריינהארט 2005-12-27 10:42:43 UTC
P.S. Does this request cover also Tamil sister projects?
See [[wiktionary:ta:Wiktionary:font_help]].
Comment 10 Niklas Laxström 2007-11-30 15:03:09 UTC
Is this something we need? What browsers support dynamic fonts? Is it common that users are unable to edit because of missing font? Is this compatible with Unicode? Are the existing ways documented in that font help page not enough?
Comment 11 Brion Vibber 2009-05-05 00:04:53 UTC
Adding a note that Safari 3.1 and upcoming Firefox 3.5 and Opera 10 support regular TrueType and OpenType fonts with @font-face. If we can generate .eot files as well for IE, doing this for several languages might be helpful.

http://techblog.wikimedia.org/2009/05/firefox-i18n-and-downloadable-fonts/
Comment 12 Amir E. Aharoni 2009-07-16 20:21:40 UTC
This should be available not just on Tamil Wikipedia. I can easily imagine it being useful on every WMF project and MediaWiki in general.

A very generic example: articles about languages and alphabets in every Wikipedia.

A less generic example: Gesenius' Hebrew Grammar on the English Wikisource has passages in Biblical Hebrew on every page and it needs a font which isn't installed on most people's computers. Fortunately, this font, called "Ezra SIL SR", is Free Software, released under the Open Font License, but few people who would be interested in reading this book have the technical knowledge or patience to download and install a new font.

Ideally, font files would be uploaded to Commons, but since they may have very intricate copyright problems, the developers may upload a limited number of Free license-checked fonts to a server which is not too open. I don't imagine that a huge number of font files would be needed anyway and there aren't a lot of Free Software fonts to begin with.
Comment 13 Aryeh Gregor (not reading bugmail, please e-mail directly) 2009-07-16 20:37:53 UTC
There are potentially serious issues with including zillions of web fonts that may or may not be needed.  Some of them are big downloads, and WebKit refuses to lay out text until the font is downloaded.  If a local font has the characters, that would be greatly preferable.

Would font-family: sans-serif, mycustomfont; mean "use mycustomfont, but only if the characters aren't available in the default local font"?  The CSS 3 Fonts spec says it should, but CSS 2.1 seems vague; does it work in practice, and if so, in what browsers?  In particular, do browsers download the font unnecessarily?  Do they support unicode-range (I'm guessing IE doesn't)?

In an ideal world, it *should* be safe to have some custom font-families defined, and do something like this on all wikis:

html { font-family: sans-serif, Wikimedia-custom-font; }
#p-lang { font-family: sans-serif; /* avoid downloading custom fonts just for interlanguage links */ }

I don't know if that would work in the real world without unpleasant side effects.

If we can use unicode-range effectively, then we can just deliver existing free fonts.  If it's not, then we should combine the ones we need into a single file, so that browsers don't have to download a bunch of files in a row to figure out which one has the characters they actually need.

A lot depends on browser implementation here.  If some browser doesn't support falling back on a character-by-character basis, then it will be a lot more painful to support this effectively.  In fact I guess it would be impossible, for that browser, to automatically use web fonts without screwing up people's choice of default fonts for some of the text.  Is anyone willing to test out IE, Firefox 3.5, and the appropriate Safari version to see how they behave?
Comment 14 Brion Vibber 2009-07-17 18:45:45 UTC
Adding also some notes on the wiki: http://www.mediawiki.org/wiki/@font-face_support
Comment 15 Bawolff (Brian Wolff) 2010-09-20 22:17:11 UTC
*** Bug 25220 has been marked as a duplicate of this bug. ***
Comment 16 Derk-Jan Hartman 2010-10-19 15:30:25 UTC
Have we considered introducing a magicword/parserfunction that loads a font like that on the fly, for one page ? With the new resourceloader that might be an option.

Together with our foreign language templates, that could prove rather useful. We'd need:

* a directory of free webfonts
* a way to load a single font
* a way to load a font for an entire wiki.

Possibly use lazyloading of fontfaces, as described by: http://www.stevesouders.com/blog/2009/10/13/font-face-and-performance/
Comment 17 Amir E. Aharoni 2011-02-01 10:25:22 UTC
Adding a comment with the word WOFF, which is the name of a modern related
standard, to make this bug easier to find.
Comment 18 Mark A. Hershberger 2011-03-23 16:52:36 UTC
Think the webfonts extension (under development at http://gitorious.org/webfonts-mediawiki-extension) would handle this.
Comment 19 Gerard Meijssen 2011-04-11 19:00:27 UTC
The WebFonts extension is now in SVN. Yes it will cope with these things. It already copes with Tamil, Oriya, Malayalam, Hebrew..

What is really relevant the base technology will work for any device that supports proper Unicode... That does include many if not most smart phones.

As I have blogged, it works for Hebrew; this is necessary  because many fonts out there are considered inadequate for the proper rendering of the Hebrew language.
Thanks,
     GerardM

http://ultimategerardm.blogspot.com
Comment 20 Quim Gil 2011-04-11 22:01:34 UTC
This extension covers the non-mobile sites, but what about the mobile? Problems with unavailable fonts are remarkable in mobile devices. In some cases the user has no (easy) option to install new fonts, and it looks like these webfonts could be a solution to this problem.

Currently only a few mobile browsers support it, but if we have a precedent (iOS apparently supports it) then it is easier to go to other mobile browser maintainers and file a feature request.
Comment 21 Brion Vibber 2011-04-11 22:17:44 UTC
The current mobile gateway site (en.m.wikipedia.org etc) is external to MediaWiki so won't automatically get extra styles we add in for webfonts, but it could be treated separately (and we should make sure that when it's integrated back into MediaWiki itself that we keep those abilities).

Will probably need to break out a separate bug with mobile-specific issues; for mobile browsers viewing the main MediaWiki sites, standard stuff should kick in where supported.
Comment 22 Platonides 2011-04-12 14:38:02 UTC
CCing Patrick for the mobile.
Comment 23 Quim Gil 2011-04-12 16:15:51 UTC
(In reply to comment #21)
> Will probably need to break out a separate bug with mobile-specific issues; for
> mobile browsers viewing the main MediaWiki sites, standard stuff should kick in
> where supported.

Done: Bug 28515 - Dynamic fonts support in mobile gateway
Comment 24 Subhashish Panigrahi 2011-05-06 06:10:58 UTC
I would be interested for the transliteration or any such thing for Odia Wikipedia (or.wikipedia.org) in this localization context.
Subha Pa (Subhashish Panigrahi)
or.wikipedia.org
Comment 25 Mark A. Hershberger 2011-05-06 23:39:00 UTC
Transliteration extension?  See bug #20246
Comment 26 Santhosh Thottingal 2011-08-31 10:31:49 UTC
http://www.mediawiki.org/wiki/Extension:WebFonts resolved this. Support for Tamil is also already in place.
Comment 27 Sundar 2011-08-31 10:45:19 UTC
(In reply to comment #26)
> http://www.mediawiki.org/wiki/Extension:WebFonts resolved this. Support for
> Tamil is also already in place.
Thanks Santhosh.
Comment 28 Mark A. Hershberger 2011-10-31 17:15:30 UTC
*** Bug 32063 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links