Sorry, but this report is pretty vague.

Can you give an example of the actual style code you might want?

grendelkhan wrote:

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.

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:

[att|=val]

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):

div[lang=gr-polytonic],
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.

Update Web browser.

Adding testme. Please test with Internet Explorer 8 and note the result here.

Which versions of IE it doesn't work? We only support back to IE 6. Also, improved Narayam extension will probably supersede this.

EN.WP.ST47 wrote:

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.