April 2001 - Wine-Devel - list.winehq.org

TrueType font metrics for PostScript driver

by Ian Pilcher

And the verdict is . . . Everyone seems to feel that using FreeType 2.x directly from the Post- Script driver is the right thing to do, so that's what I'll do. This does mean that I'm going to have to learn autoconf, so expect some stupid questions on that subject. -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================

April 30, 2001

Re: msvcrt error

by Francois Gouget

On Mon, 30 Apr 2001, Chris Morgan wrote: > I'm getting this error: > > Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: > err:win32:PE_FindExportedFunction function not found for forward > 'ntdll._iswctype' used by 'msvcrt.dll'. If you are using builtin > 'msvcrt.dll', try using the native one instead. > err:win32:fixup_imports No implementation for MSVCRT.dll.636(iswctype) > imported from C:\program files\notepad.exe, setting to 0xdeadbeef > ~/program files$ > > when running notepad.exe using builtin msvcrt.dll. Any ideas on what might > be causing this? There's no '_' in the function name in ntdll. The attached patch should fix this. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Good judgment comes from experience, and experience comes from bad judgment -- Barry LePatner

April 30, 2001

msvcrt error

by Chris Morgan

I'm getting this error: Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: err:win32:PE_FindExportedFunction function not found for forward 'ntdll._iswctype' used by 'msvcrt.dll'. If you are using builtin 'msvcrt.dll', try using the native one instead. err:win32:fixup_imports No implementation for MSVCRT.dll.636(iswctype) imported from C:\program files\notepad.exe, setting to 0xdeadbeef ~/program files$ when running notepad.exe using builtin msvcrt.dll. Any ideas on what might be causing this? Thanks, Chris

April 30, 2001

Re: TrueType font metrics for PostScript driver

by Alexandre Julliard

Ian Pilcher <ian.pilcher(a)home.com> writes: > With a separate program, FreeType is only required for people who want > to print TrueType fonts. If I put FreeType calls directly into the > driver, FreeType will be required to build/run Wine at all, even for > users that derive no benefit from it. You can have an autoconf check and #ifdef the code out if possible. We will have to use FreeType at some point anyway, so we might as well start now. Besides it seems it will be easier to use if everything is built-in instead of having to run a separate tool. -- Alexandre Julliard julliard(a)winehq.com

April 30, 2001

Re: TrueType font metrics for PostScript driver

by Bernhard Rosenkraenzer

On Mon, 30 Apr 2001, Ian Pilcher wrote: > There is also the issue of FreeType version compatibility. Red Hat 7.0 > ships with FreeType version 1.something, while Red Hat 7.1 ships Free- > Type 2.0.1. (I'm just using Red Hat as an example to point out that > multiple versions are commonly being used out there.) The "mkttfm" > program that I wrote on RH 7.0 does build and run on RH 7.1, but the > FreeType web site does indicate that this compatibility is being phased > out. It's already gone. The reason old stuff still works on RH 7.1 is that we're actually shipping both 1.4.2 and 2.0.1 in the same package. 1.4.2 and 2.0.1 have very little in common except for providing the same functionality. > A decision on which version of the FreeType API would be required. 2.x definitely. They didn't redesign the API for no reason. LLaP bero

April 30, 2001

Re: TrueType font metrics for PostScript driver

by Ian Pilcher

Alexandre Julliard wrote: > > But doesn't your solution also require FreeType anyway? Linking it > into Wine or into a separate program is not really different for the > user, he still needs to install it. > With a separate program, FreeType is only required for people who want to print TrueType fonts. If I put FreeType calls directly into the driver, FreeType will be required to build/run Wine at all, even for users that derive no benefit from it. The other issue is more architectural. I agree with Gavriel that the ultimate solution is a consolidated font handling layer that supports both on-screen rendering and printing. If we accept that, anything I do now will be an interim solution. It makes more sense to me to simply tweak the existing AFM parsing code, rather than adding a bunch of Free- Type calls that will eventually get ripped out anyway. There is also the issue of FreeType version compatibility. Red Hat 7.0 ships with FreeType version 1.something, while Red Hat 7.1 ships Free- Type 2.0.1. (I'm just using Red Hat as an example to point out that multiple versions are commonly being used out there.) The "mkttfm" program that I wrote on RH 7.0 does build and run on RH 7.1, but the FreeType web site does indicate that this compatibility is being phased out. A decision on which version of the FreeType API would be required. If, however, you feel that making the FreeType calls directly from the PostScript driver is a better interim solution, I'm perfectly willing to do that. The amount of work is not significantly different. Let me know what you think. -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================

April 30, 2001

Re: TrueType font metrics for PostScript driver

by Marcus Meissner

On Mon, Apr 30, 2001 at 02:03:48PM -0500, Ian Pilcher wrote: > Alexandre Julliard wrote: > > > > But doesn't your solution also require FreeType anyway? Linking it > > into Wine or into a separate program is not really different for the > > user, he still needs to install it. > > > > With a separate program, FreeType is only required for people who want > to print TrueType fonts. If I put FreeType calls directly into the > driver, FreeType will be required to build/run Wine at all, even for > users that derive no benefit from it. Umm, use autoconf checks and fall back methods, also for ft1 vs ft2 checks. Ciao, Marcus

April 30, 2001

Re: TrueType font metrics for PostScript driver

by Alexandre Julliard

Ian Pilcher <ian.pilcher(a)home.com> writes: > Absolutely nothing. I just don't think the immediate benefit of getting > at TrueType encodings justifies creating the dependency at this time. But doesn't your solution also require FreeType anyway? Linking it into Wine or into a separate program is not really different for the user, he still needs to install it. -- Alexandre Julliard julliard(a)winehq.com

April 30, 2001

Re: STATUS_* codes

by Dmitry Timoshkov

"David Howells" <dhowells(a)cambridge.redhat.com> wrote: > Can someone pin numbers on the following codes: > > STATUS_FILE_IS_A_DIRECTORY > STATUS_INVALID_EXECUTABLE_IMAGE > > At least I think that's what they're called (unfortunately, my book's at home > where I can't check it). > > They're listed in my NT native API book (though that's no guarantee that they > exist), but not in the Wine header files, and I don't have a copy of the DDK > installed on top of MSDEV. nt4 ddk has only one of them: #define STATUS_FILE_IS_A_DIRECTORY ((NTSTATUS)0xC00000BAL) perhaps STATUS_INVALID_EXECUTABLE_IMAGE is defined in the win2000 ddk? neither win98 ddk, nor platform sdk july 2000 edition have them.

April 30, 2001

Re: STATUS_* codes

by Ian Pilcher

David Howells wrote: > > Can someone pin numbers on the following codes: > > STATUS_FILE_IS_A_DIRECTORY > STATUS_INVALID_EXECUTABLE_IMAGE > > At least I think that's what they're called (unfortunately, my book's at home > where I can't check it). > > They're listed in my NT native API book (though that's no guarantee that they > exist), but not in the Wine header files, and I don't have a copy of the DDK > installed on top of MSDEV. > They're not defined in the MS SDK header files either. -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================

April 30, 2001