Dustin Navea wrote:
--- Tony Lambregts <[EMAIL PROTECTED]> wrote: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.
Dustin Navea wrote:There are 2 problems...
--- Francois Gouget <[EMAIL PROTECTED]> wrote: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>
On Thu, 7 Nov 2002, Dustin Navea wrote:Sorry website documenation, i dont know sgml so I am not working on that
Should I email patches to Jeremy, or just update the pages myself andemail
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.
part...
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
--
Tony Lambregts
