Yup, the right custom skin is set. The fonts are sourced from https://www.google.com/fonts, and I've followed the quick-use instructions; i.e.,
<link href='http://fonts.googleapis.com/css?family=Lato' rel='stylesheet' type='text/css'>
was placed in the header wrapper and embeds the following
@font-face {
font-family: 'Bitter';
font-style: normal;
font-weight: 700;
src: local('Bitter-Bold'), url(http://themes.googleusercontent.com/static/fonts/bitter/v5/evC1haE-MsorTl_A7_uSGbO3LdcAZYWl9Si6vvxL-qU.woff) format('woff');
} and
.bitter { font-family: ‘Bitter’, Arial, serif; }was placed in the active skin's custom css. The class was triggered in the markup like so:
<h1 class="bitter">And hopefully custom fonts work too.</h1>
I've also tried loading the font manually in the custom css only, so it doesn't seem to be a loading order problem. Any thoughts?