Wine Traffic #275 For 5/20/2005

I was away on vacation in the past few days which is why this got delayed a bit. But now that I'm back, here's a patch to translate the Wine FAQ to French using the new po4a/ directory. Note that the patch is pretty big : 136KB (not compressed). That's because that how big the FAQ translation is. Once this is in I will send patches to add a translation for the Wine User Guide and the WineLib User Guide.

Note that configure will need to be regenerated.

Changelog:

Francois Gouget <fgouget_at_codeweavers.com>br /> Add a framework to handle the translation of Wine's documentation using po4a.

Romuald VIEUX
Yvon BENOIST
Translate and proof-read the Wine FAQ to French.

OK, I've applied the patch to make your life easier, but it needs a lot of work:

A. It doesn't work for me (details below)

B. The po-rules need to be moved to Make.rules.in

C. We need to get rid of the .posgml and sed hack

Let's fix these before we put in more translations. So, in reverse order:

C. We can do so by patching po4a-translate to do the replacement itself, from within perl. This should also get rid of the .posgml

B. They need to be in the same format as the other rules in Make.rules.in (eg .sgml.txt)

A. I think we need to check in the generated .sgml too to make it simple to use, so others don't have to go through the pain. Look:
[ed note: lots of nasty perl garbage removed]

Status: Nearly complete, need testers.

http://wiki.winehq.org/MSN_Messenger_webcam_support

You need the native quartz dll, which get installed with internet explorer, as the builtin quartz doesn't work properly when changing media format on initialisation. IFilterGraph Reconnect isn't implemented, and for some reason *looks strangely at Robert* instead of a FIXME() there's a TRACE telling it is a stub...

Ok, I need advice on this one...

I have been purely testing on windows, no wine involvement, to see what happens when I do various things.

My test program doesn't do anything in the WM_PAINT handler at all. This results in the machine sitting at 100% CPU processing WM_PAINT messages.

1. Changing the WM_PAINT process to post another user message, results in alternating message posted and WM_PAINT messages, ie normal user message processing is occurring
2. Posting a user message inside the user message handler, results in WM_PAINT being driven, followed by looping processing the user messages - ie WM_PAINT messages are not on the message queue
3. RedrawWindow with update now jumps straight into the message routine with a WM_PAINT, but if we do nothing in that routine, it does indeed proceed to the line after the RedrawWindow call. Wine never leaves the updatenow processing because it loops until the whole region is validated.

I believe staying in the updatenow code in wine is incorrect. I think what happens is that when the message dispatch loop gets an empty queue and the window has an invalid region, then a WM_PAINT is returned.

So... Can we / I please remove the loop? :-))

What other tests can I do under windows to confirm the behaviour?

Woohoo... Should be easy then!

>From forum updates it appears Notes, Unreal2, UT2003, UT2004, Empire Earth and MS Office 2003 for a start are all affected by this problem, and testing seems to confirm its wrong, so I would start by changing it with a patch and see what breaks, since we have no evidence anything will as far as I know.

But first I'll have a play under wine to compare my testing results with my suggested patch and see what breaks...

Unfortunately I cant really think of a 'test' I can add into the wine tests for this as most of the testing was under windows since wine just loops!

They are in the tools/ module in the WineHQ CVS:

http://cvs.winehq.org/cvsweb/tools/

Namely 'make_winehq' and 'wine_release'.

This time, it's how to debug PE Explorer hanging when you double click on a DLL in the file open dialog (fixed in CVS).

http://wiki.winehq.com/Debugging_the_PE_Explorer_file_open_dialog

Newbie developers, I crave your feedback. Are these actually useful or am I wasting my time?

• Embedding a block of code is best done like this:
  {{{
  #!cplusplus
  if (foo)
  {
  
  bar;
  }
  }}}
  This will give it nice syntax highlighting, a monospace font and line numbers.
• Unfortunately StudlyCaps as the Win32 API uses them is the same style that triggers WikiWording. To fix this surround Win32 API names like CreateWindow or IShellLink with backticks: eg `IShellLink`. This will disable WikiWording in that section and also format them with a monospace font.
• If you have a word that it wants to WikiWord, prefix it with a ! mark. Don't do this just because there's no page for it yet, somebody may create one in future. Also don't do it for Win32 API names, use backticks instead. But it can be useful for some things.

Those Wine developers who haven't yet made a todo list, go do it! It's really informative to be able to see what people are working on (not to mention interesting) and this way we can help cut down on duplication of effort.

• if you want to put your email on your page, but are afraid of spam, use the MailTo macro like so: [[MailTo(dimi AT SPAMFREE lattica DOT com)]] This will still show the address properly in the browser, and avoids email harvesting just fine.
• please try to provide a comment when you change a page. It takes very little effort (just a few words will do), and helps a lot when you look at RecentChanges.

I'm glad people like the Wiki. It can become an amazing resource, but only if people contribute and take care of it. I think it's already on it's way of being a great development resource.

If you have any complaints, needs or wants, please don't hesitate to voice them -- I'd be more then happy to address them.