Thread: [ro-oslib-commits] SF.net SVN: ro-oslib: [243] trunk/website

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Revision: 243
          http://ro-oslib.svn.sourceforge.net/ro-oslib/?rev=243&view=rev
Author:   jtytgat
Date:     2007-04-14 16:15:03 -0700 (Sat, 14 Apr 2007)

Log Message:
-----------
- Updated details of the CVS -> SVN repository change.
- Consistent spelling for RISC OS, etc.

Modified Paths:
--------------
    trunk/website/archives.html
    trunk/website/contact.html
    trunk/website/download.html
    trunk/website/faq.html
    trunk/website/future.html
    trunk/website/guide.html
    trunk/website/history.html
    trunk/website/index.html
    trunk/website/release-6.80.html
    trunk/website/release-6.90.html

Added Paths:
-----------
    trunk/website/svn.html

Removed Paths:
-------------
    trunk/website/cvs.html

Modified: trunk/website/archives.html
===================================================================

--- trunk/website/archives.html	2007-04-14 17:46:43 UTC (rev 242)
+++ trunk/website/archives.html	2007-04-14 23:15:03 UTC (rev 243)
@@ -3,7 +3,7 @@
 <head>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
    <meta name="GENERATOR" content="Zap HoTMeaL">
-   <meta name="content" content="Acorn, Risc OS, OSLib">
+   <meta name="content" content="Acorn, RISC OS, OSLib">
    <meta name="Author" content="Tony van der Hoff">
    <title>The OSLib GPL Release - Archives</title>
 </head>
@@ -31,7 +31,7 @@
                             <li><a href="download.html">Obtaining OSLib</a>
                             <ul>
                                 <li><a href="archives.html">ZIP Archives</a></li>
-                                <li><a href="cvs.html">Source via CVS</a></li>
+                                <li><a href="svn.html">Source via SVN</a></li>
                             </ul>
                             </li>
                             <li><a href="contact.html">Contacts</a></li>
@@ -85,7 +85,7 @@
         <ul>
             <li><p>
                     <b><a href="release-6.90.html">Version 6.90</a></b>
-                    (02 January 2006).  Adds some Reporter SWIs, and
+                    (02 January 2007).  Adds some Reporter SWIs, and
                     fixes bugs in PCI, OS, and ColourTrans.
             </p></li>
 

Modified: trunk/website/contact.html
===================================================================
--- trunk/website/contact.html	2007-04-14 17:46:43 UTC (rev 242)
+++ trunk/website/contact.html	2007-04-14 23:15:03 UTC (rev 243)
@@ -3,7 +3,7 @@
 <head>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
    <meta name="GENERATOR" content="Zap HoTMeaL">
-   <meta name="content" content="Acorn, Risc OS, OSLib">
+   <meta name="content" content="Acorn, RISC OS, OSLib">
    <meta name="Author" content="Tony van der Hoff">
    <title>The OSLib GPL Release - Contacts</title>
 </head>
@@ -32,7 +32,7 @@
 <li><a href="download.html">Obtaining OSLib</a>
 <ul>
 <li><a href="archives.html">ZIP Archives</a></li>
-<li><a href="cvs.html">Source via CVS</a></li>
+<li><a href="svn.html">Source via SVN</a></li>
 </ul></li>
 <li><a href="contact.html">Contacts</a></li>
 <li><a href="faq.html">FAQ</a></li>
@@ -76,7 +76,7 @@
 </li>
 
 <li><b>oslib-commits</b> -- This is a mail-list which sends
-automatically-generated information whenever an update is committed to the CVS
+automatically-generated information whenever an update is committed to the SVN
 repository. If you want to keep bang up-to-date with OSLib, then this is for you.
 Subscribe via the
 <a href="http://sourceforge.net/projects/ro-oslib/">
@@ -114,6 +114,10 @@
 administers these web pages, and arranges periodic releases of the library.
 </li>
 
+<li><a href="mailto:Joh...@aa...">John Tytgat</a> -- John is driving
+the start of OSLib 7.00 development.
+</li>
+
 </ul>
 
 </td></tr> <!-- end main content -->

