Make WordPress Core

Opened 10 years ago

Closed 8 years ago

#29788 closed defect (bug) (invalid)

Open Sans font won't display Hebrew pages in IE 11

Reported by: narodu's profile narodu Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Themes Keywords:
Focuses: Cc:

Description

Hi,

The problem: Hebrew pages come out blank in IE 11 when using Twenty Twelve and up basic WP themes.

This is a known issue: http://stackoverflow.com/questions/23438319/using-import-for-google-fonts-is-not-working-on-internet-explorer

It's an issue in WP since this font came into use around version 3.0 and the upgrade of themes 2012 and 2013. In my team we have bypassed it with child themes. I thought I should report it after attending contributors day in WCEU2014.

Proposed solution: use for for default font in WP themes any other font that has local versions for any language.

Best

Change History (7)

#1 @SergeyBiryukov
10 years ago

  • Summary changed from Open Sons font won't display Hebrew pages in IE 11 to Open Sans font won't display Hebrew pages in IE 11

Google fonts can be disabled per language, and Open Sans is already disabled in Hebrew translation for both core and Twenty Twelve.

Twenty Thirteen uses Source Sans Pro and Bitter fonts, which are enabled. They should probably be disabled too if they cause issues.

#2 @chriscct7
9 years ago

  • Keywords needs-patch added

This ticket was mentioned in Slack in #core-i18n by ocean90. View the logs.


9 years ago

#4 @swissspidy
9 years ago

  • Component changed from I18N to Themes

#5 follow-up: @xavortm
9 years ago

Related to #36753 - System fonts are to be used instead of Open Sans.

#6 in reply to: ↑ 5 @melchoyce
8 years ago

Replying to xavortm:

Related to #36753 - System fonts are to be used instead of Open Sans.

This one isn't related, since it's talking about Open Sans displaying in themes, not in core.

#7 @SergeyBiryukov
8 years ago

  • Keywords needs-patch removed
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

No other reports in two years, and no evidence that something's wrong here, see comment:1.

Feel free to reopen if there's still an issue.

Note: See TracTickets for help on using tickets.