We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Since upgrading to Firefox 33, The open sans font did not display correctly when specified by a website.

  • 7 답장
  • 20 이 문제를 만남
  • 1 보기
  • 최종 답변자: saewulf

more options

Some of the vertical lines in the fonts are double width like a mixture of bold and normal font weight. I have hardware accellaration disabled. The problem is not fixed when I change default font settings. The problem is not resolved be resetting zoom to 0.

Inspect Element identifies the problem happens when the website selects open Sans. If I stop sites selecting fonts and force the defaults I don not get the problem. Therefore the problem is with Firefox 33.1 rendering certain fonts specified by websites.

My machine is windows vista and Open Sans is not shown in the font list. However this was not a problem with previous versions of Firefox.

I did need to do a reset of firefox parameters during the upgrade to 33 so maybe ther eis some other parameter which needs changing to help render fonts which are not loaded on the machine?

Some of the vertical lines in the fonts are double width like a mixture of bold and normal font weight. I have hardware accellaration disabled. The problem is not fixed when I change default font settings. The problem is not resolved be resetting zoom to 0. Inspect Element identifies the problem happens when the website selects open Sans. If I stop sites selecting fonts and force the defaults I don not get the problem. Therefore the problem is with Firefox 33.1 rendering certain fonts specified by websites. My machine is windows vista and Open Sans is not shown in the font list. However this was not a problem with previous versions of Firefox. I did need to do a reset of firefox parameters during the upgrade to 33 so maybe ther eis some other parameter which needs changing to help render fonts which are not loaded on the machine?

선택된 해결법

Is the operating system using font smoothing or cleartype? That makes a difference.

문맥에 따라 이 답변을 읽어주세요 👍 2

모든 댓글 (7)

more options

Here is a screenshot:

more options

Try to disable OMTC and leave hardware acceleration in Firefox enabled.

Do other fonts have the same issue?

You can do a font test to see if you can identify corrupted font(s).

more options

Thanks Cor-el. I've re-enabled hardware acceleration and disabled OMTC. No sign of the dragons. I've also downloaded and installed the Open Sans font family. None of these change the display in Firefox.

the font test shows open sans as bad but others such as myriad pro look a bit strange. I printed the test to a pdf. The print preview screen has the problem but acrobat renders the fonts correctly. So does IE8.

I thought about trying to output the whole set of parameters from about:config but at the moment havnt seen how to do that. Anyway this site doesnt let me upload a pdf.

Any more ideas welcome.

more options

You could try this setting in about:config: gfx.use_text_smoothing_setting -> true

It works for me.

more options

Thanks Finitarry. I've trid that change but the problem still exists. Maybe it is one of the other rendering parameters or now firefox wants cleartype fonts while my vist machine only has trutype and opentype. No doubt I will have learned something about fots by the time this is solved.

more options

선택된 해결법

Is the operating system using font smoothing or cleartype? That makes a difference.

more options

Ive gone through control panel to windows appearance and effects. There I enabled cleartype and behold the problem is solved.

Presumably acrobat didnt have the problem because it is for print and doesnt use cleartype. And maybe IE8 didnt need or rely on cleartype because it is old.

The other settings changes suggested above are still in place and so may be contributing to the solution.

Many Thanks Finitarry