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

Re: wineconf 2002 summary

by michael cardenas

hmm... I guess I can put the photos on my personal web site. Once they're up, I'll let you all know. My photos were pretty lame anyway. If you want to put them up, let me know. On Monday 01 April 2002 07:26, Andreas Mohr wrote: > Hi all, > > I just added a link to my final wineconf 2002 summary page at > http://home.arcor.de/andi.mohr/wine/wineconf2002/ > to the WineHQ News. > > If anyone else has anything to contribute, then feel free to tell me NOW :) > > BTW, Michael, what about your photos ? > Are they supposed to get published somewhere ? > > Thanks for listening ! -- michael cardenas lead windows compatibility engineer www.lindows.com "Be the change you want to see in the world." -Mahatma Ghandi

April 1, 2002

wineconf 2002 summary

by Andreas Mohr

Hi all, I just added a link to my final wineconf 2002 summary page at http://home.arcor.de/andi.mohr/wine/wineconf2002/ to the WineHQ News. If anyone else has anything to contribute, then feel free to tell me NOW :) BTW, Michael, what about your photos ? Are they supposed to get published somewhere ? Thanks for listening ! -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.arcor.de/andi.mohr/

April 1, 2002

Re: error: no implementation for WININET.dll.102(InternetGetConnectedState)

by Jason M Bell

> According to my files WININET.dll.102 is only present on Windows 95 >and should be InternetFindNextFileA How do I fix this in wine? playing with "wine -winver winXX" doesn't help. Is there some other debugging trace I should turn on? thanks, Jason

April 1, 2002

Re: Unicode, i18n support

by Shachar Shemesh

Dmitry Timoshkov wrote: >Probably I didn't make my position clear enough and somehow you >misunderstood me and decided that I propose to use code page 20866 >instead of 1251 for russian locale under Wine. But that's not the case. >I only proposed to create filenames on disk in encoding used natively >in Linux. > Will Windows then be able to read them in Russian? If not, I think having compatibility problems is not worth it.

April 1, 2002

Re: Unicode, i18n support

by Dmitry Timoshkov

"Shachar Shemesh" <wine-devel(a)sun.consumer.org.il> wrote: > >Probably I didn't make my position clear enough and somehow you > >misunderstood me and decided that I propose to use code page 20866 > >instead of 1251 for russian locale under Wine. But that's not the case. > >I only proposed to create filenames on disk in encoding used natively > >in Linux. > > > Will Windows then be able to read them in Russian? Sure, thanks to magic mounting options I mentioned earlier. Native Linux localized applications know nothing about anything other than KOI8-R, and filenames created by them on a vfat partition are readable under Windows just fine. > If not, I think > having compatibility problems is not worth it. Yes, I also think so. -- Dmitry.

April 1, 2002

Re: Unicode, i18n support

by Dmitry Timoshkov

"Shachar Shemesh" <wine-devel(a)sun.consumer.org.il> wrote: > I would particularily recommend against switching WINE to 20866 in light > of the fact that the only text editor I know that supports UNICODE is > Notepad. Most applications are not UNICODE, and running those apps on > WINE would become impossible if WINE did not use the same codepage as > Windows. You don't know how many buggy apps are out there assuming > things they shouldn't about things. Probably I didn't make my position clear enough and somehow you misunderstood me and decided that I propose to use code page 20866 instead of 1251 for russian locale under Wine. But that's not the case. I only proposed to create filenames on disk in encoding used natively in Linux. -- Dmitry.

April 1, 2002

Re: Unicode, i18n support

by Shachar Shemesh

