Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

@font-face Thai fonts with Mozilla Firefox in normal mode can't rendered correctly, how to fix this?

  • 2 antwoorden
  • 5 hebben dit probleem
  • 26 weergaven
  • Laatste antwoord van kreaninw

more options

@font-face Thai fonts with Mozilla Firefox in normal mode can't rendered correctly, how to fix this?

It's a problem with text rendering, a tone mark stay above the place it should be.

In normal mode even with all my add-ons disabled, the problem still remains.

Note that, it rendered correctly only in safe mode.

Among all five major web browsers, the problem only happens with Firefox! This is a critical issue for Thai language when the web developers use @font-face in their website.

'''@font-face Thai fonts with Mozilla Firefox in normal mode can't rendered correctly, how to fix this?''' '''It's a problem with text rendering, a tone mark stay above the place it should be.''' '''In normal mode even with all my add-ons disabled, the problem still remains.''' '''Note that, it rendered correctly only in safe mode.''' Among all five major web browsers, the problem only happens with Firefox! This is a critical issue for Thai language when the web developers use @font-face in their website.

Bewerkt door kreaninw op

Alle antwoorden (2)

more options

In Firefox 4 and later Safe mode disables extensions and disables hardware acceleration.

  • Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"

Try to toggle some Boolean gfx.font_rendering prefs on the about:config page to disable some features.
Filter: gfx

Some to try:

  • set gfx.direct2d.disabled to true to disable Direct2D
  • set gfx.font_rendering.directwrite.use_gdi_table_loading to false
more options

This solution doesn't help at all. T-T

I think it's a bug.