Index: documented-examples/trunk/authen-e/resources/collectionConfig.properties
===================================================================
--- documented-examples/trunk/authen-e/resources/collectionConfig.properties	(revision 36437)
+++ documented-examples/trunk/authen-e/resources/collectionConfig.properties	(revision 36517)
@@ -1,6 +1,6 @@
 name=Authentication demo
-textdate=publication date: 
-textnumpages=no. of pages: 
-textsource=source ref: 
+textdate=publication date\: 
+textnumpages=no. of pages\: 
+textsource=source ref\: 
 section_chapter=chapter
 document_book=book
@@ -16,5 +16,5 @@
 shortDescription=Collection demonstrating document-level collection authentication in Greenstone 3.
 
-description1=<p>This demonstration collection contains the same material as the original Greenstone demo collection, but it includes some basic authentication commands. Two documents are publicly available (Farming snails 1 &amp; 2), while the others require logging in to view.</p> <p><center><b> To access this collection try user:</b> <i>demo</i> <b>and password:</b> <i>demo</i></center></p>
+description1=<p>This demonstration collection contains the same material as the original Greenstone demo collection, but it includes some basic authentication commands. Two documents are publicly available (Farming snails 1 &amp; 2), while the others require logging in to view.</p> <p><center><b> To access this collection try user\:</b> <i>demo</i> <b>and password\:</b> <i>demo</i></center></p>
 
 description2=<h3>How the collection works</h3><p> The collection configuration file is exactly the same as for the original demo collection apart from the authentication directives, one plugin option (and this description).</p>
@@ -22,5 +22,5 @@
 description3=<p>The authentication scheme controls access to the collection. It works in two steps. First it determines whether to restrict access to the collection as a whole or to individual documents in it, and in the latter case which documents those are (either by giving a list of private documents for which access is to be authenticated, or specifying that all documents are private except for a given list of public documents). Then for access-restricted documents it determines which user groups are to have access.</p>
 
-description4=<p>Authentication is activated using the <i>&lt;security&gt;</i> XML element in the collectionConfig.xml file. In the example of the authen-e collection, all <i>document</i>s are set to <i>private</i> access by default, with the <i>exception</i> that they are accessible to logged in members of a <i>group</i> called <i>"demo"</i>. The <i>security</i> element further defines a set of documents (<i>documentSet</i>) called "always-public" which contains 2 documents denoted by their document identifiers/OIDs (fb33fe and fb34fe). This documentSet specifies an exceptional case: the documents in the documentSet are <i>not</i> private access like other documents in the collection are by default, but can instead be accessed by anyone in <i>any</i> group, as no group is specified for their access. \n\
+description4=<p>Authentication is activated using the <i>&lt;security&gt;</i> XML element in the collectionConfig.xml file. In the example of the authen-e collection, all <i>document</i>s are set to <i>private</i> access by default, with the <i>exception</i> that they are accessible to logged in members of a <i>group</i> called <i>"demo"</i>. The <i>security</i> element further defines a set of documents (<i>documentSet</i>) called "always-public" which contains 2 documents denoted by their document identifiers/OIDs (fb33fe and fb34fe). This documentSet specifies an exceptional case\: the documents in the documentSet are <i>not</i> private access like other documents in the collection are by default, but can instead be accessed by anyone in <i>any</i> group, as no group is specified for their access. \n\
    <pre>&lt;security default_access="private" scope="document"&gt; \n\
 		&lt;exception&gt; \n\
@@ -44,7 +44,7 @@
 description7=<p>For more information on authentication in GS3, the different possibilities when using the <i>security</i> element in a GS3 collectionConfig file, and creating new users and adding them to groups, refer to the following pages on the Greenstone wiki \n\
 <ul> \n\
-<li><a href="http://wiki.greenstone.org/doku.php?id=en:user:authentication">Authentication in Greenstone</a></li> \n\
-<li><a href="http\://wiki.greenstone.org/doku.php?id=en:user_advanced:security">Security in Greenstone Collections</a></li> \n\
-<li><a href="http\://wiki.greenstone.org/doku.php?id=en:user_advanced:gs3_user_management">Greenstone 3 User Management</a></li> \n\
+<li><a href="http\://wiki.greenstone.org/doku.php?id=en\:user\:authentication">Authentication in Greenstone</a></li> \n\
+<li><a href="http\://wiki.greenstone.org/doku.php?id=en\:user_advanced\:security">Security in Greenstone Collections</a></li> \n\
+<li><a href="http\://wiki.greenstone.org/doku.php?id=en\:user_advanced\:gs3_user_management">Greenstone 3 User Management</a></li> \n\
 </ul> \n\
 </p>
