r15828 by christoph - intro.html: fixed typos

scribus-commit scribus-commit at lists.scribus.net
Tue Nov 9 03:11:06 CET 2010


Author: christoph
Date: Tue Nov  9 02:11:06 2010
New Revision: 15828

URL: http://scribus.info/websvn/listing.php?repname=Scribus&sc=1&rev=15828
Log:
intro.html: fixed typos

Modified:
    trunk/Scribus/doc/en/intro.html

Modified: trunk/Scribus/doc/en/intro.html
URL: http://scribus.info/websvn/diff.php?repname=Scribus&rev=15828&path=/trunk/Scribus/doc/en/intro.html
==============================================================================
--- trunk/Scribus/doc/en/intro.html (original)
+++ trunk/Scribus/doc/en/intro.html Tue Nov  9 02:11:06 2010
@@ -21,9 +21,9 @@
 </i>
 </blockquote>
 
-<p>So, that&rsquo;s how the Scribus documentation started, but as Scribus attracted more developers, and the more ambitious the project became, the less maintainable the documentation appeared to be for a single person. As is natural with successful Open Source projects, more people volunteered to expand the scope of information available about Scribus. It started with the <a href="http://wiki.scribus.net/index.php/Main_Page">Scribus Wiki</a>, an ongoing successful collaborative effort, and reached a climax with the publication of the <a href="http://www.amazon.com/Scribus-Open-Source-Publishing-Christoph-Sch%C3%A4fer/dp/0956078001/ref=sr_1_1?s=books&ie=UTF8&qid=1289106422&sr=1-1">Official Scribus Manual</a>.</p>
-<p>But the documentation efforts didn&rsquo;t stop with the publication of a printed book, quite the contrary! A review of the available documentation showed that many documents, while appropriately describing Scribus&rsquo;s features at the time they were written, needed an update to reflect the vast number of features Scribus that had been added in the meantime, whereas some workarounds for Linux-related issues simply aren&rsquo;t necessary any longer on modern Linux desktops.</p>
+<p>So, that&rsquo;s how the Scribus documentation started, but as Scribus attracted more developers, and the more ambitious the project became, the less maintainable the documentation appeared to be for a single person. As is natural with successful Open Source projects, more people volunteered to expand the scope of information available about Scribus. It started with the <a href="http://wiki.scribus.net/index.php/Main_Page">Scribus Wiki</a>, an ongoing successful collaborative effort, mostly written by users fro users, and reached a climax with the publication of the <a href="http://www.amazon.com/Scribus-Open-Source-Publishing-Christoph-Sch%C3%A4fer/dp/0956078001/ref=sr_1_1?s=books&ie=UTF8&qid=1289106422&sr=1-1">Official Scribus Manual</a>.</p>
+<p>But the documentation efforts didn&rsquo;t stop with the publication of a printed book, quite the contrary! A review of the available documentation showed that many documents, while appropriately describing Scribus&rsquo;s features at the time they were written, needed an update to reflect the vast number of features in Scribus that had been added in the meantime, whereas some workarounds for Linux-related issues simply aren&rsquo;t necessary any longer on modern Linux desktops.</p>
 <p>The growing complexity of Scribus also collided with the original concept of the documentation, which can be described as as a mix of a diary and a field report, with some additional elements of a manual for sysadmins. This approach was undoubtedly necessary at the time the original documentation was written, as Scribus was first and foremost a Linux program back then. Fortunately, the Linux desktop is very user-friendly these days, and Scribus has been ported to other platforms as well.</p>
-<p>As a result, the Scribus documentation can now focus on a more structured approach, which will provide much more information about the practical use of the program. The priceless background information from Peter Linnell in the original documentation will naturally survive, albeit in another form, i.e., it will be spread across those documents, for which the respective information seems applicable. And of course Peter Linnell is still <b>mrdocs</b>, which is yet another reason to have great expectations when it comes to further improvements to the Scribus documentation&nbsp;...</p>
+<p>As a result, the Scribus documentation can now focus on a more structured approach, which will provide much more information about the practical use of the program. The priceless background information from Peter Linnell in the original documentation will naturally survive, albeit in another form, i.e., it will be spread across those documents for which the respective information seems applicable. And of course Peter Linnell is still <b>mrdocs</b>, which is yet another reason to have great expectations when it comes to further improvements to the Scribus documentation&nbsp;...</p>
 </body>
 </html>




More information about the scribus-commit mailing list