Closed Bug 761691 Opened 12 years ago Closed 12 years ago

Crappy Hebrew display in version 13.0

Categories

(Core :: Graphics: Text, defect)

Product:
Core
Component:
Graphics: Text
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 756850

People

(Reporter: mtr, Unassigned)

Details

by'"`--

I went back to version 12.0 to get a good display of Hebrew again.  Problem with certain combinations of consonant + vowel, though most display; those that cannot be displayed turn into ugly boxes instead of letters.

Why did you mess up a good rendering engine with "clever" new code that ruins the display?!?!?
Would you provide a screenshot and/or a page that displays this issue?
by'"`--

I can give you a link to a page that did not display properly for me:

http://www.mechon-mamre.org/i/t/a0411.htm

Note the ugliness that appears here in version 13!!!  And try the same page in version 12.0!
by'"`--

Example of word that is not displayed properly:  יִשְׂרָאֵל

Appears 3 times on that page.
Component: General → Graphics: Text
Product: Firefox → Core
QA Contact: general → graphics-text
Harfbuzz fallout?
by'"`--

What on Earth is Harfbuzz fallout?
This is fixed for Fx15 (see bug 756850). On affected versions, you could work around the problem by setting gfx.font_rendering.harfbuzz.scripts to 3 (instead of the default 7) in about:config.

As the patch is particularly small and safe, perhaps we should uplift it to Fx14 too.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
by'"`--

So far as I can tell setting gfx.font_rendering.harfbuzz.scripts to 3 does fix this problem, at least for the page that showed the **** Hebrew.  In version 12.0 the value was already set at 3, but the new improved version 13 uses the value of 7, which messes up Hebrew at least (and who knows what else).

Why not fix version 13 already?  Why wait for version 14?
Fx13 already shipped. Fx14 is currently in beta; if we can get the fix applied there, it'll go out in the next scheduled update.
by'"`--

Before you got into competition with Chrome for the most impressive/largest version numbers, you used to offer fractional versions like version X.0 today and X.1 tomorrow (yes, when you discovered errors in programming like this one, you would fix it RIGHT AWAY, instead of waiting for the next major version).  I think that your old policy was more responsible and better than your "new improved" policy.
You need to log in before you can comment on or make changes to this bug.