November 2002 - Wine-devel - list.winehq.org

something with Chinese character processing
by yf 15 Nov '02

15 Nov '02

I found that to show Chinese character properly. Following should be modified: in wine-2002????/graphics/x11drv/codepage.c static Xchar2b *X11DRV_unicode_to_char2b_cp936(fontObject *pfo, LPCWSTR lpwstr, UINT count) { ... for(i=0; i<count; i++, str_src++, str2b_dsg++) { if(IsLegalDBCSChar_cp936(*str_src, *(str_src+1))) { // modified begin ===> str2b_dst->byte1=*str_src&0x7f; str2b_dst->byte2=*(str_src+1)&0x7f; str_src++; // <=== modified end } else ... } ... } But there still some character can't be properly showed. Where I lost should be modified, please tell me. Best regards. /yf

1 0

Another msvcrt replacement
by Fabian Cenedese 15 Nov '02

15 Nov '02

Hi Looks like wine is not the only one in need of MS replacements. They're only at version 0.0.1 but maybe they have something wine could use or wine sure has something they could use... http://mingwacr.sourceforge.net/ bye Fabi

1 0

Wine Time Line
by Thomas Wickline 15 Nov '02

15 Nov '02

Hi, I have been looking over the FAQ and we have a question in the FAQ " What is the History of Wine" And after talking with Dimi Paun I would like to expand this to a " Wine Time Line" page that could be updated a couple times a year. This would give users info about wine's progression & events that took place over the years. Here is a draft of the first year 1993/1994..... Done by _Robert Amstadt_ -- A discussion began on USENET about the feasibility of running Windows apps on Linux. There were some people that said that it is impossible. This didn't sit well with Robert Amstadt so he began work to prove them wrong. He started out by writing a program loader for Win3.1 apps. Alexandre Julliard merged windowing functions written by Peter MacDonald in Tcl/Tk to the program loader written by Robert. Alexandre soon after rewrote everything to eliminate the Tcl/Tk in favor of direct calls to Xlib. Eric Youngdale also contributed early in many areas including improvements to the program loader. The very first Wine mailing list was operated by Robert to allow discussions between developers. After a year with many successes and growing interest in the project we asked for the creation of the newsgroup comp.emulators.ms-windows.wine. The vote was overwhelmingly in favor of its creation. Around the same time, Robert was asked to give a presentation about Wine at the first Linux Congress in Heidelberg, Germany. The room was packed. Interest in Wine was very high. During the first year of development, most of the code was written by Alexandre Julliard and Robert Amstadt. However, we have always received contributions of code from many people. Life got busy for Robert and he stepped down as head of the project and let Alexandre take control. It was probably sometime during the second year. -- Thoughts, Volinteers, Flames are most welcome.. Thomas

3 2

RE: C++ tests (1/2)
by Patrik Stridvall 15 Nov '02

15 Nov '02

> Patrik Stridvall <ps(a)leissner.se> writes: > > > In the case of generated.c it is very useful since > > alignment and that sort of thing might pontially be different > > with C++. For other normal tests I'm not sure how useful > > it is to tests with C++ as well. It can't hurt of course > > but then it takes twice as long to run... > > I don't see what this buys us at all. If the C++ compiler generates > different structure layouts from the same headers then it is broken, > but that's not really a Wine problem. First of all it was just an example what it could be used for. It is the only thing that winapi_test (tests/generated.c) currently tests for. However, there will be more tests in the future testing for other things that might or might not be C++ dependent. Secondly the test makes certain that you don't have a #ifdef __cplusplus affecting some structure by mistake. And yes, there are structure like that MONITORINFO that does. And no, don't look in the Wine source, it doesn't implement it yet. Then we could have #ifdef __cplusplus that have an "missing" #endif that matches some other #endif in the wrong place or something. We also have the COM interfaces that are different in C++... Then of course we want normal C++ tests as well. Many (most?) applications likely to be ported by Winelib are C++ application so we really should have tests for possible C++ problems. But it you don't like the .c.cxx hack I could generate C++ tests to a generated_cxx.cxx or whatever then we don't need that part of the patch. It is a little ugly I admit. :-)

2 1

Re: C++ tests (1/2)
by Alexandre Julliard 14 Nov '02

14 Nov '02

Patrik Stridvall <ps(a)leissner.se> writes: > In the case of generated.c it is very useful since > alignment and that sort of thing might pontially be different > with C++. For other normal tests I'm not sure how useful > it is to tests with C++ as well. It can't hurt of course > but then it takes twice as long to run... I don't see what this buys us at all. If the C++ compiler generates different structure layouts from the same headers then it is broken, but that's not really a Wine problem. -- Alexandre Julliard julliard(a)winehq.com

1 0

dsl file for sgml faq
by Vincent Béron 14 Nov '02

14 Nov '02

Finally, it's done. In the attached archive you'll find the following files: wine-faq.sgml -> Main sgml file faq-0.sgml \ faq-1.sgml |-> Content sgml files faq-2.sgml / faq.css -> CSS file for the FAQ index.html -> The output of docbook2html -d faq.dsl wine-faq.sgml authors.ent -> same as in documentation/, wasn't needed actually. faq.dsl -> Definition file for docbook. This is where the work went. I modify a few docbook definitions to match Dimitrie's layout. Not obvious without knowing LISP beforehand :) Of course, if somebody chooses another layout, some of this will need adjustment. Or if we prefer something closer to "vanilla" docbook. Dimitrie, the actual HTML code is rather ugly in it's source presentation, so don't hand-edit it :P Anyway, it's not meant to be hand-edited, that's what sgml and docbook are for. The layout is exactly what you already have, although with some small modifications to the layout the dsl file can be alot simpler. Tony, you can begin the transition if Dimitrie likes it (and when you have the time to). That's all for tonight. Vincent

3 7

Re: ReadFile speedup
by Hannu Kotipalo 14 Nov '02

14 Nov '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hannu Kotipalo kirjoitti Sunnuntai 10. Marraskuuta 2002 14:49: > are speeded up a lot. For example, wzebra opening database readout : > > Before : over 700 seconds > After : 12-13 seconds > A new version, replacing the earlier. I tested this with a few applications, looks like for most of applications this has not much effect. However, wzebra proves that the effect can be enourmous on some. (And Simcity tellls that it can be negative on some applications :-( Changelog: - - This patch speeds up applications reading files by small packets - - 4 static 512 byte buffers (can be defined for n * n buffers, see file.c) - - Buffer invalidation mechanism changed. With several buffers this *should* fix the reported (thans to Tony Lambregts) slowdown on SIMCITY2000. I haven't got it, cannot test. Please test and see -debugmsg +file, it can give a hint about needed buffers and their sizes. diff is made by 'diff -urN wine-20021031/ wine-20021031-patched/ > patch.diff' Hannu -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE90XAUuA3ghgc3fUsRAuk7AKDwLK/E4WzkCHMf0j615aktFuiWEgCgt0xq FLujbIUEEASUu9K51siPOwA= =RxKU -----END PGP SIGNATURE-----

3 4

Re: dsl file for sgml faq
by Tony Lambregts 14 Nov '02

14 Nov '02

Vincent Béron wrote: > Tony Lambregts a écrit: > >> Vincent Béron wrote: >> >>> Tony Lambregts a écrit: >>> >>>> I have been fighting with trying to get your sample built on my >>>> system. The end point for me seems to be that in order to use your >>>> faq.dsl I need docbook DTD 4.2. RedHat 7.2 has Docbook 3.0 through >>>> 4.1 but 4.1 just does not cut it. >>>> >>>> jade:../faq.dsl:50:24:E: reference to undefined variable >>>> "$generate-article-lot-list$" >>>> >>>> The sgml tools site has only 3.0/2 >>>> >>>> So I feel very THICK and ned some enlightenment on what direction >>>> to take either. >>>> >>>> 1) It seems pointless to rely on something (docBook 4.2 DTD) that >>>> is difficult to get, so no one will use it so, no one will maintain >>>> the FAQ. >>> >>> >>> >>> >>> Silly me, not thinking about others. It runs fine with docbook 3.1 >>> (modify the doctype at top of wine-faq.sgml) if you remove the >>> articleinfo pair (but you can keep the title). >>> >>>> >>>> 2) I am THICK and I it will be quickly apparent what I should do >>>> once I have more informatioin. >>>> >>> >>> You're NOT thick! It's just that I do things here (on my machine), >>> and I don't always check if it would work on other machines. >>> >>> Vincent >>> >> When I made the suggested changes I still get the same error... >> >> [tony(a)tony documentation]$ db2html -d ../faq.dsl wine-faq.sgml >> output is wine-faq >> Using catalogs: /etc/sgml/sgml-docbook-3.1.cat >> Using stylesheet: ../faq.dsl >> Working on: /usr/local/src/wine/documentation/wine-faq.sgml >> jade:../faq.dsl:50:24:E: reference to undefined variable >> "$generate-article-lot-list$" > > > Ok, it's the definition of the article element which causes problems. > > What is your dsssl-stylesheets version? You can locate db31.dsl and > look in the parents directory name. dsssl-stylesheets-1.64 > > > I needed to copy some definitions (bad thing to do, as your > experiencing shows) to precisely control the HTML layout. > > Try with the enclosed dsl file (warning: endlines are probably MS), > and compare the differences (if it works ;-)). Then tell me which > differences you absolutely need, or want, and I'll try to get them in > a portable way. > > Vincent I had to modify the faq-plain.dsl a little to get output >------------------------------------------------------------------------ > ><!DOCTYPE style-sheet PUBLIC "-//James Clark//DTD DSSSL Style Sheet//EN" [ ><!ENTITY walsh-style PUBLIC "-//Norman Walsh//DOCUMENT DocBook HTML Stylesheet// ><!ENTITY cygnus-style SYSTEM "/usr/lib/sgml/stylesheet/dsssl/docbook/cygnus/cygn >]> > > <!DOCTYPE style-sheet PUBLIC "-//James Clark//DTD DSSSL Style Sheet//EN" [ <!ENTITY walsh-style PUBLIC "-//Norman Walsh//DOCUMENT DocBook HTML Stylesheet//EN" CDATA DSSSL> <!ENTITY cygnus-style SYSTEM "/usr/lib/sgml/stylesheet/dsssl/docbook/cygnus/cygnus-both.dsl" CDATA DSSSL> ]> ><style-sheet> ><style-specification id="html" use="docbook"> ><style-specification-body> > >(define %html-pubid% "-//W3C//DTD HTML 4.01 Transitional//EN") >(define %html-header-tags% '(("META" ("HTTP-EQUIV" "Content-Type") ("CONTENT" "t > (define %html-header-tags% '(("META" ("HTTP-EQUIV" "Content-Type") ("CONTENT" "text/html; charset=ISO-8859-1")))) >(define %use-id-as-filename% #t) >(define %html-ext% ".html") > >(define %stylesheet% "faq.css") >(define %stylesheet-type% "text/css") > ></style-specification-body> ></style-specification> > ><external-specification id="docbook" document="walsh-style"> > ></style-sheet> > > With those changes I get output (but not the prety stuff ) <grin> -- Tony Lambregts

1 0

Re: Fw: Re: Filesystem change notifications
by Ian Pilcher 14 Nov '02

14 Nov '02

Shachar Shemesh wrote: > It's not that I am for adding everything inline. That's not a good idea. > Also, I think a Windows compatibility layer can be forgiven for having > more dependancies than a personal finance program. This holds especially > true if non-core windows functionality is only available if the external > library is available at runtime (i.e. - no fribidi install - no Hebrew > support in Wine. No CUPS installed - no printing available etc.). I'm > not sure this holds true to something which is a core Windows function. That would be the plan. No FAM header at compile time, no change notification support (i.e. current behavior); can't load FAM library or connect to FAM daemon at runtime, no change notification support. -- ======================================================================== Ian Pilcher pilchman(a)attbi.com ========================================================================

2 1

Re: Fw: Re: Filesystem change notifications
by Havoc Pennington 14 Nov '02

14 Nov '02

On Thu, Nov 14, 2002 at 07:04:24AM +0000, Keith Matthews wrote: > It sems to have been dropped in RH 7.3 which is a good thing. > No, it's not dropped. > Fam requires portmapper. If not set up properly (i.e. by someone who > understands what they are letting loose) portmapper can be a serious > security problem. The security community regard the introduction of fam > a serious backward step on RH's part. Sounds like someone is misinformed, because we don't have it listening on external ports. That's only required to make it work over NFS or something. Our FAM is a local-only thing unlike on Irix. > You are also assuming that every distro follows RH's lead which is very > definitely not true. Many people are already getting upset about the > number of libraries that are required to get some packages to run. > GNUCash being a prime example of package use gone mad. GNUCash has something like 40 dependencies including a lot of very unstable/unfinished APIs. FAM is 1 dependency and while it sucks, it doesn't change very often (or at all that I know of). Alex Larsson wanted to work on a nicer FAM-type thing based on a per-user daemon or something, but hasn't had time. Certainly there's room to write such a thing, but I don't think it's harmful to use FAM if FAM is present. It's not like a FAM dependency would be pervasive, it would be small and well-isolated and easy to change to some other dependency if you found something better. Havoc

2 1