WineHQ: remove .shtml pages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I think I've sent this one before...

ChangeLog
    Remove .shtml pages, .html will do.

-- 
Dimi.
Index: .htaccess
===================================================================
RCS file: /home/wine/lostwages/.htaccess,v
retrieving revision 1.9
diff -u -r1.9 .htaccess
--- .htaccess	8 Apr 2003 22:13:12 -0000	1.9
+++ .htaccess	26 May 2003 04:17:53 -0000
@@ -62,3 +62,6 @@
 RedirectPermanent /find                         http://source.winehq.org/find
 RedirectPermanent /search                       http://source.winehq.org/search
 RedirectPermanent /diff                         http://source.winehq.org/search
+
+# we no longer use .shtml, redirect to .html
+RedirectMatch ^/(.*)\.shtml(.*)$		http://www.winehq.org/$1.html$2
Index: templates/en/contributing.template
===================================================================
RCS file: /home/wine/lostwages/templates/en/contributing.template,v
retrieving revision 1.6
diff -u -r1.6 contributing.template
--- templates/en/contributing.template	11 Apr 2003 18:40:46 -0000	1.6
+++ templates/en/contributing.template	26 May 2003 04:17:54 -0000
@@ -369,7 +369,7 @@
     <a name="doc"></a>
     <h3>Documentation writing</h3>
     <p>Wine is in constant need of documentation updates.
-    Wine has its "<a href="http://www.dssd.ca/Docs/";>Guides</a>", like the Wine User Guide etc.
+    Wine has its "<a href="http://www.winehq.org/Docs/";>Guides</a>", like the Wine User Guide etc.
     The SGML source of the Guides can be found in the Wine CVS tree.
 
     </p>
@@ -385,7 +385,8 @@
     the workings of their patch at all !)
     </p>
     <p>If you spend a lot of time monitoring either the newsgroup or wine-users 
-    you are a good candidate for suggesting updates to the <a href="http://www.winehq.org/docs/wine-faq/t1.shtml";>wine FAQ.</a>
+    you are a good candidate for suggesting updates to the 
+    <a href="http://www.winehq.org/?page=faq#Who_Maintains_this_FAQ";>wine FAQ.</a>
     </p>
     <p>
     The documentation updates would be done by sending "cvs diff"s of the
Index: templates/en/faq.template
===================================================================
RCS file: /home/wine/lostwages/templates/en/faq.template,v
retrieving revision 1.4
diff -u -r1.4 faq.template
--- templates/en/faq.template	16 Apr 2003 18:37:17 -0000	1.4
+++ templates/en/faq.template	26 May 2003 04:17:56 -0000
@@ -242,19 +242,19 @@
  on to Alexandre Julliard, who has run it ever since. A <a href="news:comp.emulators.ms-windows.wine";>newsgroup</a>
  was created in July 1994. Over the years, ports for other Unixes have been added, 
  along with support for Win32 as Win32 applications became popular.</p>
- <p>For more information,  see <a href="http://www.winehq.com/about.shtml";>http://www.winehq.com/about.shtml</a></p>
+ <p>For more information,  see <a href="http://www.winehq.com/about";>http://www.winehq.com/about</a></p>
  
 <h3><a name="What_is_the_current_version_of_Wine"></a>What is the current version of Wine?</h3>
 
 <p>A new version of Wine is distributed about every month. You will be able to keep up on all the
  latest releases by reading the newsgroup <a href="news:comp.emulators.ms-windows.wine";>comp.emulators.ms-windows.wine</a>, 
  or by visiting the <a href="http://www.winehq.com";>Wine HQ homepage</a>.  When downloading Wine from your FTP site
- of choice (see <a href="http://www.winehq.com/download.shtml";>The Download page</a> for some of these choices),
+ of choice (see <a href="http://www.winehq.com/download";>The Download page</a> for some of these choices),
  you can make sure that you are getting the latest version by watching the version numbers in the distribution
  filename.  For instance, the distribution released on October 31, 2002 was called <tt>Wine-20021031.tar.gz</tt>.
  Patch files are also available. If you are current to the previous version, you can download and apply 
  just the current patch file rather than the entire new distribution. The patch filenames follow the same
- conventions as the monthly distribution. <a href="http://www.winehq.com/dev.shtml";>Read-only CVS</a> access is also available.</p> 
+ conventions as the monthly distribution. <a href="http://www.winehq.com/cvs";>Read-only CVS</a> access is also available.</p> 
 
 <h3><a name="What_is_the_current_Status_of_Wine"></a>What is the current Status of Wine?</h3>
 
@@ -503,7 +503,7 @@
 numbers for year, month and date, respectively. The latest one is the one to get.</p>
  
 <p>Wine binary packages are available for several OS'es and distributions.
-See <a href="http://www.winehq.com/download.shtml";>the download page</a> for the most recent list.</p>
+See <a href="http://www.winehq.com/download";>the download page</a> for the most recent list.</p>
  
 <h3><a name="Is_there_a_CVS_tree"></a>Is there a CVS tree?</h3>
 
@@ -534,7 +534,7 @@
 near you.  
  
 For a CVS mirror list, see 
-<a href="http://www.winehq.com/dev.shtml";>http://www.winehq.com/dev.shtml </a></p>
+<a href="http://www.winehq.com/cvs";>http://www.winehq.com/cvs</a></p>
 
 <p>Patch files are also available, so that you don't have to download, install,
 and configure the entire distribution each week if you are current to
@@ -732,13 +732,13 @@
 
 <h3><a name="Is_there_any_documentation_for_Wine"></a>Is there any documentation for Wine?  </h3>
 
