Last modified: 2012-02-22 12:35:16 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 1281 - IE6 requires obscene workarounds for expanded fontsets.
IE6 requires obscene workarounds for expanded fontsets.
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
PC Windows 2000
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: testme
Depends on:
Blocks: css 640
  Show dependency treegraph
Reported: 2005-01-07 21:56 UTC by grendelkhan
Modified: 2012-02-22 12:35 UTC (History)
5 users (show)

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


Description grendelkhan 2005-01-07 21:56:37 UTC
The discussion on [[en:Talk:Greek language]] centers around requiring custom
font loading for the display of polytonic Greek or IPA. The custom FONT tags are
being replaced by a template ([[en:Template:IPA]]) that includes a SPAN tag with
a list of fonts. This is still really, really ugly to do, but otherwise the
fonts won't display without IE users manually selecting Arial Unicode MS for
their display font.

Would it be possible to specify a preference for more Unicode-friendly fonts
than the default in IE, in the default CSS?

This is, I realize, modifying the stylesheet to fix problems with IE. But the
setup is already full of workarounds for problems with IE, isn't it?
Comment 1 Brion Vibber 2005-01-29 07:51:49 UTC
Sorry, but this report is pretty vague.

Can you give an example of the actual style code you might want?
Comment 2 grendelkhan 2005-03-18 20:46:36 UTC
Whoops, didn't notice the reply.

[[en:Template:IPA fonts]] lists: Code2000, Gentium, Gentium Alternative, TITUS
Cyberbit Basic, Arial Unicode MS, Lucida Sans Unicode, Lucida Grande

So the currently used code in [[en:Template:IPA]] is:

font-family:Code2000, Gentium, Gentium Alternative, TITUS Cyberbit Basic, Arial
Unicode MS, Lucida Sans Unicode, Lucida Grande; font-family:inherit;

I don't know how Windows deals with missing glyphs, or what the preferred order
is or should be, but this is what's currently used.
Comment 3 Gabriel Wicke 2006-03-24 12:24:20 UTC
The recommended way to do this is to use the lang attribute on elements like
span, div etc. This can be matched via CSS2 attribute selectors, making it
possible to adjust size, font family etc globally:

    Match when the element's "att" attribute value is a hyphen-separated list of
"words", beginning with "val". The match always starts at the beginning of the
attribute value. This is primarily intended to allow language subcode matches
(e.g., the "lang" attribute in HTML) as described in RFC 1766 ([RFC1766]).

So, in this case the rule would be (not sure about the canonical code for
polytonic greek):

span[lang=gr-polytonic] {
  font-family: Code2000, Gentium, Gentium Alternative, TITUS Cyberbit Basic, Arial
Unicode MS, Lucida Sans Unicode, Lucida Grande;

This selector is not implemented correctly in older versions of IE, it's fairly
easy to add a feature to the parser that adds a class to all elements that have
a lang attribute during rendering. This class can be added to the rules above to
provide the same style automatically.

I think this is the best approach to standardize multi-language handling, if
there are no objections i'll go ahead and implement it.
Comment 4 Siebrand Mazeland 2009-06-04 11:01:30 UTC
Update Web browser.
Comment 5 Siebrand Mazeland 2009-06-04 11:35:32 UTC
Adding testme. Please test with Internet Explorer 8 and note the result here.
Comment 6 Niklas Laxström 2011-07-11 12:56:47 UTC
Which versions of IE it doesn't work? We only support back to IE 6. Also, improved Narayam extension will probably supersede this.
Comment 7 Dan Collins 2011-07-17 05:09:09 UTC
The reporter has not been here in six years. We don't have any confirmation of what versions of IE it doesn't work on, it could work fine on all versions we support (6.0+). I don't think we'll be hearing anything more about this.

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