Should I email patches to Jeremy, or just update the pages myself and email those to Jeremy or Alexandre?
-Dustin
__________________________________________________ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2
On Thu, 7 Nov 2002, Dustin Navea wrote:
Should I email patches to Jeremy, or just update the pages myself and email those to Jeremy or Alexandre?
If 'Docu updates' refers to the Wine SGML documentation, then the right thing to do is to post the relevant patch to wine-patches. Then they should be picked up and web site updated automatically when Alexandre commits them.
--- Francois Gouget fgouget@free.fr wrote:
On Thu, 7 Nov 2002, Dustin Navea wrote:
Should I email patches to Jeremy, or just update the pages myself and
those to Jeremy or Alexandre?
If 'Docu updates' refers to the Wine SGML documentation, then the right thing to do is to post the relevant patch to wine-patches. Then they should be picked up and web site updated automatically when Alexandre commits them.
Sorry website documenation, i dont know sgml so I am not working on that part...
-Dustin
__________________________________________________ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2
Dustin Navea wrote:
--- Francois Gouget fgouget@free.fr wrote:
On Thu, 7 Nov 2002, Dustin Navea wrote:
Should I email patches to Jeremy, or just update the pages myself and
those to Jeremy or Alexandre?
If 'Docu updates' refers to the Wine SGML documentation, then the right thing to do is to post the relevant patch to wine-patches. Then they should be picked up and web site updated automatically when Alexandre commits them.
Sorry website documenation, i dont know sgml so I am not working on that part...
The wine website's Users Guide, Developers Guide, Packagers Guide, and Winelib Users guide are created from the sgml in CVS, sgml allows use to produce PS and PDF versions of these Guides as well, So you should not modify the html for the online documentation but rather the SGML. SGML (docbook) can be modified in vim or emacs or if your like me and don't mind the tags your favorite text editor. <g>
--
Tony Lambregts
--- Tony Lambregts tony_lambregts@telusplanet.net wrote:
Dustin Navea wrote:
--- Francois Gouget fgouget@free.fr wrote:
On Thu, 7 Nov 2002, Dustin Navea wrote:
Should I email patches to Jeremy, or just update the pages myself and
those to Jeremy or Alexandre?
If 'Docu updates' refers to the Wine SGML documentation, then the right thing to do is to post the relevant patch to wine-patches. Then they should be picked up and web site updated automatically when Alexandre commits them.
Sorry website documenation, i dont know sgml so I am not working on that part...
The wine website's Users Guide, Developers Guide, Packagers Guide, and Winelib Users guide are created from the sgml in CVS, sgml allows use to produce PS and PDF versions of these Guides as well, So you should not modify the html for the online documentation but rather the SGML. SGML (docbook) can be modified in vim or emacs or if your like me and don't mind the tags your favorite text editor. <g>
There are 2 problems...
1) I dont know any sgml (unless vim/emacs hides the tags or makes it look kinda like html) 2) The wine guides as they are are so confusing to me on how to recreate winehq that I cant even get make_winehq to work... That may just be something I'm doing... Could someone explain to me how to get the docs "compiled" so I can see them as they should look?
-Dustin
__________________________________________________ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2
Dustin Navea wrote:
--- Tony Lambregts tony_lambregts@telusplanet.net wrote:
Dustin Navea wrote:
--- Francois Gouget fgouget@free.fr wrote:
On Thu, 7 Nov 2002, Dustin Navea wrote:
Should I email patches to Jeremy, or just update the pages myself and
those to Jeremy or Alexandre?
If 'Docu updates' refers to the Wine SGML documentation, then the right thing to do is to post the relevant patch to wine-patches. Then they should be picked up and web site updated automatically when Alexandre commits them.
Sorry website documenation, i dont know sgml so I am not working on that part...
The wine website's Users Guide, Developers Guide, Packagers Guide, and Winelib Users guide are created from the sgml in CVS, sgml allows use to produce PS and PDF versions of these Guides as well, So you should not modify the html for the online documentation but rather the SGML. SGML (docbook) can be modified in vim or emacs or if your like me and don't mind the tags your favorite text editor. <g>
There are 2 problems...
- I dont know any sgml (unless vim/emacs hides the tags or makes it look
kinda like html) 2) The wine guides as they are are so confusing to me on how to recreate winehq that I cant even get make_winehq to work... That may just be something I'm doing... Could someone explain to me how to get the docs "compiled" so I can see them as they should look?
-Dustin
Well if you remeber we had this discussion about the same thing in bug 727 http://bugs.winehq.com/show_bug.cgi?id=727 I would really like to be able to build the documentation on my machine as well. So ANYONE that knows how to help us PLEASE speak up.
--
Tony Lambregts
On Thu, Nov 07, 2002 at 10:41:31PM -0700, Tony Lambregts wrote:
Dustin Navea wrote:
There are 2 problems...
- I dont know any sgml (unless vim/emacs hides the tags or makes it look
kinda like html) 2) The wine guides as they are are so confusing to me on how to recreate winehq that I cant even get make_winehq to work... That may just be something I'm doing... Could someone explain to me how to get the docs "compiled" so I can see them as they should look?
-Dustin
Well if you remeber we had this discussion about the same thing in bug 727 http://bugs.winehq.com/show_bug.cgi?id=727 I would really like to be able to build the documentation on my machine as well. So ANYONE that knows how to help us PLEASE speak up.
Oh come on, guys. Is it that difficult to read the README file ? The README file contains countless references to its documentation section, where it says that you're supposed to "make doc" in documentation/.
The documentation compile process does need some fixing, though. A "make doc-html" (make target in toplevel Makefile; so you could assume that *this* builds the docu) craps out with a stupid FIXME: Only NROFF supported make[3]: *** [doc-html] Error 255
- at least for me.
Also, "make doc" doesn't build HTML for me.
On Fri, 8 Nov 2002, Andreas Mohr wrote:
The documentation compile process does need some fixing, though. A "make doc-html" (make target in toplevel Makefile; so you could assume that *this* builds the docu) craps out with a stupid FIXME: Only NROFF supported make[3]: *** [doc-html] Error 255
- at least for me.
Also, "make doc" doesn't build HTML for me.
It's been kinda broken for as long as I can remember, the debian packages have just done this ever since the sgml docs were created:
$(MAKE) -C documentation wine-doc/index.html
and of course it build-depends on docbook-utils (whatever provides db2html and required stylesheets)
Le ven 08/11/2002 à 05:15, Ove Kaaven a écrit :
On Fri, 8 Nov 2002, Andreas Mohr wrote:
The documentation compile process does need some fixing, though. A "make doc-html" (make target in toplevel Makefile; so you could assume that *this* builds the docu) craps out with a stupid FIXME: Only NROFF supported make[3]: *** [doc-html] Error 255
- at least for me.
Also, "make doc" doesn't build HTML for me.
It's been kinda broken for as long as I can remember, the debian packages have just done this ever since the sgml docs were created:
$(MAKE) -C documentation wine-doc/index.html
and of course it build-depends on docbook-utils (whatever provides db2html and required stylesheets)
"$(MAKE) -C documentation everything" for my RH package (so I also have the ps, pdf and man). The html (in directory documentation/wine-doc) does get built, but there's no index.html in sight, only x????.html, c????.html, p????.html and book????.html files, with the ???? being numbers. The closest to a index.html is set1.html, which presents a link to the four guides.
But make_winehq does build it correctly (ie, with sensible names)... I'll check later today the differences between the invocation of both.
Vincent
Dustin Navea wrote:
Should I email patches to Jeremy, or just update the pages myself and email those to Jeremy or Alexandre?
Update the sgml and send the patches (diff -u ) to wine-devel.
--
Tony Lambregts
-
Andreas Mohr -
Dustin Navea -
Francois Gouget -
Ove Kaaven -
Tony Lambregts -
Vincent Béron