[wp-trac] [WordPress Trac] #21751: Twenty Twelve: allow translators to disable Open Sans custom font

[WordPress Trac]

#21751: Twenty Twelve: allow translators to disable Open Sans custom font
---------------------------+---------------------------
 Reporter:  pavelevap      |       Owner:  lancewillett
     Type:  defect (bug)   |      Status:  reopened
 Priority:  normal         |   Milestone:  3.5
Component:  Bundled Theme  |     Version:  trunk
 Severity:  major          |  Resolution:
 Keywords:  has-patch      |
---------------------------+---------------------------

Comment (by SergeyBiryukov):

 Replying to [comment:34 lancewillett]:
 > After a bunch more testing and research, it appears the subset parameter
 has no effect on the language character support. It works with out it and
 with it.

 From my testing, it does make a difference. I've got consistent results on
 Firefox 15, Chrome 21 and 23, IE 8 and 9, Opera 12, on both Windows XP and
 Windows 7.

 1. On initial page load, all characters are visible, although Cyrillic
 characters are displayed in Arial: [attachment:21751.cyrillic-arial.png]
 (also [attachment:ticket:21775:21775.content.png] in Opera).
 2. Adding `&subset=latin,cyrillic` to the `wp_enqueue_style()` call fixes
 that in all browsers, *even in Chrome on Vista*: [attachment:21751
 .cyrillic-open-sans.png].

 So it seems that [attachment:21751.open-sans-subsets.diff] would be
 helpful after all.

 P.S. The only weird thing I've noticed is that on Windows 7, Opera doesn't
 fall back to Arial if I remove `&subset=latin,cyrillic` after step 2.
 Cyrillic characters become invisible ([attachment:21751.opera.2.png])
 until the browser is restarted (clearing cache doesn't help). Then it
 falls back to Arial again.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/21751#comment:38>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software