Changeset 36621 for documented-examples/trunk/pagedimg-e/resources/collectionConfig.properties

Timestamp:

2022-09-15T16:31:38+12:00 (20 months ago)

Author:

anupama

Message:

Commit 2/2 Escaping apostrophes again in English collectionConfig.properties this time. (Other than French and English, no other language files were affected.) Previous commit message: Previous set of related commits were a big mistake. The apostrophes needed escaping in the collectionConfig.properties after all, because GTI won't even load entire translation chunks where apostrophes aren't escaped. So it may be ugly that GTI presents them unescaped, but at least it presents them when the apostrophes are escaped with Backslash.

File:

• documented-examples/trunk/pagedimg-e/resources/collectionConfig.properties (modified) (2 diffs)

documented-examples/trunk/pagedimg-e/resources/collectionConfig.properties

@@ -4 +4 @@
 shortDescription=<p>This collection contains a few newspapers from the <a href='http\://www.nzdl.org/cgi-bin/library?a=p&amp;p=about&amp;c=niupepa'>Niupepa</a> collection of Maori newspapers.</p>
 
-description1=<h3>How the collection works</h3> <p>Each newspaper issue consists of a set of images, one per page, and a set of text files for the OCR'd text. An item file links the set of pages into a single newspaper document. PagedImagePlugin is used to process the item files.</p>
+description1=<h3>How the collection works</h3> <p>Each newspaper issue consists of a set of images, one per page, and a set of text files for the OCR\'d text. An item file links the set of pages into a single newspaper document. PagedImagePlugin is used to process the item files.</p>
 
 description2=<p>There are two styles of item files, and this collection demonstrates both. The first uses a text based format, and consists of a list of metadata for the document, and a list of pages. Some examples are\: <i>Te Waka o Te Iwi, Vol. 1, No. 1</i> (in <tt>import/09/09_1_1.item</tt>) and <i>Te Whetu o Te Tau, Vol. 1, No. 3</i> (in <tt>import/10/10_1_3.item</tt>. This format allows specification of document level metadata, and a single list of pages.</p>
@@ -14 +14 @@
 description5=<p><tt>plugin PagedImagePlugin -documenttype hierarchy -process_exp xml.*\.item$ ... <br/> plugin PagedImagePlugin -documenttype paged ...</tt></p>
 
-description6=<p>XML based newpapers have been grouped into a folder called <tt>xml</tt>. This enables us to process these files differently, by utilising the <tt>process_exp</tt> option which all plugins support. The first PagedImagePlugin in the list looks for item files underneath the xml folder. These documents will be processed as hierarchical documents. Item files that don't match the process expression (i.e. aren't underneath the xml folder) will be passed onto the second PagedImagePlugin, and these are treated as paged documents.</p>
+description6=<p>XML based newpapers have been grouped into a folder called <tt>xml</tt>. This enables us to process these files differently, by utilising the <tt>process_exp</tt> option which all plugins support. The first PagedImagePlugin in the list looks for item files underneath the xml folder. These documents will be processed as hierarchical documents. Item files that don\'t match the process expression (i.e. aren\'t underneath the xml folder) will be passed onto the second PagedImagePlugin, and these are treated as paged documents.</p>
 
-description7=<p><b>Formatting</b> <p>Unlike in Greenstone 2, where the document formatting was modified to customize the display, in Greenstone 3 we rely for the rest on Greenstone's default behaviour.</p>
+description7=<p><b>Formatting</b> <p>Unlike in Greenstone 2, where the document formatting was modified to customize the display, in Greenstone 3 we rely for the rest on Greenstone\'s default behaviour.</p>