Deleted: trunk/website/cvs.html
===================================================================
--- trunk/website/cvs.html	2007-04-14 17:46:43 UTC (rev 242)
+++ trunk/website/cvs.html	2007-04-14 23:15:03 UTC (rev 243)
@@ -1,125 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta name="GENERATOR" content="Zap HoTMeaL">
-   <meta name="content" content="Acorn, Risc OS, OSLib">
-   <meta name="Author" content="Tony van der Hoff">
-   <title>The OSLib GPL Release - cvs</title>
-</head>
-<body text="#000000" bgcolor="#FFFFC0" link="#0000FF" vlink="#800080" alink="#FF00FF">
-
-<p>
-<center><h1>Obtaining OSLib via CVS</h1></center>
-
-<hr>
-
-<!--Begin outer table -->
-<center>
-<table BORDER=0 CELLSPACING=10 CELLPADDING=0 WIDTH="100%" >
-<tr VALIGN=TOP>
-<td>
-
-
-<!-- contents list Table -->
-<table BORDER=0 CELLSPACING=0 CELLPADDING=10 WIDTH="250" >
-
-<!-- Contents list -->
-<tr BGCOLOR="#80ffff">
-<td>
-<h2>Site Contents</h2>
-<ul>
-<li><a href="history.html">History and Copyright</a></li>
-<li><a href="future.html">Future Development</a></li>
-<li><a href="download.html">Obtaining OSLib</a>
-<ul>
-<li><a href="archives.html">ZIP Archives</a></li>
-<li><a href="cvs.html">Source via CVS</a></li>
-</ul></li>
-<li><a href="contact.html">Contacts</a></li>
-<li><a href="faq.html">FAQ</a></li>
-</ul>
-<a href="index.html">Home</a>
-</td></table> <!-- end contents list table -->
-
-<td ALIGN=LEFT> <!--Begin main content table -->
-
-<p><h2><a name="summary">Summary</a></h2>
-
-<p>The sources for OSLib, OSLibSupport, and the various build tools are
-freely available via CVS from SourceForge.
-
-<p>You may browse the repository using <a
-href="http://ro-oslib.cvs.sourceforge.net/ro-oslib">ViewCVS</a>.
-
-<p>In order to check out the repository to a local directory on your RISC OS
-machine, you'll need a CVS client running. <a
-href="http://www.cvs.riscos.org.uk">John Tytgat's port</a> is suitable, athough
-the front end application is out of date in respect to the main application,
-so it's probably best to use the command line interface. In order to
-correctly perform the filename translation from UNIX style to RISC OS, you'll
-need to set suffix swapping (either in the application window or via the
-environment variable UnixEnv$cvs$sfix) to include the extensions
-c:cc:h:swi:asm:s:Hdr:y.
-
-<p>The alternative is to check out the project onto a Linux box. If you're
-using Linux, you'll know how to do this. OSLib and its tools may be built under Linux,
-or under RISC OS. To do the latter, it is necessary to change all
-filenames from UNIX &lt;name&gt;.&lt;ext&gt; format to the RISC OS
-&lt;dir&gt;.&lt;name&gt; format. This is most easily achieved by using Tony
-van der Hoff's <a href="http://www.vanderhoff.org/software/risc_os/unixify.zip">Unixify</a>
-command-line utility. The archive contains a couple of example TaskObey
-files, one of which shows how to RISCOSify the OSLib sandbox.
-
-<p>Whichever platform you choose to use, the anonymous checkout procedure is
-similar:
-
-<ol>
-
-<li>Set the environment variable CVSROOT to
-:pserver:ano...@ro...:/cvsroot/ro-oslib</li>
-
-<li>Log in to SourceForge using the command "cvs login"; when prompted for a
-password, simply press Enter.</li>
-
-<li>Set the working directory to wherever you want your sandbox to end up
-(alternatively use -dir &lt;dir&gt; in the cvs checkout command, but this can
-involve a lot of typing in a deeply-nested structure).</li>
-
-<li>Check out the repository, using the command
-"cvs&nbsp;-z3&nbsp;checkout&nbsp;-P&nbsp;OSLib". This will get you the head
-revision, which is what most CVS users will want. However, be warned that
-this is in development, and may contain some unwanted surprises. To obtain
-the sources for the current stable release version, you need to specify the
-version tag; i.e.
-"cvs&nbsp;-z3&nbsp;checkout&nbsp;-dP&nbsp;-r&nbsp;&lt;tag&gt;&nbsp;OSLib",
-where &lt;tag&gt; is the OSlib version, e.g. "oslib-690".</li>
-
-</ol>
-
-<p>There is quite a lot of code, so it may take a little while on a slow
-link, but I'm sure you'll find it whorthwhile! A !Readme file in the main
-application directory explains how to build OSLib under RISC OS. You will
-need a C compiler, a Linker, a Make utility, and an ARM assembler in addition
-to the tools provided.
-
-</td></tr> <!-- end main content -->
-
-</table> <!-- end outer table -->
-</center>
-
-<hr WIDTH="100%">
-
-<a href="http://validator.w3.org/check/referer"><img border="0"
-src="http://www.w3.org/Icons/valid-html401"
-alt="Valid HTML 4.01!" height="31" width="88"></a>
-
-<div align=right><font size=-1>
-
-Tony van der Hoff,
-<br>03 February 2007
-
-</font></div>
-
-</body>
-</html>

