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).