Jeremy Newman : remove 'site' from docs urls

Jeremy Newman jnewman at
Thu Jan 29 11:01:10 CST 2009

Module: website
Branch: master
Commit: f03734eb58306dbd69a59577ff962af126cb75a7

Author: Jeremy Newman <jnewman at>
Date:   Thu Jan 29 11:00:47 2009 -0600

remove 'site' from docs urls


 templates/en/winelib.template |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/templates/en/winelib.template b/templates/en/winelib.template
index 0d50575..7a8a78f 100644
--- a/templates/en/winelib.template
+++ b/templates/en/winelib.template
@@ -10,7 +10,7 @@
   Theoretically, any Win32 app should be compilable out of the box under Wine.
   This, of course, is not the case. We have incompatible headers, and a bunch
   of other problems described in 
-  <a href="">Winelib User's Guide</a>.
+  <a href="">Winelib User's Guide</a>.
   A good way to fix these is to try to compile applications for which we
   have the source under Winelib. 
@@ -19,7 +19,7 @@
     <li>Document our experience on porting these applications to Winelib
     <li>Improve Winelib based on the above such that the porting process becomes very simple
-    <li>Update the <a href="">Winelib User's Guide</a>
+    <li>Update the <a href="">Winelib User's Guide</a>
         to the latest porting process
     <li>Fixing header &amp; library problems in the process.
@@ -54,7 +54,7 @@
     <dd>For these, <tt>winemaker</tt> does a decent job of generating a build system.
 	I will not cover this type of applications here, for the time being.
         Please refer to the <tt>winemaker</tt> 
-        <a href="">documentation</a>
+        <a href="">documentation</a>
         for more information.</dd>
     <dt>GNU tools based build process</dt>
     <dd>Fortunately, most OSS applications have a build system based around the

More information about the wine-cvs mailing list