Modified: trunk/website/download.html
===================================================================
--- trunk/website/download.html	2007-04-14 17:46:43 UTC (rev 242)
+++ trunk/website/download.html	2007-04-14 23:15:03 UTC (rev 243)
@@ -3,7 +3,7 @@
 <head>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
    <meta name="GENERATOR" content="Zap HoTMeaL">
-   <meta name="content" content="Acorn, Risc OS, OSLib">
+   <meta name="content" content="Acorn, RISC OS, OSLib">
    <meta name="Author" content="Tony van der Hoff">
    <title>The OSLib GPL Release - Download</title>
 </head>
@@ -32,7 +32,7 @@
 <li><a href="download.html">Obtaining OSLib</a>
 <ul>
 <li><a href="archives.html">ZIP Archives</a></li>
-<li><a href="cvs.html">Source via CVS</a></li>
+<li><a href="svn.html">Source via SVN</a></li>
 </ul></li>
 <li><a href="contact.html">Contacts</a></li>
 <li><a href="faq.html">FAQ</a></li>
@@ -57,21 +57,21 @@
 <p>First, the <a href="archives.html"><b>OSLib Library</b></a> in binary
 (ALF) form, complete with C and assembler headers, is available for download
 as a zipped archive, for download. This is all you need to link with your own
-applications to provide access to all the RISC O S SWI calls from assembler
+applications to provide access to all the RISC&nbsp;OS SWI calls from assembler
 or C. The archive contains both 26-bit and 32-bit versions, for linking with
 the appropriate Stubs or UnixLib.
 
 <p>Secondly, the <a href="archives.html"><b>OSLibSupport library</b></a>,
 again in binary (ALF) form, complete with C, is available for download as a
 zipped archive, for download. This is a C library of support functions,
-designed to make programming the RISC OS WIMP and Toolbox modules as easy as
+designed to make programming the RISC&nbsp;OS WIMP and Toolbox modules as easy as
 possible.
 
 <p>Third, a <a href="archives.html"><b>StrongHelp</b></a> manual covering the
 entire API from C is available for each version.
 
-<p>Finally, the <a href="cvs.html"><b>complete source</b></a> for the project
-is now available via CVS from
+<p>Finally, the <a href="svn.html"><b>complete source</b></a> for the project
+is now available via SVN from
 SourceForge. This includes all source files, together with the tools
 necessary to build the library. In addition, Makefiles are provided to build
 the tools, and the library, from scratch, out of the box, with just one

Modified: trunk/website/faq.html
===================================================================
--- trunk/website/faq.html	2007-04-14 17:46:43 UTC (rev 242)
+++ trunk/website/faq.html	2007-04-14 23:15:03 UTC (rev 243)
@@ -32,7 +32,7 @@
 <li><a href="download.html">Obtaining OSLib</a>
 <ul>
 <li><a href="archives.html">ZIP Archives</a></li>
-<li><a href="cvs.html">Source via CVS</a></li>
+<li><a href="svn.html">Source via SVN</a></li>
 </ul></li>
 <li><a href="contact.html">Contacts</a></li>
 <li><a href="faq.html">FAQ</a></li>
@@ -66,13 +66,13 @@
 
 <ul>
 
-<li> <a href="#wide file handles"> What are wide file handles and why are
+<li><a href="#wide file handles">What are wide file handles and why are
 8-bit handles retained?</a> </li>
 
