On Mon, Jun 20, 2005 at 01:10:11PM -0500, Robert Shearman wrote:
Changelog: The "Wine Marlett" font needs to be called "Marlett" for Steam to pick it up.
The font replacement mechanism should make this unnecessary. Why doesn't that work in this case?
Huw.
Huw D M Davies wrote:
On Mon, Jun 20, 2005 at 01:10:11PM -0500, Robert Shearman wrote:
Changelog: The "Wine Marlett" font needs to be called "Marlett" for Steam to pick it up.
The font replacement mechanism should make this unnecessary. Why doesn't that work in this case?
It enumerates the fonts, but Marlett isn't enumerated, only "Wine Marlett." I tried adding a value in the FontSubstitutes and Fonts registry keys and the problem was the same. You can test this very easily using notepad's Edit->Font dialog. Steam only started working when Marlett was listed as a font in there.
On Mon, Jun 20, 2005 at 01:37:45PM -0500, Robert Shearman wrote:
Huw D M Davies wrote:
On Mon, Jun 20, 2005 at 01:10:11PM -0500, Robert Shearman wrote:
Changelog: The "Wine Marlett" font needs to be called "Marlett" for Steam to pick it up.
The font replacement mechanism should make this unnecessary. Why doesn't that work in this case?
It enumerates the fonts, but Marlett isn't enumerated, only "Wine Marlett." I tried adding a value in the FontSubstitutes and Fonts registry keys and the problem was the same. You can test this very easily using notepad's Edit->Font dialog. Steam only started working when Marlett was listed as a font in there.
Yup, that's the fonts substitutes mechanism which is different from the replacements one<g> See LoadReplaceList in gdi/freetype.c
You need something like this:
[HKCU\Software\Wine\Fonts\Replacements] "Marlett"="Wine Marlett"
Huw.
Huw D M Davies wrote:
On Mon, Jun 20, 2005 at 01:37:45PM -0500, Robert Shearman wrote:
Huw D M Davies wrote:
On Mon, Jun 20, 2005 at 01:10:11PM -0500, Robert Shearman wrote:
Changelog: The "Wine Marlett" font needs to be called "Marlett" for Steam to pick it up.
The font replacement mechanism should make this unnecessary. Why doesn't that work in this case?
It enumerates the fonts, but Marlett isn't enumerated, only "Wine Marlett." I tried adding a value in the FontSubstitutes and Fonts registry keys and the problem was the same. You can test this very easily using notepad's Edit->Font dialog. Steam only started working when Marlett was listed as a font in there.
Yup, that's the fonts substitutes mechanism which is different from the replacements one<g> See LoadReplaceList in gdi/freetype.c
You need something like this:
[HKCU\Software\Wine\Fonts\Replacements] "Marlett"="Wine Marlett"
Thanks, that works. This patch is unnecessary.
Robert Shearman rob@codeweavers.com writes:
Huw D M Davies wrote:
You need something like this:
[HKCU\Software\Wine\Fonts\Replacements] "Marlett"="Wine Marlett"
Thanks, that works. This patch is unnecessary.
Except that it requires users to configure their registry properly... Is there really a reason to use a different name?
On Tue, Jun 21, 2005 at 04:13:00PM +0200, Alexandre Julliard wrote:
Robert Shearman rob@codeweavers.com writes:
Huw D M Davies wrote:
You need something like this:
[HKCU\Software\Wine\Fonts\Replacements] "Marlett"="Wine Marlett"
Thanks, that works. This patch is unnecessary.
Except that it requires users to configure their registry properly... Is there really a reason to use a different name?
It would be nice to have the Windows fonts overload the Wine ones if they're present, which is what the current scheme does. Now, for TrueType fonts we could set the version low enough such that the Windows fonts would win, but there's no version associated with a .fon font so we couldn't use that trick there.
Huw.
Huw D M Davies h.davies1@physics.ox.ac.uk writes:
It would be nice to have the Windows fonts overload the Wine ones if they're present, which is what the current scheme does. Now, for TrueType fonts we could set the version low enough such that the Windows fonts would win, but there's no version associated with a .fon font so we couldn't use that trick there.
Can't this be based on the font path, using the first font we find in the path? Then we just have to make sure the Windows dir is searched first.
On Tue, Jun 21, 2005 at 04:50:50PM +0200, Alexandre Julliard wrote:
Can't this be based on the font path, using the first font we find in the path? Then we just have to make sure the Windows dir is searched first.
That would work if the Wine fonts end up in the Windows dir, but aren't they likely to get installed into somewhere under /usr/share/fonts ?
Also, I like the versioning thing, it lets me have the ms webfonts under /usr/share/fonts and have /win/winnt/fonts in my fontconfig path. This way, if my Windows partition has a newer version of Arial than the ms webfonts I get to use that, rather than it being on a first come first serve basis.
Can't we just add the Replacement keys to wine.inf and be done with it?
Huw.
Huw D M Davies h.davies1@physics.ox.ac.uk writes:
On Tue, Jun 21, 2005 at 04:50:50PM +0200, Alexandre Julliard wrote:
Can't this be based on the font path, using the first font we find in the path? Then we just have to make sure the Windows dir is searched first.
That would work if the Wine fonts end up in the Windows dir, but aren't they likely to get installed into somewhere under /usr/share/fonts ?
Well, yes, the idea would be to search the Windows dir before /usr/share/fonts.
Also, I like the versioning thing, it lets me have the ms webfonts under /usr/share/fonts and have /win/winnt/fonts in my fontconfig path. This way, if my Windows partition has a newer version of Arial than the ms webfonts I get to use that, rather than it being on a first come first serve basis.
Sure, for fonts that have versions the priority can be based on that. First come first serve would only be for fonts that can't be versioned.
Can't we just add the Replacement keys to wine.inf and be done with it?
Yes, but that's ugly, Wine should be able to behave sanely without special registry entries.
On Tue, Jun 21, 2005 at 05:42:53PM +0200, Alexandre Julliard wrote:
Huw D M Davies h.davies1@physics.ox.ac.uk writes:
On Tue, Jun 21, 2005 at 04:50:50PM +0200, Alexandre Julliard wrote:
Can't this be based on the font path, using the first font we find in the path? Then we just have to make sure the Windows dir is searched first.
That would work if the Wine fonts end up in the Windows dir, but aren't they likely to get installed into somewhere under /usr/share/fonts ?
Well, yes, the idea would be to search the Windows dir before /usr/share/fonts.
Sorry, I misread this. So in order to have sserife.fon beat wine_sserife.fon I'd have to copy it into my Windows dir? I'd like this to happen automatically if sserife.fon existed in my fontconfig path. (Yes, I know it won't at the moment because we ignore all bitmap fonts in the fontconfig path, but I think this should be changed to let .fon bitmap through).
Can't we just add the Replacement keys to wine.inf and be done with it?
Yes, but that's ugly, Wine should be able to behave sanely without special registry entries.
True, and maybe that usurps my objection above.
Huw.
Hi,
On Tue, Jun 21, 2005 at 03:27:12PM +0100, Huw D M Davies wrote:
It would be nice to have the Windows fonts overload the Wine ones if they're present, which is what the current scheme does. Now, for TrueType fonts we could set the version low enough such that the Windows fonts would win, but there's no version associated with a .fon font so we couldn't use that trick there.
This might be problematic if some special software checks the font version, in case of a lower, non-standard Wine font version number. Or are font versions such randomly distributed that Windows programs wouldn't make such assumptions anyway?
As for .fon files, wouldn't it be possible to abuse (slightly modify) any other .fon struct item to indicate a Wine font that should have low priority? A version value really isn't that special when it comes to making a good distinction...
Andreas Mohr
-
Alexandre Julliard -
Andreas Mohr -
Huw D M Davies -
Robert Shearman