wine-devel April 2001

51 participants
93 discussions

Re: InstallShield and ole question...
by juergen.schmied＠debitel.net 01 May '01

01 May '01

> As for doing the 10k+ lines of coding myself, I have experience in > (de)marshalling and network coding, spent many years doing it, it's more a > matter of available time and learning the com wire protocols, neither of which > are currently available to me. Here's to hoping someone is already working on > it ;). For local marshalling we could use our own protocol and even our own way of ipc if we don't try to mix processes with native and wine com-dll's. It com server is only interested in the result ;-). And isn't the com marshalling similar to the dce one? For networking - the dcom protocoll is documented (IMHO). juergen

5 4

Quickbooks 5 and printing
by Sean A. Walberg 01 May '01

01 May '01

After a long break, I'd like to figure out why quickbooks 5 can't print. wineps works, ie I can print in notepad, but QB seems to implement its own printing mechanism. --debugmsg +psdrv,+print,+winspool produces no output. Adding +font spits out a lot, but no errors that I can see. This all used to work until wineps was moved from graphics to a dll about a year ago. I can see from +dosfs that it's accessing some files (WPR.DAT/WPR.INI) which contain information on printers. There is also a QBWPR.DLL file that gets loaded. Any hints on where to start would be appreciated. Thanks, Sean -- Sean A. Walberg <sean(a)ertw.com> http://www.ertw.com *updated!* Join the weekly brainbuzz.com Linux newsletter for news and resources! Send a blank email to: join-linuxnews(a)list.brainbuzz.com

5 8

TrueType font metrics for PostScript driver
by Ian Pilcher 30 Apr '01

30 Apr '01

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 ========================================================================

1 0

msvcrt error
by Chris Morgan 30 Apr '01

30 Apr '01

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

2 1

Re: TrueType font metrics for PostScript driver
by Alexandre Julliard 30 Apr '01

30 Apr '01

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

1 0

Re: TrueType font metrics for PostScript driver
by Alexandre Julliard 30 Apr '01

30 Apr '01

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

3 2

Re: TrueType font metrics for PostScript driver
by Marcus Meissner 30 Apr '01

30 Apr '01

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

1 0

STATUS_* codes
by David Howells 30 Apr '01

30 Apr '01

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

3 2

edit control problem
by Mike McCormack 30 Apr '01

30 Apr '01

Hi, Wine-20010418 seems to have a (serious) problem in the edit control. The problem occurs when i press the backspace key, and there is text after the cursor. (eg. when i am writing a reply to an email on my web-based email). Text following the cursor is not draw correctly... it appears that there are many characters missing at the beginning of the line, but the text is only drawn correctly. Perhaps one of the recent optimizations of the edit control missed something?? i don't know if this is fixed in the latest CVS... but the problem didn't exist in previous wine releases. Mike ------------------------------------------ mailto:[email protected] ph +82 16 430 0425 __________________________________________________________________ Get your own free web email at http://www.looksmart.com.au LookSmart Australia

2 1

TrueType font metrics for PostScript driver
by Ian Pilcher 30 Apr '01

30 Apr '01

In order to Unicode-enable the PostScript driver, it needs information about about font encodings that isn't present in Adobe's AFM file format (glyph names for character encodings greater than 256). For Type 1 fonts with a standard encoding, the driver can use the encoding in the Adobe Glyph List. (There's no other choice.) TrueType font designers, however, seem to regard glyph naming as an opportunity to express their creativity. Besides, the information is present in the TrueType font files, so the driver might as well use it. The driver could read this information directly from the font files, but this would make Wine dependant on the FreeType libraries, and that doesn't strike me as a wonderful idea. Instead, I have cobbled together a small program which reads a TrueType font file and creates a "TrueType Font Metrics" file, which is very similar to an AFM file. (This program does use the FreeType library.) Anyone have any objections to using this approach as a interim measure? -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel April 2001