Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Diff of /README.txt [82647c] .. [8a5fe8] Maximize Restore

  Switch to side-by-side view

--- a/README.txt
+++ b/README.txt
@@ -1,32 +1,32 @@
 ADDING A NEW PAGE
 
-Adding a new page is very easy but requires a little bit of knowledge 
+Adding a new page is very easy but requires a little bit of knowledge
 and discipline.
 
-If you have not done so yet, look at the source of any page on the 
-site in your web browser. The main page index.htm is a good starting 
-point. You are looking for the <div id="content"> element. That's 
+If you have not done so yet, look at the source of any page on the
+site in your web browser. The main page index.htm is a good starting
+point. You are looking for the <div id="content"> element. That's
 where your new code will go.
 
-Start your new page. You only have to write the HTML that goes inside 
+Start your new page. You only have to write the HTML that goes inside
 the content element.
 
-Upload it, and supporting files/images. Then test to see that the 
-site puts the template around it properly. If it does not, chances 
-are that some tags are not properly closed. Check the syntax of your 
+Upload it, and supporting files/images. Then test to see that the
+site puts the template around it properly. If it does not, chances
+are that some tags are not properly closed. Check the syntax of your
 file.
 
 Once the file displays correctly in the browser, edit /header.php.
 
-At the beginning of header.php is the array $page that describes all 
-the pages added manually to this site. Add an entry to your page by 
-looking at one of the existing examples. Note that the list is 
+At the beginning of header.php is the array $page that describes all
+the pages added manually to this site. Add an entry to your page by
+looking at one of the existing examples. Note that the list is
 ordered.
 
 
 ADDING A NEW VERSION OF THE DOCUMENTATION
 
-Starting with enblend-enfuse 4.0 and with the 2009-2010 website, 
+Starting with enblend-enfuse 4.0 and with the 2009-2010 website,
 documentation is added to the site almost automatically:
   1. Fetch the latest enblend-enfuse source
   2. Build documentation
@@ -66,14 +66,14 @@
 
 2. Build documentation
 
-Bootstrap the code and make sure that the line "can build all 
-documentation:" toward the end of the makefile execution says "yes". 
+Bootstrap the code and make sure that the line "can build all
+documentation:" toward the end of the makefile execution says "yes".
 If it says that something is missing, fix it.
 
     $ make --makefile=Makefile.scm
     ...
     $ ./configure
-    ... 
+    ...
     can build all documentation:      yes
     ...
 
@@ -85,7 +85,7 @@
 
 3. Extract it from the XHTML context
 
-Enter the documentation folder and rename the folders for the 
+Enter the documentation folder and rename the folders for the
 website. Substitute V.V.V for the tagged version number
     $ cd doc/
     $ mv enblend.pdf enblend_V.V.V.pdf
@@ -93,8 +93,8 @@
     $ mv enblend.xhtml enblend_V.V.V.xhtml
     $ mv enfuse.xhtml enfuse_V.V.V.xhtml
 
-Extract the content from the XHTML context by using the shell script 
-located in the website's source code repository at src/apply.sh 
+Extract the content from the XHTML context by using the shell script
+located in the website's source code repository at src/apply.sh
 
 4. Upload it to the website
 
@@ -102,7 +102,7 @@
 folder on the website, and do the same with the enfuse documentation
 to enfuse.doc
 
-The website's template will integrate the new documentation 
+The website's template will integrate the new documentation
 automatically.
 
 Yuval Levy / 17-Dec-2009