-<li> <a href="#signed ints"> Why are file sizes and os_t typed as signed
+<li><a href="#signed ints">Why are file sizes and os_t typed as signed
 ints?</a> </li>
 
-<li> <a href="#command line"> What command line should I use for compiling
+<li><a href="#command line">What command line should I use for compiling
 or assembling a program using OSLib?</a> </li>
 
 </ul>
@@ -101,11 +101,6 @@
 Does OSLib support 32-bit architectures?</a></li>
 
 <li>
-<a href="#Why both">
-Why do the distribution archives contain both 32-bit and 26-bit versions of
-the library?</a></li>
-
-<li>
 <a href="#tboxlib">
 Why does my toolbox application crash when linked with OSLib and tboxlibs?
 </a></li>
@@ -164,7 +159,7 @@
 <blockquote>
 
 OSLib originally defined file handles to be 8 bits wide. This was based on
-inside knowledge of the OS, and even under RISC OS 4, no file handle greater
+inside knowledge of the OS, and even under RISC&nbsp;OS 4, no file handle greater
 than &amp;FF is ever issued. However, the PRMs do specify that file handles
 should be 32 bits wide for future compatibility.
 
@@ -226,19 +221,50 @@
 <p>
 A generalised command line for Acorn (Norcroft) C using standard C, OSLibSupport,
 and OSLib would be something like this:<br>
-cc -IC:,OSLibSupport:,OSLib: program.c -o program.o<br>
+<blockquote>
+  <code>
+cc -IC:,OSLibSupport:,OSLib: C:o.stubs OSLib:o.OSLib OSLibSupport:o.OSLibSupport -o program.o program.c
+  </code>
+</blockquote>
+or:
+<blockquote>
+  <code>
+cc -IC:,OSLibSupport:,OSLib: -c program.c -o program.o<br>
 link program.o C:o.stubs OSLib:o.OSLib OSLibSupport:o.OSLibSupport -output program
+  </code>
+</blockquote>
 <p>
 For GCC (with UnixLib) this becomes somewhat simpler with the compile and link
-steps merged: <br>
+steps merged:<br>
+<blockquote>
+  <code>
 gcc program.c -I OSLib: -I OSLibSupport: OSLib:o.OSLib OSLibSupport:o.OSLibSupport -o program
+  </code>
+</blockquote>
+or:
+<blockquote>
+  <code>
+gcc -I OSLib: -I OSLibSupport: -c program.c -o program
+gcc program.o OSLib:o.OSLib OSLibSupport:o.OSLibSupport -o program
+  </code>
+</blockquote>
 <p>
 ObjASM doesn't seem to be able to expand path variables in the command line, so
 it is necessary to bodge things a bit:<br>
+<blockquote>
+  <code>
 do ObjASM -I &lt;OSLibPath&gt; program.s program.o<br>
 link program.o -output program
+  </code>
+</blockquote>
 <p>
-I don't yet know how to invoke GCC assembler, sorry.
+The GCC assembler can get invoked by:<br>
+<blockquote>
+  <code>
+gcc -I OSLib: -I OSLibSupport: -c program.s -o program.o<br>
+gcc program.o OSLib:o.OSLib OSLibSupport:o.OSLibSupport -o program
+  </code>
+</blockquote>
 
 </blockquote>
 
@@ -307,43 +333,24 @@
 <H4>Does OSLib support 32-bit architectures?</H4>
 
 <blockquote>
-OSLib can be built for both 26 bit and 32 bit architectures. The source code
+<p>OSLib can be built using APCS-R and APCS-32 ABIs.  The former can only be used
+for running on 26-bit architectures, while the latter can run on both 26-bit and
+32-bit architectures.  APCS-R is deprecated and it is recommmended to have your
+programs built using APCS-32 for future compatibility with new ARM hardware.
+
+<p>The OSLib source code
 is identical for either. The binary distribution contains two ALF images:
-OSLib and OSLib32. The 32 bit version does not preserve the caller's
+OSLib (APCS-R) and OSLib32 (APCS-32). The 32 bit version does not preserve the caller's
 processor flags, the 26 bit one does; this may raise compatibility issues
