Its Microsoft's fault :P

When firefox sees a character that doesn't exist in the current font, it tries every font it has until it finds one that works. When IE sees a character that doesn't exist in the current font, it sits down and cries.

Explicitly specifying a font that has that character would fix the issue though.

Giving this to Alolita as she is most likely to know who should/could apply the font-specification.

Created attachment 8541
IE9 screenshot. "my" language name highlighted

Added IE9 screenshot with "my" autonym highlighted. I confirm the observation that after adding the font that is advertised on the main page of http://my.wikipedia.org the interwiki link is not being diplayed in a readable format. Blocks are still being displayed, while text in my.wp is now displayed in characters instead of blocks. I have also tested on Firefox 4 in OSX with the same font, and there everything worked as expected; both interwiki link description as well as my.wp content were displayed in characters instead of blocks.

Feels very much like a browser issue, and not as a MediaWiki issue.

Attached:

Yes, it is a browser issue, but see the description: MW developers can work around it by specifying font-family explicitly for this language.

A solution that will be even better, though slightly harder to implement, would be to specify a webfont for every language based on the lang attribute. But until this is implemented (and it should be!) font-family must be explicitly specified for the interlanguage links to Burmese.

Is this solved now by WebFonts/ULS?

Amir: Do you know if this is solved by WebFonts/ULS?

Amir: Do you know if this is solved by WebFonts/ULS?

(Sorry about the delay - for some reason I didn't receive emails about this bug.)

It is solved by Webfonts or ULS on wikis where Webfonts or ULS are installed. That means - not on the English Wikipedia, for example.