-<p>Yes, see <a href="http://www.winehq.com/support.shtml";>http://www.winehq.com/support.shtml</a>.</p>
+<p>Yes, see <a href="http://www.winehq.com/support";>http://www.winehq.com/support</a>.</p>
 
 <h3><a name="I_couldnt_find_the_answer_to_my"></a>I couldn't find the answer to my question in the documentation, 
 but I've written a document explaining how to solve it. What should I do?</h3>
 
 <p>Updates and additions to the Wine documentation directory should be sent to the wine-patches mailing list at 
-<a href="http://www.winehq.com/dev.shtml#ml";>http://www.winehq.com/dev.shtml#ml</a>. Website and FAQ additions 
+<a href="http://www.winehq.com/forums";>http://www.winehq.com/forums</a>. Website and FAQ additions 
 should be added to the appropriate Wine Knowledgebase directory.</p> 
 
 <h3><a name="Is_there_a_Usenet_newsgroup_for_Wine"></a>Is there a Usenet newsgroup for Wine?</h3>
@@ -784,7 +784,7 @@
  
 <p>If you can program C, that's a good start. Download the sources via CVS, subscribe to the mailing lists, 
 look around the source, and pay attention to the <tt>comp.emulators.ms-windows.wine</tt> newsgroup and the mailing lists 
-(<a href="http://www.winehq.com/dev.shtml#ml";>http://www.winehq.com/dev.shtml#ml</a>). See if there's anything 
+(<a href="http://www.winehq.com/forums";>http://www.winehq.com/forums</a>). See if there's anything 
 that you think you can fix or work on. You won't have much trouble finding areas that need work in Wine (grep for FIXMEs in the source).</p>   
 
 <h3><a name="How_can_I_help_contribute_to_the_Wine"></a>How can I help contribute to the Wine project, and in what way(s)?</h3>
@@ -804,7 +804,7 @@
 <h3><a name="I_have_written_some_code_that_I_would"></a>I have written some code that I would like to submit to the Wine project. How do I go about doing this?</h3>
 
 <p>Patches are greatly appreciated and should be submitted to the wine-patches mailing list 
-(<a href="http://www.winehq.com/dev.shtml#ml";>http://www.winehq.com/dev.shtml#ml</a>).Also see this page 
+(<a href="http://www.winehq.com/forums";>http://www.winehq.com/forums</a>).Also see this page 
 for a description of what happens to submitted patches.</p>
 
 <a href="#TOP">Back to top</a>
Index: templates/en/status_dlls.template
===================================================================
RCS file: /home/wine/lostwages/templates/en/status_dlls.template,v
retrieving revision 1.1
diff -u -r1.1 status_dlls.template
--- templates/en/status_dlls.template	25 Mar 2003 18:56:54 -0000	1.1
+++ templates/en/status_dlls.template	26 May 2003 04:17:57 -0000
@@ -339,7 +339,7 @@
     <tr>
       <td>odbc32: ODBC Database Manager</td>
       <td class="adequate"><a
-      href="http://www.winehq.org/Docs/wine-user/odbc.shtml";>Adequate</a></td>
+      href="http://www.winehq.org/Docs/wine-user/odbc.html";>Adequate</a></td>
       <td><a href="?issue=115#ODBC and Wine">#115</a></td>
       <td class="pct70">70% complete<br>(no Windows ODBC driver support, only UNIX)</td>
       <td></td>
Index: templates/en/status_wine.template
===================================================================
RCS file: /home/wine/lostwages/templates/en/status_wine.template,v
retrieving revision 1.1
diff -u -r1.1 status_wine.template
--- templates/en/status_wine.template	25 Mar 2003 18:56:54 -0000	1.1
+++ templates/en/status_wine.template	26 May 2003 04:17:59 -0000
@@ -55,7 +55,7 @@
     </tr>
     <tr>
       <td>Wine's fundamental architecture</td>
-      <td class="outdadeq"><a href="http://www.winehq.com/docs/wine-devel/architecture.shtml";>Getting outdated</a></td>
+      <td class="outdadeq"><a href="http://www.winehq.com/docs/wine-devel/architecture.html";>Getting outdated</a></td>
           <td><a href="?issue=50#Feature: Wine Architecture by Ove Kåven">#50</a></td>
       <td class="pct85">85% complete</td>
       <td>Alexandre Julliard</td>
@@ -138,7 +138,7 @@
     </tr>
     <tr>
       <td>Native DLL overrides</td>
-      <td class="good"><a href="http://www.winehq.org/docs/wine-user/dll-config.shtml";>Good</a></td>
+      <td class="good"><a href="http://www.winehq.org/docs/wine-user/dll-config.html";>Good</a></td>
       <td><a href="?issue=46#Feature: DLL overrides by Ove Kåven">#46</a>,
       <a href="?issue=134#Native vs.Builtin DLL's">#134</a></td>
           <td class="pct95">95% complete</td>
Index: templates/en/winelib.template
===================================================================
RCS file: /home/wine/lostwages/templates/en/winelib.template,v
retrieving revision 1.2
diff -u -r1.2 winelib.template
--- templates/en/winelib.template	25 Mar 2003 17:08:01 -0000	1.2
+++ templates/en/winelib.template	26 May 2003 04:17:59 -0000
@@ -71,7 +71,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="http://www.winehq.org/Docs/winelib-user/winelib-getting-started.shtml#WINEMAKER-INTRODUCTION";>documentation</a>
+        <a href="http://www.winehq.org/Docs/winelib-user/winelib-getting-started.html#WINEMAKER-INTRODUCTION";>documentation</a>
 
         for more information.</dd>
     <dt>GNU tools based build process</dt>

[Index of Archives]     [Gimp for Windows]     [Red Hat]     [Samba]     [Yosemite Camping]     [Graphics Cards]     [Wine Home]

  Powered by Linux