- Wine-Devel - list.winehq.org

replacements for DAO/MSHTML/MSXML
by juergen.schmied＠debitel.net June 16, 2002

June 16, 2002

Hi! I'm currently looking for a replacement of this components to port a application to linux. Has anybody already had this problems and how did you solve it? How big are the nessesary changes? Are there components usable for both operating systems with similar functions? ------ PS: I found the Mozilla Active X control at http://www.iol.ie/~locka/mozilla/mozilla.htm it should be binary compatible. Couldn't we use it for implementing shdocvw ??? ------ Thanks Juergen

2 1

Mingw Wine port bug
by Steven Edwards June 15, 2002

June 15, 2002

I'm getting multiple definintion errors when building certain parts of wine under mingw. Anyone have a idea for the solution? Building Comdlg32.dll - ../../ole/libwine_uuid.a(uuid.o)(.text+0x9c0):uuid.c: multiple definition of `CL SID_ShellDesktop' D:/mingw/bin/../lib/gcc-lib/mingw32/2.95.3-7/../../../libshell32.a(shell32.o)(.t ext+0x0)://d/src/mingw/w32api/lib/shell32.c: first defined here ../../ole/libwine_uuid.a(uuid.o)(.text+0x9d0):uuid.c: multiple definition of `CL SID_ShellLink' D:/mingw/bin/../lib/gcc-lib/mingw32/2.95.3-7/../../../libshell32.a(shell32.o)(.t ext+0x10)://d/src/mingw/w32api/lib/shell32.c: first defined here ../../ole/libwine_uuid.a(uuid.o)(.text+0xa30):uuid.c: multiple definition of `FM TID_Intshcut' D:/mingw/bin/../lib/gcc-lib/mingw32/2.95.3-7/../../../libshell32.a(shell32.o)(.t ext+0x20)://d/src/mingw/w32api/lib/shell32.c: first defined here ../../ole/libwine_uuid.a(uuid.o)(.text+0xa40):uuid.c: multiple definition of `FM TID_InternetSite' D:/mingw/bin/../lib/gcc-lib/mingw32/2.95.3-7/../../../libshell32.a(shell32.o)(.t ext+0x30)://d/src/mingw/w32api/lib/shell32.c: first defined here ../../ole/libwine_uuid.a(uuid.o)(.text+0xa50):uuid.c: multiple definition of `CG ID_Explorer' D:/mingw/bin/../lib/gcc-lib/mingw32/2.95.3-7/../../../libshell32.a(shell32.o)(.t ext+0x40)://d/src/mingw/w32api/lib/shell32.c: first defined here ../../ole/libwine_uuid.a(uuid.o)(.text+0xa60):uuid.c: multiple definition of `CG ID_ShellDocView' D:/mingw/bin/../lib/gcc-lib/mingw32/2.95.3-7/../../../libshell32.a(shell32.o)(.t ext+0x50)://d/src/mingw/w32api/lib/shell32.c: first defined here ../../ole/libwine_uuid.a(uuid.o)(.text+0xa90):uuid.c: multiple definition of `II D_INewShortcutHookA' __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com

2 2

arts driver problems
by Rizsanyi Zsolt June 15, 2002

June 15, 2002

Hi! I'm trying to set up wine to use arts for audio output. So I have uncommented from the config file the "Drivers" = "winearts.drv" line. But when an application tries to open the sound device, it hangs. I have put various trace messages in the winearts driver, and seen that when wine calls arts_init that function never returns. It's not an arts configuration problem because MPlayer runs perfectly with the arts audio output. But I have checked the source of MPlayer, and the arts code there seems basically the same. Have anybody experienced something like this? Or has any idea about this? Thanks Zsolt Rizsanyi

2 1

Re: Old unicode standard
by David.Goodenough＠DGA.co.uk June 15, 2002

June 15, 2002

