Same issue here with the <a class=”users-name” href=”/users/mtrazzi”>Michaël Trazzi</a> tag. The e in “ë” is larger than the “a” (here is a picture).
The bug seems to come from font-family: warnock-pro,Palatino,”Palatino Linotype”,”Palatino LT STD”,”Book Antiqua”,Georgia,serif;” in .PostsPage-author (in <style data-jss=”″ data-meta=”PostsPage”>).
If I delete this font-family line, the font changes but the “ë” (and any other letter with accent) appears to have the correct size.
Less Wrong team: what seems to be going on is that you’re using TypeKit’s subsetting feature to specify a quite restrictive subset for the Warnock Pro font, which is excluding characters such as ‘ë’. Thus the copy of the font file that’s being served to visitors of Less Wrong doesn’t include that character.
As a result, ‘ë’ (and other characters with diacritical marks) is being rendered in one of the fallback fonts. Naturally, in the case of some of those fonts, the x-height and other metrics of the fallback font will differ from those of Warnock Pro, resulting in the visual glitch linked above.
This is easily fixed by specifying a less aggressive subsetting config in TypeKit for Warnock Pro.
Hey admins: The “ë” in “Michaël Trazzi” is weird, probably a bug in your handling of Unicode.
It looks just fine on both Less Wrong and GreaterWrong. (In both places, it correctly appears as U+00EB “Latin Small Letter E with Diaresis”.)
Perhaps it is a bug on your end? What platform / browser / version are you running?
Same issue here with the <a class=”users-name” href=”/users/mtrazzi”>Michaël Trazzi</a> tag. The e in “ë” is larger than the “a” (here is a picture).
The bug seems to come from font-family: warnock-pro,Palatino,”Palatino Linotype”,”Palatino LT STD”,”Book Antiqua”,Georgia,serif;” in .PostsPage-author (in <style data-jss=”″ data-meta=”PostsPage”>).
If I delete this font-family line, the font changes but the “ë” (and any other letter with accent) appears to have the correct size.
Ok, I think see the issue.
Less Wrong team: what seems to be going on is that you’re using TypeKit’s subsetting feature to specify a quite restrictive subset for the Warnock Pro font, which is excluding characters such as ‘ë’. Thus the copy of the font file that’s being served to visitors of Less Wrong doesn’t include that character.
As a result, ‘ë’ (and other characters with diacritical marks) is being rendered in one of the fallback fonts. Naturally, in the case of some of those fonts, the x-height and other metrics of the fallback font will differ from those of Warnock Pro, resulting in the visual glitch linked above.
This is easily fixed by specifying a less aggressive subsetting config in TypeKit for Warnock Pro.