-when migrating from one to the other. Link to whichever you wish.
-</blockquote>
+when migrating from one to the other so choose the correct one you're linking.
 
-<a href="#top">top</a> <a href="index.html">Home</a>
-<hr SIZE=4 WIDTH="100%">
+<p>Note that the last version of APCS-R OSLibSupport is 6.70.  All later versions of
+OSLibSupport library are APCS-32 only.
 
-<P><a name="Why both"></a>
-<H4>Why do the distribution archives contain both 32-bit and 26-bit versions
-of the library?</H4>
+<p>It is expected that OSLib 7.00 release will be APCS-32 only and that APCS-R support
+will be dropped for good.
+</blockquote>
 
-<blockquote>
-This requirement is imposed by the lack of general availability of the 32-bit
-Shared C Library (SCL) within RISC OS. Also, UNIXLib is currently still only
-available in 26-bit form.<br>
-
-<p>The APCS-R (26-bit) SCL and UNIXLib absolutely requires flag preservation
-across calls, and this wouldn't work with APCS-32 code. Also, the structure
-of the stubs has been changed significantly to accommodate a 32-bit system
-(where you can't use B to branch to the C library). A new C library is
-required to support those stubs.
-
-<p>It is not generally possible to mix APCS-R (26 bit) and APCS-32 (32 bit)
-code, and the linker will warn you if you try to do so. Hopefully everyone
-will be building APCS-32 soon, but until then people will need the APCS-R
-version of OSLib. <br>
-
-<p>It is presently impossible to mandate that application builders use only
-the 32-bit Shared C Library, despite the latter being readily available, and
-32-bit UNIXLib is currently unavailable.  As it is not possible to mix a
-32-bit OSLib with a 26-bit C library, the OSLib team are making both versions
-available, and will continue to do so until the 32-bit C libraries becomes
-the norm.<br> </blockquote>
-
 <a href="#top">top</a> <a href="index.html">Home</a>
 <hr SIZE=4 WIDTH="100%">
 

Modified: trunk/website/future.html
===================================================================
--- trunk/website/future.html	2007-04-14 17:46:43 UTC (rev 242)
+++ trunk/website/future.html	2007-04-14 23:15:03 UTC (rev 243)
@@ -3,7 +3,7 @@
 <head>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
    <meta name="GENERATOR" content="Zap HoTMeaL">
-   <meta name="content" content="Acorn, Risc OS, OSLib">
+   <meta name="content" content="Acorn, RISC OS, OSLib">
    <meta name="Author" content="Tony van der Hoff">
    <title>The OSLib GPL Release - Further Development</title>
 </head>
@@ -33,7 +33,7 @@
 <li><a href="download.html">Obtaining OSLib</a>
 <ul>
 <li><a href="archives.html">ZIP Archives</a></li>
-<li><a href="cvs.html">Source via CVS</a></li>
+<li><a href="svn.html">Source via SVN</a></li>
 </ul></li>
 <li><a href="contact.html">Contacts</a></li>
 <li><a href="faq.html">FAQ</a></li>

Modified: trunk/website/guide.html
===================================================================
--- trunk/website/guide.html	2007-04-14 17:46:43 UTC (rev 242)
+++ trunk/website/guide.html	2007-04-14 23:15:03 UTC (rev 243)
@@ -32,7 +32,7 @@
 into the call stack or however small the function in progress. This is
 done by keeping to a strict discipline (when I can be bothered :-)
 <P>&nbsp;&nbsp; Every function that everyone has ever written can return
-an error. Normally in RISC O S code this is done by returning an |os_error
+an error. Normally in RISC&nbsp;OS code this is done by returning an |os_error
 *|. In
 <BR>UNIX-style code, it is done by returning -1 and setting |errno|. Whatever
 the mechanism is, it *must* be checked when calling the function. Every
@@ -40,7 +40,7 @@
 an error, a |goto finish;| is executed immediately. (The only thing that
 can be done before "go to finish" is to assign the current function's error
 indicator.) At |finish:|, any local resources that may have been claimed
-(in C, chiefly malloced memory and file handlers, but under RISC O S also
+(in C, chiefly malloced memory and file handlers, but under RISC&nbsp;OS also
 windows, fonts, vectors, etc) are released. The current function then returns
 the error back to its own caller.
 <P>&nbsp;&nbsp; In this way, when any function returns an error, the whole
@@ -92,7 +92,7 @@
 <BR>&nbsp;
 <H3>
 DefMod and SWILib</H3>
-&nbsp; DefMod is a RISC O S programme written in C, and it looks as though
+&nbsp; DefMod is a RISC&nbsp;OS programme written in C, and it looks as though
 it uses OSLib. If it did, it could never have been written, as it logically
 <BR>precedes OSLib. So how was this done?
 <P>&nbsp;&nbsp; It uses a hand-crafted set of macros called SWILib. This
@@ -171,7 +171,7 @@
 <BR>&nbsp;
 <H3>
 Extensible Interfaces</H3>
-&nbsp;&nbsp; There are lots of cases in RISC O S of extensible interfaces:
+&nbsp;&nbsp; There are lots of cases in RISC&nbsp;OS of extensible interfaces:
 Wimp messages can be defined by anyone, for example. It is not good in
 these
 <BR>cases to put all of them into a file (swi.Wimp): this would mean that

Modified: trunk/website/history.html
===================================================================
--- trunk/website/history.html	2007-04-14 17:46:43 UTC (rev 242)
+++ trunk/website/history.html	2007-04-14 23:15:03 UTC (rev 243)
@@ -3,7 +3,7 @@
 <head>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
    <meta name="GENERATOR" content="Zap HoTMeaL">
-   <meta name="content" content="Acorn, Risc OS, OSLib">
+   <meta name="content" content="Acorn, RISC OS, OSLib">
    <meta name="Author" content="Tony van der Hoff">
    <title>The OSLib GPL Release - History</title>
 </head>
@@ -33,7 +33,7 @@
 <li><a href="download.html">Obtaining OSLib</a>
 <ul>
 <li><a href="archives.html">ZIP Archives</a></li>
-<li><a href="cvs.html">Source via CVS</a></li>
+<li><a href="svn.html">Source via SVN</a></li>
 </ul></li>
 <li><a href="contact.html">Contacts</a></li>
 <li><a href="faq.html">FAQ</a></li>

Modified: trunk/website/index.html
===================================================================
--- trunk/website/index.html	2007-04-14 17:46:43 UTC (rev 242)
+++ trunk/website/index.html	2007-04-14 23:15:03 UTC (rev 243)
@@ -3,7 +3,7 @@
 <head>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
    <meta name="GENERATOR" content="Zap HoTMeaL">
-   <meta name="content" content="Acorn, Risc OS, OSLib">
+   <meta name="content" content="Acorn, RISC OS, OSLib">
    <meta name="Author" content="Tony van der Hoff">
    <title>The OSLib GPL Release</title>
 </head>
@@ -25,7 +25,7 @@
 -->
 
 <!-- Begin header -->
-<center><h1>The RISC OS OSLib GPL Release</h1></center>
+<center><h1>The RISC&nbsp;OS OSLib GPL Release</h1></center>
 
 <hr>
 
@@ -48,7 +48,7 @@
 <li><a href="download.html">Obtaining OSLib</a>
 <ul>
 <li><a href="archives.html">ZIP Archives</a></li>
-<li><a href="cvs.html">Source via CVS</a></li>
+<li><a href="svn.html">Source via SVN</a></li>
 </ul></li>
 <li><a href="contact.html">Contacts</a></li>
 <li><a href="faq.html">FAQ</a></li>
@@ -65,12 +65,12 @@
 <h3>Summary</h3>
 
 OSLib is a highly optimized interface library for the Application Programmers'
-Interface (API) for the Acorn series of 32 bit RISC OS computers. It is
+Interface (API) for the Acorn series of 32 bit RISC&nbsp;OS computers. It is
 a useful tool for application program writers for this platform. It is
 of no use for any other platform.
 
 <p>OSLib provides a set of functions and C headers For its target platform,
-to provide complete coverage of the RISC OS API (the so-called SWIs) as a set
+to provide complete coverage of the RISC&nbsp;OS API (the so-called SWIs) as a set
 of C/C++ and ARM Assembler headers, together with a thin veneer library.
 
 <p>OSLib is:
@@ -97,7 +97,7 @@
 or _swix(), both in terms of the compile time type checking that is available,
 and the size and speed of the code generated.
 
-<p>OSLib provides a very convenient interface to the RISC O�S programmer,
+<p>OSLib provides a very convenient interface to the RISC&nbsp;OS programmer,
 since all the facilities of the C compiler are available to catch errors
 and generate good code. It is very small, and code written using it is
 smaller and faster than code written using other means.
@@ -107,9 +107,9 @@
 <p>
 <h3>OSLibSupport</h3>
 Whilst not strictly part of OSLib, which specialises in providing an
-interface to the RISC OS API, the OSLib development team also maintain a
+interface to the RISC&nbsp;OS API, the OSLib development team also maintain a
 higher-level C library, providing an easier to use interface, via OSLib, to
-the more arcane parts of RISC OS, and deals with Events, Messages, Tasks,
+the more arcane parts of RISC&nbsp;OS, and deals with Events, Messages, Tasks,
 Exceptions, and Errors. This is distributed on the same basis and under the
 same licence conditions as OSLib itself.
 
@@ -122,7 +122,7 @@
 <hr WIDTH="100%">
 
 <!-- footer -->
-<p><center>The RISC OS OSLib project repository is hosted by SourceForge.
+<p><center>The <a href="http://sourceforge.net/projects/ro-oslib/">RISC&nbsp;OS OSLib project 'ro-oslib'</a> is hosted by SourceForge.
 <br>
 
 <!-- SourceForge Logo -->

Modified: trunk/website/release-6.80.html
===================================================================
--- trunk/website/release-6.80.html	2007-04-14 17:46:43 UTC (rev 242)
+++ trunk/website/release-6.80.html	2007-04-14 23:15:03 UTC (rev 243)
@@ -39,14 +39,14 @@
                 <tr BGCOLOR="#80FFFF"><td>
                     <a href="http://downloads.sourceforge.net/ro-oslib/OSLib-wide-6.80.zip">Library</a>
                     suitable for file systems with unlimited 
-                    files per directory (e.g. RISC OS 4,
+                    files per directory (e.g. RISC&nbsp;OS 4,
                     LanMan, or X-Files) (1080&nbsp;Kb)
                 </td></tr>
 
                 <tr BGCOLOR="#80FFFF"><td>
                     <a href="http://downloads.sourceforge.net/ro-oslib/OSLib-unix-6.80.zip">Library</a>
                     using UNIX file-naming conventions. 
-                    Suitable for building RISC-OS
+                    Suitable for building RISC&nbsp;OS
                     targets under UNIX/LINUX (1007&nbsp;Kb)
                 </td></tr>
 
@@ -59,8 +59,8 @@
                     <a href="http://downloads.sourceforge.net/ro-oslib/OSLibExamples-6.80.zip">Examples</a>
                     from the PRMs, but using OSLib (956&nbsp;Kb).<br />
                     Note that an example of a full WIMP application using 
-                    OSLib and the RISC OS toolbox can be found at
-                    <a         href="http://www.vanderhoff.org/software/risc_os/dustbin.zip">
+                    OSLib and the RISC&nbsp;OS toolbox can be found at
+                    <a href="http://www.vanderhoff.org/software/risc_os/dustbin.zip">
                         Tony's web site
                     </a>
                 </td></tr>

Modified: trunk/website/release-6.90.html
===================================================================
--- trunk/website/release-6.90.html	2007-04-14 17:46:43 UTC (rev 242)
+++ trunk/website/release-6.90.html	2007-04-14 23:15:03 UTC (rev 243)
@@ -64,8 +64,8 @@
                     <a href="http://downloads.sourceforge.net/ro-oslib/OSLibExamples-6.90.zip">Examples</a>
                     from the PRMs, but using OSLib (30&nbsp;Kb).<br />
                     Note that an example of a full WIMP application using
-                    OSLib and the RISC OS toolbox can be found at
-                    <a         href="http://www.vanderhoff.org/software/risc_os/dustbin.zip">
+                    OSLib and the RISC&nbsp;OS toolbox can be found at
+                    <a href="http://www.vanderhoff.org/software/risc_os/dustbin.zip">
                         Tony's web site
                     </a>
                 </td></tr>

Copied: trunk/website/svn.html (from rev 242, trunk/website/cvs.html)
===================================================================
--- trunk/website/svn.html	                        (rev 0)
+++ trunk/website/svn.html	2007-04-14 23:15:03 UTC (rev 243)
@@ -0,0 +1,100 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+   <meta name="GENERATOR" content="Zap HoTMeaL">
+   <meta name="content" content="Acorn, RISC OS, OSLib">
+   <meta name="Author" content="Tony van der Hoff">
+   <title>The OSLib GPL Release - SVN</title>
+</head>
+<body text="#000000" bgcolor="#FFFFC0" link="#0000FF" vlink="#800080" alink="#FF00FF">
+
+<p>
+<center><h1>Obtaining OSLib via SVN</h1></center>
+
+<hr>
+
+<!--Begin outer table -->
+<center>
+<table BORDER=0 CELLSPACING=10 CELLPADDING=0 WIDTH="100%" >
+<tr VALIGN=TOP>
+<td>
+
+
+<!-- contents list Table -->
+<table BORDER=0 CELLSPACING=0 CELLPADDING=10 WIDTH="250" >
+
+<!-- Contents list -->
+<tr BGCOLOR="#80ffff">
+<td>
+<h2>Site Contents</h2>
+<ul>
+<li><a href="history.html">History and Copyright</a></li>
+<li><a href="future.html">Future Development</a></li>
+<li><a href="download.html">Obtaining OSLib</a>
+<ul>
+<li><a href="archives.html">ZIP Archives</a></li>
+<li><a href="svn.html">Source via SVN</a></li>
+</ul></li>
+<li><a href="contact.html">Contacts</a></li>
+<li><a href="faq.html">FAQ</a></li>
+</ul>
+<a href="index.html">Home</a>
+</td></table> <!-- end contents list table -->
+
+<td ALIGN=LEFT> <!--Begin main content table -->
+
+<p><h2><a name="summary">Summary</a></h2>
+
+<p>The sources for OSLib and OSLibSupport, the build tools and even the
+contents of this website are freely available via SVN from <a href="http://sourceforge.net/">SourceForge</a>.
+
+<p>You may browse the repository using <a
+href="http://ro-oslib.svn.sourceforge.net/viewvc/ro-oslib/">ViewVC</a>.
+
+<p>In order to check out the repository to a local directory on your RISC&nbsp;OS
+machine, you'll need an SVN client running. <a
+href="http://www.cp15.org/versioncontrol/">Alex Waugh's port</a> is the one you
+need. In order to correctly have RISC&nbsp;OS filetype support, you need to have
+set <code>*set svn$filetypeext ""</code>.
+
+<p>The alternative is to check out the project onto a non-RISC&nbsp;OS platform which is supported
+by the <a href="http://gccsdk.riscos.info/">GCCSDK</a> project using an SVN client suited
+for that host.
+
+<p>Whichever platform you choose to use, the anonymous checkout procedure is
+similar : check out the repository, using the command <code>svn co https://ro-oslib.svn.sourceforge.net/svnroot/ro-oslib/trunk oslib</code>. This will get you the head revision, which is what most SVN users will want. However, be warned that
+this is in development, and may contain some unwanted surprises.
+
+<p>To obtain
+the sources for the current stable release version, you need to specify the version tag; i.e.
+<code>svn co https://ro-oslib.svn.sourceforge.net/svnroot/ro-oslib/tags/&lt;tag&gt; oslib</code>,
+where <code>&lt;tag&gt;</code> is the specic OSlib version wanted, like e.g. oslib-690.</li>
+
+<p>There is quite a lot of code, so it may take a little while on a slow
+link, but I'm sure you'll find it whorthwhile! A <code>!Readme</code> file in the
+application directory !OsLib explains how to build OSLib under RISC&nbsp;OS or other
+GCCSDK supported host using the cross-compiler. You will
+need a C compiler, a Linker, a Make utility, and an ARM assembler in addition
+to the tools provided.
+
+</td></tr> <!-- end main content -->
+
+</table> <!-- end outer table -->
+</center>
+
+<hr WIDTH="100%">
+
+<a href="http://validator.w3.org/check/referer"><img border="0"
+src="http://www.w3.org/Icons/valid-html401"
+alt="Valid HTML 4.01!" height="31" width="88"></a>
+
+<div align=right><font size=-1>
+
+Tony van der Hoff,
+<br>03 February 2007
+
+</font></div>
+
+</body>
+</html>


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.


