Hi, this is mainly a follow up to the thread here http://www.winehq.org/pipermail/wine-devel/2007-May/057092.html , to give it a new boost....
Question is, are there any plans to include Liberation fonts in wine? I gave it a good testing last two weeks, that is, i converted the fonts with Hans' Leidekkers script , from link above, and tested the "Arial-compatible" font quite a bit, with several applications. It all seems to work great, no issues / problems found. Several applications would be very happy , if this were to be included in wine. Any comments?
Some of the tested apps: xchat --> just aborts silently without arial font Book worms adventures --> pops up a crash window without arial font d3d9-samples from DirectX 9.0 SDK --> Don't show any text without arial font + a lot more that just look prettier with arial font.
--------------------------------- Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for your freeaccount today.
On Thursday 14 June 2007 22:50:07 Louis. Lenders wrote:
Question is, are there any plans to include Liberation fonts in wine?
You mean add them to the git repository? I don't think we want that because we don't maintain them. Wine distributors could perhaps create a wine-fonts package that installs the fonts in a common place and then patch wineprefixcreate to copy the fonts from there.
-Hans
Hans Leidekker wrote:
On Thursday 14 June 2007 22:50:07 Louis. Lenders wrote:
Question is, are there any plans to include Liberation fonts in wine?
You mean add them to the git repository? I don't think we want that because we don't maintain them. Wine distributors could perhaps create a wine-fonts package that installs the fonts in a common place and then patch wineprefixcreate to copy the fonts from there.
Why do you need to copy the fonts? Wine can use the system fonts. The Wine package would need to have only a dependency on the liberation font package. The liberation-fonts rpm is already in Fedora Extras for FC6 and in Fedora 7.
bye michael
On Friday 15 June 2007 12:14:06 Michael Stefaniuc wrote:
Why do you need to copy the fonts? Wine can use the system fonts. The Wine package would need to have only a dependency on the liberation font package. The liberation-fonts rpm is already in Fedora Extras for FC6 and in Fedora 7.
That doesn't help when an app asks for Arial. Or when it references the file c:\windows\fonts\arial.ttf directly.
-Hans
"Hans Leidekker" hans@it.vu.nl wrote:
On Friday 15 June 2007 12:14:06 Michael Stefaniuc wrote:
Why do you need to copy the fonts? Wine can use the system fonts. The Wine package would need to have only a dependency on the liberation font package. The liberation-fonts rpm is already in Fedora Extras for FC6 and in Fedora 7.
That doesn't help when an app asks for Arial. Or when it references the file c:\windows\fonts\arial.ttf directly.
... which happens with every app that uses gdiplus.dll.
Hans Leidekker <hans <at> it.vu.nl> writes:
On Friday 15 June 2007 12:14:06 Michael Stefaniuc wrote:
Why do you need to copy the fonts? Wine can use the system fonts. The Wine package would need to have only a dependency on the liberation font package. The liberation-fonts rpm is already in Fedora Extras for FC6 and in Fedora 7.
That doesn't help when an app asks for Arial. Or when it references the file c:\windows\fonts\arial.ttf directly.
-Hans
So could something be included in wine's source like detect if they are present (/usr/share/fonts/liberation/ here), use Hans' convert-script to "convert" it into arial.ttf, and then copy them into /usr/share/wine/fonts/, i think that would be enough for apps to detect the font, right?
On Friday 15 June 2007 13:25:19 Louis Lenders wrote:
So could something be included in wine's source like detect if they are present (/usr/share/fonts/liberation/ here), use Hans' convert-script to "convert" it into arial.ttf, and then copy them into /usr/share/wine/fonts/, i think that would be enough for apps to detect the font, right?
They need to be inside your wineprefix (i.e. in c:\windows\fonts) for maximum compatibility. Much like how the fake dlls are generated from Wine's globally installed shared libraries and placed inside your Wine prefix when you run wineprefixcreate.
-Hans
On Fri, 15 Jun 2007, Hans Leidekker wrote:
On Friday 15 June 2007 12:14:06 Michael Stefaniuc wrote:
Why do you need to copy the fonts? Wine can use the system fonts. The Wine package would need to have only a dependency on the liberation font package. The liberation-fonts rpm is already in Fedora Extras for FC6 and in Fedora 7.
That doesn't help when an app asks for Arial. Or when it references the file c:\windows\fonts\arial.ttf directly.
Maybe Wine could check for the existence of the fonts and set up a symlink farm pointing to them from the Windows expected locations?
Steve Brown sbrown7@umbc.edu
On Friday 15 June 2007 15:30:27 Steve Brown wrote:
Maybe Wine could check for the existence of the fonts and set up a symlink farm pointing to them from the Windows expected locations?
Yes, symlinks in c:\windows\fonts that point to modified, system-wide Liberation fonts should work in most cases. Because the files are read-only we'll have a problem when we find an app that wants to write to the files.
Since that is very unlikely I'd say we should go for symlinks to save space and time. We can resort to full copies when we find an app that needs it.
-Hans
On 6/15/07, Hans Leidekker hans@it.vu.nl wrote:
Since that is very unlikely I'd say we should go for symlinks to save space and time. We can resort to full copies when we find an app that needs it.
While this strikes me as 100% a packaging issue, it just seems like something really prone to error. When the new Foo distro comes out and decides to place their fonts in /opt/Foo/X they'll need to figure out how to make the sym links, but then maybe they won't include these fonts, so the package maintainer will have to make another package and ship it alongside Wine. That'll work great until Wine gets ported some other OS that doesn't include the fonts, then that maintainer will have to deal with some odd scheme.
We're talking 1MB of duplication in the filesystem (to download: 600k) - who worries about 1MB these days? We already have all the infrastructure in Wine in place to simply drop these in windows\fonts; it's a simple solution and it'll work in every case. While maybe Alexandre doesn't want to include them in the git repository simply for maintenance reasons, I think packagers should include them directly with their Wine package and install in windows\fonts.
-Brian -Brian
On Friday 15 June 2007 18:23:51 Brian Vincent wrote:
While this strikes me as 100% a packaging issue, it just seems like something really prone to error. When the new Foo distro comes out and decides to place their fonts in /opt/Foo/X they'll need to figure out how to make the sym links, but then maybe they won't include these fonts, so the package maintainer will have to make another package and ship it alongside Wine. That'll work great until Wine gets ported some other OS that doesn't include the fonts, then that maintainer will have to deal with some odd scheme.
In my scenario the symlinks point to files that the Wine packager knows where they are because he put them there.
Say we have a wine-fonts subpackage that holds the modified versions of the liberation fonts and the install prefix is /usr/local. Then we know that Wine's fonts will be in /usr/local/share/wine/fonts and so wineprefixcreate would create a link like this:
~/.wine/drive_c/windows/fonts/arial.ttf -> /usr/local/share/wine/fonts/arial.ttf
-Hans
-
Brian Vincent -
Dmitry Timoshkov -
Hans Leidekker -
Louis Lenders -
Louis. Lenders
-
Michael Stefaniuc -
Steve Brown