Folks,
As promised, the new Wine FAQ (in beautiful color, and an amazing bouquet), is ready for public review before the end of the week. So there. :) At the moment, it is available for your viewing pleasure here:
http://www.dssd.ca/Wine-FAQ.html
Keith Matthews, and Thomas Wickline did most of the work on this one; we owe it to them. We've also received a number of useful comments from Jeremy White, thanks Jer!
Please direct all comments, suggestion, and (last, but not least) flames, to the brand new wine-faq@winehq.org. All are most appreciated.
Hopefully we'll have this one on the site not before long.
Dimitrie O. Paun wrote:
Folks,
As promised, the new Wine FAQ (in beautiful color, and an amazing bouquet), is ready for public review before the end of the week. So there. :) At the moment, it is available for your viewing pleasure here:
http://www.dssd.ca/Wine-FAQ.html
Keith Matthews, and Thomas Wickline did most of the work on this one; we owe it to them. We've also received a number of useful comments from Jeremy White, thanks Jer!
Please direct all comments, suggestion, and (last, but not least) flames, to the brand new wine-faq@winehq.org. All are most appreciated.
Hopefully we'll have this one on the site not before long.
Is this already in sgml?
On November 9, 2002 10:01 pm, Tony Lambregts wrote:
Is this already in sgml?
No, it's not. We will worry about that at a later time, now the priority is to get this out the door.
On November 10, 2002 10:49 am, Tony Lambregts wrote:
OK, Once it is finalized... It's on my TODO list.
That's cool. I can help you with that, it is written so that we can easily convert it into SGML. But to make that step, we have to be able to convince the SGML tools to generate the HTML that _we_ want. I will personally oppose such a conversion until we know how to control the tools. So if you want that to happen, find a way to get the right HTML out of docbook, and we'll convert the whole thing in no time.
Dimitrie O. Paun wrote:
On November 10, 2002 10:49 am, Tony Lambregts wrote:
OK, Once it is finalized... It's on my TODO list.
That's cool. I can help you with that, it is written so that we can easily convert it into SGML. But to make that step, we have to be able to convince the SGML tools to generate the HTML that _we_ want. I will personally oppose such a conversion until we know how to control the tools. So if you want that to happen, find a way to get the right HTML out of docbook, and we'll convert the whole thing in no time.
Is there anyone out there that has a clue how to do this... Its a fix me in the documentation
<sect3 id="docbook-tweaking"> <title>Tweaking the DSSSL stylesheets</title> <para> Things you can tweak, and how to do it (examples from default.dsl and winehq.dsl). </para> </sect3>
Le dim 10/11/2002 à 12:20, Tony Lambregts a écrit :
Dimitrie O. Paun wrote:
That's cool. I can help you with that, it is written so that we can easily convert it into SGML. But to make that step, we have to be able to convince the SGML tools to generate the HTML that _we_ want. I will personally oppose such a conversion until we know how to control the tools. So if you want that to happen, find a way to get the right HTML out of docbook, and we'll convert the whole thing in no time.
Is there anyone out there that has a clue how to do this... Its a fix me in the documentation
<sect3 id="docbook-tweaking"> <title>Tweaking the DSSSL stylesheets</title> <para> Things you can tweak, and how to do it (examples from default.dsl and winehq.dsl). </para> </sect3>
Probably www.docbook.org has some info, and examples too :)
Vincent
Le dim 10/11/2002 à 11:59, Dimitrie O. Paun a écrit :
On November 10, 2002 10:49 am, Tony Lambregts wrote:
OK, Once it is finalized... It's on my TODO list.
That's cool. I can help you with that, it is written so that we can easily convert it into SGML. But to make that step, we have to be able to convince the SGML tools to generate the HTML that _we_ want. I will personally oppose such a conversion until we know how to control the tools. So if you want that to happen, find a way to get the right HTML out of docbook, and we'll convert the whole thing in no time.
I hope the HTML you want to generate will pass the W3C validator, because the current FAQ doesn't.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.dssd.ca%2FWine-FAQ.html&a...
Yes, I'm feeling like nitpicking :) And no, I haven't checked if the html that we already generate do validate. But yes, I'll check.
And I'll take a (small) look at the dsl thing.
Vincent
On 10 Nov 2002, Vincent Béron wrote: [...]
I hope the HTML you want to generate will pass the W3C validator, because the current FAQ doesn't.
I really wouldn't worry about that. I think that the way to go really is to use DocBook (documentation/faq.sgml) so the final html code will be different anyway.
Le dim 10/11/2002 à 18:43, Francois Gouget a écrit :
On 10 Nov 2002, Vincent Béron wrote: [...]
I hope the HTML you want to generate will pass the W3C validator, because the current FAQ doesn't.
I really wouldn't worry about that. I think that the way to go really is to use DocBook (documentation/faq.sgml) so the final html code will be different anyway.
Yes, of course. I did say I was nitpiking :)
I'm currently building a dsl file for the faq, on the basis of the layout of the FAQ Dimitrie put online a few days ago.
BTW, anybody knows LISP around here? The dsl files are coded in it, and I could use some help for a few points (like code formatting).
Expect a first draft (consisting of a few questions only) later tonight. My goal is only to provide a working dsl, not convert the whole FAQ, so that others can do the conversion.
Vincent
As promised, the new Wine FAQ (in beautiful color, and an amazing bouquet), is ready for public review before the end of the week. So there. :) At the moment, it is available for your viewing pleasure here:
1/ rewind & winex descriptions have been interverted 2/ i get (on netscape) some ugly font changes between paragraphs (in some cases bold 14, in other normal 10: is this intentional ?) (I'm not speaking about paragraph title but paragraph body) 3/ helping wine: we could add a paragraph about writting test cases for a given (set of) API
On November 10, 2002 04:02 am, Eric Pouech wrote:
1/ rewind & winex descriptions have been interverted
<blush>Fixed.</blush>
2/ i get (on netscape) some ugly font changes between paragraphs (in some cases bold 14, in other normal 10: is this intentional ?) (I'm not speaking about paragraph title but paragraph body)
No, it is not. I don't get that in Galeon, or Konqy. Where do you see the problems? ...starting up Netscape... Oh my God! Netscape renders this too bad for word! It's terrible, please use Mozilla/Konqy for the moment, until we figure out how to fix it for Netscape. This is strange, we use very simple HTML...
3/ helping wine: we could add a paragraph about writting test cases for a given (set of) API
Will do.
On November 10, 2002 04:02 am, Eric Pouech wrote:
3/ helping wine: we could add a paragraph about writting test cases for a given (set of) API
Well, not that I read what's in there:
You can contribute programming or documentation skills, or monetary or equipment donations, to aid the Wine developers in reaching their goals.
Writing tests is "programming", so to add it in there, we would have to restate the whole thing.
The simplest thing is to just point them to the Wine Contribution Page, which lists all these, and more. Which is what I've done. Is this OK?
At the moment, it is available for your viewing pleasure here:
http://www.dssd.ca/Wine-FAQ.html
From the FAQ: --- Will MFC work with Wine? What do I need to do?
Work is underway to support this. In fact a libmfc42.so has already been written. You can expect a working MFC porting system relatively soon. ---
What is the status of this libmfc? It's not mentioned in the status page http://www.winehq.com/about/index.php?status
Thanks
bye Fabi
On Mon, 11 Nov 2002, Fabian Cenedese wrote:
At the moment, it is available for your viewing pleasure here:
http://www.dssd.ca/Wine-FAQ.htmlFrom the FAQ:
Will MFC work with Wine? What do I need to do?
Work is underway to support this. In fact a libmfc42.so has already been written. You can expect a working MFC porting system relatively soon.
What is the status of this libmfc? It's not mentioned in the status page http://www.winehq.com/about/index.php?status
That FAQ is incorrect or at least misleading. Wine is not implementing an MFC replacement nor does it intend to. Thus libmfc is not mentioned in the status page. However it is possible (with a lot of work) to compile the MFC from source and thus produce an mfc42.dll.so library.
How to do it is (meant to be) described in the Winelib guide. Well, there are some intructions already though they are incomplete and/or outdated.
-
Dimitrie O. Paun -
Eric Pouech -
Fabian Cenedese -
Francois Gouget -
Tony Lambregts -
Vincent Béron