770362 - One Mozilla blog theme shouldn't be using only a subset of glyphs for Open Sans

Status: RESOLVED FIXED

(Websites Graveyard :: blog.mozilla.org, defect)

Description

[Fred Wenzel [:wenzel]]

Example blog post:

http://blog.mozilla.org/l10n/2012/06/15/get-to-know-a-l10n-driver-matjaz-horvat/

Matjaz' name contains an easter European glyph that's not currently contained in our fonts.

We should probably use the full font.

Comment 1

[Craig Cook (:craigcook)]

It turns out this isn't a blog theme issue, it's a Tabzilla issue. Tabzilla loads Open Sans via @font-face, defined with the same name used in the theme's styles. And because tabzilla.css loads first, it's first to define that name. The copy of Open Sans tabzilla references lives at mozilla.org/img/fonts and is the MacRoman subset, which does cover most western languages but still lacks some of the glyphs common in Polish (and other languages).

I've updated that font to the unsubsetted version in r106949, which we'll need to push to production. The unsubsetted font has a much broader character set, but the trade-off is a much larger file size (went from 30k to 107k).

Comment 2

[Valerie Ponell]

Thanks for looking into this Craig. I actually just noticed the same issue when starting to add content to our Polish press center: http://blog.mozilla.org/press-pl/

Comment 3

[Valerie Ponell]

Hi everyone,

the Polish press center still does not display Polish characters properly (in Firefox): https://blog.mozilla.org/press-pl/

Anything we can do to get this fixed?

Thanks,

Valerie

Comment 4

[Craig Cook (:craigcook)]

Tabzilla is still referencing the subsetted copy of the font, but we're going to be establishing a single official instance of the Open Sans with the full character set, so this will be fixed very soon (see bug 776905).

Comment 5

[Pascal Chevrel:pascalc (PTO until April 26)]

This looks fixed to me