Add author list as with the other guides.

documentation/winelib-bindlls.sgml

   <chapter id="bindlls">
-    <title id="bindlls.title">Using Linux libraries as DLLs</title>
+    <!-- FIXME: note that you can link PE DLLs to Winelib apps -->
+    <title id="bindlls.title">Building WineLib DLLs</title>
     <sect1 id="bindlls-intro">
       <title id="binary-dlls-intro.title">Introduction</title>
       <para>
-        For one reason or another you may find yourself with a Linux shared
+        For one reason or another you may find yourself with a Linux
         library that you want to use as if it were a Windows Dll.  There are
         various reasons for this including the following:
         <itemizedlist>
@@ -17,14 +18,14 @@
           <listitem>
             <para>
               There is a well-defined interface available and there are several 
-	      Linux solutions that are available for it. 
-	      (The ODBC interface in Wine)
+	      Linux solutions that are available for it
+	      (e.g. the ODBC interface in Wine).
             </para>
           </listitem>
           <listitem>
             <para>
-              You wish to do something that you can do in Linux but Wine does
-              not yet support it.
+	      You have a binary only Windows application that can be extended 
+	      through plugins, such as a text editor or IDE.
             </para>
           </listitem>
         </itemizedlist>
@@ -184,8 +185,7 @@ signed short WINAPI MyProxyWinFunc (unsigned short a, void *b, void *c,
         is quite long it is extremely simple in structure.
       </para>
       <para>
-        The MAIN_OdbcInit function is the function that was named in the
-        <link linkend="bindlls-spec">spec file</link> as the init function.
+        <function>DllMain</function> the function is used to initialize the DLL.
         On the process attach event the function dynamically links to the
         desired Linux ODBC library (since there are several available) and
         builds a list of function pointers.  It unlinks on the process

documentation/winelib-mfc.sgml

@@ -47,19 +47,12 @@
     <sect1 id="mfc-legal-issues">
       <title id="mfc-legal-issues.title">Legal issues</title>
       <para>
-        (Extracted from the HOWTO-Winelib written by Wilbur Dale
-        &lt;wilbur.dale@lumin.nl&gt;)
-      </para>
-      <para>
         The purpose of this section is to make you aware of potential legal
         problems. Be sure to read your licenses and to consult your lawyers.
         In any case you should not consider the remainder of this section to
         be authoritative since it has not been written by a lawyer.
       </para>
       <para>
-        Well, let's try to have a look at the situation anyway.
-      </para>
-      <para>
         During the compilation of your program, you will be combining code
         from several sources: your code, Winelib code, Microsoft MFC code,
         and possibly code from other vendor sources. As a result, you must

documentation/winelib-porting.sgml

@@ -6,12 +6,11 @@
 
       <para>
 	The <literal>wchar_t</literal> type has different standard
-	sizes in Unix (4 bytes) and Windows (2 bytes). Recent versions
-	of gcc (2.9.7 or later) support the 
+	sizes in Unix (4 bytes) and Windows (2 bytes). You need a
+        recent gcc version (2.9.7 or later) that supports the
 	<parameter>-fshort-wchar</parameter> option to set the
 	size of <literal>wchar_t</literal> to the one expected
-	by Windows applications. Pass this option to every file
-	that is built.
+	by Windows applications. 
       </para>
 
       <para>
@@ -21,26 +20,11 @@
         the msvcrt runtime library instead of glibc. The functions in
         glibc will not work correctly with 16 bit strings.
       </para>
-      <para>
-        To prevent warnings when declaring a single unicode character
-        in C, use <function>(WCHAR)L'x'</function>, rather than
-        <function>__TEXT('x')</function>.  This works on Windows also.
-      </para>
     </sect1>
 
     <sect1 id="C-library">
       <title id="C-library.title">C library</title>
 
-      <!-- *** Is all of this covered now?  Make sure before deleting ***
-      <para>
-        Winelib currently only supports on C library: that of your
-        compiler.  three solutions: native, mixed or msvcrt except we
-        only have native right now, using the native C library ->
-        different behavior: fopen, O_TEXT, unicode support,
-        reimplement msvcrt
-      </para>
-      -->
-
       <para>
         There are 2 choices available to you regarding which C library
         to use: the native glibc C library or the msvcrt C library.

documentation/winelib-user.sgml

@@ -12,6 +12,22 @@
 <book id="index">
   <bookinfo>
     <title>Winelib User's Guide</title>
+    <!-- Until we learn how to format this thing nicely, 
+	 we can't really incude it -->
+    <!--authorgroup>
+      <author>
+	<firstname>Wilbur</firstname>
+	<surname>Dale</surname>
+      </author>
+      <author>
+	<firstname>Francois</firstname>
+	<surname>Gouget</surname>
+      </author>
+      <author>
+	<firstname>John</firstname>
+	<surname>Sheets</surname>
+      </author>
+    <authorgroup-->
   </bookinfo>
 
   &intro;