Dmitry Timoshkov wrote: >Filenames, created by windows programs running under Wine, of course are >seen correctly *under Wine*. But regular Linux applications for apparent >reasons display them incorrectly, but still can open them. > >>One more thing I don't understand is this. The filenames are a list of >>bytes. When setting the codepage inside WINE to 1251, does it still not >>see them correctly? >> > >See above. > I think what you have now is the best solution you can opt for. If I understood correctly, WINE uses 1251, but Linux the 20866 (you'll have to excuse me, Russian was, in fact, on my "todo" list to learn, but I never got around to it). The reason I think this is the best move is because this way WINE is compatible with Windows, and creates no more serious compatibility problems with Windows than Windows does. I would particularily recommend against switching WINE to 20866 in light of the fact that the only text editor I know that supports UNICODE is Notepad. Most applications are not UNICODE, and running those apps on WINE would become impossible if WINE did not use the same codepage as Windows. You don't know how many buggy apps are out there assuming things they shouldn't about things. In my history I've had one application that stored binary stuff in the registry under the "string" type. All went well until my program stored that data intermediatly as UNICODE, using a Japanese (MBCS) locale. Some byte combinations produced illegal characters, and were translated back to "?", and the app would break. Moral - if compatibility is what your'e after, be compatible. Don't rely on apps to behave themselves. Shachar

April 1, 2002

Re: make test leaves 2 wine processes running

by Michael Stefaniuc

On Sat, Mar 30, 2002 at 11:58:49PM +0100, Sylvain Petreolle wrote: > Did you set the "Desktop" parameter at any value other > than "N" ? Running it whitout a desktop window gives > no problem. Hmm ... you are right, I never use wine in desktop mode. I can now reproduce your problem. bye michael > Noted another thing : occasionnally the program goes > to debugger and is in X processes. > > > I'm running the same and don't see the problem, no > > wine process is left > > after make test. -- Michael Stefaniuc Tel.: +49-711-96437-199 System Administration Fax.: +49-711-96437-111 Red Hat GmbH Email: mstefani(a)redhat.com Hauptstaetterstr. 58 http://www.redhat.de/ D-70178 Stuttgart

April 1, 2002

Re: Unicode, i18n support

by Dmitry Timoshkov

"Shachar Shemesh" <wine-devel(a)sun.consumer.org.il> wrote: > >One more thing that should be addressed IMO as the part of the unicode > >support in Wine: file APIs. For instance in the current state all russian > >file names created by windows programs are completely unreadable in Linux > >because they are created in code page 1251 but native russian encoding > >in Linux is KOI8-R (code page 20866). Therefore all file APIs should > >work with unicode natively, and convert file names to code page specified > >somewhere in the config file (like [x11drv]/TextCP) on create, and vice versa > >on reading file names from disk. > > > > I don't think this is a WINE issue. Depending on whether you access > those files via a local mount or SMB, the translation between 1251 and > 20866 should be taken care of in the filesystem or via SMB respectively. To make things worse, here is general mount options, used by *all* russian users in the world to be able correctly see cyrillic filenames under Linux from a vfat partition: mount -t vfat -o codepage=866,iocharset=koi8-r. > After all, I don't see any reason that WINE will be able to access these > files, but regular Linux/BSD users won't. Filenames, created by windows programs running under Wine, of course are seen correctly *under Wine*. But regular Linux applications for apparent reasons display them incorrectly, but still can open them. > One more thing I don't understand is this. The filenames are a list of > bytes. When setting the codepage inside WINE to 1251, does it still not > see them correctly? See above. -- Dmitry.

April 1, 2002

Re: error: no implementation for WININET.dll.102(InternetGetConnectedState)

by Francois Gouget

On Mon, 1 Apr 2002, Jason M Bell wrote: > hey everybody, > > I'm trying to debug a windows application - the Paradise Poker client > program. I keep getting an error when it runs: > > -------------- > err:win32:PE_fixup_imports No implementation for WININET.dll.102(InternetGetConnectedState) imported from C:\Program Files\ParadisePoker\client.exe, setting to 0xdeadbeef According to my files WININET.dll.102 is only present on Windows 95 and should be InternetFindNextFileA -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ In theory, theory and practice are the same, but in practice they're different.

April 1, 2002