Digit 9 in [old AAT version of] Lucida Grande renders as en-dash
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
People
(Reporter: benjamin.lerner, Unassigned)
References
Details
Attachments
(1 file)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0
Steps to reproduce:
Visit https://betanews.com/2019/04/07/windows-10-safely-remove-usb/ on Windows 10 (ironically, v1809) with default system Lucida Grande fonts installed.
Actual results:
The digit nine, in e.g. "Windows 1809" renders as "Windows 180–" (that's an en-dash, and it might even render as an em-dash, hard to tell). If I select and copy the text, I indeed get the digit nine, so it's a display issue somehow. I've tried this in safe mode, to confirm it's not an extension weirdness (though I don't know how an extension could cause that).
If I tweak the CSS in the page, so that the normal text renders as Lucida Grande Bold, then the digit appears just fine. If I tweak it to be italicized, there's no effect.
I've edited the text to contain 1234567890, and only the 9 renders incorrectly.
If I tweak the CSS to use a different font, it appears correctly.
So far as I know, Lucida Grande isn't a subsetted font (as I've recently seen has problems with unicode characters), and all the other bugs I've seen for "Lucida Grande" are either closed or macOS-specific and several years old, so I suspect this is a new issue.
| Reporter | ||
Comment 1•7 years ago
|
||
Comment 2•7 years ago
|
||
Hi Ben, I can't reproduce this issue because the recognized font for me is Lucida SANS Unicode instead of Lucida Grande, I also tried downloading and installing the font but still the Sans unicode is recognized on that page, I'll set the component for this issue, maybe our devs will manage to reproduce and fix this issue.
Comment 3•7 years ago
|
||
As far as I'm aware, Lucida Grande does not ship with Windows 10; so the first question here is exactly what Lucida Grande font you have installed. Where did it come from, and what precise version is it?
Aside from a bad font resource, the other possibility would be some kind of system corruption. Does completely shutting down and restarting Windows make any difference?
| Reporter | ||
Comment 4•7 years ago
|
||
Hmm, I migrated fonts from my older (Win7) laptop to this one, so it's possible that it migrated from there, but I honestly don't recall (and I don't know how it would've gotten onto that laptop either). I'm on a linux machine at work right now, so I can't check the font version until later tonight. (I'll leave the needinfo flag set until then.)
As for system corruption: no, restarting Firefox, restarting in safe mode, restarting Windows, restarting Fx again, running Windows Update, restarting again, and restarting Firefox again all did nothing for this.
Comment 5•7 years ago
|
||
OK, thanks. If you can confirm the exact version (and file size, as a cross-check) when you have the opportunity, that would be useful.
Another thing to try would be using Lucida Grande in other applications: e.g. if you run WordPad and format the same text using the exact same font and size, does the same problem with the '9' show up?
| Reporter | ||
Comment 6•7 years ago
|
||
My system has only two Lucida Grande fonts on it: regular and bold. It appears I have Lucida Grande (regular) v0.24.1, size 297,824 bytes, SHA256 of 78D58E0050593266E258415389C30587CEDEBCDB5E6D782E95E99AC3C3FF2417. And somehow I have Lucida Grande (bold) v0.45.1, size 193,212 bytes, SHA256 45D5353A7D0714907D72E26195BEB1A14D68F9967F066A520C8D8551E74DBDFB. I have no clue why they're different versions.
When I try running WordPad and use Lucida Grande there, all the digits show up just fine. But simultaneously, Firefox still doesn't render the digit.
If this font is just horrifically old, and there's an updated version I should be using, then I'll happily update. But still, kinda odd.
Comment 7•7 years ago
|
||
After off-line discussion and examination of the font involved, it appears to be a very old version of Lucida Grande originally shipped with Apple software (Mac OS X, Safari, or something like that), and contains a 'mort' table which -- when used with harfbuzz, which has added 'mort' support recently -- results in the '9' -> dash substitution. The same thing happens in Chrome.
It doesn't happen in WordPad (etc) because that only uses OpenType layout tables (GSUB/GPOS) and not AAT layout (feat/mort).
So the problem is caused by the flawed 'mort' table in this font, in combination with harfbuzz's recently-added 'mort' shaping support; not really a Firefox bug.
Description
•