https://bugs.winehq.org/show_bug.cgi?id=48783
Bug ID: 48783 Summary: Wine Tahoma is missing many glyphs Product: Wine Version: 5.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: fonts Assignee: wine-bugs@winehq.org Reporter: huupoke12@gmail.com Distribution: ---
The built-in Tahoma is missing many glyphs. This make programs just renders them as boxes. Some of them are in Greek, Thai and Latin Extended Additional (Vietnamese) plane.
https://bugs.winehq.org/show_bug.cgi?id=48783
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #1 from Zebediah Figura z.figura12@gmail.com --- It would be nice to make this bug a bit more specific, e.g. can we target a specific set of glyphs? Otherwise I don't know when this bug can be considered resolved.
https://bugs.winehq.org/show_bug.cgi?id=48783
--- Comment #2 from Nguyen Chinh Huu huupoke12@gmail.com --- I think that we should cover the same set of glyph range as MS Tahoma (FontForge is useful to see font's covered ranges). If this not possible for the all of the glyphs, then I think at least we should cover the languages that MS Tahoma cover. As I see, Thai, Greek, Hebrew, some Vietnamese (Latin Extended Additional), some Cyrillic is missing.
https://bugs.winehq.org/show_bug.cgi?id=48783
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #3 from Anastasius Focht focht@gmx.net --- Hello folks,
as Zeb indicated, the ranges should more specific and linked to actual application misbehaviour ("glyphs x,y not rendered in app foobar, making UI unusable").
I recently mentioned one of these long standing font meta-bugs -> bug 7156 (wingdings) in https://bugs.winehq.org/show_bug.cgi?id=12995#c16
These font meta-bugs get recycled over and over again and essentially stay for many years.
Regards
https://bugs.winehq.org/show_bug.cgi?id=48783
--- Comment #4 from Nguyen Chinh Huu huupoke12@gmail.com --- So I don't think this problem can be solved in that way (creating new glyphs). The program doesn't have a static character set, mostly of it is user-generated content (chat, metadata (names)...).
So I think that we should re-use existing fonts. There are many high quality font licensed under SIL Open font license, so if they are incompatible with LGPL, then we should make a separate package for it (like wine-gecko and wine-mono). But I think that the SIL license is only applied to those fonts, not the application comes with those font. And if that still not possible, then we should make the system responsible of rendering the missing glyphs (fontconfig just find the installed fonts for the glyphs). And by the way, I see GNU FreeFont is under GPL but it's v3, I don't think it compatible with v2.
https://bugs.winehq.org/show_bug.cgi?id=48783
--- Comment #5 from Nikolay Sivov bunglehead@gmail.com --- It has to be metrics-compatible with original Tahoma to be a suitable replacement.
https://bugs.winehq.org/show_bug.cgi?id=48783
--- Comment #6 from Nguyen Chinh Huu huupoke12@gmail.com --- After some testing and inspection, I have some questions:
1. I noticed that that W10's shipped Tahoma is not fully metric-compatible with the Tahoma in Wine (Wine Tahoma only fully metric-compatible with the Tahoma in the tahoma verb which can be downloaded from winetricks). Why MS not keeping it fully metric-compatible with the previous version of Tahoma?
2. As I see, W10's Tahoma doesn't contain bitmap glyphs. Is it necessary for Wine Tahoma to have bitmap glyphs? And I thought that the .sfd are the source files for fonts, but Wine tahoma.sfd only contains bitmap fonts, and the vector fonts is only in tahoma.ttf. So if I want to contribute to Wine Tahoma (vector font), I have to create a git commit for a binary file (tahoma.ttf)? I don't think using git to track binary files is a good idea. And do I have to also to make change to the same glyphs for the bitmap font?
3. As I see, the vector font tahoma.ttf is based on Bitstream Vera fonts (the bitmap font tahoma.sfd seems to be also somewhat to be based on it, but many glyphs are self-created?). So if I want to contribute more glyphs to Wine Tahoma, is it fine if I take the glyphs from DejaVu fonts (DejaVu changes seems to be in a public domain and another one license for some glyphs which is very similar with Bitstream Vera font license).
https://bugs.winehq.org/show_bug.cgi?id=48783
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=48783
--- Comment #7 from Nikolay Sivov bunglehead@gmail.com --- (In reply to Nguyen Chinh Huu from comment #6)
After some testing and inspection, I have some questions:
- I noticed that that W10's shipped Tahoma is not fully metric-compatible
with the Tahoma in Wine (Wine Tahoma only fully metric-compatible with the Tahoma in the tahoma verb which can be downloaded from winetricks). Why MS not keeping it fully metric-compatible with the previous version of Tahoma?
I don't know how you're testing this.
- As I see, W10's Tahoma doesn't contain bitmap glyphs. Is it necessary for
Wine Tahoma to have bitmap glyphs? And I thought that the .sfd are the source files for fonts, but Wine tahoma.sfd only contains bitmap fonts, and the vector fonts is only in tahoma.ttf. So if I want to contribute to Wine Tahoma (vector font), I have to create a git commit for a binary file (tahoma.ttf)? I don't think using git to track binary files is a good idea. And do I have to also to make change to the same glyphs for the bitmap font?
Windows font contains hinting program, and no bitmaps. Wine has no hinting program, but bitmaps for some sizes, to make it look better than it otherwise would. Fontforge source tahoma.sfd contains both bitmaps and outlines. Repo contains both sources and generated font files, so you don't have to do that in build time (wine uses slightly customized version of fontforge for that).
- As I see, the vector font tahoma.ttf is based on Bitstream Vera fonts
(the bitmap font tahoma.sfd seems to be also somewhat to be based on it, but many glyphs are self-created?). So if I want to contribute more glyphs to Wine Tahoma, is it fine if I take the glyphs from DejaVu fonts (DejaVu changes seems to be in a public domain and another one license for some glyphs which is very similar with Bitstream Vera font license).
https://bugs.winehq.org/show_bug.cgi?id=48783
--- Comment #8 from Nguyen Chinh Huu huupoke12@gmail.com --- (In reply to Nikolay Sivov from comment #7)
I don't know how you're testing this.
I use LibreOffice with some text copied from Wikipedia and see if the lines breaking at different positions with different fonts (Select all => Change to a font => Change to another font => Keep Ctrl-Z and Ctrl-Shift-Z to see the differences).
Fontforge source tahoma.sfd contains both bitmaps and outlines
Sorry, I didn't notice there are both bitmap and outline layers there. FontForge show bitmap glyphs by default.
- ...
I see that you are quoting this section but there are no reply content from you. If this is an error, please reply it again.
https://bugs.winehq.org/show_bug.cgi?id=48783
--- Comment #9 from Nguyen Chinh Huu huupoke12@gmail.com --- Created attachment 66844 --> https://bugs.winehq.org/attachment.cgi?id=66844 The odt file and screenshots taken from the metric testing of Tahoma
-
WineHQ Bugzilla