Well volume 1 of the 1.0 version has an entire appendix, 11 pages in all. Volume 2 of 1.0 does not seem to have anything on directionality (as 1.0 names it). 2.0 has 10 pages at the end of chapter 3 on Bi-Directional behavior. Typing all this lot up could take a while, and our scanner is broken at the moment (its my wife's, and I must encourage her to go get it fixed as its warrantee will run out soon if she does not get a move on). David Shachar Shemesh <wine-devel(a)sun.consum To: andi(a)rhlx01.fht-esslingen.de, David.Goodenough(a)dga.co.uk er.org.il> cc: Wine Devel <wine-devel(a)winehq.com> Subject: Re: Old unicode standard 06/15/02 10:35 AM Andreas Mohr wrote: >Hmm, which approximate time frame is this ? >1998 ? 94 ? 89 ? :-) > > > I'm talking about the 1991-2 time frame. I believe this makes it ~Unicode 1.0. A later version could come in handy as well. See later on. David.Goodenough(a)dga.co.uk wrote: >Shachar, > >I have the version 1.0 and 2.0 books, what exactly do you want to know? In >wha?t form would you like the information > >David > > I am interested in the BiDi algorythm as defined by these standards. Any format that you can send me is fine. If you would just like to summarize the algorythm, that would be great, but I'm afraid that would amount to huge amounts of work. LIke I said - I would have used the online library, only it doesn't go back that much. It seems from the information MS released in the MSDN that they are using Version 1.0 of the BiDi algorythm. This goes a great way in understanding why their reordering is so crummy. That leaves us the question of what do we do now. MS defines only 12 BiDi types. These are not enough to implement the 3.0 BiDi algorythm. I don't know whether the types defined are compatible with the 2.0 algorythm. There is also the question of whether we want to support MS's bugs, in addition to their features. What version I need depends on what's in the 2.0 standard. If the algorythm there depends on the same 12 types MS defined, I'm leaning torwards implementing that. If it requires further types (as the 3.0 algorythm does), I think I'll go with the 1.0 standard. We may add a special command line feature, available only if a library such as freebidi is available, that will send the strings to an outside library for reordering, which will give us 3.0 support for very little extra work (with performance penalties). Shachar

1 0

WM_GETTEXTLENGTH returns double size
by Andriy Palamarchuk June 15, 2002

June 15, 2002

This happens in code which unmaps message, mapped from ASCII to Unicode. See windows/winproc.c, function WINPROC_UnmapMsg32ATo32W: case WM_GETTEXTLENGTH: case CB_GETLBTEXTLEN: case LB_GETTEXTLEN: /* there may be one DBCS char for each Unicode char */ return result * 2; What is the correct way to handle double-byte characters in this situation? How Windows handles this? At least can we return double values when system metrics SM_DBCSENABLED is true? We could have a switch in the config file for this system metrics. I came across this issue when used default combo box control implementation in Delphi 6. I assume the same issue also exists for edit controls. The returned length is correct if I comment out the code above. Existing behavior is a possible cause of bug in entering serial numbers - when cursor jumps to the next edit field when only half of text is entered. Thanks, Andriy __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com

3 18

Old unicode standard
by Shachar Shemesh June 15, 2002

June 15, 2002

Hi all, I am trying to find any references to the old unicode standard. In particular, I need the Bidirectional algorythm used with ~unicode 1.0. If anyone can help, it would be greatly apretiated. If you don't have the 1.0 standard, but do have a later standard (but not 3.0, which is what is available on the unicode web site), that would probably be a great help too. Shachar

3 3

please report this (quicken error)
by Shane Shields June 15, 2002

June 15, 2002

hi all ive been lurking for a while and reading some very lively discussions but thats off topic. the reason ive come out of my hole is the following messages. just being a good (?) citizen. let me know what other information you need and how i can collect it. regards shane locutus:/mnt/hdc/c/QUICKENW$ wine qw fixme:keyboard:X11DRV_KEYBOARD_DetectLayout Your keyboard layout was not found! Using closest match instead (Turkish keyboard layout) for scancode mapping. Please define your layout in windows/x11drv/keyboard.c and submit them to us for inclusion into future Wine releases. See the Wine User Guide, chapter "Keyboard" for more information. err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this. err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this. err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this. err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this. err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this. err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this. err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this. err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this. err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this. err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this. err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this. err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this. err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this. err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this. err:win:WinHelpA can't start winhlp32.exe -x ? locutus:/mnt/hdc/c/QUICKENW$ -- To drink the WINE of success you must first seek the sayings of source Anyone sending unwanted advertising e-mail to this address will be charged $25 for network traffic and computing time. By extracting my address from this message or its header, you agree to these terms.

1 0

Re: Old unicode standard
by David.Goodenough＠DGA.co.uk June 14, 2002

June 14, 2002

Shachar, I have the version 1.0 and 2.0 books, what exactly do you want to know? In wha?t form would you like the information David Shachar Shemesh <wine-devel(a)sun.consum To: Wine Devel <wine-devel(a)winehq.com> er.org.il> cc: Sent by: Subject: Old unicode standard wine-devel-admin(a)wineh q.com 06/14/02 01:04 PM Hi all, I am trying to find any references to the old unicode standard. In particular, I need the Bidirectional algorythm used with ~unicode 1.0. If anyone can help, it would be greatly apretiated. If you don't have the 1.0 standard, but do have a later standard (but not 3.0, which is what is available on the unicode web site), that would probably be a great help too. Shachar

1 0

Taking a step back :(
by Dustin Navea June 14, 2002

June 14, 2002

sigh, hey guys i have some bad news, but no too bad... due to me having to work 6 if not 7 days a week now and the school being closed for the summer, i am going to have to take a step back from wine development for a few months... i just don't have the time, energy, or chance to be on the computer (let alone the internet) as much as i used to, and so my inbox is getting packed... but i will be back when 1 of 2 things happens... 1) i get internet at my house (hopefully in the next couple of months) or 2) the school opens again for the fall semester... either way, i will be back though, sorry it has to be like this, but thats the way it goes sometimes.... so, TTFN -Dustin P.S. I will still be monitoring wine-announce and wine-cvs, but im removing myself from devel, bugs, and patches...jeremy, please don't drop my bugzliia priveleges ;) thanks guys... __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com

1 0

Re: PATCH - twain.h
by Francois Gouget June 14, 2002

June 14, 2002

On Fri, 14 Jun 2002, Steven Edwards wrote: > I dont know if this is proper or not but mingw already > defines WIN32 _WIN32 and __declspec(spec) > > Changelog: Fix Warnings > > cvs diff -u twain.h > Index: twain.h > =================================================================== > RCS file: /home/wine/wine/dlls/twain/twain.h,v > retrieving revision 1.3 > diff -u -r1.3 twain.h > --- twain.h 31 May 2002 23:40:53 -0000 1.3 > +++ twain.h 14 Jun 2002 10:42:57 -0000 > @@ -56,9 +56,11 @@ > > #define FAR > #define huge > +#ifndef __MINGW__ > #define WIN32 > #define _WIN32 > #define __declspec(spec) > +#endif I don't think the twain.h header should define any of these macros, including FAR and huge. The main issue is that _WIN32 is normally defined by the compiler. As an alternative we could define it in one of the Wine headers, but why define _WIN32 rather than _WIN64? Maybe we could add the following in basestd.h: #if !defined(_WIN32) && !defined(_WIN64) #define _WIN32 #endif WIN32 is not normally defined by the compiler but it is part of the default set of macros defined my Visual C++ project. So maybe we should add: #ifdef _WIN32 #define WIN32 #endif Does anyone else care to comment on the above? Then * FAR is defined in winnt.h so there is no need to redefine it * __declspec is defined in winnt.h too * huge will not be needed if WIN32 is defined -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Linux: Because rebooting is for adding new hardware

2 1