Hi,
This weekend I was reading the 'Dutch slashdot' (tweakers.net) about Wine 1.1.17 and a user was wondering when Wine would finally support font anti-aliasing. I said we have been supporting this for ages. I also thought I was using it on my own Debian system.
When asking more and more users about it in #winehackers (Chris, Detlef, Marcus, Stefan ..) only Stefan had it working on a Wine 1.1.0 build he still had around on his system (he didn't have a newer normal Wine copy) on his Gentoo. Further nobody on Debian, Fedora, Gentoo or Suse had it working except someone on a old 1.0 Wine.
For the record when anti-aliasing is around Winecfg should look like: http://stud4.tuwien.ac.at/~e0526822/winecfg.png (this on Stefan his 1.1.0).
What is so special about Wine why anti-aliasing isn't working for most users? (it could be a regression) In Stefan his case it started working after installing a Windows tahoma.ttf. What is so special about this font? A modern Linux system has dozens or hundreds of fonts installed and both GNOME/KDE can use each font AA'ed without issues.
Roderick
2009/3/15 Roderick Colenbrander thunderbird2k@gmx.net:
What is so special about Wine why anti-aliasing isn't working for most users? (it could be a regression) In Stefan his case it started working after installing a Windows tahoma.ttf. What is so special about this font? A modern Linux system has dozens or hundreds of fonts installed and both GNOME/KDE can use each font AA'ed without issues.
I recently reinstalled this system with Ubuntu 8.10 and its inbuilt Wine 1.0.1. I then added the budgededicated.com repo to get the fortnightly snapshots. A string of registry changes enabled smoothed fonts for me:
http://forum.winehq.org/viewtopic.php?p=20061&sid=6fbbcf362e44a66b310ef8...
However, it's deeply problematic that I had to do this at all instead of it Just Working when Wine was updated. This is just broken.
- d.
2009/3/15 Roderick Colenbrander thunderbird2k@gmx.net:
What is so special about Wine why anti-aliasing isn't working for most
users? (it could be a regression) In Stefan his case it started working after installing a Windows tahoma.ttf. What is so special about this font? A modern Linux system has dozens or hundreds of fonts installed and both GNOME/KDE can use each font AA'ed without issues.
I recently reinstalled this system with Ubuntu 8.10 and its inbuilt Wine 1.0.1. I then added the budgededicated.com repo to get the fortnightly snapshots. A string of registry changes enabled smoothed fonts for me:
http://forum.winehq.org/viewtopic.php?p=20061&sid=6fbbcf362e44a66b310ef8...
However, it's deeply problematic that I had to do this at all instead of it Just Working when Wine was updated. This is just broken.
- d.
For Stefan (and some others who tried 1.0) I believe it worked on a PLAIN wine config without any registry settings. Where these options added after 1.0? (I think the subpixel one was) Perhaps these options should appear in winecfg or perhaps even be turned on by default and let users disable it in there if needed.
Thanks, Roderick
Roderick Colenbrander wrote:
2009/3/15 Roderick Colenbrander thunderbird2k@gmx.net:
What is so special about Wine why anti-aliasing isn't working for most
users? (it could be a regression) In Stefan his case it started working after installing a Windows tahoma.ttf. What is so special about this font? A modern Linux system has dozens or hundreds of fonts installed and both GNOME/KDE can use each font AA'ed without issues.
I recently reinstalled this system with Ubuntu 8.10 and its inbuilt Wine 1.0.1. I then added the budgededicated.com repo to get the fortnightly snapshots. A string of registry changes enabled smoothed fonts for me:
http://forum.winehq.org/viewtopic.php?p=20061&sid=6fbbcf362e44a66b310ef8...
However, it's deeply problematic that I had to do this at all instead of it Just Working when Wine was updated. This is just broken.
- d.
For Stefan (and some others who tried 1.0) I believe it worked on a PLAIN
wine config without any registry settings. Where these options added after 1.0? (I think the subpixel one was) Perhaps these options should appear in winecfg or perhaps even be turned on by default and let users disable it in there if needed.
There is already a bug for that: http://bugs.winehq.org/show_bug.cgi?id=16729
It's back to the discussion of people just breaking stuff and never following up to fix it. Because they don't care or it's not their problem.
Vitaliy
Roderick Colenbrander wrote:
2009/3/15 Roderick Colenbrander thunderbird2k@gmx.net:
What is so special about Wine why anti-aliasing isn't working for most
users? (it could be a regression) In Stefan his case it started working after installing a Windows tahoma.ttf. What is so special about this
font? A
modern Linux system has dozens or hundreds of fonts installed and both GNOME/KDE can use each font AA'ed without issues.
I recently reinstalled this system with Ubuntu 8.10 and its inbuilt Wine 1.0.1. I then added the budgededicated.com repo to get the fortnightly snapshots. A string of registry changes enabled smoothed fonts for me:
http://forum.winehq.org/viewtopic.php?p=20061&sid=6fbbcf362e44a66b310ef8...
However, it's deeply problematic that I had to do this at all instead of it Just Working when Wine was updated. This is just broken.
- d.
For Stefan (and some others who tried 1.0) I believe it worked on a
PLAIN
wine config without any registry settings. Where these options added after 1.0? (I think the subpixel one was) Perhaps these options should appear in winecfg or perhaps even be turned on by default and let users disable it in there if needed.
There is already a bug for that: http://bugs.winehq.org/show_bug.cgi?id=16729
It's back to the discussion of people just breaking stuff and never following up to fix it. Because they don't care or it's not their problem.
Vitaliy
Thanks I hadn't seen the bug report. As far as I understand it, the only issue left is the lack of a default registy settings in wine.inf (and winecfg support) ?
Roderick